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.
Related
Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference
bump. should I post somewhere else?
Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!
I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App
I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies
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
Was skeptical about the N5100 battery life since it only have 4600mAH battery.
Now that I have bought it, it seems my worries are confirmed.
I'm running stock rom, only rooted it without other modification.
Installed and have greenify running. Not using any sim card, only using it on WiFi.
Playing a video using MX Player, drained up about 20% of battery for a 45min video. That's rather heavy imo.
Normal browsing and reading forums eats up about 4% per 6min of use.
Is this normal? Or is it my battery has significantly degraded? Cuz I bought this 2nd hand 8 months old.
Btw the above test were with Power Saving mode(CPU and Screen) and screen brightness was at 25%~30%. Currently on 4.2.2.
And does using the S Pen eats up significantly more battery?
Thanks in advance for the feedback.
hahnliang said:
Was skeptical about the N5100 battery life since it only have 4600mAH battery.
Now that I have bought it, it seems my worries are confirmed.
I'm running stock rom, only rooted it without other modification.
Installed and have greenify running. Not using any sim card, only using it on WiFi.
Playing a video using MX Player, drained up about 20% of battery for a 45min video. That's rather heavy imo.
Normal browsing and reading forums eats up about 4% per 6min of use.
Is this normal? Or is it my battery has significantly degraded? Cuz I bought this 2nd hand 8 months old.
Btw the above test were with Power Saving mode(CPU and Screen) and screen brightness was at 25%~30%. Currently on 4.2.2.
And does using the S Pen eats up significantly more battery?
Thanks in advance for the feedback.
Click to expand...
Click to collapse
Do a search on battery and charging by me, in the Q&A threads. I won't repeat myself here, but I go into how to correct drain issues. Many developers will push their apps for calibration. The real trick is discovering what is doing the drain. I have seen for myself how one app can do a lot of damage with media. Normally I get 12% per hour on battery usage while Miracasting Netflix to my tv, and about 10% on normal usage with WIFI always on. I have MXplayer and a bunch of apps as well running so I am not going to get the same power savings as with a cleaned up stock ROM without any apps, what would the point of having a tablet if that is the case???? I guess peeps like to show off when it comes to numbers. I like to show off when it comes to usability and function without all the apps get in the way.
my battery stats
I'm running CivZ-FLEX-BEAM-REV3.6.2 ROM.
Installed and have greenify running. Not using any sim card, only using it on WiFi, even off the WiFi before I off the screen.
Even use underclock to 1.2Ghz cuz only used for normal browsing, nothing intense that require more power.
Here's my battery stats:
Is this normal? Or is it my battery has significantly degraded? Cuz I bought this 2nd hand 8 months old, now 9 or 10 months already.
Now considering should I replace the battery or just get a powerbank to help.
Thanks in advance for the feedback.
hahnliang said:
I'm running CivZ-FLEX-BEAM-REV3.6.2 ROM.
Installed and have greenify running. Not using any sim card, only using it on WiFi, even off the WiFi before I off the screen.
Even use underclock to 1.2Ghz cuz only used for normal browsing, nothing intense that require more power.
Here's my battery stats:
Is this normal? Or is it my battery has significantly degraded? Cuz I bought this 2nd hand 8 months old, now 9 or 10 months already.
Now considering should I replace the battery or just get a powerbank to help.
Thanks in advance for the feedback.
Click to expand...
Click to collapse
From what the graphs show... it looks like the battery could be going bad, as there has some that say Samsung is aware of bad batteries in some units. You could contact them, but you will need to un-root if sending to Samsung for repair.
Since you are rooted, I suggest installing xposed framework and install Wanam DVFS Disabler for Xposed. It is a standalone utility from the complete Wanam xposed app. Once installed make sure both xposed is functional, and the app in xposed is enabled. These apps act as a separate process from the OS. So installing them requires user interaction for activation and updating, along with a reboot most of the time.
Once they are running... it is best to turn off the tablet for 1 minute and then plug in the USB charger and wait til it is showing 100%. Then turn on the tablet. You can unplug the USB power cable and wait 1 minute, then plug it in. Take note if the charge takes less than a minute to get to 100%. If it takes a minute or more... you will need a stop watch, as it should take about 15 to 20 seconds to go to fully charged, unless you have music or media running at the time. If it does charge quick, you can then disconnect and do another days worth of use and check your stats. Hopefully disabling DVFS will cure your issue if it is not battery related.
As for unrooting, make sure you do a clean uninstall, and have any apps that require root uninstalled. If running triangle away uninstall that as well. You may have to check within the apps settings to make sure you uninstall properly, as to uninstall from play store or the system may not properly remove the app.
Updated Battery Stats
this is my updated battery stats, now I'm suspecting it maybe due to calibration problem?
My screen on time is now 2 hrs 45 mins, and for the last 45 mins it has been running on that last 1% of battery(but with screen dimmed, as brightness is automatically dimmed and can't be adjusted when below 5%).
Even until now the device haven't auto shut down due to run out of battery yet even though been running 45mins SOT for that 1%.
Calibration problem? I've tried calibrating using calibration apps, which I charged to 100% then press calibrate, but didn't help.
hahnliang said:
this is my updated battery stats, now I'm suspecting it maybe due to calibration problem?
My screen on time is now 2 hrs 45 mins, and for the last 45 mins it has been running on that last 1% of battery(but with screen dimmed, as brightness is automatically dimmed and can't be adjusted when below 5%).
Even until now the device haven't auto shut down due to run out of battery yet even though been running 45mins SOT for that 1%.
Calibration problem? I've tried calibrating using calibration apps, which I charged to 100% then press calibrate, but didn't help.
Click to expand...
Click to collapse
Sudden drop of more than 3% at any level after doing the DVFS disable and properly charging can be one of two things.
A bad battery, or bad charging cable. Yep, I have had two bad Samsung cables, one did exactly what is happening with you, and the other did a melt down at the USB connection on my tablet. If you have a good cable from a Blackberry or a Sony/Ericson device, you can try that. I have moved over to Sony Xperia cables, as they are pretty well built and longer.
If another cable does not solve your issues, I suggest unrooting and cleaning up rooted apps before having Samsung service your tablet. It very well could be a bad battery.
thanks for the reply, I think I'll just resort to sending it back to Samsung to fix it.
Now I have made a nandroid backup already, then I flashed stock firmware, so my device is now unrooted and on stock firmware, however my flashcount is still there, and now I can't run triangle away cuz my device is unrooted already.
If I were to root it, it'll flash custom recovery again then it won't be on stock firmware anymore.
hahnliang said:
thanks for the reply, I think I'll just resort to sending it back to Samsung to fix it.
Now I have made a nandroid backup already, then I flashed stock firmware, so my device is now unrooted and on stock firmware, however my flashcount is still there, and now I can't run triangle away cuz my device is unrooted already.
If I were to root it, it'll flash custom recovery again then it won't be on stock firmware anymore.
Click to expand...
Click to collapse
Your unroot sequence was done out of order.
Set USB debug
Root stock rom with saferoot.zip
Install triangle away
perform clear of counters
Verify after clearing in about device that custom is not set.
If so make sure triangle away is set to clear and perform clearing.
Remove triangle away
Remove SuperSU through the settings, clear for reinstall.
To make sure everything is proper... do a factory reset.
Once those steps are done, your tablet should be stock and able to perform OTA or Kies updates, without any issues with counter and root.
Hello, new to the forums here. I recently updated to 4.4.2 on my LG Optimus G Pro and I went from having a battery that lasted all day, sometimes two days to my phone being dead by the time I get home from work for the day ever since the update.
Two days ago I had 1hr18min of screen time within a 6 hours off the charger and the phone was at 15% battery life left. Today, I had 13 minutes of on screen time and at the end of my 6 hour shift my phone was at 40% and dead a few hours after I got home. I have GPS, bluetooth, NFS all disabled and my brightness set to 30%.
Any help would be greatly appreciated, I'm thinking of doing a factory reset and just not updating to the new version of android when it prompts.
Thanks
silentvelcr0 said:
Hello, new to the forums here. I recently updated to 4.4.2 on my LG Optimus G Pro and I went from having a battery that lasted all day, sometimes two days to my phone being dead by the time I get home from work for the day ever since the update.
Two days ago I had 1hr18min of screen time within a 6 hours off the charger and the phone was at 15% battery life left. Today, I had 13 minutes of on screen time and at the end of my 6 hour shift my phone was at 40% and dead a few hours after I got home. I have GPS, bluetooth, NFS all disabled and my brightness set to 30%.
Any help would be greatly appreciated, I'm thinking of doing a factory reset and just not updating to the new version of android when it prompts.
Thanks
Click to expand...
Click to collapse
Get betterbatterystats and see if you phone deep sleeps. If not then check what the wakelocks are in partial wakelocks. If it's a kernel problem maybe you need to flash a different kernel.
cxyjordan said:
Get betterbatterystats and see if you phone deep sleeps. If not then check what the wakelocks are in partial wakelocks. If it's a kernel problem maybe you need to flash a different kernel.
Click to expand...
Click to collapse
i am running stock phone. it is not rooted or anything
Same exact battery drain problem. Im on stock e980 rom (rooted) with no custom kernel.
Gsam battery monitor app is showing the kernel as keeping my phone wake for the entire time my phone has been unplugged.
The problem seems to come and go though. One day itll be fine, but another day the battery will be sucked dry fast.
Sent from my SM-P600 using Tapatalk
I'm running stock rooted for e980 and have pretty good battery life .... Try clearing Google play services data and rebooting ... Check and see what's draining your battery mol its pretty easy
2SHAYNEZ
I'm also running stock kernel, and have great battery life on kitkat. Just reset your phone to factory defaults
Sent from my LG-F240L
ccelis said:
I'm also running stock kernel, and have great battery life on kitkat. Just reset your phone to factory defaults
Sent from my LG-F240L
Click to expand...
Click to collapse
I've done this twice in the past 3 days....
I'm sick of having to set up my phone over and over again. And this is a new phone too. I just got it Monday under warranty because my old phone broke.
It's getting annoying. I used to get 14-17hrs+ of battery life (casual use, usually ending the day at 30-50% too, so I never even reached 0%) with my old phone on Jelly Bean. Now with Kitkat, I get around 6 hours if I'm lucky! According to Wakelock detector, my phone is awake 85%+ of the day! All it points to is Kernel (Android OS). I see lots of Wlan_wake triggers too, so I suspect wifi, but even with wifi off, the drainage still occurs. And I only have a 2GB data plan shared between 3 people, so it's not like I can just use data all the time either. I actually NEED wifi.
spexwood said:
I've done this twice in the past 3 days....
I'm sick of having to set up my phone over and over again. And this is a new phone too. I just got it Monday under warranty because my old phone broke.
It's getting annoying. I used to get 14-17hrs+ of battery life (casual use, usually ending the day at 30-50% too, so I never even reached 0%) with my old phone on Jelly Bean. Now with Kitkat, I get around 6 hours if I'm lucky! According to Wakelock detector, my phone is awake 85%+ of the day! All it points to is Kernel (Android OS). I see lots of Wlan_wake triggers too, so I suspect wifi, but even with wifi off, the drainage still occurs. And I only have a 2GB data plan shared between 3 people, so it's not like I can just use data all the time either. I actually NEED wifi.
Click to expand...
Click to collapse
do you have an SD card installed? Maybe you can try to remove that and get rid of all other media from your phone storage. Might be a media scanner problem? Or maybe you can try to disable auto sync, and check if Google play services is the culprit.
Sent from my LG-F240L
ccelis said:
do you have an SD card installed? Maybe you can try to remove that and get rid of all other media from your phone storage. Might be a media scanner problem? Or maybe you can try to disable auto sync, and check if Google play services is the culprit.
Sent from my LG-F240L
Click to expand...
Click to collapse
The media scanner usually shows up in the battery stats window though, and it isn't. I've had a corrupted SD card on my tablet once before and it caused media scanner to go berserk, but the Mediascanner entry appeared under Settings>Battery as the highest battery consumer.
In this case of my phone right now, it is Android OS in Settings>Battery. According to Wakelock detector, GSam, and BetterBatteryStats, it's more specifically Kernel.
spexwood said:
The media scanner usually shows up in the battery stats window though, and it isn't. I've had a corrupted SD card on my tablet once before and it caused media scanner to go berserk, but the Mediascanner entry appeared under Settings>Battery as the highest battery consumer.
In this case of my phone right now, it is Android OS in Settings>Battery. According to Wakelock detector, GSam, and BetterBatteryStats, it's more specifically Kernel.
Click to expand...
Click to collapse
Have you tried reflashing your firmware, instead of just doing a factory reset?
I assume you are rooted since you are using BBS and wake lock detector on KK. Why not flash a custom rom?
Sent from my LG-F240L
Battery
silentvelcr0 said:
Hello, new to the forums here. I recently updated to 4.4.2 on my LG Optimus G Pro and I went from having a battery that lasted all day, sometimes two days to my phone being dead by the time I get home from work for the day ever since the update.
Two days ago I had 1hr18min of screen time within a 6 hours off the charger and the phone was at 15% battery life left. Today, I had 13 minutes of on screen time and at the end of my 6 hour shift my phone was at 40% and dead a few hours after I got home. I have GPS, bluetooth, NFS all disabled and my brightness set to 30%.
Any help would be greatly appreciated, I'm thinking of doing a factory reset and just not updating to the new version of android when it prompts.
Thanks
Click to expand...
Click to collapse
Hi i had the same problem as you but i started digging inside the system of the phone i found the problem but you will require root access. If you have root you have to delet a lib file tand it carrier iq wich run in background and drains your battery the file to delete is libiq_client.so do that and you will see an increase in battery life
Hav
ccelis said:
Have you tried reflashing your firmware, instead of just doing a factory reset?
I assume you are rooted since you are using BBS and wake lock detector on KK. Why not flash a custom rom?
Sent from my LG-F240L
Click to expand...
Click to collapse
I did this on Tuesday or Wednesday.
... I messed something up on my phone while trying to install a custom recovery, so I was basically forced to reinstall everything. I'm on stock ATT e980 ROM (on an E980) + root. I reflashed the Jelly Bean tot file and then did the OTA update with no apps installed.
On the phone that got warrantied, I had flashed the E980 kitkat backup (now has a flashable version too), and the battery life seemed to be much better on it for about a week, and then the issues started there too.
I just rebooted the phone into recovery and wiped cache and Dalvik cache. Many people on Kitkat are reporting that this helps, but only for about 2 days then the issue returns. Obviously, I want a permanent solution.
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
xoLEOox said:
Hi i had the same problem as you but i started digging inside the system of the phone i found the problem but you will require root access. If you have root you have to delet a lib file tand it carrier iq wich run in background and drains your battery the file to delete is libiq_client.so do that and you will see an increase in battery life
Hav
Click to expand...
Click to collapse
I just tried this right now. Will see what happens.
Will report back if I see anything noticeable.
How would this this battery though? Like, what does it do? Are there any adverse effects to removing it?
EDIT: BTW, I know you weren't addressing this at me, but I'm still trying it LOL
spexwood said:
I did this on Tuesday or Wednesday.
... I messed something up on my phone while trying to install a custom recovery, so I was basically forced to reinstall everything. I'm on stock ATT e980 ROM (on an E980) + root. I reflashed the Jelly Bean tot file and then did the OTA update with no apps installed.
On the phone that got warrantied, I had flashed the E980 kitkat backup (now has a flashable version too), and the battery life seemed to be much better on it for about a week, and then the issues started there too.
I just rebooted the phone into recovery and wiped cache and Dalvik cache. Many people on Kitkat are reporting that this helps, but only for about 2 days then the issue returns. Obviously, I want a permanent solution.
---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------
I just tried this right now. Will see what happens.
Will report back if I see anything noticeable.
Click to expand...
Click to collapse
Ok restart when you delete the file this is a permanent solution for me i hope this helps you as it did me
ccelis said:
I assume you are rooted since you are using BBS and wake lock detector on KK. Why not flash a custom rom?
Sent from my LG-F240L
Click to expand...
Click to collapse
I didn't see this part of your message, but I just had to respond lol
Yes, I'm rooted and I absolutely hate custom roms. They take out all the features of the phone that I originally bought the phone for, like Smart Screen, the IR remote (yes, I know it can be ported), and the quick memo button. Plus I used custom ROMs on my old SGS2 and they always caused me tons of problems. Crashes, overheating, random reboots, random SODs, etc etc etc. Plus I hate the AOSP feel. I know it's true Android, but I just don;t like it.
---------- Post added at 11:42 PM ---------- Previous post was at 11:38 PM ----------
xoLEOox said:
Ok restart when you delete the file this is a permanent solution for me i hope this helps you as it did me
Click to expand...
Click to collapse
I'm still getting more than usual battery drain, but it is better now.
I just got a replacement OEM LG battery, so I will try that to see if maybe the battery is defective. When I got my phone replaced under warranty, they didn't have batteries in stock, so they just gave me back my old one and ordered me a knew one. The old phone was overheating a lot too, so maybe the battery is bad.
UPDATE: OK, MUUUUUUUUUCH better battery now!
I put in that new battery and "recalibrated" it by draining it to 0% and charging with the power off. Once it reached 100%, I let it charge an extra hour, unplugged, and started up the phone.
I also installed Qualcomm Snapdragon's Battery Guru. I set it up so that it's mostly managing app syncing, but I also set it up so that it will not rely on location services to turn on/off my wifi. I don't want to leave my location services on all the time. I don't know how it is on Kitkat, but on older Android versions (ICS and GB), leaving GPS on was a huge battery drainer! I still treat location like it was back then.
Anyways, it will take a few days for the app to learn my usage patterns, but it's already helping by making certain apps only sync when I open them, etc. I suspect that all the wlan_wake wakelocks are being caused by auto-sync but I'm reluctant to turn it completely off since i rely on it to sync my work schedule, calendar, etc between my phone and tablet. I just wish there was a system setting to allow auto-sync to run every X hours or something. I really only need the sync to run every 6 hours or so.
It's been about 35mins now with 6mins of screen time and the phone is still at 100%. A few text messages and the installation of Battery Guru too. This is normal and how things used to be. After a while, the phone will most likely go to 99% and then have faster drain, but it shouldn't be so rapid like before. Earlier today, after 30mins, the battery would be at at least 95% or lower by now! After a full day, the battery usage graph would should a 45 degree angle too! It used to be an almost level, very gradual angle instead.
I should also mention that for a while, I was using a Zero Lemon slim battery (3150mAh). I bought it because of all the hype Zero Lemon was getting here on XDA, but I really regret it now. I used it for 2 weeks (1 week on my broken phone and 1 week on my replacement) and the drain wasn't consistent, even after several calibration attempts. It lasted me all day though, but I'd be stuck at maybe 3% for like an hour, then while in deep sleep, the battery would "magically charge" to 6%.
After I swapped back to the OEM battery, I don't think I recalibrated, so I wonder if my phone thought I was still using the Zero Lemon.
I'm planning to return the Zero Lemon.
UPDATE2: It's been a couple hours now and the Android OS is starting to retreat from the #1 slot in the battery consumption list!
Screen is #1 now and Android OS went from 65% usage to 14%! :good: :good:
UPDATE3: :crying: OK, it's broken again. I didn't do anything to the phone, but when the phone hit 50%, I left it alone for 2 hours and the battery drained 30% while it was supposed to be sleeping. Android OS is back up to 80% usage!
Wifi on, Location off, Bluetooth off, auto-sync on. I'm trying auto-sync off today to see if there's any dramatic improvement.
UPDATE4: I might be on to something now. I noticed 2 things: 1st, when the screen is off and the phone is SUPPOSED to be in deep sleep, the back of the phone stays warm to the touch. It wasn't hot, but it was warm enough to be noticeable. 2nd, I had System Tuner installed yesterday but uninstalled it this morning. Despite uninstalling and rebooting, the phone was still draining battery fast (I still lost 25% in 2 hours today!). I noticed that System Tuner had added a script to System/etc/init.d, so I deleted that and rebooted. Now the phone seems to be sleeping (says so in BetterBatteryStats and WakeLockDetector), and the back of the phone is COLD to the touch when doing so. I took a shower today (I take fairly long showers too LOL), and then checked my email, and the battery life didn't decrease at all during that time while it was asleep.
Obviously, I need to test this throughout the day now, but this is definite progress, if not the solution.
Also, on my warrantied phone, when I had the Zero Lemon battery inserted, battery drain was high (battery's fault), so I installed System Tuner then too, trying to tweak the phone. After switching back to the stock battery, the drain remained, but most likely due to System Tuner's script.
Then when I got my replacement phone, I ALSO installed System Tuner and of course, I got battery drain issues! I factory reset, but did not install System Tuner, but the problem still remained. However, it probably remained because the reset doesn't remove system files, so this script was still in the init.d folder.
FINAL: I ended up flashing the stock ROM again (I used Eazy Kat 1.0 this time). My phone began bugging out on me. Random crashes here and there, mobile data randomly disappearing (no LTE/4G/3G at all), and worst of all, people were having difficulty hearing me during calls. Reflashing seems to have worked perfectly this time. *knock on wood*
FYI: The last flashes I did, I used .tot files to flash back to stock Jelly Bean and then updated to Kitkat via OTA.
xoLEOox said:
Hi i had the same problem as you but i started digging inside the system of the phone i found the problem but you will require root access. If you have root you have to delet a lib file tand it carrier iq wich run in background and drains your battery the file to delete is libiq_client.so do that and you will see an increase in battery life
Hav
Click to expand...
Click to collapse
I stumbled across this post and tried that fix. I'll check back in later to see what it does.
Hi All,
My predicament appears a bit special. From my searches I haven't found anyone that is quite like it. My Tab S 10.5 in is brand new, I've only had it for a week. I've updated 5.02, and I don't really have any idea how the battery life was prior to that update because I updated it as soon as I got it out of the box (which to me, was a grave mistake now...).
My Samsung Tab S is draining battery, but it is draining because of "Android OS" keeping my tablet 100% awake. when I say 100% awake, I mean in the awake bar it is completely solid with absolutely no breaks. I am rooted, and have tried BBS and Wakelock detector and they give me the same information. Tablet is 100% awake, and never ever gears down to "Deep Sleep". There are absolutely zero wakelocks present, kernel or partial (which is peculiar, I don't know why they aren't showing at all, they used to show when I first installed BBS and activated root). However, a peculiar thing is this isn't 100% consistent. I've had the tablet for 6 days as of today, and only 2/6 days did Android OS do this massive drain. The latest drain was last night, where between 5:00PM and 4:00AM it drained 81% of its battery. At around 4:00AM suddenly the Tab went into "Deep Sleep". What is the problem?
Prior to going to sleep at 11:00PM~ I enabled every single Samsung app via the Application manager in settings. I suppose Samsung finally finished downloading and syncing all the bloatware and **** it wanted to do, and finally let my tablet got to sleep by 4:00AM.
How do I determine what is keeping my tablet awake? Obviously Wakelock Detector and BBS has been absolutely no help thus far. Is anyone else having this problem? I need this tablet to be more reliable. I can't exit my house at the beginning of the day, not use it at all and jsut have it at 0 percent by night.
If you are going to advise flashing a custom rom/kernel, I will be doing so in the near future (once I get something settled), but as of right now it is a no go solution. I want to exactly pinpoint what my problem is, so that one day if I do happen to remain stock I can actually deal with the drain.
Some may say it is the Google Play services bug, but I have tried using "Disable Services" app to prevent this, and no change so far.
Why not just factory reset or downgrade to kitkat?
I have a specific game that my gf was playing that needed to be cracked through the obb files.
I know I can backup the apk+save data as I've done it numerous times on my Nexus 5, but I'd rather not risk losing her save data due to corruption or whatnot.
Also avoiding 5.02 lollipop/factory reset "may" be a solution but is not guaranteed. I want to know precisely what is happening, so that if the same thing occurs along in the future I don't have to downgrade/factory reset to remedy it.
Do you have any alarms or timers set, also an syncs can stop your tablet sleeping.
Have you tried "Deep Sleep Battery Saver" it controls the cpu and forces it to sleep when you tune the tablet off, it need root to work.
https://play.google.com/store/apps/details?id=com.rootuninstaller.batrsaver&hl=en
John.
I don't recall setting any alarms/timers. BBS also does not indicate any Alarms in the alarms section.
Sync has been turned off.
I tried Deep Sleep Battery Saver already on aggressive mode, no change (at the time).
Like I said, my tablet suddenly was able to deep sleep after 8 hours... I'm just thinking of alternatives to try when the drain returns since it has visited me twice.
I would install the free watchdog app and use setup to include all processes and wait for any apps to use a lot of cpu power and it will sound an alarm, you can whitelist any games or app you dont want it to monitor.
https://play.google.com/store/apps/details?id=com.zomut.watchdoglite&hl=en
I lost lost 30% in 3 hours while my tab was in it`s case during the night, luckily i had an battery monitor app set to check for high battery temps and sound an alarm, else my battery would of been flat by the morning.
EDIT: My 10.5 has never been rebooted or turned off since i got it, the battery manger says it`s been on for 157days.
John.
My advice is to do a full back up with twrp and titanium backup(to the sd card)
Factory reset then see how it goes. If the issue is gone you know where the problem lies. Add back your apps in gradual fashion with titty backup and see if any cause the issue.
You could always restore everything if there is no change.
EDIT : CRAP - Somebody on this forum suggested to use Helium to do a backup, never tried it, but i bookmarked it just in case i need it.
John.
QUOTE=ashyx;60323930]My advice is to do a full back up with twrp and titanium backup(to the sd card)
Factory reset then see how it goes. If the issue is gone you know where the problem lies. Add back your apps in gradual fashion with titty backup and see if any cause the issue.
You could always restore everything if there is no change.[/QUOTE]
ashyx said:
My advice is to do a full back up with twrp and titanium backup(to the sd card)
Factory reset then see how it goes. If the issue is gone you know where the problem lies. Add back your apps in gradual fashion with titty backup and see if any cause the issue.
You could always restore everything if there is no change.
Click to expand...
Click to collapse
+1 on this. Never used Helium but Titanium backup has been flawless for me. I would highly recommend that instead.
I was trying to avoid a full wipe. I've done backing up with Titianium Backup and ES File Explorer numerous times on my nexus 5.
Thanks for the input guys. I will try the Watchdog app as well.
The full wipe is just a test . It'll take only a few minutes to do a full device backup with twrp.You can then restore at will and be back to where you started. Anybody who has a custom recovery should have at least one full backup.
ashyx said:
The full wipe is just a test . It'll take only a few minutes to do a full device backup with twrp.You can then restore at will and be back to where you started. Anybody who has a custom recovery should have at least one full backup.
Click to expand...
Click to collapse
Exactly. One of the first things I do with every phone or tablet i purchase is root, install TWRP and take a full nandroid backup as well as install Titanium backup and backup everything. I know it may be a bit over the top but it ensures I can always get back to a clean slate or restore original state of apps. Highly recommend this as it will allow you to experiment and then return to last known state if you mess something up. If you do this, you really have nothing to lose.
As an update and for reference, the Android OS drain wouldn't stop. When I got home from work yesterday and unplugged @ 5:00PM battery was at 100%. With almost zero use, the battery had completely discharged by 4:00AM in the morning, and was overheating like crazy at 100% awake time. I couldn't take it any longer and had to do my wipe.
Things to note if someone could elaborate:
1) Prior to my wipe, I noticed that there was several issues with storage. I could not take screenshots due to "Unable to save screenshot due to storage space, app permissions or your organization", which none of the above is true. Why did this occur?
2) Prior to my wipe, I tried downloading a ROM via Chrome browser and the error "Download unsuccessful" appeared. I tried downloading the same ROM via Opera browser and it would download, but hang at 100% and I could not even find the file anywhere on my internal/external storages. Why is that?
3) I did a factory reset via TWRP. The first bootup after factory reset had me seriously worried as I thought my tablet had bricked. It took almost 5 minutes or so just to boot up. It was all fine and dandy - except the wakelock was still present. My tablet stayed awake for the entire 5 minute duration I tested (which is a small sample size and is a totally unfair sample, but I didn't have the patience to see my battery heat up due to 100% awake time). At this point in time, the screenshot function is now working again.
4) I proceeded to flash IronMan ROM, and wiped dalvik/cache right after the flash. What was extremely peculiar to me was that after my dalvik/cache wipe, the tablet rebooted instantly itself. I've never had TWRP do that. Every time I did a dalvik/cache wipe, it always informs me that the wipe is successful, and that I can go back to TWRP for more options. The reboot was unsuccessful as well, and hanged at the "Samsung Tab S powered by Android" logo, and wouldn't even proceed to the Samsung logo.
5) I rebooted into TWRP, did a factory reset cause I assumed there was something buggy with the IronMan ROM. When trying factory reset, an error popped up saying E/could not mount cache. The reset still proceeded though. Did a reboot after the reset finished and the same first boot took almost 5-10 minutes thinking my Tab S is bricked. It finally booted, and it appeared that the factory reset via TWRP didn't restore the tablet to Lollipop stock (which I assumed it would...). It was on IronMan ROM. Does anyone know how the factory reset works on TWRP? Should it have been Lollipop?
6) I rebooted just to check the boot time, and it rebooted in the normal 15 second span about so that's good. Screenshot function was still working. And most importantly....the tablet in just a 5 minute test deep sleeped for 4 mins and was awake for the 1st minute i was using it. Even after a 50 minute test, it deep sleeped for 45 minutes and was awake for 5 minutes. Which leads me to believe there is some sort of bloatware on the stock that Ironman removed, and is finally letting my tablet go to bed.
Can someone answer the plethora of questions in my procedure?