Join now - be part of our community!

Wake locks issue

SOLVED
clinta12
Visitor

Wake locks issue

here are screen shots of my phone kept over two seperate nights.

The first screen shot is keeping wifi off for whole night,my phone doesnt sleep properly. On the other hand when i keep the wifi on the wake locks seem less.Is this a possible bug in ics as i am not the only one facing this problem. Also what are the possible solution for it . I hope sony fixes this issue in the next update.

Screenshot_1.pngScreenshot_2.png

21 REPLIES 21
jonumbah01
Visitor

Yeah me too. My XSL is also like this. Screen is off but is awake:smileyconfused:

berserkk
Visitor

clinta12:

change view from partial wake locks to "alarms"

tap "alarm manger" app in better battery stats it will give you more details of what was causing it.

probably you will find it is com.sonyericsson.android.wakeup > com.sonyericsson.android.wakeup.FastDormancyWakeupServer

you can also see this by doing

adb shell dumpsys alarm > AlarmDump.txt

and viewing at the bottom " Alarm Stats:"

here is mine: (sorry i cant seem to format it with line endings intact)

Current Alarm Manager state:

  Realtime wakeup (now=2012-10-13 23:08:42):

..... removed.....

  Elapsed realtime wakeup (now=+10h56m33s872ms):

  .....

  removed

  .....

  Broadcast ref count: 0

  Alarm Stats:

  com.google.android.location

    16ms running, 2 wakeups

    2 alarms: act=com.google.android.location.ALARM_WAKEUP_LOCATOR flg=0x14

  android

    150060ms running, 117 wakeups

    6 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD flg=0x14

    580 alarms: act=android.intent.action.TIME_TICK flg=0x40000014

    22 alarms: act=com.android.server.action.NETWORK_STATS_POLL flg=0x14

    63 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x14

    10 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x14

    11 alarms: act=android.app.backup.intent.RUN flg=0x40000014

    90 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x14

  com.sonyericsson.extras.liveware

    249ms running, 1 wakeups

    1 alarms: act=com.sonyericsson.extras.TIME_INITIATOR flg=0x4 cmp=com.sonyericsson.extras.liveware/.asf.TimeService

  com.sonyericsson.androidapp.smart

    483ms running, 0 wakeups

    8 alarms: act=com.sonyericsson.androidapp.smart.action.TRIGGER_CALL_LOG_CHECK flg=0x14

  com.android.phone

    14084ms running, 1 wakeups

    180 alarms: act=com.android.internal.telephony.gprs-data-stall flg=0x14

    1 alarms: act=com.android.internal.telephony.gprs-reconnect.0 flg=0x14

  com.facebook.katana

    13938ms running, 5 wakeups

    3 alarms: flg=0x14

    1 alarms: act=com.facebook.katana.service.19 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    1 alarms: dat=fbservice:/fgbg/background_idle flg=0x4 cmp=com.facebook.katana/.service.BackgroundDetectionService

    2 alarms: act=Orca.KEEP_ALIVE flg=0x4 cmp=com.facebook.katana/com.facebook.orca.push.mqtt.MqttPushService

    1 alarms: dat=fbservice:/fgbg/pause flg=0x4 cmp=com.facebook.katana/.service.BackgroundDetectionService

    3 alarms: act=com.facebook.katana.service.12 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    2 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.22 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    1 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.17 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    1 alarms: act=com.facebook.katana.service.8 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    225 alarms: act=com.facebook.katana.service.5 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    2 alarms: act=com.facebook.katana.service.4 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    5 alarms: act=com.facebook.katana.service.7 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    1 alarms: act=com.facebook.katana.service.21 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    5 alarms: act=com.facebook.katana.service.6 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

    2 alarms: act=com.facebook.katana.service.3 flg=0x4 cmp=com.facebook.katana/.service.FacebookService

  com.google.android.apps.plus

    3042ms running, 46 wakeups

    10 alarms: act=com.google.android.apps.plus.content.cleanup flg=0x4 cmp=com.google.android.apps.plus/.service.EsService

    16 alarms: act=com.google.android.apps.plus.content.sync flg=0x4 cmp=com.google.android.apps.plus/.service.EsService

    20 alarms: act=com.google.android.apps.plus.NEW_PICTURE flg=0x14

  com.alfray.timeriffic

    850ms running, 2 wakeups

    2 alarms: act=com.rdrrlabs.intent.action.APPLY_STATE flg=0x14

  com.sonyericsson.illumination.service

    29ms running, 5 wakeups

    5 alarms: act=com.sonyericsson.illumination.intent.action.STOP_BUTTON_2 flg=0x4 cmp=com.sonyericsson.illumination.service/.IlluminationService

  com.android.vending

    57ms running, 3 wakeups

    2 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.DailyHygiene

    1 alarms: flg=0x4 cmp=com.android.vending/com.google.android.finsky.services.ContentSyncService

  au.com.weatherzone.android.weatherzoneplus

    42840ms running, 0 wakeups

    2 alarms: act=au.com.weatherzone.android.weatherzoneplus.action.update_data dat=content://au.com.weatherzone.android.weatherzoneplus/retry_data flg=0x14

    10 alarms: act=au.com.weatherzone.android.weatherzoneplus.action.update_data dat=content://au.com.weatherzone.android.weatherzoneplus/update_data flg=0x14

    573 alarms: act=au.com.weatherzone.android.weatherzoneplus.action.update_clock dat=content://au.com.weatherzone.android.weatherzoneplus/update_clock flg=0x14

  com.android.providers.calendar

    23546ms running, 16 wakeups

    4 alarms: act=com.android.providers.calendar.SCHEDULE_ALARM flg=0x14

    1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1350109200000 flg=0x14

    1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1350096600000 flg=0x14

    1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1350126000000 flg=0x14

    8 alarms: act=com.android.providers.calendar.intent.CalendarProvider2 flg=0x14

    1 alarms: act=android.intent.action.EVENT_REMINDER dat=content://com.android.calendar/1350113400000 flg=0x14

  com.sonyericsson.hdmi.controlservice

    650ms running, 33 wakeups

    33 alarms: act=interval flg=0x4 cmp=com.sonyericsson.hdmi.controlservice/com.sonyericsson.tvout.TvOutControlService

  com.Ink.Android.MobileQuotaPlus

    77ms running, 2 wakeups

    2 alarms: act=org.Ink.Android.MobileQuota.UPDATE flg=0x4 cmp=com.Ink.Android.MobileQuotaPlus/com.Ink.Android.MobileQuotaLib.Service.UpdateService

  com.google.android.gm

    723ms running, 0 wakeups

    7 alarms: act=com.google.android.gm.intent.provider.INDEX_MESSAGE_CONTENT dat...removed...

  com.sonyericsson.android.wakeup

    91763ms running, 2397 wakeups

    2397 alarms: act=com.sonyericsson.android.wakeup.FastDormancyWakeupServer flg=0x14

  com.android.calendar

    1453ms running, 0 wakeups

    5 alarms: act=com.android.calendar.APPWIDGET_SCHEDULED_UPDATE dat=content://com.android.calendar typ=vnd.android.data/update flg=0x14

  com.zynga.scramble.paid

    6148ms running, 104 wakeups

    104 alarms: flg=0x14

  com.google.android.apps.maps

    1215ms running, 13 wakeups

    13 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.prefetch.android.PrefetcherService

  com.sonyericsson.secureclockservice

    11ms running, 1 wakeups

    1 alarms: act=com.sonyericsson.secureclockservice.UPDATE_TIME flg=0x4

  com.sonyericsson.updatecenter

    234ms running, 0 wakeups

    1 alarms: act=com.sonyericsson.updatecenter.scheduler.Scheduler.START flg=0x4

    1 alarms: act=com.sonyericsson.updatecenter.tracking.TrackingService.START flg=0x4

    1 alarms: act=com.sonyericsson.updatecenter.UpdateCenterService.START_SERVICE flg=0x4

  com.nuance.swype.input

    19ms running, 0 wakeups

    2 alarms: flg=0x4 cmp=com.nuance.swype.input/com.nuance.swype.connect.ConnectClient

  com.google.android.gsf

    12357ms running, 82 wakeups

    23 alarms: flg=0x14

    21 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x14

    10 alarms: act=com.google.android.intent.action.MCS_HEARTBEAT flg=0x14

    28 alarms: act=com.google.android.intent.action.SEND_IDLE flg=0x14

  com.amazon.venezia

    1144ms running, 10 wakeups

    10 alarms: act=com.amazon.mas.client.framework.UpdateService.EXECUTE_RECURRING_TASKS flg=0x4 cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService

  com.ebay.mobile

    643ms running, 2 wakeups

    2 alarms: act=com.ebay.mobile.service.POLL_SAVED_SEARCH flg=0x14

  com.lsdroid.cerberus

    137ms running, 1 wakeups

    1 alarms: act=com.google.android.c2dm.intent.REGISTER flg=0x4

  com.sonyericsson.devicemonitor

    1263ms running, 0 wakeups

    10 alarms: act=com.sonyericsson.devicemonitor.TICK flg=0x4 cmp=com.sonyericsson.devicemonitor/.DeviceMonitorService

