Don't use "wake on tap or motion" for T-Echo touch button #3745
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Back in 2022, @caveman99 mentioned an issue where transmitting would trigger a long-press of the touch button.
The "wake on tap or motion" setting was used recently as a "bail-out" option for any users experiencing this issue.
I am not aware of any reports of this issue recently, so it seems safe to enable the touch button for all T-Echo devices, removing the association with the "wake on tap or motion" setting.
There is currently a mystery issue, where this setting does not always persist. Removing the use of this setting with the T-Echo avoids the issue for now.