Related
I understand all these battery drain issues that the prime has been having but haven't actually had them, until now. I used to lose about 2-3% overnight but suddenly I am losing around 15% because it won't sleep. I go into the battery setting and it shows it been awake the whole time. Now I am sure if I looked around I may find a fix but it just seems a bit odd that it has just suddenly occurred. And its not a wifi drainage issue as I usually put it to sleep at power saving mode and wifi off. Just asking why?
Thanks,
I think it could be the Asus weather widget which I had set at 1 hour refresh rate.
if this just recently occured out the blue, likely a rougue app or something you recently installed. an app running in background or sync is likely the culprit.
Just put Skype on it but that's not signed in most of the time
every android tablet and phone i have does this occasionally, and those occasions are when i either play video or music. some of these media players employ a wakelock that will not disable after you put your device to sleep. sometimes a reboot will work, sometimes not. most of the times the reboot keeps it from draining. even force quitting all my media apps wouldn't work.
so basically i reboot every time i use any type media player so i don't get the drain - netflix doesn't require it, dice and just about every music player does. i'm not sure it this may be your problem, but it may be a possible solution.
I find that making sure to check the last two settings under Asus Customized Settings helps this. I was waking up in the morning to find my dock dead everyday before I checked those two settings. The only down side is when I turn the screen on and wake it up, it takes about 5-10 seconds to connect to the wifi. No biggie.
Use better battery stats and see what is causing it. I have read that skype does drain battery pretty bad. And even if you're not connected it still runs in the background at start up. Another app I would recommend is Autostarts. It allows you to disable apps at start up. I know system tuner is free and has the same functionality but I find Autostarts better. With ST, you just disable the app at start up, with Autostarts you can disable it at start up, shutdown(which some apps fire when the tab is being shut down and other system events), also other events. Like some apps fire up when you get a text, or when your connection changes etc.. I just think Autostarts has more options.
Also dev Entropy has a thread in the GS2 forums about know battery drainers. Some of it applies specifically to the GS2 but there are a bunch of general battery killers listed
http://forum.xda-developers.com/showthread.php?t=1308030
If you go to setting and battery it should show you which is using the most battery. The first one on top. If its android system, you can click on it and it will show you a list of whats been using your battery which may point you to the culprit. In my case, media was the only thing in the list. And I know if an SDcard is inside my dock it will drain battery. So after removing it the drainage went away. Havent had the drain issue since. Again yours might be different so check the battery usage.
Thanks for the feedback guys, the first thing i am gonna do is charge it up after it fell flat right up to 100% then try some suggestions. I am thinking a reboot could help it.
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
I've found a similar problem, and explanations on why it's happening, but it says that it appeared in Gingerbread but has been corrected in Honeycomb and ICS.
It does seem like the exact same problem with the same symptoms though, so I wonder if it really is gone...
Here is the page where I found the info :
http://fivasim.pcriot.com/androsensor.html
And here is a quote from that page :
Update: After many months of testing and debugging I haven't found a way to fix the battery issue for good. Perhaps I shouldn't... It's not really my issue but a general android problem (just google for "gingerbread battery drain"). And it happens with EVERY app that makes use of the sensors that are the root of the problem.
The battery leakage comes from android sensors that are not well supported by the kernel or the android OS. Most usually the accelerometer sensor causes the issue but sometimes the light sensor and the proximity sensor can cause this issue as well. Other sensors seem to have nothing to do with battery drain.
However I have found what's causing it and ways to `patch` over it (unfortunately, no way to permanently fix it).
Trying to invoke a sensor with such a problem, will cause the sensor to stay open even after the app is stoped and disposed of memory.
Another common issue is a conflict. Two apps register the same sensor, then one app unregisters but fails because the sensor is in use by the other app. The sensor stays in use by one of the two apps and this will remain even after both apps are killed.
In most cases there is a way to fix this:
- In the first case, you may just find which sensor is misbehaving (strange readings, very slow response or 'Failed to start' error etc.). Go to AndroSensor's settings and disable that sensor. Then reboot, run AndroSensor once and wait to see if the problem persists. Most usually the light and the proximity sensors are to blame for this issue. Sometimes the issue is caused only if both light and proximity are enabled, but disappears after disabling any of the two.
- If you don't have a misbehaving sensor then there is probably some conflict. Conflicts can be caused (usually in Gingerbread) when having auto-rotate (accelerometer use) or auto-brightness on.
Solution: Go to your device's display settings and disable auto-brightness and auto-rotation. Then reboot, run AndroSensor once and wait to see if the battery drain continues. If the problem persists then there is probably a conflict with some hidden/system service. Most usual is the conflict with SGS and SGS2 secret menu ( by dialling "*#0*#" on the dialer ). I have found no way to bypass this and it can only be solved by disabling the accelerometer and orientation sensors in AndroSensor, then reboot (orientation sensor makes seemless use of the accelerometer).
The only good thing about this, is that in HoneyComb and ICS the issue seems to have disappeared for good!
Am I really the only one with the problem?
Mithrandir007 said:
I've noticed something strange which seems to drain my battery faster when it happens.
Some apps that use sensors seem to leave the sensor active after closing the app itself (even with force close from app manager).
I've first noticed this problem with the app "GPS Essentials", then "GPS Status" the next day, they left the "Magnetic Field" sensor active after manually force closing them.
After a few hours, in Badass Battery Monitor, I could see that the Apps were eating about 75% of the battery, and when looking at the details, "GPS Essentials" was using about 45%, more than the kernel and android system), and it said that it had been using the "Magnetic Field" sensor for more than 5 hours, although the app was manually force closed about 20 minutes after I've started it.
That was in the stock ROM.
Since then, I've installed a custom ROM (CheckROM V2, so it's still based on Samsung's base ROM), and the problem is appearing again.
This time, I've had the same problem with Sygic that left the "Orientation" sensor active, and continued using it according to Badass Battery Monitor, even after force closing Sygic.
Did anyone else notice that or is it a problem with my phone?
Is there a solution besides rebooting every time after using any of these apps?
Thanks!
Click to expand...
Click to collapse
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
chamonix said:
Does CPU Spy confirm that problem, showing awake instead of deep sleep?
Click to expand...
Click to collapse
It does seem to go to deep sleep, but I still see a big difference in battery life between when it happens (around 7-10%/hour), and after I reboot (~ 1%/hour).
Before I start applications using those sensors, the battery life is normal as well, so I don't think it's something else.
I've just made a few screenshots to show what's happening.
Last night, before going to bed, I've rebooted the phone, then started Sygic and AndroSensor, exited the apps, then manually force closed them to make sure.
Then I left the phone charging for the night.
This morning, I remove the phone from the charger, and Badass Battery Monitor starts from that point to calculate the battery drain from everything (so I'm sure neither Sygic nor AndroSensor have been running at all since I unplugged the phone).
Since then, a bit less than 2 hours have passed (I've barely used my phone during that period since I was getting ready then driving to work).
There was a 5% discharge (which is strangely not as much as I had yesterday, but still more than the usual 1%/hour when in standby) and we can clearly see what's eating the battery the most in Badass Battery Monitor.
The "Orientation", "Pressure", "Magnetic Field" and "Accelerometer" sensors have been running the whole time since it was unplugged.
What do you think, is this normal behavior?
I've now installed another custom ROM (Omega 8, with the new samsung firmware update), and the problem seems to remain..
If I'm the only one with the problem, I'm starting to think it might be something hardware (or an app I've installed every time maybe), since I've had the problem with every ROM I've installed...
Switching to another kernel didn't seem to help either.. I'm really starting to wonder if this is something I can fix.
Does no one else have the problem?
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
Click to expand...
Click to collapse
Yes I care. Thanks very much for posting this. I've noticed exactly the same thing and it's been driving me crazy. Good to know it's just a false alarm. With ICS 4.0.4 coming to the Galaxy S2 soon, maybe it will be fix there.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
If this is really the problem that would be an deep in Android or between the hardware and android as it is the 'batteryinfo' service reporting sensors data.
Indeed, I don't think there is an easy fix for this one, unless someone has already worked on that part ((un)registration of sensors from the battery measurement service).
Hopefully it'll be fixed in a future version of the firmware, or in Jelly Bean.
XDA-Usr : maybe it'll be fixed in that version, indeed..
It is just a false alarm, although it still leads to inaccuracy of the battery level.
Mithrandir007 said:
I think I've found the reason but now I wonder why no one else seems to have the problem (or maybe I'm the only one who actually cares ).
It looks like it's a battery usage reporting bug in the Samsung firmwares, not an actual drain.
Whenever you run an app which uses sensors (like GPS Status, AndroSensors, Sygic, ...), there is a good chance that when quitting the app, Android will not register the sensors as "stopped", even though they are not running anymore.
This means that the current battery life calculation takes those sensors into account as if they were still running, and the battery % drops faster than it should.
Here's a post from the creator of GPS Status, explaining the problem :
http://forum.xda-developers.com/showpost.php?p=23106668&postcount=491
There is also a small explanation from the author on the Google Play page for GPS Status, I'll quote :
"KNOWN FIRMWARE ISSUES (please do not report them):
- Samsung phones: Because of a firmware bug those phones may report extreme battery consumption for GPS Status (and for other programs using sensors) even if it is not running. This is harmless and no power is consumed! Just ignore it and let's hope that a future firmware upgrade will fix this."
So I'm still wondering if this is something we can fix, or if we have to wait for Samsung to correct that bug?
Click to expand...
Click to collapse
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
luzok said:
Now 1 year has past since your original post. I'm still experiencing the same problem on my Galaxy Note 2. :silly:
Click to expand...
Click to collapse
On my Galaxy S4, the problem seems to be gone, so hopefully it'll be gone on your device as well once Samsung releases the 4.2.2 update.
Sent from my GT-I9500 using xda app-developers app
Hi there,
i have a SIII and i'm having a strage situation with it.. although the screen is off (no wi-fi, no data, just idle) sometimes the screen turns on, without even touching it, and off again (after the seconds that it usually takes to turn the screen off when no one touches it). This can happen 10/15 times in a row with no specific interval between them (but usually just a few seconds). And then just stops for hours..
i have NFC turned off as i though maybe i had something that would send a signal..
when it turns on, if i check the phone, there aren't any notifications at all..
anyone has seen this situation in this phone??
thanks in advance
I had it ones. I figured it happened when live wallpaper was enabled. Wallpaper was from the market, not from original firmware. It never happened with stock wallpapers though.
So if you have live wallpaper, try disabling it and see if problem persists.
I call this an android virus. This mostly happens when you install an app (most probably a free app) and it just keeps on running in the background. It keeps on turning the screen, so monitor when the problem started and remove any recent installed app one by one.
I also had this situation. When i installed a custom rom, the problem just vanished.
thanks, i will try and give some feedback
having the same problem and still have no idea what is causing it.......
I'm completely stock aswel.this is very annoying when it happens
Sent from my GT-I9300 using xda premium
Hi all,
this is my very first post here on xda, so please forgive me if this is not the proper section for my thread. I searched for other thread about similar issues, but I didn't find anyone. I'm Italian, so I even hope to not being wrong in English writing.
I recently bought (on November 2014) an Huawei Ascend Y550-L01 (Android 4.4.4, EMUI 2.3, ROM B137), coming from a (Portuguese) Samsung Galaxy Y Pro GT-B5512. Soon I experienced a very strange GPS behaviour: GPS turns itself off. No problem in signal fixing, nor in quality or precision. It simply deactivates.
First I noticed this using the OruxMaps app (which works fine on many phones, even my old one), simply recording the track. Indeed, at the beginning the app was being killed (because of the integrated task-killer) when screen was off, but after setting it as a "protected" app, when I record a track, GPS works while screen is on and, if screen turns off, then most of the times (not always) GPS is deactivated from within Android settings.
I even received (from the purchasing time) some GPS errors while in the home screen... I don't remember exactly that error, but in a fast Internet search it was told being caused from the weather widget, precisely from the "actual position" setting. I deactivated it and added manually my town and those errors were gone.
Then I noted another strange behaviour: GPS turns off even in standby, during night. It is on "extreme precision" on evening and it's off at morning. Sometimes I notice these deactivation (in the notification menu or into the energy saving widget) while I'm using the phone (but always when screens is off), without any error or message popping out... It simply gets deactivated.
Any other experiencing this strange issue? What could be the cause? I sent a mail to official support, but they asked me to take the phone in a service point... I can't stay without phone, so I would like to avoid this if it's not strictly needed.
I think it's a ROM issue (said that even in the mail), but unfortunately still there is no alternative one (or at least I found none). I think also that (almost) every app that uses GPS suffers for the same behaviour I faced using OruxMaps.
PS: phone IS rooted by a couple of week, but I'm facing this issue from the first day.
What the hell is going on? Any help, idea or trying suggestion is appreciated...
Many thanks!
Up?
I also see strange problems on the Y550-L01 connected to GPS.
In my case the GPS does not disconnect completely, but during car navigation the signal gets lost from time to time (tested with different navigation apps).
This is only the case when the Y550 is NOT connected to the charger. If I connect it to the power supply, GPS works quite reliable and accurate!
For me this sounds like a software problem (maybe connected to a power saving mode?). I hope a firmware update will fix this soon.
Even to me this is a firmware issue. Before of your answer, I was really beginning to think it's a fault of my phone. Now that I'm not the only one, I went back to think of a bug.
If it is a power save problem, then try to use this app to stop the power save mode :
https://play.google.com/store/apps/details?id=eu.thedarken.wl
(ultra light : 35K, free/no adds)
"Wake Lock gives you control over the Android Power- and WifiManager.
For example, you can force the PowerManager to keep the screen on or have the CPU still running in standby mode or make sure the Wifi connection keeps running at full performance.
You can use it on any android phone or tablet.
Use it to keep the screen on in full brightness or dimmed mode during movies or slideshows.
To make sure the CPU is still running in the background doing your tasks when you press the standby button."
Thank you for the report.
It seems that the new huaweï G620S has the same GPS problem :
https://www.google.fr/search?q=G620S+GPS+problem+fix
Any news of an Huaweï update ? Hope yes...
magooz85 said:
Hi all,
this is my very first post here on xda, so please forgive me if this is not the proper section for my thread. I searched for other thread about similar issues, but I didn't find anyone. I'm Italian, so I even hope to not being wrong in English writing.
I recently bought (on November 2014) an Huawei Ascend Y550-L01 (Android 4.4.4, EMUI 2.3, ROM B137), coming from a (Portuguese) Samsung Galaxy Y Pro GT-B5512. Soon I experienced a very strange GPS behaviour: GPS turns itself off. No problem in signal fixing, nor in quality or precision. It simply deactivates.
First I noticed this using the OruxMaps app (which works fine on many phones, even my old one), simply recording the track. Indeed, at the beginning the app was being killed (because of the integrated task-killer) when screen was off, but after setting it as a "protected" app, when I record a track, GPS works while screen is on and, if screen turns off, then most of the times (not always) GPS is deactivated from within Android settings.
I even received (from the purchasing time) some GPS errors while in the home screen... I don't remember exactly that error, but in a fast Internet search it was told being caused from the weather widget, precisely from the "actual position" setting. I deactivated it and added manually my town and those errors were gone.
Then I noted another strange behaviour: GPS turns off even in standby, during night. It is on "extreme precision" on evening and it's off at morning. Sometimes I notice these deactivation (in the notification menu or into the energy saving widget) while I'm using the phone (but always when screens is off), without any error or message popping out... It simply gets deactivated.
Any other experiencing this strange issue? What could be the cause? I sent a mail to official support, but they asked me to take the phone in a service point... I can't stay without phone, so I would like to avoid this if it's not strictly needed.
I think it's a ROM issue (said that even in the mail), but unfortunately still there is no alternative one (or at least I found none). I think also that (almost) every app that uses GPS suffers for the same behaviour I faced using OruxMaps.
PS: phone IS rooted by a couple of week, but I'm facing this issue from the first day.
What the hell is going on? Any help, idea or trying suggestion is appreciated...
Many thanks!
Click to expand...
Click to collapse
Hi! Better post your question in our small Huawei Ascend Y550 thread. Maybe there someone of us can help.
If you understand German:
http://www.android-hilfe.de/huawei-...gation-unzuverlaessig-nur-im-akkubetrieb.html
These folks have the same proplem, but no solution.
Try it while a charger is attached.
Hi all,
I am getting a strange issue with my Google Play services and GCM_Reconnect wakelock.
My wifi icon keeps changing from white to orange within seconds and this creates lots of GCM_Reconnect wakelocks and eats my battery too much.
I tried to go deeper to see what exactly it's happening but other than watching few connecting and disconnected errors I couldn't find any relative helpful information to sort it out and searching didn't provide me any info about this specific issue too. I tried google as well as xda too.
If I disable my wifi, my phone is fine and these wakelocks doesn't occur anymore but as soon as I activate my wifi, these wakelocks come back and wifi icons start going from white to orange and white and then orange thus showing how aggressively my phone connects and disconnects with google servers.
I couldn't find a reason to this or how to sort it out, any help is greatly appreciated.
PS. I have removed every kind of restriction through Privacy guard but no positive result.
Thank you.
how did you get to the screen that shows the "Ping, Connect, Disconnect, Events"?
I'll explain something but you have to apply it to your situation.
These apps you can get that protect privacy, control wakelocks, control network aspects of apps, startups, processes etc etc that people claim to save battery are all, to put it in a reasonable term, crap.
They do exactly what they say they do but one thing that is never explained is that android is its own entity and will do what it does regardless of what anyone tells it to do, or not do.
An example of this would be, you run an app that changes the running status of another app. The problem is that android will always run the closed app and the app that was used to close the app will always use wakelocks to determine if the app is running or not. If it IS running the app closes it, android picks this up and runs it again so the app wakelocks and finds the app is running so closes it again. Rinse and repeat, you have a war going on in your phone!.
Android will automatically close unnecessary apps and apps you dont use or need over time. But it will ALWAYS FILL THE RAM WITH APPS. Android is natured for that.
So the be all and end all is to get rid of the apps that attempt to control your device as they are the ones responsible for the battery issues by causing app wars on your phone.
Beamed in by telepathy.