-
Notifications
You must be signed in to change notification settings - Fork 964
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
[Bug]: "Wake On Tap Or Motion" Still Not Honored #5579
Labels
bug
Something isn't working
Comments
fifieldt
added a commit
to fifieldt/meshtastic-firmware
that referenced
this issue
Dec 20, 2024
As reported by @Mason10198, the WisMesh Pocket was always waking on accelerometer motion. This change gates the LIS3DH sensor's call to wakeScreen based on config.display.wake_on_tap_or_motion . fixes meshtastic#5579
fifieldt
added a commit
to fifieldt/meshtastic-firmware
that referenced
this issue
Dec 20, 2024
As reported by @Mason10198, the WisMesh Pocket was always waking on accelerometer motion. This change gates the LIS3DH sensor's call to wakeScreen based on config.display.wake_on_tap_or_motion . fixes meshtastic#5579
fifieldt
added a commit
to fifieldt/meshtastic-firmware
that referenced
this issue
Dec 21, 2024
As reported by @Mason10198, the WisMesh Pocket was always waking on accelerometer motion. This change gates the LIS3DH sensor's call to wakeScreen based on config.display.wake_on_tap_or_motion . fixes meshtastic#5579
fifieldt
added a commit
to fifieldt/meshtastic-firmware
that referenced
this issue
Dec 21, 2024
As reported by @Mason10198, the WisMesh Pocket was always waking on accelerometer motion. This change gates the LIS3DH sensor's call to wakeScreen based on config.display.wake_on_tap_or_motion . fixes meshtastic#5579
fifieldt
added a commit
to fifieldt/meshtastic-firmware
that referenced
this issue
Dec 21, 2024
As reported by @Mason10198, the WisMesh Pocket was always waking on accelerometer motion. This change gates the LIS3DH sensor's call to wakeScreen based on config.display.wake_on_tap_or_motion . fixes meshtastic#5579
fifieldt
added a commit
to fifieldt/meshtastic-firmware
that referenced
this issue
Dec 21, 2024
As reported by @Mason10198, the WisMesh Pocket was always waking on accelerometer motion. This change gates the LIS3DH sensor's call to wakeScreen based on config.display.wake_on_tap_or_motion . fixes meshtastic#5579
fifieldt
added a commit
to fifieldt/meshtastic-firmware
that referenced
this issue
Dec 23, 2024
As reported by @Mason10198, the WisMesh Pocket was always waking on accelerometer motion. This change gates the LIS3DH sensor's call to wakeScreen based on config.display.wake_on_tap_or_motion . fixes meshtastic#5579
fifieldt
added a commit
that referenced
this issue
Dec 23, 2024
As reported by @Mason10198, the WisMesh Pocket was always waking on accelerometer motion. This change gates the LIS3DH sensor's call to wakeScreen based on config.display.wake_on_tap_or_motion . fixes #5579
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Category
Other
Hardware
Rak4631
Firmware Version
v2.5.15.79da236
Description
I see that this was brought up in #4384, merged in #4642, and closed - but the "Wake On Tap Or Motion" still appears to have no effect on the WisMesh Pocket (RAK4631). I have tried toggling the setting on/off via the Android and Web clients, but the display continues to always wake on accelerometer motion.
Unlike #4384, the setting toggle does persist (appears to stay off) across reboots in the Android/Web client, but the WisMesh still ignores the setting.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: