claude0001

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?

Several posts on the IGG comments thread suggest QWERTY variants are out now. Remaining orders seem to be asked to choose between QWERTZ and scandinavian keyboard layout ... 😕 Edit: Has hit the discord channel too, now.

I agree with your criticism of the Pro1-X's remaining hardware and delivery process. But in these lines you essentially state that you backed a keyboard phone even though you have absolutely no use for a keyboard phone. Of course you have every right to do this. But then do not lateron blame F(x)tec when they indeed ship you a keyboard phone as ordered ...

As previously stated, I can only agree. I have 2 x Pro1 and 1 x Pro1-X and all displays have these black moons in at least some of their corners. The good news is that they haven't worsened over time, which is 4+ years for my initial Pro1.

Not using SFOS myself since many years. But others indeed have reported much better results. As you had similarly devastating experience with Droidian, also (kind of) positively tested by others, I wonder if something is wrong with your device. Did it work correctly with stock Android 11?

Maybe it is. But not because you dislike the screen. Rather because you do like the rest of the phone! Just joking of course ... 😉

VoIP was enabled by default on my Pro1-X, and WCDMA (part of 3G) is being, or has been, phased-out in many regions ...

My Pro1-X from Expansis is also black. I think they made a lot of those.

Happy to meet someone who is capable of joking on the subject. 🙂 You're not alone with that problem. As far as I know, most Pro1's and Pro1-X's have screens that shown black spots in their corners. Most users simply accepted them until now. I do not know of any standards that an AMOLED screen must legally fulfil in this respect.

You must be new here ... Sorry for the pun, but you'll soon learn that f(x)tec is no ordinary business ... 😄

I wouldn't worry about those. My Pro1's (got two of them) and my Pro1-X have had these black spots in the corners of the screen since day one. They haven't worsened over time (we're talking years for my initial Pro1)

They have previously stated that they no longer have spare parts for all components of the OG (SD835) Pro1. So, depending on what's broken, they might simply not be able to repair it. I'm just guessing, though. For any other company that wouldn't be a big deal - they'd just send you a completely new phone. In F(x)tec's case you could ask them for a new Pro1-X. However, considering the rate at which they manage to send those out, also that could take a while ... In two years, they managed to get out an estimated couple hundred Pro1-X's into the wild. I.e., on average, they ship ~1 pho

I've just uploaded my latest build of LineageOS16.0 (for SD835 Pro1), dated 20240820, to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Changes since last month: Includes backported security patches up to the August 2024 Android Security Bulletins. Updates the bundled system WebView to Chromium 127.0.6533.103 (as shipped with official LOS 20 and 21). Have a lot of fun!

I unfortunately have to agree. The aftermarket is flooded with Pro1X's that Expansys sold for 300 $ a piece (that's how I got mine). No one is going to give you 800 bucks for that thing ...

I had this once (after dropping the phone) and solved it by re-seating the screen connectors in the top unit of the phone. Disassembling the top unit is quite easy. I've done it many times. Take a good look at the instructional videos before though.

I cannot reproduce this with my Pro1-X. Not using Termux, though. I'm running Debian 11 in a (rooted) chroot of LOS 20.0 and use ConnectBot as my terminal emulator. Your script works fine (with some trivial changes to match my environment). As, also for you, the keyboard behaves normally in other apps, it seems to me that you are somehow triggering a bug in the terminal emulation of Termux.