Rob. S.

Of course, thanks for the hint! The "Reporting Body Identifier" is 35, meaning it's from the UK...

Here in Germany I don't think I ever had a phone with a SIM lock, but I may have just been lucky. My G6 doesn't show any traces of having come from any of the mobile providers, either...

Bummer, you're right. I was actually recording music coming from my living room stereo, but I must have been playing it louder when I recorded with FiLMiC. Tried again now with lower volume and it indeed becomes just as bad as with the recorder app. 🙁

That's interesting indeed... Perhaps it were just some countries where the update didn't arrive? That said, I cannot really be sure where my G6 really comes from, as I bought it second-hand...

Oh, I didn't want to suggest something different, either 🙂

There's one workaround: Record video and then extract the sound. The sound in video is probably as good as it gets with the built-in microphone, and no obvious noise filtering, compression or any such thing is going on there. (Just tried it with the FiLMiC Pro app that also gives you a a bit of control over audio quality and the recording level.) EDIT: No, it doesn't really work, see below... 🙁

Just for the record, for me, the Pro1 seems to have no significantly worse GPS precision or ability to get a GPS fix compared to the phones I was using before (Motorola Moto Z, Moto Z3 Play). That said, a Moto G6 I have acquired lately (just to find out that here in Europe it didn't and won't even get the update to Android 9 that it got in the US, so it will be stuck on Android 8) actually does seem noticeably better. Outside of my house, the Pro1 varies between 4m and 9m accuracy, the Moto Z3 Play between 3m and 9m, while the Moto G6 quickly arrives at 3m and stays there, using the tool @Eske

While the design isn't for the battery to be immediately user-replaceable like the Nokia, the replacement still seems to be relatively easy because it's not supposed to be much more than removing a few screws. That said, a bigger problem might become to actually get a new battery. F(x)tec doesn't seem to be able to ship any at this time; the ones they're offering through Indiegogo (I ordered one in November 2020) have been officially delayed until October, and we have yet to see whether this works out. While, in contrast to the display which is easy to get because it's identical to the one in

Just for the record, after I decided to install LOS 18.1 with Magisk when I moved to 18.1 after had been using a non-rooted LOS 16.1, the first thing I tried was to just install the next OTA and see what comes out of it, and both GApps and Magisk were still there and working after the reboot. Has been that way for me ever since.

Good idea. Something to try next time I need a screen replacement, if noone else does it first... By the way, I guess someone should really change that script and remove those REMs before the system/vendor related lines...

For what it's worth, charging didn't want to start again today (charging level was at 53%), and then I had another look at AccA and its several configuration options. One of them is the "charging switch", and beside the option to add one myself and an "automatic" option, I can choose between five preconfigured "charging switches" which are labeled like this: battery/input suspend 0 1 (default, selected) dc/input suspend 0 1 0 250 350 ... whatever all of it exactly means (ok, the first two are somewhat self-explanatory), and there's a function "test charging sw

Thanks for the confirmation. What I'm still not sure of is whether this has been in Android 11 / LOS 18.1 right from the start, or might have been introduced later? Like in one of the last few updates? I've been on 18.1 on my Pro1 for a while now, and I've been using Locus Maps on it for a while, too, until now also without observing any GPS hiccups (I've asked about that on the Locus Maps forums, too)...

Today I noticed (because the device switched off GPS while my hiking app, Locus Maps, should have been recording the track) that some apps under "battery optimisation" are neither listed as "optimising battery use" nor "not optimising", but "battery optimisation not available". Is this something new, because I never saw this before, especially not with my Locus Maps app, or have I just missed out on this?

I have been trying formatting my SD card to ext4 in an earlier LineageOS version, too, but had to give up as hardly any app properly worked with that setup. (I didn't have root back then, though.)

Elephone U pro is correct. Yes, Elephone U Pro is definitely correct; all the successful third-party display replacements I've read about here (plus my own) were with Elephone U Pro screens. That said, I have yet to learn of any difference whatsoever between the Elephone U and the Elephone U Pro screens. Some Aliexpress sellers do offer a choice between the two, but some don't (and only offer one screen as fitting for both phones), and none of even those that do actually would show two different screens for U vs. U Pro, it's always the same image. (Have there perhaps been

Indeed, but wasn't that something that's been reported very early and also fixed in the first stock Android update?

I guess from what's been reported here so far it's safe to conclude that a run-down battery is largely unrelated to the phenomenon, except that the phenomenon helps a lot in letting the battery run down 😉

Don't worry, I don't think your criticism regarding users' rights would have made anyone infer that you wouldn't care about world hunger. Maybe even less so if there might be agreement about both issues, different as they may be, having common causes.

Indeed. It gets even weirder when not only a rooted, up-to-date LineageOS, but even an unrooted, up-to-date LineageOS with the latest security fixes is seen as a security issue by many banking apps, while an ancient Android 7 phone that never received any fixes is deemed secure enough for those apps to not complain... Don't get me started on this 😉

Indeed!

I didn't know we had a guitar in our Pro1? Ok, that's exactly what AccA reports. Question is, is there a way to force it from 'not charging' to 'charging' without having to reboot (if we don't get the device to automatically switch to charging, that is)...

Lately, once in a while I get two 'e' characters instead of one, which definitely looks like the result of wear. I still hope that one day we'll get those replacement keyboards Fxtec originally hoped to be able to offer at some point, which seem to be easy enough to replace at home... We'd also be able to exchange a QWERTY keyboard for a QWERTZ then, or vice versa, or a shifted QWERTY for a non-shifted QWERTY...

Interesting. So it seems like there are application developers which bothered enough to implement at least a check for a physical keyboard, but didn't bother enough to really think about exactly how a physical keyboard should behave differently... In theory, I would see two approaches to fix this – filing bug reports for every app behaving like this, or finding a way to (optionally, per-app) trick Android/LineageOS into not reporting the physical keyboard to apps, if there would be such a way... (FWIW, I recently moved from K9 to FairEmail, which looks a bit like K9 in its brand new

Strange. To the best of my knowledge, there still must be some piece of software doing it. I've never seen a hardware keyboard doing autocapitalization...

I'm still not sure about the whole spectrum of things the app can change, but I guess the app can change quite a bit. I fear my brain is already overloaded with all those keyboard details even without going into things like debugging and changing a keyboard driver... I can't quite remember how it used to be in LOS 16.1 (which had an US International keymap with dead keys for accents and umlauts), but now in LOS 18.1 the long-press special-character popups don't work in text boxes on web pages, so I'm happy to get the umlauts and accents I need through Sym+key combinations...