Display unlocks frequently without interaction #6527
Replies: 1 comment
-
Posted at 2023-11-06 by @gfwilliams Do you have I know someone did report an issue that for some reason having the HRM on caused taps to register on the accelerometer and I still have to look into that, but if you just have 'wake on BTN' on then you should be fine Posted at 2023-11-06 by HughB I have noticed this today. I only have wake on touch on. Posted at 2023-11-06 by user147320 You mean the option in the LCD menu next to wake on BTN, right? No, I do not have wake on touch enabled. I also noticed that it wakes up a few seconds after HR Measurement started. Posted at 2023-11-06 by HughB I see this behaviour as well with the HRM to 3 mins. Posted at 2023-11-07 by d3nd3-o0 I do not. How to recreate? Edit: I just experienced it, I set only I made further testing and requires :
some timestamps in ms between each wake, with watch on desk face down to keep hr light on:
It seems calling
My readings are all Posted at 2023-11-07 by @gfwilliams
it's two down from It's a bit confusing but it's documented in the readme there - the touchscreen draws a bunch of power when on so we do wake on touch by detecting a 'tap' from the accelerometer. Just touching won't wake it, you have to tap it such that the watch actually moves. So @hughb and @d3nd3-o0 it's what I said in your case with the spurious tap events, original report at https://forum.espruino.com/conversations/390041/#comment17120157 And yes turning the HRM on resets the hrmWearDetect/hrmPushEnv values @d3nd3-o0 but I don't think that's related to @user147320's issue. If you want to see how to use env values check out https://banglejs.com/apps/?id=flashcount @user147320 but you're sure that Posted at 2023-11-07 by @gfwilliams I just looked into this more, and I believe unfortunately it's related to power fluctuations from the heart rate sensor. The HRM isn't being accessed at the time the accelerometer errors occur so it's not an I2C issue, but if I keep the HRM running but turn off the green LED part of it, the spurious readings stop. Or if you try:
and put the watch face up on the desk, then slowly move your finger near (without touching) so it thinks you're wearing it and turns on the LEDs then you can see the difference in accelerometer readings really goes up drastically, and down when you move your finger away and the LEDs turn off. It's not a great situation but there's not much we can really do to fix the accuracy (except maybe put the accelerometer into a higher power mode that does more averaging when the HRM is on). But, I just bumped the threshold for tap detection up a tiny bit (0x1A to 0x25) and that's had a massive effect on the misreported taps, without noticeably causing problems detecting any normal taps - so if you try the current 'cutting edge' build I think you'll find its a lot better Anyone who wants to experiment with different values can do so with:
Posted at 2023-11-07 by user147320
Unfortunaly yes, only wake on BTN is enabled :( Posted at 2023-11-07 by @thyttan How are you trying to update? Phone or computer? Official app loader, development app loader or personal app loader fork? Posted at 2023-11-07 by d3nd3-o0 Bangle 2 and the accel wakeOnTouch has been around for a while, yet we didn't have those issues around?. Has the hr usage always been having this influence on other components or is it related to the third-party algorithm? Whats the new variable here to cause it? @gfwilliams I did forget that it uses accel, was assuming it has another touch sensor similar to bangle 1. Is there an older firmware version of b2 that does Posted at 2023-11-07 by d3nd3-o0 @user147320 it'd do us a favour if you ran Posted at 2023-11-07 by user147320 Sure thing, good idea!
I used the official App-Loader and Android (Gadgetbridge and Chrome). With Version 2v19.53 it still wakes up randomly, although I am not sure of the connection with HR-Measurement anymore. I need more time to observe this again after the update to tell. Posted at 2023-11-07 by d3nd3-o0 EDIT: This response is based on false evidence. Results are that v19 has anomalies which are not present in v18. No where near as high. Still, I am unable to explain OP's condition or find a test-case that screen turn on without Posted at 2023-11-08 by @gfwilliams @user147320 thanks for that dump! That's an odd one - as you say it looks like the wake sources are set up fine. Maybe you could try If you're connected with the IDE you could paste I notice you do have
No, they've always had it as far as I know. I'm pretty sure Wake on Touch (tap) was added reasonably recently which is why this got noticed - before, we were never forwarding these events.
More info? I really don't think this is a recent issue. Posted at 2023-11-08 by user147320
I wont have time for this today but I will try this soon. With 2v19.53 it got definitely better. With Recorder running it wakes up about every other minute and with only the Health App I so far did not notice it waking up.
I installed it because Gadgetbridge kept asking me to do so (no idea why), but I already unistalled it since. Posted at 2023-11-08 by @gfwilliams
Thanks! I just realised Gadgetbridge is still mentioning Gadgetbridge, not Android integration. I'll fix that. However the fact that it's complaining about this even if you have the Posted at 2023-11-08 by d3nd3-o0 EDIT: Ignore this post. False. I mean the above, in the context of using your setHRMPower script with accel events. I also have to test this on 2v18 too. Posted at 2023-11-08 by @thyttan Just to chime in, I've also sporadically had the screen turn on seemingly in correlation to the watch capturing hrm data. For me, I'm pretty sure most of these times I have not had any other of the standard ways of unlocking on than via the hardware button. However, I do use I've also seen this across many stable firmware versions. Posted at 2023-11-08 by ccchan
Posted at 2023-11-09 by @gfwilliams
That'd be it then... Posted at 2023-11-09 by user147320
I too use that widget, but I do not have the setting turned on, tapping the corner did not wake up the screen.
I tried it and it did not fix it. Still good to know that this exists!
Even if I actively wake it up with the button this command does not tell me about it. And btw a huge thanks for the great support! Posted at 2023-11-10 by @gfwilliams
Ahh, sorry - my mistake. Right now it's a bit hard to see why it woke - I guess I could change the firmware so that it reported why it woke up, and that might allow us to pin this down more? Posted at 2023-11-10 by user147320 That might not be necessary. So far I did not observe any more wake ups. I would observe it for a few more days before calling this fixed, but there's hope that's it.
Thanks for the hint, I would never have thought about blaming this widget. Posted at 2023-11-10 by ccchan
negative, no. thanks Posted at 2023-12-20 by d3nd3-o0 I wanna just clear up that my previous statements were based on false evidence. The scripts I used to collect the data were causing the bias. I didn't have time to double check. So paranoia say bye bye. But today, I did double check and there was no differences across firmware v18 and v19. So all guchi!. |
Beta Was this translation helpful? Give feedback.
-
Posted at 2023-11-05 by user147320
I setup my Bangle.js 2 to only unlock when the button is pressed (not for turning my arm or touching the display or anything).
Despite that the display keeps turning on (and unlocking) regularly (multiple times a minute to every few minutes).
I suspect that it turns on every time it tries to read my heartrate, since if I ask health to measure every 3 minutes it occurs every 3 minutes and if i use recorder to measure more often it turns on multiple times a minute. But I am not certain, if this is really the reason.
It is pretty annoying.
Is this expected behaviour? Did I mess up some setting (I looked everywhere but could not find anything related)? Any ideas would be appreciated. I love the locked, unlit display and would like to use it more often.
Firmware: 2v19
Apps installed:
openstmap (0.25), widid (0.03), antonclk (0.11), wid_a_battery_widget (0.04), bthrm (0.17), widlock (0.08), agpsdata (0.06), widmessages (0.05), messageicons (0.05), widbt (0.09), lightswitch (0.09), android (0.32), iconlaunch (0.19), messagegui (0.74), notify (0.13), messages (0.62), boot (0.59), antonclkplus (0.10), locale (0.17), gbridge (0.27), hrm (0.11), health (0.27), recorder (0.32), setting (0.65)
Beta Was this translation helpful? Give feedback.
All reactions