notice com.sonyericsson.android.wakeup.FastDormancyWakeupServer has 2397 alarms/wakeups

this is causing the battery drain on my system

Message was edited by: berserkk

sbkhbk
Visitor

Hello berserkk,

To check what exactly is causing the wake locks, its mandatory to ROOT the phone.

Is it possible to check for the wake locks causing apps without Rooting ?

berserkk
Visitor

you can try the adb command to see wakelock information

adb shell dumpsys alarm > AlarmDump.txt

i dont believe you need root for this

sbkhbk
Visitor

I actually tried the command which you are talking about. Notepad file was created with a line stating No Access. From that i understand that Root access is required to know the info..

clinta12
Visitor

@berserkk

as i am not rooted i cant access the alarm tab.

after installing gsam battery monitor app i found that services like google bookmark sync,contact sync are causing the most wake locks. Even when i try to disable these services they still cause wakelocks  which drains the battery.Whats more annoying is that after every reboot there is a new service causing wakelocks.

If possible install gsam battery monitor app. It will tell you what services exactly are causing the wakelocks.

sbkhbk
Visitor

You are right clinta12

I have installed GSam battery monitor since long time ago, but never explored it properly, i found that there is an option to check for the services with numb of wake locks.. when i look into it i see lots of google contact sync causing wakelocks and its really huge!!! and its traces are not shown at all in the default Battery indicator!!

orablue8
Visitor

strange!

on my XS, i notice that com.sonyericsson.android.wakeup is still running even after i have disabled it in  Apps->All. i did rebooted the phone after disabling com.sonyericsson.android.wakeup

using adb shell dumpsys, there is a process id for ...android.wakeup. 

maybe disable feature is not working correctly.

th0r
Visitor

Same problem, but with Xperia V. Is this bug fixed?

Sea2605_gmail_c
Visitor

My Xperia Z (.253 latest firmware, latest updates of all apps) has the same issue since I bought it. Even in two-three fw-updates this issue wasn't solved... another thread even shows that this issue exists for at least a year...

This wifistatemachine - bug is hughly draining battery ( minus 1,5 h of screenon-time ). Tested with several fw, rooted and unrooted, stock and custom roms, stock and custom kernel, ...

This is definitly not a issue that should be neglected... wifi off during screen off shouldn't consume more battery life then leaving wifi on all the time...! Shoudn't be neglected and moreover: should have been solved a long time ago!