Fixes for Raspberry Os Bookworm: Refactor gpio-buttons.py for debounce and clarity / re-enable I2C to active display #14
+149
−119
Conversation
This file contains hidden or 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
Updated GPIO button script for OLED Phoniebox to include software debounce and improved button handling.
Add command to enable I2C interface via raspi-config.
jonaskor
changed the title
Updated README to reflect changes in project details, installation instructions, and troubleshooting steps for the oled_phoniebox fork.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Updated GPIO button script for OLED Phoniebox to include software debounce and improved button handling. Also re-enabling I2C (display disabled if not active). Code changes suggested by copilot, tested by me.
Root cause: Bookworm’s default gpio backend produces very-rapid spurious edges for your hardware that were interpreted as many presses; Bullseye used a different backend and did not show this behavior.
Fix applied to gpio-buttons.py (on-device): added a backend-agnostic software debounce wrapper for when_pressed handlers plus a small bounce_time — this prevents the sub-millisecond PRESSED/RELEASED bursts from firing multiple actions while leaving when_held behavior intact. After that change the service starts normally and the duplicate-presses are gone on Bookworm device.
Display works as usual after I2C is reenabled.