EskeRahn

Hmm, not in my case. It worked fine on 22.1, and now works fine back on latest stock android. Though I will not rule out if Lineage got the calibration wrong, and thought it was at 100% when it was not, and thus did not use the full span - I highly doubt it though. Much more likely that 'something' in the system got confused on the dirty flashing from 22.1 to 22.2 (or maybe rudiments from earlier dirty flashing, that kicked in going to 22.2) I really ought to have made a factory reset while on 22.2, to test before going to stock, but well I did not.... But anyone else seeing the bug, I

....For comparison here an old one from stock: Note that it is at 82% after 10h, and even among that MUCH lesser usage, a lesser portion is apps.

Hmm the below seems to say otherwise. But It MIGHT be the lacking factory reset that triggered the bug.

Well I'm now off the LineageOS wagon for a while, at the least until I get all transferred, a lot is omitted by google on transfer. Several important apps .... 😠 Note that I did NOT do a factory reset going from 22.1 to 22.2, so that MIGHT be the issue, and obviously would be the first to try for a support ticket.....

I just followed the guide at page 1, and took the liberty to adjust a few more details The line on userdata missed a destination Commented that you might want to skip flashing persist.img if from Android/LineageOS Added that you MUST do an extra factory reset from the settings, to use the full amount of memory. Hope that's OK @Waxberry🙂

The worn one is very worn due to daily usage since 2019, so a good time to upgrade. And no, have not bothered making an official report.

As 22.2 seems useless, I think I will try to revert it to stock, and make it my new daily driver, and then let my quite worn pro1 become the test device with Lineage 22.1, until 22.2 get usable or 23 is released - what ever comes first....

(lineage-22.2-20250503-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage. I have no idea whether the draining issue has been improved/fixed. Add: The draining issue is still there. From 100% to 18% in 11h, idle screen off, will recharge and turn off...

...tried again with both long press Power+VolDown hold to recovery menu and very-long-power press deep boot. And yet it is down from 100% to 90% in less than an hour... ADD: From 100% to 50% in ten hours. So horrible, but at the least slightly flattening out from the initial worse than 10% per hour.... ADD II: From 100% to 20% in 14 hours. 🙄

Hmm I already did a very-long-power press deep boot, to no avail. I did not try the Power+VolDown hold, but did that just now, so will report back with any difference, though I highly doubt it. It seems like something with the significant motion detection not being deactivated when locked. Maybe some silly fitness crap that I forgot to disable, or the upgrade enabled??

I can confirm the issue is their with yesterdays version also. 95% to 65% in just 4½h idle, screen off 'all' apps killed According to GSAM, it kept the Significant Motion Detector active for the full period, and I got no raise-to-wake or the like activated. ADD: 95% to 15% in just 13h !!! idle, screen off 'all' apps killed. When it has been recharged, I will turn it off and hope for better luck with next update... 😢

(lineage-22.2-20250426-nightly-pro1-signed.zip on April 5 security patch installed smoothly using adb sideload and MindTheGapps-15.0.0-arm64-20250214_082511) And we still can only select one keyboard layout, so no easy layout switching, for multilingual usage. Unfortunately I see no entries in the changelog that seems to address the power-wasting issue. But keep my fingers crossed...🤞

Interestingly, all reports OK here status.lineageos.org but still both manual download and OTA seems down?? Their recent history reports short bursts of outage, but is seems to have been continuously down for about a day. ...But strictly speaking you could say that it is not an outage as the page technically is answering It is just that it is not working and all direct device references go to the same page: Unable to contact upstream API ADD: They are back up 🙂

...And today download.lineageos.org/ seems down...

(The dotsrc.org mirror issue has been fixed)