You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the Android TV v0.3.4 image (the latest stable release), the enter key on my Logitech K400+ wireless keyboard/mouse combo is interpreted as a click. The keyboard is sending key code 28 for enter, according to a key code app I found; I guess the OS is not handling it right.
This seems to be a relatively common problem with that keyboard, and is in theory fixable by tinkering with the key mappings somewhere in /system.
Unfortunately, the image isn't rooted, and the fancy full-disk encryption that Android uses means even though the keys are in there (since the card is the only memory device in use), I can't find a way to mount the SD card on a computer to edit the mapping files.
How do I root the image to update the key mappings? And can this problem for this keyboard be fixed in the base image?
The text was updated successfully, but these errors were encountered:
I'm having similar keyboard issues.
It seems like there's no development for over a year.
This Android release/image seems just like it was a hit and run, one-and-done. Support seems to have left the building 18 months ago.
On the Android TV v0.3.4 image (the latest stable release), the enter key on my Logitech K400+ wireless keyboard/mouse combo is interpreted as a click. The keyboard is sending key code 28 for enter, according to a key code app I found; I guess the OS is not handling it right.
This seems to be a relatively common problem with that keyboard, and is in theory fixable by tinkering with the key mappings somewhere in /system.
Unfortunately, the image isn't rooted, and the fancy full-disk encryption that Android uses means even though the keys are in there (since the card is the only memory device in use), I can't find a way to mount the SD card on a computer to edit the mapping files.
How do I root the image to update the key mappings? And can this problem for this keyboard be fixed in the base image?
The text was updated successfully, but these errors were encountered: