EskeRahn
-
Content Count
5,881 -
Joined
-
Last visited
-
Days Won
378
Posts posted by EskeRahn
-
-
....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.-
1
-
-
5 hours ago, TeZtdevice said:
Updated / now closed ticket:
No such drain here - must be something you're doing mod or app wise.
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.....-
1
-
-
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🙂
-
2
-
3 minutes ago, CornholioGSM said:
BTW have you reported battery problem on lineageos gitlab?
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....
-
1
-
-
(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...-
2
-
-
...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. 🙄-
1
-
1
-
-
3 hours ago, Hook said:
However, now I need to try it with my Pro 1, which I haven't used much for a couple of weeks.
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??
-
1
-
1
-
-
23 hours ago, EskeRahn said:
Unfortunately I see no entries in the changelog that seems to address the power-wasting issue. But keep my fingers crossed...🤞
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...🤞
-
2
-
-
15 hours ago, EskeRahn said:
...And today download.lineageos.org/ seems down...
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 🙂-
1
-
-
...And today download.lineageos.org/ seems down...
-
1
-
-
(The dotsrc.org mirror issue has been fixed)
-
I see a VERY horrible stamina after the 22.2 updates!!!
It usually last for about four days on a charge, now it depletes over night (95% to 23% in 14 hours while idle on a table with display off, AND all user apps killed with Greenify as usual)
It MIGHT be related to "Significant motion detector", But I would strongly recommend to avoid upgrading currently.-
1
-
-
13 hours ago, Hook said:
I don't really understand what mirrorbits is or what it's advantages are (even after reading their Github, lol), but Saturday's Pro1 update downloads just fine from the official Lineage download sites. Just FYI for folks.
Maybe they use different regional mirrors, but it does not work here from their official site, that points to
https://mirrorbits.lineageos.org/full/pro1/20250419/lineage-22.2-20250419-nightly-pro1-signed.zip
that then reroutes to thepage that is (still) down -
As the download is still unavailable I did an OTA that WAS available. So now on
lineage-22.2-20250419-nightly-pro1-signed.zip on April 5 security patch-
1
-
-
...Anyone else having trouble fetching (the new) files from mirrorbits.lineageos.org ? (tried to fetch an older file with same result)
Known issue -
17 hours ago, claude0001 said:
So what about the LineageOS 22.1 ports for the Pro1 and Pro1X? Do they include AVF or not?
22.2 is the newest on the Pro1, and most likely on Pro1X on next release in a few days. I have no idea on how to check if it got "AVF" or not..... But if you could guide...
ADD: I tried on un-rooted Pro1 to check if I could see a folder
"/apex/com.android.virt/bin" also just "/apex"
And it reports that it does not exists (and not merely that I do not have the permisions to see it" -
(lineage-22.2-20250412-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.
-
2
-
-
(lineage-22.1-20250405-nightly-pro1-signed.zip on March 1 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.
-
2
-
-
(lineage-22.1-20250329-nightly-pro1-signed.zip on March 1 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.
-
2
-
-
3 hours ago, daniel.schaaaf said:
Sorry to disappoint you, I own the older Pro1 model. I edited my posting accordingly.
Maybe I misunderstood what I read in this thread. I got the impression that even for the Pro1 we would have to re-flash Android, and I was excited to see that the app was able to flash the display directly on a running LOS.
Oh indeed this is also simpler for Pro1, but would be really great if it also worked for pro1X, where there are no known fix at all (except using a Pro1 to do it)
-
6 hours ago, daniel.schaaaf said:
Essentially, Kaali said it all and provided the correct files. I uploaded translated and modified instructions as a PDF.
This is very interesting, and seems a LOT easier than flashing to stock on a Pro1. But I lack one crucial detail, did you do this on a Pro1 or a Pro1X. It would be SO great if you provided a method for finally doing this on a Pro1X, as this has previously not been known (previously the trick was to mount the display on an a mule Pro1, and flash that to stock, and then move the display back)
-
1
-
LineageOS 22.x Official Release for Pro1 (QX1000)
in General Discussion
Posted
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 would strongly recommend to try a factory reset (after suitable backups obviously)