Leaderboard

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

Lineage-22.2-20250721-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

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

I will test it tonight with VoLTE off.

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.

Yes, my VoLTE was ON.

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?

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.

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.

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, Æ <-> Ø.

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.

Lineage-22.2-20250714-NIGHTLY-pro1x with July 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

Lineage-22.2-20250707-NIGHTLY-pro1x with June 1st security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

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