Leaderboard

Yes and no. The Pro1 (and, by extrapolation, the future Pro1-X) can be set up as a quite OK always-carry-on GNU/Linux computer. I achieved that using rooted LineageOS + a custom-made Devuan chroot (see this thread for an entry point). Similar results can certainly be obtained using stock Android combined with a solution like Termux if you do not want to root, especially if a Un*x CLI is everything you really need. In fact, if you ordered your Pro1-X with UbuntuTouch you may (hopefully) be good to go pretty much out-of-the-box. None of these solutions breaks the "phone" functions in any wa

Its purpose is to bring the tap-insensitive display borders back from too wide to normal after a display replacement. If you need a display replacement and you get one from any other source than Fxtec (and Fxtec has been out of replacement units for some months now, also they're expensive as they include casing and front camera and other electronics), those replacement units will come with significantly wider tap-insensitive borders – to the extent of making it difficult to impossible to use some functions in some apps, even with the margin settings provided by LineageOS reduced to zero.

Theoretically, ACC/AccA has that function, it's called "charging power control" and it lets you set limits for both voltage and current. Problem is, so informs us the app, "unfortunately not all devices/kernels support this feature", and unfortunately I've had no luck getting this to work on the Pro1, either. Within the app, there's also no way to find out whether the device or the kernel is to blame... Another cool feature doesn't work with the Pro1, either: "prioritize battery idle mode": "This allows supported device to draw power directly from the external power supply when charging i

It may happen but shouldn't it reduce only the CPU speed? You are right that it may affect overall performance and my feeling can be wrong anyway. Also it may happen if there is a component which runs well from 3.3V power supply but battery is getting closer to 3V is also starting to run at lower performance it there is no step-up converter for it - however, it may happen that UFS is basically running at 1.8V (haven't looked into it) which makes the circuit simpler in this relation. 🙂

My Pro1 hasn't seen much use as of late due to my habit of breaking the screen, still charging has had a few hiccups here and there – though nothing as drastic as having to reboot to start charging again, if I remember correctly. That said, I'm running LineageOS 18.1 with Magisk and I have the ACC (Advanced Charging Controller) daemon installed as a Magisk module (plus the AccA app), which I had thought to be the culprit here. Whether it was or wasn't, whenever the phone wasn't charging although it should, I opened the AccA app and that usually made charging start again...

Just to note, I never shut down my Pro1. It just gets a weekly reboot with the update.

Had this happen to me as well yesterday. Noticed the phone didn't keep charging at 73%. I had used it while plugged in some time before but it was cool right then. Was fixed after a reboot this morning. Usually I shut down my phone over night but this week I had just used airplane mode, so it had already several days of uptime.

Here is the long story of how I got expelled from the AT&T network: My old phone, before the Pro1, was a Galaxy Note 3. It was 3G-only. When I got my Pro1, I swapped the Note's sim card into the Pro1 and carried on as normal. This worked great. I did notice that some features, such as HD Voice, did not work. Probably because this was a very old (2014) SIM card that wasn't provisioned for those features? Anyway, it didn't affect my enjoyment of the Pro1. In 2021, I started getting texts from AT&T saying that my "Note3" was 3G only and would soon be unsupported. They

I'm having no charging issues with 18.1 (I update weekly). I tend not to let it drop lower than 40% and I use slow charging from a USB 2 powered hub.