Related
I've tried several different ROMs (AvaV10, Cyanogen, Fresh, NonSense), along with different kernels (pretty-much any that I could find), and I simply can not get my phone to sleep. It's always at 100%, no matter what I do.
In Spare Parts I'm getting:
Other Usage - Total in all time:
Running 100.0%
(everything else under 10%)
Partial wake usage - Total in all time:
Android System ~35%
UID 10027 ~20%
(everything else under 10%)
Network Usage - Total in all time:
0 - 100%
Dialer ~40%
Android System ~50%
(everything else under 20%)
So now my question is, what is the "0" that shows up at 100% in my network usage? No matter what I change, I can't seem to get rid of that "0".
I'm on:
HBoot 2.10.0001
Radio 2.15.00.11.19 (I've tried 09.01 also)
Newest WiMax, PRI, and NV.
AmonRa Recovery v1.8.0
Multiple wipes on everything, nothing works.
The problem started about a week ago, and I simply can't figure it out. I've changed everything I could think of. I was originally on Radio 09.01, and I updated, but this was after the problem started. I also updated my HBoot from 0.97 after the problem started. Nothing seems to be working.
Note: I've also tried airplane mode, this does not help.
Solved using Calkulin's wipe method
I'm getting pretty good results from my setup.
1. Myn's Warm rom rls4
2. New kernel- I just downloaded last night but the battery stayed on 100% for quite a while. Here's the link- http://forum.xda-developers.com/showthread.php?t=876590&highlight=calkulin's
3.Riptide9's ColorNclear theme with several of the addons, speedo batt, blue dialer, launcher pro (the update for warm2.2 themed).
I myself have tried probably every rom out there that has working 4g, I dont see owning an evo and not having 4g, and found this one to be the best. You do have to do an update to the wireless tether, can be done through the app itself. Hit me up if you need assistance. If it is the batt life you're primarily concerned with, this kernel is supposed to be awesome. Check it out, mine is overclocked to 1152000 and it still stayed at 100% for a good amount of time after being taken off charge. If you try it and like it let me know. I like to know that I was able to help someone.
Try removing your SD card and see if it still has that issue.
I suppose I should have mentioned why I need a fix so badly...
I'm only getting ~4 hours of battery life. I go into work at 6:30am and when I leave for lunch at 11:30, my phone is dead (with absolutely no use).
I need to figure out what this "0" is in "Network usage" because that's what is keeping my phone awake 100% of the time. Like I said though, even Airplane mode doesn't fix it (I don't see why something is using my network in airplane mode).
I tried removing the SD-card, that didn't help.
I've already tried the kernel that you linked to, that didn't make a difference... Same issue, my battery just drops.
If I'm doing something, I can literally just watch it drop in front of my eyes. If I'm using the phone (browsing the web, checking email, etc...) it drops one percent about every 20-25 seconds (I get something like 40-45 minutes if I'm using the phone before it dies).
maybe you have a faulty batt. I dont know.
Have you tried completely starting from square one?
titanium backup, then wipe everything, wipe again, and flash the stock rooted rom (or maybe even the OTA and re-root later).
After flashing, reboot your phone but dont restore your backup yet. See what happens, then slowly restore apks and files, etc, one at a time and see how the battery acts.
I don't know what the "0" means, sorry. But maybe this will help you figure out what is causing the problem.
Harfainx said:
I've tried several different ROMs (AvaV10, Cyanogen, Fresh, NonSense), along with different kernels (pretty-much any that I could find), and I simply can not get my phone to sleep. It's always at 100%, no matter what I do.
In Spare Parts I'm getting:
Other Usage - Total in all time:
Running 100.0%
(everything else under 10%)
Partial wake usage - Total in all time:
Android System ~35%
UID 10027 ~20%
(everything else under 10%)
Network Usage - Total in all time:
0 - 100%
Dialer ~40%
Android System ~50%
(everything else under 20%)
So now my question is, what is the "0" that shows up at 100% in my network usage? No matter what I change, I can't seem to get rid of that "0".
I'm on:
HBoot 2.10.0001
Radio 2.15.00.11.19 (I've tried 09.01 also)
Newest WiMax, PRI, and NV.
AmonRa Recovery v1.8.0
Multiple wipes on everything, nothing works.
The problem started about a week ago, and I simply can't figure it out. I've changed everything I could think of. I was originally on Radio 09.01, and I updated, but this was after the problem started. I also updated my HBoot from 0.97 after the problem started. Nothing seems to be working.
Note: I've also tried airplane mode, this does not help.
Click to expand...
Click to collapse
You need to do caulks format all as it will wipe everything that the recovery misses. Hope that helps
Sent from my PC36100 using XDA App
Excellent, I got it working!
Performing Calk's wipe, and doing a fresh install seems to have it working again. I was thrilled to see that I wasn't at 100% after setting my phone down for 20 minutes to let it sleep.
I've been installing apps one by one hoping that something doesn't break it again.
I still have no idea what was causing the problem, but it's fixed now. Thank you for the help everyone, especially Craigbailey for the advice and Calkulin for the fix.
So I'm having this exact same problem (100% time running), but Calkulin's format all did not work for me. I ran it, flashed a brand new ROM, and I was still at 100% run time. I did nothing other than sign in to google, and download spare parts to check my run time.
Any other suggestions?
First remove the battery let it sit for 5 minutes outside of the phone... At the same time remove the sd card and put it back in... Then after waiting 5 minutes put the battery back in. Then do the format and all should be good... I too had this problem with original senseui rom that was rooted and solved this problem through sprint and thats what they told me to do and it worked... Oh and also try setcpu and a screen off profile with the right kernels should extend your evo battery to 30 hours or more depending on phone usage! I have cm7 nightly with savage zen bfs kernel and with setcpu I'm getting 30 hours on a regular batstat says 37 hours has been my max awake time... So doing pretty good with that give it a try and with cyanogen you should try performance tweaks to underclock your rom.
After finally flashing my phone with EVIo Cailukin's Rom I have endured some problems and I've search for them and coudln't find anything. I rooted my phone with the latest UnrEVOked program. Noticed this morning my phone was running 100%...
upon other problems, my phone internet speed is lagging. and my battery is really hot!
Pneuma1985 said:
First remove the battery let it sit for 5 minutes outside of the phone... At the same time remove the sd card and put it back in... Then after waiting 5 minutes put the battery back in. Then do the format and all should be good... I too had this problem with original senseui rom that was rooted and solved this problem through sprint and thats what they told me to do and it worked... Oh and also try setcpu and a screen off profile with the right kernels should extend your evo battery to 30 hours or more depending on phone usage! I have cm7 nightly with savage zen bfs kernel and with setcpu I'm getting 30 hours on a regular batstat says 37 hours has been my max awake time... So doing pretty good with that give it a try and with cyanogen you should try performance tweaks to underclock your rom.
Click to expand...
Click to collapse
I tried the removing the battery thing, and I'm still getting 100% run time, with a nandroid restored rom, and 2 different newly installed roms. I am so confused now. Anyone have any suggestions?
UPDATE: Looks like my phone is not at 100% run time anymore. All I did was redo Calkulin's format_all, flash a new ROM, and then reflash the new radios and PRI, and now my phone is not 100% running anymore.
Yay!
Ever since I got the Desire HD (which is a little over a week now), I am running MIUI on it as my daily ROM. I replaced the Torch.apk with the one from CyanogenMod 7.1 (just like I did with my old Desire), so I can have the Full brightness mode.
The Full brightness mode never caused any problems. I could use it, and also with strobe -- I was avoiding using it for extended periods of times, to not harm the LEDs. It was not on for more than 30 seconds continuously.
Now, it seems to be causing problems. I try to turn on the LEDs, on full brightness, and the phone would instantly shut down. Same happens with strobe. It's all good if I don't use full brightness, though.
It doesn't reboot or freeze or anything. It just SHUTS ITSELF DOWN!
I tried this with : MIUI with original CM kernel, with LorDModUE kernel, and also with CyanogenMod 7.1.0. I wanted to try with CyanogenMod 6.1.0, to see if that helps (yeah, silly), but it seems like the ROM isn't booting at all.
I went on ROM Manager, in the section for CyanogenMod, and saw some comments of other people who were experiencing the same problem. Some guy was saying that this is because of the battery. Well, I know this for sure : my battery is as good as new.
Anyone... any ideas...?! :/
which MIUI are you using. If you're using freshly sqeezed then i get no problem like that but if you're using other custom ones, it is possible that the customization done to the stock MIUI can cause problems, some scripts maybe? you should try using other MIUI versions..
shad0wboss said:
which MIUI are you using. If you're using freshly sqeezed then i get no problem like that but if you're using other custom ones, it is possible that the customization done to the stock MIUI can cause problems, some scripts maybe? you should try using other MIUI versions..
Click to expand...
Click to collapse
I'm using the UK variant (MIUIAndroid). Since I also tried with CyanogenMod 7.1.0, and it was the same issue... I doubt that matters.
Right now, I am having more serious problems. Phone shuts itself down after boot... It doesn't do that when it's in Hboot or Recovery. I even flashed 3 other ROMs upon full wipe.
Battery : 49%. Phone shuts down.
Going into Hboot. 5 minutes, no shut down.
Going into Recovery. It shows battery is at 25%.
Reboot.
Now it shows that I have 11% left.
I guess LorDModUE's overcharging thing kind of messed up with this battery. Otherwise, I see no reason for it to act like this, since I barely used the phone today, and it was at 80% when I left home this morning (GMT+2, that is).
I'll just charge it now... then I'll have to go out. I'll flash Tiamat kernel, see how it handles THAT.
My battery is very faulty, alright. I'll buy a MOMAX X-Level battery (of 1150 mAh) next week.
what rom are you on?
i had the same problem on a previous rom, i changed over and it was sorted.
not to sure why it happens though.
MrLarner said:
what rom are you on?
i had the same problem on a previous rom, i changed over and it was sorted.
not to sure why it happens though.
Click to expand...
Click to collapse
I am on the latest MIUI (MIUIAndroid, not US). I also tried with CyanogenMod 7.1. I believe it's the battery, which barely holds half of the charge... I'm going to replace it soon, see if THAT solves the problem.
As I originally said, it didn't cause any trouble at all the first few days... just like the battery...
--
EDIT. It really was the battery. Got a new one now and it works to have Torch on full brightness.
I still don't get why it would turn off the phone even with the battery ~fully charged and the charger still connected.
can someone tell me please, where to get this torch-app with full brightness. I've tested it on jellytime, but now I'm on a different ROM.
Loved this heavy brightness... :cyclops:
I am hoping there is an easy way to troubleshoot and fix this issue. Every couple of days I can try to turn my screen on and nothing happens. I have to pull the battery to get it to come back up. When it comes up I notice the battery has dropped anywhere from 20-30%. I have tried a couple of different rom's. I am on the EL13 modem. I have tried the El26 and EL29 modem's but I have the same issue. I am not using any oc apps. How can I troubleshoot this and try to correct it?
When in doubt, backup, wipe, and flash the same or a different ROM. It's a bit tedious, but that usually fixes the problem. What ROM are you on right now?
I have done that. Was on caulkin's 2.8 now on the latest blazer. I believe it is related to the LOS bug. I just happened to be on a phone call when it happened again. It dropped the call and the screen went black but the phone didn't restart. I had to pull the battery and when it came up I had lost about 20% of the battery. Trying a different modem now.
There was a similar problem on the OG Epic...maybe this thread will help?
If it's not just a display issue (and something is actually draining the battery), I assume you've tried BetterBatteryStats? It usually works wonders for finding the source of wakelock problems.
EDIT: Actually responded to the question!
I have been trying to monitor this and it seems to be a different issue than what I thought. I thought it was related to the LOS but it isn't. My screen won't come and I have to reboot the phone. I think the battery level is just being shown incorrectly. I don't know why the screen won't come on. It is like it is asleep and won't wake up. I have been searching thru the forums and trying to monitor my phone processes to see what might be causing this. I have not found a solution yet. I have tried 3 different rom's so far and it seems to happen at least once a day regardless of the rom. I have wiped the phone and installed fresh. I have tried different modem versions and that didn't help either. Not sure what to do at this point.
when in doubt take it to sprint and get it swapped out.
im having this issue as well actually and i have to conclude that it's a battery display issue; my phone will be over 50% charged then drop as low as 8% when i reboot. i thought it went away with my last blazer flash but it still happens.
If it helps at all, I was/am running the MIUI rom and the phone would lock up on a nearly full charge at the same location. It was every time I walked out of class in the morning, the phone would just go black screen. I'd hold down the power, reboot, and wouldn't have that problem anywhere else. Hope this helps us find an answer.
I'm getting quite annoyed with my S3 and its piss poor battery life - currently seeing as little as 5 hours. On average, 55% of my battery goes to "Android System". I've tried a variety of battery monitors, but none can dig deep enough to determine which of the processes under Android System are sucking up all my juice. I'm on stock (rooted) and have tried to uninstall as much as I can (including the notorious Google+). Any tips on an app that can determine exactly which process is draining? I've also disabled as many Samsung apps as I can. I *did* try CM10 for a bit, but too many small things were not working right, so I nandroid'ed back to stock again.
ScottC said:
I'm getting quite annoyed with my S3 and its piss poor battery life - currently seeing as little as 5 hours. On average, 55% of my battery goes to "Android System". I've tried a variety of battery monitors, but none can dig deep enough to determine which of the processes under Android System are sucking up all my juice. I'm on stock (rooted) and have tried to uninstall as much as I can (including the notorious Google+). Any tips on an app that can determine exactly which process is draining? I've also disabled as many Samsung apps as I can. I *did* try CM10 for a bit, but too many small things were not working right, so I nandroid'ed back to stock again.
Click to expand...
Click to collapse
I had this problem numerous times before. If it is Android System that is taking up battery, then its most probably a bad kernel. Your nandroid backup probably was bad. (it sucks, i know). Redownload the stock rom, flash it in odin, before starting up reboot in recovery and factory reset, then start it up. Your problem should be resolved. dont restore any apps and start fresh. Like I said it sucks but what can you do?
Hey ScottC,
Definitely doesn't sound normal. At the end of the day, I'm sitting around 10% lost to android system, 15% tops (of course this can vary on what you use and how you use it, but if your battery dies in 5 hours, certainly something is wrong). It's possible that in the process of nandroiding back, something messed up. I'd recommend a complete wipe (factory reset, wipe dalvik, etc), then test it out for a day or two. If the issue persists, you will likely want to Odin back to stock. If it still persists (highly unlikely), I'd call in for an exchange. Best of luck to you, and please let us know the results!
Thanks for the tips - to clarify, it was doing this before I ever nandroided back - but I have a feeling wiping might be the best bet (or trying out a better JB leak).
I think you may be getting the gsiff_daemon bug. Next time you have the battery start draining like that, turn on show cpu usage under developer options in settings. If you see gsiff_daemon at the top, then that's what's causing the android system battery suck.
The fix is simple go to /system/bin with a root explorer, mount r/w and rename gsiff_daemon to .Bak or delete it. This won't hurt anything. Then reboot.
There is a thread about this in QA. If you check it out keep in mind it's full of wags and speculation.
Sent from my SGH-T999 using xda premium
I have the same issue. My phone was 100 percent and I've been sitting here watching the Texans game and I'm getting the worst battery life today that I have in my week or so of owning this phone. My phone is bone stock.
Sent from my SGH-T999 using xda premium
I have the same issue
ibous said:
I think you may be getting the gsiff_daemon bug. Next time you have the battery start draining like that, turn on show cpu usage under developer options in settings. If you see gsiff_daemon at the top, then that's what's causing the android system battery suck.
The fix is simple go to /system/bin with a root explorer, mount r/w and rename gsiff_daemon to .Bak or delete it. This won't hurt anything. Then reboot.
There is a thread about this in QA. If you check it out keep in mind it's full of wags and speculation.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Add another one to the list for this problem. I've had my phone since Sept. 27th (so 3 weeks?) and up until about 4 days ago it was great. Great battery life, even with all the bells and whistles turned on, and several apps that update constantly. For some reason a few days ago it started to battery drain HARD, downing to 25% of the battery life in less than 6 hours. That's with the phone sitting idle, not touching it, on wi-fi (not 4G) with excellent signal. Last night I plugged the phone in at 10% battery, did some chores, and returned some 3 hours later to find the battery at 5%. It drained while it was plugged in!
The battery drain issue seemed to start after the phone decided to have a certain level of diffuculty finding a 4G signal. I had to reboot the phone to get it to connect to the network. After that, the Android System will take anywhere from 55% to 76% of the battery drain.
I have shut off numerous programs, disabled the Samsung apps that were said to possibly be a problem, and looked for the gsiff_daemon in the CPU list (my top process is "com.android.systemui"). I searched com.android.systemui to see if I could find a fix, and all I'm really seeing is "flash a new ROM" or "Your kernal is bad, reset or reflash it." I'm running a 100% stock phone, and actually had no intention of rooting or flashing this phone yet, and I didn't want to have to factory default it. It's starting to look like that's my only option. Someone said that this bug seems to crop up out of pure chance and I think they may be right. My husband has the identical phone, bought, charged and activated the same day, and he doesn't have this problem. He's still getting the incredible battery life that I used to get.
So what's the skinny? Is my only option on this a factory reset? I've seen threads referrring to a thread dedicated to this topic, yet no links. If there's more info to be found, I'd love to read it.
This thread might as well be titled "all noobs thread". It is known widely that android system in jb leaks is a problem but of course u cant know that cuz reading and searching are two words that sound like chinese to you.
lazarat said:
This thread might as well be titled "all noobs thread". It is known widely that android system in jb leaks is a problem but of course u cant know that cuz reading and searching are two words that sound like chinese to you.
Click to expand...
Click to collapse
Actually I have "searched" and "read". I wouldn't have posted had I been able to find an answer. Everything I've found has been for ROOTED/FLASHED ROMs, and I'm on stock. I don't want to root/flash this phone, I'd like to fix it without having to return it or factory default it if possible. I also mentioned that I had gone through threads and tried as many of the tips there that applied to my situation.
While I'm not nearly the level of many here, I'm also not a n00b. I've flashed, rooted and hacked many devices, I'm just trying to avoid that here. I didn't run across anything called "jb leaks" in my search, so if you'd care to be helpful and elaborate on that term, it might prove useful.
I believe this is the thread you were told about.
http://forum.xda-developers.com/showthread.php?t=1755180
When you checked cpu use, how did you check it? There's an option in Dev Options to Show CPU Usage and you can see real time what's running. Just fyi in case you did it differently.
Sent from my SGH-T999 using xda app-developers app
Thanks for the Link, Doc! It's much appreciated. As far as checking the CPU, I used the option under the Dev Options menu and watched it bounce about. Many different programs would take top spot, but when the phone was idling it was always com.android.systemui at the top. When it wasn't top, it was never far below.
Have you tried booting into recovery and wiping dalvik cache?
If it comes to it, before factory resetting since you want to avoid that, download the official stock FW and flash with Odin. I'm pretty sure it will keep your data and apps intact. Backup data first in case I'm remembering wrong. If that doesn't do it then factory reset may be your final option.
Check settings > Battery, and open Android System (I'm betting its at the top). This may give you a better idea of what the root cause could be, maybe...
Sent from my SGH-T999 using xda app-developers app
CorbieMessenger said:
Actually I have "searched" and "read". I wouldn't have posted had I been able to find an answer. Everything I've found has been for ROOTED/FLASHED ROMs, and I'm on stock. I don't want to root/flash this phone, I'd like to fix it without having to return it or factory default it if possible. I also mentioned that I had gone through threads and tried as many of the tips there that applied to my situation.
While I'm not nearly the level of many here, I'm also not a n00b. I've flashed, rooted and hacked many devices, I'm just trying to avoid that here. I didn't run across anything called "jb leaks" in my search, so if you'd care to be helpful and elaborate on that term, it might prove useful.
Click to expand...
Click to collapse
You are not the op of this thread so i cannot comment about your problems. The first posts regard rooted devices running jb leaked roms and in the jb leaked roms threads all people talk about is android system taking a high percentage of the battery usage. So one must be really blind not to notice what is the problem and fix if there is any. There is no fix and it is kernel issue. Thats the reason why it is called leak and not official release. U can post some screenshots of ur battery usage and firmware version you are running if u want people to help u since u claim u r all stock and still android system usage is high 76%.
Doc-
I tried booting into recovery, but since I'm not a rooted user I can't clear the delvick cache. Somehow in the process of attempting booting into recovery I managed to lose my set wallpaper and most of my homescreen widgets, though the rest of my data and programs seem perfectly intact (accidentally went into a safe mode option). I did clear the cache partition in recovery, and tried another trick someone listed of pulling the battery and holding down the power key (I'll try anything at this point) and oddly it seems to be behaving better so far. Sitting on my desk it didn't discharge at all, and having just put all my widgets back it's only drained a few points. The screen is now the big spender at 39% with Cell Standby next at 12% (previously is was Android System being the hog at 50-70%). I have no idea which of the things I did actually did anything, but I think this just saved my tail.
I'm going to charge the phone normally tonight and leave it loose all day tomorrow like I usually do, and see what happens. If it starts battery draining again, I'm going to try flashing with Odin. Here's hoping I'm one of the few lucky ones where the problem simply "goes away".
Thanks again for your help!
Well that's kinda weird...good, but weird!
I've heard of people going into safe mode but its never intentional and I've never found how to do so at will.
As long as it goes back to normal though! Hope it does! Good luck!
Sent from my SGH-T999 using xda app-developers app
I know that this sounds pretty simple and you may have already tried this, but it always works like a charm for me. Try draining the battery ALL the way down until it automatically shuts off. Then keep turning it on until it won't even turn on our vibrate anymore. Plug it in and turn it on. Leave it plugged in until it's at 100% again, I do this overnight so there's no usage other than standby. Hopefully this will get your battery back in shape. Good luck!
DocHoliday77 said:
Well that's kinda weird...good, but weird!
I've heard of people going into safe mode but its never intentional and I've never found how to do so at will.
As long as it goes back to normal though! Hope it does! Good luck!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Sometimes I wonder how I got into Safe mode.
forum.xda-developers.com/showthread.php?t=1821557
Well, It behaved for about an hour, then it started the massive drain again. Sadly I just backed a few things up and then factory defaulted it. We're leaving on a trip tomorrow, and I need it to not be a power-sucking brick. Oddly, everything that my CPU report was showing was identical to my husban'd phone, which has no issues with battery life. The Gsiff daemon never once showed up.
As far as safe mode, I held down the volume down button while I powered up the phone. It went into safe mode. Don't know if it'll work for y'all, or if it was just a fluke on my part. :>
Thank everyone for your help in trying to troubleshoot this. One of these days I'd love to have an electronic device that just worked without me having to poke around in it's guts. ;>
If its still acting up after the factory reset, your best bet is to flash the stock FW with Odin. If the factory reset didn't wipe your internal sdcard, you may need to to wipe it in recovery by using format data as well. (Factory reset should do this anyway as long as you're on stock recovery)
I've seen on some jb leaks where this would significantly help. I know your not using jb but its worth mentioning anyway.
Good luck!
Sent from my SGH-T999 using xda app-developers app
Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!
Different roms use a different amount of power...
Sent from my GT-P3100 using xda app-developers app
xSTUDDSx said:
Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!
Click to expand...
Click to collapse
I'm not 100% sure but it is possible the bricking messed with the battery. LGNPSTing back to stock could have affected it, anytime you flash a new rom it takes a couple of days to "settle in" but you said last weekend so it should be settled by now.
But from your info, it may be the way you are charging it. There is a common misconception that every so often you are supposed to let your battery drain fully and then charge to 100%. This is only true for nickel based batteries, ours is lithium so this is in fact quite detrimental. Lithium batteries are built to be charged often and you should never let it dip too far into the red. Doing so decreases the life and performance of your battery significantly. 5% is as low as I'll let my battery dip before charging and even that is pushing it imo. There is an app in the play store called battery calibration that actually tells you to do this, but like I said, it's only useful for nickel based rechargeable batteries. Also this same app's function is deleting the batterystats.bin file in order to "recalibrate" the battery. This is also completely false as that file has nothing to do with how well your battery performs.
I wouldn't turn the phone off to charge, just charge it while it's still on so the screen actually shuts off. Checking your wakelocks and using greenify on power hungry apps will go a long way. I also turn my capacitive buttons off because I don't need to see them to know left, right, center and what they do. And if I'm not using it, it is always off, sync, gps, brightness when inside, etc. But as I said, it may have been the way you were charging it, it might not affect the battery for months, then all of a sudden your battery doesn't perform as well because it's dying due to improper charging techniques. And when you LGNPSTed back to stock, your system tries to start fresh which is why it may have happened immediately afterwards.
I hope some of this helps you - if using greenify doesnt show improvement you may want to buy a bigger capacity battery and start fresh. Installing the new battery is tricky however, there are youtube videos on how to do it, but it may not be for everyone.
Good luck and I'm sorry if I assumed too much or misread your info!
EDIT: You may also want to try flashing a different stock kernel(I use Viper1.1, my signature has a link to the thread) and using trickstermod to undervolt the cpu. The improvement is minimal but every little bit helps. On average I get a full 24 hours in between charges and usually charge once it hits 10-15%. And it only takes about 60-120 minutes to fully charge.
However the lgog is also very fickle, what works for one may not work on another, even if it's the exact same model. Many people have reported the same security bootloop soft brick after deleting google apps for instance, but I deleted(not frozen or disabled) google apps just fine. The only ones I have on my phone are play store and google search and I'm still on stock zvc.
HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.
And based off what your saying would you not recommend doing LGNPOST again?
xSTUDDSx said:
HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.
Click to expand...
Click to collapse
Ok well it seems like you follow good battery techniques. Maybe try LGNPSTing back to a full stock zvc(or zvb and then updating to zvc) and charge it to 100%(let it sit at 100% while still charging for 15 mintues or so) before rerooting and unlocking. I would probably also copy your internal to your pc and wipe everything in recovery before doing LGNPST just to make sure it is a completely clean slate. I added an edit in my post above as well.
I had a strange issue a few weeks back where I tried overclocking my cpu with AK kernel - my battery was at 99%. My phone shut off and wouldn't come back on, just had a red blinking light. I later found out it was an issue with AK. I charged it for a few minutes and luckily was able to get into TWRP. The strange part was that when I did get into TWRP my battery read 0%, I did a full wipe and restored my backup, then my battery read 99% in TWRP. It's a different issue from yours but makes me think that it's possible that your softbrick and LGNPSTing affected it somehow.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
xSTUDDSx said:
And based off what your saying would you not recommend doing LGNPOST again?
Click to expand...
Click to collapse
I honestly have not had or heard of any issues with LGNPST and battery performance. Anytime Ive had to use LGNPST with a full stock .bin, it essentially set my phone back to factory condition, battery performance included. However since this all happened when you did this, maybe try flashing another rom first, even a stock based one and leave LGNPST as a last resort. Just make sure you read the instructions for whatever rom you decide to test and always do a full wipe(data, cache, dalvik and system) before flashing.
EDIT: Sorry if it seems like I gave you conflicting info, if it was me I would probably be weary of using LGNPST again, personally. But if I tried flashing other things, different recoveries, roms and still had the same issue, maybe it was just a slightly messed up LGNPST flash and would try it again as a last resort.
Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?
xSTUDDSx said:
Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?
Click to expand...
Click to collapse
After holding volume up + power, you then will hit volume down twice and power again. Once in TWRP it is very easy, there is an install button, wipe button, etc. Hit the backup button, pick all available options and then do a backup and reboot into your OS. From there, download a rom(optimus DE is a great stock rom) to your internal and you will probably need gapps as well(depends on rom but almost all of them need gapps or you wont even have the play store - just read the install instructions of the rom). Go back into recovery, This is under the advanced wipe button in the wipe menu - wipe everything except internal storage(if you wipe internal you will lose your backup, pictures, music, etc) and then go to install, pick the rom.zip and flash that, then pick the gapps zip and flash that as well.
Also keep in mind that if you flash an AOSP or CM based rom, the file system will be different. Our internal storage is /data/media but for AOSP based it is /data/media/0. So say for instance you make a backup in TWRP of your stock then flash an AOSP rom, it will look as if your internal is gone as well as your backup. You will just have to use a root file explorer to copy the /data/media/TWRP folder to /data/media/0/TWRP and then you will be able to restore your backup from TWRP.
If you are just going to try LGNPST again then when you get into TWRP pick everything including internal and turn the phone off and put the phone into dl mode(you know what you are doing from there).
One final note, if you are using current FreeGee to unlock then you are most likely using the updated TWRP. Some people have had SEVERE issues with it, for others it works just fine. You need it to install any rom based on Android 4.4 but I personally use TWRP 2.5.0.0 which will flash stock to Android 4.3 roms just fine and it is rock solid stable. So unless you are planning on installing a kit kat rom, I would first download the TWRP 2.5.0.0 zip found here to your internal, go into twrp, pick the install button, find the .zip file and install that, then go to reboot in TWRP's main menu and choose recovery instead of system. TWRP should now read 2.5.0.0.
Sorry for the books I'm writing here but I think it's always best to be thorough!! And I haven't slept in about 30 hours so I am a bit scatter brained.