Rob. S.

I just confirmed that the brand-new German AusweisApp2 (meaning "passport app 2") – which uses the credentials stored in the latest version of the NFC-enabled German passport (which I had to renew recently) to safely and securely authorize me online in various situations like dealing with the authorities (instead of having to visit them in person) for things like registering a new car – works perfectly with the F(x)tec Pro1 running LineageOS 18.1 (with Magisk and MagiskHide). Our phone is not yet mentioned in the list of compatible smartphones, but it might be soon, because I made use of the

No it isn't possible, see above post with link to SwiftKey forums. Major fail from SwiftKey if you ask me. Bummer. That's the one thing I don't like with SwiftKey, either...

I see. I have obviously no idea how long the registration process takes... Regarding root, I'd say if you didn't sideload Magisk you aren't rooted, and if you did, you are, no matter if you made actual use of it (i.e. granted root to some apps) or not. (I asked because I don't know whether root might interfere with Google Play Store honouring the certification registration...)

Yes, MindTheGApps should include all necessary services... Are you rooted now, or not?

Now that's interesting. If you try this, I'd be interested to see how it goes, and what banking and other apps say after that.

Right, I don't use gestures... It's the same, though, whether I come from the home screen or from another app.

That's what I originally thought, too. I started out with unrooted LineageOS 16.1, which was already installed when I got my device (pre-owned) and generally I was fine with it. It turned out, though, it is more likely to get all or most of those apps running with a rooted device than with an unrooted one. More and more apps check for modifications which deviate from an unchanged phone with stock and complain even if it the device running LineageOS is not rooted. As soon as you have Magisk properly set up with MagiskHide and passing SafetyNet, at this point (possibly impending changes in Googl

If I've observed the task switcher correctly, when "auto-rotate" is enabled, the cards' outer shape always follows the orientation in which the phone is currently held, and the cards' displayed content always follows the orientation the respective task was opened in. For me, this works the same for closed keyboard and open keyboard – with the exception that open keyboard forces landscape even when the device is held in portrait orientation.

@ToniCipriani @VaZso A couple of days ago I had a similar but different effect, the screen recording taps and moves all over the place no matter where I was actually tapping; I was told that could come from badly shielded power adapters and/or cables and some other devices were sensitive there, too. Then I noted it only happened when the phone was connected to the charger, and it stopped after I put that specific charger and that specific cable aside. Do you perhaps see a difference in behaviour between connected and not connected to a charger? Even though the charger/cable will probably not b

Yes, I've been paying contactless with my phone at supermarket counters ever since I moved to LOS 18.1+ Magisk. Just had to install Google Pay from Play Store, activate Magisk Hide for it (actually I don't even know if it's necessary) and configure something (like my VISA card) as payment method. At least here in Germany paying by phone actually works better than using the bank card via NFC, where the bank regularly requires me to enter the PIN even though I'm using NFC. With the phone I don't have to. Until now, I always installed system updates OTA from the system settings. Both GApp

I think the necessary services are all included, and the missing apps should be installable from the Play Store. I just added Maps (which somehow couldn't be restored from backup) successfully that way.

So after a few more failed/stuck attempts (I still can't seem to get to grips with that A/B layout, I'm never really sure whether I need to boot before doing something or not...!) I finally got it up and running again 🙂 Even the "Identity" one-time token app for my employer's VPN seems to run (but I need the IT service people to transfer the account to my Pro1 again before I can be absolutely sure). Also, much of what I had could be restored. So much for the good news, and the previous sentence already hints at some of the bad 😉 The one banking app that made it through the process d

Right, Fxtec is not who's making all this, the mainboard manufacturer ("IDEA international Development Ltd." in Shenzhen, China) is providing it. But I guess @claude0001 knows that perfectly well and criticizes Fxtec's purposefully-unclear marketing rather than their not doing more in this regard...

No... maybe a few minutes. (I wasn't successful at my first attempt, either, and I did kill boot attempts which took longer than, say, ten or fifteen minutes, and flashed everything again...) A factory reset after sideloading LineageOS is definitely not necessary. Regarding Magisk: First I installed Magisk by sideloading it. (I took the the apk from https://github.com/topjohnwu/Magisk/releases/tag/v23.0 and renamed it to zip before sideloading.) After first boot, the Magisk app already showed up. (If it wouldn't, you'd need to install the apk. I still reinstalled the original apk, t

@VaZso I just went through the procedure of moving to LOS 18.1 from stock, too (even though I went through stock only to get those display margins right after a display replacement, after I had bought my device with LOS already installed, so I saw stock for the first and only a short time)... Booting LOS for the first time always took unusually long for me (compared to a normal boot), regardless of the device, and no matter whether with or without Magisk, and it did so again this time. I guess that's just normal. To the best of my knowledge, user data needs to be wiped before flashin

I guess this is the time to mention @Erik so that he might get notice about @adam.c.r.roman's and @Swond's above cases? With the regularity these cases come up even with the limited base of existing Pro1 devices, I fear it is now becoming enough bad publicity to deter potential customers for the upcoming Pro1X. Regarding @ToniCipriani's case – I think we can be sure now that new display replacements will not come earlier than the new Pro1X itself, which (as of now) means not before October or November. Also, we don't know if there even will be black screen casings to buy for our exis

Ok, now I do: They're M1.4x2 and any shop that sells small screws should carry them. Also, they're easy to find in black, too, looking good enough for me to not bother with the black stickers anymore. (The black ones I just bought have a slightly thicker head than the original silver screws, but it's still flat enough for the black stickers to perfectly fit on top of them.)

You might want to try the 'AccuBattery' app for that; to record charge and discharge periods is one of its features.

Ok, no, it isn't! That's too small. (And no, I won't reveal how much I paid for them... 🤨) Next size from the list of Nokia E7 screws is M1.4x2.3 which now should be the right one – also something similar enough should be much easier (and cheaper) to source... I'll report back later...

Better still, there actually is something between the LED and the display glass now although I don't think it does much to diffuse the light: After I glued on the display and finally removed the protective film, I sat there and scratched my head and asked myself why there still was a red tab on the upper side of the screen!

Thanks for reminding me of that insightful table. No, I didn't exclude anything from the restore, only Chrome and Maps after TB got stuck or complained. I didn't even have in mind that switching the GApps package could have made a difference ("what could go wrong") at the time... Ok, then I guess it's back to step 4. – probably best if I choose MindTheGapps again for the new attempt..

This is what I did (starting with a fully functional and stable LOS 18.1 + GApps + Magisk + XPosed setup): Backed up everything (Titanium Backup). Replaced display. Flashed stock according to @Waxberry's [Guide] Restore to stock firmware using Fastboot method. Used the 20200825 firmware (it was necessary to re-enable the four commented-out lines in fastboot_all.bat). Display margins returned to normal on first boot. No installation of newer OTA updates necessary. Reinstalled LOS 18.1, GApps, Magisk, XPosed like in https://wiki.lineageos.org/devices/pro1/install and

Yes, they're slow end even erratic in answering emails... Also, sending multiple emails on the same subject is prone to slow things down even further, because that's how they said their ticket system works; another ticket on the same issue moves the issue to the end of the queue. That said, shouldn't your not being at home for a parcel be a subject between you and the parcel service? [Edit : didn't see your post in the other thread earlier]

Bummer! I just did my first own screen replacement (which seems to have gone well and was easier than I thought, and I also used B-7000 which is much easier to work with than any other glue I ever used for anything before, thanks to the tiny metal nozzle) but I forgot about the LED issue!