Jump to content

claude0001

Members
  • Content Count

    793
  • Joined

  • Last visited

  • Days Won

    121

Posts posted by claude0001

  1. On 7/22/2025 at 3:46 PM, Hook said:

    but my Pro1 can no longer make or receive calls. It has a SIM, knows it has a SIM and is fine with texting and data, but can't call. If I put in another SIM, the same thing happens.

    You are saying your Pro1 ceased to work as a phone. This is no minor regression for such a device.

  2. I've uploaded the latest build of LineageOS 16.0 (for OG Pro1 / qx1000) to

    https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1

    The ROM dated 20250723 contains a WebView updated to chromium 138.0.7204.63. As Google did not publish any ASBs for July 2025, there are no further changes with respect to last month's build. I decided to still bump the security string to "1 July 2025" to reflect the fact that the system browser was updated.

    As usual, you can get an idea of the full list of changes with respect to the last official LOS16 from the patch tarball also available at the link above.

    Have fun.

    • Like 3
  3. 2 hours ago, helder_alemao said:

    two 22.2 updates of 1Gb each

    The point is that the updates are not incremental. The weekly OTAs each time contain the full ROM, even if changes relative to the previous one are minor or non-existing.

    The idea behind the a/b partitioning scheme is to keep the previous version of the system intact for backup, while flashing a completely new version of the OS to the respective other slot with every update. This is to make sure one of the slots always contains a working OS, even in case of a bad flash or faulty download.

    • Like 3
    • Thanks 1
  4. On 5/31/2025 at 1:49 AM, diejuse said:

    Is possible to add black theme?

    Sorry for answering so late, I do not check this thread very often any more.

    In Settings, navigate to Display -> Advanced -> Style and set Style to "Dark". Then, on the same page, set "Dark mode" from "Default" to "Black".

    Unfortunately, the default launcher and other system apps (contacts, phone, gallery, ...) are not yet prepared to pick up a dark system theme. This is Pie after all 🙂. You should be able to find suitable third-party substitutes in most cases, though.

    • Like 2
  5. 11 hours ago, EskeRahn said:

    But as you keep the 16.0 alive, we can hope that  you, or someone else with the suitable knowledge, can keep the 22.1 alive, if the 22.2 stay broken....

    It would be far easier to stay with lineage 21.0: That branch still gets patched with ASB fixes upstream, so all you'd have to do is fetch the source tree and make the build, which is piece of cake. Basically all you need is a Ubuntu virtual machine with enough storage and RAM.

    Because of the new QPR release scheme, staying with 22.1 is more complicated: Only the latest QPR (22.2 as of writing) is getting patched according to the ASB. 22.0 and 22.1 are not and I'm not sure if the available ASB patches for 22.2 could be directly applied to them. At least in the long run you'd probably have to backport all the patches yourself if you wanted to stay with some intermediate QPR.

    Anyway, I'm not going to do either of these things, sorry. Imho, distributing an unofficial ROM really makes sense only if you daily-drive it yourself. Otherwise bugs, like the one here discussed, slip through unnoticed far too easily. Since I keep my Pro1 on LOS 16.0, those builds are the only ones I feel comfortable distributing.    

    • Like 1
    • Thanks 2
  6. 9 hours ago, EskeRahn said:

    I wonder if it is like AICP a nice project that was just made horrible by some crucial bugs.... 😣:classic_sad:

    Not that I have anything constructive to add, but in LineageOS's defence: They are stuck forever with the Linux kernel version and drivers that shipped with the original Android 9 OS. As the divide between increasingly modern Lineage/Android userland and the base Linux OS amplifies, bugs like this become more and more likely, unfortunately. 

    • Like 2
  7. On 4/12/2025 at 1:33 PM, EskeRahn said:

    22.2 is the newest on the Pro1, and most likely on Pro1X on next release in a few days

    Thanks. Yes I know that. But the doc linked above lists almost nothing for the new 22.2 branch (yet?), while there are quite specific instructions for 22.1, that's why I asked about that one.

    As I am routinely self-building, I feel confident to compile any of the officially-supported branches and thus think I do not depend on the pre-made ROMs from the LOS build farm. However, I hesitate to ditch one of my working installs just to find out that AVF has simply not been ported (or may not be possible at all) for the Pro1 ...

  8. Has anyone tried running a GNU/Linux distro through AVF in recent versions of LineageOS?

    As can be seen from my signature, I am running old(er) versions of LOS on my Pro1(X)'s. The main reason for this is that I have relatively complex Linux-in-rooted-chroot setups in place, that are notoriously difficult to migrate to different Android releases.

    AVF introduced in Android 14 and 15 could be a game-changer for me as it - theoretically - enables official support of Linux-Distros in containers, potentially making my hand-made solutions obsolete.

    However, it is not clear to me if AVF is enabled in all LOS releases. In official Android, it seems to be limited to specific devices/SoCs. So what about the LineageOS 22.1 ports for the Pro1 and Pro1X? Do they include AVF or not?

  9. Here's another one. The ROM dated '20250326', available at

    https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1

    gives you my latest unofficial build of LineageOS 16.0 for Pro1 (qx1000).

    To make the thread more accessible, I'll recapitulate the full list of enhancements with respect to official every few months. So here it comes:

    • Backported AOSP fixes up to the "1 March 2025" ASB (official LOS 16.0 stopped updating in January 2022).
    • Improved keyboard behaviour, partly backported from later LOS releases (code changes can be found in my local patch tarball).
    • Several more improvements with respect to the upstream LOS 16 tree (GPS fix, touchscreen margin control, ...) as documented in that same patch tarball.
    • Updated graphics driver stack (using the same blobs as LOS21 & 22).  
    • Updated bundled WebView to Chromium 134.0.6998.95 (important for those running without Gapps).

    Have a lot of fun.

    • Like 3
  10. Thanks for the feedback.

    With my Pro1 still on LineageOS 16.0, this works. I can select multiple layouts under "Keyboard & input methods > Physical keyboard" and then cycle through them on the fly. Pretty cool, actually. I didn't know about this feature.

    However, on the Pro1 with LOS16, the hotkey for layout switching is Ctrl + Spacebar. Yellow arrow + Spacebar is equivalent to pressing the power button in my case, which is another pretty cool feature introduced by @tdm with his initial port of LOS.

  11. On 2/10/2025 at 4:15 PM, EskeRahn said:

    Indeed, it was broken long ago, then fixed and later broken again, but you are right the chances of a fix seems slim.

    OK. I just think: this sounds like a general regression in AOSP, as keyboard support in Android is generally nothing specific to the Pro1 (hence my question whether this is also observed in the Pro1-X port). I just wonder if it could be worthwhile to open a bug against LineageOS because of this.   

  12. 10 hours ago, EskeRahn said:

    And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage.

    I probably missed why you have been including this warning every week for quite some time. Is this problem unique to the Pro1 (as the corresponding qx1050 thread does not mention it)?

    Anyway, it seems I can find no open bug reported against LOS about this. So, whatever your issue is, I doubt it will ever be resolved "automatically" by an OTA.  

  13. 11 hours ago, CornholioGSM said:

    Passport have on lineage same problem as was on FX (first custom roms) - multipressing keys. 

    Can anyone help me fix it? Will be needed to add something like key press deelay.

    The respective fix for the Pro1 is here:

    https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/318274

    Note that this is specific to the qx1000.c keyboard driver in android_kernel_fxtec_msm8998, it won't be directly applicable to another device.

    • Like 1
  14. The only way of "upgrading" is installing LineageOS 22, which will give you the equivalent of Android 15.

    Since LIneageOS re-uses most of the device drivers from stock Android 9, it is unlikely that audio or camera quality will be improved. At least I do not know of any such updates.

    That being said, a recent LineageOS will give you all those Android security patches since 2020, which is of quite some value in itself ...

    • Like 2
  15. 7 hours ago, cash said:

    TL;DR: I ended up getting the battery to charge after disassembly.

    Congrats. 👍

    I once documented my very similar procedure here:

    This was before the rubber-band trick was discovered, so I hadn't tested if that would have worked in my case.

    At the time, I also measured 0 V between the pins, but you are probably right, that the internal protection disconnects the cell below some critical value. My Pro1-X has been working fine since (though I do not use it much anymore).

    • Like 2
  16. This is ridiculous. I understand that F(x)tec are low on resources, but Let's Encrypt certificates are available for free! They literally would only need to run the 'certbot renew' command.

    I can only hope they will pass on the contents of this forum to the community in some way before the server goes down, otherwise all the (mostly unofficial) info on the Pro1/Pro1-X we have collected here will be lost ...

    • Like 2
  17. 6 hours ago, diejuse said:

    I'm having issues with the physical keyboard since I tried installing new versions of LineageOS. I recently reinstalled stock rom but the problems persist (key repetition or no response sometimes). I'm sure it's a hardware issue.
    Do you notice any issues with the physical keyboard with this modified version of LineageOS?

    Those are hardware issues, unfortunately.

    All recent releases of Lineage (including mine) have a workaround implemented in the keyboard driver that suppresses unwanted multiple keystrokes (https://review.lineageos.org/c/LineageOS/android_kernel_fxtec_msm8998/+/318274).

    For the undetected keypresses, there is unfortunately no software fix. I have three Pro1s. One (the oldest) has that issue to the point where the keyboard is almost unusable, the second has one or two keys that sometimes need two presses to react. Only my most recent device has a flawless keyboard.

    All three run the same version of my LOS16 ROM. So it must be hardware issues, I think.

    • Like 3
×
×
  • Create New...

Important Information

Terms