Some Users are reporting that the Battery stays at 14% for a long time.
I had this issue too , until i waited till the Phone was down to 1% and switched off, ( this took ~6h with GPS active and Display on!!) since this time i did not notice this behaviour.
drcyber said:
Some Users are reporting that the Battery stays at 14% for a long time.
I had this issue too , until i waited till the Phone was down to 1% and switched off, ( this took ~6h with GPS active and Display on!!) since this time i did not notice this behaviour.
Click to expand...
Click to collapse
+1 This issue has been part of my Fairphone experience since the beginning - and fully draining the charge like you described doesn't seem to help: Even after 20 complete discharges, it still gets stuck at 14% for hours, making a correct estimate how much battery I actually have left impossible. These three screenshots are all one week apart (Jan 17th, Jan 22nd & Jan 30th - click to enlarge):
↑ Reboot caused this glitch.
@drcyber, thanks for making a thread for this - I didn't know whether it was enough of an issue to do so myself
Repeating my question from the main thread (for the last time, don't worry): I am well aware that Joe & his crew might not be able to do/tell us anything about this, but maybe someone can shed a bit of light on this issue for me: Is this purely a hardware glitch of the battery itself? Do some sensors / parts of the measuring software need to calibrate themselves first? Is everyone experiencing this or just the few that have reported it here?
now its back, 14% for 15 hours now..
Try to monitor the kernel's power level sensors, and see if they change. There are 3 possible issues: the hardware isn't measuring correctly, the kernel isn't outputting the correct values, or the system itself is bugged, and doesn't handle the kernel's values correctly.
That's all I can say for now, as I neither have the device myself' nor the sources, as I am being in the hospital right now, but maybe I can give some theoretical help
Sent from my Nexus 7 using xda app-developers app
Same problem here
laufersteppenwolf said:
Try to monitor the kernel's power level sensors, and see if they change. There are 3 possible issues: the hardware isn't measuring correctly, the kernel isn't outputting the correct values, or the system itself is bugged, and doesn't handle the kernel's values correctly.
That's all I can say for now, as I neither have the device myself' nor the sources, as I am being in the hospital right now, but maybe I can give some theoretical help
Click to expand...
Click to collapse
Sparparts+ tells me that the mVolts are decreasing normally, so i guess the Kernel works correctly and it is just a interpreting issue.
Gute Besserung!
Gesendet von meinem FP1 mit Tapatalk
Maybe it's related. I looked at the power config XML in the framework res. And that was complete garbage. See the file in the other thread.
Chris
Sent from my FP1 using xda app-developers app
See
http://forum.xda-developers.com/showpost.php?p=49598488&postcount=337
Sent from my FP1 using xda app-developers app
chrmhoffmann said:
Maybe it's related. I looked at the power config XML in the framework res. And that was complete garbage. See the file in the other thread.
Chris
Sent from my FP1 using xda app-developers app
Click to expand...
Click to collapse
You're right, this file actually really is important
But the good thing is, it's relatively easy to fix I'm sure Fairphone should be able to bring up a fix quite soon, as they should have all values ready, and just need to insert them correctly
The other thing is, when loading the phone, it stucks for some time at 99%.
As far as I experienced it, it only comes, when you unload your phone to less than 14%
If you stop loading at less than 99% (aften unloading below 14%) you do not have the Battery keeping for hours at 14%.
Can anybody confirm this behaviour?
Edit:
I did not have the GPS active, regardless what the energy manager tells
haiag said:
The other thing is, when loading the phone, it stucks for some time at 99%.
As far as I experienced it, it only comes, when you unload your phone to less than 14%
If you stop loading at less than 99% (aften unloading below 14%) you do not have the Battery keeping for hours at 14%.
Can anybody confirm this behaviour?
Click to expand...
Click to collapse
yes after completly discahrge the 14%-Error seems to be gone, but i dont know for how long, but after the Update to 1.1 i was back again.
drcyber said:
yes after completly discahrge the 14%-Error seems to be gone, but i dont know for how long, but after the Update to 1.1 i was back again.
Click to expand...
Click to collapse
Did you had the 99%-Error when loading?
Or was it directly to 100% without the 14%-Error?
uhm, I may be wrong but doesn't the phone charge/uncharge/charge/un.. when it tends to reach 100%? So it stays at 99% the whole time
arghwhymustiregister said:
uhm, I may be wrong but doesn't the phone charge/uncharge/charge/un.. when it tends to reach 100%? So it stays at 99% the whole time
Click to expand...
Click to collapse
I think usually Android phones load to 100%, then drop to 90% and load back to 100% again. At least the Nexus S did so, IIRC.
No, if you wait long enough, it gets to 100%.
But the green LED comes earlier than 100%
Sent from my FP1 using xda app-developers app
But this 99% thing i never saw as a bug, because your Phone never tells you the full truth about the Battery, 100% is never really 100% , and never 0% because the battery would get damadegt ift its really empty or completly full all the time.
Here is a better explenation in German:
http://www.giga.de/downloads/firmwa...e-von-smartphones-lugt-und-warum-das-gut-ist/
and English:
http://forum.xda-developers.com/showthread.php?t=871051
But this 99%thing just happens, when you unload your phone to less than 14%. So IMHO it's correlated somehow.
I think the maximal capacity isn't right...
Sent from my FP1 using xda app-developers app
haiag said:
The other thing is, when loading the phone, it stucks for some time at 99%.
As far as I experienced it, it only comes, when you unload your phone to less than 14%
Click to expand...
Click to collapse
Can confirm, battery only gets stuck at 99% if discharged below 14% (click to enlarge):
haiag said:
If you stop loading at less than 99% (aften unloading below 14%) you do not have the Battery keeping for hours at 14%.
Click to expand...
Click to collapse
Can confirm, 99% is enough of a charge to make the battery information get stuck (click to enlarge):
drcyber said:
Here is a better explenation in German:
http://www.giga.de/downloads/firmwa...e-von-smartphones-lugt-und-warum-das-gut-ist/
Click to expand...
Click to collapse
Sehr informativ, vielen Dank!
All in all, I think there isn't much we can do about this without a properly set power-profile.xml in framework-res.apk, like @chrmhoffmann and @laufersteppenwolf said. Since I have not the faintest clue on how to correct the xml, I can only wait for Joe & the Fairphone team to answer this in the next round of questions - after they've adressed this week's questions, of course
simsalonaut said:
Nope, mine still gets stuck at 14%, no matter how much I had charged the battery before unplugging. This is after a discharge from less than 99% (click to enlarge):
Click to expand...
Click to collapse
Did you unload the battery before below 14% ? Than charge to less than 99%, afterwards the 14% thing shouldn't appear.
So 13% -> max 98% -> No 14% Stuck...
Related
jeffreii said:
UPDATE/CONFIRMED:
The plummet is back.
After 10 days of plummet-free use with LTE disabled, it has returned after less than 48 hours uptime following my re-enabling of LTE.
For me, I am quite convinced that some LTE bug - perhaps with switching back and forth to HSPA+ - is causing the plummet. Unless some very knowledgeable devs join this discussion and help to find the root cause, I only see two options to avoid this problem:
1) Disable LTE and live with HSPA+ speeds
2) Wait for an OTA update with a fix, assuming Samsung/AT&T know about it
Personally I am sick and tired of wasting my time diagnosing this. I have lost time and enjoyment of my device trying to keep a stable testing environment. I now know the general cause and solution and am satisfied with that.
Thanks to anyone and everyone who helped.
Again, here is the link to my method for disabling LTE:
http://forum.xda-developers.com/showthread.php?t=1826409
It's unfortunate that using HSPA+ only also disables 2G, but that's not really a problem for me in Miami.
Click to expand...
Click to collapse
Anyone who can help diagnose the cause of this would be my hero. Please read carefully the evidence I already have.
Scenario:
Battery life is great for awhile and then suddenly it will start plummeting for no good reason. It will continue to do so, even if the screen is off and the phone is unused with all tasks closed. It will not stop dropping fast unless I reboot it. Then battery life returns to normal/excellent..a day or so later it starts dropping fast again.
Things I've tried:
-Factory reset - reinstall only most common apps
-Exchanged the device at AT&T - same result
-Monitored with GSAM (Badass) Battery Monitor and Better Battery Stats. No culprit found.
Important notes:
-As per attached screenshot*, I have tested ways to stop the drain without a reboot. Turning off wifi does nothing. Turning off mobile data does nothing. Turning off the radio (airplane mode) is the only way to stop it - but once I turn airplane mode off, it continues to drop quickly. Only a reboot is a working temporary fix.
-The phone itself is reporting the "cell standby" as the major culprit. I am not sure if this is inflated due to the known bug in reporting that data.
-There is something quirky with the "mobile network signal" bar - I am in Miami where signal is strong almost everywhere. The steep decline occurs even at my apartment where I always have 4 or 5 bars of LTE signal. I am almost never in any area where there is no signal, despite what the line indicates.
Attached screenshots:
1 & 2) good battery life followed by a sudden and steep decline
3) the subsequent "test" listed in note # 1 above with the resulting plateau achieved by turning on airplane mode with the drop continuing when airplane mode was disabled
4 & 5) I then charged the device to full overnight and unplugged it in the morning. I let it sit unused for about 2 hours and the battery dropped 25%.
6 & 7) these screenshots are from normal excellent battery life scenario where the "plummeting" battery did not occur
Thank you so much for any help
Since turning on airplane mode stops it my guess is that its a bad radio. Only option would be to exchange it and tell them this is your second defective unit.
DudeWatsThat said:
Since turning on airplane mode stops it my guess is that its a bad radio. Only option would be to exchange it and tell them this is your second defective unit.
Click to expand...
Click to collapse
What are the odds of me having two units in a row with the exact same problem, which does not appear to be widespread?
The bad news is that I am past my 30 day exchange window.
jeffreii said:
What are the odds of me having two units in a row with the exact same problem, which does not appear to be widespread?
The bad news is that I am past my 30 day exchange window.
Click to expand...
Click to collapse
If you got that unit during your 30 days you should have 30 days for that unit and if you don't then go through manufactures warranty. Unless your willing to play around with roms to see if that solves it.
In terms of odds maybe your ATT store just got a bad batch either that or you have incredibly bad luck but I do know of one other person who had the same problem if I remember correctly.
Sent from my GSIII
DudeWatsThat said:
If you got that unit during your 30 days you should have 30 days for that unit and if you don't then go through manufactures warranty. Unless your willing to play around with roms to see if that solves it.
In terms of odds maybe your ATT store just got a bad batch either that or you have incredibly bad luck but I do know of one other person who had the same problem if I remember correctly.
Click to expand...
Click to collapse
My understanding of the return policy, as confirmed by the rep, is that exchanging your device does not reset the 30 days. I would have to go through the manufacturer warranty now, facilitated by AT&T. Much more hassle than just going to the store and swapping it out.
I received my first S III in the mail from AT&T Online. 30 days later I went to one of several local corporate stores and exchanged it. They were definitely not the same batch. This is probably not bad luck and I have heard from several others that they have this same problem...
My next step, after some more logs and troubleshooting, would be to factory wipe again and use the phone stock with no apps for up to a week to see if I can reproduce it. Sounds terrible but I'm willing to do it if it is necessary. Still hoping someone here on XDA can help me pinpoint the problem.
Thanks again for your response.
I get this battery drain maybe once a week, a friend of mine also gets it occasionally, It is very unlikely that our phones are from the same batch, because he got his 2 weeks before i got mine. It seems to be a more widespread problem than we think, and i hope samsung, or someone on XDA, can figure it out and fix it.
jeffreii said:
My understanding of the return policy, as confirmed by the rep, is that exchanging your device does not reset the 30 days. I would have to go through the manufacturer warranty now, facilitated by AT&T. Much more hassle than just going to the store and swapping it out.
I received my first S III in the mail from AT&T Online. 30 days later I went to one of several local corporate stores and exchanged it. They were definitely not the same batch. This is probably not bad luck and I have heard from several others that they have this same problem...
My next step, after some more logs and troubleshooting, would be to factory wipe again and use the phone stock with no apps for up to a week to see if I can reproduce it. Sounds terrible but I'm willing to do it if it is necessary. Still hoping someone here on XDA can help me pinpoint the problem.
Thanks again for your response.
Click to expand...
Click to collapse
Do that and remember to do a test using airplane mode if it doesn't loose battery while in airplane mode then there are two theorys then: samsung software bug that affects radio or hardware issue.
It also depends how many "several others" are, remember even 100 people are a minority compared to the millions of units sold.
Keep us updated so we can get to the root of the problem.
Sent from my GSIII
Here's another sample with a Better Battery Stats log attached as well.
I'm going to do another test tonight with airplane mode enabled + another BBS log.
jeffreii said:
Here's another sample with a Better Battery Stats log attached as well.
I'm going to do another test tonight with airplane mode enabled + another BBS log.
Click to expand...
Click to collapse
Whats your screen on time, battery stats indicated a deep idle of only 2hrs.
And damn your cell standby % is huge. When I had the cell standby bug it only rose to about 15%.
IMO that high cell standby is not normal even with the bug.
DudeWatsThat said:
Whats your screen on time, battery stats indicated a deep idle of only 2hrs.
And damn your cell standby % is huge. When I had the cell standby bug it only rose to about 15%.
IMO that high cell standby is not normal even with the bug.
Click to expand...
Click to collapse
I agree with you, I don't think it's normal even with the bug. Maybe OP should download fix or a rom with the fix if he doesn't want to use the warranty and see if it still tops the charts with the bug fixed.
jeffreii said:
Here's another sample with a Better Battery Stats log attached as well.
I'm going to do another test tonight with airplane mode enabled + another BBS log.
Click to expand...
Click to collapse
post your bbs log to the thread here : > Android Development and Hacking > Android Apps and Games > [APP] [30 Jul - V1.9.1] BetterBatteryStats adds battery history back to Android
http://forum.xda-developers.com/showthread.php?t=1179809
you will be helped there for sure.
This has happened to me on several ROMs, but it doesn't happen very often. It does seem to be radio related. The last time it happened, I checked the battery graph and the signal strength was solid green from exactly the time the battery started plummeting. Not sure if that means anything but it's another data point.
Firestar292 said:
I agree with you, I don't think it's normal even with the bug. Maybe OP should download fix or a rom with the fix if he doesn't want to use the warranty and see if it still tops the charts with the bug fixed.
Click to expand...
Click to collapse
Strange thing is the bug just reports the % wrong and applying the fix won't actually solve is drainage issues, although if he does apply it and still sees a high percentage its most probably the radio or he could apply it see normal cell % and we be back to square one.
bradld said:
post your bbs log to the thread here : > Android Development and Hacking > Android Apps and Games > [APP] [30 Jul - V1.9.1] BetterBatteryStats adds battery history back to Android
http://forum.xda-developers.com/showthread.php?t=1179809
you will be helped there for sure.
Click to expand...
Click to collapse
+1
Search for the gsiff_daemon thread. It sounds like that may be your problem. I don't have the link handy but if you don't find it I'll dig it up for you.
Sent from my GT-P3113 using xda app-developers app
jcejohnson said:
Search for the gsiff_daemon thread. It sounds like that may be your problem. I don't have the link handy but if you don't find it I'll dig it up for you.
Sent from my GT-P3113 using xda app-developers app
Click to expand...
Click to collapse
I agree that its gsiff_daemon bug. I get it on occasion when streaming music through web. Even when I close it will drain the battery quickly. Do a search for that daemon and see if that shows up in battery stats. Usually shown as android system. When you hit refresh under battery stats it usually displays the gsiff name quickly.
Sent from my SGH-I747M using xda app-developers app
blue265 said:
I agree that its gsiff_daemon bug. I get it on occasion when streaming music through web. Even when I close it will drain the battery quickly. Do a search for that daemon and see if that shows up in battery stats. Usually shown as android system. When you hit refresh under battery stats it usually displays the gsiff name quickly.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
What is gsiff_daemon? I looked in the thread but the info is scattered.
DudeWatsThat said:
Whats your screen on time, battery stats indicated a deep idle of only 2hrs.
And damn your cell standby % is huge. When I had the cell standby bug it only rose to about 15%.
IMO that high cell standby is not normal even with the bug.
Click to expand...
Click to collapse
The BBS log was only 2 hours, 38m, as you can see from the extracted data below:
Since 2 h 38 m 8 s
Deep Sleep (): 2 h 24 m 59 s (8699 s) Ratio: 91.7%
Awake (): 13 m 9 s (789 s) Ratio: 8.3%
Screen On (): 40 s (40 s) Ratio: 0.4%
Firestar292 said:
I agree with you, I don't think it's normal even with the bug. Maybe OP should download fix or a rom with the fix if he doesn't want to use the warranty and see if it still tops the charts with the bug fixed.
Click to expand...
Click to collapse
Yeah I can see about downloading the fix but that is only a display issue and wouldn't help at all with my battery.
bradld said:
post your bbs log to the thread here : > Android Development and Hacking > Android Apps and Games > [APP] [30 Jul - V1.9.1] BetterBatteryStats adds battery history back to Android
http://forum.xda-developers.com/showthread.php?t=1179809
you will be helped there for sure.
Click to expand...
Click to collapse
I have posted several times in that thread and they tried to help but couldn't find anything...the main suggestion was to try a custom kernel...I'm going to post my latest logs there now though (and in this thread).
EDIT: Here's my new post in that thread:
http://forum.xda-developers.com/showthread.php?p=29716265#post29716265
21cdb said:
This has happened to me on several ROMs, but it doesn't happen very often. It does seem to be radio related. The last time it happened, I checked the battery graph and the signal strength was solid green from exactly the time the battery started plummeting. Not sure if that means anything but it's another data point.
Click to expand...
Click to collapse
I noticed the same thing with the mobile network signal bar being solid. I still don't understand why that bar has so many gaps where it appears to show the radio off when it's not...anyways I thought there was a correlation there but have since seen plenty of "plummets" without the solid green mobile network signal bar.
jcejohnson said:
Search for the gsiff_daemon thread. It sounds like that may be your problem. I don't have the link handy but if you don't find it I'll dig it up for you.
Click to expand...
Click to collapse
gsiff_daemon is not in my BBS logs...see the new logs I'm about to post.
Ok so I've been continuing my tests from above.
I first charged a bit and then turned off wifi since wlan_rx_wake was a biggie in my BBS log. You can see the log for that period below. Battery continues to plummet as it did before.
I then turned on airplane mode and started a new BBS log. The battery stopped going down. In fact it was one of those situations where the charger mis-reported the actual charge and in nearly two hours time BBS sees the battery as having gone up 1%. That log is also attached.
Also below are screenshots of this whole process where you can see the battery plateau created by airplane mode.
Perhaps we can compare these 3 log files to determine something? I am going to post them in the BBS thread as well.
Thanks again everyone I hope we can get to the bottom of this!
jeffreii said:
Ok so I've been continuing my tests from above.
I first charged a bit and then turned off wifi since wlan_rx_wake was a biggie in my BBS log. You can see the log for that period below. Battery continues to plummet as it did before.
I then turned on airplane mode and started a new BBS log. The battery stopped going down. In fact it was one of those situations where the charger mis-reported the actual charge and in nearly two hours time BBS sees the battery as having gone up 1%. That log is also attached.
Also below are screenshots of this whole process where you can see the battery plateau created by airplane mode.
Perhaps we can compare these 3 log files to determine something? I am going to post them in the BBS thread as well.
Thanks again everyone I hope we can get to the bottom of this!
Click to expand...
Click to collapse
I couldn't find anything between all 3 that is consistent and have enough % of use to screw up your battery.
I'm curious, what is your theory on what might be the cause?
DudeWatsThat said:
I couldn't find anything between all 3 that is consistent and have enough % of use to screw up your battery.
I'm curious, what is your theory on what might be the cause?
Click to expand...
Click to collapse
Thanks again for looking. Honestly I am assuming it's a bug deep in the software or something...either that or one of my apps.
First I thought it was an app. Then I thought it was hardware. Now I am just trying to re-evaluate and look at all of the evidence.
Part of me wants to just reboot every night and forget about it...
Hi,
I have been having a problem of battery.
1. Battery dies from being 100% overnight.
2. Phone randomly shuts itself having more than 40% battery but shows 0 battery when it restarts.
3. Phone restarts quite frequently when taking a picture. (once a week)
Please let me know what should I do to solve the problem. Thanks in advance.
Sent from my HTC One X using xda app-developers app
Could you install BetterBatteryStats from XDA? It's free for XDA members Install it, charge your phone back up, and let this issue happen again. Take a screenshot of Kernel Wakelock and Partial Wakelocks, as well as Process. Would get a much better view of what's eating your battery for breakfast.
Get Better Battery Stats installed.
jph7170 said:
Hi,
I have been having a problem of battery.
1. Battery dies from being 100% overnight.
2. Phone randomly shuts itself having more than 40% battery but shows 0 battery when it restarts.
3. Phone restarts quite frequently when taking a picture. (once a week)
Please let me know what should I do to solve the problem. Thanks in advance.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I've got the same drain problem as your number 1, but not the other 2 issues. The funny thing is it only started a week or so ago, before that it was fine. I've been running the Viper rom, and Faux kernel without a hitch for over a month up until now.
I used to get a day out of the battery, and 2.5-3 hour screen on which was fine IMO, but not anymore.
I'm wondering if a recent app update has caused the issue, just speculating though, also it seems to be that the drain is happening when I'm not using the phone, when I do use the handset for whatever it uses the battery as normal.
Not trying to hijack your thread, just thought I'd give my two pennies worth as I'm having a similar problem.
DrumJ86 said:
I've got the same drain problem as your number 1, but not the other 2 issues. The funny thing is it only started a week or so ago, before that it was fine. I've been running the Viper rom, and Faux kernel without a hitch for over a month up until now.
I used to get a day out of the battery, and 2.5-3 hour screen on which was fine IMO, but not anymore.
I'm wondering if a recent app update has caused the issue, just speculating though, also it seems to be that the drain is happening when I'm not using the phone, when I do use the handset for whatever it uses the battery as normal.
Not trying to hijack your thread, just thought I'd give my two pennies worth as I'm having a similar problem.
Click to expand...
Click to collapse
I think you may be right because I have had the last 2 problems since a while and gave in HTC to repair the phone but it still hasnt been solved and I have got the first problem since the last week itself.
Did you manage to install Better Battery Stats? Leave your screenshots here when it happens again and we'll be able to help you much easier
I had an Arc before, so i thought maybe this will help:
"ALWAYS and I Mean ALWAYS reboot the phone RIGHT AFTER you have disconnected it from the computer or charger to avoid the f*king Android OS issue"
Click to expand...
Click to collapse
by jimbo77 http://forum.xda-developers.com/showthread.php?t=1597771, turn off fastboot when restarting.
You have enough network in your area. I had this issue and change the Network selection to manual which took care of the issue.
ShyamSasi said:
You have enough network in your area. I had this issue and change the Network selection to manual which took care of the issue.
Click to expand...
Click to collapse
I have full network in my area so that shouldnt be the problem.
The problem didnt occur last night...i will post the better battery stats results if the problem arises again!
I'd install other ROM/KERNEL...
Hi
jph7170 said:
Hi,
I have been having a problem of battery.
1. Battery dies from being 100% overnight.
2. Phone randomly shuts itself having more than 40% battery but shows 0 battery when it restarts.
3. Phone restarts quite frequently when taking a picture. (once a week)
Please let me know what should I do to solve the problem. Thanks in advance.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
You seem to have a lot of applications running and something is keeping your phone awake. Any awake time when the screen isn't on also is an application using your phone.
Go to the play store and check the permissions of your downloaded apps, any app that has the permission to keep your device awake is a candidate for your problem. Uninstall them all and your problem should be gone, re-install one by one and see when it returns.
Regards
Phil
The problem occurred again. I have attached a image of the battery stats.
Thanks in advance.
Phil[/QUOTE]
ArmedandDangerous said:
Could you install BetterBatteryStats from XDA? It's free for XDA members Install it, charge your phone back up, and let this issue happen again. Take a screenshot of Kernel Wakelock and Partial Wakelocks, as well as Process. Would get a much better view of what's eating your battery for breakfast.
Click to expand...
Click to collapse
Rusty! said:
Get Better Battery Stats installed.
Click to expand...
Click to collapse
ArmedandDangerous said:
Did you manage to install Better Battery Stats? Leave your screenshots here when it happens again and we'll be able to help you much easier
Click to expand...
Click to collapse
Need a shot of the 'partial wakelocks' category.
Also, don't stick them altogether into one pic, the board shrinks it massively. Just upload them individually
Rusty! said:
Need a shot of the 'partial wakelocks' category.
Also, don't stick them altogether into one pic, the board shrinks it massively. Just upload them individually
Click to expand...
Click to collapse
Here is the individual files
Looks like it's the radio causing the majority of your drain. How is the signal in your location? I see you've switched from EDGE to 3G during the screenshots... if the 3G signal isn't great then it will cause battery drain searching. It might be worth forcing your phone to either 2G or 3G only and seeing what happens.
Rusty! said:
Looks like it's the radio causing the majority of your drain. How is the signal in your location? I see you've switched from EDGE to 3G during the screenshots... if the 3G signal isn't great then it will cause battery drain searching. It might be worth forcing your phone to either 2G or 3G only and seeing what happens.
Click to expand...
Click to collapse
Actually I just switched to 3g in the last couple of days. I only had 2G previously and the problem still occurred. Its funny that it happens only at night.
I think its the time for a fresh start. Format your phone and start all over.
So, how much will it takes you? Less than 3 hours? I'd say go for it.
At lest it would give you less headache and hopefully more battery.
Good Luck
I've had this problem before too, with baseband and alarm wakelocks.
Look here
http://forum.xda-developers.com/showpost.php?p=23893234&postcount=2
Then I think I just googled the offending process and found a solution there
After being frustrated for a couple of weeks and wanting to return my s3 due to overnight cell standby batty drain of around 40-50% (from full charge with no use overnight, I finally called Samsung tech support and they told me to power down, take out the battery and reinsert, and use the original charger ONLY (i was using a old clamshell phone's charger that I found lying around rather than the one that came with the phone. I freakin can't believe it but it solved the issue for me!!! I only lost about 4 percent overnight. I was soooo pissed before, but now I love my s3 again )
Curious to hear if this works for others who have also been frustrated with this awesome device...
That's been a known problem since the beginning and there was a fix zip floating around, flashed it and my cell standby is only ever 1-2% max 6%
Sent from my SGH-I747M using xda premium
Well just restarting my phone works to "fix" the massive battery drain issue (presumably because cell standby is using about 60% of my battery) but it will be back in a few days. While I do sometimes use more than one battery charger,I don't think this is related to using something other than the original charger but that is something I can test. Thanks for that tip.
This is one of the 3 big problems I have with this phone (the others being random loss of service presumably due to LTE network deficiencies and the face proximity sensor acting to disable the screen whenever I try to touch the screen with my finger). Since mine is a replacement phone for another S3 with the exact same issues, I'm assuming there is no real fix for these problems (for a stock phone). Yes, I have learned to hate my phone...
thatsupnow said:
That's been a known problem since the beginning and there was a fix zip floating around, flashed it and my cell standby is only ever 1-2% max 6%
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
can i get a link please
Yeah happened to me last night had 60 percent to 0 on paranoid android
Sent from my SAMSUNG-SGH-I747 using xda premium
I found that letting the battery drain until the phone dies and then charging iy conpletely while off helped my sleep drain significantly. That and un installing apps that have numerous wakelocks such as facebook.
Sent from my SGH-I747M using xda app-developers app
Noodile said:
can i get a link please
Click to expand...
Click to collapse
here flash this
mzaidel said:
After being frustrated for a couple of weeks and wanting to return my s3 due to overnight cell standby batty drain of around 40-50% (from full charge with no use overnight, I finally called Samsung tech support and they told me to power down, take out the battery and reinsert, and use the original charger ONLY (i was using a old clamshell phone's charger that I found lying around rather than the one that came with the phone. I freakin can't believe it but it solved the issue for me!!! I only lost about 4 percent overnight. I was soooo pissed before, but now I love my s3 again )
Curious to hear if this works for others who have also been frustrated with this awesome device...
Click to expand...
Click to collapse
The Cell Standby Fix posted above me...which I use as well...does not fix a DRAIN...it fixes a false reporting of the drain. Charger has nothing to do with it. That was a fluke or a misrepresentation.
i turned off the voip services that i had running and now it discharges only about 15-20% over night
Do a search for gsiff_daemon. That is most likely the cause of your problem and while I can't say for sure, I suspect the charger advice worked coincidentally due to the problem being fixed temporarily by powering down and restarting.
Sadly, I don't know of Samsung admitting to this issue and it looks like even the jelly bean update does not fix it.
I get the cell standby misreporting, not adversely affecting life at all. I did flash the fix and the cell standby consumption is now reported much lower, but I seem to be getting a slightly higher battery drain. sitting idle I generally drop around 2% per hour due to syncing and email push. after flashing the fix I'm up to about 5% per hour. I backed up right before this install so I'll probably revert back...
any idea why this would be?
tmagritte said:
Do a search for gsiff_daemon. That is most likely the cause of your problem and while I can't say for sure, I suspect the charger advice worked coincidentally due to the problem being fixed temporarily by powering down and restarting.
Sadly, I don't know of Samsung admitting to this issue and it looks like even the jelly bean update does not fix it.
Click to expand...
Click to collapse
do you think that gsiff_daemon can just be deleted?
Sent from my SGH-I747M using xda premium
tmagritte said:
Do a search for gsiff_daemon. That is most likely the cause of your problem and while I can't say for sure, I suspect the charger advice worked coincidentally due to the problem being fixed temporarily by powering down and restarting.
Sadly, I don't know of Samsung admitting to this issue and it looks like even the jelly bean update does not fix it.
Click to expand...
Click to collapse
Russ77 said:
I get the cell standby misreporting, not adversely affecting life at all. I did flash the fix and the cell standby consumption is now reported much lower, but I seem to be getting a slightly higher battery drain. sitting idle I generally drop around 2% per hour due to syncing and email push. after flashing the fix I'm up to about 5% per hour. I backed up right before this install so I'll probably revert back...
any idea why this would be?
Click to expand...
Click to collapse
thatsupnow said:
do you think that gsiff_daemon can just be deleted?
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I highly doubt using the Cell Standby reporting fix is causing the 5% drain Russ77. It's a proven fix without reported side effects. I have looked at the code myself. It simply alters a certain math value of 34 to 3.4.....a coding typo! Once again, probably just coincidental timing. But read on....you may have this bug if you run a stock rom...
Here is a full test report on the gsiff_daemon that I performed yesterday with details on how to reproduce it, and how to work around it. Hopefully some smart cookie will look into it and fix the code from the inside!
thatsupnow said:
do you think that gsiff_daemon can just be deleted?
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Check out the thread linked to by themadproducer (I post up) for more details. But basically, yes, if you have root you can rename the file. I just did this a couple of days ago. I haven't noticed any issues. Maybe GPS lock takes a few seconds longer, but it's hard to say if that's true or just a coincidence.
It does seem the gsiff_daemon issue is triggered by a hot reboot, which sometimes happens spontaneously. I haven't had one since I rename the file, but I don't know if renaming that also affects the spontaneous hot reboots, which are annoying in themselves. But at least it won't cause the phone to eat through battery and turn itself into a mini hotplate...
Cell standby is the one which is concerned with network connections.
The solution that would work can be changing the SIM card. Get a new SIM from your operator and throw away the old one.
thatsupnow said:
here flash this
Click to expand...
Click to collapse
How to install this zip file, please help
Thanks
tmagritte said:
Check out the thread linked to by themadproducer (I post up) for more details. But basically, yes, if you have root you can rename the file. I just did this a couple of days ago. I haven't noticed any issues. Maybe GPS lock takes a few seconds longer, but it's hard to say if that's true or just a coincidence.
It does seem the gsiff_daemon issue is triggered by a hot reboot, which sometimes happens spontaneously. I haven't had one since I rename the file, but I don't know if renaming that also affects the spontaneous hot reboots, which are annoying in themselves. But at least it won't cause the phone to eat through battery and turn itself into a mini hotplate...
Click to expand...
Click to collapse
Where is this gsiff_daemom file found? I have a rooted s3 and would like to rename it.
flash
how can i flash that zip file in an stock recovery
thatsupnow said:
here flash this
Click to expand...
Click to collapse
Can I use this for my Samsung Galaxy ace s5830i too?
haha
Hi Guys,
I have spent days researching this, and have read dozens of forum posts, but nothing has worked. Here's the problem- I bought a used GNEX off of Craigslist. The phone looks great and seems to work well. But, it won't show a charge beyond about 70%.
I thought the battery might be the issue, so i bought an a new OEM extended battery, but the new battery didn't make any difference. It still won't show a charge above 70% no matter how long I leave it on the charger (with the phone turned on or off). I have done probably 20 discharge/recharge cycles, but nothing changes.
Next, I bought an external charger. When I fully charge the battery in the external charger and pop it in the phone, it still shows around 70%. So, it is definitely an issue with the phone (not the batteries).
I've also tried four different ROMs, as well as all the black-magic "battery calibration" tricks found in the forums, but nothing helps.
I am totally stumped! Is there anyway I can fix this?
Thanks!
Slim
Please HELP! More info.
Hi guys,
Just an update. Yesterday I tried three different kernels, just in case that might make a difference. No luck. The kernels didn't make a difference.
Any advice on how I can make this phone handle battery levels correctly? It's been on the charger all night and only shows 66% charge.
-Slim
Same here !
reza2224 said:
Same here !
Click to expand...
Click to collapse
Hey, Reza. How long has your GNEX been having this problem?
You might try returning to stock to see if eliminating custom ROMs helps.
imthepits said:
You might try returning to stock to see if eliminating custom ROMs helps.
Click to expand...
Click to collapse
Thanks. I actually already tried that. Took it back to completely stock, unrooted. No dice. The issue was still there. I am stumped!. I hope it's not a hardware issue.
SlimKermie said:
Hey, Reza. How long has your GNEX been having this problem?
Click to expand...
Click to collapse
I have this phone about six months,but couple days age after I tried to install cm10.1 carch up with this problem.
Changing custom rom,returning to stock,callibrating , every thing I tried didn't work.
Firs it stops about 98,then after a recharge it stops @ 95 ,then 90 and now it does'nt exceed 87.
Sent from my Galaxy Nexus using xda premium
Same problem
reza2224 said:
I have this phone about six months,but couple days age after I tried to install cm10.1 carch up with this problem.
Changing custom rom,returning to stock,callibrating , every thing I tried didn't work.
Firs it stops about 98,then after a recharge it stops @ 95 ,then 90 and now it does'nt exceed 87.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Same issue here, i tried with another battery that showed 95% in other Gnex and in my gnex showed 60%.....
I'm getting crazy!
Definitely a hardware issue.
Toro | Carbon | AK SKL
try an app named "BatteryCalibration" by marosige. When opened it shows the in circuit battery voltage. 3600-3700mV is to be expected from a well charged and in good shape battery. We seam to be having the same issues with mine having progressed to showing 0%. I have a recent thread here as well. I have read that the recovery battery stat wipe is just for the application level, but I think there must be a file or setting somewhere that maps mV to %'s and that this is what needs wiped/reset.
Anyone overhere still having issues?
I updated my thread on a similar if not the same problem, and am looking for some volunteers to help gather a little data. I would like for one or more persons to install SL4A and python, run a script and report findings. If you are willing please post a reply in my thread.
Thank you
Hi, i bought one moto z play, almost 2 months ago, and the battery was excellent, you can see on airplane mode, idle, not using it, the phone lates more than 17 days, and had 23% of juice left, after that, i boight another one, both are used, but this one, only last 2 days on the same conditions, airplane mode, even safe mode, not using at all, just 2 days, drains like 2% per hour without even touching it at all, what can i do?
What does it matter what happens when you never use it? And why buy a second phone if you already have one that lasts great?
Just sell the second and start using it like normal people. Nobody can tell you why that difference is and it doesn't matter. They have to last under normal conditions, but what you are doing is pretty much waste of battery. Letting it lie around in airplane mode for days is simply stupid. Then you could just turn it off
Artim_96 said:
What does it matter what happens when you never use it? And why buy a second phone if you already have one that lasts great?
Just sell the second and start using it like normal people. Nobody can tell you why that difference is and it doesn't matter. They have to last under normal conditions, but what you are doing is pretty much waste of battery. Letting it lie around in airplane mode for days is simply stupid. Then you could just turn it off
Click to expand...
Click to collapse
Seems like a reasonable test of baseline battery drain to me. I get less than 2% drain per hour with all my background stuff on with my MZP. My old S6 (notorious for bad battery) gets like 3% per day in airplane mode with no screen on time.
Just because his use case isn't your use case, doesn't mean what he's doing is stupid.
OP, I'd be inclined to think you have a hardware issue - you've eliminated all the normal software side stuff that typically is responsible for battery drain.
dandrumheller said:
Seems like a reasonable test of baseline battery drain to me. I get less than 2% drain per hour with all my background stuff on with my MZP. My old S6 (notorious for bad battery) gets like 3% per day in airplane mode with no screen on time.
Just because his use case isn't your use case, doesn't mean what he's doing is stupid.
OP, I'd be inclined to think you have a hardware issue - you've eliminated all the normal software side stuff that typically is responsible for battery drain.
Click to expand...
Click to collapse
Exactly, it was just a test, obviusly under normal conditions the drain Is Worst, only 3 SoT and 9 hours of battery, if you compare the two phones, one drains 2% and the other 0.1% por hour, that it's not normal.
If is not hw issue, something is draining battery in background. Have you tried factory reset? Compare settings on both phones, wifi/bt scan, SIM is inside on both, sd card?
Anyway, try to make both phones exactly the same from hw and sw perspective. If you haven't already.
Sent from my XT1635-02 using Tapatalk
Maybe put a CPU monitor app on both phones, let them both run in the same condition for the same time period, and see if the histories match? Not really sure how else to look, since you said safe mode didn't fix it.
Zeljko1234 said:
If is not hw issue, something is draining battery in background. Have you tried factory reset? Compare settings on both phones, wifi/bt scan, SIM is inside on both, sd card?
Anyway, try to make both phones exactly the same from hw and sw perspective. If you haven't already.
Sent from my XT1635-02 using Tapatalk
Click to expand...
Click to collapse
the one with the problem has the december patch update, the good one, the november patch, thats the only difference on both. already tried factory reset, wipe cache, safe mode, even on safe mode, the 2% per hour draining persist.
dandrumheller said:
Maybe put a CPU monitor app on both phones, let them both run in the same condition for the same time period, and see if the histories match? Not really sure how else to look, since you said safe mode didn't fix it.
Click to expand...
Click to collapse
gonna FDR both, charge them to 100% and let them dry for a couple of hours with the cpu monitor.
kmry said:
the one with the problem has the december patch update, the good one, the november patch, thats the only difference on both. already tried factory reset, wipe cache, safe mode, even on safe mode, the 2% per hour draining persist.
Click to expand...
Click to collapse
You can try to upgrade good one to December patch to get the same batter life result
If there's no other difference, then looks like that is hw problem. But I'm still suspecting that you are missing something.
Zeljko1234 said:
You can try to upgrade good one to December patch to get the same batter life result
If there's no other difference, then looks like that is hw problem. But I'm still suspecting that you are missing something.
Click to expand...
Click to collapse
good joke, but im not gonna take that risk; cant think what i would be missing; i think ive tried everything except for a downgrade, but i read somewhere it cannot be done, the phone is on 7.1.1.
kmry said:
good joke, but im not gonna take that risk; cant think what i would be missing; i think ive tried everything except for a downgrade, but i read somewhere it cannot be done, the phone is on 7.1.1.
Click to expand...
Click to collapse
Do not downgrade. It is doable but next upgrade (OTA) and you will end up with brick.
I've already asked you, both phones are with/without SIM/sd card?
Zeljko1234 said:
Do not downgrade. It is doable but next upgrade (OTA) and you will end up with brick.
I've already asked you, both phones are with/without SIM/sd card?
Click to expand...
Click to collapse
both phones on airplane mode, without simcard, without sd card.
kmry said:
both phones on airplane mode, without simcard, without sd card.
Click to expand...
Click to collapse
Well, if both phones are the same from hw and sw perspective (except update on "bad one") then most probably cause is hw or update.
Do not try to downgrade, 8.0 is under SOAK (quite long already, but still has issues) and you may try it when is ready (don't flash leaked SOAK, please).
As said above, most likely is hw issue. Sorry for that.
camera app left running?
dandrumheller said:
Seems like a reasonable test of baseline battery drain to me. I get less than 2% drain per hour with all my background stuff on with my MZP. My old S6 (notorious for bad battery) gets like 3% per day in airplane mode with no screen on time.
Just because his use case isn't your use case, doesn't mean what he's doing is stupid.
OP, I'd be inclined to think you have a hardware issue - you've eliminated all the normal software side stuff that typically is responsible for battery drain.
Click to expand...
Click to collapse
KrisM22 said:
camera app left running?
Click to expand...
Click to collapse
All apps were closed.
kmry said:
All apps were closed.
Click to expand...
Click to collapse
Your second pic says it's running. Sorry if I misinterpret.