Test on your own devices # Alert. Notification. ACK. Test the complete path on your team’s phones before the first shift. Record the model, Android version, background settings and result for each scenario. [Create a trial account](https://app.acktide.com/signup) [Install Free](https://acktide.com/en/free.html) Product delivery tests ## Android notification and acknowledgment in the console These screenshots come from laboratory tests of the working app, with the interface in Russian. They show two stages: a system notification with an ACK button and the acknowledgment received in the web console. [](https://acktide.com/assets/delivery-notification.png) Prometheus → Alertmanager → Acktide test on an Android emulator, September 9, 2026. [](https://acktide.com/assets/delivery-ack.png) Separate Cloud test, September 19, 2026: the console shows acknowledgment received and the test user’s name. ### Recorded observations | Scenario | Test result | What was measured | | --- | --- | --- | | Critical alert with screen off and Doze enabled | 0.61 seconds | Time until the app confirmed receipt; notification was present | | Recovery after the server connection was interrupted | 3.46 seconds | Time until the app confirmed receipt | | Network loss and recovery without opening the app | 7.02 seconds | Includes the simulated network outage | | ACK from notification | Confirmed | The engineer’s name and action appeared on the server | Conditions: AOSP 15 emulator without Google Services; background scenarios tested on version 0.1.7 in September 2026. These are individual observations, not averages or an SLA. The emulator did not reproduce manufacturer-specific sleep restrictions on Motorola or HONOR devices. Battery use and extended background operation on those phones were not measured in this run. These results do not replace testing the current version on the physical phones used by your on-call engineers. [Download test results and conditions as JSON →](https://acktide.com/downloads/android-delivery-evidence.json) ## Preparation You need a connected source, primary and backup engineers in the route, and Android with Acktide installed and notifications allowed. For self-hosted setups, the phone needs HTTPS access to the server. Use a test service so the test cannot be mistaken for a production incident. ## First event - Send a test alert from monitoring. Check that Acktide creates an alert card. - Check device receipt and notification display. These are technical confirmations from the app. - Tap ACK in the system notification. Check the engineer’s name and action on the alert card. - Send a resolved event from the source and check that the alert closes. The console’s built-in test checks phone connectivity. A separate event from your monitoring system also tests the source integration. ## Real on-call conditions - **Screen off:** wait for a new test event, check the sound and ACK without opening the alert card. - **Extended background operation:** repeat after several hours with your normal power-saving settings. - **Network loss:** disconnect the network, send an event, reconnect and check that the stored alert is delivered. - **No ACK:** leave the test unacknowledged and check that the backup recipient is notified after the configured delay. - **Multiple installations:** check that the acknowledgment reaches the correct organization. ## Record your results Record the phone model, firmware, Acktide version, network type, permissions and time of each stage. Record missing sound, missing notifications and missing ACK in the console separately; they are different outcomes. Repeat the test after changing phones or updating the software. ## What has been tested so far Existing tests used an AOSP emulator without Google Services: receipt with the screen off, ACK and recovery of queued delivery. This does not replace testing a physical phone with its manufacturer’s firmware. A public long-duration test matrix across devices and a universal numerical SLA are not available yet. After force-stopping the app, you need to open it again. Without a network connection, delivery waits until reconnection. SMS and calls require a separately configured provider and are disabled by default. [Full feature list and limits →](https://acktide.com/en/limits.html)