All Activity

Updated / now closed ticket: Nolen Johnson1 hour ago No such drain here - must be something you're doing mod or app wise.

Definitely do not have the battery drain with Google-less Pro 1 on Lineage 22.2. I will make the MTG test tonight.

It's too early to say.but almost an hour later, I am not seeing excessive battery drain on my Pro1 after updating from 22.1 to 22.2. I did a simulated battery pull right after updating. If this continues, I will have to further experiment because this is a Google-less installation. Cornholio's comment got me thinking-- what if the problem is actually MTG? That is the primary difference between Official and Oddsolution. It would be odd if that were true because I am not seeing the battery drain at all on my Pro1x, but it was a much older version of MTG that I first installed on that a

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.....

hmm...you have problem after upgrade to 22.2...thats wierd. I am from - i am not sure - january on 22.2 oddsolution and battery looks same as on 22.1. Official and unofficial are same i mean - only on unofficial are integrated gapps

Well, that´s my first ticket 🙂 Let´s see, what happen https://gitlab.com/LineageOS/issues/android/-/issues/8767

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.

...i am not sure but maybe you can dirty flash oddsolution version. I am on 22.2-20250422-UNOFFICIAL-pro1 and no problem with battery. BTW have you reported battery problem on lineageos gitlab?

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-20250505-NIGHTLY-pro1x with April 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained.

An updated build of LineageOS 16.0 for OG Pro1 (qx1000) is available for download at: https://findus.zwergenschaenke.net/~puma/linux.html#lineagepro1 The build dated '20250504' gives you backported security fixes from the Android Security Bulletin up to the "1 April 2025" patchlevel, and updates the bundled WebView to Chromium 135.0.7049.100. Otherwise no changes with respect to last month's upload. Have fun.

(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...

Lineage-22.2-20250503-nightly-pro1-signed.zip on April 5 (2025) security patch, installed smoothly using OTA I have to charged my phone 3-4 times per day 😔 Update (05.05.): 06:30am with 85% battery => 11:00am with 22% battery (screentime about 30min.) At this time, I missed my old phone with TWRP. If something went wrong... restore to an old backup in 10min.

On my old second device I have exactly these issue. My plan was to reflash android, to use my new dispay on my daily driver (LOS 22.2). Any ideas? Second device hast stock android 9 ; unlocked ; not rooted For my main Pro1 and my spare Pro1 I use the same adb drivers, notebook, usb cable and usb port. UPDATE: I have to execute a batch file, to edit the registry of my Win11. You can find the file, if you search: How to fix press any key to shutdown fastbood error After that, I phone is still in fastboot mode

Just wanted to follow up with my camera lens cover repair in case anyone else need the info. I used a heat gun to loosen the glue. It was just a few seconds and I was able to ply out the glass with a dental sharp tool. I was careful not to scratch the camera lens itself. Cleaned the residual glue with rubbing alcohol and Q tips. Once again thanks to CornholioGSM's tip on the Redmi Note 7 glass I ordered it. It was the exact size, except that I had to install it upside down (the writing will be upside down) so the larger opening is on top. Nice not to have halos in my pictures. Thanks

Lineage-22.2-20250428-NIGHTLY-pro1x with April 5th security patch installed smoothly via OTA. MindTheGapps15, and root was maintained. I think the April 1st dates in previous posts was a typo I kept perpetuating. Lol. So far well behaved, battery-wise. Lost 3% in 2 hours including activity post-update. Edit: Looks good. 7 hours, yes, mostly idle, but has only dropped 10%. That's par for the course given that I have background mail, dropbox ans calander syncing.

So, I discovered my Pro1 is still on 22.1. So I will get a baseline as-is, and then I'll update. It's also Google-less for now, so I'll see what happens.

Thanks chief That worked for me too, though now my GPS is all over the place. I got lost while driving round because it couldn't lock onto my location. I use my phone as the sat-nav fairly regularly, so this is a weird one for me. Hoping the sat-nav issue is a Lineage6 22.- update issue rather than a problem with the Network type.

...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 am actually seeing much better battery performance after the simulated battery pull. My Pro1x only dropped from my max of 85% to 77% in 7 hours, and my Pixel only dropped to 80% with quite a bit of use. I'll keep monitoring just to make sure I'm not jumping to conclusions, But I have to admit simulated battery pull is my go-to for weird stuff happening. However, now I need to try it with my Pro 1, which I haven't used much for a couple of weeks.

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... 😢

I think I am also seeing it on my Pro1x. I'm testing this week-end. But I also have been getting unusual battery drain on my Pixel 7 Pro. Coincidence? Or is the problem an Android 15 update problem and not a purely Lineage problem. I did a simulated battery pull on both devices (to clear out janky stuff going on and will watch both.

Lineage-22.2-20250426-nightly-pro1-signed.zip on April 5 (2025) security patch, installed smoothly using OTA. I can confirm the issue with the energy usage, since LOS 22.2