claude0001

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.

I've uploaded my latest build of LineageOS 16.0 for OG Pro1 (SD835) to https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The ROM dated "20240807" gives you backported Android security patches up to the July 2024 ASB. There are no other changes since last time. The full patchlog, documenting all my changes relative to unmodified LOS 16.0 is also available, as usual. Have fun.

<off-topic> In recent (12+) Android versions, you have to disable phantom process culling to run Linux distros in chroots, otherwise the OS will randomly kill your Linux programs. Google thinks this is a feature, but luckily they introduced toggles to switch it off in Android 13 and beyond. Requires some form of root access though. I have Debian 11 running in a chroot of LOS20 on my Pro1-X, so it is technically feasible. Not using it daily though, as I like the OG Pro1 better. </off topic>

I guess this is about a Pro1-X (SD662). I've got the same issues with OpenCamera on LineageOS 20.0: Random hangs during focussing and zooming, which make the app useless for spontaneously taking a picture. Doesn't matter whether one uses OG Camera-API or Camera2-API. The default LineageOS camera app (org.lineageos.aperture) works fine without these issues. It cannot use Camera2-API and I am not sure if one can install it on stock Android, but this does show that the camera is useable in principle (though not of high quality).

That's quite similar experience I had before fixing the antennas of my prawn-x. One one side of my flat calls and data would work, on the other not at all. Can depend on what bands are strongest in different places ... Also in my case, wifi was unaffected and always worked. Its on a separate antenna module.

Supporting what @Hook wrote, and quoting the official LineageOS wiki: Alternative ROMs cannot magically fix problems that reside in the hardware or the binary blobs of the Pro1X. Are you sure WiFi, LTE and GPS worked fine with stock Android?

I'm sure you could ask way more for an OG Pro1 in such good condition. I'd be very much tempted, but i've got a spare prawn already. Would be a pity if yours had to spend its remaining life in a drawer. Hope it will find another loving owner...

I use it for remote-controlling my Pro1. Works well, but the refresh rates are rather low. Obviously, this requires a third device to act as the VNC client between the phone and the external display, so it's certainly no solution for all use cases ... Also, as any mirroring technique based on screengrabbing, it cannot be used to display DRM protected content (Netflix, Prime ...). Luckily the Pro1 has true HDMI ...

Depending on your needs, you might want to add the Izzy repository to F-Droid. It has a lot of interesting open-source stuff that does not (yet) meet the acceptance criteria for the official F-Droid repo. Aurora Store is what you want to be able to install (free) software from the Google Appstore. Some apps (e.g. official Firefox) are not on F-Droid, despite being open source ... Congrats on getting things going at last!

As far as remember, you do have to "accept" the Google terms, even if you skip connecting the device to a Google account. That's probably because the Google Services are already installed in the Stock ROM, whether you want to use them or not. It's been a long time for me though ... That being said, the only point with enabling USB debugging in Stock Android is to trigger that initial reboot to the bootloader, which you can indeed also just do manually with the "Volume Dn + Power" combo. While there really is no special trick about it, let me try a step-by-step: Power off the de

Fully agree. When I first got my Pro1-X, there simply were no Google-free OS options yet. Still, I remember I was able to start the phone without linking it to any Google account.