Rob. S.

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...

Me, I cannot say because I never used a (potentially unsigned) custom build, but when I installed the official 18.1 build these days I had problems with GApps showing up, too, on first boot. Because of conflicting information and experience regarding how/when to sideload GApps (and Magisk) after having sideloaded LOS, I finally flashed those ZIPs on both A and B partitions (and then both came up)...

Nothing against it, but just to be clear, what do you mean with Fn? The key with the F stylized after the Fxtec logo?

Yes, I did just a few minutes ago.

Strange indeed.

Using English(US) layout, it does (except with software that takes over the keyboard like Softmaker Office). This is strange; last time I tried, I could bring up the emoji selector by long-pressing alt on LOS 18.1, but right now I can't, no matter in which app. This is QWERTY with English (US) International keymap.

Just for the record, now I've experienced the same for the first time after I reinstalled LOS 18.1 from scratch. AccuBattery showed 47% charge level and 7mA charge current (i.e. nothing). ACC is set up to stop charging at 75% and to resume charging when the charge level drops to 70%. AccA app reported "not charging" (with the cable connected) where it usually says either "charging" or "discharging". Contrary to what I was remembering, opening the AccA app (or restarting the ACC service) didn't restart charging, either, so I had to reboot, too. So according to AccA ther

Would it be possible and even sensible to make LOS behave a bit more like stock here, meaning that it would become compatible with FinQwerty/FxQwerty custom layouts? They seem to have worked well for anyone who's used them. I don't have that experience as I never used stock. I was happy, though, with how the US International keymap used to work in LOS 16.1, but I also find 18.1 a bit lacking...

Sep 2019 here 😆 – plus a Pro1X order from Oct 2020, to improve the odds for getting at least one phone at some point. It's all very well for me to laugh of course since in the meantime I was lucky to get a pre-owned Pro1 and I'm totally happy about it...

Definitely none whatsoever. There have been reports of only limited exposures to water which inflicted damage, we have to be a bit careful with fluids. (That said, I recently spilled a thorough measure of drink over my Pro1 and it lived, but it was closed at the time so the obvious part that might let liquids in, the keyboard, wasn't exposed to it...) I'm not too sure about it since here in Germany 5G isn't really a thing yet, as far as I can see. But from what I've read, and someone please correct me if I'm wrong, I think contrary to earlier generation changes 5G isn't really suppose

I'm using the "English (US), international style" layout for the physical keyboard (QWERTY), and I've attached what I get from it (made with Softmaker Office for Android on the Pro1) with the help of the Sym key when (as in most if not all browsers) I have no access to the long-press special key selection popup. Unfortunately, while this key map covers much including everything the German language uses, I already can see it does not even remotely cover the French accents. keys.pdf