Gordon Williams

Thanks for the log! Ok, so it definitely looks like `KDE Connect` is popping up notifications with the wrong video in, and then Gadgetbridge is parsing those and only showing...

Yes, you could try overwriting those functions and see what happens - overwriting setWatch might be enough, and maybe it's something you could even provide as an app. But personally...

Now you've bought it up I'm more aware of how long I end up pressing the button for before releasing :) Try adding: ```JS { let _setWatch = setWatch; global.setWatch...

> the reference erroneously [says default is "both"](https://www.espruino.com/ReferenceBANGLEJS2#l__global_setWatch) Actually it does say: > see below for more information and then > edge:'rising'(default for built-in buttons)/'falling'/'both'(default for pins), but I'll delete...

> Sorry for not reading thoroughly.. Well, thanks for pointing out the issue. Most people (including me) only glance at the docs anyway, so we don't want the summary up...

> I guess some app may add additional button watches after a setUI call which may be problematic. True... In a way it'd be good to know those so they...

I think in that case, doesn't the button end up calling the function with `ud==0`? We could extend setUI so that even if mode!=custom, button/touch/swipe/etc are still honoured?

If you do: ``` ud => { if (ud) Bangle.musicControl(ud>0 ? "volumedown" : "volumeup"); else load(); } ``` I think that has mostly the same effect looking at setUI -...

Sounds like a good plan, yes

> Perhaps we could have it work for buttons too? The problem is that the whole point is to do the action as soon as possible, so the action is...