Leaderboard

This is now official. Builds are weekly, currently scheduled for Wednesdays. Install instructions are exactly as LineageOS 18.1. Download site: https://dwnld.aicp-rom.com/ Enjoy!

I seem to have successfully flashed AICP 16, but I'll update once I have the phone fully set up again which will take me a while with other things I have to do. It booted up and is running very smoothly. I used the Lineage 18 recovery and started by wiping data/factory resetting, assuming a dirty flash wasn't a good idea. I did adb sideload and then, as always, rebooted to recovery. When I did that, I got a few mounting errors (which I didn't write down, sorry) which I chose to ignore. Lol. I flashed Magisk and open gapps nano and booted the system. Usual longer bootup for first time. E

@tliebeckWelcome on the forums. I think the displayed layouts on the IGG page are still what they were when first published. The community has already heavily criticized them in multiple places on those forums. My take on this, is that it should look like that: See also: The last thing we want is removing modifiers, also having printable characters on the bottom row of keys is not a good idea IMHO.

You should be able to use pretty much any recovery to install it.

Right now you will need to use 'adb' to install the custom keymap, and there isn't any app to help you create the map 😕 @Slion made this nifty QWERTY keyboard image with each key labelled with the 'key number' in yellow: The manual process is to choose which key you want to remap, and to look up the keycode you want it to generate in this list: https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h You will need to convert the keycodes from decimal to hexadecimal if they don't begin with '0x'. The custom keymap is a file with lines contain

Just a final note. Have most everything set up again and I am loving being back on AICP-- my favorite tweak being that it uses Slim Recents. Still tweaking, but everything is running smoothly.

Per the layout spec here (QWERTY version): https://www.indiegogo.com/projects/pro1-x-smartphone-functionality-choice-control#/ This keyboard is 90% of a traditional keyboard with some absolutely random (and in my opinion, absurd) changes. For one, there is absolutely no reason to ever require the user to press the yellow "Up/Right" arrow to display a symbol. The "/" and "?" keys presently require using this key on the "P" and "L" keys. I would strongly recommend the following: Place the /? key in the traditional location (replacing current \| key. (this puts in the tradi

+1, that would be a much better key placement. I will definitively use backslash at the bottom-left corner regardless of the print but that is a right place for it and none of the positions of back- apostrophe key is perfect (that would be the position of ESC), so placing it below backspace is a valid option. I would also live without that key but in my national layout, that button is "0" anyway, so it is definitively used by at least one international layout.

I like Slions version, except I would swap the backslash and back- apostrophe keys. to more usual placements, and especially in light of other qwerty-based languages where the accents are usually on the right side

This has very obvious security implications, however. If you do this, you should be aware you are disabling some of the malware protection Google has built into Android. As an alternative, you might consider including gapps inside your custom OS image, like the OEMs do. For more details on how to do this, see: https://github.com/opengapps/aosp_build

Yes, that is what I meant. FWIW, meta+A doesn't appear in the list shown by Trebuchet, so perhaps there is missing code somewhere in the framework.

oh, quick question before I go to bed. Is there an R boot image/recovery?

Thanks so much, @tdm Can't wait to try this out in the morning! 😎

Okay, virtually everything in this thread is over my head. Can someone direct me to good sources to figure out how to create or modify a keymap and what to do with it. I'd really like to understand how to make this modification on my Pro1 and I'm willing to do my own homework, but would appreciate being pointed in the right direction. 🙂 TIA.

Anyway, I had a problem with Button Mapper on stock Android of Pro1 as it caused lag on my hardware keyboard and a feeling it is not fluent which was solved by removing it...

Android uses 'meta' for the built-in keyboard shortcuts, such as meta+B for the web browser, meta+E for the email app, meta+enter to switch back to the launcher (i.e. 'HOME'), and meta+backspace for 'BACK'. This list of shortcuts is extensible, but I don't think the interface is currently exposed in any system app. By default, the 'F logo' key generates KEY_META in LineageOS, enabling these shortcuts. You can display a list of the currently defined shortcuts with meta+/, although this is unfortunately a three-key chord on the Pro1 which makes it rather difficult to type. 😕 However, pressing b

Yes, this is a 2-in-1 problem. The first one is the different keymap of shifted (QWERTY) and normal (QWERTZ) variants of keyboards we have. It is a bit strange that F(x)tec itself has generated this issue as otherwise these layouts would work exactly the same way deep inside. So the problem is the shifting itself which made default layout of Pro1 to be unusual while QWERTZ variant is a perfectly usual layout. So @tdm's keyboard driver solved this issue by allowing to map appropriate keycodes to shifted keys respective to its written functions while also maps appropriate keycod

Revised layout suggestion attached. All characters in yellow should be accessed via SHIFT key, not requiring use of YELLOW UP-RIGHT ARROW.