EskeRahn

I have tried rigoursly to find a stable way to trigger it, without any luck. The bug is common for Lineage 18 and 19 as well as AICP R Unfortunately we do not have an Android 11 for the Pro1, so we can not tell if the bug is in Lineage or deeper. When the bug kicks in, the phone DO draw power from the charger, but only to sustain what ever the phone is doing, not to charge it, so the battery percentage remains at a (roughly) constant level for hours. There seem to be some system to prevent over-charging a constantly connected phone, my personal theory is that it is this system,

Moving more into the guessing land, you must remember that they can not get a new Pro1, and that they (from what I seen users report in here) early on was unusually kind in just replacing phones on various errors. So they are likely to have a number of devices with some deffect they can potentially refurbish with a combination of new parts they can get, or used parts. But indeed doing so, the resulting devices ought to be thoroughly tested before sent as replacements.

It does indeed sound odd. But guessing here it just MIGHT be that they have combined parts of multiple devices deemed dead-beyond-repair to create a replacement unit. But it certainly does not sound good that it then comes back with keys not working correctly.

Have a look at this https://eskerahn.dk/?p=3123 (How I got rid off this on my Samsung) - but could be any android device)

(Smoothly installed aicp_pro1_r-16.1-WEEKLY-20220622.zip on June 5 security patch and open_gapps-arm64-11.0-pico-20220503.zip using adb sideload)

Indeed. I met them at the London event before all the Corona mess. And it was quite obvious that these are really good guys, and kind too. If you could blame them for anything it would be for being overoptimistic, and that communication isn't their strong side. But they undoubtedly really tries to go an extra mile to bring keyboard phones back. I'm amazed to see their stamina! Had it been me, I would have folded after the swindle, but oh no, they 'just' went for reinventing the whole inner part once more!! And Chen's handling of the Moto-Mod project that failed due to Motorola, was also a

(lineage-19.1-20220620-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313)

Last chance.... One left, that is likely to be gone in a day or two....

(Smoothly installed aicp_pro1_r-16.1-WEEKLY-20220615.zip on June 5 security patch and open_gapps-arm64-11.0-pico-20220503.zip using adb sideload)

Indeed, touchscreens are just fine for replies like "OK", "Thanks" or "See you". And works tolerable for most web-addresses too. But a longer reply.... nah...

Add to that not having to look concentrated at the keyboard during typing, to keep touches inside the dedicated 'key' areas.....

(lineage-19.1-20220613-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and MindTheGapps-12.1.0-arm64-20220605_174313)

(split some old keyboard related stuff over here https://community.fxtec.com/topic/3576-key-mapped-as-meta-key )

Launcher3QuickStep.zip

No doubt that Nova is smart with many features. Which only makes it even more odd that they (still) do not offer a more advanced solution for Landscape/Portrait. As for quite a number of years aspect ratios in the ball park of 2:1 has been very common on slabs. One offer could be individual settings, another could be to to offer the 2x1 vs 1x2 mode that our stock launcher offers. (The flip-side of the later being that widgets obviously can not generally cross the border between the two 'halves')

Have Nova Launcher finally found a better way of handling landscape than compress and stretch of portrait (like most other launchers also do)

Does it work for your set-up?

This is the info I see on it. (ignore the old stamp, other system stuff reports the same)

If I remember correctly I tried to use it on Lineage without any luck... (it is a variant of the AOSP com.android.launcher3 available here) ADD: Just (re)tried. The APK does not load on neither LineageOS 19.1 nor AICP R

Then I would say that it is highly unlikely that you would be the first to get a mail, so I think the "oem" here is the key for "China"

Ah! Good point. Sounds plausible.

Indeed this looks self contradicting. I do not know why. My personal GUESS is that they in April just got a confirmation that it passed and they would be getting the official approval, but did not get the actual paperworks... But I could be wrong. And do seem odd that this should take more than a month to be delivered.

Mindthegapps on 19.1 has a /system/addon.d/30-gapps.sh of 2.2Kb size that looks quite different from the similar 70-gapps.sh I see on AICP with OpenGapps (10.8K) Here collage of the interesting parts (in above order)

I can see that I chose my perk with the Scandinavian layout. Will be interesting to see if this affects the delivery time? I would not be surprised if plain US-QWERTY was served first.

Just tried to redo the lineage-19.1-20220606-nightly-pro1-signed.zip using adb sideload and NikGapps-core-arm64-12-20220421-signed.zip To get rid of some of all the junk from the MindTheGapps package - (OpenGapps still does not support 12(.1) at all) It got 'stuck', never going past the initial animated logo. New reboots and patience did not help. Note that I did NOT do a factory reset at first attempt. It did load enough to support adb though so did a adb reboot bootloader Selected "Recovery mode" and there "Factory reset" and reboot. It worked in principle. (But still with s