I was using the stock rom rooted 30d and I started to have battery issues, it showed 30% then 40% then 2% and bootloops with gps applications, and time date issues, I changed the battery, the gps problems disappeared battery changing disappeared, but I get occasional bootloops when battery is less than 10% or random date time errors, I reinstalled everything and used the 30e version, problem still persists what do you guys recommend flash instead with lg tool, and reroot? or any other suggestions? thanks
Related
Hi,
I'm using s4 mini LTE I9195 with CM11 M6, f4ktion 1.4.0 kernel, BN3 modem, TWRP 2.7 recovery
All was working fine, average battery drain on idle was 1%-2% (not great, but fine), and suddenly it rocketed to drain 15%-30% per hour.
I usually use Android Tuner's battery measure stats to track drain statistics over time.
After checking it, I"ve noticed that it () the drain) started in the middle of the night.
So it's not due to "I launched this App, and then..." It just went nuts on it's own...
I've checked which process is to blame and the first one with max battery consumption is:
com.android.systemui (with KitKat logo) followed by Android System, then Screen, and then all the usuals.
I tried to do reboots, disable wifi/nfc/rotation/data/sync/anything else/kill user apps - no effect ...
It still drains about 20% per hour on system and systemui for the whole day now :crying:
And I have no idea what causing it / how to revert it...
So, do you have any suggestions on how to trace this bug?
What to search for in logs?
Any thing else?
I'm not a big pro on android OS subsystem, so advises are welcomed!
I'd love to help, but I actually stumbled upon this thread while googling to help myself
I'm using Note 2 (N7100), running CM11 - newest nightly (although I flashed it today, after slightly recharging the battery once I noticed the problem) and Devil3 kernel.
I'm having the same issue - yesterday everything was fine, I've left the phone to charge over night and display time as usual and in the morning nothing seemed out of the ordinary, until 6 hours later. After those 6 hours my battery was fully depleted (whereas normally lasts whole day and is not even close to being depleted). com.android.systemui and Android System seem to be the problem for me too.
I've also tried turning off some functions, uninstalling some apps, turning off notification privileges for others. Even, as said earlier, flashed newest nightly. Nothing helped. Using phone with without flashing Devil3 kernel didn't help.
Anyone have any ideas?
Just try to flash stock software and again CM.
Try a older version of CM11, and if stability is a priorty stay on CM 10.2
OK, so I've tried a few things, and had a few surprising outcomes:
I've analyzed the CPU load with various tools, as Android Tuner, OS Monitor, and All-In-One Toolbox.
Most of them reported Android System using 30% CPU, and com.android.systemui using 25% CPU, all on the highest frequency.
But All-In-One Toolbox recognized top process instead of Android System as Lockscreen android process, so maybe there is a hint there...
(and I don't use any custom lockscreen stuff beyond stock CM's one)
So, backed up the current troublesome system (let's call it BKP_NEW), just in case, and decided to restore a full NANDroid backup I had from a week ago (and the issue is just from yesterday).
Restored all 6 partitions (/system, /boot, /cache, /efs, /modem, /data), rebooted, and....
...The issue was still present! Crazy battery drain just as before!
Very confusing... Then I went for a factory reset - it fixed the issue, but I have to start from scratch with all the SW installs and config, and I don't have a week to waste setting everything up again, and potentially running into the same issue some time later.
So, I've decided to move further back, and restored a two week old NANDroid backup > reboot > No issue presents
But it was just too weird, since the delta between 1-week old and 2-week old backup is infinitesimal.
So, out of curiosity I've decided to restore the BKP_NEW (the one of the system with the issue present)... and after the restore it works just fine! (WTF?!?!)
After thinking on it for a while, my conclusion is that there was some problem with some part of system that was wiped/fixed in TWRP's Factory Reset, but is not touched/overwritten during the NANDroid 6-partition restore.
But again, this is just my assumption, need someone more knowledgeable to confirm this possibility...
(maybe @ne0zone75 can advice on this?)
Since that, all is working fine (at least so far).
And if my assumptions are correct, @Ksenios, you can try to do this, and still have working system with all apps and configs (If youre comfortable with recovery / backups management).
hi,
(passing bye from google - just a note)
com.android.systemui cpu high usage (about 37%),
on my huawei media pad x2 (gem702l) but only while charging (and just sometimes), if that gives something for someone, any clues why ?
A fair number of unlucky LG G3 owners using AOSP/CM-based ROMs, myself included, have a major problem with the issue where a reboot/power-on cycle results in the phone getting stuck at the LG or boot splash screen ad infinitum.
The only way around it is to do a battery pull, sometimes several times, before the phone eventually recovers, but not until after it's gone thru its "Optimizing" or "Upgrading" apps, which takes 5-10 extremely annoying minutes.
I'm using a D851 and have this issue with every ROM I've used (Xenon, Exodus, AICP, to name a few).
This is not a battery issue as I've had the same problem using batteries from 3 different manufacturers. I've also had the same problem when plugged in.
If anyone knows of a fix - would be greatly appreciated (please don't say factory reset or root back to stock - I've already done this and it doesn't fix this issue).
I also have this problem with aosp and cm roms, i also get bsod sometimes. I think that maby the battery is broken, but im not sure since i dont got any problems on stock. When i get money for a new battery i will reply here with results.
I got my new battery today and it bootet up instantly
I had this issue on my d852 running cm12.1. It turns out using autorec is what caused it for me. I fixed it by flashing a kitkat tot then installing twrp using flashify. Once I had twrp installed I flashed the modem.bin from a lollipop d852 kdz. I haven't had a shutdown/reboot hang in a week now.
I have the same problem D851, it happens on latest builds of exodus and aicp. candy and blisspop works fine without any issues. I have changed the battery but the problem persist on exodus and aicp
A couple weekes ago i rooted my phone and flashed fulmics 6.9. Then 1 or 2 days later i flashed Lineage OS, but because i didnt have some of the stock apps from LG that i use (QuickMemo+ and LG camera app) i flashed fulmics rom again. I decided to root the phone and flash a custom rom because the phone started to get laggy and the battery life wasn't the best. But then i start experiencing a restart loop on the fulmics rom. I then tried to do a clean install of fulmics rom again, but because of the constant restart loop i only managed to successfully install it again while plugged on the charger. I googled for a solution and found out that it could be a battery issue. I then tried to flash Stock v30B rom but without success (because of the restart loop once again, and also the flash software kept saying that it lost connection with the phone). I then took my brothers battery (He has the same phone, LG G3 D855), and successfully flashed the stock rom (v30B), but when i put my battery again it started to restart again in loop. After some testing i found out that it only happened when the battery was about 20/40% and everytime it restared, the battery percentage wasnt correct (I got drops from ~ 40% to 5%), and if i removed the battery from the phone for a few minutes it would show incorrectly again but with more percentage (like 25% instead of 5%), i even tried to calibrate the battery but with no successfull results. I then bought a new battery (supposedly original) and from my tests the restart loop stopped, but now the battery drains on iddle like it drains while using (It went from 100% to about 70/60% until it "stabilizes"). I researched for a solution and found out that it could be background apps and installed greenify and it seems to have improved a bit but nothing significant, and enabled airplane mode after that and it improved even more, but once again, nothing significant (I still think it drains more than normal while on iddle). When i rooted and flashed the roms i was on stock v30N and never have rooted the phone before that, and tried to follow all steps correctly so i wouldnt damage anything. Currently im on stock v30N again. And i've had experience with root and rom flash before, and never had any problems. My phone is almost 2.5 years and never had any issues with it or the battery, and also im now using the same apps as before.
Is it possible that i damaged the phone somehow during the root and rom flash process? or im just unlucky with the batteries ?
Note: The tests i conducted with greenify and airplane mode only went for a couple hours (still testing right now), maybe it needs more time so i note any difference.
Sorry if i mispelled something wrong (Im Portuguese ).
Vimaraes said:
A couple weekes ago i rooted my phone and flashed fulmics 6.9. Then 1 or 2 days later i flashed Lineage OS, but because i didnt have some of the stock apps from LG that i use (QuickMemo+ and LG camera app) i flashed fulmics rom again. I decided to root the phone and flash a custom rom because the phone started to get laggy and the battery life wasn't the best. But then i start experiencing a restart loop on the fulmics rom. I then tried to do a clean install of fulmics rom again, but because of the constant restart loop i only managed to successfully install it again while plugged on the charger. I googled for a solution and found out that it could be a battery issue. I then tried to flash Stock v30B rom but without success (because of the restart loop once again, and also the flash software kept saying that it lost connection with the phone). I then took my brothers battery (He has the same phone, LG G3 D855), and successfully flashed the stock rom (v30B), but when i put my battery again it started to restart again in loop. After some testing i found out that it only happened when the battery was about 20/40% and everytime it restared, the battery percentage wasnt correct (I got drops from ~ 40% to 5%), and if i removed the battery from the phone for a few minutes it would show incorrectly again but with more percentage (like 25% instead of 5%), i even tried to calibrate the battery but with no successfull results. I then bought a new battery (supposedly original) and from my tests the restart loop stopped, but now the battery drains on iddle like it drains while using (It went from 100% to about 70/60% until it "stabilizes"). I researched for a solution and found out that it could be background apps and installed greenify and it seems to have improved a bit but nothing significant, and enabled airplane mode after that and it improved even more, but once again, nothing significant (I still think it drains more than normal while on iddle). When i rooted and flashed the roms i was on stock v30N and never have rooted the phone before that, and tried to follow all steps correctly so i wouldnt damage anything. Currently im on stock v30N again. And i've had experience with root and rom flash before, and never had any problems. My phone is almost 2.5 years and never had any issues with it or the battery, and also im now using the same apps as before.
Is it possible that i damaged the phone somehow during the root and rom flash process? or im just unlucky with the batteries ?
Note: The tests i conducted with greenify and airplane mode only went for a couple hours (still testing right now), maybe it needs more time so i note any difference.
Sorry if i mispelled something wrong (Im Portuguese ).
Click to expand...
Click to collapse
I have been testing the iddle battery life with greenify for a while now and it improved a bit, not nothing major. Any thoughts what it might be ?
I'm absolutely losing my mind please help
A little story time, skip to the end for my question;
So, how to start - One day I unlocked my bootloader, went for some android 11 rom and all was fine. Then android 12 was released and I downloaded the crdroid 12 rom, where I was experiencing some battery drain issues. So I downloaded pixel experience rom. The Bluetooth died because of this rom's cursed source code. I flashed the latest miui fastboot rom and the Bluetooth issue still persisted (remember this for later - not all the drivers flash with the Rom). I fixed the Bluetooth issue by switching several miui roms, also made a guide if you're interested. That fixed the Bluetooth issue and I went for pixel plus ui rom. It was a bit laggy, so I switched to the shiny new Evolution X rom. It was amazing, so much stuff co customize, etc. Well, i experienced another battery drain issues, so I just went for the stock miui with magisk pixelify module. Im pretty fine with this rom, and I thought the problems are gone, because it stock and everything should be fine. Well no. The battery drain issue persists. I was wondering what even is happening, so I opened battery settings. That said that the top apps wasting my battery is screen, Google services and android system. I downloaded a CPU usage stats app, which showed me that the cpu usage is at 99% (I think it's correct as the phone is overheating). The app with most cpu usage was using only 1%. I don't know if this is a firmware bug or whatever, but I think some rom broke it and the latest stock miui didn't overwrite that driver, as written above with the Bluetooth issue.
So, how can I make my phone be as it was released from xiaomi with all the drivers to actually use the hardware correctly?
Thanks in advance for any replies, I'm seriously going to throw my phone out of the window
Also the way how I install the stock Rom is by downloading the latest fastboot rom, extracting it and executing ./flash_all.sh file.
SOLVED! My problem was because of my credit card. I have my cc in the phone case. The cpu was going insane because it was constantly detecting the card and loading info from it. Literally turning off NFC fixed this whole issue. Bruh.
Since the last few updates, even on a fresh install with nothing installed. My LineageOS in Alioth has been using 7% to 11% /hr of battery on a fresh install with no extra apps added. Tried doing a clean install, reset to factory, even tried reseting battery stats. Sadly cant do anything about it and I'm not being able to go back to versions I knew worked OK (19.1-20220723 for example since i dont have an img to use and lineage page only have the latest).
Most battery, about 55% is consumed by Kernel. Has anyone had the same issue?
Not sure what else to do and really don't want to go back to MIUI.
I got similar issues a few Updates back, it was related to some Magisk modules I used. After removing them the battery drain stopped.
Try getting the logcat output and see if something is reported there.
Also make sure you are using the right firmware.
Thanks for the advice Boracho, but this is happening on a 100% clean install. Not even gapps on it.
Did clean installs of both OS and recovery versions 19.1-20220917, 19.1-20221001 and 9.1-20221008... all had the same problem. Finally remembered I had 19.1-20220723 in a pendrive. Installed it. Works just fine. Battery problem is gone.
Disabled auto updates. The end.