Jump to content

claude0001

Members
  • Content Count

    711
  • Joined

  • Last visited

  • Days Won

    96

Everything posted by claude0001

  1. Hi @raymo, Thanks for your interest and feedback. So you are saying you had no HW keyboard issues with LOS 17.1, but input problems started when you tried my ROM? That is interesting: My keyboard driver indeed contains several mods with respect to the upstream LOS 16.0/17.1 one, as documented in my patch log. Partly, those are backports from LOS 18.1 and above that are actually supposed to improve keyboard behavior ... E.g. I think unwanted multiple presses of the same key became much fewer (for me) after I had backported the respective patch from 18.1. I do experience problems with
  2. so ... what keeps them from working on the Pro1-X's Android OS or at least explaining why they chose to stop development?
  3. Of course they are out of money. On the other hand, as they are neither producing nor selling devices right now, what else is there to work on except software development? Since last summer they - reportedly - were chasing all those Pro1X bugs with highest priority. And for months they were confident to release a new OTA soon. Then, with the April update, all news on stock Android development stopped. What sense would it make to abort such development at a stage when, apparently, 95% of the work has already been spent? Rather than financial issues, I suspect that either 1) all their
  4. Given that a significant number of Pro1-Xes have been grey-marketed, and given the significant problems it causes many users, unboxed-but-unused Pro1-X pop up on E-bay all the time. It shouldn't be hard to get one if you really want it. Be warned though: my Pro1-X absolutely cannot work as a smartphone due to missing LTE connectivity in my area (EU/Germany). I have a perfectly-working original Pro1 as direct comparison. The X has quite a number of other bugs, but none is as dealbreaking as its missing mobile network connection ...
  5. All the income on the preorders and IGG perks has already been generated. They have all that money already ...
  6. Most who actually have one got it via Expansys' grey-marketing (myself included). But F(x)tec's delays in delivering the preorders/perks is one thing. What is imho more worrying is that all technical activity on their side seems to have come to a halt. They appear to mostly manage the logistics disaster the Pro1-X has become. The bragging about community-supplied OSes in their IGG updates appears like a helpless attempt to mask the fact that their in-house development work has essentially stopped. Considering that the Pro1-X's stock Android (on which also all alternate OSes rely) still ha
  7. Like they did already in May, they fill their update with information on an alternative OS that is entirely community-developed (besides all this information on Droidian being readily available on this forum anyway). What about the work the community cannot do? What about stock Android? Will we ever get that update towards which we have been "sprinting" for the better part of a year now? Any news on firmware fixes related to LTE connectivity? Battery depletion bug? Anything at all? I wonder if the prawn-X might be the first device to be EoL'd before even all preorders have shipped ..
  8. At least for the Pro1-X, the battery connector directly contacts the cell electrodes. Otherwise charging with an external PSU would not be possible in the way that has been shown to work. I'd be surprised if the Pro1 was any different in this respect ...
  9. The polarity on that one seems to be inverted with respect to the Pro1-X's ribbon cable (compare the labels P+/P- with those from @Whitey's picture). Everyone, be sure to always connect your charger in the right way ("+ to +, - to -"). Otherwise bad things may happen.
  10. [deleted] Edit: OK, had not seen your last edit. I guess problem is solved?
  11. For some phones, the bootloader can be re-locked after LineageOS has been installed, provided they have not been rooted. I know that this is possible e.g. on the FairPhone 3. However, this is not generally the case, and users here have reported that they bricked their prawns while trying ...
  12. Check if your SD partition gets mounted with a SELinux context (see my edited post above regarding this aspect). If yes, I would first try to disable the latter ("/vendor/bin/setenforce 0"). In fact, I'd do that anyway, just to be sure. ^^ If you mean this bug: https://gitlab.com/LineageOS/issues/android/-/issues/3321 reported by @EskeRahn, I think that was introduced only in LOS 18.1. As far as I understand, things were fine in 16.0 and 17.1. I do not know for sure, though, as I'm not using multiple keyboard layouts on my 16.0 ROM. If you provide me with sufficiently precise
  13. Actually, I was wrong in my previous post. In LOS 16.0, the ext3 partition does get mounted automatically under /mnt/media_rw/. I then just bind-mount that file to wherever I want (/data/DEBIAN, in my case). The difference to ext4 (and my reason for using it) was that Android 9 does not seem to subject ext3 partitions to a SELinux security context, which would effectively prevent a seperate (chrooted) OS to run on them. Sorry for causing confusion, it's just quite long ago that I set this all up. Look at the initial lines of my chroot script above: #!/system/bin/sh # # Script to set u
  14. I haven't made a better picture than the uploaded one. However, @Whitey have a pretty nice one in their post above:
  15. On LOS 16.0, ext3 is supported in the kernel. I do not know about LOS 20, but it would surprise me if someone had removed something as basic as ext2/3 from the config. Check this on your device: # cat /proc/filesystems nodev sysfs nodev rootfs nodev ramfs nodev bdev nodev proc nodev cpuset nodev cgroup nodev cgroup2 nodev tmpfs nodev configfs nodev debugfs nodev tracefs nodev sockfs nodev pipefs nodev devpts ext3 ext2 ext4 vfat msdos nodev ecryptfs nodev sdcardfs fuseblk nodev fuse nodev fusectl f
  16. What f(x)tec euphemistically refer to as a "sleep state" means nothing else than that the battery erroneously got depleted to literally 0.0 V, so that there is no energy whatsoever left in it. The "battery protection" system should normally prevent this from happening. Not only is so deep discharging bad for a Li-battery's life expectancy, it also turns out that Android actually always needs enough residual charge left to boot its kernel before re-charging from USB can start. So, yes, once bitten by the battery depletion bug, there is no other way than to either 1) send the phone back
  17. Happened to me once with LOS 20. The battery literally ran down to 0.00 V and I had to use a lab PSU to recharge it -- definitely not something you want to do every week. @Sean McCreary confirmed that it is a problem with the proprietary BMC code, so the fix needs to come to Stock before community OSs can pick it up. I do not believe it is fixed in 2.1.5 as that has been around since September last year, and f(x)tec reportedly were working on the issue as recently as in March. Maybe in that 2.1.6-beta?
  18. According to their website, you can use "apt, dnf, pacman and yay" interchangeably. apt will use the Ubuntu repos, pacman those from Arch, and dnf will get its packages from Fedora. P.S.: As a hardcore Debian user, who even hesitates to mix "stable" and "testing" packages, I am horrified by the idea to blend together several distributions that are completely unrelated. But that's a different question ... 😉
  19. I do not know BlendOS, but it appears it can use the Ubuntu package repositories. In that case a simple sudo apt install adb fastboot should provide you with everything you need to follow e.g. the flashing instructions from the LineageOS wiki.
  20. The Pro1-X can can do off-mode-charging. I have it enabled and working on one of the Lineage beta releases. That being said -- as @Sean McCreary clarified in another thread -- Android devices are not truly "off" during "off-mode-charging". The Linux kernel and battery management software need to be up and running, just like if the device was switched "on". The only difference is that the Android GUI is not loaded. Now the problem with the Pro1-X is that it's got a bug which allows the battery to discharge completely. If that happens, the device is bricked, irrespective of off-mode-ch
  21. @jakfish, @Hook, @brunoais: I respect (and sometimes admire) your point of view. However, please let's agree on that the Pro1-X was not marketed as an HPPC, but as a phone that could (maybe) double as an HPPC. Let's also not forget that it was meant to be delivered with LineageOS (OK, we finally have that now thanks to community support) and UbuntuTouch (nowhere close). Let's further not forget that it was supposed to come with HDMI-Out to enhance that HPPC aspect (especially with UBTouch). I do not see how my Pro1-X is fulfilling any of those design goals. That's why I, sadly, shelved it
  22. Another update of LineageOS 16.0 (for SD835-Pro1 only) is available at https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1. The ROM dated 20230516 gives you backported security patches up to the 5 May 2023 ASB. No other changes since last month. As usual you can refer to the tarball of local mods to learn all about differences with respect to the official lineage-16.0 tree. Have fun!
  23. It's really hard to interpret those lines differently than that further development of stock Android (on which all alternative OS's rely on in the end!) is essentially off the table. Bad news for anyone who hoped for updated driver modules or firmwares that would fix network reliability issues. This is the second month in a row with no news whatsoever on in-house software development or bug-fixing (after we've been in "the final sprint" for an OTA since November or so). Do not get me wrong: Yes, it's great that we have LOS 20.0. But that's a community effort. In my understanding, F(x)tec
  24. ... well that's the point: I want to stay on my custom LOS 16.0 ROM, but have backported quite a few fixes from later LOS releases. That's why I was asking about the specific patch to look at ... 🙂
  25. I'm about to update my LOS builds with the May 2023 ASB fixes. So I repeat my question: Does anyone know what patch in LOS 17 or 18 apparently fixed low-brightness screen colours on the Pro1? Would love to include that one ...
×
×
  • Create New...

Important Information

Terms