Bug report in beta version: alarms on watch will toggle watch notifications setting to mute

[claresloggett]

I think I've found a bug in the beta version of GlucoDataHandler. Is this the right place to report it? Happy to create an issue (don't have permission by default, I think) and/or help with a fix.

I'm using GlucoDataHandler on a Pixel Watch 4, signed up to beta in the Play Store, and the version of the watch app is 2.5. If relevant, versionName=2.5, versionCode=2201.

The observed behaviour is: if my watch does NOT have "mute ringtones and notifications" toggled on, and a GlucoDataHandler alarm goes off, afterwards my watch will have "mute ringtones and notifications" set. This is the toggle setting you see when you swipe down on the watch face, a bell icon with a line through it. GlucoDataHandler alarms will continue to sound because it sets the sound back on immediately before it alerts and turns it off again afterwards. But other watch notifications will not sound.

The mute behaviour can seem random if you don't realise it's correlated to BGL alerts; you'll just look at your watch sometime during the day and see that it's muted again.

I couldn't at first work out what was toggling my watch to mute, but observing the logs through ADB shows:

    2026-08-11T15:46:41.836457 - set_ringer_mode_internal: com.google.android.apps.wearable.systemui,i:vibrate->normal,e:vibrate->normal
    2026-08-11T18:49:58.551206 - set_ringer_mode_internal: AS.AudioService.onSetStreamVolume,i:normal->vibrate,e:normal->vibrate
    2026-08-11T19:23:05.079163 - set_ringer_mode_internal: AS.AudioService.onSetStreamVolume,i:vibrate->normal,e:vibrate->normal
    2026-08-11T19:23:06.636977 - set_ringer_mode_internal: AS.AudioService.onSetStreamVolume,i:normal->vibrate,e:normal->vibrate
    2026-08-11T19:53:12.925470 - set_ringer_mode_internal: AS.AudioService.onSetStreamVolume,i:vibrate->normal,e:vibrate->normal
    2026-08-11T19:53:14.505907 - set_ringer_mode_internal: AS.AudioService.onSetStreamVolume,i:normal->vibrate,e:normal->vibrate
    2026-08-11T20:23:10.621059 - set_ringer_mode_internal: AS.AudioService.onSetStreamVolume,i:vibrate->normal,e:vibrate->normal
    2026-08-11T20:23:12.176111 - set_ringer_mode_internal: AS.AudioService.onSetStreamVolume,i:normal->vibrate,e:normal->vibrate
    2026-08-11T23:18:35.617330 - set_ringer_mode_internal: com.google.android.apps.wearable.systemui,i:vibrate->normal,e:vibrate->normal

You can see the sound being turned on and off again in quick succession. The first and last interactions, where the sound was turned back on by com.google.android.apps.wearable.systemui, is when I noticed my watch was muted and manually un-muted it.

Correlated with these times, from adb shell dumpsys audio:

08-11 18:49:56:984 setStreamVolume(stream:STREAM_RING index:1 flags:0x0 oldIndex:1) from de.michelinside.glucodatahandler
08-11 18:49:56:986 setRingerMode internal to 2, caller=AS.AudioService.onSetStreamVolume, delegateModified=2
08-11 18:49:58:526 setStreamVolume(stream:STREAM_RING index:0 flags:0x0 oldIndex:1) from de.michelinside.glucodatahandler
08-11 18:49:58:551 setRingerMode internal to 1, caller=AS.AudioService.onSetStreamVolume, delegateModified=1
08-11 18:49:58:572 sending VOLUME_CHANGED stream:STREAM_RING index:0 (was:1) aliased streams: STREAM_DTMF:0 STREAM_SYSTEM_ENFORCED:0 STREAM_SYSTEM:0
08-11 19:23:04:932 setStreamVolume(stream:STREAM_RING index:1 flags:0x0 oldIndex:0) from de.michelinside.glucodatahandler
08-11 19:23:05:064 sending VOLUME_CHANGED stream:STREAM_RING index:1 (was:0) aliased streams: STREAM_DTMF:2 STREAM_SYSTEM:1
08-11 19:23:05:079 setRingerMode internal to 2, caller=AS.AudioService.onSetStreamVolume, delegateModified=2
08-11 19:23:06:610 setStreamVolume(stream:STREAM_RING index:0 flags:0x0 oldIndex:1) from de.michelinside.glucodatahandler
08-11 19:23:06:637 setRingerMode internal to 1, caller=AS.AudioService.onSetStreamVolume, delegateModified=1
08-11 19:23:06:655 sending VOLUME_CHANGED stream:STREAM_RING index:0 (was:1) aliased streams: STREAM_DTMF:0 STREAM_SYSTEM_ENFORCED:0 STREAM_SYSTEM:0
08-11 19:53:12:880 setStreamVolume(stream:STREAM_RING index:1 flags:0x0 oldIndex:0) from de.michelinside.glucodatahandler
08-11 19:53:12:905 sending VOLUME_CHANGED stream:STREAM_RING index:1 (was:0) aliased streams: STREAM_DTMF:2 STREAM_SYSTEM:1
08-11 19:53:12:925 setRingerMode internal to 2, caller=AS.AudioService.onSetStreamVolume, delegateModified=2
08-11 19:53:14:464 setStreamVolume(stream:STREAM_RING index:0 flags:0x0 oldIndex:1) from de.michelinside.glucodatahandler
08-11 19:53:14:506 setRingerMode internal to 1, caller=AS.AudioService.onSetStreamVolume, delegateModified=1
08-11 19:53:14:524 sending VOLUME_CHANGED stream:STREAM_RING index:0 (was:1) aliased streams: STREAM_DTMF:0 STREAM_SYSTEM_ENFORCED:0 STREAM_SYSTEM:0
08-11 20:23:10:584 setStreamVolume(stream:STREAM_RING index:1 flags:0x0 oldIndex:0) from de.michelinside.glucodatahandler
08-11 20:23:10:606 sending VOLUME_CHANGED stream:STREAM_RING index:1 (was:0) aliased streams: STREAM_DTMF:2 STREAM_SYSTEM:1
08-11 20:23:10:621 setRingerMode internal to 2, caller=AS.AudioService.onSetStreamVolume, delegateModified=2
08-11 20:23:12:152 setStreamVolume(stream:STREAM_RING index:0 flags:0x0 oldIndex:1) from de.michelinside.glucodatahandler
08-11 20:23:12:176 setRingerMode internal to 1, caller=AS.AudioService.onSetStreamVolume, delegateModified=1
08-11 20:23:12:192 sending VOLUME_CHANGED stream:STREAM_RING index:0 (was:1) aliased streams: STREAM_DTMF:0 STREAM_SYSTEM_ENFORCED:0 STREAM_SYSTEM:0

