Leaderboard

Also testing kbd-3 here on my QWERTZ. While button mashing I ran into the issue again where the keyboard completely locks up (save for the Alt key) - so I tried to reproduce it... As far as I see, you can trigger this by pressing two keys at exactly the same time. I managed to lock the keyboard up after just a few tries with X+D or W+S with my big enough left thumb.

if you have root, yes /system/usr/keychars/Vendor_181d_Product_5018_Version_0001.kcm if not mistaken is the default (when no keymaps selected) alternatively unzip finqwerty or fx-qwerty (apk files are just zips) and edit one of the keymaps in the res/raw/ directory (or add one and edit the xml file in res/xml/ that that tells where the .kcm files are) then zip it again and use and then use jarsigner to sign it and then zipalign, or first zipalign then apksign (java sdk and android sdk provide these things) to sign and align them so android is happy and you can use that (either search google

@tdm Ok I have flashed boot-stock-kbd-3.img I give a try and will reply what happens. Thanks !

@DieBruine and other keyboard testers, here is a new test image: http://files.nwwn.com/android/pro1/boot-stock-kbd-3.img This switches the irq/event logic to the Lineage code. The remaining differences between this and the official Lineage driver are really just the de-ghosting logic.

Thanks I'll look into that.

If I remember well, if you choose the internal storage option, you see only one drive on the laptop, the combined internal storage.

At my husband's suggestion I chose internal and now I want to undo that.

I doubt very much that FxTec would like to mess with the OS to disable this, as their attitude has been to stay as close to stock Android as possible, only changing stuff where it relates to the Pro1 Hardware (particularly the slider functionality, as hardware keyboards are already supported in stock Android). This is certainly not the only annoying 'feature' in Android, and as far as normal third party apps can not fix them, LineageOS or rooting might be the way to go. Just a thought. Restricting what ever offers the sharing from accessing contacts MIGHT fix this particular issue. I