alarm manager wakelock battery drain help!

Search This thread

craze96

Senior Member
Dec 23, 2010
155
3
so I just installed BetterBatteryStats and under wakelock the culprit is alarm manager. I don't have any alarms on but it keeps turning on how to turn this thing off? thanks
will hit thanks for any helpful answers :)
 

twiztedvvv

Senior Member
Mar 14, 2010
253
25
O sorry i didnt realize you meant alarm manager was a system app.
You can uninstall it using root but not a good idea.
I have not heard of this causing battery drain though.

Sent from my Desire HD using XDA Premium App
 
It can cause drain, but its not the AlarmManager in it self that is causing it, its the other apps that use it. Other apps use it to wake up on specific times or intervals, like if you have a weather widget that needs updating every 30 min or an application that checks your location every x min etc. Here are parts of my own AlarmManager dump and you might get the idea what I mean:

Code:
  Alarm Stats:
  com.google.android.gsf
    20993ms running, 75 wakeups
    4 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
    42 alarms: flg=0x4
    29 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4

  se.f1nally.snowstorm
    547ms running, 11 wakeups
    11 alarms: act=se.f1nally.yrvader.UPDATE_ALL flg=0x4 cmp=se.f1nally.snowstorm/.UpdateService

  com.mobitobi.android.gentlealarm
    2128ms running, 11 wakeups
    11 alarms: act=com.mobitobi.android.gentlealarm.ALARM_ALERT flg=0x4

  com.jb.gosms
    45ms running, 1 wakeups
    1 alarms: act=com.jb.schedule.private.box flg=0x4

  com.blizzard.bma
    2061402ms running, 0 wakeups
    2611 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4

  android
    809072ms running, 281 wakeups
    1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
    9 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
    1138 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
    123 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
    19 alarms: act=android.app.backup.intent.RUN flg=0x40000004
    80 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
    173 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4

  com.liato.bankdroid
    443ms running, 6 wakeups
    6 alarms: flg=0x4 cmp=com.liato.bankdroid/.appwidget.AutoRefreshService

  com.google.android.apps.maps
    804ms running, 43 wakeups
    43 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService

  com.viber.voip
    164775ms running, 618 wakeups
    617 alarms: act=com.viber.voip.action.KEEP_ALIVE_RECEIVE flg=0x4
    1 alarms: act=com.viber.voip.action.VERSION_CHECK flg=0x4

  net.dinglisch.android.tasker
    14114ms running, 104 wakeups
    90 alarms: act=net.dinglisch.android.tasker.ANOFFCHECKORUM flg=0x4
    14 alarms: act=net.dinglisch.android.tasker.ALARUM flg=0x4

  de.devmil.minimaltext
    6619ms running, 0 wakeups
    64 alarms: act=updatetasker dat=minimaltextwidget://widget/id/updatetasker flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
    249 alarms: act=update dat=minimaltextwidget://widget/id/update flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
    59 alarms: act=forceupdate dat=minimaltextwidget://widget/id/forceupdate flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
    3 alarms: act= dat=minimaltextwidget:/weather/ flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService
    3 alarms: act=ForceUpdate dat=minimaltextwidget:/weather/ForceUpdate flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService

  org.koxx.pure_calendar
    29ms running, 5 wakeups
    5 alarms: act=org.koxx.pure_calendar.UPDATE_ALL flg=0x4 cmp=org.koxx.pure_calendar/.UpdateService

  com.bigtincan.android.adfree
    11231ms running, 1 wakeups
    1 alarms: flg=0x4

It is part of the android os so thats why I dont think you can uninstall it. See this page for dev info on AlarmManager.
 

kyo_udon

Member
Dec 14, 2010
20
1
Connect your phone to a computer and run this:

Code:
adb shell dumpsys alarm > AlarmDump.txt

or download GScript lite and create the following script:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt

Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.

where can i find the AlarmDump.txt on my computer?
 
