claude0001

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!

While buying a miniature Phillips screw driver, make sure to also get some prying tool. Besides the screws, the display frame "clicks" onto the supporting base plate. Especially if it has never been removed before, fingernails are not enough to get it loose. You wont have to mess with the hinge mechanism by the way. However, be careful with the ribbon cable connecting the two halves of the phone: it is just long enough to allow you to reach the connector head. Once the display frame is unmounted (which is quite easy) you can check and re-seat the ribbon cables coming from the bottom ha

https://archlinux.org/packages/extra/x86_64/protobuf/ ?

I've been using a Raspberry Pi3 for all my Pro1(-X) flashing for years. Its rustic USB turned out to be 100% reliable for adb and fastboot. Plus installing the latter is just an "apt install" away in Raspberry Pi OS. This is in contrast to my (Debian) Linux-PCs that repeatedly had problems with fastboot connections to my Pro1s.

The latest build of LineageOS16.0 (for SD835 Pro1), dated 20240924, is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 (Kind of) full list of features: Backported security patches up to the September 2024 ASB. Improved keyboard behaviour (backported from later LOS releases) as documented in the local patch tarball. Several more improvements with respect to the upstream LOS 16 tree (GPS fix, touchscreen margin control, ...) as documented in that same patch tarball. Updated graphics driver stack (from LOS21). Update of the bund

We can't help if you don't disclose what is not working. The how-to on the Lineage wiki is a s complete as it gets. What is the first step that fails in your case? If you are using a Windows PC for flashing, it is likely that you need to install the Google OEM driver to get fastboot to work ...

Forget it. The Pro1-X camera cannot handle such light conditions. The Pro1's is better, but still takes a lot of patience and manual intervention (and a good camera app) with night shooting. The price tag comes from the mech keyboard. Full stop. Other than that they're mid- (Pro1) to low-class (Pro1-X) phones. The position of the spot on you screen is different from all I've seen before, though. Normally they are all in the corners of the display, and hardly visible in normal operation. So forget what I said before: Might be worthwhile contacting F(x)tec for a replacement after al

Yep. One of the major reasons I went back to the original (SD885) Pro1. Although the Pro1 camera is also quite mediocre, it at least does not have these hangs of the Pro1-X's which make spontaneous picture shooting impossible. Note that the Pro1-X camera at least did not hang for me when using the camera app built into LineageOS. This prevents access to advanced camera controls though, and anyway the optical quality remains horrible of course. Especially the vignetting is catastrophic on my prawnX. As to your screen problem, I think everything has been said already. This has really

On discord they helped some guy install UBtouch manually after the installer didn't work for him either, basically following this how-to: https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x To get all the partitions required for flashing, you need a "devel-flashable" zip. Unfortunately, the last successful job of that kind at UBports was 9 months ago, and the resulting artifacts.zip is no longer available for download: https://gitlab.com/ubports/porting/community-ports/android11/fxtec-pro1x/fxtec-pro1x/-/jobs So self-building the system p

I once tried to swap-in the screen assembly of a Pro1-X into a Pro1. They fit mechanically and connector-wise. The result was that the Pro1 was able to boot into a (working) Lineage recovery, but not into the full OS. I thus assumed the selfie camera was different. Of course, the top half of the Pro1(X) includes more than the (touch)screen and camera. There is the indicator LED, the ambient-light photodiode, a speaker and (I guess) a mic for handheld audio. But somehow I had assumed those were analogue devices that could not cause a crash upon boot.

Can't find it back either. But I just checked: If you *carefully* lift the edge of a cap with a pair of tweezers, you can see the transparent mat below. So the keycaps indeed seem to be individual parts. Not something that was meant to be user-customizable, but it does seem possible ...

I think someone here reported that one of the keycaps came off, and they glued it back in place?