Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Given the UX is resolution locked, framebuffer size should be set in /boot/config.txt
See original GitHub issueAfter unsuccessfully attempting to modify the scripts to handle different screen resolutions, I had success with the following settings which match the hard-coded values in your UX. Without these settings, if touch UI is enabled, a significant portion of the screen to the right and bottom is left black. Without touch UI, IIRC it just added extra rows and columns leaving the text very small but centered.
/boot/config.txt:
framebuffer_width=480
framebuffer_height=320
This resolves the issue completely.
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
OK … so I will add this to the
blitz.display.shforhdmi&lcdmode for the next v1.7.2 rc.On second thought, I think this just changes the framebuffer size, not the resolution sent to the screen. If that’s so, I’m not sure why it would cause any issues with your monitor. You can double-check the monitor is getting the correct settings in raspi-config.
I did have an issue with the screen going black in this configuration with touch UI enabled, but it started working over a couple reboots. Without touch UI enabled, it always displayed correctly so you may try toggling that as well.