Related
hello mates,
I have rooted my htc desire and installed redux 1.2 ROM(gingerbread) with a ManU kernel...When charging the LED changes to green precisely at 90% (which i dont have a major problem with as it will go all the way to 100% if kept on charge)..also the phone will die at 10-15% of battery...I have read other threads regarding this same problem and am wondering if its a calibration error or is the problem with gingerbread ROMs as someone pointed out...Otherwise the battery is fine...and gives me a decent 1-2 days of use with moderate usage...its jus the problem abt the 15% n going dead which is a lil troublesome as the fone has died on me many a time for that last important msg, call or IM...any help appreciated...cheers..
That's not really a problem. The green LED at 90% is normal for android (try to fix it with battery calibration, helps sometimes) and the shutdown at 10-15% is also normal. Just take the last one how it is, all batteries are different. Some phones shut down at 5%, others at 20%.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
noticed this on ICS dev rom too but also had it on my old G1
wipe cache,battery stats try diffrent kernel
stupidflanders1 said:
hello mates,
I have rooted my htc desire and installed redux 1.2 ROM(gingerbread) with a ManU kernel...When charging the LED changes to green precisely at 90% (which i dont have a major problem with as it will go all the way to 100% if kept on charge)..also the phone will die at 10-15% of battery...I have read other threads regarding this same problem and am wondering if its a calibration error or is the problem with gingerbread ROMs as someone pointed out...Otherwise the battery is fine...and gives me a decent 1-2 days of use with moderate usage...its jus the problem abt the 15% n going dead which is a lil troublesome as the fone has died on me many a time for that last important msg, call or IM...any help appreciated...cheers..
Click to expand...
Click to collapse
You should try calibrating your battery for the 10-15% dying problem.
And as for the 90% LED changing to green, all AOSP ROMs do that, so no worries there
What worked for me was charging it while the phone is on, when the LED turns green, power it off and charge it again till it turns green.
Repeat this twice and then reboot.
galdel said:
What worked for me was charging it while the phone is on, when the LED turns green, power it off and charge it again till it turns green.
Repeat this twice and then reboot.
Click to expand...
Click to collapse
This is to calibrate the battery. Some people find it useful to run a program called BatteryRepair, in my case I noticed a clear improvement on battery performance.
To avoid calibration problems with the battery, remember to unplug your phone when you flash a new rom!
Tapatalking
Turning off at 15% of battery with Supernova 2.4 ROM
I am using Supernova Xtreme 2.4.0.0 ROM, and my phone turns off at 15% of battery. My battery is freshly calibrated and this problem did not occured with LeeDroid ROM and with the stock ROM neither. On the Droidzon page I have found some info in FAQ section, which says the following:
Question: Recently I let my battery go completely flat. When I switched my handset back on I was bombarded with forced close messages.
This has been reported once previously, but could not be reproduced under Sibere’s extensive testing under similiar conditions. For the same reason, unfortunately, we dont have a solution too. The OS is supposed to prevent a complete drain, and to shutdown at 15% and then 5%. The shutdown at 5% is supposed to be forced too. If it shutdowns, then this issue shouldnt occur. Data2SD depends on a normal shutdown to prevent data corruption. Once Data corruption has occured due to untidy shutdown, data is not unmounted cleanly, and then the issue can recur on every subsequent boot, which would require a complete reinstall.
So it seems to be normal, connected to the ROM, and NOT connected to my battery (it is calibrated).
My question is (which goes to Droidzone firstly), what should I do, if I want to use this ROM, but I do not want it to turn off at 15% rather I want it to turn off my phone at 2%?
Sofokles_ said:
I am using Supernova Xtreme 2.4.0.0 ROM, and my phone turns off at 15% of battery. My battery is freshly calibrated and this problem did not occured with LeeDroid ROM and with the stock ROM neither. On the Droidzon page I have found some info in FAQ section, which says the following:
Question: Recently I let my battery go completely flat. When I switched my handset back on I was bombarded with forced close messages.
This has been reported once previously, but could not be reproduced under Sibere’s extensive testing under similiar conditions. For the same reason, unfortunately, we dont have a solution too. The OS is supposed to prevent a complete drain, and to shutdown at 15% and then 5%. The shutdown at 5% is supposed to be forced too. If it shutdowns, then this issue shouldnt occur. Data2SD depends on a normal shutdown to prevent data corruption. Once Data corruption has occured due to untidy shutdown, data is not unmounted cleanly, and then the issue can recur on every subsequent boot, which would require a complete reinstall.
So it seems to be normal, connected to the ROM, and NOT connected to my battery (it is calibrated).
My question is (which goes to Droidzone firstly), what should I do, if I want to use this ROM, but I do not want it to turn off at 15% rather I want it to turn off my phone at 2%?
Click to expand...
Click to collapse
I'm afraid this is not similiar to the issue in the FAQ. Your issue is that phone shutsdown at a level earlier than expected. The Data corruption issue is because the phone did not shutdown at the expected level and went down to as far as zero level of the battery, which resulted therefore in an untidy shutdown with no sync or clean unmount of data2sd partition, and hence ext4 errors. The 15% shutdown level is a normal soft shutdown prompt (which was missing in case of the issue reported by the user). The shutdown at 2% is the normal forced shutdown by OS.
As I said previously, your issue seems to be due to a poorly calibrated or defective battery, and it would help to do a calibration as per guides on XDA. If this fails, have the battery checked. To reiterate, it's not a rom issue and not something like a bug in the rom.
Thanks. So normally the phone with Supernova ROM should turn off at 15%. After that I have to be able to turn it on again, and use it till it drains to 2%, and shuts down finally.
For me it just shuts down at 15% and then when I switch it on and it boots up, the battery level shows 0% and it shuts down immediately.
Sofokles_ said:
Thanks. So normally the phone with Supernova ROM should turn off at 15%. After that I have to be able to turn it on again, and use it till it drains to 2%, and shuts down finally.
For me it just shuts down at 15% and then when I switch it on and it boots up, the battery level shows 0% and it shuts down immediately.
Click to expand...
Click to collapse
No, a normal rom would popup a warning at 15%, asking the user to shutdown. If he doesnt, it would continue, and then give additional warnings, and finally do a forced shutdown at 2%. If it shutsdown before that forcibly, it's something peculiar to your hardware.
Ooops, so Supernova ROM should behave exactly the same way as a stock ROM (or any other) does in terms of warnings and shutdows.
I might try to do something with battery calibration. Should I do it before or after flashing Supernova? Or it does not matter? If I flash a new ROM, does it delete battery logs or it stays as it was before flashing?
Sofokles_ said:
Ooops, so Supernova ROM should behave exactly the same way as a stock ROM (or any other) does in terms of warnings and shutdows.
I might try to do something with battery calibration. Should I do it before or after flashing Supernova? Or it does not matter? If I flash a new ROM, does it delete battery logs or it stays as it was before flashing?
Click to expand...
Click to collapse
Correct. For all intents and purposes, Supernova is exactly like a Stock rom. Difference is only in where internal apps are stored.
The so called calibration is just a file at /data, which means it will be wiped when you do a wipe for rom install.
[Update] Problem solved. I flashed UOT battery MOD after first boot (not before). Now it works perfectly.
A flashed the ROM again, did the battery calibration several times, but the phone keeps turning off at 15%. I checked battery voltages at different levels of battery, and I experienced that at 16% it is 3635 mV, then it turns off below 15%. When I turn it on, battery level is 0% and the voltage is 3390 mV, and when it is charged up to 1% it is 3723 mV, which is higher than it was at 16%. What is wrong here? Actually I use UOT kitchen battery MOD, can this confuse the system somehow?
Im having a sudden battery issue with my G2 that started about 2 weeks ago. Im currently running 2.3.4 and have been for a while now. When using my phone at near full charge, it randomly shuts down. When it restarts it states I have less than 2% power and the red "x" is at the top. A few seconds later it shuts down again as it if it has no power. The only way to correct this is to remove the battery completely and reboot. Once I reboot, the battery level goes back to a normal state or it will read somewhere near 50%. Ive also noticed the following: the battery will charge VERY slowly. Sometimes overnight it still won't say fully charged. I've done the following to try to fix:
1. I replaced the battery with a brand new one. Same issues right off the bat.
2. Wiped my phone and reinstalled.
3. Checked to see if any APP was draining the battery or causing the issue. None are!
I've seen this issue reported by other G2 users on the Tmobile Support forum and none of them have gotten any solid results. I've browsed this forum some and couldn't find it either, unless i missed it.
Any help is appreciated!
Lou
louballs said:
Im having a sudden battery issue with my G2 that started about 2 weeks ago. Im currently running 2.3.4 and have been for a while now. When using my phone at near full charge, it randomly shuts down. When it restarts it states I have less than 2% power and the red "x" is at the top. A few seconds later it shuts down again as it if it has no power. The only way to correct this is to remove the battery completely and reboot. Once I reboot, the battery level goes back to a normal state or it will read somewhere near 50%. Ive also noticed the following: the battery will charge VERY slowly. Sometimes overnight it still won't say fully charged. I've done the following to try to fix:
1. I replaced the battery with a brand new one. Same issues right off the bat.
2. Wiped my phone and reinstalled.
3. Checked to see if any APP was draining the battery or causing the issue. None are!
I've seen this issue reported by other G2 users on the Tmobile Support forum and none of them have gotten any solid results. I've browsed this forum some and couldn't find it either, unless i missed it.
Any help is appreciated!
Lou
Click to expand...
Click to collapse
Power down and charge 'til it thinks it's fully charged (should be a green light). If it doesn't show a green light (like you said, it won't fully charge), just leave it charge for a while (overnight would be good). Boot into recovery, either by booting Android + rebooting recovery or by rebooting recovery through bootloader, go to advanced and select wipe battery stats... I think CWM 5 still has this option (don't know about 4EXT)
zeppelinrox has a battery calibrator script which is useful and can automatically delete battery stats once fully charged... I can't find it though. I'll attach / PM it if you need it.
BTW I'm not sure if this is the problem, it could be hardware related. I'd try it though, it might help.
If all else fails and you're sure it's not a hardware problem, I'd do a factory reset and /or reflash ROM.
HTCDreamOn said:
Power down and charge 'til it thinks it's fully charged (should be a green light). If it doesn't show a green light (like you said, it won't fully charge), just leave it charge for a while (overnight would be good). Boot into recovery, either by booting Android + rebooting recovery or by rebooting recovery through bootloader, go to advanced and select wipe battery stats... I think CWM 5 still has this option (don't know about 4EXT)
zeppelinrox has a battery calibrator script which is useful and can automatically delete battery stats once fully charged... I can't find it though. I'll attach / PM it if you need it.
BTW I'm not sure if this is the problem, it could be hardware related. I'd try it though, it might help.
If all else fails and you're sure it's not a hardware problem, I'd do a factory reset and /or reflash ROM.
Click to expand...
Click to collapse
Thanks for the tip. I had already deleted the battery stats bin file from the system and rebooted and received the same results (assume thats what your fix does). I've also reinstalled the rom and had no issues. Ive done searches and found that SEVERAL other people with the G2 had this issue. Kind of surprised it hasnt yet been addressed on this forum. Back in 2011 Tmobile was asking for people to volunteer some info in order to fix it. Apparently nothing was ever done and when i call in (several times), no one seems to know what im talking about even when i point them in the direction of their own forums. I'm really at a loss and don't feel like paying out the a$$ for a new phone when I know this is not something I did.
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.
Hi, I just bought a used galaxy tab s 10.5 and the battery jump from 20 to 99% in 20 minutes when charging . I started using it at 100% and it shuted down for low battery in 30minutes and I power it on again a it said 75%. How do you thinks is going on with the tablet? Thanks and sorry for my bad english.
Do you know if it's rooted and has a custom recovery. Clear cache and fix permissions in recovery mode
No root
It is not rooted and it have stock recovery. Is there an app to reset battery stats?
MLopez14 said:
It is not rooted and it have stock recovery. Is there an app to reset battery stats?
Click to expand...
Click to collapse
try booting stock recovery and do a factory reset.if that don't work than look into rooting it and TWRP so you'll have the option to flash something else or clear the cache and fix permissions
done
I did the factory reset and the permissions fix thrught TWRP but the battery still crazy. What more can I do?
I got the tablet down to 0% battery, to the point that it wouldn't turn on.
Took off the back cover using prying tools and then disconnected the battery, power cycled thrice by holding and releasing power button and then reconnected the battery and let it charge overnight to 100% and now battery life is amazing, don't have those drastic drops anymore.
There are no warranty stickers torn etc involved with doing this so you don't have to worry about voiding it. Just take your time and start at the microsd slot, open the hatch and work your way around slowly. Its difficult first time around because there is adhesive glue as well as clips holding it down. But still very doable without damaging anything.
Here is a link to a battery calibrator for root users
https://play.google.com/store/apps/details?id=com.vitula.batterycalibration
There are other calibration apps
Definitely other options before taking it apart [emoji111]
..
I tried with the battery calibration app and nothing. I leave you a screenshot , thats is WHITHOUT any charge, when it shuted out I just turn it on again. What is indexservice?
OK after ready the links below I believe a debloated ROM could solve your problem
https://www.google.com/search?q=wha...google&sourceid=chrome-mobile&espv=1&ie=UTF-8
List of Roms
[emoji652]
http://forum.xda-developers.com/galaxy-tab-s/development
I will try a debloated rom because son process called index service is draining the 60% of my battery, but is rare that the tablet shuted down and when I tried to turn in on and it shuted down immediately for low battery, but and enter in recovery mode and leave it on with max brightness and it stay awake for 4 hours!! Even when twrp said that is has only 1%.
MLopez14 said:
I will try a debloated rom because son process called index service is draining the 60% of my battery, but is rare that the tablet shuted down and when I tried to turn in on and it shuted down immediately for low battery, but and enter in recovery mode and leave it on with max brightness and it stay awake for 4 hours!! Even when twrp said that is has only 1%.
Click to expand...
Click to collapse
Post back to let us know it is after a ROM flash
Can you post a full screenshot of your battery settings. You just posted the graph. Not sure about the index service, but knox drains battery too.
Had the same issue crop up on mine. Did the the battery 0% drain then recharge a few times. And factory format. Now it just randomly keeps restarting (even when on charge now). Called Samsung and they have sent a pack to post it to them to sort I hope.
Now with the debloated rom the crazy battery drops have stop but I'm having random restarts. What's is happening now?
I know it's a lot of work and getting frustrating but let's try Odin back to stock .
http://forum.xda-developers.com/showthread.php?t=2800372
Let's try back to stock. Thanks a lot for taking time to help me.
MLopez14 said:
Let's try back to stock. Thanks a lot for taking time to help me.
Click to expand...
Click to collapse
I'm on here all the time and when I get my devices the way I want them I just browse around trying to help with what I can .no problem and your welcome
...
Now with stock rom I still having random restarts and battery drops. I dont know what more to do and I dont have warranty.
I leave it all night on plugged in the charger and it didn't restart but when I started using it, it freezes up and restart.
Now it sounds like a kernel issue .I really dislike that cortex chip to
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?