claude0001

You are saying your Pro1 ceased to work as a phone. This is no minor regression for such a device.

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

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.

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.

Sorry for answering so late, I do not check this thread very often any more. In Settings, navigate to Display -> Advanced -> Style and set Style to "Dark". Then, on the same page, set "Dark mode" from "Default" to "Black". Unfortunately, the default launcher and other system apps (contacts, phone, gallery, ...) are not yet prepared to pick up a dark system theme. This is Pie after all 🙂. You should be able to find suitable third-party substitutes in most cases, though.

It would be far easier to stay with lineage 21.0: That branch still gets patched with ASB fixes upstream, so all you'd have to do is fetch the source tree and make the build, which is piece of cake. Basically all you need is a Ubuntu virtual machine with enough storage and RAM. Because of the new QPR release scheme, staying with 22.1 is more complicated: Only the latest QPR (22.2 as of writing) is getting patched according to the ASB. 22.0 and 22.1 are not and I'm not sure if the available ASB patches for 22.2 could be directly applied to them. At least in the long run you'd probably have

Not that I have anything constructive to add, but in LineageOS's defence: They are stuck forever with the Linux kernel version and drivers that shipped with the original Android 9 OS. As the divide between increasingly modern Lineage/Android userland and the base Linux OS amplifies, bugs like this become more and more likely, unfortunately.

I've uploaded an updated build of LineageOS 16.0 for good-old qx1000 (SD835 Pro1) to: https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The ROM dated '20250528' contains backported ASB fixes up to patchlevel "1 May 2025". No other changes since last post. Have fun.

I think many (most?) of those who had ordered an OG (qx1000) Pro1 via the website and were "upgraded" to a qx1050 after the SoC thing happened. At some point all the focus was on IGG backers, and website customers were left in the rain ...

An updated build of LineageOS 16.0 for OG Pro1 (qx1000) is available for download at: https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The build dated '20250504' gives you backported security fixes from the Android Security Bulletin up to the "1 April 2025" patchlevel, and updates the bundled WebView to Chromium 135.0.7049.100. Otherwise no changes with respect to last month's upload. Have fun.

Thanks. Yes I know that. But the doc linked above lists almost nothing for the new 22.2 branch (yet?), while there are quite specific instructions for 22.1, that's why I asked about that one. As I am routinely self-building, I feel confident to compile any of the officially-supported branches and thus think I do not depend on the pre-made ROMs from the LOS build farm. However, I hesitate to ditch one of my working installs just to find out that AVF has simply not been ported (or may not be possible at all) for the Pro1 ...

Has anyone tried running a GNU/Linux distro through AVF in recent versions of LineageOS? As can be seen from my signature, I am running old(er) versions of LOS on my Pro1(X)'s. The main reason for this is that I have relatively complex Linux-in-rooted-chroot setups in place, that are notoriously difficult to migrate to different Android releases. AVF introduced in Android 14 and 15 could be a game-changer for me as it - theoretically - enables official support of Linux-Distros in containers, potentially making my hand-made solutions obsolete. However, it is not clear to me if AV

Here's another one. The ROM dated '20250326', available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 gives you my latest unofficial build of LineageOS 16.0 for Pro1 (qx1000). To make the thread more accessible, I'll recapitulate the full list of enhancements with respect to official every few months. So here it comes: Backported AOSP fixes up to the "1 March 2025" ASB (official LOS 16.0 stopped updating in January 2022). Improved keyboard behaviour, partly backported from later LOS releases (code changes can be found in my local patch tarball).

I've just uploaded build '20250309' of LineageOS 16.0 for OG Pro1 (qx1000) to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Changes since last release: Backported fixes up to the "February 2025" Android Security Bulletin. Updated system WebView and browser to Chromium 133.0.6943.137. Have fun.

Thanks for the feedback. With my Pro1 still on LineageOS 16.0, this works. I can select multiple layouts under "Keyboard & input methods > Physical keyboard" and then cycle through them on the fly. Pretty cool, actually. I didn't know about this feature. However, on the Pro1 with LOS16, the hotkey for layout switching is Ctrl + Spacebar. Yellow arrow + Spacebar is equivalent to pressing the power button in my case, which is another pretty cool feature introduced by @tdm with his initial port of LOS.

OK. I just think: this sounds like a general regression in AOSP, as keyboard support in Android is generally nothing specific to the Pro1 (hence my question whether this is also observed in the Pro1-X port). I just wonder if it could be worthwhile to open a bug against LineageOS because of this.

I probably missed why you have been including this warning every week for quite some time. Is this problem unique to the Pro1 (as the corresponding qx1050 thread does not mention it)? Anyway, it seems I can find no open bug reported against LOS about this. So, whatever your issue is, I doubt it will ever be resolved "automatically" by an OTA.

Another unofficial build of LineageOS 16.0 (for qx1000) is here, celebrating 3 years of support beyond its AOSP EOL. 🥳 At https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the ROM dated 20250203. Changes since last release: Backported fixes up to the "1 January 2025" Android Security Bulletin. Updated system WebView and browser engine to Chromium 132.0.6834.122. Have fun.

The respective fix for the Pro1 is here: https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/318274 Note that this is specific to the qx1000.c keyboard driver in android_kernel_fxtec_msm8998, it won't be directly applicable to another device.

The only way of "upgrading" is installing LineageOS 22, which will give you the equivalent of Android 15. Since LIneageOS re-uses most of the device drivers from stock Android 9, it is unlikely that audio or camera quality will be improved. At least I do not know of any such updates. That being said, a recent LineageOS will give you all those Android security patches since 2020, which is of quite some value in itself ...

Congrats. 👍 I once documented my very similar procedure here: This was before the rubber-band trick was discovered, so I hadn't tested if that would have worked in my case. At the time, I also measured 0 V between the pins, but you are probably right, that the internal protection disconnects the cell below some critical value. My Pro1-X has been working fine since (though I do not use it much anymore).

This is ridiculous. I understand that F(x)tec are low on resources, but Let's Encrypt certificates are available for free! They literally would only need to run the 'certbot renew' command. I can only hope they will pass on the contents of this forum to the community in some way before the server goes down, otherwise all the (mostly unofficial) info on the Pro1/Pro1-X we have collected here will be lost ...

Slightly off-topic: My browser has been flagging this site as insecure for weeks. Could someone please just run 'certbot -renew' once? 🙄

The latest unofficial LineageOS 16.0 (for qx1000) is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the build dated 20250108. Changes since last month: Backported fixes up to the "1 December 2024" Android Security Bulletin. Updated system WebView and browser to Chromium 131.0.6778.200. Have fun.

Those are hardware issues, unfortunately. All recent releases of Lineage (including mine) have a workaround implemented in the keyboard driver that suppresses unwanted multiple keystrokes (https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/318274). For the undetected keypresses, there is unfortunately no software fix. I have three Pro1s. One (the oldest) has that issue to the point where the keyboard is almost unusable, the second has one or two keys that sometimes need two presses to react. Only my most recent device has a flawless keyboard. All three run t