EskeRahn

It has been reported before. I do not personally see it though, (and do not remember if there is a known workaround)

My guess it it much matters if people 'know what they are doing'. If a device is opened and something accidentally destroyed in the process, I doubt they will cover it, but if opened and closed properly they seem to be quite generous on it not breaking warranty. After all It is designed to be service-friendly with the majority accessible after dismounting some screws only, without the need of a heat gun. So if in doubt contact a local service-professional and have them help you. Add: Also remember that the original Pro1 quite literally is irreplaceable, as they can not get the components

Thanks. Have you tried if his workaround fixes it for keymapper for you?

My guess is that the three all mess with the keyboard part of accessibility, but Greenify uses other parts. (Android Assistant uses it to fake user interaction for stopping apps, and that might be done with sending e.g. combinations of tab and space....)

Great, thanks. So we know of at the least three apps that can trigger the issue. (but it is not all as Greenify can have accessibility ON) Some confusion on names. The app I mentioned was previously called "Android Assistant", and that is how it present it self on the phone. But on the Android market it has been renamed to "Assistant for Android"

Just to be sure for those that are testing. Does it require BOTH of these two to be installed to trigger the issue, or does EITHER of them do it individually?

It is the one from "AA Mobile". https://play.google.com/store/apps/details?id=com.advancedprocessmanager https://play.google.com/store/apps/details?id=com.androidassistant.paid (despite the different name, it is the paid/ad-based variants, both can cause the issue) ADD I see in user feedback that other of their users have reported issues on Android 11, so unless other apps causes the same, it might not be important now.. @TeZtdevice do you also use Android Assistant, or were it other apps that triggered it for you?

Just did a clean factory reset, restoring nothing, opened the Android Market app and installed Android Assistant (only). And from Accessibility set it to ON, and it is enough to trigger the phenomena.

Thanks!! Not quite though. It is allowed to have Greenify set to ON in accessibility, so not a general issue, BUT if I turn it ON for "Android Assistant", the keyboard is messed up, and turning it off things works again. So now at the least we have a way to trigger the phenomena!

Mine DID work, but today it does not???? I will see if I can find the time to dig deeper on the subject later, currently I'm just confused..... My best guess is that since I had done a factory reset it initially worked, until some app of mine were installed as part of the restore in the background.

Yes this is a forum issue. They raised the bar for images in replies, at some point, but in the original posts, the limit is still rather low... I'm not sure if this was by accident, or a deliberate attempt from stopping spamming bots flooding the servers with garbage. I'll tag @Erik in case it was by accident.

Seems to be fixed with the 20210614 update 🙂

(lineage-18.1-20210614-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210412_124247)

You could try to flash the 20210531, with a little luck it will work stepping back 'one step' even without resetting.

The IMEI number is an individual number for each specimen of a phone model. You could see it as a standardised serial number. See e.g. wiki

PS I will suggest the opposite order. Install the functioning rom, and do a reset from that (you can do it from the recovery menu, so it is a clean boot on the newly flashed rom) (I have updated the original bug report with this new variant, so if we are very lucky and a developer is bored today, we might see a fix included in tomorrows update...)

Will do 🙂

Nope, it is a test-device (the old pre-production unit without a few radios...) A factory reset does NOT fix it... Will try to flash a few weeks back and do a reset... Edit I. It still worked flashing 20210510 (and doing a factory reset) Edit II. It still worked flashing 20210517 (no reset) Edit III. It still worked flashing 20210524 (no reset) Edit IV. It still worked flashing 20210531 (no reset) SO the conclusion is that keyboard selection was broken with the 20210607, beyond what a factory reset can fix! (will not re-flash now, but optimistically try going from 0531 to 0614

Oh you are right, sorry did not test, just asummed it still worked.... But yes It is destroyed on mine again(!) Ctrl+Space for changing languages is again ignored. Is it on yours two? (you have to have selected more than one first obviously) I will try to do a factory reset (yes tedious!!!) to see if this fixes it this time too.... (tried the two softer resets of network and then apps, and as expected that did NOT make any difference)

You need to BOTH tell it whether it is the qwertZ or qwertY version (see above) and ALSO select the language you want to type on it. e.g. German on qwertZ.

I'm not sure I quite understand your question. You can select the physical layout Inside Lineage settings ("languages and input", "physical keyboard", "Advanced settings", "physical layout"). If it is selecting the layout you wish, that does not seem to work, then see a few pages back, where I had odd problems with the layouts going to 18.1, that was fixed by a factory reset. We never really found out why the upgrade failed. For some the upgrade goes just fine, so some combo with other stuff...

Many other factors could affect this (unfortunately), so no easy dead sure answer. Sometimes a different port (even on the same PC) can make a difference. And some have reported that using a hub might help, and others that not using a hub helped... The driver on the PC for the port also matters... so I would say the best to do is to experiment, including other cables and perhaps other pc's. It is not that it is hard to get it working, but when it isn't working, it can be hard to figure out the why. 😖 I have it working fine even with fairly cheap Chinese usb-cables on an ancient Lenovo th

As far as I know there are no OIS in the setup, so it must be the focus mechanism you are 'poking', so if it for some reason got stuck or had some dirt preventing its movement it does make sense that poking it might help it move freely again.

Never seen that. My guess would be that it is some app that does it.... Say some app that fails to do whatever it tries to and is signalling for you to fix it. e.g. a mail app failing to communicate with the mail-server When you say restart, is it just a Press power select Restart, or is it a hold power down for some 10 secs? The later does a deeper boot. (and is simple and non-destructive so try that first) If that does not fix it I would try to stop apps (Settings, Apps, See all apps, find and click app, click Force Stop) on any newly installed or newly updated app, to see see if t

just to be sure, have you tried checking if the top part is 'clicked' together. Some have reported that it can get loose, and that we can simply snap it back with just a squeeze between two fingers. That MIGHT explain the random behaviour. See it described with images here.