EskeRahn

Next time try launching a program that ignores your auto-rotate setting, And rotate the Pro1 back and forth within the app. e.g. the snapdragon camera app or AndroSensor. It usually solves it for me.

Slight update to the helper-script, removing a few clicks, and make it more suited for 80 char width Assuming the needed files are saved in a LineageOS sub dir, so change as needed. @ECHO off if %1.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot bootloader pause fastboot flash boot_a LineageOS\lineage-16.0-pro1-test%1-boot.img fastboot --set-active=a REM fastboot reboot recovery does not work, so do manually: ECHO * Roll down to "Recovery Mode" with VolDown, and press Power to select. ECHO * Await recovery boot. Select "A

A little more on LiveDisplay. The options displayed is the same for Test9,10 and 11. There is another minor (new) issue from Test10: In the notification area, pressing and holding the A in a square fails to launch LiveDisplay (It works with both Test8 and Test9, but NOT on neither test10 nor test11) It understand that it is supposed to do something, and collapses the notifications, but no launch.

Here an example with some allegedly 0.5mm thin rubber strips from here suitably cut I placed two 'long' strips (5x65mm) at each end, and two minor pieces, one next to the space bar under the screen (3x17mm), and one on the opposite long edge side (7x17mm).

Just a hint. IF our mail-server's certificate is not correct we can select to accept this BUT if we import settings, we are not presented with this option, we have to go to both incoming and outgoing server on each mailbox affected, and click connect... Only then will we be presented with the dialogue to accept... (it is a K9-bug)

Same here.

You are absolutely right, home office might not be a possibility. Even though the computer could be just a laptop, but that too could be a problem. If some other family member already use the flat during the day-time. As an example take the classic stereotype of the wife using the flat for some textile business in day time. And even if the flat is spacious enough, the internet connections available might be of a quality/price preventing a VPN connection from being a viable solution.

And the FM works too. Thanks. 😎

As a last resort, if all other methods fails, I suggest a small piece of high friction tape. see e.g. here for various suggestions on how to open.

It would be if the software development were based in a place without COVID19, but unfortunately idealte is in China (AFAIK), and china have not had a tradition for even IT-people to work from home. So most likely things are not set up allowing that. It would require a VPN setup, and a company sponsored computer per person, and if they not already got that, it will be hard to get that too now, even if the budget for that was accceptable.

Thanks. Well I have no idea. And do not know how to check, sorry.

Thanks, works like a charm AND you forgot to advertise that it nicely re-awakes the screen by the magnet only, if re-opened before the Lock-time-out. 😎

Just curious, why are the options in LiveDisplay reduced with Test10 compared to Test8? (do not recall how it was on Test9)

Awesome, thanks!

Virus? What virus? [/sarcasm]

Try press and hold the power only for about 7s and release. That should force it to restart, and that should show something on the display within a few seconds. If not it is almost certainly a hardware issue. I assume we can rule out a completely flat battery, right? If not attach it to the charger and leave it say half an hour, and retry the about 7s power-press. It should at the least show a logo.

... Or the more realistic 3) , they don't have anything they can send currently. If you should have missed out on it, they still have not got neither all the phones nor alle the parts they need.

An odd issue I have had quite a number of times: When the screen is locked, I try with a finger to unlock, but get the double-stroke haptic feed back telling me it was rejected, I can try two-three times with same result, If I then press the power button, and tries the finger again, it is accepted without any problems. It is not that it never is accepted, it just happens a little too often to be accidental, I think, I do not see it on Stock. Does anyone else see this behaviour?

I tried to simplify the flashing process so I did not need to fiddle with the devices buttons, and remember/read as much If I do this at the bootloader fastboot reboot recovery the response looks sensible Rebooting into recovery OKAY [ 0.001s] Finished. Total time: 0.003s BUT despite saying otherwise it boots into normal and not recovery, so can not simplify that step So now my script for lineage+gapps is like this @ECHO off if %1.==. goto :EOF ECHO * Wait for boot to bootloader to finish (or do manually holding VolDown+Power) adb reboot

AFAIK they are electrically wired in parallel, so the 66 physical keys represents 64 'logical' keys.

In other threads someone have reported that this issue on other devices is often linked to buffer under-runs. But of course there can be many reasons for that, but a buffer increase would be a place to start, if it is not a problem with pulling data faster than it fetches it.

But just imagine if it turned itself off when not needed/relevant, so we did not have to do it manually.... It would make things easier...

Well sort of. Root ALSO breaks SafetyNet, but it requires more than just not rooted to pass. (yes yes, I am aware that rooted there are tricks to get SafetyNet happy)

See the text written in red in what you quoted. 😥

It is clearly having several issues that needs to be adjusted when used as speaker phone, as discussed elsewhere.