Leaderboard

I have an ext4 partition on my SD card and it is recognised by Android. I did partition and format the card using my Linux PC, not from the Pro1, though. Beware that many Android Apps will have problems accessing the ext4 partition. A file manager with root access will work, but many "normal" Apps won't. After some months, I found that disabling SELinux at boot time and re-mounting one of the many cryptic mountpoints of the SD partition allows one to use it almost normally from Android. I described that in this post. Of course one may want to think twice before nuking SELinux as that disa

I have been trying formatting my SD card to ext4 in an earlier LineageOS version, too, but had to give up as hardly any app properly worked with that setup. (I didn't have root back then, though.)

That is not what I see with getevent. Android does repeat keys when they are held down, so it seems your monitor is looking at the event stream at a much higher level than the event stream from the kernel. To fix this behavior, we probably need to be looking in the Android framework rather than the keyboard driver. I agree a GUI for creating custom keymaps would be a helpful feature. After applying CR#315276 and CR#315298, you will be able to install a custom keymap with adb: adb root; adb push my_keymap /data/system/keyboard/keymap As a sample custom keymap file, this is the KE

When I have replaced my screen, I had no touchscreen border problem. I don't know which firmware my display had, but I was using stock OS.

In CR#315342, you may disable the 'Fn-shift' by not assigning any modifier key to KEY_RESERVED. I'm not sure if you mean the separate keydown and keyup events sent by the virtual 'chording' behavior. @tdm carefully designed this so the events are sent in a 'safe' order (i.e. shift down, key down; key up, shift up). The current keyboard driver does not repeat keydown events if you hold the key down. The way I normally check the event stream sent by the driver is with 'adb shell getevent'. The output of getevent has three values, the event type (always 0001 for EV_KEY), the keycode

I have same touchscreen issue. Touch screen does not react as usual, randomly freezes without any reason. (Aug/30 build) https://www.youtube.com/watch?v=48H3H5kwVIE https://www.youtube.com/watch?v=GLLCkAqtvvY