Last edited:
  • Like
Reactions: Sean Harita

LordManhattan

Senior Member
Oct 20, 2007
15,047
5,495
Kepler-34b
It can cause drain, but its not the AlarmManager in it self that is causing it, its the other apps that use it. Other apps use it to wake up on specific times or intervals, like if you have a weather widget that needs updating every 30 min or an application that checks your location every x min etc. Here are parts of my own AlarmManager dump and you might get the idea what I mean:

Code:
  Alarm Stats:
  com.google.android.gsf
    20993ms running, 75 wakeups
    4 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
    42 alarms: flg=0x4
    29 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4

  se.f1nally.snowstorm
    547ms running, 11 wakeups
    11 alarms: act=se.f1nally.yrvader.UPDATE_ALL flg=0x4 cmp=se.f1nally.snowstorm/.UpdateService

  com.mobitobi.android.gentlealarm
    2128ms running, 11 wakeups
    11 alarms: act=com.mobitobi.android.gentlealarm.ALARM_ALERT flg=0x4

  com.jb.gosms
    45ms running, 1 wakeups
    1 alarms: act=com.jb.schedule.private.box flg=0x4

  com.blizzard.bma
    2061402ms running, 0 wakeups
    2611 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4

  android
    809072ms running, 281 wakeups
    1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
    9 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
    1138 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
    123 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
    19 alarms: act=android.app.backup.intent.RUN flg=0x40000004
    80 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
    173 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4

  com.liato.bankdroid
    443ms running, 6 wakeups
    6 alarms: flg=0x4 cmp=com.liato.bankdroid/.appwidget.AutoRefreshService

  com.google.android.apps.maps
    804ms running, 43 wakeups
    43 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService

  com.viber.voip
    164775ms running, 618 wakeups
    617 alarms: act=com.viber.voip.action.KEEP_ALIVE_RECEIVE flg=0x4
    1 alarms: act=com.viber.voip.action.VERSION_CHECK flg=0x4

  net.dinglisch.android.tasker
    14114ms running, 104 wakeups
    90 alarms: act=net.dinglisch.android.tasker.ANOFFCHECKORUM flg=0x4
    14 alarms: act=net.dinglisch.android.tasker.ALARUM flg=0x4

  de.devmil.minimaltext
    6619ms running, 0 wakeups
    64 alarms: act=updatetasker dat=minimaltextwidget://widget/id/updatetasker flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
    249 alarms: act=update dat=minimaltextwidget://widget/id/update flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
    59 alarms: act=forceupdate dat=minimaltextwidget://widget/id/forceupdate flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
    3 alarms: act= dat=minimaltextwidget:/weather/ flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService
    3 alarms: act=ForceUpdate dat=minimaltextwidget:/weather/ForceUpdate flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService

  org.koxx.pure_calendar
    29ms running, 5 wakeups
    5 alarms: act=org.koxx.pure_calendar.UPDATE_ALL flg=0x4 cmp=org.koxx.pure_calendar/.UpdateService

  com.bigtincan.android.adfree
    11231ms running, 1 wakeups
    1 alarms: flg=0x4

It is part of the android os so thats why I dont think you can uninstall it. See this page for dev info on AlarmManager.

I have/had the same problem with that service, but after i read your post, i remembered that my Facebook, G+ and RSS feed is set to update every hour. Solution? Update manually from now on :)
 
  • Like
Reactions: JLHumbert

maka8

Member
Jan 26, 2012
12
0
My AlarmDump. How to interpret?

I was hoping someone can take a look at this dump and help me interpret? My battery life sucks and AlarmManager was the highest at 1 hr 1 min of partial wakelocks as reported by Better Battery Stats.

Not sure I am reading this log right, but I'm guessing we want the lower the # of wake locks the better, but the total running time for those # of wakeups is probably more important I am assuming. So "com.amazon.venezia" with 410ms running and 24 wakeups is probably using LESS battery than the "com.xfinity.tv" with 498ms running and 1 wakeups. Does that sound about right?

