Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 07/20/2025 in all areas

  1. Hello, Soo today i have tested today touch fix on new display from ali. Method with goodix app does not work on los22...all was fine...selinux set, read data from display was working too, but after flashing new firmware phone makes reboot and nothing - still same. But method - flashing stock rom without wipe, wait for boot and then flash back los22 works fine 🙂 ...only reinstal magisk was needed
    4 points
  2. Lineage-22.2-20250728-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.
    3 points
  3. HI, the Lineage Juli Update maybe improved the battery drainage a little bit. Instead of going down from 100% to 30% during the night (meaning, the Pro1 was at standby and "Do not disturb" was activated) my Pro1 was emptying the battery to only 50%. Slight improvement, but still to much to use it during the day at work and so on. Last night I had "Airplane Mode" on and Wifi on too. VoLTE (4G-Anrufe in the phone localized to a German UI) was on. The battery was going down from 100% to 93%. This is approximately, what I had in the past before the update of Lineage to version 22.2. I
    3 points
  4. 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
    3 points
  5. Lineage-22.2-20250721-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.
    3 points
  6. ...i have i mean 2 flex spare cables and 2 small pcbs from top part - pcb between flex and display/camera/earpiece. I have repaired some fx and mainly not working display was not problem by flex but by pcb on top. Was needed to resolder flex connectors.
    2 points
  7. The only means of upgrading Android on the Pro1x is to flash Lineage OS, an ASOP-based alternative. The current official version is Lineage 22.2, which is AOSP Android 15. https://download.lineageos.org/devices/pro1x/builds https://wiki.lineageos.org/devices/pro1x/install/ https://community.fxtec.com/topic/4223-lineageos-22x-official-release-for-pro1-x-qx1050/
    2 points
  8. Lineage-22.2-20250811-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. I want to note that even though my Pro1x has working phone stuff, it has never demonstrated the battery drain problem on 22.2.
    2 points
  9. Spotted a more important bug that could be related with the battery waste as we discussed earlier. With the same sim in the same phone at the same location, and set for LTE only, here VoLTE works just fine on 22.1, but not at all on 22.2. So 22.2 CERTAINLY introduced some important bug in handling of carriers and bands (the sim is TDC in Denmark).
    2 points
  10. Due to the changes @Hook reported here, I tried upgrading to 22.2 (again). Will edit this post in some hours with the result.... ADD: And it is completely USELESS!!! Went from 97% to 47% in short of 8 hours. (Idle overnight, as much as possible uninstalled/disabled,,,,) Will go back to 22.1, or maybe stock and just forget about LineageOS, that (like the AICP project) seems to have F.. itself up to a useless state... Went back to 22.1, though over four months old still much newer than Android 9 in stock....,
    2 points
  11. I don't have any objective way of testing this, but I noticed that the change log for the last update and this one included references to carrier stuff. It seems to me that my phone call clarity has improved. The phone stuff actually worked pretty good for me from the get go. It wasn't perfect but far better than many people were reporting. But it seems, though anecdotal, that it has improved. Unfortunately, I don't really use this phone as a phone, as ironic as that it is for one that mostly works. So I haven't tried in a very long time, which makes this anecdotal report even more suspici
    2 points
  12. Lineage-22.2-20250804-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.
    2 points
  13. Lineage-22.2-20250818-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. A little slow on getting the Aug security patch.
    1 point
  14. I have not tried for a very long time, I just tried to adb reboot fastboot on the one on 22.1 and got a variant of the menu I've never seen before I can not remember what it used to fail with, maybe it was not until the flashing, OR something has been updated since last i tried.... On the one on stock the same command just reboots back into android. Booting into bootloader, it boots to android as soon as I attach a cable when in a direct port, but works fine in a port on the docking
    1 point
  15. I used my Pro 1 with VoLTE off during the past 3 days. At nights I set it to "Airplane Mode" on and Wifi on. For this, VoLTE off made no difference regarding the battery drainage. But during the day - with "Airplane Mode" off and "normal" phone usage, VoLTE off reduced the battery drainage. It is still not as good as with Lineage 22.1, but my Pro 1 survived the days without additional charging in the afternoon. The past two days were weekend days, where my phone usage is different to week days. Therefore I have to observe this a few more days. I also received a new 5G SIM card
    1 point
  16. I will test it tonight with VoLTE off.
    1 point
  17. Just to be clear, I wasn't suggesting not using a Pro 1 as a phone should be a solution for anyone. However, my defect led me to a diagnosis of the possible problem with Airplane Mode being a test. 🙂 I'm just lucky my problem doesn't affect me much because I happen to be weird.
    1 point
  18. Really weird. OH just retested. VoLTE by this carrier now works! (TEST: selecting LTE as only band, restart, and do a call). Does yours (clam to) do VoLTE? It could be interesting to turn it OFF/ON. If it for some odd reason relates to the battery bug. @TeZtdevice do you have VoLTE ON or OFF?
    1 point
  19. Except that, after maybe the first half of 2020, I have never used it as a phone. Same with my Pro1x although, in fact, my Pro1x actually works pretty well as a phone. They are pocket computers for me. I'm retired and don't do a lot of phoning, Mostly the phoning I do is related to my home health care of Mrs. Hook and I use a Pixel 7 Pro on Verizon for that as I need great coverage and reliability for that. 🙂 Other than that, I don't even give most people my phone number. I prefer asynchronous communication.
    1 point
  20. Sorry for the "delayed" answer. I didn't activate notifications. Therefore I did not realize your question earlier. I activated notifications now. My Pro1 was on the June release of Lineage. I just updated to the July release. I will report the effect of the update on the energy consumption in a few days. Just for information: I use the MicroG version of Lineage: lineage-22.2-20250719-microG-pro1 (https://lineage.microg.org/ and https://download.lineage.microg.org/pro1/). There are no GAPPS installed on my Pro1 and I have even removed most of the Google stuff that was in the ROM.
    1 point
  21. If on stock, use FinQwerty by @Anssi Hannula you can find it in the normal android market. to handle 1 and 7. (It really is not a running app as such, but presents the right configuration files for the wanted layouts to system on boot, so we an choose them side be side with the normal ones) PS Dansk og norsk layout er 99.9% identisk, Æ <-> Ø.
    1 point
  22. Are you still on stock Android, or have you updated to LineageOS? I recall the problem with Chrome refreshing the page from the fingerprint sensor was present in the stock Android, but fixed in LOS. IIRC, the work around was to switch to Firefox, if you don't switch to LOS. Some of your other issues might work better with LOS, too. No real downside to it, except for the time it takes to set it up.
    1 point
  23. Lineage-22.2-20250714-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.
    1 point
  24. Lineage-22.2-20250707-NIGHTLY-pro1x with June 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.
    1 point
  25. USUALLY the problems people experiences with fastboot is related to the communication with the watch. Either cable, port or driver. Silly as it may sound on Windows11, a 'newer' USB3 port might cause problems. On my Lenovo X1 Yoga gen 6 (20XY), I can not get fastboot to work directly. But if I use an old usb2 hub, things works fine. It also works fine if I go via my thunderbolt 4 docking, and a USB3 port on that. AFAIK, there are fewer issues if the machine is on LINUX. You might also try from an old PC with USB2 ports only. Usually it is not super picky on the cable, but try sw
    1 point
×
×
  • Create New...

Important Information

Terms