Leaderboard
Popular Content
Showing content with the highest reputation since 06/05/2025 in Posts
-
I've seen a few posts raising concerns about how much longer this community forum will be available. It seems F(x)tec is still in business, working on the Clicks keyboard case and other projects, but I don't know if there's a future for the Pro1 line. I've gained a lot of useful information from here, so as a precaution, I saved an offline copy of the forum over the weekend. Specifically, the command I used to mirror the forum was: wget -E -k -m -np -p https://community.fxtec.com The archive is about 17 GB in total. Compressed as .tar.gz, it shrinks to about 2.3 GB, which I think i5 points
-
Try this. The download links seem to work (I am not knowledgable on any of this)... https://web.archive.org/web/20200406195436/http://files.nwwn.com/android/pro1/factory.html4 points
-
One more update, with apologies for the triple-post. I received a secondhand original Pro1 in the mail from the indefatigable @Hook. Using the official flashing guide from this thread, I updated the Pro1 to firmware 20200825 and re-ran the initial setup process (including a one-time factory reset). The Pro1 was confirmed to be working normally. However, when I unplugged the original Pro1 screen frame and plugged in my Pro1 X screen frame (with the replacement Elephone screen attached), the Pro1 immediately entered a boot loop. I then went back to the guide and reflashed all the firmw4 points
-
Sorry for the late reply but I do have a copy if your still interested. This is the qfpkg_linux.zip, not sure if there were any others. qfpkg_linux.zip4 points
-
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 needed4 points
-
The point is that the updates are not incremental. The weekly OTAs each time contain the full ROM, even if changes relative to the previous one are minor or non-existing. The idea behind the a/b partitioning scheme is to keep the previous version of the system intact for backup, while flashing a completely new version of the OS to the respective other slot with every update. This is to make sure one of the slots always contains a working OS, even in case of a bad flash or faulty download.4 points
-
Lineage-22.2-20250623-NIGHTLY-pro1x with June 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. Definitely not a big update. Downloaded and installed very quickly.4 points
-
Lineage-22.2-20250616-NIGHTLY-pro1x with June 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.4 points
-
Lineage-22.2-20250609-NIGHTLY-pro1x with June 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.4 points
-
Lineage 23.0 (Android 16) has been released for the Pro1X. I haven't yet had time to install it bbut will either tonight or tomorrow morning, if you want to let me be the guinea Pig. 😉 https://download.lineageos.org/devices/pro1x/builds https://wiki.lineageos.org/devices/pro1x/upgrade/ https://wiki.lineageos.org/gapps/3 points
-
Here is it for you 🙂 https://drive.google.com/file/d/1HxTmm2_oW65ijT2Ewf7pCh4qjF_JKHkK/view?usp=sharing3 points
-
3 points
-
So, I tried doing LOS 23.2 (the Feb 9th update) as if it were a new install with were a new install, doing a factory reset and all. It just made things worse,,, I got the same symptom of it only booting to bootloader, but worse because I finally could not get back to LOS 23.0 and, of course, I couldn't reinstall 23.0 because that was viewed but the system as a downgrade. So on a whim, I decided to try something. I did the whole thing over again (including factory reset-- nothing to lose at this point), but this time I didn't flash Magisk. Boom, Everything worked. I was also able to up3 points
-
Warning! ⚠️ Tried to update to Lineage-23.2-20260209-NIGHTLY-pro1x (notice we have jumped from 23.0 to 23.2). It reboots to the bootloader menu. It won't reboot to system and if you go to Recovery, rebooting to recovery does not change the slot. However, doing a shutdown, booting the phone (you still end up in bootloader menu), going to Recovery and doing a System reboot finally boots the older Lineage 23.0 (Future reboots are fine) with 23.2 in the updater labeleed as needing installing. This problem has been reported in the their Github for two other devices with people having tri3 points
-
3 points
-
F(x)tec never had all the driver sources. And even if they did, they would not have been allowed to publish them. A prominent exception is the keyboard, which is the one hardware component they developed themselves. The rest of the hard- and software came from a Chinese OEM. The idea that f(x)tec ever wanted to make the Pro1/Pro1X "open" phones is a misconception introduced by some media and bloggers. F(x)tec never publicly corrected that misunderstanding, presumably as they hoped to profit from all that "Linux-phone" hype. In reality, the Pro1 was designed as a pretty standard, proprieta3 points
-
Lineage-23.0-20251027-NIGHTLY-pro1x with October 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.3 points
-
Lineage-23.0-20251020-NIGHTLY-pro1x with October 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.3 points
-
Lineage-23.0-20251013-NIGHTLY-pro1x with October 1st security patch installed smoothly using the Lineage upgrade procedure linked in the OP. It was installed with MindtheGapps 16 and Magisk 29 installed as a zip for SU only. all data was preserved in the upgrade. I did have to open the Magisk app to let it run an update, but root was established. All went according to plan and everything seems to be working so far.3 points
-
Lineage-22.2-20251006-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250929-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
New build of LineageOS 16.0 for qx1000 (OG Pro1) available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1. Go for the ROM dated "20250926". Changes since last upload: Backported ASB security fixes up to September 2025. Have fun!3 points
-
Lineage-22.2-20250922-NIGHTLY-pro1x with September 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250915-NIGHTLY-pro1x with Aug 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250908-NIGHTLY-pro1x with Aug 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250825-NIGHTLY-pro1x with Aug 1st (Finally!) security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250728-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
HI, the Lineage Juli Update maybe improved the battery drainage a little bit. Instead of going down from 100% to 30% during the night (meaning, the Pro1 was at standby and "Do not disturb" was activated) my Pro1 was emptying the battery to only 50%. Slight improvement, but still to much to use it during the day at work and so on. Last night I had "Airplane Mode" on and Wifi on too. VoLTE (4G-Anrufe in the phone localized to a German UI) was on. The battery was going down from 100% to 93%. This is approximately, what I had in the past before the update of Lineage to version 22.2. I3 points
-
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 available3 points
-
Lineage-22.2-20250721-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250707-NIGHTLY-pro1x with June 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-22.2-20250630-NIGHTLY-pro1x with June 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Sadly I highly doubt that more will ever be produced, nor that they have any left to send out. Though they in theory might make a new one I highly doubt it will ever happen - frankly I'm positively surprised that this community site is still kept alive.3 points
-
The latest build of LineageOS 16.0 for OG Pro1 (qx1000) is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The ROM dated 20250625 gives you: Backported AOSP security fixes up to the June 2025 ASB. A system Webview and browser updated to version 137.0.7151.72. Have a lot of fun.3 points
-
Sorry, running a little bit behind this week... 😉 Lineage-22.2-20250602-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.3 points
-
Lineage-23.2-20260518-NIGHTLY-pro1x with May 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes2 points
-
Lineage-23.2-20260511-NIGHTLY-pro1x with May 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes2 points
-
You mean GAPPS for LineageOS 21.0? Then...this one: https://github.com/MindTheGapps/14.0.0-arm64/releases/tag/MindTheGapps-14.0.0-arm64-20250203_2000512 points
-
Yes, I have some boot.img. One moment... Link: https://limewire.com/d/12R72#U1UK7JaNiG2 points
-
Lineage-23.2-20260302-NIGHTLY-pro1x with February 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Changelog: https://download.lineageos.org/devices/pro1x/changes2 points
-
Lineage-23.0-20260105-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained.2 points
-
Thank you very much for all of your effort. I'd be interested in giving it a try myself. I'll send a DM.2 points
-
Lineage-23.0-20251222-NIGHTLY-pro1x with December 1st security patch installed smoothly via OTA. MindTheGapps16, and root was maintained. Again, to be clear, when I say "root was maintained" I mean that after OTA, and without reflashinng Magisk or opening the app, I still had root on my phone.2 points
-
I think that for an OS like Lineage, which is supposed to be just Android-without-the-Google-bits, upgrading the major Kernel version will be next to impossible. The proprietary vendor blobs compiled for 4.4. will not load with 4.14 or later. That's just not how Linux works. Yes, there may be some other ms8998 devices out there using later Android kernels. So it may boot somehow. But what's the good of that if your LTE-modem, camera, and touchscreen no longer work?2 points
-
Lineage 23.0 (Android 16) is out for the Pro1x. This conversation continues here:2 points
-
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.2 points
-
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 suspici2 points
-
If you get the 8GB number, factory reset. I believe that corrects the problem. It happens from time to time, but not often, as I recall. It's always a good idea to check after flashing.2 points
-
It is highly advised to take a backup of your device specific partitions right after you receive the device. Update 20220829: tl:dr: Community has not found a safe way to restore backups as of yet. Making below described backups is still highly advised for a future where some wizard found a reliable way to restore those backups. For now, if you have broken sensors from flashing another OS, the restorecon method described in the "Repair sensors/ folder..." section does 100% work to fix those while retaining your attestation keys. While restoring any backup has a high chance to make the keys2 points
-
Perhaps.... here: https://b4.timschumi.net/lineage-archive/lineage-22.1-20250407-nightly-pro1x-signed.zip (not the last, but one of the 22.1 versions) That´s the main page of this archive: https://lineage-archive.timschumi.net/#pro1x2 points
