MilosKozak
commented
2 years ago v3 uses Android alarm function instead for better compatibility. OK means command was executed. there nothing I can help with I did a small chnge that can help on very busy slow phones https://github.com/nightscout/AndroidAPS/commit/aee036e20074fdb0992ccfd582bf7cd8b1689418
Dev18 Android 9
Expected behavior:
Automation "Going Low - Give 1 Glucotab" is set for warning on an upcoming low. Automation triggers if network location is outside school in a 5Km radius. An alarm is set to trigger. Since AAPS v3, when Automation is successful, the alarm clock starts a 10sec countdown and triggers an alarm which can be snooze like a normal alarm clock. Notification set on AAPS header in main screen and a dot with message is set in graph.
Issue:
Automation "Going Low - Give 1 Glucotab" set for warning on an upcoming low is triggered. Header and graph notification are set but no alarm triggered anymore even though all volume levels (music, alarm and ringtone) are set at around 50%. No alarm clock countdown started. No battery saving mode active.
Reproducing:
Not easy to reproduce as it happens every now and then. Just exported logs (attached) on latest occurrence this morning.
Question:
Is this Android alarm clock triggering the new expected behavior? In v2.8.2 there was a nice pop up with an alarm that triggered with no count down and an option to snooze for different time-frame or even stop the alarm completely.