claude0001

As a long time Pro1 supporter and LineageOS maintainer, I must say that I am somewhat unsettled by announcements like this. For many users (including myself) the Pro1-X is effectively a brick, as its GSM/LTE connectivity problems do not allow it to be used as a phone in the first place. In that perspective, advertising the possibility for custom-made shells just seems ... wrong ... at some level. Sorry to write that, but where are the relevant news on the topic?

Not to disregard that it may work for some, but just my 2 cents to all others: Think about how often you use your phone's camera, for family pictures, barcode scanning and all that ... In many cases, a flip case that does not have the holes where they should be will not make you happy.

@EskeRahn Maybe you're right and I am too negative. But for me it's listed as "currently unavailable" anyway, so ...

Looking at the pictures, its camera aperture does not seem to be low enough to accommodate the Pro1-X's lens. And certainly not its flash LED. Wouldn't recommend.

There is no need to root stock, just to install LineageOS. For that it would have been enough to just unlock the bootloader, no need for Magisk and boot.img patching ... On the other hand, if having root during use of the phone was your goal, you will find that in your newly flashed LineageOS, Magisk and su are now gone. You'll then have to re-install Magisk and re-do the boot.img-patching procedure (this time using the boot.img from payload.bin, contained in the lineage*.zip you used for sideloading).

I agree with @Hook. That screen in the first screenshot should be shown while you use fastboot to flash the boot.img. adb, on the other hand, does its job only from recovery, not from that bootloader screen. That said, just flashing the Magisk-patched boot.img (which I understand is what you are trying to achieve) does not require any action to be performed from recovery. You should not go there at all for this. The no-command-screen usually indicates that the recovery image fails to boot. It normally should not be shown at any step of a reflashing procedure, and probably indicates t

Thanks for testing the Pi4 in this respect. I do not have any of these and always worried its USB-3.0 parts might behave differently when compared to the older models' USB-2.0. Good to know this is not the case. I'm not sure which OS you use on your RPi, but since 'buster' the respective Debian packages are just called "adb" and "fastboot". I.e. in recent Raspberry Pi OS, one would rather do sudo apt install adb fastboot

I have always only used "B" models, which come with 4 USB ports and Ethernet in addition to WiFi. This of course doesn't mean that the A+ will not work for your purpose ...

I have an X250 and could never use fastboot from it (original Pro1, Linux also here). Probably ... There all kinds of tips and tricks (use external hubs, remove unnecessary devices from the bus, ...) but it all feels a bit like doing a rain-dance and tossing salt over your shoulder ... All I can say is: Since I have set up adb/fastboot on that Raspi3 (others have reported RPi4 will also work inspite of different USB HW), I have never looked back.

fastboot is way more picky about the USB connection than adb. If @Casey's suggestions do not help: Various RaspberryPi's have been 100% reliable for me when it comes to flashing Pro1(X) -- I've never again used adb/fastboot from my PCs since I found that solution.

No idea. I am coming directly from lineage-16.0. But you are right, according to user reports on the net, 18.1 seems to have broken the built-in sshd. This has nothing to do with the Pro1-X.

@Sean McCreary : Thanks for that background info. Do not get me wrong though: I understand that this is beta software, and am fine with all the limitations that implies. I expected you would, sooner or later, move to the Pro1 (aka. tdm) keyboard driver anyway. Hence, I thought it would not be worthwhile to file a bug against the present state of things. Coming back to my above point: Is the missing sshd intrinsic to lineage-20.0, or could you choose to include it in the builds?

@Sean McCreary: I was under the impression that several of the "yellow" modifier keys did not work correctly in the 20230120 rom. I have a QWERTY Prawn-X. I did not try to study the problem in depth tbh. Since installation of the new build it just works ...

Update: Just flashed the new ROM dated 20230124 via sideload smoothly. Level-3 keyboard modifier ("yellow arrow") keys now work correctly, with more keyboard options to come according to the XDA thread. Awesome! I also successfully rooted using Magisk. Yay! On the downside, I find that lineage-20.0 seems to no longer provide an OpenSSH-server . I think I will need that to re-implement the full functionality of my GNU/Linux-chroot setup on Pro1/lineage-16.0. I see there are Magisk modules providing sshd nowadays ... probably will have to get into that ...

Me too. Installation was smooth using the instructions linked above. Seems stable (i.e. no crashes)up to now, but I haven't played much with it yet (Pro1-X is not my daily). LTE/GSM connectivity is just as bad as in stock -- as was to be expected. On the positive side, WiFi scanning again works correctly after 2.1.5-GMSless had somehow broken that for me.

