Leaderboard

There seems to be some TWRP ... see https://community.fxtec.com/topic/3005-ubuntu-touch-os-for-fxtec-pro1/ ... Preparation: TWRP for Pro1: Download here https://drive.google.com/open?id=1IgUjxEKV5MU_3cRkNCyGc-YpRkUQ3xHh (Credit to Mccreary) ... Thanks for for the steps/listing! I was on LineageOS 16 (Android9) and had to activate USB debugging via --> Settings --> About Phone (scroll down to last option) --> Build number (scroll down to last option) and tap on "Build number" multiple times --> until notifcation for "developer options are enabled" -->

I thought I was pretty focused on setting up my phone the way I wanted. But I can only bow to such determination in the quest. 😄 Sorry it did not work out for you. But thanks a lot for sharing your experience with twrp with those who will follow you. I'll keep using my third-party QR scanning App on Lineage 16 because ... I am a coward. Respect. (I'm not joking!)

Thanks a lot! That sucks a lot 😕

Normally you could make a twrp backup, upgrade and rollback if things are not as expected... but we still don't have twrp for pro1/lineage, do we? (the last time I checked it was only for sailfish)

OK, look guys, my post was a reaction to @daniel.schaaaf, who I think is fundamentally right in his criticism of some aspects of today's open-source software culture. I tried to provide some examples how us so-called "power users" are simply more affected by major OS upgrades, and are hence left in the rain if Lineage versions are abandoned at every second stop. True. But neither can we change FxTec ways of public communication, IGG policies, or EOLs of QualComm product lines (to name but a few). Did that stop anyone from whining and complaining here? Now it is my turn. 😉 Self-bu

Of all the days to release the first official 18.1 build, they chose this one.

Yes, indeed! Thank you very much! I just hope the problem with international characters 18.1 obviously has can somehow be either solved or worked around; until then, I have to stay at 17.1...

Yes, but – if I understood this correctly – as it is missing a device specific key which they would need to get from the manufacturer, something which only is being attempted when a device-specific TWRP is really 'done' and fine to get the 'official' status, it won't decrypt data and therefore is useless for backups, unfortunately.

How long will there be updates for LOS 17.1? 18.1 still has a bunch of bugs for me, so I am considering a downgrade. But somewhere I read that LOS doesn't retrieve updates for old versions. Is there any policy on that?

The case in black.

I could not agree more. What you describe is the reason I am staying on LOS 16. I have plenty of hacks in place, where I cannot predict whether they would still work on LOS 18.1 (or 17.1, for what matters). I use several autostart scripts in /data/local/userinit.d/ for setting up stuff on boot automatically. Those scripts are officially unsupported already in LOS 16, but can be made to work using some third-party apps. Will those still work with LOS 18.1? Obviously, all of those autorun scripts require root access. Will those early-executed shell scripts work with (third-party) Mag

If you just want to run a few Linux programs, something like Termux and AnLinux is definitely the easiest way to start. I have never used those Apps, though, so I cannot help with specific questions about them. For advanced stuff, like the above, a "hand-made" chroot (with root access to Android/Lineage) will probably always be superior to (non-root) in-App solutions. Setting up your own Linux chroot on Android is actually not that hard provided you have some experience with Linux. The real problem is that the required information is scattered all over the internet. Also, some things

As I wrote above, 17.1 no longer has the Pro1 as build target, so there will be no more (official) updates for it. See https://www.lineageoslog.com/17.1/pro1 ... and that is exactly why the older, stable versions should keep building, at least on monthly basis so they keep receiving the upstream security fixes in AOSP. Every upgrade that changes APIs or other major parts of an OS is potentially disruptive for the already-installed base. That is why professional distributions keep their "stable" branches alive as long as upstream fixes can be picked-up with reasonable effort.

I went form unofficial to official and used NikGapps Omni instead of MtG. adb reboot bootloader fastboot flash boot lineage-18.1-20210401-recovery-pro1.img reboot to recovery adb sideload lineage-18.1-20210401-nightly-pro1-signed.zip reboot to recovery adb sideload NikGapps-omni-arm64-11-20210324-signed.zip And if you get stuck in a bootloop, try flashing the OS to slot_b and NG/ MtG again to slot_a. Mind you, I went from official 17.1 to unofficial 18.1 without any problems. So the above should also work for 17.1 to 18.1 official.

Update: I can now run the X.org X11 server inside my Devuan chroot. Yes, the real thing, not TigerVNC or TightVNC. The nice thing with X.org is that I can use it with xorgxrdp in the chroot and connect to my Linux distro via a much better-performing (native) RDP connection as compared to using VNC as backend for XRDP. I still use the Microsoft Remote Desktop 8 App combined with the default xrdp-0.9.9 shipping with Devuan 3/Debian 10. As far as I can see, one can find no information on how to do this on the internet. Either it is really tricky and I am a genius, or no one cares about

No updates... 😥 As soon as they switch they forget about supporting the stable version.... 🤐 See this: https://www.lineageoslog.com/17.1/pro1 from this by @claude0001

It'll likely get worse from this point onwards. I'm not seeing that many vendors on Taobao selling replacement screens for Elephone U Pro (same LCD used by the Pro 1), so it could mean it's a discontinued part.

So the ghosting got worse again, I decided to do another re-seat. One thing I noticed this time was that the screw holding down the LCD cable assembly next to the earpiece basically fell out. I've screwed it back in now and tightened it down, wonder if that was a contributing factor as well. Let's see how long this fix will last, FXtec quoted me 1 month for the replacement display to be shipped. EDIT: Nope, didn't help at all.