claude0001

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, proprieta

The base kernel source is of course available as per the GPL2. Also, e.g., the keyboard-driver source is available as part of LineageOS. However, much of the device drivers that make up basic mobile-phone functionality are not. The project of mainlining the Pro1 got stuck on such profane things like the touchscreen driver requiring some non-disclosed firmware magic to be usable in the first place. Device drivers not being open-sourced is pretty standard in the Android world, though. Nothing specific to the Pro1 here. 👎

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?

Not using it myself on the Pro1X. But most SFOS users (well, still quite few actually) are on discord. I send you an invite link via pm. Be reminded that whatever technically did not work on Android/Lineage with your Pro1X will also not work in SFOS. Under the hood, it is the same core OS, after all. There will be additional technical limitations with respect to Android, because not every function is available from SFOS userspace. E.g., as far as I know, VoLTE does not work with SFOS on Pro1/X, while it does in Lineage.

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!

I would try to flash only the (unpatched) boot.img with fastboot: fastboot flash boot boot.img The original boot.img can be extracted from an ota.zip, either manually or by using free tools like these. While this should preserve your data, it's obviously recommended to backup your stuff first. Applies to any kind of flashing job, actually.

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