My dump is here since it was too big for this url:
justpaste.it/alarmdumptxt
 

starbright_

Senior Member
Apr 11, 2010
1,432
249
Can you give me help in interpreting this? Just point which parts are of importance and why, maybe give a hint of how do reduce the load by Alarm.
This might be an example for others too.
Code:
Current Alarm Manager state:
 
  Realtime wakeup (now=2012-03-26 10:13:59):
  RTC_WAKEUP #17: Alarm{4095c618 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{4097f250: PendingIntentRecord{40904180 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #16: Alarm{4090c788 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{4092eed8: PendingIntentRecord{4094c838 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #15: Alarm{40a44320 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{40a33410: PendingIntentRecord{40a31cb8 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #14: Alarm{4092df20 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{4058e368: PendingIntentRecord{40574b10 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #13: Alarm{40a05f90 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{409bc5e8: PendingIntentRecord{40a05f18 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #12: Alarm{407b7f68 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{4095e550: PendingIntentRecord{40a2ecc8 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #11: Alarm{4092a308 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{405ab6a0: PendingIntentRecord{4094a640 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #10: Alarm{4098bae0 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{40928c30: PendingIntentRecord{40b34878 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #9: Alarm{40b2a8c0 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{40a03590: PendingIntentRecord{40a589f8 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #8: Alarm{40a32220 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{407ca930: PendingIntentRecord{40a321a8 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #7: Alarm{409a1c20 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{40aa09b0: PendingIntentRecord{40acd310 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #6: Alarm{40bc03c0 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{409f6e20: PendingIntentRecord{40bc0348 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #5: Alarm{4099a7d0 type 0 com.google.android.gsf}
    type=0 when=+4d3h27m53s60ms repeatInterval=596271000 count=0
    operation=PendingIntent{405bce00: PendingIntentRecord{40b842f0 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #4: Alarm{409a56f0 type 0 com.android.vending}
    type=0 when=+12h5m50s99ms repeatInterval=0 count=0
    operation=PendingIntent{4086d2d8: PendingIntentRecord{40bf6218 com.android.vending startService}}
  RTC_WAKEUP #3: Alarm{40be64b8 type 0 com.android.providers.calendar}
    type=0 when=+59m18s164ms repeatInterval=0 count=0
    operation=PendingIntent{409c06f8: PendingIntentRecord{40be6440 com.android.providers.calendar broadcastIntent}}
  RTC_WAKEUP #2: Alarm{4097c0a8 type 0 com.carl.tcpro}
    type=0 when=+56m43s378ms repeatInterval=0 count=0
    operation=PendingIntent{409829a0: PendingIntentRecord{40931070 com.carl.tcpro broadcastIntent}}
  RTC_WAKEUP #1: Alarm{40a1a148 type 0 com.google.android.gsf}
    type=0 when=+12m39s711ms repeatInterval=1800000 count=0
    operation=PendingIntent{40862d48: PendingIntentRecord{409270e0 com.google.android.gsf broadcastIntent}}
  RTC_WAKEUP #0: Alarm{40adda38 type 0 ccc71.bmw.pro}
    type=0 when=+51s501ms repeatInterval=60000 count=1
    operation=PendingIntent{4096db50: PendingIntentRecord{408dc0c0 ccc71.bmw.pro broadcastIntent}}
  RTC #1: Alarm{40a18a10 type 1 android}
    type=1 when=+1h46m0s382ms repeatInterval=0 count=0
    operation=PendingIntent{407a5be8: PendingIntentRecord{4082f728 android broadcastIntent}}
  RTC #0: Alarm{40868118 type 1 android}
    type=1 when=+382ms repeatInterval=0 count=0
    operation=PendingIntent{407cc4a8: PendingIntentRecord{40794130 android broadcastIntent}}
 
  Elapsed realtime wakeup (now=+1d19h4m25s877ms):
  ELAPSED_WAKEUP #8: Alarm{409b9610 type 2 android}
    type=2 when=+4d19h7m48s886ms repeatInterval=0 count=0
    operation=PendingIntent{4082ea00: PendingIntentRecord{4084f700 android broadcastIntent}}
  ELAPSED_WAKEUP #7: Alarm{4088fe08 type 2 android}
    type=2 when=+26m6s381ms repeatInterval=1800000 count=1
    operation=PendingIntent{40861368: PendingIntentRecord{4088fd90 android broadcastIntent}}
  ELAPSED_WAKEUP #6: Alarm{409b3a38 type 2 tv.dailyme.android}
    type=2 when=+14m45s126ms repeatInterval=0 count=0
    operation=PendingIntent{4098c660: PendingIntentRecord{40a1a7d0 tv.dailyme.android startService}}
  ELAPSED_WAKEUP #5: Alarm{405c45a0 type 2 com.google.android.apps.maps}
    type=2 when=+11m6s381ms repeatInterval=900000 count=0
    operation=PendingIntent{409f7738: PendingIntentRecord{40a37f48 com.google.android.apps.maps startService}}
  ELAPSED_WAKEUP #4: Alarm{409b6658 type 2 com.google.android.gsf}
    type=2 when=+10m53s906ms repeatInterval=0 count=0
    operation=PendingIntent{405d77e0: PendingIntentRecord{409b65e0 com.google.android.gsf broadcastIntent}}
  ELAPSED_WAKEUP #3: Alarm{408e0b58 type 2 de.avm.android.laborapp}
    type=2 when=+6m56s119ms repeatInterval=0 count=0
    operation=PendingIntent{4099b3f0: PendingIntentRecord{4094a1e8 de.avm.android.laborapp broadcastIntent}}
  ELAPSED_WAKEUP #2: Alarm{40a21b68 type 2 getjar.android.client}
    type=2 when=+6m23s400ms repeatInterval=600000 count=1
    operation=PendingIntent{408b0638: PendingIntentRecord{40a21af0 getjar.android.client startService}}
  ELAPSED_WAKEUP #1: Alarm{40b02f38 type 2 org.forcas.netstat}
    type=2 when=+45s45ms repeatInterval=120000 count=1
    operation=PendingIntent{40ac23b8: PendingIntentRecord{40a2bc38 org.forcas.netstat broadcastIntent}}
  ELAPSED_WAKEUP #0: Alarm{40a12ab0 type 2 de.avm.android.laborapp}
    type=2 when=+41s449ms repeatInterval=0 count=0
    operation=PendingIntent{40797118: PendingIntentRecord{40bba158 de.avm.android.laborapp broadcastIntent}}
  ELAPSED #3: Alarm{40a7a2c0 type 3 android}
    type=3 when=+30d13h45m57s978ms repeatInterval=0 count=0
    operation=PendingIntent{40829828: PendingIntentRecord{4086bd30 android broadcastIntent}}
  ELAPSED #2: Alarm{40a5f600 type 3 com.ebomike.ebobirthday}
    type=3 when=+58m44s416ms repeatInterval=0 count=0
    operation=PendingIntent{409620a8: PendingIntentRecord{40a3cd20 com.ebomike.ebobirthday startService}}
  ELAPSED #1: Alarm{40bde040 type 3 android}
    type=3 when=+6m48s126ms repeatInterval=0 count=0
    operation=PendingIntent{4088ee20: PendingIntentRecord{4086bc58 android broadcastIntent}}
  ELAPSED #0: Alarm{409ee130 type 3 ccc71.pmw.pro}
    type=3 when=+964ms repeatInterval=10000 count=1
    operation=PendingIntent{40be7bc0: PendingIntentRecord{40705900 ccc71.pmw.pro broadcastIntent}}
 
  Broadcast ref count: 0
 
  Alarm Stats:
  ccc71.pmw.pro
    66820ms running, 0 wakeups
    1427 alarms: flg=0x4
  ccc71.bmw.pro
    68780ms running, 2586 wakeups
    2586 alarms: flg=0x4
  android
    193673ms running, 99 wakeups
    1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
    2544 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
    256 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
    86 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
    1 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
    1 alarms: act=com.android.server.ThorottleManager.action.RESET flg=0x4
    12 alarms: act=com.android.internal.policy.impl.KeyguardViewMediator.DELAYED_KEYGUARD flg=0x4
  de.avm.android.laborapp
    1380ms running, 67 wakeups
    67 alarms: flg=0x4
  com.google.android.apps.maps
    989ms running, 85 wakeups
    85 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
  tv.dailyme.android
    581ms running, 44 wakeups
    44 alarms: flg=0x4 cmp=tv.dailyme.android/.util.download.DownloadService
  org.forcas.netstat
    52392ms running, 1302 wakeups
    1302 alarms: flg=0x4
  getjar.android.client
    2801ms running, 259 wakeups
    259 alarms: flg=0x4 cmp=getjar.android.client/.global.DoStatReceiver
  com.google.android.gsf
    7929ms running, 171 wakeups
    86 alarms: flg=0x4
    8 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
    77 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
  com.android.vending
    119ms running, 12 wakeups
    3 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.DailyHygiene
    9 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.ContentSyncService
  com.ebomike.ebobirthday
    765ms running, 0 wakeups
    1 alarms: dat=custom://144190064 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://93733139 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://32458777 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://18057403 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://46870974 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://3652773 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://10856123 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://140590043 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://21657426 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://72078163 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://90129065 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://75678207 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://68478103 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://100934060 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://79279000 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://126164095 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://97334034 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://136964376 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://50472017 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://86529016 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://133364133 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://39659122 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://147790087 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://64876017 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://28858526 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://129764113 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://151390113 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://122564081 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://104534229 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://61275992 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://108134289 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://82886009 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://14456146 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://115363961 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://118964053 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://52208 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://43259213 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://36059036 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://54072054 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://25257674 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://111735023 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://57672097 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
    1 alarms: dat=custom://7256099 flg=0x4 cmp=com.ebomike.ebobirthday/.EboBirthdayService
  com.android.providers.calendar
    451ms running, 1 wakeups
    1 alarms: act=com.android.providers.calendar.SCHEDULE_ALARM flg=0x4
  com.carl.tcpro
    15596ms running, 44 wakeups
    44 alarms: act=com.carl.tcpro.UPDATE_RUN flg=0x4
  com.lsdroid.cerberus
    11ms running, 1 wakeups
    1 alarms: act=com.google.android.c2dm.intent.REGISTER flg=0x4

From my little knowledge I would assume the first part is not important, but the Alarm Stats, and there this with most running time as "com.carl.tcpro" at the very end. But what I can do with this?

BTW: In this overnight test, most time the phone was in flight mode.

Thanks
 

ccs86

Senior Member
Nov 16, 2011
702
65
I'm in the same boat of trying to interpret mine, so I'm not an expert...

IMO, the most important part is the "Time Running", and nothing looks too bad in yours. Since everything is in ms, even that com.carl.tcpro only ran for 15 seconds.

Does anyone know how to reset the Alarm Manager log? Mine seems to be covering like 54 days.

Also, a breakdown of what some of the most important definitions are:

"RTC_WAKEUP"

"type"

RTC #X

ELAPSED_WAKEUP #X

ELAPSED #X

etc...



Thanks!
 

SayWhat10

Senior Member
Jun 27, 2010
2,676
204
40
Miami
www.msn.com
android.intent.action.TIME_TICK

what is that? in the above posted it showed 1,000 alarms

its that not high on mine, but pretty high

exactly what is android.intent.action.TIME_TICK ?
 

num1gever

Senior Member
Jun 5, 2011
95
8
just for everybody knowledge.
i've recently solved this problem on my sg2 aswell.
but for me the only thing that helped was flashing an old bootloader.
i was on the new ics bootloader until somehow i saw on my system info that my bootloader is unknown. i've also couldnt get the jig working, so i thought why not try to flash the old bootloader.
and yes!!!! finally the alarmManager is no longer on the toplist of BBS's partial wakelocks. and the phone is finally entering deepsleep mode whenever i turnoff the screen.
 

bene_

New member
Aug 5, 2008
4
0
Hey,

I also have problems with the alarmmanager. A month ago my phones battery was 65% after 3 days, today I'm lucky if I have enough battery left to do a phone call at the end of a day. The last few days I really read a lot about battery draining and I think it is the alarmmanager causing the problems.

The problem is, I have a Motorola Defy mini and this phone is not rootable to get the alarmmanagers dump: http://forum.xda-developers.com/showthread.php?t=1658568&page=11
So I have no idea how to solve the problems with my phone. Do you know what I could do?
 

ap1618

Senior Member
Connect your phone to a computer and run this:

Code:
adb shell dumpsys alarm > AlarmDump.txt

or download GScript lite and create the following script:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt

Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.

Im trying to do it through the terminal emulator per the second command, but get a permission denied error in the alarmdump.txt file... any idea why?
(samsung galxy S running CM9)
 

djuramutavi

New member
Nov 2, 2012
3
0
Connect your phone to a computer and run this:

Code:
adb shell dumpsys alarm > AlarmDump.txt

or download URL and create the following script:
Code:
cd /sdcard
dumpsys alarm > AlarmDump.txt

Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.

I executed adb shell dumpsys alarm > AlarmDump.txt, but i can't find AlarmDump.txt on root of my sdcard... What did I do wrong?? :confused:
 
Last edited:

sekosan

Senior Member
Apr 5, 2011
166
19
Torak
Can anybody help with this alarm dump:

Alarm Stats:
com.google.android.location
22ms running, 3 wakeups
3 alarms: act=com.google.android.location.ALARM_WAKEUP_LOCATOR flg=0x4
com.google.android.gsf
2899ms running, 141 wakeups
10 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
3 alarms: flg=0x4
5 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
123 alarms: flg=0x4 cmp=com.google.android.gsf/.checkin.EventLogService$Receiver
com.android.jrdfota
306ms running, 2 wakeups
2 alarms: act=com.android.jrdfota.TIME_NOTIFY_CHECK_VER flg=0x4
com.android.vending
592ms running, 23 wakeups
10 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.DailyHygiene
13 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.ContentSyncService
android
133548ms running, 217 wakeups
3 alarms: act=android.intent.action.DATE_CHANGED flg=0x30000004
879 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
209 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
2 alarms: act=android.app.backup.intent.INIT flg=0x4
187 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
6 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
19 alarms: act=android.app.backup.intent.RUN flg=0x40000004
3 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
com.mx.browser
3271ms running, 51 wakeups
51 alarms: act=com.mx.service.SYNC_MXFAV flg=0x4
com.google.android.apps.maps
275ms running, 5 wakeups
5 alarms: act=com.google.android.apps.maps.nlp.ALARM_WAKEUP_CACHE_UPDATER flg=0x4
com.vp.alarmClockPlusDock
443ms running, 2 wakeups
2 alarms: act=com.vp.alarmClockPlusDock.ALARM_ALERT flg=0x4
 

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    Connect your phone to a computer and run this:

    Code:
    adb shell dumpsys alarm > AlarmDump.txt

    or download GScript lite and create the following script:
    Code:
    cd /sdcard
    dumpsys alarm > AlarmDump.txt

    Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.
    6
    It can cause drain, but its not the AlarmManager in it self that is causing it, its the other apps that use it. Other apps use it to wake up on specific times or intervals, like if you have a weather widget that needs updating every 30 min or an application that checks your location every x min etc. Here are parts of my own AlarmManager dump and you might get the idea what I mean:

    Code:
      Alarm Stats:
      com.google.android.gsf
        20993ms running, 75 wakeups
        4 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
        42 alarms: flg=0x4
        29 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
    
      se.f1nally.snowstorm
        547ms running, 11 wakeups
        11 alarms: act=se.f1nally.yrvader.UPDATE_ALL flg=0x4 cmp=se.f1nally.snowstorm/.UpdateService
    
      com.mobitobi.android.gentlealarm
        2128ms running, 11 wakeups
        11 alarms: act=com.mobitobi.android.gentlealarm.ALARM_ALERT flg=0x4
    
      com.jb.gosms
        45ms running, 1 wakeups
        1 alarms: act=com.jb.schedule.private.box flg=0x4
    
      com.blizzard.bma
        2061402ms running, 0 wakeups
        2611 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
    
      android
        809072ms running, 281 wakeups
        1 alarms: act=android.intent.action.DATE_CHANGED flg=0x20000004
        9 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x4
        1138 alarms: act=android.intent.action.TIME_TICK flg=0x40000004
        123 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
        19 alarms: act=android.app.backup.intent.RUN flg=0x40000004
        80 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
        173 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
    
      com.liato.bankdroid
        443ms running, 6 wakeups
        6 alarms: flg=0x4 cmp=com.liato.bankdroid/.appwidget.AutoRefreshService
    
      com.google.android.apps.maps
        804ms running, 43 wakeups
        43 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService
    
      com.viber.voip
        164775ms running, 618 wakeups
        617 alarms: act=com.viber.voip.action.KEEP_ALIVE_RECEIVE flg=0x4
        1 alarms: act=com.viber.voip.action.VERSION_CHECK flg=0x4
    
      net.dinglisch.android.tasker
        14114ms running, 104 wakeups
        90 alarms: act=net.dinglisch.android.tasker.ANOFFCHECKORUM flg=0x4
        14 alarms: act=net.dinglisch.android.tasker.ALARUM flg=0x4
    
      de.devmil.minimaltext
        6619ms running, 0 wakeups
        64 alarms: act=updatetasker dat=minimaltextwidget://widget/id/updatetasker flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
        249 alarms: act=update dat=minimaltextwidget://widget/id/update flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
        59 alarms: act=forceupdate dat=minimaltextwidget://widget/id/forceupdate flg=0x4 cmp=de.devmil.minimaltext/.MinimalTextUpdateService
        3 alarms: act= dat=minimaltextwidget:/weather/ flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService
        3 alarms: act=ForceUpdate dat=minimaltextwidget:/weather/ForceUpdate flg=0x4 cmp=de.devmil.minimaltext/.weather.WeatherUpdateService
    
      org.koxx.pure_calendar
        29ms running, 5 wakeups
        5 alarms: act=org.koxx.pure_calendar.UPDATE_ALL flg=0x4 cmp=org.koxx.pure_calendar/.UpdateService
    
      com.bigtincan.android.adfree
        11231ms running, 1 wakeups
        1 alarms: flg=0x4

    It is part of the android os so thats why I dont think you can uninstall it. See this page for dev info on AlarmManager.
    3
    It is not really advisable to uninstall AlarmManager since it is used by a lot of applications and by android itself. Not sure you even can uninstall it.

    ANywas, getting that dump file I mentioned above will show you what app was causing the most wakeups, and then you can take actions from there.
    2
    Try installing startup cleaner 2 or similar to stop it starting at boot. Or uninstall it :p

    Sent from my Desire HD using XDA Premium App
    1
    Connect your phone to a computer and run this:

    Code:
    adb shell dumpsys alarm > AlarmDump.txt

    or download GScript lite and create the following script:
    Code:
    cd /sdcard
    dumpsys alarm > AlarmDump.txt

    Note that you probably need root access for the GScript to work. The AlarmDump.txt file will be on your sdcard root directory.

    where can i find the AlarmDump.txt on my computer?