Bug #949
closed
Pi Zero doesn't work with keyboards using elecrow 5" HDMI display
100%
Description
This is probably a keyboard handling issue in launcher.
This needs to work to complete testing of Pi Zero/Zero W on Kiosk and AutoKiosk.
Related issues
Updated by Hammel about 1 year ago
- Blocks Testing #893: System Integration Tests for Harkonnen Release added
Updated by Hammel about 1 year ago
- Blocks Testing #894: Generate release candidates builds: Harkonnen added
Updated by Hammel about 1 year ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
This is probably because the display is identified as a touchscreen (with updates to config.txt applied) so keyboards no longer work.
Removing the touschscreen overlay from the config and checking the launcher log it seems that the arrow keys on the mini keyboard (SINO WEALTH USB KEYBOARD) are not recognized.
The easy way to handle this is to map normal alphabetic keys to left/right and up/down so if the arrow keys don't work there is always a fallback.
Updated by Hammel about 1 year ago
The code for this is in the launcher, in the RM949-keyboard branch. I started this to help debug Pi Zero Kiosk problems but those are being pushed out to the PiBox 3.0 release.
It would probably be beneficial to add this to libpibox - create a common cli interface for things that all apps share, like use of keyboards or touchscreens, etc. This should be integrated into all app specific cli parsers using an app that would look something like this.
piboxCli(&cliflags)
So that the cli flags can be updated first, before the app-specific updates are handled. All apps would need to reserve some bit field span for use by the library, however.
Updated by Hammel about 1 year ago
- Priority changed from Immediate to Urgent
- Target version changed from 2.0 - Harkonnen to 3.0 - Corrino
- Severity changed from 01 - Critical to 02 - High
Updated by Hammel about 1 year ago
- % Done changed from 10 to 70
The much simpler solution to this is to just have the launcher allow keyboards all the time. There really isn't a reason to not allow a keyboard (at least that I can think of). If a keyboard is present then it works along with the touchscreen - they don't interfere with each other. Disconnecting the keyboard doesn't affect the touchscreen.
I've implemented this change to launcher and tested on a pistore system. Works fine.
Updated by Hammel about 1 year ago
- Status changed from In Progress to Closed
Code committed and pushed.
Closing issue.