EskeRahn

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.

Great that it works for you. 🙂 Though I'm quite puzzled how it could fix it.

(lineage-18.1-20210607-nightly-pro1-signed.zip on May 5 security patch installed smoothly using adb sideload and MindTheGapps-11.0.0-arm64-20210412_124247) Please note: On keyboard layout selection issues, see this thread.

A functional question, I noticed a minor dent at the bottom of the upper camera cover, does it affect images? EDIt see answer below And a thumb up for that one. 😁

Just a hint to potential buyers. It looks like all this wear will be within what will be covered if you use a shell (or flip case), grabbing the lower part. There are multiple alternatives, you could start in the newer end of this long thread or at my DIY experiments.

Same here... 🙂

It is, and there have been none since (to my knowledge).

@Rob. S. How do you correct the item order as you did? The fourth icon is hard to get in portrait. And the one used most by me is Aeroplane mode that is fourth on mine.... PS I am aware that I can DISABLE others, but no matter the order i reenable them, i end with Aeroplane mode as the fourth, not lockdown

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

Since just after a software upgrade, I would guess software issues first. But obviously it could be unrelated and be a hardware issue.... Had it been the front facing camera, it could have been accidentally pushed during the display replacement, but it could hardly have affected the rear camera.

I'm not sure if it will work, but you could try to limit the bands it is allowed to use. In the dialer app, 'dial' *#*#4636#*#*, select phone 1 and select "Set preferred network type" gives something similar but not identical to what @netman suggests.

I bet that was the hardest part, to leave that bottle untouched for 48 hours? 😂

Oh clearly it is. And even more so as the coming Pro1X are going to have different interiors, so the ten are unique. So it is a matter of finding the right collector for it. As a rarity it is not exactly what I would expect the buyer to use as a daily driver. Unfortunately for you I think there are more potential users than collectors in this forum. So you might benefit trying to search for a more general forum for rare phones, to find potential buyers willing to pay up 🙂

As far as we know the only difference is the colour between the original Pro1 and the Pre Christmas Pro1 X. (The internal storage differences, new key layouts and different software were planned to be for the models set for March. That is, until they were hit by the swindle and forced to change radically)

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

(thanks, merged the threads)

Sorry, I do not. But let us tag @Erik that might know.

It seems to not always be a requirement, but it do seem to fix it if you got the issue. But an upgrade can survive! The precise condition for when it survives and when it fails is unfortunately currently unknown. PERHAPS it is related to installed keyboard drivers and/or FinQWERTY, but could well be even more complex. Mine was upgraded from 16 to 17 last year and now to 18. I do not recall if I even made a factory reset going from test-16 to release-16 in the autumn... So might be old rudiments that triggers the issue now. If so it could be very hard to reproduce consistently, and thus not v

At the least one seem to have got one of the second category.

Yeah, the two early one could be fake... no one seems to have posted that they got one....