Leaderboard

Lineage-22.2-20250825-NIGHTLY-pro1x with Aug 1st (Finally!) security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

I wish I had an answer for you for what is going on. I have no idea on how the legal construction/status is, and if any assets are left at all. The fxtec site has for long just redirected to some 'placeholder'-page, but some deep links (including this community) is still kept alive (AFAIK). I have no idea who is paying for them staying alive. I'm not sure if it was this thread or another, but a year or two back, some dug up info on the company from some official British site, and the company was still alive back then.

...i have i mean 2 flex spare cables and 2 small pcbs from top part - pcb between flex and display/camera/earpiece. I have repaired some fx and mainly not working display was not problem by flex but by pcb on top. Was needed to resolder flex connectors.

The only means of upgrading Android on the Pro1x is to flash Lineage OS, an ASOP-based alternative. The current official version is Lineage 22.2, which is AOSP Android 15. https://download.lineageos.org/devices/pro1x/builds https://wiki.lineageos.org/devices/pro1x/install/ https://community.fxtec.com/topic/4223-lineageos-22x-official-release-for-pro1-x-qx1050/

Lineage-22.2-20250811-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. I want to note that even though my Pro1x has working phone stuff, it has never demonstrated the battery drain problem on 22.2.

Spotted a more important bug that could be related with the battery waste as we discussed earlier. With the same sim in the same phone at the same location, and set for LTE only, here VoLTE works just fine on 22.1, but not at all on 22.2. So 22.2 CERTAINLY introduced some important bug in handling of carriers and bands (the sim is TDC in Denmark).

Due to the changes @Hook reported here, I tried upgrading to 22.2 (again). Will edit this post in some hours with the result.... ADD: And it is completely USELESS!!! Went from 97% to 47% in short of 8 hours. (Idle overnight, as much as possible uninstalled/disabled,,,,) Will go back to 22.1, or maybe stock and just forget about LineageOS, that (like the AICP project) seems to have F.. itself up to a useless state... Went back to 22.1, though over four months old still much newer than Android 9 in stock....,

I don't have any objective way of testing this, but I noticed that the change log for the last update and this one included references to carrier stuff. It seems to me that my phone call clarity has improved. The phone stuff actually worked pretty good for me from the get go. It wasn't perfect but far better than many people were reporting. But it seems, though anecdotal, that it has improved. Unfortunately, I don't really use this phone as a phone, as ironic as that it is for one that mostly works. So I haven't tried in a very long time, which makes this anecdotal report even more suspici

Lineage-22.2-20250804-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250728-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250818-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. A little slow on getting the Aug security patch.

Hello, Soo today i have tested today touch fix on new display from ali. Method with goodix app does not work on los22...all was fine...selinux set, read data from display was working too, but after flashing new firmware phone makes reboot and nothing - still same. But method - flashing stock rom without wipe, wait for boot and then flash back los22 works fine 🙂 ...only reinstal magisk was needed

I've uploaded the latest build of LineageOS 16.0 (for OG Pro1 / qx1000) to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The ROM dated 20250723 contains a WebView updated to chromium 138.0.7204.63. As Google did not publish any ASBs for July 2025, there are no further changes with respect to last month's build. I decided to still bump the security string to "1 July 2025" to reflect the fact that the system browser was updated. As usual, you can get an idea of the full list of changes with respect to the last official LOS16 from the patch tarball also available