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

This. That's precisely why I gave up on all those alternative OSes that are said to be more "Linux-like" than Android but, actually, are just AOSP piggybacking another UI via libhybris. Like you, I settled early for a combination of (Google-free) LineageOS and a chrooted Debian Linux install, giving me native access to the huge Android ecosystem of apps. Unfortunately, the latter is just necessary nowadays. On the bright side, I can cover almost all my needs with FLOSS Android apps. Installing some alt OS that claims to be "real Linux" but, actually, runs on a containerized vers

Back in the days, Canonical wanted people to believe Ubuntu Touch was the Ubuntu GNU/Linux distribution for PCs, just repackaged for their mobile phones. Of course UBTouch is nothing even close to that. Fun fact, it does not even use a Ubuntu Linux kernel! It runs on the same Android kernel and proprietary drivers than Stock, interfacing them using middleware layers. The latter, however, can be used only by specific "native" UBTouch apps, not by your random favourite software from the full Ubuntu distribution. You can run Linux Firefox or Thunderbird on UBTouch just like you can on A

Yep, think so too, see above.

Have you performed the steps listed in section "Repair sensors/ folder in persist.img" of this post: I understand those steps are necessary after flashing back to stock from UBTouch. Note that you need to root the device. Also, please note that I never tried Ubuntu on the Pro1X, so I never had to do this procedure myself. Just trying to point you into what I think is the right direction ...

Newest unofficial LineageOS16.0 (for SD835 Pro1) is available. At https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 get the ROM dated 20241116. Changes since last month: Backported security fixes up to the "1 November 2024" ASB. Update system webview and browser to Chromium 130.0.6723.73. Have fun.

Note that the GNU/Devuan system is not part of the ROM as offered for download above. You'll have to set that up yourself. That being said, I still use that same Debian/Devuan setup I once described in this thread: It does not rely on Termux or any similar App-based solution. Rather, it runs in a native (rooted) chroot of LineageOS and starts in parallel to that upon boot. This is done via a Userinit script which you can download from that other post above for reference. All this relies on the native AddonSU root-management solution of LOS16, though you can certainly achieve the sam

AFAIK, the advantage of the CTIA standard is greater backwards compatibility. A CTIA headset can be plugged into a traditional (3-contact) stereo-jack socket and still work as an output-only stereo-headphone set (without mic function, obviously). If an OMTP headset is plugged into such a socket, even the earphone function could not work, as there might be no connection of the speakers to common ground (the common ground of the socket contacts the MIC ring instead of GND).

No glue between the screen frame and the baseplate. There is some holding the actual screen to the frame, but you won't have to touch that to test the connectors.

I was saying that even after you remove the screws, the screen will still cling to the base plate. Detaching it requires some prying tool to insert between the screen frame and the base plate.

The October build of LineageOS16.0 (for SD835 Pro1) is available. Head to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 and get the ROM dated 20241017. Changes since last month: Backported security fixes up to the October 2024 ASB. Update of the bundled System WebView and browser to Chromium 129.0.6668.70 (from LOS21). Have a lot of fun!