I thought what was happening is that GlucoDataHandler turns off any mute setting right before it alarms, then turns it back on again afterwards, and that the problem is it does this even if the mute setting was originally off. But looking at the logs I'm not sure.

Edit: actually, I don't fully understand the signals in the audio logs, but I think that makes sense - the notification logs show a mute event with no prior un-mute at 18:49. But the audio logs show both the un-mute and mute signals every time, i.e. two setRingerMode events around 18:49. So I assume what's happening is that GlucoDataHandler sends an un-mute signal, and the audio logs record it, but the notification logs don't record anything because the watch was already not muted? And then it sends the mute signal.

[pachi81]

Hi,
can you also enable logging in GDH on watch!? Even Debug-Logging.

But I think, I know the problem, because there is a similar issue on newer Android mobile version. The system does not report the current state correctly, so GDH retrieve the state, that everything is muted. After it forces the sounds it resets the settings back to state Android reported before...

But I also think, the force option is not needed, as GDH uses alarm settings as default, which can have sound, even watch system sound settings are muted. So the best solution is to disable the force alarm sound settings in GDH on watch.

Best regards,
Michael

[claresloggett]

Ok, I'll try turning on debug logs and post them here! Where will the debug logs appear, i.e. how should I retrieve them with adb?

For the force alarm sound settings, I'm not sure I understand, do you mean under the GDH Alarms menu, it might work to turn off the "Alarm Notification" setting?

[pachi81]

I made my app for normal people :-D so no adb needed. Just save the logs in phone version from watch.
You can also use contact option to send me the logs or upload them here.

For the force alarm sound settings, I'm not sure I understand, do you mean under the GDH Alarms menu, it might work to turn off the "Alarm Notification" setting?

This settings you can find under Advanced in Alarm settings menu. There is an option to force alarm sound.

[claresloggett]

Ah right. "Force alarm sound" is already turned off, I didn't have it on originally (unless turning Alarm Notifications off and back on again could have disabled it?)

I'll do some debug logs and send them after I get an alert

[pachi81]

You can also trigger an alert your self, just open an alert an press the test button.

[claresloggett]

Sorry for the delay @pachi81 ! Here are debug logs. Basically I started the logging, played a test alarm, and then saved the logs, so they're very short. The ringer was on (mute setting off) before I started. Let me know if you want me to try anything different!

GDH_WEAR_APP_20260816_172523.txt

Edit: I think this test did NOT result in my mute setting being disabled (i.e. the bug behaviour) and I have no idea why... so these logs might not be useful!

[pachi81]

Hi, sorry for late response, but I'm in holidays and have only a few time.
I would need the logs from the bug to analyse. So would be great, if you can reproduce it.

Michael

[claresloggett]

Sorry again for delays, think I finally have a log exhibiting the behaviour. This is a test of the High alert, which I think triggered it.

GDH_WEAR_APP_20260822_154508.txt

[pachi81]

I have checked to logs, GDH does not change the ringer-mode. Only sets the sound level to 0 when the alarm starts and back to 1, when the alarm is finished.
The ringer mode is detected as vibration only. So no sound should appear.

What is the exact problem!? Please try to set the sound level to -1 for the alarm.