Oh right, that's the reason this stuff is built into all apps: it's the only way to know if it buzzes for an alarm or only for a notification.
We might get away with something like Bangle.forceBuzz() for alarm apps? Someone might want to definitely disable all vibration though...
Suppressing setLCDPower from apps might work, because turning on for interaction is done by the firmware. But then you end up needing a "disable setLCDPower" setting to schedule it :-(
I don't use an alarm app, and if a notification arrives I twist my watch to look at it anyway, so just scheduling vibration = on/off and removing setLCDPower from notifications would be fine with me...
(The schedule app also works fine for me: "Off" at 8:30 and "Alarms" at 21:30.)
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Oh right, that's the reason this stuff is built into all apps: it's the only way to know if it buzzes for an alarm or only for a notification.
We might get away with something like
Bangle.forceBuzz()
for alarm apps? Someone might want to definitely disable all vibration though...Suppressing
setLCDPower
from apps might work, because turning on for interaction is done by the firmware. But then you end up needing a "disable setLCDPower" setting to schedule it :-(I don't use an alarm app, and if a notification arrives I twist my watch to look at it anyway, so just scheduling
vibration = on/off
and removingsetLCDPower
from notifications would be fine with me...(The schedule app also works fine for me: "Off" at 8:30 and "Alarms" at 21:30.)