claude0001

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

Nope, it isn't. My Pro1s (still on LineageOS 16 and located in Germany) generally indicate "LTE" or "LTE+", which are different variants of the LTE protocol. In areas where network coverage is bad, my phones drop to "EDGE" (2G, still available in Germany). You are supposed to be able to somewhat influence the protocol switching behaviour using the "Preferred network type" system setting, but I've never seen much effect while playing with this. For practical purposes, "4G", "LTE", and "LTE+" are pretty much equivalent, and indicate the Pro1 is operating at the fastest protocol family it

@Rob. S. is absolutely right. QA with F(x)tec phones - especially with the Pro1X - is practically non-existent and you may always end up with a device that has issues in core functionality. And even the "best" specimens come with shortcomings you would never accept from a major manufacturer. Unless you really want that hardware keyboard, you should avoid the Pro1 and even more the Pro1X.

Hi @drcp, @Hook has written down all the essential information already. I just want to add that, while the black spots in the corners are standard for these screens, they do not worsen over time. I own three Pro1 and one Pro1-X: All have the black corners to some degree, but even for the oldest device they have been stable over time. Concerning QWERTZ vs. QWERTY: F(x)tec lost many QWERTY devices to unauthorized grey marketing by their Chinese logistics partner company, which is likely the reason they ran out while shipping to backers. If you are really unhappy with the keyboard

Camera functionality seems to be important to @mangled. The device pages for Pro1 and Pro1X still state camera stack to be unstable and video recording not to work at all. So I guess the question is whether this information is up to date. Beyond that, here as well as on discord, users reported many more issues related to things fundamental to daily phone use, like mobile connectivity, battery life, and stability of core apps. Those problems are not mentioned at all on the project page, which lists the Pro1 and Pro1X as "officially supported". A brief, but honest, report about how us