Rob. S.

😄 I never understand why the 'pessimist' has such a bad name, by the way! In my book, being a pessimist is the best basis for a happy, even-tempered life. If you always expect the worst, more often than not you'll come out lightened, pleased and happy because things didn't work out as bad as they might have, and even if they turn out really bad you're prepared, not negatively surprised, devastated...

I surely agree. That said, at least after Fxtec eventually decided to turn to Indiegogo again* for funding the Pro1X, a real danger of maybe never seeing either one's device or one's money again has always been the elephant in the room. Which still is no excuse for their bad (or complete lack of) communication, of course. _____ * after the founders (as a company named Livermorium Ltd. back then) had been using Indiegogo already to fund the Moto Z Keyboard Mod, which failed to reach general availability due to no fault of their own, with everyone being offered a refund, and

Same here with the OTA update.

Things already used to seem bad enough when Erik was still responding and setting things in motion for people who had come here with their problems. It did already give the impression of support being virtually nonexistent, except for the few people who find this forum and then try to catch attention here. I suppose even an Erik will be on holiday for some time. My own experience communicating with Fxtec has been something like fifty/fifty, with one thread in which I received sensible responses, although not quite the result I would have liked (which would have been the fulfilment o

The Middle Rhine (near a town named Oberwesel). They make nice wines there... I'm still happy with the Pro1's camera, by the way! @EskeRahn I just wonder whether we might have the size restrictions for images loosened here in the forum?

Yes, I already saw this on LOS 16.1 (never used stock), thought it was the hardware, and decided to just live with it... Also, if I have observed everything correctly, when in this state, after using the on/off button and swiping up to get the num pad (I have a numerical code configured as well), sometimes fingerprints work to unlock the device then, sometimes not.

Indeed 🙂

As usual, the OTA update installed smoothly here, too (with previously sideloaded MindTheGApps and Magisk installations unharmed)...

Yes, they did... looks good for now! For the sake of completeness: 😉

I don't use Alt-Tab much (yet, that is – maybe I should start to), but I guess I would be fine with using left-AltGr + Tab, too (left thumb + left index finger). I confess I still find the plethora of modifier keys on the Pro1 keyboard more confusing than helpful 😉

I confess I never tried French accents via dead keys, but you're right, some dead keys seem to be there, at least [`], [^] and [~]. Other than in LOS 16.1, though, ['] and ["] don't work as dead keys for umlauts in 18.1, as I think it would be standard in US international keyboard layouts with dead keys.

I think @tliebeck's question (which is also the thread title) is quite easily answered: because we need at least two keys which standard keyboards usually have on a sixth row above our five rows, Esc and Del, and unfortunately there doesn't seem to be a standard for five-row keyboards which include those two keys. Plus, there's at least one special key for Android which has no analogy on PC keyboards. That said, Fxtec could perhaps have found some existing keyboard on one of the many existing laptops/notebooks/netbooks than would have made a better model for our keyboard than what we have

From my experience with LOS (16.1 and 18.1, never used stock) I can say that the excessive call volume is related to VoLTE being enabled and active on both sides. While someone else (on another network) reported he had to completely disable 4G, for me, disabling VoLTE ("4G Calling" in the "Mobile network" settings) was enough to get rid of the issue.

Hmm... My software channel is "reteu" which I think means "retail EU", like in all my previous Motorolas... And "dteu" then probably means "Deutsche Telekom EU"...

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