Excessive battery consumption on latest LineageOS - Xperia Z4 Tablet Q&A, Help & Troubleshooting

Has anyone else exprienced this with the latest LineageOS from March 23rd?
I get <5 projected hours of battery usage with the main user "Android system" <- this is not normal.
Before I got 3 to 4 days projected usage.
I rebooted after power off for some time.
I could get new Gapps. Those I got are from last November.
I could roll back to LineageOS from March 16th.
Anything else?
What do you think?

Seems to be solved
FWIW:
I cleared system and cache partitions via recovery (spared the data partition).
Then flashed the LineageOS again and the latest GAPPs pico in one swoop.
Now I get 5 days of projected usage again.

Related

(mods please delete)

(delete)
Dougmeister said:
I had Android 4.1.1 installed on a rooted Sprint Galaxy S3 with ClockworkMod. Someone recommended TWRP, so I installed it and used the backup feature, thinking I was completely covered if my foray into ROM flashing on the SGS3 went awry.
So I booted to TWRP, did a "Wipe Data/Factory Reset", and installed the "Blazer" ROM; didn't like it. So I TWRP'ed again, wiped it and flashed CyanogenMod 10.1. Didn't like it either. So I went back into TWRP, did the "Wipe Data/Factory Reset" again, and restored my backup.
When it finished rebooting, it was good for like 20 seconds. I left it on the "lock" screen, and the date reverted back to Dec 24th at some ungodly hour (4 am?). It wouldn't unlock. After less than a minute, it reboots. It kept doing this.
I had a hard time getting back *into* TWRP. I kept getting this weird picture of the battery (?) and the phone kept buzzing every 10 seconds or so. The battery had at least 30% charge. Eventually, by taking the battery out, I was able to get back into TWRP.
Tried it again 2 or 3 more times with the same result. This last time, I immediately got off the lock screen and let it "sit". It has been stable (no lockups or reboots) for a few minutes now.
Any idea what's going on?
(If I'm leaving out important information, I apologize. Please let me know and I'll add it.)
Click to expand...
Click to collapse
Sprint ??? this is I9300 forum .
jje

Battery Life after updating to Lollipop

I recently upgraded my phone from 4.4.2 to 5.0.2. I upgraded it via the RUU method. My bootloader is unlocked, my phone is s-off and I rooted my phone after by flashing the supersu.zip file. I also wiped the cache and davlik cache after upgrading it. However, since then, the battery life seems worse. I have been using GSam battery monitor for a while now and it says that for App Usage, the Kernal (Android OS) is using about 25 percent, and Android System is using about 19 percent. Is this normal? My apps use a total of 75% of my battery while the screen only uses 20 percent. Any suggestions or tips and tricks? Thanks!
Just did the same thing with the exact same results. I may down grade back to the January global WWE RUU. How can it be so much worse!?

What are these CUST updates??

I was running a custom L ROM until recently... Switched to testing some custom M ROMs... went well, then decided to go stock M. I used a TWRP backup someone posted for the initial upgrade. It completed, and was a laggy mess. I ran that way for three days. No updates.
fast forward to now...
last weekend I flashed full, proper stock M ROM (the DLOAD folder trick)
Within 30 minutes of first boot, I got an OTA- Cust something or other update
I accepted it.
Now, I see a new section in About Phone- it's labeled Custom version
What the heck is this?
Dead_Dude said:
I was running a custom L ROM until recently... Switched to testing some custom M ROMs... went well, then decided to go stock M. I used a TWRP backup someone posted for the initial upgrade. It completed, and was a laggy mess. I ran that way for three days. No updates.
fast forward to now...
last weekend I flashed full, proper stock M ROM (the DLOAD folder trick)
Within 30 minutes of first boot, I got an OTA- Cust something or other update
I accepted it.
Now, I see a new section in About Phone- it's labeled Custom version
What the heck is this?
Click to expand...
Click to collapse
I saw the cust update in my updater and thought it was the result of downloading a custom recovery. However, I downloaded the full firmware package from the Huawei site and extracted it. The documentation also referred to cust. It appears that this update was so minor that rather than change the version/build, they just added in the cust part. Weird. But I went ahead and accepted the update through updater, and it installed just fine without wiping my apps and data. I did revert to stock recovery and unrooted before I did so, of course.
roflofogus said:
I saw the cust update in my updater and thought it was the result of downloading a custom recovery. However, I downloaded the full firmware package from the Huawei site and extracted it. The documentation also referred to cust. It appears that this update was so minor that rather than change the version/build, they just added in the cust part. Weird. But I went ahead and accepted the update through updater, and it installed just fine without wiping my apps and data. I did revert to stock recovery and unrooted before I did so, of course.
Click to expand...
Click to collapse
Noticed anything different? Does it run any smoother? I had to go back to CM13 as it just seems like my phone starts to slow down after a few days on stock MM.
jordant2 said:
Noticed anything different? Does it run any smoother? I had to go back to CM13 as it just seems like my phone starts to slow down after a few days on stock MM.
Click to expand...
Click to collapse
It's only been a day, but I'll say that there seems to be a slight improvement in battery life and memory utilization. Someone mentioned that this patch was supposed to improve the GPS performance but I haven't had a chance to test that. Speedwise, I haven't had any slowdown issues before or after the update. Then again, I'm coming from a 1st gen Moto E so by comparison anything else seems lightning fast. As long as they keep pumping out solid updates, I'm gonna stick with stock.
roflofogus said:
It's only been a day, but I'll say that there seems to be a slight improvement in battery life and memory utilization. Someone mentioned that this patch was supposed to improve the GPS performance but I haven't had a chance to test that. Speedwise, I haven't had any slowdown issues before or after the update. Then again, I'm coming from a 1st gen Moto E so by comparison anything else seems lightning fast. As long as they keep pumping out solid updates, I'm gonna stick with stock.
Click to expand...
Click to collapse
I got this cust update a few days ago and it seems to have fixed my GPS issues. Maps used to take forever to get a GPS fix and frequently lost the fix every few minutes. Now it gets a fix in seconds and I haven't had a dropout yet.
When I first installed the update, the internal storage was showing up as 2GB. Couldn't figure out why so I just did a factory reset and everything is back to normal (internal storage reporting as 16GB), and the GPS still works well after the reset.

