Leaderboard

This is where that second hexadecimal number in each keymap rule is useful. It allows you to specify an alternate Linux event code plus any combination of Shift, Alt, AltGr, Ctrl, or Fn. F(x)tec moved the yellow labels around in ways that can't be matched by only rearranging the keys, and tdm gave us another layer in the kernel to fix this 🙂 Say the yellow label was 'Å', but the .kcm file defined that as 'AltGr + some other key'. You would define the last number in the keymap rule to be that other key, but with the 'AltGr' flag set as well, e.g. key_code | KF_ALTGR == key_code | 0x1000

Not asking for a refund here (well, I backed via IGG, so not eligible for refund, but I would continue to wait even if I could). I believe I will get my Pro1x (actually, I will end up with two), just no idea when. I am lucky enough to have my Pro 1. If I don't, it's money I spent 2 years ago. It's been "written off" already.

There is another layer, the .kcm file. For Scandic models of the Pro1-X I made this key character map: https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1x/+/348323/5/AsantiKeypad/res/raw/keyboard_layout_fxtec_scandic.kcm The Unicode code point for Å is U+00C5, which is mapped from the key code for "LEFT_BRACKET" (decimal 26) here. I used Android's Swedish language overlay as the basis for the F(x)tec Scandic default .kcm file, and I suggest you choose the language overlay closest to your own and set up your kernel keymap to match. This unfortunately excessively com

Basically you should think about keyboard scan codes. So every keys on a real keyboard generate a code which represents the physical key pressed. Then you have keyboard layouts, which assigns physical keypresses (scan codes) as an actual letter. Looking from the other end: In the past, there was an US keyboard layout. Later, national keyboard layouts are also appeared which were practically the very same keyboard what US layout was, simply the prints of actual keys were different. So OS should know which layout was printed on keyboard, then it can generate the same keys wh

Right now, issues related to mobile network connectivity are reported from practically all over the world (I heard of: USA, Europe, Asia, Australia), though not by all users. There is no really clear picture yet, but, as F(x)tec acknowledged in their latest update, there may be a correlation with specific LTE bands and there may be a firmware fix at some point ...

OTA for the same was also smooth. This time, I stayed rooted. My experience is that, most of the time, OTA updates don't disturb root, but once in a while I don't have root afterwards. Don't know why, but no big deal. Easily fixed when it does happen.

(lineage-20.0-20230220-nightly-pro1-signed.zip on February 5 security patch installed smoothly using adb sideload and MindTheGapps-13.0.0-arm64-20221025_100653)

It is not a stretch to say that the smartphone market is a mess! and the Pro 1x simply does not fit in

Unbelievable, this actually worked! And I did a system upgrade (LOS 18->19) as well, and that worked on top! This was my first time a dirty flash worked – with device encryption. This is what I flashed from the stock rom: fastboot flash boot_a boot.img fastboot flash boot_b boot.img fastboot flash dtbo_a dtbo.img fastboot flash dtbo_b dtbo.img fastboot flash system_a system.img fastboot flash system_b system.img fastboot flash vendor_a vendor.img fastboot flash vendor_b vendor.img fastboot flash vbmeta_a vbmeta.img fastboot flash vbmeta_b vbmeta.img rem fastboot flash userdata

I found an easy way to fix this from any ROM, without having to wipe userdata. tl;dr: Edit: Make backups. It shouldn't be necessary, but you never know! Flash the 2020-08-25 stock ROM, but skip flashing/wiping userdata. More info here. Let it attempt to boot (for a couple of minutes). It (very probably) won't ever get through it, because the userdata partition wasn't wiped. This doesn't matter, though. It does flash the touchscreen firmware, which fixes the unresponsive screen edges. Edit: I did not time it, but I think I let it sit at the boot logo for 2-3