Related
So, I'm at a loss of what to do here. No matter what settings I seem to use I can't get good/decent battery life.
In fact, I get terrible battery life. With light to moderate usage I have to charge my phone at least two times a day, mostly three. Current widget reads that at standby I'm anywhere between 55mA-70mA and when in use 200mA-500mA. When charging it reaches 400mA-600mA
I see everyone talking about being able to get 5-10mA and I'm amazed at this. I've searched and read most "Battery saver" threads and none of it seems to work.
I was originally using Chucky rom lite and when I noticed the drain was abnormal I switched to the set up that chiasoft uses in his ReadMe for the ROM (stock 2.10ROM/2.08 radio).
Although since switching to the stock WinMo ROM I had repeated BSOD and SOD issues. To the point that it became unusable. I switched over to latest Energy ROM.I installed EBL and on both Stock and this Energy ROM. I am still having BSOD/SOD problems. Could it be the EBL? I plan on upgrading the radio to 2.12 in a few after I test out this EBL theory.
My setup as of this post is this:
WinMo ROM: Energy.BLACKSTONE.21916.Sense2.5.Nov.08 (Switched back to Stock 2.10)
Radio: 2.08.50.08_2 (Switched to 2.12)
Android: MooMoo Froyostone Sense 3.2 w/hastrain kernel
SetCPU:
998max/245min Ondemand on boot
Profiles: Screen off; Priority 100; 384max/245min ondemand
Battery <25% 576max/245min Priority 0 ondemand
Sampling 20000; Up Threshold 40
Advanced Task Killer:
Kill Level Agressive
I really don't want my LI-ON battery to die before I've even had the phone for the year. So if anyone can think of anything to help I'd be ever so grateful.
And of course, thanks to all the people who make all this possible.
(Sorry for the tl;dr post. I wanted to give as much info as possible.)
when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.
mofoahh said:
when you fully charge your batter what is your mV ? use the battery life widget to determine this. If it is not nowhere 4000mV once fully charged, you might need to consider buying a replacement battery.
btw. my mA reading is actually worst than yours. Might have to calibrate the battery again later.
Click to expand...
Click to collapse
idk what it is fully charged. I'll be sure to check it later though. How do you calibrate the battery?
Also, I realized that I made an oversight on my part. When I switched to the stock WinMo rom I hadn't realized fully that it changed my Radio to 2.08 even though I posted it.
The rom chef recommends 2.10ROM/2.12 Radio, so that's what I switched to to check out that combination.
btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.
mofoahh said:
btw change it to interactive not on demand.
you charge the battery when your phone is off. Till your charge indicator turns green.
Once that is off. you can use root explorer or adb and go to rm/data/system delete the batterystats.bin leave your phone plugged in while you are deleting the batterystats.bin file
i prefer root explorer. but its not free and your device has to be rooted.
let the phone drain the battery till its dead and turn it on again to make sure it is completely dead.
charge the phone like you would usually afterwards.
Click to expand...
Click to collapse
I don't have interactive in my options.
what version are you running?
mofoahh said:
what version are you running?
Click to expand...
Click to collapse
2.03 I got it through here.
Just installed 2.04 and there still isn't an interactive.
thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4
mofoahh said:
thats odd. because im on 2.0.4 also and I am able to select interactive.
btw i followed this guide for the battery conditioning.
http://forum.xda-developers.com/showthread.php?t=827762&highlight=ultimate+setcpu
and this one for my setcpu settings.
http://forum.xda-developers.com/showpost.php?p=8246854&postcount=4
Click to expand...
Click to collapse
Yeah. No interactive settings. Also, that guide recommends 1190 max, but mine only goes up to 998.
Also, I finally got it to down to 7mA in standby. When I changed the radio to 2.12 and using a 2.10 stock WinMo rom.
no issues here getting 48 hours of light use, or a full 24 of moderate use...
I've yet to "condition" my battery. I'm worried it'll do more harm than good. Especially since I just got it finally to a decent mA draw. Although I'm worried my phone won't charge up to 100%. Always stop at 95.
Is conditioning really necessary/important?
easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..
t1h5ta3 said:
easy answer... whats your full charge voltage? shuld be 4.2
if not , your looseing batt life..
Click to expand...
Click to collapse
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.
mofoahh said:
yes full charge voltage should be around 4.2. Try charging it with the phone OFF till your charge indicator is green. This way you can achieve a full charge.
By the way how the hell are you getting 48 hours on light usage?? excuse my language. What are your setcpu settings, configurations. etc.
Click to expand...
Click to collapse
Yeah, 48 hours seems improbable. I finally got it down to 7-10mA on standby, and I think it charges up to 4.2 but I'll find out for sure tonight.
same
I had the same problem, make sure you use EBL android launcher and set to autoboot at 3 seconds. Make sure you restart your phone anytime youw ant to load android. I assure you this will work.
My HD2, like all others can be flattened in 2-3 hours with windows/android if used hard, the difference seems to be on very light usage/standby win mobile could last 4 days... with everything turned off and basically not used Android would struggle to last 2 days !
Same phone same network/signal levels etc, can only be poor power management within Android, and I think that means voltages for all the processor and comms modules, not just a simple case of turning down speeds.
What do others think ?
Update: Upon switching to WinMo:2.10 and Radio:2.12+ MooMoo's MMS fixed froystone3.2 I was achieving 6-10mA in standby. The phone would last all day with a two-three hour charging period with moderate usage. Low battery use, rare DC's. Perfect. Best build I've used so far.
I'm noticing a new problem however, and I wonder if it's happened to Chiasoft who recommended this build. I'm getting serious touch screen freezes since last night. Anytime before that the set up was working AMAZINGLY.
Now? It's almost unusable sometimes. This morning it was happening in Android so I switched to WinMo and surprisingly enough it happened in there too. So I read touch freezes are Radio problems mostly. Is this true? Should I switch to a new radio? I'm confused as to why it would just randomly start happening though and worried it would mess up my battery troubles I just solved.
Any advice?
Hmm. I noticed that it almost always freezes when I hold down the end home button to turn off the phone or data or to silence it. I can't actually use the touch screen again until I hit the button again to put it to sleep.
I wonder if it's hardware related because it was happening in WinMo that way as well.
Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.
pretzdothack said:
Okay, so now the entire adroid system is acting up mostly related to the touchscreen. Like I use the calculator and it appears that i'm holding a button down. Or I try to make a call and it's not responding. It appears that when I hit end call button repeatedly it allows me to unlock the phone. But when holding down the end call button to get to the Power Off screen nothing in that menu is responsive.
It seems... software related, but I'm not sure. Any info would be helpful. I'm going to reformat my card and reinstall droid and see what happens.
So, called t-mobile. They're sending me a new replacer phone. Oh well. We'll see how that one goes.
Click to expand...
Click to collapse
I give you only a very short suggestion
You have just to DELETE SETCPU
and delete ANY TASK KILLER (you can keep it just to close any apps that could hang, but not to "free up ram")
Android is not Windows, you dont need to free up ram, and you dont need to overclock/undervolt to gain some minutes of battlife despite stability.
Talk to any Dev and they will confirm this.
Good Luck
Hey guys just like we all i suffered from the insane battery drain in CM7 with my lovely Vibrant. But yesterday night i found a cure that gives me now great battery life - almost like a 2.2 rom.
What i did?
I googled around and found this post:
1. Open up the dialpad, and type:
*#*#4636#*#*
(the numbers are for 'info'; don't press call, it should automatically go to a 'Testing' menu)
2. Go into 'Phone information'
3. Press Menu, and select 'Select radio band' (this will result in a force close, but that's what we want.. just keep going.)
4. Go back into 'Phone information' and scroll down to the bottom'. It will probably still say 'CDMA auto (PRL)', but the problem is this is probably a visual glitch. Or it might say 'Unknown'. Either way, switch it to something else, then switch it back to 'CDMA auto (PRL)'. Then you can turn off the radio and turn it back on with the button right underneath that.
5. At this point, the fix has been applied, but it would be a good idea to clear the battery stats to get a fresh start. So boot into recovery and do that, then reboot. The fix *should* stick after this reboot, but I think it didn't when I first did it. But assuming it does, then you're golden. It will be like this for all other reboots. If it does not, then just do it again. You can tell if it worked if when you go into battery usage, and go into cell standby, the TWS% is much lower. I charged mine completely overnight after applying this fix and have been off the charger now for over a half hour and TWS% is still at 0% (even though cell standby is at 46% (but that's not a problem at all..), and my battery is still at 100%
My Vibrant gives me now GSM/CDMA auto (PRL) as network type.
So let me know whether it works for you too or not.
For me its asesome, since i can enjoy CM7 all day long ;-)
Seems to be working fine for me, would I have to do this for every nightly.
Sent from my SGH-T959
great find +1 the battery life of cm7 drove me away to a JVQ rom but imma try this find and use it!
I don't know if the cure will work for me, too. I found out that my device doesn't enter deep sleep, so even when I'm thinking it's sleeping, it is not.
The process Android System keeps it awaken. At least it did in #54 and other recent builds. It completly depletes my battery like me drinking lemonade.
Does it sleep for you?
I like this. I can actually stream music while charging without slowly losing charge.
I'm going to try this and see what happens
Hope this gets run through Atinm.
kleineschatz said:
Hey guys just like we all i suffered from the insane battery drain in CM7 with my lovely Vibrant. But yesterday night i found a cure that gives me now great battery life - almost like a 2.2 rom.
What i did?
I googled around and found this post:
1. Open up the dialpad, and type:
*#*#4636#*#*
(the numbers are for 'info'; don't press call, it should automatically go to a 'Testing' menu)
2. Go into 'Phone information'
3. Press Menu, and select 'Select radio band' (this will result in a force close, but that's what we want.. just keep going.)
4. Go back into 'Phone information' and scroll down to the bottom'. It will probably still say 'CDMA auto (PRL)', but the problem is this is probably a visual glitch. Or it might say 'Unknown'. Either way, switch it to something else, then switch it back to 'CDMA auto (PRL)'. Then you can turn off the radio and turn it back on with the button right underneath that.
5. At this point, the fix has been applied, but it would be a good idea to clear the battery stats to get a fresh start. So boot into recovery and do that, then reboot. The fix *should* stick after this reboot, but I think it didn't when I first did it. But assuming it does, then you're golden. It will be like this for all other reboots. If it does not, then just do it again. You can tell if it worked if when you go into battery usage, and go into cell standby, the TWS% is much lower. I charged mine completely overnight after applying this fix and have been off the charger now for over a half hour and TWS% is still at 0% (even though cell standby is at 46% (but that's not a problem at all..), and my battery is still at 100%
My Vibrant gives me now GSM/CDMA auto (PRL) as network type.
So let me know whether it works for you too or not.
For me its asesome, since i can enjoy CM7 all day long ;-)
Click to expand...
Click to collapse
I hope this works, but when i first went to phone info and did radio band, it asked for country, i choose usa, it didnt FC thou, then when my setting was already GSM/CDMA (prl) . I will report back tommorow how it goes. thanks
I'm guessing the same would apply to MIUI?
It definitely seems to be doing something. My signal hasn't dropped below the full four bars yet, which is weird considering it's normally around 1 or 2. The phone also seems to go to sleep faster, but that could be placebo.
Sent from my SGH-T959 using XDA App
duboi97 said:
I'm guessing the same would apply to MIUI?
Click to expand...
Click to collapse
yes i tried this it didnt seem to work for me i dont think i got it to stick on im gona try it again
didnt get Force closed at the select radio band. Now what should I do?
on Miui I had to select Turn Radio Off first, then it forced closed and now it seems to stick when I change radio bands. Just turn on/off radio a few times and it should help.
ferhanmm said:
on Miui I had to select Turn Radio Off first, then it forced closed and now it seems to stick when I change radio bands. Just turn on/off radio a few times and it should help.
Click to expand...
Click to collapse
Thanks! Finally I got it to force closed and I did everything else. But I went into cell standby I saw my TWS% is 71 when my cell standby is only 21%. Is that a problem?
SuperJMN said:
I don't know if the cure will work for me, too. I found out that my device doesn't enter deep sleep, so even when I'm thinking it's sleeping, it is not.
The process Android System keeps it awaken. At least it did in #54 and other recent builds. It completly depletes my battery like me drinking lemonade.
Does it sleep for you?
Click to expand...
Click to collapse
I had this same problem. Apparently alot of others did too, but no one seems to have a solution that I have seen.
Sent from my SGH-T959 using XDA App
Effect of USB Charging on CPU Idle Utilization CM7
First, this test was performed on nightly #55 with KB5 baseband. I have performed this on KA7 as well and found the results to be similar.
I am very sensitive to my battery utilization. In turn, I am also a very frequent charger. Even if I'm at 80%, I feel I must plug my phone in as soon as possible. Because of this, there is hardly a time where my phone is on during a session in which it had never been on usb. This changed, however, this last weekend. I was playing around with KA7 vs KB5, and was away from my computer and charger. Later, when I reviewed my cpu utilization during idle time, I was shocked to see that the phone was just sipping the battery. Less than 1% utilization in System panel.
My initial reaction was "KA7 is amazing." However, the next morning, battery usage appeared to be the same as normal. On a hunch, I wondered if it was possible that it was the charging that is causing issue. As we all know, when the phone is plugged in, cpu utilization is fairly high (~30%), and some even report the battery getting hot (in some cases, even to reboot the phone). But -- is it possible that even after you unplug, there is some lingering "stuff" happening that will not go away, regardless of how long you idle?
What I did was simply charge my phone fully, unplug, reboot. I consistently find that my phone will go in and out of very low cpu utilzation state when I do this. If I go into airplane mode, I will even see full sleep state with no green bars in System panel (not that I would do this, as I like to USE my phone).
I am very curious if some of you may be able to try this experiment and report back. If this is confirmed, I wonder if there may be a way to determine what is getting stuck and robbing our cpu cycles after the phone is unplugged from charging.
Attached are four screenshots:
syspanel_pre_reboot_8hr.jpg: showcasing the long overnight charge, followed by very low activity, yet with >3% cpu utilization while idle. (by wall charge, though this has shown to be the case via computer usb charging as well)
syspanel_pre_reboot_2hr.jpg: a closer look at the idle time after the charge.
syspanel_post_reboot_8hr.jpg: A big picture view of the charging, the reboot, and the subsequent idle time. The first thing I did once the phone booted was download and install several app updates from market. I wanted to stress the phone before letting it fall back to idle.
syspanel_post_reboot_2hr.jpg: here you can see the lower idle cpu utilization on the phone. Initially there is activity as I updated apps from the market, and then it fell to hover around ~1%.
This behavior can be replicated and repeated on my phone every time. I was hoping someone with logcat experience may be able to help me define a filter so that we can see exactly what processes plugging the phone into usb starts, compared to which it terminates when unplugged. If we were to find this, I would suspect it could be added to the code itself.
THAT is what I'm experiencing TOO.
I have tried that fix. When entering the "select radio band" it doesn't force close. I just see "EURO Band" , "USA Band" etc...
also on the bottom it says "GSM only".
Is the fox already applied for me?
I'm using TRIGGER (CM7 based).
ginzberg said:
First, this test was performed on nightly #55 with KB5 baseband. I have performed this on KA7 as well and found the results to be similar.
I am very sensitive to my battery utilization. In turn, I am also a very frequent charger. Even if I'm at 80%, I feel I must plug my phone in as soon as possible. Because of this, there is hardly a time where my phone is on during a session in which it had never been on usb. This changed, however, this last weekend. I was playing around with KA7 vs KB5, and was away from my computer and charger. Later, when I reviewed my cpu utilization during idle time, I was shocked to see that the phone was just sipping the battery. Less than 1% utilization in System panel.
My initial reaction was "KA7 is amazing." However, the next morning, battery usage appeared to be the same as normal. On a hunch, I wondered if it was possible that it was the charging that is causing issue. As we all know, when the phone is plugged in, cpu utilization is fairly high (~30%), and some even report the battery getting hot (in some cases, even to reboot the phone). But -- is it possible that even after you unplug, there is some lingering "stuff" happening that will not go away, regardless of how long you idle?
What I did was simply charge my phone fully, unplug, reboot. I consistently find that my phone will go in and out of very low cpu utilzation state when I do this. If I go into airplane mode, I will even see full sleep state with no green bars in System panel (not that I would do this, as I like to USE my phone).
I am very curious if some of you may be able to try this experiment and report back. If this is confirmed, I wonder if there may be a way to determine what is getting stuck and robbing our cpu cycles after the phone is unplugged from charging.
Attached are four screenshots:
syspanel_pre_reboot_8hr.jpg: showcasing the long overnight charge, followed by very low activity, yet with >3% cpu utilization while idle. (by wall charge, though this has shown to be the case via computer usb charging as well)
syspanel_pre_reboot_2hr.jpg: a closer look at the idle time after the charge.
syspanel_post_reboot_8hr.jpg: A big picture view of the charging, the reboot, and the subsequent idle time. The first thing I did once the phone booted was download and install several app updates from market. I wanted to stress the phone before letting it fall back to idle.
syspanel_post_reboot_2hr.jpg: here you can see the lower idle cpu utilization on the phone. Initially there is activity as I updated apps from the market, and then it fell to hover around ~1%.
This behavior can be replicated and repeated on my phone every time. I was hoping someone with logcat experience may be able to help me define a filter so that we can see exactly what processes plugging the phone into usb starts, compared to which it terminates when unplugged. If we were to find this, I would suspect it could be added to the code itself.
Click to expand...
Click to collapse
i usually reboot after i charge when i wake up then i send a few texts and work the phone a bit my battery life isnt too bad
romitkin said:
I have tried that fix. When entering the "select radio band" it doesn't force close. I just see "EURO Band" , "USA Band" etc...
also on the bottom it says "GSM only".
Is the fox already applied for me?
I'm using TRIGGER (CM7 based).
Click to expand...
Click to collapse
no i have the same problem for some reason i cant get this fix to work either
Gave it a try, will see what happens. Battery life is now the only bummer on CM, if this solves it, I'll be a happy guy.
Hope someone can help me solve this issue.
The Setup
I recently went out of the country and before I left I unlocked my GS4 following from wonderhowto[dot]com
Arrived to my Carribean destination, bought a prepaid SIM, popped her in and everything worked great.
Problems started when I flew back into Miami. I removed my prepaid SIM and installed my old one, changed my APN name back
and rebooted the phone. Decided to plug it into my laptop (USB3.0) to get some extra juice before the next flight and I noticed that
the battery was actually going down and quite quickly too, about 1% every 3 minutes. The phone was also doing a lot of connecting and disconnecting from the laptop even though it was not being moved.
I use two batteries which I have an external charger for , so this didn't slow me down too much.
After a few days, I thought maybe by unlocking the phone I had left it in some "roaming" state where it was eating up battery looking for its signal, so I decided that I'd restore it to the nandroid backup ROM Manager created before I did the unlock procedure. OH NUGGETS!
Things got ugly , quick!. In the process of trying to restore got MD5 mismatch error, so I went back to 3 previous backups before all of which said either "MD5 mismatch" or unable to open .zip -None of them worked.
Thankfully I had saved a copy of the backup folder in clockworkmod to my PC and tried to load that, it started and then get to writing /data and said error writing data.
I rebooted. Bootloop.
After a few hours of attempts with KIES, and some well timed cold beer deliveries from my wife, I finally got the phone back to stock version.
Rooted it again, motochopper, And loaded GoldenEye Rom v 8.0 . Still slow to little or no charging.
Loaded PACMAN and noticed something that should be mentioned.
Pacman rom has its own little battery widget that sits in the top tray and shows the %. It glows green from bottom to top to show that it is charging. I noticed on every couple of cycles, the battery meter would flash red for a quick second before turning green and sweeping up.????
Went back to a backup of GoldenEye8.
The current status
The phone is currently plugged in to the stock charger (2A) and stock cable. It has charged up only about 3% in 20 minutes time. I have it in battery saving mode with wifi on , and EVERYTHING else turned off.
Battery info says:
Temp 87.3 F
Voltage 4033mV
Plugged True
Charging
Li-ion
Health:Good
Charge Type : AC
Battery use shows 62% of battery use coming from SCREEN (Yes I have auto-brightness set, and NO live wallpaper)
Anyone have some good input?
Maybe its a bad cord? Or bad USB port/connection on the phone it self...
Sent from my SGH-I337 using Tapatalk 4
62% screen usage is normal, I sometimes see over 70% with my brightness all the way up.
Make sure apps aren't keeping it from going idle and staying active.
Battery temp. seems a bit high. General causes of that are a faulty cable.
Download greenify and hibernate any apps that may be running unnoticeably in the background.
If your kernel allows fast charging (disables access to phone storage while fast charging is on) enable it while charging if you're not using the phone.
Play with CPU and GPU governors in your kernel to save battery life. I.E: I put my CPU governor on "powersave" while idle and not using the phone for anything extensive.
Sent from my SGH-I337 using XDA Premium HD app
mg2195 said:
Maybe its a bad cord? Or bad USB port/connection on the phone it self...
Sent from my SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
Tried two other cords,but they just made it worse. They actually caused it to look like its charging but the battery level was going down.
Your second suggestion is probably right, but i'd like to exhaust my options first before having to restore and send to creator. I do find that with the stock cable and no external case on it stays plugged in well and doesn't make any "interrupted connection" noises.
With stock charger and cable and minimal functions running its charging about 1% every 4 minutes. ( Approx 6.5 hrs to full charge )
I feel like the hardware must be working in order to do that, and that the software is putting some kind of excessive strain on it. Possibly?
The battery use still shows, screen as the major contributor at 61% , so I switched from a really high resolution static background to a low res one. ( results to follow)
Downloading WanamLite now and going to try that out, also going to try performing the unlock procedure I did in reverse order and see what that does. Keep you posted. Open to suggestions.
Br4nd3n said:
62% screen usage is normal, I sometimes see over 70% with my brightness all the way up.
Make sure apps aren't keeping it from going idle and staying active.
Battery temp. seems a bit high. General causes of that are a faulty cable.
Download greenify and hibernate any apps that may be running unnoticeably in the background.
If your kernel allows fast charging (disables access to phone storage while fast charging is on) enable it while charging if you're not using the phone.
Play with CPU and GPU governors in your kernel to save battery life. I.E: I put my CPU governor on "powersave" while idle and not using the phone for anything extensive.
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the advise, I'm running greenify and its really only showing facebook and my sms app, I hibernated facebook anyways just to test it, but I know out of the box , on a car adapter this thing was charging 1%/min , maybe I have a bad ROM/Kernel mix?
prodigaltaurus said:
maybe I have a bad ROM/Kernel mix?
Click to expand...
Click to collapse
Doubt it, but maybe you can try going from touchwiz to aosp. Very much more lightweight, though you'll lose some s4 features. If it is faulty hardware/battery I'd just save yourself the trouble and swap it for a new one; or try another battery. I guess you can try doing a compete wipe and flashing a fresh ROM with a kernel you know will definitely run smooth with it.
Sent from my SGH-I337 using XDA Premium HD app
Br4nd3n said:
Doubt it, but maybe you can try going from touchwiz to aosp. Very much more lightweight, though you'll lose some s4 features. If it is faulty hardware/battery I'd just save yourself the trouble and swap it for a new one; or try another battery. I guess you can try doing a compete wipe and flashing a fresh ROM with a kernel you know will definitely run smooth with it.
Sent from my SGH-I337 using XDA Premium HD app
Click to expand...
Click to collapse
Already tried the second battery, no luck. Any suggestion on the rom/kernel combo?
I use task650 with kt's kernel and it's excellent. Though it's all opinion, there is many great combinations. Some ROMs come packaged with their own kernel or a custom one.
Sent from my SGH-I337 using XDA Premium HD app
IMO: those temps are pretty normal.
Why you don't try a bone stock rom and see how it respond for a few hours, if the stock rom behaves the same, probably you will need to send it for warranty.
i changed the phones battery i noticed that it is acting weird. i fully charged the phone and this morning i took the charger out and in 30 minutes without touching it it dropped to 95% and from 7 am until 4 am the battery is now at 26% without even touching it. what happens is when i look at it it says that is still 95 but then when i go to settings/battery then it changed to 26 out of nowhere. i tried putting the old battery but still no go.i tried installing a custom rom and kernel and i even tried 4.2.2 stock and 4.3 stock and even changing radio and i looked online for help but same thing happens. i dont know whether is a battery problem or a software or hardware problem. i really need the phone working and i was wondering if someone had the same problem and also if you used to charge the phone with a wireless charging station because i saw something about using it and then not getting enough power from stock charger. i bought it on ebay and the previous owner had a wireless charging if it helps and he told me a new battery would fix the blinking red light of death. any fixes for this? here is the video of the weird battery problem and it is on airplane mode and safe mode. https://www.youtube.com/watch?v=PlFqagJ2v-k here is another video of how slow the device detects the battery drain https://www.youtube.com/watch?v=Blz68xgQcDU
Install the following app:
https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats
You can find a free version that works just as great but I personally like this. Charge to 100% then just use it normally. After it drains, open up the app and see what wakelocks there are. You can Google them and it'll tell you what to disable or uninstall from there
Sent from my Nexus 5 using XDA Premium 4 mobile app
I have a problem like yours... during the night my phone drain 10-15% of the battery in airplane mode... i've tried to install stock rom, clean install of cm11, some kernels, UV and UC... nothing works...
Last night i went to sleep with 93%, after 8 hours i had 93% but after 5-6 seconds it dropped to 81%.... no sync, airplane mode, greenify on all apps...
I've also bought a new battery... nothing to do... it can be can hardware problem?
Thanks
Is anything wrong with my battery?CM11 with ak kernel @ 1944 mhz, intellidemand, eco mode on, Wi-Fi on, GPS on, auto brightness on
VikramW8 said:
Is anything wrong with my battery?CM11 with ak kernel @ 1944 mhz, intellidemand, eco mode on, Wi-Fi on, GPS on, auto brightness on
Click to expand...
Click to collapse
First of all kill that 1.9Ghz OC for gods sake....poor phone
Mashed_Potatoes said:
First of all kill that 1.9Ghz OC for gods sake....poor phone
Click to expand...
Click to collapse
Well the graph has started from when the phone was at 1.2Ghz... The battery life just doesn't get worse.. Its the same with 1.2 and 1.9.. Just some minor differences.. There is less heat and low performance on 1.2 and on 1.9 the phone heats up quite a bit but the performance also increases considerable.. But it doesn't seem to affect battery life..
Vikram: Firstly, its bad manners to hijack someone else's thread. You should start your own if you have a question.
It's hard to say if it affects a battery life, because your graph is over the span of two days. One single charge and discharge cycle is sufficient to demonstrate any issues. In any case, it may be unrelated to your overclocked processor, I would install the wake lock detector app and start from there.
My Son's Nexus 10 had served its purpose. But Started to die at Random percent, Mostly above 50%.. So Got a new Tablet for him. But Did not want to throw away this Gem of a Tablet.
After weeks of Trial and Error finally found a solution Thanks to input from a Redditor.
Issue/Problem: Dies at Random % showing battery %0 and Shutdown. But In Recovery with Full Brightness it does not Die for hours.. (as later found out.. Recovery does not need much CPU power)
So What did I try:
1. Changed Rom's (All the way from Base Google Images to Oreo) >> Did NOT fix the Problem
2. Clearing battery stats.. etc. ( incl completely discharge and Charge and all those cycles usually we do to calibrate the battery) >> Did NOT Fix the Problem
2. Ordered a New Battery - (Samsung Model From Ebay - I guess it was used or who knows ) >> Did NOT fix the Problem
3. Changed Multiple chargers (Wall Adapters/ Cable from multiple brands which i have at home.. LG, Samsung etc etc) >> Did NOT Fix the Problem
Solution/ What Fixed:
Thanks to redditor.. Who mentioned about CPU power consumption.. And Old Mother board might not be providing enough Power to CPU. (As this tablet is Old.. It was just an Hobby to make it work and Did not want to spend more money on MotherBoard)
By this time I was on Marshmallow Linage OS Rom.. (As Everything works), Gave Root access to one of the CPU app's and Did this..(See Below) Enabled on Boot to keep the same settings.
Setting the CPU max to 1200MHz and Min to 200 it WORKED! I tried every damn thing before. For some reason... this idea did not strike my brain. So its the Power consumption from CPU.
EDIT 1: after some more testing You can go upto MAX 1600MHz (Your mileage may vary)
Finally Battery drained till zero without shutting down.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO.. If you have the same issue as mine. (I Know many had this issue like mine.. but none had solution) Hope this helps.
streetsmart999 said:
My Son's Nexus 10 had served its purpose. But Started to die at Random percent, Mostly above 50%.. So Got a new Tablet for him. But Did not want to throw away this Gem of a Tablet.
After weeks of Trial and Error finally found a solution Thanks to input from a Redditor.
Issue/Problem: Dies at Random % showing battery %0 and Shutdown. But In Recovery with Full Brightness it does not Die for hours.. (as later found out.. Recovery does not need much CPU power)
So What did I try:
1. Changed Rom's (All the way from Base Google Images to Oreo) >> Did NOT fix the Problem
2. Clearing battery stats.. etc. ( incl completely discharge and Charge and all those cycles usually we do to calibrate the battery) >> Did NOT Fix the Problem
2. Ordered a New Battery - (Samsung Model From Ebay - I guess it was used or who knows ) >> Did NOT fix the Problem
3. Changed Multiple chargers (Wall Adapters/ Cable from multiple brands which i have at home.. LG, Samsung etc etc) >> Did NOT Fix the Problem
Solution/ What Fixed:
Thanks to redditor.. Who mentioned about CPU power consumption.. And Old Mother board might not be providing enough Power to CPU. (As this tablet is Old.. It was just an Hobby to make it work and Did not want to spend more money on MotherBoard)
By this time I was on Marshmallow Linage OS Rom.. (As Everything works), Gave Root access to one of the CPU app's and Did this..(See Below) Enabled on Boot to keep the same settings.
Setting the CPU max to 1200MHz and Min to 200 it WORKED! I tried every damn thing before. For some reason... this idea did not strike my brain. So its the Power consumption from CPU.
Finally Battery drained till zero without shutting down.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO.. If you have the same issue as mine. (I Know many had this issue like mine.. but none had solution) Hope this helps.
Click to expand...
Click to collapse
Hi!
I have the same problem for a while. Could you tell me which CPU app did you use?
I thank you very much for your help.
Marco
Kukl said:
Hi!
I have the same problem for a while. Could you tell me which CPU app did you use?
I thank you very much for your help.
Marco
Click to expand...
Click to collapse
I used below app (But u can use any CPU app).. But other than those above setting(s).. I DID NOT change anything else. But u need ROOT to make that change.
Good Luck. hopefully it helps you too.
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
streetsmart999 said:
I used below app (But u can use any CPU app).. But other than those above setting(s).. I DID NOT change anything else. But u need ROOT to make that change.
Good Luck. hopefully it helps you too.
https://play.google.com/store/apps/details?id=com.grarak.kerneladiutor
Click to expand...
Click to collapse
I try it immediately, I hope it works!
Thank you very much
Kukl said:
I try it immediately, I hope it works!
Thank you very much
Click to expand...
Click to collapse
Hey You can go MAX upto 1600.. If that doesn't work for u.. Keep reducing a lil by little.
streetsmart999 said:
Hey You can go MAX upto 1600.. If that doesn't work for u.. Keep reducing a lil by little.
Click to expand...
Click to collapse
Unfortunately at the moment I don't solved the problem, even if I set the cpu min to 200 and max to 1200.
I've installed a new ROM, deleted the cache and still the problem persists. I will do other tests trying to recalibrate the battery.
Kukl said:
Unfortunately at the moment I don't solved the problem, even if I set the cpu min to 200 and max to 1200.
I've installed a new ROM, deleted the cache and still the problem persists. I will do other tests trying to recalibrate the battery.
Click to expand...
Click to collapse
Humm... Anyway @1600 mine died at 30% .. So made it 1500 and past below 18% and Still running. So I guess 1500 is max I can go
Also Before coming this conclusion: I did the fowling
Charge 100%
Delete Batterystats.bin
Run this command from adb "adb shell dumpsys batterystats --reset"
And then Changed the CPU max (Please NOTE , Select "On Boot" to keep the same parameters). Once u change the CPU settings .. Reboot and see .. if its keeping the same settings.
Many thanks. I tried all of the the things you tried and setting the cpu max frequency is the only thing that worked.
I could get away with seeing it to 1600.
Deleting batterystats.bin does nothing https://www.xda-developers.com/goog...-battery-stats-does-not-improve-battery-life/
Now with a new battery, PureNexus Rom and your amazing fix my Nexus 10 is a thing of beauty again.
LET ME KNOW IF THIS FIXED YOUR TABLET TOO..
Click to expand...
Click to collapse
Streetmart you absolute legend. I'd never thought I'd see the day my Nexus 10 would drain down to zero again. I tried 1600, then 1500, to no avail; then I said screw it I'll just go down to 1200 (with little hope of it working).
It feels so weird to actually have an internet “solution” work. I'm super happy. I didn't want to buy another tablet. I love this one and it worka perfect for what I use it for.
Thank you! :good::highfive:
OMG! thank you for this thread! i was just posting to look for a replacement for my 10... i hope this fixes it BTW.. what's the normal max cpu speed? I REALLY don't want to replace it as the new dropbox 3 device thing really screws me..
Icetech3 said:
OMG! thank you for this thread! i was just posting to look for a replacement for my 10... i hope this fixes it BTW.. what's the normal max cpu speed? I REALLY don't want to replace it as the new dropbox 3 device thing really screws me..
Click to expand...
Click to collapse
I think the normal is 1700MHz. It's what the program showed before I changed it. All the best! Keep us updated.
Hez0 said:
I think the normal is 1700MHz. It's what the program showed before I changed it. All the best! Keep us updated.
Click to expand...
Click to collapse
What a difference... i installed that a few days ago, and i haven't used my N10 much but on standby it's still at 99% usually it would be WAY lower.. i think that program did more than just lower the max cpu a little.. don't care though. the N10 lives on!!
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
DragonFire1024 said:
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
Click to expand...
Click to collapse
I'm currently running at 1600 with this guy modified kernel and wow, besides no more suddenly shutdowns it runs very smoothly, it reminds me the pre-marshmallow age of this tablet.
DragonFire1024 said:
If you still have this issue, I have been updating the kernel and also found some of the power control settings needed tweaked. Disabling "opportunistic sleep" "logging time spent in suspend" and enabling "advanced power controls" seems to do the trick. had an issue where the device would shut off if battery level reached 20%. Haven't had it happen again yet.
Click to expand...
Click to collapse
Where are you finding these control settings to change?
I have replace the battery of my N10 because of low capacity.
Now it charge from 0% to 52% then it goes to 100%. On discharge it goes from 100% to 46% then shutdown and battery shows 0%. Percentage is the same in TWRP.
Since replacement of battery it have aroud 10 charge/discharge cycles without any changes.
Any solution for that?
Der_Graf said:
I have replace the battery of my N10 because of low capacity.
Now it charge from 0% to 52% then it goes to 100%. On discharge it goes from 100% to 46% then shutdown and battery shows 0%. Percentage is the same in TWRP.
Since replacement of battery it have aroud 10 charge/discharge cycles without any changes.
Any solution for that?
Click to expand...
Click to collapse
I have to agree on, that the N10 chipset/cpu/powersupply has degraded somewhat & as the battery voltage gets lower during discharge, it can not supply stable power any longer :crying:
If i reduce the CPU speed from 1700MHz to 1200MHz I get to go down to 20% instead the N10 shutting down abruptly at just 30%
I do have a spare battery in the fridge for later on. Once I open up the N10, I'll see if there is a capacitor or two, that could replaced in the power supply area to possibly fix the issue.
Note:
1. On second full charge since lowering the CPU to 1200MHz the battery got down to 14% & I have decided to charge it instead of letting it die at some point at a lower percentage
2. I should have mentioned earlier, that I still use the original N10 battery & plan to replace the original battery with a new aftermarket battery later on if I need to.
3. I use the N10 in an air-conditioned room for no longer, than half an hour at a time only browsing & reading articles with a short 10min video from YouTube.
4. Before lowering the CPU clock from 1700MHz to 1200MHz, the tablet consistently has shut down abruptly, at 27-30% battery level to my dismay.
5. Tried complete battery drain / cache reset to 0% in Recovery mode & then fully charging it while shut down 3 times without success.
6. So far lowering the CPU clock has made a difference & for prof now I am evaluating the N10 battery capacity with AccuBattery.
7. I charge my devices at around 20-25% or higher up to 80% to prolong battery life using apk's to stop charging or alert me.
I have switched to the UNOFFICIAL Resurrection Remix for Nexus 10 (ResurrectionRemix-M-v5.7.4-20161208-manta) MM ROM after rooting my N10 (Danke schön Corinna ) & had to update the baked in Kernel Adiutor.
Installing from APKMirror the "Kernel Adiutor (ROOT) 0.9.73 beta (Android 4.0.3+)" has allowed me to lower CPU MAX Frequency and have it stick after BOOT!
com.grarak.kerneladiutor_0.9.73_beta-241_minAPI15(nodpi)_apkmirror.com
Ottoman Mint said:
I have to agree on, that the N10 chipset/cpu/powersupply has degraded somewhat & as the battery voltage gets lower during discharge, it can not supply stable power any longer :crying:
Click to expand...
Click to collapse
I don´t think so. The capacity of new battery looks really good. I use the N10 as wall-mounted control tablet for my home. With activated DT2W, full brightness, showing cams on motion, controlling home and audio over the day, my new battery runs about 28 hours before it stops. With old battery it was around 15-18 hours from full to off. My workaround: Reading battery with tasker and starts charging at 50%
I think the china batterys have different voltages than samsung batterys and N10 can´t work with this.
Der_Graf said:
I don´t think so. The capacity of new battery looks really good. I use the N10 as wall-mounted control tablet for my home. With activated DT2W, full brightness, showing cams on motion, controlling home and audio over the day, my new battery runs about 28 hours before it stops. With old battery it was around 15-18 hours from full to off. My workaround: Reading battery with tasker and starts charging at 50%
I think the china batterys have different voltages than samsung batterys and N10 can´t work with this.
Click to expand...
Click to collapse
Hey,
That sounds very interesting. I may find out about that, when I replace the original N10 battery to my replacement battery from China.
I forgot to mention in my post earlier, that I am still using the original N10 battery. The original N10 battery keeps crashing at 30% unless I lower the CPU clock to 1200MHz.
After the first charge at (1200MHz max CPU) I got the N10 down to 20%+ before crashing to shut down & after the second charge I got it down to 14% at the same 1200MHz without crashing to shut down & just recharged it. Mind you I was just surfing the net & watching YouTube. I am also using AccuBattery to estimate the battery capacity atm. (Oh & don't install Battery Charge Limiter, because it boot-loops the N10 after install!)
DT2W sounds awesome. Which ROM are you using on your N10 to get DT2W, if you don't mind me asking?
Ottoman Mint said:
Hey,
That sounds very interesting. I may find out about that, when I replace the original N10 battery to my replacement battery from China.
I forgot to mention in my post earlier, that I am still using the original N10 battery. The original N10 battery keeps crashing at 30% unless I lower the CPU clock to 1200MHz.
After the first charge at (1200MHz max CPU) I got the N10 down to 20%+ before crashing to shut down & after the second charge I got it down to 14% at the same 1200MHz without crashing to shut down & just recharged it. Mind you I was just surfing the net & watching YouTube. I am also using AccuBattery to estimate the battery capacity atm. (Oh & don't install Battery Charge Limiter, because it boot-loops the N10 after install!)
DT2W sounds awesome. Which ROM are you using on your N10 to get DT2W, if you don't mind me asking?
Click to expand...
Click to collapse
Sometimes it shuts down at 20% and other times it won't. I'm almost pretty sure it doesn't have anything to do with advanced power settings or any kind of internal power settings with the kernel. There are no thermal configurations on this device and they don't add any drivers for it or support for it until much later versions. Heat seems to play a role especially down here Florida when outside. So far in my experience it's most likely to shut down at 20% if it's too hot and not likely to do so if it's been idle for a bit or not plugged in.
Sent from my Samsung Nexus 10 using XDA Labs