Leaderboard

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.

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. I

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

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

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

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.

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

If on stock, use FinQwerty by @Anssi Hannula you can find it in the normal android market. to handle 1 and 7. (It really is not a running app as such, but presents the right configuration files for the wanted layouts to system on boot, so we an choose them side be side with the normal ones) PS Dansk og norsk layout er 99.9% identisk, Æ <-> Ø.

Hi everybody, I just wanted to mention here, that I am one of the Pro1 users, who is effected by the battery drainage of the Pro1 after the update of the device to Lineage 22.2. For me, this is really a mess, because I used the Pro1 as my so called "daily driver" for the past 2,5 years. 😢 Like TeZtdevice, I also assume, that it will take me too many hours to downgrade the Pro1 to a previous Lineage version. Unfortunately, I will not have the necessary time for this task before September. To "survive" until September, I reactivated an old Samsung A10. ☹️ I cross

Had 3 available updates and started from the oldest. Then figured that could update from the most recent one

Update on the battery, it seems the radio is to blame, and changing the network type seems to help. This night the phone was on my nightstand and over the course of 6 hours went from 100 to 34%. Network was set to LTE/TDSCDMA/CDMA/EVDO/GSM/WCDMA. Looking at battery usage over system showed the radio as the big culprit. (See image). I've set it before to LTE/TDSCDMA/GSM which seems to work for my local cell network, and battery life seemed to be good, however sometimes the phone would hang while on standby and I changed the network type hoping this would not happen. It didn't happen but th

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.

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/#pro1x

I received the phone (Pro1x) in one of the first batches and I did order it from the website. It might have been due to some (lucky for me 😉 ) confusion at FxTec, because I alse made an IndieGoGo order of the spare battery (and never received it), thus I was _also_ an IndieGoGo contributor (who paid more for the phone due to higher price on the website - as a compensation for a supposedly lower risk of paying but not receiving anything - cough, cough - and yet even more due to additional money paid for a never delivered spare battery).

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.

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

I will test it tonight with VoLTE off.

Just to be clear, I wasn't suggesting not using a Pro 1 as a phone should be a solution for anyone. However, my defect led me to a diagnosis of the possible problem with Airplane Mode being a test. 🙂 I'm just lucky my problem doesn't affect me much because I happen to be weird.

Yes, my VoLTE was ON.

Really weird. OH just retested. VoLTE by this carrier now works! (TEST: selecting LTE as only band, restart, and do a call). Does yours (clam to) do VoLTE? It could be interesting to turn it OFF/ON. If it for some odd reason relates to the battery bug. @TeZtdevice do you have VoLTE ON or OFF?

Except that, after maybe the first half of 2020, I have never used it as a phone. Same with my Pro1x although, in fact, my Pro1x actually works pretty well as a phone. They are pocket computers for me. I'm retired and don't do a lot of phoning, Mostly the phoning I do is related to my home health care of Mrs. Hook and I use a Pixel 7 Pro on Verizon for that as I need great coverage and reliability for that. 🙂 Other than that, I don't even give most people my phone number. I prefer asynchronous communication.

Sorry for the "delayed" answer. I didn't activate notifications. Therefore I did not realize your question earlier. I activated notifications now. My Pro1 was on the June release of Lineage. I just updated to the July release. I will report the effect of the update on the energy consumption in a few days. Just for information: I use the MicroG version of Lineage: lineage-22.2-20250719-microG-pro1 (https://lineage.microg.org/ and https://download.lineage.microg.org/pro1/). There are no GAPPS installed on my Pro1 and I have even removed most of the Google stuff that was in the ROM.

Are you still on stock Android, or have you updated to LineageOS? I recall the problem with Chrome refreshing the page from the fingerprint sensor was present in the stock Android, but fixed in LOS. IIRC, the work around was to switch to Firefox, if you don't switch to LOS. Some of your other issues might work better with LOS, too. No real downside to it, except for the time it takes to set it up.

