Jump to content

Sean McCreary

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Sean McCreary

  1. 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
  2. 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
  3. 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
  4. 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 😞
  5. 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
  6. 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.
  7. 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
  8. 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
  9. 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.
  10. 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.
  11. 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.
  12. 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
  13. 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
  14. 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.
  15. 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
  16. By popular demand, lineage-20.0-20230209-UNOFFICIAL-pro1x.zip changes the built-in keyboard type to 'ALPHA'. This makes the Shift, Alt, and AltGr keys 'sticky' in some contexts, where Caps Lock is active for the next keypress. It does not make Ctrl, or Fn sticky, and has some other UI side effects. I also added a change log at the end of README.md in the same folder as the OS images. To cut down on forum spam, I will stop announcing minor changes and only post notices for major bug fixes or similar large changes. EDIT: It's Android's "press twice to lock" feature of ALPHA keyboards t
  17. lineage-20.0-20230208-UNOFFICIAL-pro1x.zip includes the February ASB patches (with date 'February 5, 2023'), and removes the mapping rule for 'Caps Lock + Backspace -> Forward Delete'. After a only few minutes of testing I realized this was a terrible idea, as it made correcting my typos with Caps Lock on much less natural πŸ˜‰
  18. To help you create your own custom keymaps, I updated @Slion's excellent keyboard map for the Pro1-X QWERTY layout and added the key numbers for each of the six modifier keys ('F logo' Fx, Shift, Ctrl, Alt, and right and left "yellow arrow" Fn). Remember that the two Shift keys are actually the same, as are the two Ctrl keys. Unfortunately, you can't map right and left Shift to different key codes, or right and left Ctrl either πŸ™
  19. I have uploaded lineage-20.0-20230207-UNOFFICIAL-pro1x.zip, adding the option to remap the 'Del' key to '\' to improve compatibility with native Android language overlays. While this won't improve agreement between the labels printed on the keys and the characters they generate, it does eliminate the 'missing keys' problem. For example, with the 'English (US)' language overlay enabled, the key labeled '?' will produce ';' and ':' (with Shift) like an ordinary QWERTY keyboard, and the key labeled '/' will produce '/' and '?'. Remapping 'Del' will make that key produce the two missing characters
  20. There are already dedicated buttons for volume on the side of the phone, and there is a slider for screen brightness in the notification shade (swipe down twice). But to answer the generic question, the key remapping feature allows you to reassign any key on the keyboard to whatever Linux key event code you prefer. For example, you could reassign the Del key to generate KEY_MUTE using this custom keymap rule: 21:0071:0071 Remember that the third value in the keymap rules is ignored by the current driver, and it does not support keycode modifier flags either. Right now, the only way to c
  21. I am looking for a few beta testers for an unofficial-UNOFFICIAL variant build of LineageOS 20 for the Pro1-X. While it is compatible with the official beta published on XDA, it includes additional keyboard features, some of which may not be present in the final official-OFFICIAL release of LineageOS. The additional features include: Support for Pro1-X models with QWERTZ, AZERTY, and Scandic keyboards The custom key map feature from the pro1 Reassign the right-hand yellow arrow key to AltGr, from "Settings -> System -> Languages & input -> Physical keyboard ->
  22. Until we are using tdm's driver, there will be undesirable interactions between the F(x)tec's custom keymap and the keyboard language selection in Android. Have you selected a language and layout as directed by the persistent notification to "Configure physical keyboard"? Don't do that. 😜
  23. Believe it or not, this is how we used to create OS distributions back-in-the-day. Fattire even wrote a short poem about it: So Many Zeroes! A Children's Book By Dr. Seuss (a.k.a. fattire) Blue had his V2, all shiny and GNU, and wanted to send it, but stopped to review. "What would this ware weigh, if zipped up today? Should it not be much larger than the SDK?" And yet it was bigger (nearly one-half a gigger!), but Blue still released it with vim and with vigor. "A drive is a drive, at any old size! But a drive is alive when its zero'ed to thrive!" So Blue packered his tracks with a /
  24. sshd is present in /product/bin, with sshd_config in /product/etc/ssh. I don't use this myself, but adb root && adb shell /product/bin/sshd -dddDf /product/etc/ssh/sshd_config doesn't behave the way I would expect. Did this work in 19.1? A quick check of old versions suggests this doesn't work in 19.1 or 18.1 either, so it may have been broken for a couple of years 😞 Since this isn't specific to the beta test you might open a bug report, following the instructions here: https://wiki.lineageos.org/how-to/bugreport
  25. Some of the modifier keys are mapped a little differently from stock, but the driver is still the same one as F(x)tec ships. The most important differences are the 'F logo' key is mapped to META, and the SYM key is mapped to AltGr (ralt). The old behavior of the 'F logo' key (KEY_HOMEPAGE) has consequently moved to 'F logo' + ENTER, but you can now use any of the other keyboard shortcuts built into Android. This list is contextual, and 'F logo' + '/' will bring up the list of shortcuts defined by the current app. FWIW, this is the same mapping as LineageOS uses on the Pro1. Among other mi
  • Create New...

Important Information