Leaderboard

I intend to stick with LOS 17.1. Building wasn't difficult, but I am afraid to install my build and mess up due to signature issues. I hate not having TWRP :-( Anyways, I plan to try my luck within a few weeks. If the update from the official LOS 17.1 to my own build works out alright, I will publish this new build here and on XDA.

Short answer: Why not? 🙂 Long answer: I have set up a quite complex system with LOS 16 and a GNU/Linux (Devuan) running in a chroot, with multiple partitions, automatically starting servers, and shared data folders. To realise that, I use all kinds of tricks to work around Android restrictions. I fear that at least some of these hacks would not work on more recent releases because of changes in the Android security mechanisms. So I would probably have to learn new ways, which is bad because I'm lazy ... 🙂 LOS 16 has a nicely-integrated and low-profile root-management solution

Wow, that's great news. 😀 Maybe I've become jaded over the years but I was expecting delays until the end of the year. Kudos to FxTec for making steady progress and keeping up the communication. The keyboard backlight video looked interesting, hopefully the light will be more evenly spread across the keys than the bright spots we get currently.

I got a response from Fxtec on my support ticket: Hopefully they do fix it for the Pro1, and not just the upcoming Pro1 X!

(lineage-18.1-20210816-nightly-pro1-signed.zip on August 5 security patch installed smoothly using adb sideload and Open_Gapps-arm64-11-pico-20210712) ...But the reintroduced Accessibility / keyboard bug is not (yet) fixed, see above. Did not try to do a factory reset first...

Sorry, I do not know anything about that. I am no Android power-user, I just want the OS to run the few apps I need to make it through the day. LOS 16 fulfils that requirement. I compile the upstream LOS 16 sources following the instructions in the LineageOS wiki. The only modification I do locally is to enable AGPS.

The 20200825 IS the newest. On the things not working after restore my guess would also be on opengapps/mindthegapps. They are quite different, see this I tried to combine. Did yo actively exclude all Gapps from the restore? If not I would try that.

In Lineage 16.0, that key combination (Yellow Arrow + Alt) brings up an emoji selector box. Works in all apps I have tested.

fastboot is extremely picky about the USB connection. Try different ports and cables. If you are on Windows some missing USB driver required by fastboot (but not by adb) could also be the issue (source). I have no Windows so I can't help much with that. I have found a Raspberry Pi (3) to be the most stable solution for flashing my Pro1. It never had any connection issues (as opposed to my PCs) and adb and fastboot are trivial to install using the Raspbian package management.

Also have that problem, especially it shows when phone is more than 10 days of uptime. Lineage 18.1.

Oh dear, how I hate the locked phone world... Thanks a lot for all the information, it will maybe not replace my laptop, but I will at least have a nice degoogled phone ^^ I looked for the astro slide too but the lack of linux support got me off (no support to Ubuntu Touch or Mobian, just a mention of linux). Hope that the pro1x will be worth!

The location has changed, the teardown guide is now here: https://github.com/imax9000/fxtec-pro1-teardown

"Mainline" refers to using the upstream Linux kernel with open-source drivers. That's what I think Mobian does. To this date (and to my knowledge), there is no OS for the Pro1 that uses upstream Linux. All available systems use the vendor-supplied Linux kernel of Android 9 ("4.4.153-perf+") with the proprietary (and closed-source) device drivers. That includes UbuntuTouch and SailfishOS! The latter actually run a slimmed-down version of Android 9 in a container and access the hardware via Android compatibility layers (libhybris). I suspect the situation will be quite similar for the Pro1

It seems like the best shot at it getting to work is if FxTec can do something similar to what @peter.s.fidelman described UniHertz did with AT&T to get the Pro1(X) whitelisted - I have no idea what it takes to do so (AFAIK it is not as easy to swap the IMEI on th Pro1, so most likely it would be to get existing IMEI-ranges whitelisted), but let us tag @Waxberry and @Erik and see if one of them can perform some magic here 🙂

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

Its rooted with magisk. I just updated to16 Aug release of Linage OS and still have this issue. I would like to help fix it but how do I get debug into to the right person. I killed all running apps and still have the issue. Also even with say 70% left it still does not charge until a reboot.

Does anyone else have issues where the screen doesn't turn on for an incoming phone call? It's only happened a handful of times so far but all but once I've had to restart the phone by holding the power key for 10s to recover from this.

So support FINALLY replied to me after sending 3 emails and a tweet, now my screen has been further pushed out to October. Think I'm about to just give up on this phone and move my Moto One Hyper as the primary. And the screen isn't the only thing that's bugging me now, I recently found out that my reception problems was the phone itself. I couldn't sustain a phone call properly in my room, but when I put my SIM into the Moto, it conducted phone calls perfectly fine even with just the 1 bar of signal.