Candy7 / CM13 ROM restarting loop issue

Hi everyone,
My phone has this restarting loop issue after flashing either Candy7 or CM13 ROM. Not sure if this is bootloop error because It got pass the Huawei booting logo, but as soon as it finish loading the Google App and go to the OS home screen it restart again and again. Worth noting that the phone restart from ROM loading logo (the blue face for CM13 or the Google Dot for Candy7), not all the way back from Huawei booting logo.
First I use TWRP to factory reset wipe, then advance wipe /system, /data, /cache / Dalvik, then install new ROM + Gapp, and got the sucess message, then reboot to system.
I also tried with out Gapp to save loading time, and it restart again when get to OS home screen.
Please advise what may cause this.
No issue when i restore back to B322 EMUI 3.1
I have US version unlocked MT2-L03, B322 version, unlocked bootloader, rooted, TWRP 3.1.1.0 installed.
I made a video clip of the looping: https://www.youtube.com/watch?v=Y7kRpdGN2qA
I'm going through the EXACT same thing. I tried CM13, CM14 and even CandyRom, and the same thing happened more or less. Even if I got the ROMs running for a while, eventually that LOD (Loop of Death) would hit and I'd have to again reflash. I'm now back to B322 (Lollipop) for stability.
Given that the SAME thing is happening on all those ROMs, it's leading me to think that perhaps there is a software issue with my phone. Not sure if this helps, but I do think it could be the way I updated to Lollipop (B322) from the original Jelly Bean (B148). I've done a LOT of digging, and it looks like the way I did it was not quite right, even though my phone has worked fine all this time.
Here is the XDA post that seems to detail the correct upgrade path to B322:
https://forum.xda-developers.com/ascend-mate2/help/how-to-update-unlocked-mt2-l03-to-t3422775
Basically, it looks like the correct path should be B148 (Jelly Bean) --> B309 (Lollipop) --> B322 (Lollipop)
Being rather new, I just flashed to B322 right off of B148. I am now wondering if this could be the source of my problems. Especially since I keep getting the "Error 7" for "unknown bootloader" whenever I use TWRP 3.1.1 to flash LineageOS or CandyRom.
But, if you successfully used TWRP 3.1.1 to flash, that means your bootloader was recognized (I got the Error 7). If that's the case, then we're both having the same issue and something else is indeed the culprit.
I strongly suspect that "something else" could be GAPPS. I've experimented with several GAPPS packages, and noticed that right before crashing and the dreaded infinite loop, something glitched involving Google apps.
Desperately want to leave Lollipop since Oreo is about to drop meaning we Android L users are in for a world of hurt if we can't migrate soon. :-\
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
My phone has been rooted for over a year now, I've had many roms on it doing that time. This loop started with a app I updated from the play store. Not sure it may be substratum will look into it when I have more time..
These problems is because of the room. Try to install lineageOs.
Thanks Kevinoriej,
Same looping issue on LineageOS, after loading to OS homescreen , phone restart.
Also get error 7, and manually remove "assert" lines in the ROM script in order to flash.
hondaman82 said:
I upgrade my phone B148-B309-B322. I also get error 7 whenever I flashed the ROM, so I have to manually delete '"assert" command line from ROM script to flash successfully.
Error screen shot: http://imgur.com/zzTbjRJ
Click to expand...
Click to collapse
I believe the Error 7 message is because your bootloader is showing as "unknown". I downloaded an app from the Playstore that gave me my device's technical info, and sure enough, my bootloader is listed as "unknown". I forwarded a question to Huawei's EMUI team asking them if that happened due to unlocking it (using Huawei's official unlocking request). Still waiting for a replay. In order to get any of the ROMs to install, I had to downgrade TWRP to 2.8.7.0. Any version above that would trigger Error 7.
Out of curiosity, I then downgraded and flashed CandySix (with a corresponding GAPPS package) - and sure enough, the same looping happened. And again when I flashed CM13 AND LineageOS. The phone would successfully boot, get to the actual Start screen, and then boot again. I could NEVER predict exactly what triggered this. Also, I tried installing ROMs without GAPPS, and that didn't go well for me (couldn't get any of them to load properly without flashing a GAPPS package for some reason).
Something goofy seems to be happening between Google services and the custom ROMs on this phone. I'm not sure what's triggering it, but given the sheer number of different ROMs I've tried - ALL of which have the EXACT SAME ISSUE - I strongly suspect there is indeed a GAPPS problem lurking somewhere.
As a side note - I reflahsed B322 (restoring from backup) and the phone is again as stable as it has always been.
Is there an EMUI GAPPS package for Marshmallow and/or Nougat (i.e., pulled from Mate 7, 8 or 9) available for download? I'm game for testing.
RE: MT2 boot loop
(*** SEE POST #25 FOR UPDATED FIX!***)
I just noticed this thread, wish I found it earlier. I recently posted my discussion of the boot loop (and fix) here:
https://forum.xda-developers.com/ascend-mate2/orig-development/cm-nougat-mt2-t3478345/page14
Bratzilla was right when he said in his post, "I strongly suspect there is indeed a GAPPS problem lurking somewhere".
Thanks EndlessFall,
please help to check this link: github(dot)com/opengapps/arm/releases/download/20170811/open_gapps-arm-7.1-pico-20170811.zip
no files listed.
RE: dead link for Open GApps previous versions & boot loop fix
Strange, it seems that in the past day Open GApps has purged their GitHub archive. The "Older Releases" button at their website still redirects to the GitHub repo, but it no longer displays any version other than the current one.
As long as it does not violate any policy, I can always post a copy of the Open GApps 08/11/17 ARM 7.1 Pico package.
Although I have not tried other GApps distributions (Delta, Beans, etc), in theory there is no reason why they shouldn't work, as long as Google Play Services is not newer than v11.3.02. I recommend the minimal GApps available. Installing "pico" was an important part of isolating, and simplifying the search for, the culprit.
As I mentioned in my original post, I tested all versions of Google Play Services on apkmirror newer than v11.3.02 (build format 436 for MT2L03), up until 08/26. All newer builds induced an immediate boot loop. A future version may resolve the boot loop issue and work fine on the MT2L03, but it does not seem to be available as of today.
Have been running custom ROMs on my MT2L03 for years. Boot looping problem began for me two weeks ago when I completely wiped/formatted my CandyROMs v7.1.2 06/15 install and flashed MDMower's 08/19 LineageOS. Began digging deep into the cause (knowing MDMower would not release garbage) and discovered the connection to Play Services. Have been running MDMower's LineageOS & CandyROMs v7.1.2 ever since without any issues.
Remember to use MDMower's TWRP v3.1N0-0, it is much more stable on the MT2L03.
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
RE: MT2 boot loop fix (workaround)
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
hondaman82 said:
Thanks again Endless,
I follow your instruction to flash Candie ROM and the matching GAPP from 6/15, all went well, no more bootloop. I will check the phone from time to time to see if the Loop of death come back, maybe once GAPP get updated it may come back. LOL... hopefully not though.
Click to expand...
Click to collapse
EndlessFall said:
Great, hondaman82 - so glad it worked for you. Funny, the exact same environment that you are using (06/15 CandyROMs with the matching 06/15 Open GApps) is what served as my "proof of concept" that current Open GApps with updated Play Services was likely the problem.
Although the proper GApps package resolves the boot loop issue, it is important to point out that it's more of a workaround than a fix. The root cause might be a bug in the AOSP/LineageOS source code itself, preventing MT2L03 compatibility with the latest versions of Play Services.
MDMower has just released a new build of LineageOS dated 08/29/17. I'll continue to test the latest ROMs with the latest GApps & Play Services to see if new commits/updates fix the problem...
Click to expand...
Click to collapse
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
RE: new ROM builds, GApps, & boot loop issue
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing (at least for me). Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
MT2-User said:
Have you had the chance to try 0829 Build of Lineage OS with newer GApps? TIA.
Click to expand...
Click to collapse
EndlessFall said:
Yes, I tested MDMower's LineageOS 08/29 last night using the 08/29 Open GApps package. Unfortunately, the boot loop bug persists. However, the 08/29 LineageOS runs great with Open GApps 08/11 and is worth installing. Hopefully MDMower will keep up the good work and release a build in the next week or two with the Sept security patch.
I'll continue to test and report back if there is any progress...
Click to expand...
Click to collapse
Thanks!
RE: return of boot loop
Sorry to hear that Hondaman82.
I can only speak from my own experience, which is that my MT2L03 has been stable for the past 2 weeks using Open GApps pico dated no later than 08/11. It is possible that your Google Play Services was auto-updated to a version newer than v11.3.02 (inducing the loop), but you won't be able to tell because you can't boot the corrupted OS to read the version number in app settings. If my boot loop returns, I'll do an ADB pull from TWRP to examine the Play Services package version (curious to see if there is an update correlation).
Goes to show what I mentioned yesterday, which is that the root cause is likely some incompatibility between the ROMs customized for MT2L03 and Play Services that can only be fixed by a commit to the ROM source code, a script, patch, or change to Play Services.
Let's see what happens, perhaps MDMower would be willing to offer his expertise? I visited Matt's website, GitHub and XDA profile, but it seems difficult to contact him directly....
hondaman82 said:
Oh nooo.. the LOD (loop of death) come back, after 3 days of working OK... sigh.... back to EMUI stock
Click to expand...
Click to collapse
RE: preventing Google Play Services auto-update
(***SEE UPDATED FIX IN POST #25!***)
For those of you willing to experiment further, there is a method that supposedly disables Google Play Services from updating. This might allow you to "lock in" v11.3.02 until there is a proper fix for the boot loop:
https://forum.xda-developers.com/android/help/delete-disable-downgrade-prevent-update-t3091832
Basically, this involves using a root file manager to create two empty folders entitled "com.google.android.gms-1.apk" and "com.google.android.gms-2.apk" in the "\data\app" directory, causing auto-update to fail.
I haven't used this hack, try at your own risk!
Of course, this works off of the assumption that updating Google Play Services beyond v11.3.02 is the only factor involved in the boot loop. I just haven't dug deep enough...
Mine (Candy 0725 build) went into LOD by itself a moment ago
Does anyone have a B322 TWRP backup ZIP? I as of this morning have 2 MT2 phones dead. One went into LOD about 3am and the other about 4am.

[ROM][11]LineageOS 18/18.1 Z4Tablet[SGP712/771]

There is Android 11 ROM for Xperia Tablet Z4.
It's quite stable.
Kernel sources
What doesn't work:
- when the tablet is off, during charging, the diode will always light red;
- external SD Card as internal storage;
- restart into recovery;
- tablet encryption;
- SELinux proper configuration for a proper security.
How to install:
1) use TWRP 3.5.0.
2) do factory reset (wipe)
3) Flash the firmware, nik,bit or flamegapps , magisk 21 and that’s it.
Change log:
20201206- initial build.
Last builds (mirror) are here.
Sabar_op link
We must be infinite grateful to sabar_op for his hard work in development of this rom and Bernie and Tarkzim who help to update kernel for kitakami devices. :good:.
I found that I cant install vanced YouTube with lucky patcher or SAI, with vanced manager it's OK. But root version says google services is not supported on this device. I checked with both bit and nik gapps, but no luck. Anyway to use root version with los 18?
Update new rom dated on 11 Dec 2020 :
- camera now works
- fix some sepolicy denials.
I found that "reboot to recovery" doesn't work. Only Power + -val is only way to get the recovery.
Thanks for the R version for our device.
I found an issue on play store. I can't download some games (like Walking Dead Road to survival for example). When install begin it stop and an error appears.
lvtz said:
Thanks for the R version for our device.
I found an issue on play store. I can't download some games (like Walking Dead Road to survival for example). When install begin it stop and an error appears.
Click to expand...
Click to collapse
Send me the log pls..
sabar_op said:
Send me the log pls..
Click to expand...
Click to collapse
I already came back on Android 10 to install games. Try on your side if you can with the game mentionned above please.
alex009988 said:
I found that "reboot to recovery" doesn't work. Only Power + -val is only way to get the recovery.
Click to expand...
Click to collapse
Thanks for the report. Not sure why like that, perhaps due to LOS18 is still beta?
sabar_op said:
Thanks for the report. Not sure why like that, perhaps due to LOS18 is still beta?
Click to expand...
Click to collapse
Best ROM for the best Android tablet. Thanks for your work.
lvtz said:
Thanks for the R version for our device.
I found an issue on play store. I can't download some games (like Walking Dead Road to survival for example). When install begin it stop and an error appears.
Click to expand...
Click to collapse
The same thing with war robots.
Battery consumption on karen-windy is huge as always on this. The android system itself lost 46% in 12 hours idle.
frode_ said:
Battery consumption on karen-windy is huge as always on this. The android system itself lost 46% in 12 hours idle.
Click to expand...
Click to collapse
True. Battery drains to 0% when leaving the device switched off or on! Red LED stays on even when device switched off..
Any fix available or updated builds?
else need to revert back to stock...
rb69 said:
Any fix available or updated builds?
Click to expand...
Click to collapse
Sabar made Los18.1 build which should reduce battery consumtion. But it also brings new bugs, no exfat for sdcard, half of screen is disabled after wakeup in many cases. I hope it'll be fixed soon.
Half black screen bug is fixed with 20200103 rom. You may need also to reformat sdcard as external storage.
How's the battery consumption?
jelbo said:
How's the battery consumption?
Click to expand...
Click to collapse
I remember los15 and 17 had serious problem with battery consumption so it was hard to use, now it's better. I use now aicp 16 but I was using stock marshmallow 32.2.A.5.11 several days ago. The stock is amazing, fast, no kernel panics, bugs at all. But I had a battery life there only for one day even with stock, as I have it with custom los14. So los14 maybe is more battery consuming a little bit. But don't except that android 11 is less buggy and battery consuming than los14.
As far as I tested android 11 it's more or less OK, even for now it can be used for daily usage. But it will likely to be a bit worse than los14 according to battery life. I think you can backup the stock with twrp 3.4.0 and try android 11. If it's not OK for you, you can easily restore the stock by twrp.
alex009988 said:
I remember los15 and 17 had serious problem with battery consumption so it was hard to use, now it's better. I use now aicp 16 but I was using stock marshmallow 32.2.A.5.11 several days ago. The stock is amazing, fast, no kernel panics, bugs at all. But I had a battery life there only for one day even with stock, as I have it with custom los14. So los14 maybe is more battery consuming a little bit. But don't except that android 11 is less buggy and battery consuming than los14.
As far as I tested android 11 it's more or less OK, even for now it can be used for daily usage. But it will likely to be a bit worse than los14 according to battery life. I think you can backup the stock with twrp 3.4.0 and try android 11. If it's not OK for you, you can easily restore the stock by twrp.
Click to expand...
Click to collapse
Do you use this marshmallow firmware with AICP 16 and LOS 18 ? If no, which one ?
And what about kernel panics, reboots and some games impossible to install on play store on your side on LOS 18 ?
lvtz said:
Do you use this marshmallow firmware with AICP 16 and LOS 18 ? If no, which one ?
And what about kernel panics, reboots and some games impossible to install on play store on your side on LOS 18 ?
Click to expand...
Click to collapse
I haven't used stock for years, but some days I've gone back to it just to see and find out what about root here. The last nougat there has no way to get the root, so I've downgraded to marchmallow. I also uploaded some stock ftp to my cloud.
Now I used aicp. Kernel panic are possible here but over two days I havent faced a one.
And yes, big games like war robots and call of duty are impossible to install with all nik, bit and flame gapps. There is some storage permission problem even though that I gave the neccesary ones. But you can find the games on 4pda.ru download and install them. The other bug is that vanced root YouTube doesn't work with all three gapps too. Maybe the reason of two problems there is still no opengapps for android 11.
I found some info about YouTube bug https://github.com/YTVanced/Vanced/issues/201
There is the error when downloading war robots.
01-07 18:15:19.260 E/Finsky:download_service(10456): java.io.IOException: Can't create file:///storage/emulated/0/Android/obb/com.android.vending/com.pixonic.wwr/temp.main.106419.com.pixonic.wwr.obb
So I decided to check storage/emulated/0. I tried ES file manager and root explorer. And find that emulated folder is empty. But it should be not. Maybe be its a clue.

Categories

Resources