alarms do not work properly, confirmations are not processed

[atomphil]

Description of the issue:

Sometimes alarms from xDrip are not immediately displayed as a call on the watch. When an alarm is displayed on the watch as a call, the confirmation is not passed on to xDrip. Confirmation in xDrip does not stop the watch alarm (see #4).
Currently, every alarm must be confirmed on the clock as well as on the mobile phone.

---

My wearable devices are:

Amazfit Bip S and Bip S lite

My Android version:

LineageOS for microG 18.1 (Android 11)

WatchDrip version:

0.2.1.1 (build date 2023-01-21)

[bigdigital]

Could you please check the following version https://www.dropbox.com/s/onub6e82gkzh789/WatchDrip_v0.2.6.apk?dl=0

[dassystem]

Version 0.2.6 solves this issue for me on mi band 4.

[atomphil]

Could you please check the following version https://www.dropbox.com/s/onub6e82gkzh789/WatchDrip_v0.2.6.apk?dl=0

Basically, it works: With this version, the alarms are displayed again as a call on the watch and can also be confirmed correctly.

However, there is still a small flaw: When there is a new alarm, it is signaled for a fraction of a second as a call, but at the same time the watchface is updated. This interrupts the "call", which cannot be confirmed and the notification "missing alarm" appears shortly afterwards. In the second attempt, the call is not interrupted and can be confirmed as planned -> "alarm snoozed".

A solution would be to execute the alarm signaling only after the successful watchface update.

[atomphil]

If Watchdrip has been running for a while, alarms may not be displayed or they may be displayed but cannot be snoozed.

Force closing the Watchdrip app and reopen it solved the problem. I have no idea how the communication works in detail, but maybe an automatic reinitialisation in the background (maybe every hour) would solve the problem and increase the reliability of the app.