Related
I've been reading around about obtaining better battery life while the phone is idle. The #1 cause of higher battery drain is this thing called Fast Dormancy.
On the SGS2 you can turn off FD by dialing *#*#9900#*#* in the dialer. I tried that on the Atrix and nothing happens.
More info on partial wakelocks and FD:
http://forum.xda-developers.com/showthread.php?p=15869868#post15869868
When using that app, it shows that "FDCompleteTime" is at #1 for partial wakes on my Atrix.
By default, the Samsung Galaxy S II has Fast Dormancy support enabled. One of the goals of Fast Dormancy is to increase the battery life of a device, by limiting the amount of signaling between the phone and the cell network. But, when Fast Dormancy it is not enabled in the network and is enabled on the phone it ironically works the other way around, and actually drains more battery than before.
Luckily, Fast Dormancy can be disabled on the phone. For the Galaxy S II, do the following:
Dial *#9900#
Press “Disable Fast Dormancy“
Press “Exit“.
Click to expand...
Click to collapse
Source: http://www.ctrlplusz.com/2011/07/disable-fast-dormancy-improve-battery-life-on-the-galaxy-s-ii/
More info on FD: http://www.computerworld.com/s/arti...martphone_networking_and_battery_performance_
This may be a huge battery improvement if we can find a way to disable FD.
See attached for partial wakelock usage using BetterBatteryStats
I'd also like to know more about this...interesting...
My #1 partial wakelock is always Alarm Manager. I'd like to know what is causing this one (as i'm sure alot of others do as well..)
Rickroller said:
My #1 partial wakelock is always Alarm Manager. I'd like to know what is causing this one (as i'm sure alot of others do as well..)
Click to expand...
Click to collapse
see this post:
http://forum.xda-developers.com/showthread.php?p=17145428#post17145428
disabling reminders in cal may help, but may not be ideal
andy2na said:
I've been reading around about obtaining better battery life while the phone is idle. The #1 cause of higher battery drain is this thing called Fast Dormancy.
On the SGS2 you can turn off FD by dialing *#*#9900#*#* in the dialer. I tried that on the Atrix and nothing happens.
More info on partial wakelocks and FD:
http://forum.xda-developers.com/showthread.php?p=15869868#post15869868
When using that app, it shows that "FDCompleteTime" is at #1 for partial wakes on my Atrix.
Source: http://www.ctrlplusz.com/2011/07/disable-fast-dormancy-improve-battery-life-on-the-galaxy-s-ii/
More info on FD: http://www.computerworld.com/s/arti...martphone_networking_and_battery_performance_
This may be a huge battery improvement if we can find a way to disable FD.
See attached for partial wakelock usage using BetterBatteryStats
Click to expand...
Click to collapse
Just so you all are aware (and this might be exactly what you're looking for), you can find an element in Titanium Backup's "backup/restore" list called Modem Fastdormancy Monitor service.
You might be able to freeze it to achieve what you're looking for.
Take a look and let me know.
you guys may want to look at the settings for fd, it's not only on or off. I'm on my phone right now so searching is not that easy but there have been some threads about fd and I think I remember some properties that could be set to slow down the bursts occuring in logcat.
found it: http://forum.xda-developers.com/showthread.php?t=1086599
check for the database update scripts
xyrovice said:
Just so you all are aware (and this might be exactly what you're looking for), you can find an element in Titanium Backup's "backup/restore" list called Modem Fastdormancy Monitor service.
You might be able to freeze it to achieve what you're looking for.
Take a look and let me know.
Click to expand...
Click to collapse
I just saw that too...I'm skeptical to freeze it, but what's the worst that can happen right?
lexx210 said:
I just saw that too...I'm skeptical to freeze it, but what's the worst that can happen right?
Click to expand...
Click to collapse
It probably wouldnt kill your phone, but everything has risk so be careful.. have a nandroid ready. From what I've read though, it's a feature that helps save battery life so you might want to keep it.
The way it's described, it enables your phone to disconnect from the network quickly after a transmission, so not to waste battery life with unnecessary network time. But it also sounds like the app is written to help the network as well, so I'm sure there is a way it could be tweaked to help your phone's battery a little more, at the cost of the network's overall efficiency.
It's strange because FDCompleteTime doesn't really hurt me that much. It's always 4th or 5th on the batterystats list, and doesn't log much time at all. AlarmManager always tops my list, which is strange because I don't use an alarm on my phone.. It must serve another purpose.
yeah, I was out in a different area the past few hours and FD moved to second place while alarm manager took first.
At work, it seems like phone disconnects/loses signal for a second and instantly gets it back at random times. If thats the case while its sleeping, that may be why its #1 at work. I get perfectly fine reception at work, 3-4 bars no problem.
Alarm manager seems to be a universal culprit for phone wakes. FDCompleteTime may become 1st or 2nd depending where you are at and will only show off when youre not on wifi. If you are on wifi the entire day, FDCompleteTime will not show up at all on the partial wakes (or it shouldnt)
xyrovice said:
Just so you all are aware (and this might be exactly what you're looking for), you can find an element in Titanium Backup's "backup/restore" list called Modem Fastdormancy Monitor service.
You might be able to freeze it to achieve what you're looking for.
Take a look and let me know.
Click to expand...
Click to collapse
chamonix said:
you guys may want to look at the settings for fd, it's not only on or off. I'm on my phone right now so searching is not that easy but there have been some threads about fd and I think I remember some properties that could be set to slow down the bursts occuring in logcat.
found it: http://forum.xda-developers.com/showthread.php?t=1086599
check for the database update scripts
Click to expand...
Click to collapse
Thanks, Ill give both of these things a try in the next few days and monitor the FD in partial wakes and the functionality of the phone. It would be interesting if anyone with cyanogenmod Alpha can show us their top wake locks. I really think it may be a Motorola software bug.
Heres my partial wakelocks on the latest cherryblur. it was on 3g the entire time (no wifi connection). FD was #1, as expected
So I disabled "Modem Fastdormancy Monitor service" in TitaniumBackup last night and did a full recharge. I also disabled calendar notifications to see if it helped out the Alarm manager.
Its only been 2.5 hours but "FDCompleteTime" does not show on the partial wake lists at all and the battery status screen shows very little phone wakes!
As for Alarm manager, its still there, but it seems its not waking the phone as much.
Ill see how the battery is by the end of the day
andy2na said:
So I disabled "Modem Fastdormancy Monitor service" in TitaniumBackup last night and did a full recharge. I also disabled calendar notifications to see if it helped out the Alarm manager.
Its only been 2.5 hours but "FDCompleteTime" does not show on the partial wake lists at all and the battery status screen shows very little phone wakes!
As for Alarm manager, its still there, but it seems its not waking the phone as much.
Ill see how the battery is by the end of the day
Click to expand...
Click to collapse
Good news.
With regards to AlarmManager, disabling calendar reminders will certainly reduce partial wakelocks caused. As of yet, we are not sure what else contributes to this process. It is therefore normal still to see some wake cause by AlarmManager, but less than prior to removing calendar reminders.
EDIT: I also posted a means by which you can disable FD without having to freeze through Titanium over on the BBS thread (via the build.prop).
Would the phone automatically getting the time from the network contribute? My battery seems a lot better when I let it calculate the time manually and it seems to only be a few seconds off to my computers time. You can turn it off in the Date & time settings. Hope that helps.
lexx210 said:
Would the phone automatically getting the time from the network contribute? My battery seems a lot better when I let it calculate the time manually and it seems to only be a few seconds off to my computers time. You can turn it off in the Date & time settings. Hope that helps.
Click to expand...
Click to collapse
yep, that should help battery life, while not much, everything counts.
I have had it shut off for awhile now. not sure which process it contributes to in partial wakes
nobnut said:
Good news.
With regards to AlarmManager, disabling calendar reminders will certainly reduce partial wakelocks caused. As of yet, we are not sure what else contributes to this process. It is therefore normal still to see some wake cause by AlarmManager, but less than prior to removing calendar reminders.
EDIT: I also posted a means by which you can disable FD without having to freeze through Titanium over on the BBS thread (via the build.prop).
Click to expand...
Click to collapse
How does one go about disabling calendar reminders? I, for one, hardly ever use the calendar regardless (only ever to look at days/dates, never for schedules), so I wouldn't suffer from any functionality loss.
Sorry for my ignorance, and thanks for your time and info.
Also, I'm glad to see the TiBU/freeze way works. Maybe you could post a link to the build.prop version?
Thanks again. It's refreshing to see effective troubleshooting and creative thinking.
xyrovice said:
How does one go about disabling calendar reminders? I, for one, hardly ever use the calendar regardless (only ever to look at days/dates, never for schedules), so I wouldn't suffer from any functionality loss.
Sorry for my ignorance, and thanks for your time and info.
Also, I'm glad to see the TiBU/freeze way works. Maybe you could post a link to the build.prop version?
Thanks again. It's refreshing to see effective troubleshooting and creative thinking.
Click to expand...
Click to collapse
Just go into calender, menu, settings, hit set alerts & notifications and select Off.
after an entire day on 3g, I FD never showed up on the wakelock screen and after a little usage, it got 16 hours, which is slightly better than the 14 hours I had with FD enabled. I havent seen any downsides of disabling it yet.
AlarmManager was still #1, need to find out the reason behind this
guys, please run this in terminal emulator:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt
or adb:
Code:
adb shell dumpsys alarm > AlarmDump.txt
This will dump all the alarm events so you can see what is invoking AlarmManager as a wakelock. From there you can find the culprits that have a lot of wakeups. In some instances, you cant do anything about it (Android System), but in others, you can uninstall or disable notifications. Hope this helps in solving your excessive AlarmManager problems.
Scroll to the " Alarm Stats" near the bottom, it should look like this:
Code:
com.motorola.devicestatistics
3383ms running, 1 wakeups
1 alarms: act=com.motorola.devicestatistics.APP_STATS_ALARM flg=0x4
26 alarms: act=com.motorola.batterymanager.wlmonitor.CHECK_STATUS flg=0x4
13 alarms: act=com.motorola.eventlogger.START_LOG flg=0x4
1 alarms: act=com.motorola.devicestatistics.CHECKIN_STATS_ALARM flg=0x4
1 alarms: act=com.motorola.batterymanager.wlmonitor.CHECKIN flg=0x4
com.google.android.location
11688ms running, 222 wakeups
222 alarms: act=com.google.android.location.ALARM_WAKEUP flg=0x4
com.jb.gosms
685ms running, 1 wakeups
1 alarms: act=com.jb.schedule.private.box flg=0x4
com.motorola.blur.service.storagemon
7681ms running, 0 wakeups
77 alarms: act=com.motorola.blur.service.blur.Actions.CHECK_STORAGE_USAGE flg=0x4
com.netgate
1374ms running, 53 wakeups
26 alarms: flg=0x4 cmp=com.netgate/.pia.services.ReportingService
27 alarms: flg=0x4 cmp=com.netgate/.android.service.PushService
android
227995ms running, 408 wakeups
1 alarms: act=android.intent.action.DATE_CHANGED flg=0x4
7 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
1584 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
28 alarms: act=com.android.server.WifiManager.action.DEVICE_IDLE flg=0x4
155 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
2 alarms: act=com.android.server.action.UPDATE_NIGHT_MODE flg=0x4
371 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
com.levelup.beautifulwidgets
246776ms running, 10 wakeups
10 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATEWEATHER flg=0x4
1583 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATECLOCK flg=0x4
com.motorola.blur.datamanager.app
22ms running, 0 wakeups
1 alarms: act=com.motorola.blur.datamanager.app.checkin.timeout flg=0x4 cmp=com.motorola.blur.datamanager.app/.DataManagerCheckinService
ccc71.bmw
130743ms running, 1585 wakeups
1585 alarms: flg=0x4
com.motorola.kpilogger
2156ms running, 0 wakeups
13 alarms: act=com.motorola.kpilogger.START_LOG flg=0x4
com.gau.go.launcherex
528ms running, 10 wakeups
6 alarms: act=com.jiubang.intent.action.AUTO_CHECK_UPDATE flg=0x4
4 alarms: act=com.jiubang.intent.action.SCAN_APPS flg=0x4
com.motorola.datacollection
13243ms running, 0 wakeups
27 alarms: act=com.motorola.datacollection.onehourtimer flg=0x4
com.facebook.katana
1360ms running, 71 wakeups
3 alarms: flg=0x4
1 alarms: act=com.facebook.katana.service.19 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.50 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.52 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.54 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
3 alarms: act=com.facebook.katana.service.12 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
3 alarms: act=com.facebook.katana.service.11 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
3 alarms: act=com.facebook.katana.service.14 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.13 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
3 alarms: act=com.facebook.katana.service.16 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.15 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
2 alarms: act=com.facebook.katana.service.18 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.17 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.20 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.21 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.44 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.46 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.66 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.48 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.68 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.64 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.62 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.60 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.42 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
2 alarms: act=com.facebook.katana.service.40 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.83 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.24 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.23 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.81 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.22 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.28 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.26 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.79 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.10 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
7 alarms: act=com.facebook.katana.service.8 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.77 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.32 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.30 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.36 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.3 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.34 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
8 alarms: act=com.facebook.katana.service.2 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.58 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.56 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
2 alarms: act=com.facebook.katana.service.38 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
com.android.vending
1384ms running, 0 wakeups
9 alarms: act=com.android.vending.FORCE_UPDATE_CHECK flg=0x4
com.motorola.batterymanager
552ms running, 0 wakeups
3 alarms: act=android.intent.action.batteryprofile.CHK_ALRM flg=0x4
1 alarms: act=android.intent.action.batteryprofile.DATA_ALRM flg=0x4
2 alarms: act=android.intent.action.batteryprofile.DATA_CHECK flg=0x4
com.android.providers.calendar
142ms running, 2 wakeups
1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1314902700000 flg=0x4
1 alarms: act=com.android.providers.calendar.SCHEDULE_ALARM flg=0x4
com.motorola.blur.service.search
439ms running, 0 wakeups
1 alarms: act=com.motorola.blur.service.search.SCHEDULED_INDEXING_ACTION flg=0x4
com.glu.android.ck
1813ms running, 0 wakeups
105 alarms: act=com.urbanairship.push.HEARTBEAT flg=0x4 cmp=com.glu.android.ck/com.urbanairship.push.PushService
com.rdr.widgets.core
5059ms running, 134 wakeups
46 alarms: act=com.rdr.widgets.core.action.REFRESH dat=intent:#Intent;action=com.rdr.widgets.core.action.REFRESH;component=com.rdr.widgets.core/.calendar.CalendarUpdateService;i.appWidgetId=18;end flg=0x4 cmp=com.rdr.widgets.core/.calendar.CalendarUpdateService
26 alarms: act=com.rdr.widgets.core.action.ACTION_RELOAD flg=0x4 cmp=com.rdr.widgets.core/.calendar.CalendarUpdateService
42 alarms: act=com.rdr.widgets.core.action.REFRESH dat=intent:#Intent;action=com.rdr.widgets.core.action.REFRESH;component=com.rdr.widgets.core/.people.PeopleUpdateService;i.appWidgetId=16;end flg=0x4 cmp=com.rdr.widgets.core/.people.PeopleUpdateService
1 alarms: act=com.rdr.widgets.core.action.ACTION_RELOAD flg=0x4 cmp=com.rdr.widgets.core/.timeline.TimelineUpdateService
1 alarms: act=com.rdr.widgets.core.action.ACTION_RELOAD flg=0x4 cmp=com.rdr.widgets.core/.people.PeopleUpdateService
46 alarms: act=com.rdr.widgets.core.action.REFRESH dat=intent:#Intent;action=com.rdr.widgets.core.action.REFRESH;component=com.rdr.widgets.core/.timeline.TimelineUpdateService;i.appWidgetId=17;end flg=0x4 cmp=com.rdr.widgets.core/.timeline.TimelineUpdateService
com.google.android.apps.maps
1898ms running, 69 wakeups
53 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
14 alarms: act=com.google.android.location.ALARM_WAKEUP_LOCATOR flg=0x4
2 alarms: act=com.google.android.location.ALARM_WAKEUP_ACTIVE_COLLECTOR flg=0x4
com.groupon
21ms running, 1 wakeups
1 alarms: flg=0x4 cmp=com.groupon/.service.TodaysDealAlarmDownloadService
com.motorola.blur.service.blur
7368ms running, 43 wakeups
43 alarms: act=com.motorola.blur.service.blur.pm.alarmintent flg=0x4
com.probeez.profiles
401ms running, 38 wakeups
28 alarms: act=rulecheck flg=0x4 cmp=com.probeez.profiles/.manager.AutoProfileService
10 alarms: act=watchdog flg=0x4 cmp=com.probeez.profiles/.manager.AutoProfileService
com.motorola.blur.weather
272ms running, 0 wakeups
3 alarms: act=com.motorola.blur.weather.LOCATION_UPDATE_ALARM flg=0x4
1 alarms: act=com.motorola.blur.weather.LOCATION_UPDATE_GUARD flg=0x4
com.google.android.gsf
8324ms running, 66 wakeups
13 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
52 alarms: flg=0x4
1 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
com.mhuang.overclocking
21153ms running, 0 wakeups
160 alarms: act=setcpu.intent.action.updatewidget flg=0x4
com.amazon.venezia
294ms running, 13 wakeups
13 alarms: act=com.amazon.mas.client.framework.UpdateService.EXECUTE_RECURRING_TASKS flg=0x4 cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService
com.google.android.apps.googlevoice
81ms running, 1 wakeups
1 alarms: act=com.google.android.apps.googlevoice.INBOX_NOTIFICATION_REGISTRATION flg=0x4
As you can see, in my case, the services that have invoked AlarmManager seem to be BeautifulWidgets (to update the clock everytime the minute changes - 1583 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATECLOCK flg=0x4)
Battery Monitor Widget (obviously to pull the mW of the battery) - 130743ms running, 1585 wakeups
You could also reduce the amount of AlarmManager events by simply turning off Wireless location, Signing out of Google Talk, and turning off notifications or updates in apps you dont really use.
TLDR: AlarmManager is a universal process that MANY apps use to update time, push you notifications, etc. In most cases, it is a necessity; in other cases, you should really check it out and disable/uninstall things that have invoked it too much
andy2na said:
guys, please run this in terminal emulator:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt
or adb:
Code:
adb shell dumpsys alarm > AlarmDump.txt
This will dump all the alarm events so you can see what is invoking AlarmManager as a wakelock. From there you can find the culprits that have a lot of wakeups. In some instances, you cant do anything about it (Android System), but in others, you can uninstall or disable notifications. Hope this helps in solving your excessive AlarmManager problems.
Scroll to the " Alarm Stats" near the bottom, it should look like this:
Code:
com.motorola.devicestatistics
3383ms running, 1 wakeups
1 alarms: act=com.motorola.devicestatistics.APP_STATS_ALARM flg=0x4
26 alarms: act=com.motorola.batterymanager.wlmonitor.CHECK_STATUS flg=0x4
13 alarms: act=com.motorola.eventlogger.START_LOG flg=0x4
1 alarms: act=com.motorola.devicestatistics.CHECKIN_STATS_ALARM flg=0x4
1 alarms: act=com.motorola.batterymanager.wlmonitor.CHECKIN flg=0x4
com.google.android.location
11688ms running, 222 wakeups
222 alarms: act=com.google.android.location.ALARM_WAKEUP flg=0x4
com.jb.gosms
685ms running, 1 wakeups
1 alarms: act=com.jb.schedule.private.box flg=0x4
com.motorola.blur.service.storagemon
7681ms running, 0 wakeups
77 alarms: act=com.motorola.blur.service.blur.Actions.CHECK_STORAGE_USAGE flg=0x4
com.netgate
1374ms running, 53 wakeups
26 alarms: flg=0x4 cmp=com.netgate/.pia.services.ReportingService
27 alarms: flg=0x4 cmp=com.netgate/.android.service.PushService
android
227995ms running, 408 wakeups
1 alarms: act=android.intent.action.DATE_CHANGED flg=0x4
7 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
1584 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
28 alarms: act=com.android.server.WifiManager.action.DEVICE_IDLE flg=0x4
155 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
2 alarms: act=com.android.server.action.UPDATE_NIGHT_MODE flg=0x4
371 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
com.levelup.beautifulwidgets
246776ms running, 10 wakeups
10 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATEWEATHER flg=0x4
1583 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATECLOCK flg=0x4
com.motorola.blur.datamanager.app
22ms running, 0 wakeups
1 alarms: act=com.motorola.blur.datamanager.app.checkin.timeout flg=0x4 cmp=com.motorola.blur.datamanager.app/.DataManagerCheckinService
ccc71.bmw
130743ms running, 1585 wakeups
1585 alarms: flg=0x4
com.motorola.kpilogger
2156ms running, 0 wakeups
13 alarms: act=com.motorola.kpilogger.START_LOG flg=0x4
com.gau.go.launcherex
528ms running, 10 wakeups
6 alarms: act=com.jiubang.intent.action.AUTO_CHECK_UPDATE flg=0x4
4 alarms: act=com.jiubang.intent.action.SCAN_APPS flg=0x4
com.motorola.datacollection
13243ms running, 0 wakeups
27 alarms: act=com.motorola.datacollection.onehourtimer flg=0x4
com.facebook.katana
1360ms running, 71 wakeups
3 alarms: flg=0x4
1 alarms: act=com.facebook.katana.service.19 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.50 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.52 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.54 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
3 alarms: act=com.facebook.katana.service.12 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
3 alarms: act=com.facebook.katana.service.11 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
3 alarms: act=com.facebook.katana.service.14 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.13 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
3 alarms: act=com.facebook.katana.service.16 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.15 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
2 alarms: act=com.facebook.katana.service.18 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.17 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.20 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.21 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.44 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.46 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.66 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.48 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.68 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.64 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.62 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.60 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.42 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
2 alarms: act=com.facebook.katana.service.40 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.83 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.24 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.23 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.81 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.22 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.28 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.26 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.79 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.10 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
7 alarms: act=com.facebook.katana.service.8 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.77 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.32 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.30 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.36 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.3 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.34 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
8 alarms: act=com.facebook.katana.service.2 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.58 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.56 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
2 alarms: act=com.facebook.katana.service.38 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
com.android.vending
1384ms running, 0 wakeups
9 alarms: act=com.android.vending.FORCE_UPDATE_CHECK flg=0x4
com.motorola.batterymanager
552ms running, 0 wakeups
3 alarms: act=android.intent.action.batteryprofile.CHK_ALRM flg=0x4
1 alarms: act=android.intent.action.batteryprofile.DATA_ALRM flg=0x4
2 alarms: act=android.intent.action.batteryprofile.DATA_CHECK flg=0x4
com.android.providers.calendar
142ms running, 2 wakeups
1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1314902700000 flg=0x4
1 alarms: act=com.android.providers.calendar.SCHEDULE_ALARM flg=0x4
com.motorola.blur.service.search
439ms running, 0 wakeups
1 alarms: act=com.motorola.blur.service.search.SCHEDULED_INDEXING_ACTION flg=0x4
com.glu.android.ck
1813ms running, 0 wakeups
105 alarms: act=com.urbanairship.push.HEARTBEAT flg=0x4 cmp=com.glu.android.ck/com.urbanairship.push.PushService
com.rdr.widgets.core
5059ms running, 134 wakeups
46 alarms: act=com.rdr.widgets.core.action.REFRESH dat=intent:#Intent;action=com.rdr.widgets.core.action.REFRESH;component=com.rdr.widgets.core/.calendar.CalendarUpdateService;i.appWidgetId=18;end flg=0x4 cmp=com.rdr.widgets.core/.calendar.CalendarUpdateService
26 alarms: act=com.rdr.widgets.core.action.ACTION_RELOAD flg=0x4 cmp=com.rdr.widgets.core/.calendar.CalendarUpdateService
42 alarms: act=com.rdr.widgets.core.action.REFRESH dat=intent:#Intent;action=com.rdr.widgets.core.action.REFRESH;component=com.rdr.widgets.core/.people.PeopleUpdateService;i.appWidgetId=16;end flg=0x4 cmp=com.rdr.widgets.core/.people.PeopleUpdateService
1 alarms: act=com.rdr.widgets.core.action.ACTION_RELOAD flg=0x4 cmp=com.rdr.widgets.core/.timeline.TimelineUpdateService
1 alarms: act=com.rdr.widgets.core.action.ACTION_RELOAD flg=0x4 cmp=com.rdr.widgets.core/.people.PeopleUpdateService
46 alarms: act=com.rdr.widgets.core.action.REFRESH dat=intent:#Intent;action=com.rdr.widgets.core.action.REFRESH;component=com.rdr.widgets.core/.timeline.TimelineUpdateService;i.appWidgetId=17;end flg=0x4 cmp=com.rdr.widgets.core/.timeline.TimelineUpdateService
com.google.android.apps.maps
1898ms running, 69 wakeups
53 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
14 alarms: act=com.google.android.location.ALARM_WAKEUP_LOCATOR flg=0x4
2 alarms: act=com.google.android.location.ALARM_WAKEUP_ACTIVE_COLLECTOR flg=0x4
com.groupon
21ms running, 1 wakeups
1 alarms: flg=0x4 cmp=com.groupon/.service.TodaysDealAlarmDownloadService
com.motorola.blur.service.blur
7368ms running, 43 wakeups
43 alarms: act=com.motorola.blur.service.blur.pm.alarmintent flg=0x4
com.probeez.profiles
401ms running, 38 wakeups
28 alarms: act=rulecheck flg=0x4 cmp=com.probeez.profiles/.manager.AutoProfileService
10 alarms: act=watchdog flg=0x4 cmp=com.probeez.profiles/.manager.AutoProfileService
com.motorola.blur.weather
272ms running, 0 wakeups
3 alarms: act=com.motorola.blur.weather.LOCATION_UPDATE_ALARM flg=0x4
1 alarms: act=com.motorola.blur.weather.LOCATION_UPDATE_GUARD flg=0x4
com.google.android.gsf
8324ms running, 66 wakeups
13 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
52 alarms: flg=0x4
1 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
com.mhuang.overclocking
21153ms running, 0 wakeups
160 alarms: act=setcpu.intent.action.updatewidget flg=0x4
com.amazon.venezia
294ms running, 13 wakeups
13 alarms: act=com.amazon.mas.client.framework.UpdateService.EXECUTE_RECURRING_TASKS flg=0x4 cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService
com.google.android.apps.googlevoice
81ms running, 1 wakeups
1 alarms: act=com.google.android.apps.googlevoice.INBOX_NOTIFICATION_REGISTRATION flg=0x4
As you can see, in my case, the services that have invoked AlarmManager seem to be BeautifulWidgets (to update the clock everytime the minute changes - 1583 alarms: act=com.levelup.beautifulwidgets.ACTION_UPDATECLOCK flg=0x4)
Battery Monitor Widget (obviously to pull the mW of the battery) - 130743ms running, 1585 wakeups
You could also reduce the amount of AlarmManager events by simply turning off Wireless location, Signing out of Google Talk, and turning off notifications or updates in apps you dont really use.
TLDR: AlarmManager is a universal process that MANY apps use to update time, push you notifications, etc. In most cases, it is a necessity; in other cases, you should really check it out and disable/uninstall things that have invoked it too much
Click to expand...
Click to collapse
How did you get yours formatted nicely?
---------- Post added at 10:32 PM ---------- Previous post was at 10:02 PM ----------
Here is my dump file. I notice Perfect AppLock has a lot of wakelocks. What else is using an unusual amount of wakelocks?
Code:
Alarm Stats:
net.rgruet.android.g3watchdog
6471ms running, 216 wakeups
2 alarms: act=net.rgruet.android.g3watchdog.ACTION_MIDNIGHT_REACHED flg=0x4
214 alarms: act=net.rgruet.android.g3watchdog.ACTION_CHECK_SERVICE_ALIVE flg=0x4
com.motorola.devicestatistics
2480ms running, 3 wakeups
3 alarms: act=com.motorola.devicestatistics.APP_STATS_ALARM flg=0x4
67 alarms: act=com.motorola.batterymanager.wlmonitor.CHECK_STATUS flg=0x4
33 alarms: act=com.motorola.eventlogger.START_LOG flg=0x4
2 alarms: act=com.motorola.devicestatistics.CHECKIN_STATS_ALARM flg=0x4
2 alarms: act=com.motorola.batterymanager.wlmonitor.CHECKIN flg=0x4
com.sgiggle.production
606ms running, 164 wakeups
164 alarms: act=tango.service.KEEP_ALIVE flg=0x4
cmp=com.sgiggle.production/.service.MessageService
uk.co.senab.blueNotifyFree
147ms running, 4 wakeups
4 alarms: act=android.intent.action.SYNC dat=fplusfree://wservice?request=5451 flg=0x4
com.motorola.blur.service.storagemon
11442ms running, 1 wakeups
1 alarms: act=com.motorola.blur.service.blur.Actions.ACTION_PURGE_DATA cat=com.motorola.blur.service.storagemon.intent.category.LEVEL0] typ=vnd.motorola.blur.ageable/* flg=0x4
201 alarms: act=com.motorola.blur.service.blur.Actions.CHECK_STORAGE_USAGE flg=0x4
com.zomut.watchdoglite
152680ms running, 0 wakeups
3965 alarms: flg=0x4
android
374533ms running, 292 wakeups
2 alarms: act=android.intent.action.DATE_CHANGED flg=0x4
18 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
4041 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
1 alarms: act=com.motorola.wifi.MotWifiScan.action.CHANGE_SCAN_FREQ flg=0x4
403 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
138 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
135 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
com.morrison.applocklite
539029ms running, 24287 wakeups
24287 alarms: flg=0x4
com.motorola.blur.datamanager.app
66ms running, 0 wakeups
2 alarms: act=com.motorola.blur.datamanager.app.checkin.timeout flg=0x4
cmp=com.motorola.blur.datamanager.app/.DataManagerCheckinService
ccc71.bmw
125937ms running, 4042 wakeups
4042 alarms: flg=0x4
com.motorola.kpilogger
1414ms running, 0 wakeups
33 alarms: act=com.motorola.kpilogger.START_LOG flg=0x4
com.motorola.blur.tasks
694ms running, 0 wakeups
2 alarms: act=task_auto_delete flg=0x4
com.android.phone
12311ms running, 124 wakeups
124 alarms: act=com.android.internal.telephony.gprs-reconnect flg=0x4
net.sbsh.phoneweaver
19278ms running, 209 wakeups
1 alarms: act=net.sbsh.intent.action.INTENT_ACTIVATE_AUTO_PROFILE flg=0x4
4 alarms: act=net.sbsh.intent.action.INTENT_AGENDA_EVENT flg=0x4
51 alarms: act=net.sbsh.intent.action.INTENT_REPEAT_ALARM flg=0x4
16 alarms: act=net.sbsh.intent.action.INTENT_ACTIVATE_TIME_PROFILE flg=0x4
135 alarms: act=net.sbsh.intent.action.INTENT_AGENDA_REFRESH flg=0x4
2 alarms: act=net.sbsh.intent.action.INTENT_DAILY_SCHEDULE flg=0x4
com.motorola.datacollection
2825ms running, 0 wakeups
68 alarms: act=com.motorola.datacollection.onehourtimer flg=0x4
com.android.vending
1301ms running, 0 wakeups
10 alarms: act=com.android.vending.FORCE_UPDATE_CHECK flg=0x4
com.motorola.batterymanager
2096ms running, 0 wakeups
83 alarms: act=android.intent.action.batteryprofile.CHK_ALRM flg=0x4
1 alarms: act=android.intent.action.batteryprofile.DATA_ALRM flg=0x4
1 alarms: act=android.intent.action.batteryprofile.DATA_CHECK flg=0x4
com.android.providers.calendar
61ms running, 2 wakeups
1 alarms: act=com.android.providers.calendar.SCHEDULE_ALARM flg=0x4
1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1316533640522 flg=0x4
com.motorola.blur.service.search
187ms running, 0 wakeups
2 alarms: act=com.motorola.blur.service.search.SCHEDULED_INDEXING_ACTIONflg=0x4
com.motorola.blur.alarmclock
8282ms running, 6 wakeups
6 alarms: act=com.motorola.blur.alarmclock.ALARM_ALERT flg=0x4
com.motorola.PerformanceManager
6ms running, 1 wakeups
1 alarms: act=com.motorola.action.PHONE_READY flg=0x4
com.youmail.android.vvm
609ms running, 44 wakeups
35 alarms: act=com.youmail.android.intent.service.YouMailApi dat=loaded://service/2 flg=0x4
8 alarms: act=com.youmail.android.intent.service.YouMailApi dat=loaded://service/21 flg=0x4
1 alarms: act=com.youmail.android.intent.service.YouMailApi dat=loaded://service/27 flg=0x4
com.handyapps.easymoney
14001ms running, 811 wakeups
811 alarms: flg=0x4
cmp=com.handyapps.easymoney/.AlarmService_Service
com.google.android.apps.maps
4480ms running, 135 wakeups
135 alarms: flg=0x4
cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
com.motorola.blur.service.blur
19296ms running, 78 wakeups
78 alarms: act=com.motorola.blur.service.blur.pm.alarmintent flg=0x4
vStudio.Android.GPhotoPaid
120ms running, 5 wakeups
5 alarms: flg=0x4 cmp=vStudio.Android.GPhotoPaid/.Service.UpdateCheckService
com.google.android.gsf
6580ms running, 190 wakeups
40 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
134 alarms: flg=0x4
16 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
I found that Perfect AppLock was the culprit in my horrible battery life. My phone is at 1d 14h with 5% battery life left. Very pleased with that!
Now its time to give a bad review to this damn app that was working so well for me.
i charged my phone to 100% then unplugged it and get sleep (wifi and data is turned OFF)
after i wake up, i found 94% of battery and checked betterbatterystats found these services making wakelocks
=========
Wakelocks
=========
LocationFriendService (com.google.android.apps.maps.Maps): 16 m 28 s (988 s) Count:1852 3.5%
BackgroundFriendService (com.google.android.apps.maps.Maps): 1 m 42 s (102 s) Count:471 0.4%
AlarmManager (Android System): 1 m 14 s (74 s) Count:1349 0.3%
*network-location* (com.anddoes.fancywidget.pro.Fancy Widget Pro): 32 s (32 s) Count:12 0.1%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 15 s (15 s) Count:464 0.1%
3gdog.Service (net.rgruet.android.g3watchdogpro.3G Watchdog Pro): 12 s (12 s) Count:1 0.0%
*network-location* (Android System): 7 s (7 s) Count:33 0.0%
FacebookService (com.facebook.katana.Facebook): 4 s (4 s) Count:21 0.0%
backupdb (com.whatsapp.WhatsApp): 3 s (3 s) Count:1 0.0%
NLP PendingIntent client in com.google.android.apps.maps (com.google.android.apps.maps.Maps): 3 s (3 s) Count:1397 0.0%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 3 s (3 s) Count:933 0.0%
Event Log Service (Google Services): 2 s (2 s) Count:32 0.0%
ActivityManager-Launch (Android System): 1 s (1 s) Count:29 0.0%
================
i've attached full detail and graph image below this posts
my curiuos are:
- the map services like locationFriend, backgroundFriend are running even my data is turned off?
- i setup no alarm, but why AlarmManager is making wakelock??
- i've got Kernel Wakelocks from PowerManagerService for 21m, 1102 counts. Which services are running this wakelock?
thx
For the maps wakelocks, the culpit is Google Latitude. In your Latitude Settings you have to see what is making Latitude check your location frequently. In mine, I set it to do not report location. I also signed out of Latitude when I don't use it.
Another thing, under you Location and Security Settings, disable Use wireless networks when you don't need. I always disable it and enable it when I access the maps my self.
As for the Alarm, not having an alarm set doesn't mean it will not wakelock your phone. You need to make sure that all alarms are disabled. Depending on the ROM you have, the Alarm manager is known to be a battery hog.
For the other services you have, facebook etc... double check you location settings on these,how often they update and the syncs.
To answer you other questions:
- the map services like locationFriend, backgroundFriend are running even my data is turned off? -- Make sure you have Use wireless network to off and you sign out from Latitude.
- i setup no alarm, but why AlarmManager is making wakelock?? Answered above.
- i've got Kernel Wakelocks from PowerManagerService for 21m, 1102 counts. Which services are running this wakelock? This really depends on how you set your phone sleep policy. Its not a specific settings but a bunch of them that can affect the sleep of your phone...like wifi policy, sync services, location services, background processes, CPU profiles if you have them, Tasker or Locale if you use these apps...
You can minimize Data access while your phone is sleeping by disabling Background Data. Apps will have data access when you open them only...But that might be too restrictive if you need apps to work in certain automated way....
Also there is specific wakelock thread using the Betterbatterystats app, check it out:
http://forum.xda-developers.com/showthread.php?t=1179809
Hope that helps.
G+
Google+ is another great one for this and its one you seriously have to keep an eye on.
Ive disallowed 'automatic update' in the play store for it, and yet it still automatically updates.
And when it automatically updates, it automatically resets your sync options (i have them disabled)
So what ive been finding is that ill get a good week or so on my S3 with VERY good battery life, then suddenly the phone is chewing through 5% battery or so per hour.
First thing i do is check when G+ last updated. Its almost always because its a new update. That has re-enabled EVERY damn sync option that it can.
- i setup no alarm, but why AlarmManager is making wakelock??
Click to expand...
Click to collapse
AlarmManager is not for the alarm app. It is a combination of all apps that have "alarms" to wake up the phone.
- i've got Kernel Wakelocks from PowerManagerService for 21m, 1102 counts. Which services are running this wakelock?
Click to expand...
Click to collapse
This is a combination of all your partial wakelocks.
Check out this thread for more details and a much better explanation.
http://forum.xda-developers.com/showthread.php?t=1827676
At first glance I do not find anything wrong with your wakelocks except for the location friend service. Post your BBS log to the thread mentioned in the post above to make sure.
Woah didn't notice the date...this is old. Noticed the old version of BBS...
Use Titanium Backup.
MARCOSOFT said:
Use Titanium Backup.
Click to expand...
Click to collapse
"To err is human, to forgive is divine"
Sent from my SGS II
,can we prevent this from waking up?,it keeps my phone awake at night,what apps can trigger this,thanks,
-experienced it in aokp ICS and Razr-ui v7.1,tia
A lot of apps can cause it. Facebook is one of them. You'll see that waking up even if you haven't installed anything after flashing clean. Even on stock rom.
You can run this command on a terminal emulator:
Code:
$ su
# cd ..
# cd sdcard
# dumpsys alarm > AlarmManager.txt
or in adb
Code:
adb shell dumpsys alarm > AlarmManager.txt
The text file will be in your sdcard's root. Open it, scroll down, and look for the Alarm Stats area to see which applications are waking up your alarm manager. Freeze them, uninstall them, pet them, do whatever you want with them... but as usual, I will only be held responsible for the damages I do to my phone.
Like this...
Code:
Alarm Stats:
com.riteshsahu.SMSBackupRestore
1580ms running, 2 wakeups
2 alarms: act=com.riteshsahu.SMSBackupRestore.Backup flg=0x14
com.google.android.gsf
6846ms running, 97 wakeups
32 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x14
32 alarms: flg=0x14
3 alarms: act=com.google.android.intent.action.MCS_HEARTBEAT flg=0x14
30 alarms: act=com.google.android.intent.action.SEND_IDLE flg=0x14
com.android.calendar
1442ms running, 0 wakeups
1 alarms: act=com.android.calendar.APPWIDGET_SCHEDULED_UPDATE dat=content://com.android.calendar typ=vnd.android.data/update flg=0x14
com.facebook.katana
1153ms running, 95 wakeups
6 alarms: flg=0x14
1 alarms: flg=0x4 cmp=com.facebook.katana/.service.PhotoCleanupService
1 alarms: flg=0x14 cmp=com.facebook.katana/com.facebook.orca.analytics.AnalyticsPeriodicReporter$ReporterBroadcastReceiver
1 alarms: dat=fbservice:/fgbg/background_idle flg=0x4 cmp=com.facebook.katana/.service.BackgroundDetectionService
82 alarms: flg=0x4 cmp=com.facebook.katana/.service.FacebookService
2 alarms: dat=fbservice:/fgbg/pause flg=0x4 cmp=com.facebook.katana/.service.BackgroundDetectionService
1 alarms: act=com.facebook.katana.service.12 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.11 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
1 alarms: act=com.facebook.katana.service.975 flg=0x4 cmp=com.facebook.katana/.service.FacebookService
com.google.android.apps.plus
89ms running, 2 wakeups
1 alarms: act=com.google.android.apps.plus.content.cleanup flg=0x4 cmp=com.google.android.apps.plus/.service.EsService
1 alarms: act=com.google.android.apps.plus.content.sync flg=0x4 cmp=com.google.android.apps.plus/.service.EsService
org.koxx.pure_grid_calendar
37ms running, 3 wakeups
3 alarms: act=org.koxx.pure_grid_calendar.UPDATE_ALL flg=0x4 cmp=org.koxx.pure_grid_calendar/.UpdateService
com.android.vending
135ms running, 4 wakeups
1 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.DailyHygiene
3 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.ContentSyncService
android
130198ms running, 61 wakeups
1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000014
631 alarms: act=android.intent.action.TIME_TICK flg=0x40000014
32 alarms: act=com.android.server.action.NETWORK_STATS_POLL flg=0x14
82 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x14
13 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x14
1 alarms: act=com.android.server.NetworkTimeUpdateService.action.POLL flg=0x14
7 alarms: act=android.app.backup.intent.RUN flg=0x40000014
8 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x14
33 alarms: act=com.android.server.WifiManager.action.START_SCAN flg=0x14
com.google.android.apps.maps
738ms running, 13 wakeups
13 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
com.android.providers.calendar
29378ms running, 7 wakeups
7 alarms: act=com.android.providers.calendar.intent.CalendarProvider2 flg=0x14
com.keramidas.TitaniumBackup
365ms running, 1 wakeups
1 alarms: act=com.keramidas.intent.action.SCHEDULE_NEXT_WAKE_UP flg=0x14
com.google.android.gm
29ms running, 0 wakeups
1 alarms: act=com.google.android.gm.intent.provider.INDEX_MESSAGE_CONTENT dat=content://(content deleted)/indexer flg=0x4 cmp=com.google.android.gm/.provider.MailIndexerService
com.android.phone
6278ms running, 0 wakeups
142 alarms: act=com.android.internal.telephony.gprs-data-stall flg=0x14w
Sent from my LG-P500 using Tapatalk 2
androidmeda said:
A lot of apps can cause it. Facebook is one of them. You'll see that waking up even if you haven't installed anything after flashing clean. Even on stock rom.
You can run this command on a terminal emulator:
Code:
$ su
# cd ..
# cd sdcard
# dumpsys alarm > AlarmManager.txt
or in adb
Code:
adb shell dumpsys alarm > AlarmManager.txt
The text file will be in your sdcard's root. Open it, scroll down, and look for the Alarm Stats area to see which applications are waking up your alarm manager. Freeze them, uninstall them, pet them, do whatever you want with them... but as usual, I will only be held responsible for the damages I do to my phone.
Click to expand...
Click to collapse
tried it and this is what it's say,TIME_TICK has so many alarms,
Code:
Current Alarm Manager state:
Realtime wakeup (now=2012-06-01 13:06:23):
RTC_WAKEUP #0: Alarm{4074cd30 type 0 com.onycom.android.calendar}
type=0 when=+10h53m36s73ms repeatInterval=86400000 count=1
operation=PendingIntent{4074f088: PendingIntentRecord{407e8758 com.onycom.android.calendar broadcastIntent}}
RTC #2: Alarm{406fde88 type 1 android}
type=1 when=+10h53m36s44ms repeatInterval=0 count=0
operation=PendingIntent{406bfaa0: PendingIntentRecord{40692c90 android broadcastIntent}}
RTC #1: Alarm{408fe988 type 1 android}
type=1 when=+36s44ms repeatInterval=0 count=0
operation=PendingIntent{40669048: PendingIntentRecord{406bfa28 android broadcastIntent}}
RTC #0: Alarm{4074ae38 type 1 com.tni.TasKiller}
type=1 when=+11s890ms repeatInterval=15000 count=1
operation=PendingIntent{407c1a10: PendingIntentRecord{407c8270 com.tni.TasKiller startService}}
Elapsed realtime wakeup (now=+2d2h8m36s773ms):
ELAPSED_WAKEUP #0: Alarm{407543d0 type 2 android}
type=2 when=+21h52m36s948ms repeatInterval=86400000 count=1
operation=PendingIntent{40773068: PendingIntentRecord{40772298 android broadcastIntent}}
ELAPSED #0: Alarm{409369f0 type 3 android}
type=3 when=+2m7s806ms repeatInterval=0 count=0
operation=PendingIntent{40635910: PendingIntentRecord{406518e8 android broadcastIntent}}
Broadcast ref count: 0
Alarm Stats:
android
245194ms running, 1 wakeups
2 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
1577 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
1 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
234 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
com.handcent.nextsms
3142ms running, 187 wakeups
187 alarms: flg=0x4
com.tni.TasKiller
147025ms running, 0 wakeups
4142 alarms: dat=/widgetRefresh/ flg=0x4 cmp=com.tni.TasKiller/.TasKillerLauncher
com.onycom.android.calendar
5263ms running, 5 wakeups
5 alarms: act=updateToday flg=0x4
You'd normally want to focus on the wakeups, not the alarms themselves. Like in your case,
Code:
com.handcent.nextsms
3142ms running, 187 wakeups
187 alarms: flg=0x4
If you could, try using just the stock messaging for a moment and see if that makes a difference. You'll have to uninstall/freeze handcent, of course. And then compare battery life to see if removing that app drastically affects your battery life (which I'm assuming is your reason for questioning the alarm manager in the first place).
androidmeda said:
You'd normally want to focus on the wakeups, not the alarms themselves. Like in your case,
Code:
com.handcent.nextsms
3142ms running, 187 wakeups
187 alarms: flg=0x4
If you could, try using just the stock messaging for a moment and see if that makes a difference. You'll have to uninstall/freeze handcent, of course. And then compare battery life to see if removing that app drastically affects your battery life (which I'm assuming is your reason for questioning the alarm manager in the first place).
Click to expand...
Click to collapse
,ill try it,thanks,but ill try first my solution,i freeze bunch of things that i think causes the problem,thanks for replying,^^
Careful not to freeze critical system apps.
Sent from my LG-P500 using Tapatalk 2
com.tni.TasKiller 4142 alarms ??
Why are u even using a task killer? Android's mom, Google, says it's no good to end tasks as you please. Android knows how to handle memory by itself. If u still do want to end tasks, do it manually, not automatically. Just kill that task killer. System panel is a simple app which has a widget able to kill the apps you want from a predefined list.
In my case max wakeup is 580 by go weathe.is ok or should i do something about it?
klaudyuxxx said:
com.tni.TasKiller 4142 alarms ??
Why are u even using a task killer? Android's mom, Google, says it's no good to end tasks as you please. Android knows how to handle memory by itself. If u still do want to end tasks, do it manually, not automatically. Just kill that task killer. System panel is a simple app which has a widget able to kill the apps you want from a predefined list.
Click to expand...
Click to collapse
,i use it wisely i only kill games with it,i ignore apps that is usually inuse,for example,launcher,messaging,settings,cmsettings,etc,and i use that task killer since ive got my phone and it dosent drain much battery,
vikasb32 said:
In my case max wakeup is 580 by go weathe.is ok or should i do something about it?
Click to expand...
Click to collapse
You could increase the number of minutes/hours in between checks for go weather. Apps like that try to sync with servers every so often.
Sent from my LG-P500 using Tapatalk 2
algie
just curious, how long does your battery give back up for? I'm on AOKP ICS, with 3G disabled. I am getting 3 days of backup, with nominal wifi, 2g data usage.
thanks,
c
coolics said:
algie
just curious, how long does your battery give back up for? I'm on AOKP ICS, with 3G disabled. I am getting 3 days of backup, with nominal wifi, 2g data usage.
thanks,
c
Click to expand...
Click to collapse
1 and a half with 40% remaining,thats text and some wifi,2g connection,also,do you have wake bugs?,
I think I have minimal wakelocks. But then again, I've not installed a whole lot of apps.
This is wat I've done.. Got 2m Alarm manager wake lock in 11 hrs standby..
Uninstall Google contact sync, Calender sync, network location, partner setup,talk
Block internet access for Android system.. Don't block gsf..
Uncheck back up data in privacy settings..
,freeze taskkiller and handcent sms,still my phone wakes up,now i nandrestore my oxygen 2.7,mybe ill stick to this,^^,gonna update to 2.8 nxt tym,
carrthee89 said:
This is wat I've done.. Got 2m Alarm manager wake lock in 11 hrs standby..
Uninstall Google contact sync, Calender sync, network location, partner setup,talk
Block internet access for Android system.. Don't block gsf..
Uncheck back up data in privacy settings..
Click to expand...
Click to collapse
Does Google Play still work after that?
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
algie17 said:
,freeze taskkiller and handcent sms,still my phone wakes up,now i nandrestore my oxygen 2.7,mybe ill stick to this,^^,gonna update to 2.8 nxt tym,
Click to expand...
Click to collapse
A majority of mine was for google talk and facebook. I decided to freeze and kill the apps when not in use. I still get some wakelocks but that's expected with smartphones. My battery life seems to be around the same with stock GB and CM7 and oxygen, though.
androidmeda said:
Does Google Play still work after that?
---------- Post added at 02:48 PM ---------- Previous post was at 02:46 PM ----------
A majority of mine was for google talk and facebook. I decided to freeze and kill the apps when not in use. I still get some wakelocks but that's expected with smartphones. My battery life seems to be around the same with stock GB and CM7 and oxygen, though.
Click to expand...
Click to collapse
,i dont have gapps in mine also i freezes facebook,i dnt know what makes it wake up,wakeups now gone in oxygen,same apps in TB,so i know that not of my apps makes it wakeup,
In the space of a few hours I have Android waking up my phone 253 times:
Code:
android
1391915ms running, 253 wakeups
6 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x14
190 alarms: act=com.android.server.LightsService.action.UPDATE_SVC_LED flg=0x14
339 alarms: act=android.intent.action.TIME_TICK flg=0x40000014
13 alarms: act=com.android.server.action.NETWORK_STATS_POLL flg=0x14
36 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x14
12 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x14
45 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x14
I had this in last boot:
Code:
android (): Wakeups: 1398
Alarms: 1380, Intent: com.android.server.LightsService.action.UPDATE_SVC_LED
Alarms: 178, Intent: android.intent.action.TIME_TICK
Alarms: 7, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 19, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 12, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 2, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 1, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
Alarms: 4, Intent: android.content.syncmanager.SYNC_ALARM
Is that my Led activity that is waking up my device??
Sent from my GT-i9300 using TapaTalk2
Over 800 alarms from com.google.android.location are observed in BBS overnight.
I know this can be solved by disabling location service, but is there a way that I can identify which apps are causing the alarms?
I have already turned off wifi/mobile data/auto sync.
Thanks:laugh:
Ask the question in this thread.
chamonix said:
[APP] [26 Aug - V1.10] BetterBatteryStats adds battery history back to Android
Click to expand...
Click to collapse
Sent from my Desire S
Since few days i see in betterbatterystats com.google.android.gms alarms 50% usage of battery, 40 wakeups per hour.
Why?
what should i do?
My device is in signature - samsung g900f s5 with marshmallow.
xtam said:
Since few days i see in betterbatterystats com.google.android.gms alarms 50% usage of battery, 40 wakeups per hour.
Why?
what should i do?
My device is in signature - samsung g900f s5 with marshmallow.
Click to expand...
Click to collapse
Get Amllify pro and limit as u want.