So i downloaded BetterBatteryStats and found that in my wakelock there is a service "AlarmManager" that won't stop and i believe is the reason behind my "phone idle" battery drain issue...is it safe to stop it? and if so, how can i stop it?
I can't seem to find it in Titanium Backup to freeze..
bump...
I have the same issue. I'm going to try this fix.
http://forum.xda-developers.com/showthread.php?t=1198333
I also see a lot of wakelocks caused by AlarmManager. When I look at my battery stats the phone is active about 50% even though the screen is only on 10% of the time. The activity doesn't seem to correlate to anything either. It isn't cyclical like an hourly update or something.
According to Google, the AlarmManager handles the following:
This class provides access to the system alarm services. These allow you to schedule your application to be run at some point in the future. When an alarm goes off, the Intent that had been registered for it is broadcast by the system, automatically starting the target application if it is not already running. Registered alarms are retained while the device is asleep (and can optionally wake the device up if they go off during that time), but will be cleared if it is turned off and rebooted.
The Alarm Manager holds a CPU wake lock as long as the alarm receiver's onReceive() method is executing. This guarantees that the phone will not sleep until you have finished handling the broadcast. Once onReceive() returns, the Alarm Manager releases this wake lock. This means that the phone will in some cases sleep as soon as your onReceive() method completes. If your alarm receiver called Context.startService(), it is possible that the phone will sleep before the requested service is launched. To prevent this, your BroadcastReceiver and Service will need to implement a separate wake lock policy to ensure that the phone continues running until the service becomes available.
Note: The Alarm Manager is intended for cases where you want to have your application code run at a specific time, even if your application is not currently running. For normal timing operations (ticks, timeouts, etc) it is easier and much more efficient to use Handler.
You do not instantiate this class directly; instead, retrieve it through Context.getSystemService(Context.ALARM_SERVICE).
Click to expand...
Click to collapse
http://developer.android.com/reference/android/app/AlarmManager.html
This leads me to believe that something is registering events that are causing the phone to frequently wake up. I may try reviewing the logs to find out what is doing this.
EDIT: After spending sometime, I couldn't find anything. I recently downloaded BetterBatteryStats version 0.7.0 which seems much improved. I no longer see AlarmManager in the list, so maybe it was a red herring and nothing was wrong? I will keep monitoring
Nope, still getting a lot of partial wakelocks for AlarmManager. About 1 hour for every 8 hours of run time.
Anyone have any idea how to track down what is registering for the wakelocks in AlarmManager?
krkeegan said:
Nope, still getting a lot of partial wakelocks for AlarmManager. About 1 hour for every 8 hours of run time.
Anyone have any idea how to track down what is registering for the wakelocks in AlarmManager?
Click to expand...
Click to collapse
I'm not sure if you're still looking for this information but running the command below should show you registered events hooked into the alarmmanager service.
adb shell dumpsys alarm
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 recently installed Semi V17 and an updated BetterBatteryStats version. With that combination, I noticed that my device was never able to move into deep sleep due to constant location updates, thus causing battery drain. I think I've narrowed down the culprit for my battery drain, however, I'm not sure I know how to resolve it. It appears to be the Latitude support in Google Maps. I'm not enrolled in Latitude, but based on "adb shell dumpsys" output, it appears that it is running and requesting location updates constantly. The following is the registration for location updates from dumpsys. Notice that it is specifying no minimum time or distance, which implies (to me) constant updates.
Code:
Receiver{419e7ad0 Listener [email protected]}mUpdateRecords: {passive=UpdateRecord{421e75a0 mProvider: passive mUid: 10084}}:
passive:
UpdateRecord{421e75a0 mProvider: passive mUid: 10084}
mProvider=passive mReceiver=Receiver{419e7ad0 Listener [email protected]}mUpdateRecords: {passive=UpdateRecord{421e75a0 mProvider: passive mUid: 10084}}
mMinTime=0 mMinDistance=0.0
mSingleShot=false
mUid=10084
Dumpsys identifies the 10084 process as the LocationFriendService:
Code:
*APP* UID 10084 ProcessRecord{41af23e8 13037:com.google.android.apps.maps:LocationFriendService/10084}
class=com.google.googlenav.android.AndroidGmmApplication
Does anyone have any idea how to disable this service without completely freezing/removing the Google Maps application?
Thanks,
Craig
Have you turned off automatic location detection in the Latitude/Maps settings? You can completely disable it or set so it asks you to update it manually.
Also if you have Facebook installed make sure you disable location reporting in your Facebook app settings. That was a big one for me.
One other thing to check is any widgets that use location detection (like weather widgets).
In settings... same place where you enable the GPS.
Strangely, I had to click through to enable Latitude before I could get to the settings to control Latitude and really shut it off. I've now turned off everything I could find related to Latitude and will see if that "sticks". Previously, it would seem to work for some period of time and then all of the sudden start running like crazy, so until I've run like this for at least 24 hours I'm just not going to know if I've truly managed to disable this service.
Next time, check here first.http://www.chucknorrisfacts.com/
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
csetera said:
Strangely, I had to click through to enable Latitude before I could get to the settings to control Latitude and really shut it off. I've now turned off everything I could find related to Latitude and will see if that "sticks". Previously, it would seem to work for some period of time and then all of the sudden start running like crazy, so until I've run like this for at least 24 hours I'm just not going to know if I've truly managed to disable this service.
Click to expand...
Click to collapse
It appears like disabling all things Latitude has cured my battery drain. If only they hadn't hidden those settings, it would have been way more obvious. Thanks for the tip.
Hi all,
I have an AT&T Samsung Note 3 SM-N900A running Android 4.3 (baseband version N900AUCUBMJ5, kernel v3.4.0-1625098). I rooted it using Kingo, installed Tasker (with Secure Settings plugin), and created 2 profiles: one with a 'Home' location context, and one with a 'Work' location context. In the 'Location Edit' map screen for each, I set a pinned location w/ a radius of 200m. I also de-select 'GPS' (leaving only 'NET'), since I don't want GPS enabled all the time (to extend battery life). I confirm that these work when I'm actively using the phone.. the profile becomes active when I'm at the specified location (as expected). I know it's active because it's displayed in the Notification Panel (and it's also shown in green in the Tasker profiles list).
The issue I'm having is that after ~10 minutes of idle time (i.e. when the display is off and I'm not using the phone), I find that the profile is no longer active when I turn the display back on and start using the phone again. I confirmed that this *doesn't* happen after 1 minute, 2 minutes, nor 5 minutes… only > 10. I also confirmed that it happens for both profiles consistently. However, as soon as I start Tasker again from the Apps Drawer (or from Recent Apps screen), the profile is immediately activated again, and my Enter task is re-run.
I enabled the run log in Tasker prefs, but it basically shows a clean activation of the profile (with no warnings or anything that looks weird to me).
I know there's a 10-minute timeout in the Display Off Monitoring prefs, but that doesn't seem to be related to my issue. I tried reducing the All Checks Seconds from 600 to 90, rebooted the phone, and it still took ~10 minutes before the profile would become inactive after the phone being idle.
Any thoughts as to what the culprit might be? Are there any system logs I can look at that might shed some light here? I'm new to Android, and this seemed like the place to ask..
Thanks.
Ok, not solved..
Alright, bumping this, as the problem is back again after some time.
Has anyone ever seen Tasker exhibit the behavior I described? Again, I start the phone and Tasker profile is active, let the phone go idle for >10 minutes, the profile is no longer active and I need to restart Tasker manually to make it active again.
Still trying to figure out what logs are best to look at..
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Nafiganado said:
Hi all,
I experience problems with kernel wakelock, named "s5p-ehci". In random moment it's getting seized my phone and the phone stops sleeping. It looks like:
all other kernel wakelocks and partial wakelocks take less than 1 min of activity, whereas s5p-ehci is active during hours. So, for instance, if s5p-ehci is active at night - I am loosing about 4% of charge per hour (phone deep sleep time is 0%).
Temporary solution is to reboot the device: so s5p-ehci's activity time is between seconds and minute, later it gets crazy again and is active constantly. I did not succeed to find some relation between it and applications or system processes.
I am not an Android developer, but since there is no other kernel for my device (Meizu MX2) I'm eager to TURN OFF this damned s5p-ehci... Please, tell me, how to do it:
either via build.prop or via linux command or changing some configs.
I have tried to use other firmware, wiped my phone and tried to work without my apps, but all in vain: so I still don't know, WHY this s5p-ehci is on Earth getting so active so long all of the sudden. It has nothing to do with USB, because my phone is not plugged with cable when it happens
Click to expand...
Click to collapse
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
es0tericcha0s said:
Since it persistent across different versions of the software, I'm wondering if it is not hardware related, like the USB is shorting out or messed up (yes, I read that it wasn't plugged in during the main issue, but doesn't mean it is not the root cause). Have you tried using https://play.google.com/store/apps/details?id=com.uzumapps.wakelockdetector to see if maybe it can narrow down the source of your issues?
Click to expand...
Click to collapse
Hi,
yes, i've used Wakelock detector app as well as its advanced colleague - BetterBatteryStats. So that's how I've found out about "s5p-ehci" wakelock. And I can see there is no other reason of phone insomnia, besides s5p-ehci.
All other apps and processes consume CPU moderately. When s5p-ehci activity is moderate - phone sleeps well. When it gets berserk and is active during several hours - phone does not sleep at all during whole this time (deep sleep is 0%), instead works on minimal frequency (300MHz), however, it's about 40% of battery draining per night.
If it's a hardware issue - I wonder who can help me with that investigation. Services do not deal with such cases, since there is no permanent problem signs. In my case the process can behave properly during a day. Then, all of a sudden, it's getting active and some its activity lasts hours! Then it's getting back to normal again. I've looked at kernel log and system log. There is a lot of various events happening there: something is going on, then device sent to sleep, then again something is going on, then wakeup, in various cases wakeup reasons are different, I was unable to find some relevant info... I would send this log to anyone who could help me to find source of the problem.
I've rolled back to Android 4.1 firmware and installed custom kernel.
Here situation is better, but what I have discovered:
phone seems not to detect when it's being plugged off from charger - no matter, USB cable from computer or wall socket wire. s5p-ehci does not go away and sucks off my battery. What only helps is manually resetting EHCI power: setting 0 in ehci_power file. As a result, something is reset, ehci power is on again, but this sucker goes away and after that everything is fine until next charge. But I need to find a root of the problem!
Going on investigation - too view info in Internet...
Is it possible to set up Tasker (maybe with this plugin: https://play.google.com/store/apps/details?id=com.intangibleobject.securesettings.plugin ) or another automation app (eg Macrodroid) so that it wakes up the phone every x minutes, say, every hour, in order to cause the phone from exiting Marshmallow's Doze mode?
Doze is causing lots of problems with lots of apps because it breaks most push notifications; unless you're rooted, you cannot disable it, and disabling battery optimisation for a given app doesn't do much. I cannot root my phone otherwise the app to connect to my work email won't work.
I was wondering if it is possible to set some automated task that indirectly causes to phone to exit the doze mode, e.g. turning the screen on for 10 seconds every 60 minutes, or launching a specific app, or else.
Has anyone tried it?
Also, I haven't found a way to monitor when the phone is in Doze, nor have I found any official documentation on what triggers Doze (phone stationary, but for how long?).
Thanks
No one knows?
Anyway, this partial solution works for me: http://androidforums.com/threads/ma...x-is-preventing-doze-with-macrodroid.1058445/
It's about using MacroDroid to wake up the phone every 45 minutes, thus prveenting Doze mode from kicking in at all. Battery usage is acceptable (1% /hour with two push emails on).
I don't know if MacroDroid or Tasker can be set up to cause the phone to exit Doze mode, but this solution, however partial or indirect, is better for me as having push email on is a priority to me.