Sean McCreary

For a QWERTY Pro1x using the "F(x)tec QWERTY" keyboard layout (the default), you can type a semicolon by pressing both the 'L' key and one of the diagonal yellow arrow keys (Fn) at the same time. As Hook mentioned, this changes if you use any other keyboard layout, such as "English (US), International style" or "English (UK)". The UK Sterling character (Unicode code point U+00A3 = '£') is available in the "English (UK)" keyboard layout via the key combination Shift + 3. Unfortunately this keyboard layout does not include the all of the key combinations F(x)tec printed in yellow on the key

Charging-only mode is part of Android, so the phone must be able to boot the high-level OS to charge. When you connect a power source, it will always start the Android boot process. If the off-mode-charge flag is set, it will start the charger program instead of the full Android UI. Yep, you triggered the "battery protection bug". The problem is in the closed-source firmware, and relates to the PMC configuration. LineageOS doesn't have licenses for this source code, so we need F(x)tec to fix it. The only way to avoid it is to periodically charge your Pro1 X, and once a month should be

You really only need to flash enough to get into LineageOS recovery, as the full LineageOS image will install everything it needs. If the Pro1 X boots into LineageOS, then you can be confident you didn't skip anything important 😉 Also, 'super_empty.img' isn't needed for the Pro1 X, as it ships with dynamic partitioning. Some devices need to be reconfigured for dynamic partitioning before they can run LineageOS, and that file is used to prepare the device, e.g. https://wiki.lineageos.org/devices/grus/install#installing-a-custom-recovery-using-fastboot

Unfortunately, you must factory reset before installing the official build of LineageOS. The unofficial builds are signed with different keys from the official ones, and we don't have a simple way to swap signing keys in Android 13 😞

It does this because F(x)tec makes the key generate KEY_HOMEPAGE. The fix is to change this in the kernel source, e.g. https://github.com/LineageOS/android_kernel_fxtec_sm6115/commit/41b535243dce9e057069adda494cbbaf8c720f35

FYI, some Linux distributions (like Debian Bullseye) name the prerequisite package "python3-protobuf", and you may need to set "PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=python" to get the script to work.

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

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

Yes, this should work in LineageOS 20. Please let me know if it doesn't, and I will fix it 🙂 Download this file: https://review.lineageos.org/c/LineageOS/android_device_fxtec_pro1/+/348111/3/devicesettings/QWERTZ_keymap There is also a full keymap for Pro1 QWERTY in the same CR.

As another example, I can't build crosshatch from scratch without OOM errors, even with 32 GB RAM. The problem is that the build system doesn't avoid scheduling too many memory-hungry jobs in parallel, and LTO of the kernel takes ~40 min to complete on my build system. LTO uses 6GB of RAM, and will still be running when all of the Java and dex2oat jobs want > 2GB each. Some people swap to zRAM as a workaround, but sometimes the build will complete if you wait for the partial build to fail, and then immediately run 'brunch' a second time.

LineageOS is a group project, and support for the Pro1-X wouldn't have been possible without Georg Veichtlbauer and@npjohnson's efforts. And of course we built upon @tdm's work on the Pro1 as well.

The general idea is for Settings to set a global value, and and a modified KeyCharacterMap.java to check that value instead of depending on the .kcm files. The negative reviews are about the various possible ways to do this: a setting, a system property, etc. An instance variable isn't usable for this as each app gets a different instance of the KeyCharacterMap object, so there's no way to use a method in the class itself and have the change take effect in all instances. The normal way to do this is to add a new setting in LineageOS' SDK, but unfortunately the SDK can't be linked against the c

lineage-20.0-20230212-UNOFFICIAL-pro1x.zip disables the "press twice to lock" feature. You can still press just one key at a time, but you'll need to press Shift/Alt/AltGr before every key you want to modify. Note that Caps Lock is available if you want more than one capital letter in a row. I hope this small change is a compromise everyone can accept. Early feedback on my patch to make the keyboard type configurable from Settings has been negative, suggesting it would be unlikely to appear in official builds of LineageOS. If you are building your own OS images and are interested in th

LineageOS 20 is stable and usable on the Pro1, but I don't use Magisk. Please report any bugs you might find by following the instructions on the LineageOS Wiki. FWIW, I never liked Android 11 much either.

This feature was added to official builds for the pro1 in Nov 2021 with this change: https://github.com/LineageOS/android_kernel_fxtec_msm8998/commit/a340af4b4e360d11cd53d7ad199950faac344b78 It supports remapping the yellow arrow keys to any Linux key event code, but doing so prevents them from triggering the alternate keymap in the kernel. You can remap them both to AltGr and just ignore the kernel 'keymap shift' feature entirely. In fact, I used this feature to add the layout mod that makes the left yellow arrow key AltGr without requiring a custom keymap: https://github.com/Linea