Rob. S.

Tried Lawnchair, same thing happens. Looked at Nova's settings which indeed was 'battery optimised', but disabling that didn't help. When the selection dialog appears, it's system modal, but when I choose another launcher to go on with and then check Nova's info, it still is stoppable. My suspicion for now is that copying the Pro1's configuration over to the Pro1X (from Google's backups with the Google app on setting up the phone) carried over some hidden settings which are not compatible, even though both are on Android 11 (only that the Pro1 obviously was running LineageOS and t

Same here!

SwiftKey is an Android software keyboard with an autocorrect function that also works with the hardware keyboard.

QWERTZ with 'Physical Keyboard' set to 'German' indeed generally works. Although there are two bugs in the layout which make both the accent grave or backtick < ` > and the apostrophe < ' > unavailable:

I see, thanks! 🙂

Just for the record, for lack of a perfect solution I've now applied on the back of the Pro1 X what probably kept my Pro1 from becoming completely damaged because of frequent drops: clear packaging tape on the back (the one I've used it German 'Tesa'). On the blue Pro1 X, it doesn't even look quite as ugly as on the black Pro 1... The slippery back of the phone is arguably its most dangerous aspect; the phone slides out of your hand as soon as you loosen your grip a bit. And my impression is that the blue shell didn't help there much, if at all...

How about the approach of running some kind of Linux using Termux and PRoot, like AnLinux? You don't even need a rooted Android. I quickly tried a minimal setup of AnLinux (minimal Ubuntu + Xfce) which installed in a few seconds and does look like fun, except that after first install it doesn't come in native resolution and the RealVNC viewer I've used here (it uses VNC to display itself) doesn't seem too user-friendly, either, at least not at first glance.

I've seen other benchmarks which, all in all, attested the SD 662 only slightly lower performance compared to the SD 835. From that I would expect to hardly notice any difference at all in actual use, perhaps with the exception of a rare app that heavily uses one of the operations for which the difference is more significant. On the other hand, that's only the CPU; the GPU is substantially slower indeed. Still, as of now, the Pro1 X doesn't feel any less snappy to me than my old Pro1. But then again, except maybe for the BB PRIV, I never used anything but midrange phones which always performed

@Hook Yes, I did ...

Anyone else experiencing this? After setting up Nova (Prime) Launcher and making it default, I still frequently get asked which launcher I want to use when the home screen is about to come up.

Thanks @toast, yes, it was in the official update. Also, they showed images of the first cameras they received, and they showed '586' in the print on the ribbon cable:

The rear camera is a Sony IMX586. The sensor really has 48 MP, but the full resolution is only used internally, like for AF. This is standard for Quad Bayer layout sensors (the 20 MP, physically 80 MP sensor of the high-end OM System / Olympus OM-1 interchangeable lens camera, for example, has the same design and the same limitation). A full-resolution readout would not make much sense, as the colour matrix only has 12 million colour squares, each one covering an array of 2x2 pixels. (There are few phones with 12/48 MP sensors which make an exception, though, and try to make 48 MP results avai

https://play.google.com/store/apps/details?id=nextapp.fx&hl=en&gl=US https://play.google.com/store/apps/details?id=com.expressvpn.vpn&hl=en&gl=US My preferred file manager app and VPN provider. The FX name is just a coincidence 🙂

@spam71 Thanks for the report! Reasons why some of us thought it would have to be software are discussed here. Seems the Pro¹ X screws are fastened tighter than the ones on the Pro¹. Had no problem with that part of disassembling my Pro¹ today—but then again, for me, neither the removal of the keyboard (exactly following the instructions regarding the heat gun), nor the prying apart of the two lower shell parts went without inflicting ugly cosmetic damage to the shell. Especially the latter step was only possible using violence and metal tweezers, no other tool could find purchase be

You're right, they're two different things. Then again it might still be a specific problem of your phone; I've tested calls to both mobile and landline connections, calling as well as being called from the other phone, and no such issues came up in any way...

Just to be sure, I suppose this is exactly what should NOT have happened with the fingerprint sensor ribbon cable of my old Pro¹? I replaced the defective USB module today, and I wanted to see if I might be able to get the fingerprint sensor working again, too, which had stopped working months ago, but I guess I can forget about that now. Except if Fxtec might be able to sell a back cover including buttons and fingerprint sensor as a replacement part, perhaps?

The question has also turned up on XDA today, with links to the necessary boot.img file, which indeed seems to relate to the file @Casey Cheung linked to here. The rest I'd suppose should be the same as for the Pro¹... (Personally, I guess I'll wait with root until LineageOS becomes available. Unrooted stock Android on the Pro¹ X so far is a much better experience than I expected.)

Indeed. Interesting.

That would be true if Android phones would be obliged to come with a light sensor designed and specified to report correct Lux values, but that is not the case. The app is taking readings from a sensor that never was designed for the purpose, just guessing what Lux value those readings might correspond to. If nothing reliable comes out of that, it's not the fault of the phone.

It's Gorilla glass, and I doubt there's any phone on the market where it's easier to swap screens, provided you get the official replacement unit (which practically is the whole top part of the phone, replacement involves just five screws and a ribbon cable). As a cheaper option there also is the actual display available from sources like Aliexpress which is also not too difficult to replace, but involves gluing which carries the danger of a less than perfect result. Right, but there are other issues which may arise with protectors, and physically breaking isn't what you need to protec

Anyone else observing this? Once paired and connected, I cannot make the phone 'forget' a Bluetooth device. At least not with audio devices which actively try to reinstate a connection with a controlling unit that knows it, like a phone or a laptop. Tried this with a 'Willnorn Soundplus' Bluetooth speaker and a 'Logitech' BT audio adapter for stereo systems. If I tap 'forget' while the device is connected and active, nothing at all happens. If I tap 'disconnect' and then 'forget', the device moves to 'previously connected devices' for a second, then immediately reconnects and

Except for the shutter release button not having two steps (which is no problem for my as camera apps seem to start with continuous autofocus anyway), I have not seen any complaints yet with regard to the camera, or were there some? I've only found a small one so far; my preferred camera app ('Manual Camera') does offer RAW mode, but, when activated, either freezes or crashes when I try to shoot. The default 'Snapdragon Camera' app doesn't offer RAW mode to begin with. Neither does 'Open Camera', although it ought to, as long as the camera itself supports it. Might be a b

Import VAT (129.16 € including administration fees) was 22.4% of the perk's original price for me, $679 which did equal 576 € in Oct 2020. Excluding administration fees (111.31 €), it's 19.3%, close enough to Germany's import VAT rate of 19%. I think I missed the 'super early bird' offer only by a few days back then 😉 but I found and find $679 to still have been an excellent price for what it is. By the way, without root, for the time being, and therefore without the ability to use the 'Advanced Charging Controller' daemon and app (ACC/AccA), I've reactivated my 'Chargie' devices to