claude0001

Afaik, the keyboard is the same than the Pro1's. That one's driver is open-source, and all versions of LineageOS for the Pro1 have a key-remapping interface. I would assume those bits will get ported to the Pro1X's Lineage.

"Fastboot-mode" is the state the device is in when the bootloader screen is shown.

That variable has the same value on my Pro1. rostkatze:~ # cat /sys/class/power_supply/battery/constant_charge_current_max -22000 I'm still running LOS 16.0 and never had the charging bug. Whatever that number means, I think it is unlikely that this is the right track ...

Confirm this with a Pro1. I sometimes stream music (from youtube) to a bluetooth speaker via the Pro1. When the latter uses the 2.4-GHz-wifi band, there can be a ver short hickup in the bt-audio when the player downloads another bit of the youtube stream. Can be prevented by forcing the Pro1 to use the 5-GHz WiFi bands (which sadly have lower range) ... Of course, both, 2.4-GHz-WiFi and bluetooth should be able to handle this kind of interference according to their spec, but reality obviously disagrees. When we bought our house in 2017, everyone was laughing at me when I wired different r

@Slion, in all fairness and understanding: wireless connectivity is the central capability of a mobile phone. It should also be at the center of the design and QA. The Pro1 was not outstanding in this respect, but the Pro1X is obviously failing to be useful at all for some users because of the quality of its radios. While I hope they will be able to improve behaviour in future firmwares, these bugs should have been ironed-out in the prototype phase.

The latest update on IGG (two weeks ago) https://www.indiegogo.com/projects/pro1-x-smartphone-functionality-choice-control#/updates/all suggests LineageOS development is stopped until October. It is essentially waiting to be rebased on the new stock-ROM that they hope to certify in September.

I do not recall anyone complaining about missing 5G capabilities here. This is about bad experience with LTE (4G) and wifi connections with the Pro1X.

All the news we have are about f(x)tec (slowly) working through existing (pre-)orders that have in part been pending for several years. This should not prevent you from ordering a Pro1-X. As far as we know, f(x)tec finally always delivers. However, you should not count on getting you phone very soon. Also note that the Pro1 and Pro1-X do not "support" Linux in the way the PinePhone does. While some progress in mainlining the original Pro1 (the SD-835 variant) has been made, all existing GNU/Linux OSes for the Pro1/Pro1X that can at least remotely qualify as daily-drivers (SailfishOS, Ubun

I think greyed-out switches usually mean that the feature is not available. This is how it looks when VoLTE is available (though it can then still be disabled in Android):

Just use the "code" icon (labelled "<>") in the text formatting bar.

I've had similar issues with my Pro1 since day 1, though I cannot restrict the phenomenon to a certain subset of keys. In the beginning, me trying to type fast always resulted in many errors, either from missing characters or from the software registering additional (e.g. "addd&nitional") keys, I certainly had not pressed. Over time, I improved in hitting the keys "right", i.e., quite firmly and in a well-defined sequence. However, I cannot say that this kind of typing is much fun. I type slowly, and cannot practically use more than two fingers, even when putting the Pro1 down on a t

The Pro1's camera window is actually sunken-in by a tiny amount, to protect it when the phone is put on a table for keyboard operation. I remember f(x)tec were quite proud they had achieved that in designing the back of the phone ...

For what it's worth, another update of Netflix (to version "8.35.0 build 19 50257") just came in via Aurora. Runs just fine on rooted, GAPPs-free LOS 16.0. Seems like it is indeed just a matter of circumventing the Google Play store ...

A new build of good-old LineageOS 16.0 for our good-old Pro1 (835) is available at http://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 Go for the ROM dated 2022-08-23. It contains backported AOSP security fixes up to patchlevel "1 August 2022". I bumped the Android security string to reflect that. Seemingly, people are slowly losing interest in Pie. While the AOSP patches since May have been backported and have undergone basic testing (by me and on other devices), they have not been merged into the official LOS 16.0 tree yet, due to pending code review. While I a

Affirmative. Consensus is that deep discharge is bad and high temperatures (as occur during quick-charging) are bad. This is true for any Li-ion battery, nothing Pro1(X) specific here.

Sorry, but just use a non-Quick-Charge-enabled power supply. No other action requied.

Deep-discharging being a good thing is a popular myth from Ni-Cd-battery times. Li-ion batteries do not like that. @EskeRahn is right in that temperature is a decisive factor. Using QuickCharge (tm) results in my Pro1(not X) becoming so hot it is uncomfortable to touch. I hence avoid quick-charge by using only my PC USB-ports for charging.

Unfortunately, I have no second specimen of this (quite expensive) type. Now, I could insert my Pro1 card into the laptop and test. However, considering that I routinely hurt at least two of my fingernails when extracting the Pro1's <censored> SD/SIM holder, and subsequently always wonder whether I haven't broken the puny little thing for good now, I prefer not to, sorry. 🙂

I've had a SanDisk eXtreme 256 GB in my Pro1 (no X) since day 1. My impression is that, while isolated read or write access is OK, random access cannot be compared to an ssd or even a magnetic hdd, no matter what you are being told. I learned this the hard way after installing my GNU/Linux OS on my SD-card (in an effort to reduce wear of the bulit-in memory). Some benchmarks from my system: Pure writing: dd if=/dev/zero of=test.dat bs=512k count=1k 1024+0 records in 1024+0 records out 536870912 bytes (537 MB, 512 MiB) copied, 8.25252 s, 65.1 MB/s Pure reading: dd if=test.dat of

I can confirm that the app itself does not (yet?) complain about rooting per-se. Rooted, Google-free Pro1 with LineageOS 16.0 here. That's good-old "su" (on modified root partition), no magisk hiding anything about it. I could install Netflix via Aurora store and it is getting updated normally.

Other American users have reported that soon, all networking protocols prior to 4G will be shut down in the US. So this might not be a long-term solution ... edit: As expected, @Hook was faster ... 😄

Confirmed for the 835 Pro1. Toggling that flag causes the Pro1 to ignore the connected power cable and drain its battery instead.

Awesome findings, thanks. I did not test the (unsafe) battery capacity-faking bit (yet). 😉 The battery charging control works the same on the original (835) Pro1. The keyboard backlight control also works similarly, except that, on the Pro1, the respective sysfs files are located under /sys/class/leds/keyboard-backlight/ rather than "/sys/class/leds/button-backlight/".

Thanks for this heads-up. Having my Pro1 so nicely set-up as daily driver almost feels like a burden, now. If I only had a spare Pro1 or Pro1X for tinkering with such promising projects ... At first glance, I can find no review or video online about Droidian even for the original Pro1, which is strange given it is one of the only three officially supported devices ... @steeb did you test on Pro1 or Pro1X?

I'm not using Termux myself. But, in my (very limited) understanding, it still works on Android 12. It is just not receiving updates (or is not installable at all?) from the Google App Store (because it still targets Android 9 SDK). The F-Droid version should not be affected by this, nor manual installation using the *.apk. There seem to be some worries that, in the future, Android 12+ might shut down apps targeting Android 9 SDK via SELinux policies. But would this necessarily also affect LineageOS 19.1+? Anyway, I disabled SELinux on my Pro1 (LOS 16.0) long ago ...