Jump to content

claude0001

Members
  • Content Count

    463
  • Joined

  • Last visited

  • Days Won

    53

claude0001 last won the day on August 31

claude0001 had the most liked content!

Community Reputation

812 Excellent

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Your reasons were not wrong, quite the opposite in my opinion. End of 2020, the original Pro1 was fully developed, had been shipped in significant numbers already, and could be ordered normally from the F(x)tec website. At that point, the sole reason for the Pro1-X IGG campaign (as I see it) was to generate additional funds so F(x)tec could actively push the development of alternative OS's for the Pro1. This is what you supported through your backing. However, after realising they could not source the SD835 SoC anymore, F(x)tec had to repurpose that funding toward development of
  2. Yes, the headline is certainly click-bait to some extent. I think the author is just very serious about the "alternative OS" aspect of the phone, and -- as I tried to lay out above -- this was ineed the central promise made about the Pro1-X (unless I'm mistaken, the "X" initially stood for "XDA"). Anyone still remember: "the smartphone that gives you control. Control over your data, control over your privacy, and choice over your software."? In a nutshell, the review says the following: Pro1-X backers were told they invest in a slightly upgraded Pro1 with much better (official!) Goog
  3. Disregarding the tone of the OP, I find the review this thread refers to actually kind of OK. Obviously, the article does not go into much technical detail. But then, those who follow this forum every day would probably find any level of detail insufficient, and I think the author does a decent job in summarising the state of the Pro1-X project for outsiders. Of course, we, having followed all the developments of the last years, understand why the Pro1-X eventually became a different phone. But why should a reviewer care about that? All he does is compare the phone that is actually d
  4. 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?
  5. 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 ...
  6. 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 ...
  7. 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 ...
  8. 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.
  9. 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
  10. 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
  11. 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 ...
  12. 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 ...
  13. 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.
  14. "Fastboot-mode" is the state the device is in when the bootloader screen is shown.
  15. 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 ...
×
×
  • Create New...

Important Information

Terms