Rob. S.

I asked and they haven't. Reassembled the phone now as it is, and I'm actually surprised it switched on and booted successfully, given how clumsy I've been... That said, and to get back to being on-topic for a sec, in the process I also damaged the volume-up button and the camera button... Thankfully the phone is still usable without both. One other thing happened, too; the screen orientation is now fixed to landscape, as if the keyboard slide mechanism would permanently signal 'keyboard out'. Any idea what I could have missed in reassembling there? (For now, if I have to use the old

My phone doesn't exhibit what you describe, but then again I think we can give you the all-clear there, because what you can touch on the back of the phone is not the camera itself, it is just a clear window over the camera, part of the phone's casing. The camera unit is fixed inside on the opposite plate, the one on top of which is the keyboard.

@Logan Like @EskeRahn, I usually resort to a "real camera" when I want to get halfway decent photos in low light 😉, but, I guess, for the Pro1X, 'Open Camera' might be a decent starting point for low light, too, if it has to be the phone. There might be special apps which add something like 'night mode' (which may or may not call for a tripod), but I have no experience with those...

Regarding that guide... ... I've read somewhere else that QPST/QFIL doesn't work from a Windows VM within a Linux installation, either, as @Casey did suggest; or does someone have other information/experience?

Like I feared, it doesn't help...

With the original Pro1 and LOS 18.1, I mostly did use 'Manual Camera' because I like its interface and it also can produce raw (DNG) files (not with the Pro1X, though), in theory giving me more options for post processing including best-of-breed noise reduction. For the Pro1X, I've now found 'ProShot', which not only can output DNGs, but also has an intelligent image optimisation, which, for example, sharpens the (generally weaker) corners more than the centre, producing visibly better default results than I've seen from other apps until now. Unfortunately it has no HDR options and therefore i

A well founded decision. It's just not compatible with my laziness 😉 Bummer, that strengthens the suspicion... And given that other Launchers also suffer from the issue, it might not even help to uninstall and reinstall Nova... but that's what I did just now. Deleted its data before uninstalling just in case. We'll see how it goes.

I haven't heard about the existence of clandestine OTA updates happening in the background, and I have no reason to suspect my phone would have had any such update in the short while that I have it. That said, I have no idea what has been happening here, either, but, purely speculatively, I could think of some things. Like some kind of speaker calibration happening in the first days of usage, with some usage data gathered and the driver behaviour changing slightly according to the collected data. I have no idea why anyone would program something like that for something as simple as a speaker,

Yeah, I´ve read somewhere that the default launcher includes some basic functionality other launchers rely upon, too... so disabling is not recommended... 😕

All of this, despite being a completely different matter, reminds me a bit of an old Chinese 'Chuwi' x86 tablet/convertible that came with an Android + Windows dual boot setup which was so fragile that even just looking at the incredibly complex flash drive partitioning "from the outside" with a pendrive-booted Linux left the system in a state so that Android wouldn't start anymore. In the end I repartitioned the flash drive, the 64 MB of which had been too small to share it between Android and Windows anyway, and installed Linux Mint. Should have done that earlier...)

I suppose the camera button is connected to the default camera app like it used to be on the Pro1. Problem now is, starting with (stock) Android 11, changing the default camera app is not possible anymore for alleged security reasons. One of the many Android changes over time which artificially limit the versatility and reduce the usability of our phones.

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