EskeRahn

Have I missed some announcement, or am I interpreting what they are writing wrong? Will it initially be available with these two OS only? I see no mentioning of plain stock Android.

(lineage-18.1-20210712-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210412_124247) Then redid with the new OpenGapps 11, Including a WIPE of the user data! (lineage-18.1-20210712-nightly-pro1-signed.zip on June 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712)

I totally agree that the Pro1/Pro1X is not a device for everyone. For those entering a modest amount of texts, a real keyboard might not outweigh the various issues (size, weight, curved display and many others) but for us that uses a keyboard a lot, there are few alternatives. And in my book comparing those ends as an easy win for the Pro1. BUT that is my personal weighing, other might end up prefering one of the few alternatives, or even decide to let do with a fake (=touch) keyboard, to get a device sold in millions or billions, and thus (most likely) a more smooth experience..

Though a full case is definitely an interesting option, it will make the space above the top key row less, so the two are not independent. Also note that a regular screen without curvature, would cause the same, unless it was smaller, with a curved housing. And that effect (less the protection of the display) can easily be achieved with software leaving a passive black margin on the current screen. Personally I got no problems with the top key-row. But for people with large(r) thumbs and/or long nails and/or a full case, I can see the problem. So that would suggest that it would have been

There is a silly setting that automatically tuns the phone on when a charger is applied. It can be turn off from a pc (If i remember right it is a fastboot command, but could be adb)

This sounds like a much better idea. Hidding yourself in the head with a mallet to get rid of a headache is not recommended either, though you might be lucky that it works...

The hardware of the qwertY and the qwertZ models is identical, except the print on the keys. The software handles qwertY as the default. When qwertZ is selected by the user, the keys are remapped.

I am in an odd in-between position. I have no issues with the size of the keyboard. (I use std qwertZ, not the shifted qwertY) But on one hand the screen is too big to use one handed as touch only, while keeping a secure grip. My thumb is incapable of covering the full display. On the other hand I'm so old that a smaller screen, in a font size I can read effortsless, would leave even less data on screen....

Can be hard to guess the cause, hopefully just a software bug teasing. If it is hardware, battery is not very likely, it is more likely that the usb-port is somehow damaged. Dirt is a common culprit in a usb-plug, but unlikely as you had the coil plate installed in the port. But perhaps an unlucky bump to this broke the usb-port?

I would first try to hold the power button for some 10 seconds as this is a deep (non-destructive) boot. If noting happend. Try to plug in a wired charger, leave it for say ten minutes and retry the same, to see if you get anything on the display and/or the notification LED

Yeah, a series of images rotating between portrait and landscape could do the trick, hinting that the device is designed to be used in either direction.

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

I would love if it selected one with the proper orientation, depending on how you hold it, and not just portrait only...

Note to self: Do not throw your Pro1 under a bus nor a steamroller. 😇

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.