claude0001

That is a good question indeed, and the silence from F(x)tec on this is strange even by their standards of communication skills. I can imagine they are engaged in legal procedure against Expansys and their lawyers are recommending them to not publicly comment for the time being. As I read, they did promise the regular IGG update before end of the month. Let's see what will be in there ...

Besides the apparent lack of free ROMs, my biggest concern is that the keyboard -- unlike the Pro1(X)'s -- seems to lack many of the special symbols important for shell work or coding. Like "~", "|", ">" "\", or the sqare ("[]") and curly ("{}") brackets. Is there a way to enter these characters using the hw keyboard, e.g. via customisation?

Thanks @Casey. But what does this mean regarding native HDMI-support in Android/LineageOS. Will it ever work? What about the convergence mode of UbuntuTouch? Any hope for that?

With the original Pro1, HDMI works for me in LineageOS using this all-in-one hub: https://www.amazon.de/-/en/gp/product/B093FKT9BF/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1 Wait, what? Does that mean that things like this [iggcdn.com] will never actually work with the Pro1-X? I think that was a major feature for those who ordered with UbuntuTouch ...

Nice thanks. On LOS 16.0, a half-press (i.e. the first stage of the shutter button) can be used for "Screen peek", i.e. shortly activate the (lock) screen only while the button is held. Does that no longer exist in LOS 18.1+? I find that quite useful for e.g. checking the time. Of course, as Pro1X has no double-action shutter button anymore, it wouldn't work there anway ...

Bummer. I have also used OpenCamera with my Pro1 since day one. Do you have any information on how not allowing users to set another camera app as default is supposed to be more secure? Did LineageOS 18.1 and 19.1 adopt that "improvement" or can Lineage users still pick whatever camera they want? Might be one more reason for me to camp on 16.0 a little longer ...

The Pro1's kernel supports vfat ("FAT32"), msdos ("FAT16"), ext2/3/4, and f2fs. At least for FAT32, ext3 and ext4, cards can be read also when partitioned and formatted on my (Linux) PC. Even with multiple partitions on the card, Android (Lineage) can access them all. I never tested f2fs. Of course, you should understand the implications of a UID-aware filesystem, before using something like ext. The same would hold for NTFS, where Unix-UIDs would need to be mapped to NT-UIDs in some way.

F(x)tec communication at its best ... 🙂 "Contractual issues" with their partners that lead to a 4-month-delay? With their tradition to underestimate delays by a factor 2 to 3? That's asking for the wildest speculations ... Here are mine: Option 1: The logistics partners suddenly want more money due to prices skyrocketing because of the ongoing crisis. F(x)tec can't pay more so they insist on fulfilment of the existing contract. Parter refuses and stops all activity, witholding the phones. They need to take it to court. Option 2: The entire batches 1 and 2 have "disappeared" fr

Odd, that looks like two different graphical layouts of the bootloader. Never seen that. I did everything fastboot (on Pro1, no X!) from the bootloader screen like on your first picture. That is the one I get when selecting "restart to bootloader" from LineageOS. You are right that a bad fastboot flash may mess up your data. However you should always be able to reach the bootloader for a full reinstall by holding "volume down" while powering the device. Make sure you have a full battery before any flashing experiments! If you have a bad feeling about your fastboot connections, I

I think @eorg is mistaking recovery for bootloader. He/she wrote that fastboot does work in "fastboot-mode" but not in "bootloader-mode", which makes no sense because the two are the same ...

Also for the Pro1, the Lineage driver was completely rewritten with respect to Stock. I have always only used Lineage and that one indeed supported sticky shift. As far as I am being told, that is a high level Android feature though, and has nothing to do with the actual device driver ("qx1000.c"). I am pretty confident all those things can be changed once we get a Lineage port ...

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