When you are worried about privacy, the single most important step is to get away from manufacturer-taintedbranded ROMs, Google Apps, and the Play Store. A publication demonstrating that by network analysis of phones' upstream traffic has actually been posted here before. Privacy-wise, you can essentially get on-par with all those self-proclaimed "privacy-first" OS's by simply installing LineageOS without Gapps and using F-Droid for your app needs. Sounds hard, and few do this, I know. On the other hand, If you think you can't live without Google services and Google apps, no amount o

Awesome! Too bad I'll be back with my Prawn-X only on Monday evening ... Can't wait ...

@Casey, please do not assume that only people opening tickets are affected by the connectivity problems. I think many of us (including myself) regard this as a general problem of the device that will be fixed in an upcoming software/firmware update. These hopes are based on last year's October and December updates, where you acknowledged poor signal and connection drops as one of the most notable bugs of the stock Android ROM, and wrote you were preparing an update to fix this. Assuming the problem is already being worked on, I thought it would not be helpful to open yet another tick

LineageOS 16.0 has been updated to include backported ASB fixes up to patchlevel "5 January 2023", celebrating one year of support beyond Android 9 EOL 🙂. At https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 fetch the ROM dated 20230111. Remember that this is for the original SD835-Pro1 only! The note about lacking upstream code-review still applies (see above): all I know is that the system seems to run fine on my own prawn. As usual, all mods with respect to the official lineage-16.0 tree are available as a tarball for reference. Have a lot of fun.

*off-topic* Yes, stick to that beautiful machine as long as you can. I love those old laptops that were actually compactified versions of true workstations -- with all ports, interfaces, and peripherals ever needed. I sadly will have to retire my beloved T400 soon (due to lack of video acceleration in recent Firefox). It is to be replaced by a T470p that can't even come with an optical drive bay. All for the "added value" of a few mm-thinner frame ...

After trying to actually use my Pro1-X as a phone, I am now convinced that community devs simply refuse to invest further effort into a Lineage port until at least the most blatant bugs in the device are ironed-out by the manufacturer. Few will want to invest time and effort into a new OS for a device that does not work on the most fundamental level of a phone. If the Pro1-X's connectivity problems are indeed related to the modem driver, we'll just have to wait until F(x)tec pump out a new stock to base on. If the issues are hardware-related, the device is practically DOA for many users a

The Pro1 seems really problematic with regard to fastboot. I recently flashed my wife's Fairphone3 using my Thinkpad X250 without any problems. That same PC never succeeded with the Pro1 ... There seem to be multiple factors affecting flashing, especially in fastboot mode, and some are not controllable in a daily-driver PC. E.g. many USB-attached peripherals are not "removable" in a laptop. Hence my advice to just use a dedicated system for all Pro1 flashing. Using adb/fastboot from a Raspberry 2 or 3 just works(tm)! They're hardly more expensive than a separate USB hub and are usefu

Sooo ... I finally got myself an additional SIM for my Pro1-X. And ... things seem to be bad ... Very bad ... So bad, that I now regret relativizing some of the devastating experiences others have posted here before ... Apologies, guys! I got my Pro1-X two months ago (from Expansys) and found its WiFi and GPS functions to be somewhat on par with the - albeit not great - capabilities of my Pro1. Based on that, I extrapolated that telephony could not be much worse, either. I think I've never been that wrong! After a few hours of testing, the Pro1-X's GSM/LTE modem seems to be a disast

I too had initially many troubles when trying to use several Linux PCs (both, desktops and laptops) for flashing the Pro1 in fastboot mode. Compared to other phones, it seems to be quite picky about the USB hardware ... I ended up configuring one of my Raspberry Pi3 specially for flashing my Pro1 and Pro1X: no problems ever since. The RPi3's are cheap, their simple USB-2.0 ports have proved to be 100% reliable for the purpose, and adb/fastboot is just an "apt install" away in Raspbian.

From this thread, it seems like you already know all there is to know. Still, here is my summary for any newcomers dropping in: For unknown reasons, F(x)tec ship their phones configured in a way that allows battery charging only with a running OS. If, by whatever circumstances, the battery charge ever drops to zero in that configuration, re-charging will no longer work, as this would require to first boot the OS which - in turn - would need at least some residual charge to be left in the battery. In that situation, the only way to re-charge is probably to disconnect the battery from the c