Leaderboard

The update is here, just making November. https://www.indiegogo.com/projects/pro1-x-smartphone-functionality-choice-control/x/17980121#/updates/all

I'm hoping to improve the existing Settings app as part of the changes to support the Pro1X. An option to install a custom keymap from within Settings seems like a good idea, and I want to add support for a full custom keymap generator app in the driver. This would include a way to ask the driver what default keymaps are supported, and what keys are in each map (i.e. what is printed on each key). Since the default QWERTY map on the Pro1X will be different from the Pro1, the standard keyboard layout names aren't sufficient specify the correct 'default' keymap.

For completeness 🙂 : So there we go – January at the earliest, more probably February.

Quite well, actually. Earlier this year, to be a bit more safe, I applied a display protection foil after the phone had come back from a screen replacement. Next thing I did was trying to swipe some dirt from the display, which resulted in swiping the phone from the table, as the screen protector was much more sticky than the screen alone—making the next display replacement necessary... Then I thought, why not put something like that foil on the back of the phone instead of the front? I experimented with commercially available back cover protector foils for some other phones, but they did

It will be on January, in the current prediction... We are getting close.... Maybe I can get mine on February

November update is here: https://www.indiegogo.com/projects/pro1-x-smartphone-functionality-choice-control/x/17980121#/updates/all

Theoretically, the driver was designed in a way it should reflect the written texts of the QWERTZ unit (also for non-standard places), so I would think it should basically work out of the box when you also select German layout in Android. However, to activate custom keymap function of GUI, you should place your custom keymap file here: /data/system/keyboard/keymap It has a format of 0:0000:0000 1:0024:1024 2:0031:1032 ...etc... The first part is the physical position of a key (reflect to physical wiring), the second part is the normal function of it and the third part is

What symbols do you get, if you try to type the Umlauts? I had the problem, that I had Fxservice installed on LineageOS 18.1, which triggered the bug with accessibilty services and prevented the German layout to be used. So instead I was getting [ and similar symbols instead. Could that be your problem?

Thank you - I didn't have chance for it to test (on other device) before but now (as part of the last update) it was installed on my daily driver. Naturally, it works. 🙂 Maybe one option what would be good to have is a setting to pick a custom layout file then copy it to its appropriate folder, that would eliminate the need of any kind of root mechanisms. However, it is an Android programming question and not kernel-related.

(lineage-18.1-20211129-nightly-pro1-signed.zip on November 5 security patch installed smoothly using OTA ) ...But the reintroduced (early August) Accessibility / keyboard bug is not (yet) fixed. The stage after download and install called "Finalising package installation" is surprising slow though)

When I used stock ages ago, I used an app called Edge Null to set the screen margins. Worked pretty nicely, IIRC. https://play.google.com/store/apps/details?id=com.meatcube.edgenull

So the next update will be "all the phones are packed ready to be sent out tomorrow"?! That sounds too good to be true though I certainly wouldn't complain.

I was on stock and hopeful for the longest time but gave up on it as the chipset "upgrade" of the X clearly meant the original would not get any official support. Moved to Lineage 3 months ago and never looked back. Yes it takes time and effort to set it up but it is well worth it.

I am completely gave up using stock OS, going for LineageOS is a better option instead. Also, it has Android 11 support...