Remember, the updates are not just what is being added... they are the whole package with the updates integrated. (They don't disturb your settings and data).

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

I do not think I done a stock flash, that did NOT have this memory issue, so would strongly suggest to either always do the reset, or at the least make a check, part of the installation procedure

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 keys

Yesterday when I wanted to switch from LineageOS 22.2 to 22.1, I foolishly performed a factory reset/data wipe on LineageOS22.2 Recovery before removing the Google account I had logged on to on 22.2 with MindTheGapps. Now, if I flash MindTheGapps, I cannot login to my google account on the phone -- it fails. I can use the phone if I flash an OS without GMS. But then I cannot st the PIN/screen-lock. I suppose something is amiss on the persist partition? I do have the backup which I took before logging in to Google. Is there still no trustworthy method for flashing the persist bac

I have managed to find a recovery for the "microG" flavour of LineageOS 22.1 and that has allowed me to flash 22.1. For future reference if anyone needs, I downloaded it here from microG's website. The archived image from timschumi as pointed out by @TeZtdevice worked perfectly. I have just booted into 22.1 and will check battery life and usability in the next couple of days. Thanks for all the help! EDIT: Daaaargh! I forgot to remove my google account from the phone when I was on 22.2. Now I can't re-login on the phone on 22.1! Had to reflash LOS without MindTheGapp

FYI: 22.1-20250407 is the last build of 22.1 https://web.archive.org/web/20250504214754/https://download.lineageos.org/devices/pro1x/builds ...but I don´t find the other img´s, Sorry.

I was on full stock. Still couldn't make it work. After bashing my head a lot, I found the answer. Here's what I had missed:

try restoring back to stock android and repeat the process?

Well it depends a bit on what you mean. Originally yes,, I for one bought a Pro1 ages back, and got it in 2019. but I have no idea when a weborder was last sent out,

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

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.

Lineage-22.2-20250526-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250519-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250512-NIGHTLY-pro1x with May 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

USUALLY the problems people experiences with fastboot is related to the communication with the watch. Either cable, port or driver. Silly as it may sound on Windows11, a 'newer' USB3 port might cause problems. On my Lenovo X1 Yoga gen 6 (20XY), I can not get fastboot to work directly. But if I use an old usb2 hub, things works fine. It also works fine if I go via my thunderbolt 4 docking, and a USB3 port on that. AFAIK, there are fewer issues if the machine is on LINUX. You might also try from an old PC with USB2 ports only. Usually it is not super picky on the cable, but try sw

Lineage-22.2-20250505-NIGHTLY-pro1x with April 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250428-NIGHTLY-pro1x with April 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. I think the April 1st dates in previous posts was a typo I kept perpetuating. Lol. So far well behaved, battery-wise. Lost 3% in 2 hours including activity post-update. Edit: Looks good. 7 hours, yes, mostly idle, but has only dropped 10%. That's par for the course given that I have background mail, dropbox ans calander syncing.

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

never. we all start somewhere. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ I can't provide much better steps than what is already in the OP. I guess start here: backup persist. try adb method first. requires unlocked and a recovery boot if above doesn't work, install EDL (see readme and OP) edl r persist persist_backup.img edl r modemst2 modemst2_backup.img edl r modemst1 modemst1_backup.img edl r fsc fsc_backup.img edl r fsg fsg_backup.img flash your OS of choice:

Finally, this issue has been fixed by restoring backup files. I need pass '--memory=ufs' for each command $ ./edl w persist ./persist_backup.img --memory=ufs $ sleep 3 $ ./edl w modemst2 ./modemst2_backup.img --memory=ufs $ sleep 3 $ ./edl w modemst1 ./modemst1_backup.img --memory=ufs $ sleep 3 $ ./edl w fsc ./fsc_backup.img --memory=ufs $ sleep 3 $ ./edl w fsg ./fsg_backup.img --memory=ufs $ sleep 3 Here is link for my backup files if you need them: https://github.com/steward-fu/pro1x/releases/tag/v1.0 Thanks

I found a way to backup partitions that also works for windows, with just the usual ADB on the PC. HOWEVER this ONLY works for an unlocked device. ADD: The below only works on Linieage/AICP not stock android, see also this If not unlocked - unlock wiping data, or look for another method.... Make sure that your phone is in developer mode [*], and allows adb to connect as root (the phone does NOT need to be rooted) Connect cable and run (first time you must accept the connection from the pc) adb root adb shell find /dev/block/platform -name "by-name" -exec ls -al {}

Thank you for this thread (i added a link here)

I wouldn't be too bothered to bring a dock, keyboard (which is already tiny) and all, as it would replace my 1.5 kg laptop in my backpack (plus I don't need a mouse if I have a touchpad/tactile screen). The display would be my main concern. But to be honest, when I need a screen to work more seriously I will certainly have one to connect too (friend's house tv, university, work...). The pro x1 would also be more powerful than my laptop at least in term of ram (I don't know how amd64 and arm ships can compare), which was already enough for me. I don't really want an "ecosystem". I usual

I too was a die-hard fan of the N900. 🙂 I am quite happy with my hybrid Lineage+Devuan system now, which provides almost everything my N900 could do, but you are right that there are limits (HW accelerated graphics, transparent FS access, ...) because of Android concepts standing in the way. Note that UbuntuTouch comes with very similar limitations: It too is designed primarily as a phone OS and copys some of Andoid's concepts. E.g. apps are individually sandboxed, native "phone" apps and "desktop" Ubuntu software live in separate worlds, the latter running in libertine containers wi

Right, Pro1 can be very handy to do real things like logging into a server and do what is necessary, which is very frustrating on any touch keyboards. However, the one and only real and well-working Linux phone I used so far which also had a keyboard was N900. Although Pro1-X will also come with Ubports, so some kind of a Linux ecosystem will exist, nowadays one have to have an Android phone because of other services, and as it is a very restricted system, it seems for me the very same well-working environment what N900 had is not working anymore if you don't want to bring another de

Yes and no. The Pro1 (and, by extrapolation, the future Pro1-X) can be set up as a quite OK always-carry-on GNU/Linux computer. I achieved that using rooted LineageOS + a custom-made Devuan chroot (see this thread for an entry point). Similar results can certainly be obtained using stock Android combined with a solution like Termux if you do not want to root, especially if a Un*x CLI is everything you really need. In fact, if you ordered your Pro1-X with UbuntuTouch you may (hopefully) be good to go pretty much out-of-the-box. None of these solutions breaks the "phone" functions in any wa