Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Display turns on every 30 min when Shake Wake is active #1425

Open
1 task done
efelon opened this issue Nov 7, 2022 · 5 comments
Open
1 task done

Display turns on every 30 min when Shake Wake is active #1425

efelon opened this issue Nov 7, 2022 · 5 comments
Labels
bug Something isn't working

Comments

@efelon
Copy link

efelon commented Nov 7, 2022

Verification

  • I searched for similar bug reports and found none was relevant.

What happened?

While Shake Wake is active, the display turns on automatically every full and half hour.

What should happen instead?

I expect that the display stays off unless there was a shake.

Reproduction steps

  • Turn on Shake Wake
  • Observe the display every 30 minutes to the full and half hour
    (you may place the watch on the table to prevent accidental shake activation)

More details?

  • Chimes are off.
  • Other Wake Up options seam not to influence this behaviour.

Version

v1.10.0 and v1.11.0

Companion app

Gadgetbridge

@efelon efelon added the bug Something isn't working label Nov 7, 2022
@JF002
Copy link
Collaborator

JF002 commented Nov 19, 2022

Could you try to enable and then disable the Chimes (enter the Chimes settings, enable it, exit the settings to save it and then disable it) and check if it fixes the issue?

@efelon
Copy link
Author

efelon commented Nov 20, 2022

Sorry, no it does not solve it. My previous test was while the watch was charging (where it does not turn on every 30 minuets). As soon as I put it back on my wrist the problem resumed. And I repeated your requested procedure several times now, without success.

@AtomToast
Copy link

I have the same issue. It always turns on at full and 30 past

@segaretroboy
Copy link

I have been having this issue as well, only enabled wake action besides the button is to shake wake and the screen turns on every 30 minutes regardless of the chime setting.

@mark9064
Copy link
Member

This is probably influenced by motion being updated on every systemtask loop, meaning that when the onnewhour/halfhour events arrive, motion is calculated twice in quick succession causing the acceleration value to be calculated way higher than it should be. This issue will have been partially alleviated by #2041 but I will be opening constant frequency motion updates as a PR soon :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants