So i know i might get some flak from Mr.Clown but since i have gotten 0 responses on my last post. I figure the only way to get the attention needed from the people i need attention from i have to post here in the general section.
So basically my phone, like many others, is having an issue with phone idle, well did some work and reading and looked into my alarm manager stats and found that a process is draining my battery and probably many others too.
If someone could please look at the log and tell me if they see anything that is draining my battery and keeping the phone awake.
Code:
Alarm Stats:
com.motorola.devicestatistics
2563ms running, 1 wakeups
1 alarms: act=com.motorola.devicestatistics.APP_STATS_ALARM flg=0x4
39 alarms: act=com.motorola.batterymanager.wlmonitor.CHECK_STATUS flg=0x4
19 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.gsf
4305ms running, 148 wakeups
79 alarms: flg=0x4
4 alarms: act=com.google.android.intent.action.GTALK_RECONNECT flg=0x4
65 alarms: act=com.google.android.intent.action.GTALK_HEARTBEAT flg=0x4
com.motorola.blur.service.storagemon
5408ms running, 0 wakeups
107 alarms: act=com.motorola.blur.service.blur.Actions.CHECK_STORAGE_USAGE f
lg=0x4
com.motorola.datacollection
2198ms running, 0 wakeups
40 alarms: act=com.motorola.datacollection.onehourtimer flg=0x4
com.android.vending
110ms running, 0 wakeups
[COLOR="Red"]4 alarms: act=com.android.vending.FORCE_UPDATE_CHECK flg=0x4
android
119954ms running, 316 wakeups
2 alarms: act=android.intent.action.DATE_CHANGED flg=0x4
1545 alarms: act=android.intent.action.TIME_TICK flg=0x40000004[/COLOR]
1 alarms: act=com.android.internal.location.ALARM_WAKEUP flg=0x4
2 alarms: act=com.motorola.wifi.MotWifiScan.action.CHANGE_SCAN_FREQ flg=0x4
212 alarms: act=com.android.server.ThrottleManager.action.POLL flg=0x4
1 alarms: act=android.appwidget.action.APPWIDGET_UPDATE flg=0x4
36 alarms: act=com.android.internal.policy.impl.PhoneWindowManager.DELAYED_K
EYGUARD flg=0x4
276 alarms: act=android.content.syncmanager.SYNC_ALARM flg=0x4
com.motorola.blur.datamanager.app
44ms running, 0 wakeups
2 alarms: act=com.motorola.blur.datamanager.app.checkin.timeout flg=0x4 cmp=
com.motorola.blur.datamanager.app/.DataManagerCheckinService
com.motorola.batterymanager
296ms running, 0 wakeups
1 alarms: act=android.intent.action.batteryprofile.CHK_ALRM flg=0x4
1 alarms: act=android.intent.action.batteryprofile.DATA_ALRM flg=0x4
4 alarms: act=android.intent.action.batteryprofile.DATA_CHECK flg=0x4
com.motorola.kpilogger
1109ms running, 0 wakeups
19 alarms: act=com.motorola.kpilogger.START_LOG flg=0x4
com.google.android.apps.maps
2942ms running, 137 wakeups
94 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.pre
fetch.android.PrefetcherService
43 alarms: flg=0x4 cmp=com.google.android.apps.maps/com.google.googlenav.fri
end.android.BackgroundFriendService
com.motorola.blur.service.blur
114ms running, 5 wakeups
5 alarms: act=com.motorola.blur.service.blur.pm.alarmintent flg=0x4
com.motorola.blur.service.search
199ms running, 0 wakeups
2 alarms: act=com.motorola.blur.service.search.SCHEDULED_INDEXING_ACTION flg
=0x4
com.motorola.blur.alarmclock
2092ms running, 2 wakeups
2 alarms: act=com.motorola.blur.alarmclock.ALARM_ALERT flg=0x4
#
I believe the problem to be some where in the red code i highlighted.
cheers for your help!!
I suffer from a lot of partial wakelocks caused by AlarmManager as well and I would be very interested in tracking down what is causing it.
What log is that you have posted?
krkeegan said:
I suffer from a lot of partial wakelocks caused by AlarmManager as well and I would be very interested in tracking down what is causing it.
What log is that you have posted?
Click to expand...
Click to collapse
Its the AlarmManager log itself.
You can either use terminal to view the log on your phone or use cmd on your pc.
get into adb shell and type "dumpsys alarm"
the "AlarmManager Stats" is about half way down....thats where you can see the count #, how many times its woken up the phone and for how long its been in use more or less as i understand it.
I KNOW that it is something in AlarmManager because when i use betterbatterystats and i go to wakelocks and i hit refresh....the number count for AlarmManager just keeps going up every time i hit refresh!!! which means something is using it all the time!!
I have the same problem. When I freeze it then I get error logger usage up. Any fix?
Sent from my MB860 using XDA Premium App
There is definitely an issue with my atrix staying awake. I leave it for 8 hours while I sleep, and the battery graph shows near solid awake time and no screen time. Its done this every since I bought it. Definitely some wakelock bug by a moto service or similar.
is this a problem only present in gingerbread? Or was it also present in froyo as well?
I've had battery drain problems since updating to 2.3.4 using different roms and kernels.. I hope something comes out of this
Sent from my MB860 using XDA App
I've had battery issues every since Apps were invented. I need 5 apps to check my battery and processes, 2 apps to freeze like 30 things that I have NO CLUE wth they are for or what they do. ... .. ... ... .. . .Does anypne know what com.android truesuite or something like that is for? I seem to always see its running.
so i flashed an ATT radio "1.77.30p" and although the AlarmManager is still running, i have so far better battery life. So the phone has been running for 6 hours now with the new radio flash, and im at 91% where as before at the run time i would have probably about 60% or less. Keep in mind this is with VERY light usage...all i have done in the past 6 hours is check the battery usage...yes phone idle is still high....but that IS because i have not really been using it, i checked betterbatterystats a few times, made a phone call or 2 for like a minute each and sent a few text's...oh and checked xda with the app a few times..thats it...very light usage but at least its not draining at break neck speeds like it usually does.
I am still determined to solve this AlarmManager problem though...still hoping that a dev or someone that knows what they'er looking for might pop into this thread..
*fingers crossed*
Thanks for the update J-Roc, I'll try the radio and report back.
Sent from my MB860 using XDA App
I too have a similar issue.
m0biusace - Not sure if it was present in Froyo, but the battery use summary that was introduced in Gingerbread is what made people aware of the issue.
Phoneguy589 - com.authentec.TrueSuiteMobile is needed for the finger scanner.
There is a related discussion on Atrix Forums, but as a new user I can't link to it. If someone wants to link it, the thread title is "Phone Awake vs. Sleep Time (Phone rarely sleeps when not in use)"
Summary of issues that I believe are related:
1) Phone nearly always shows as awake, even during long periods of display off
2) AlarmManager is constantly receiving calls - appears to be for system use
3) Logs show repeated errors for NetlinkEvent and Netlinklistener
So I flashed the 1.77.30p radio and it looks promissing! I charged up the phone 3 hours ago and let the phone idle. I'm now at 97% charge left... I would have been around 85% with the previous radio. I don't remember which radio I had previously.. 1.77.15 or something like that. We'll see tomorrow if it's for real.
Ya my idle is still high sitting at 75% BUT its now been running for 20 hours on battery with more on the moderate side of usage and im only at 65%, looks like the new radio is helping but I think it could be even better
Sent from my MB860 using XDA Premium App
Pinch & Jroc, is the alarmmanager still as active triggering the wakelocks? Does the phone sleep more if you look at the bars under the battery graph?
i think i am having a similar problem. This morning my phone was off the charger for 8 hours and went down to 55% battery with only 20 minutes of display on time. I also saw long periods of the phone being awake without the screen being on. Is this new radio fixing this problem? If so could someone link the thread with it? Thanks
ElQuixote said:
Pinch & Jroc, is the alarmmanager still as active triggering the wakelocks? Does the phone sleep more if you look at the bars under the battery graph?
Click to expand...
Click to collapse
Well it is still active and appears to be draining battery however "event log service" has entered the picture as the lead in battery drainage as far as wake locks are concerned. Alarm manager being at about 26% and event log at about 28% or so. Im not really sure what to make of this but the radio has definitely helped in battery drainage.
I will a link to the radio which is a CWM flashable file when I get home
Sent from my MB860 using XDA Premium App
I took the radio file from the Alien rom post in the dev section. There's a download link near the middle of the first post. This is the link:
http://briefmobile.com/alien#downloads
I was starting to think my battery was going bad but this radio finally fixed it.
Sent from my MB860 using XDA App
So here is the radio i am using v1.77.30P: http://www.multiupload.com/ICVTP3FRGC
My battery usage stats are weird i've noticed...i have been using games, internet, other apps and so on and the only things showing in there are phone idle, cell standby and display. Phone idle being the highest consumer at 64%...my phone has now been off the charger for 1 day 5 hours and im at 40% left.
Any fix yet? BTW - Pinch - I have a hunch that you are thesmokingandroid. am I right?
Lol, that's right kartik
Sent from my MB860 using XDA Premium App
Seems to me after much searching here and all over the internet I might be the only I9500 owner with this problem, but it's been driving me crazy and making my battery life just ridiculous. Posting in hopes someone might have seen it before.
Got the phone about a month ago, battery life was shorter than I expected from the start, but then it became so short I had to recharge mid morning if I wanted it to last until noon with moderate use. After installing BBS, I found out a massive GPS wakelock, which causes the phone to NEVER enter Deep Sleep after it first appears.
The only solutions I've found so far to stop the wakelock from happening are:
Toggle GPS off and Restart phone
Do a shut down and pull the battery
Use System Tuner Pro to kill GPSD, then kill most system apps
After doing any of those, the phone will enter deep sleep normally if the GPS is switched off. When it's switched on again, sometimes the problem will start again after minutes/hours, sometimes it won't. Something odd about it though, is that if I stay home, it won't happen (can't tell you how many times this has given me false hope the problem was fixed) but if I'm moving around commuting or staying still at any other place, it will randomly start wakelocking the device again.
So far I've done the following to try and fix it:
Flash a couple of different firmwares I got from SamMobile
Factory reset, flash again, factory reset
Flash Adam Kernel
Flash pre-rooted firmware again with a factory reset
Format everything, including /system sdcard and extSD, then flash yet another, different firmware
On the last format I just have the basic apps running, frozen the standard bloatware along with a google apps, yet the problem persists.
Could this be a hardware problem? If I use the GPS with Maps or Waze while the phone is deep sleeping normally, the phone continues to behave as it should, so it seems the GPS radio can be turned on and off without problem, at least while the screen is on.
Does anyone have any other ideas I can test? I don't want to completely disable GPS, that would defeat part of the reason of owning a smartphone, nor does it seem necesary as there are thousands of people using their phone with GPS on and no problems. I haven't used Logcat, but if someone knows what exactly I should be logging, I can search a quick tutorial and give it a go.
Posting here a short version of the BBS log and attaching the full file. For reference, this BBS log was taken from the moment I woke up and unplugged the phone (and it was deep sleeping normally) until mid morning after the problem had reappeared.
General Information
===================
BetterBatteryStats version: 1.14.0.0B2
Creation Date: 2013-08-13 11:11:32
Statistic Type: Unplugged to Current
Since 4 h 46 m 4 s
VERSION.RELEASE: 4.2.2
BRAND: samsung
DEVICE: ja3g
MANUFACTURER: samsung
MODEL: GT-I9500
OS.VERSION: 3.4.5-1133023
BOOTLOADER: I9500XWUBMG5
HARDWARE: universal5410
FINGERPRINT: samsung/ja3gxx/ja3g:4.2.2/JDQ39/I9500XWUBMG5:user/release-keys
ID: JDQ39
TAGS: release-keys
USER: dpi
PRODUCT: ja3gxx
RADIO: I9500ZCUCMF3
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -33% (100% to 67%) [6.9%/h]
Voltage lost [mV]: (4291-3915) [79.0%/h]
===========
Other Usage
===========
Deep Sleep (): 37 m 26 s (2246 s) Ratio: 13.1%
Awake (): 4 h 8 m 37 s (14917 s) Ratio: 86.9%
Screen On (): 25 m 4 s (1504 s) Ratio: 8.8%
Phone On (): 5 m 11 s (311 s) Ratio: 0.2%
Wifi On (): 4 h 46 m 4 s (17164 s) Ratio: 100.0%
Wifi Running (): 4 h 46 m 4 s (17164 s) Ratio: 100.0%
No Data Connection (): 4 h 3 s (14403 s) Ratio: 83.9%
No or Unknown Signal (): 4 h 3 s (14403 s) Ratio: 83.9%
Moderate Signal (): 5 m 47 s (347 s) Ratio: 0.2%
Good Signal (): 14 s (14 s) Ratio: 0.0%
Screen dark (): 6 m 2 s (362 s) Ratio: 2.1%
Screen dimmed (): 11 m 25 s (685 s) Ratio: 0.3%
Screen medium (): 7 m 35 s (455 s) Ratio: 0.2%
================
Kernel Wakelocks !!! wakeup_sources !!!
================
GPS (): 3 h 39 m 11 s (13151 s) Cntc/wc/ec)3/0/0 6.6%
l2_hsic (): 1 h 13 m 21 s (4401 s) Cntc/wc/ec)8634/4/8634 25.6%
PowerManagerService (): 38 m 38 s (2318 s) Cntc/wc/ec)816/2/0 13.5%
rpm_hsic (): 11 m 24 s (684 s) Cntc/wc/ec)8651/2/0 4.0%
wlan_rx_wake (): 9 m 46 s (586 s) Cntc/wc/ec)636/0/637 3.4%
BT_bt_wake (): 6 m 52 s (412 s) Cntc/wc/ec)60/0/60 0.2%
umts_ipc0 (): 6 m 26 s (386 s) Cntc/wc/ec)928/1/928 2.3%
ssp_wake_lock (): 3 m 31 s (211 s) Cntc/wc/ec)70/0/70 1.2%
BT_bt_wake (): 1 m 52 s (112 s) Cntc/wc/ec)141/0/141 0.1%
wlan_wd_wake (): 1 m 44 s (104 s) Cntc/wc/ec)2382/1/0 0.6%
wlan_ctrl_wake (): 1 m 22 s (82 s) Cntc/wc/ec)94/0/94 0.5%
rmnet0 (): 1 m 2 s (62 s) Cntc/wc/ec)66/0/66 0.4%
ssp_sensorhub_wake_lock (): 30 s (30 s) Cntc/wc/ec)67/0/67 0.2%
wlan_wake (): 18 s (18 s) Cntc/wc/ec)12310/1/0 0.1%
sec-battery-monitor (): 8 s (8 s) Cntc/wc/ec)525/2/0 0.0%
alarm (): 7 s (7 s) Cntc/wc/ec)602/2/0 0.0%
AudioOutLock (): 6 s (6 s) Cntc/wc/ec)9/0/0 0.0%
alarmtimer (): 4 s (4 s) Cntc/wc/ec)2/2/2 0.0%
battery (): 3 s (3 s) Cntc/wc/ec)525/2/0 0.0%
event11-2940 (): 1 s (1 s) Cntc/wc/ec)145/0/0 0.0%
PowerManagerService.Broadcasts (): 1 s (1 s) Cntc/wc/ec)8/0/0 0.0%
KeyEvents (): (0 s) Cntc/wc/ec)12150/2/0 0.0%
client-interface (): (0 s) Cntc/wc/ec)8549/0/0 0.0%
vib_present (): (0 s) Cntc/wc/ec)224/0/0 0.0%
event13-2940 (): (0 s) Cntc/wc/ec)46/0/0 0.0%
mmc2_detect (): (0 s) Cntc/wc/ec)35/2/0 0.0%
mmc0_detect (): (0 s) Cntc/wc/ec)35/2/0 0.0%
autosleep (): (0 s) Cntc/wc/ec)98/0/0 0.0%
======================
Alarms (requires root)
======================
android (): Wakeups: 69
Alarms: 0, Intent: android.intent.action.TIME_TICK
Alarms: 0, Intent: com.android.server.ThrottleManager.action.POLL
Alarms: 0, Intent: com.android.server.action.NETWORK_STATS_POLL
Alarms: 24, Intent: com.android.internal.policy.impl.Keyguard.LANDSCAPE_WAKE_TIME_LIMIT_EXPIRED
Alarms: 23, Intent: com.android.server.LightsService.action.UPDATE_SVC_LED
Alarms: 9, Intent: android.appwidget.action.APPWIDGET_UPDATE
Alarms: 4, Intent: com.android.internal.policy.impl.PhoneWindowManager.DELAYED_KEYGUARD
Alarms: 4, Intent: android.app.backup.intent.RUN
Alarms: 5, Intent: android.content.syncmanager.SYNC_ALARM
Alarms: 0, Intent: android.intent.action.DATE_CHANGED
Alarms: 0, Intent: edm.intent.action.elm.cleanrecords
Alarms: 0, Intent: android.net.wifi.DHCP_RENEW
Alarms: 0, Intent: com.android.server.action.UPDATE_TWILIGHT_STATE
Alarms: 0, Intent: com.android.server.NetworkTimeUpdateService.action.POLL
com.google.android.gsf (): Wakeups: 64
Alarms: 28, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 4, Intent: com.google.android.intent.action.MCS_HEARTBEAT
Alarms: 10, Intent: {com.google.android.gsf
Alarms: 22, Intent: com.google.android.intent.action.GTALK_RECONNECT
com.google.android.googlequicksearchbox (): Wakeups: 27
Alarms: 18, Intent: com.google.android.apps.sidekick.calendar.CalendarIntentService.UPDATE_CALENDAR_ACTION
Alarms: -33, Intent: {com.google.android.googlequicksearchbox
Alarms: 8, Intent: com.google.android.apps.sidekick.REFRESH
Alarms: -84, Intent: {com.google.android.googlequicksearchbox
Alarms: -100, Intent: {com.google.android.googlequicksearchbox
Alarms: 0, Intent: send_events
com.google.android.gms (): Wakeups: 27
Alarms: 27, Intent: com.google.android.intent.action.SEND_IDLE
Alarms: 0, Intent: com.google.android.gms.icing.INDEX_RECURRING_MAINTENANCE
com.nuance.swype.dtc (): Wakeups: 20
Alarms: 20, Intent: {com.nuance.swype.dtc
com.whatsapp (): Wakeups: 14
Alarms: 0, Intent: ALARM_ACTION
Alarms: 10, Intent: ALARM_AVAILABLE_TIMEOUT
Alarms: 0, Intent: ALARM_ROTATE_LOGS
Alarms: 0, Intent: ALARM_MESSAGES_DB_BACKUP
Alarms: 0, Intent: ALARM_REPORT_SYNCS
Alarms: 4, Intent: com.whatsapp.MessageService.RECONNECT
com.android.providers.calendar (): Wakeups: 12
Alarms: 12, Intent: com.android.providers.calendar.intent.CalendarProvider2
com.sec.chaton (): Wakeups: 12
Alarms: 12, Intent: com.sec.chaton.push.ALARM_TIMER_ACTION
com.sec.esdk.elm (): Wakeups: 4
Alarms: 4, Intent: com.sec.esdk.elm.service.ACTIVATION_DEACTIVATION_RETRY_INTENT
Alarms: 0, Intent: com.sec.esdk.elm.alarm.SAVE_APICALLLOG
com.android.vending (): Wakeups: 2
Alarms: -1, Intent: {com.android.vending
Alarms: -5, Intent: {com.android.vending
com.sec.android.app.clockpackage (): Wakeups: 2
Alarms: 1, Intent: com.samsung.sec.android.clockpackage.alarm.ALARM_ALERT
Alarms: 1, Intent: com.samsung.sec.android.clockpackage.alarm.NOTIFY_ALARM_LOCATION
Thanks for your help
Turn off gps if you don't need it. That's what I do and saves much power bro.
Sent from my GT-I9505 using xda premium
gee2012 said:
Turn off gps if you don't need it. That's what I do and saves much power bro.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
I do turn off any extra drain some days if I'm gonna be away from a charger most of the day, but any other day, when I'm at my office, I actually like all the features that require location and I've used them without any hassle on my GS3 and even on my old GS1 with a JB rom and my battery lasted me through a normal workday. The GS4 will drain itself overnight if the bug is happening and it's not charging. In contrast, my father's GS4 has everything on all the time, and even without Greenify, it will last an entire work day without recharging and with moderate use.
So clearly, there is something wrong with my phone. Sure, having the GPS toggle on means that apps on the background will occasionally wake up the phone, access fine location and go back to sleep, the problem is my phone never gets back to sleep.
Forgot to say on the main post: apps that force deep sleep when the screen is turned off are unable to do so after it's bugged.
Thanks!
Get this
https://play.google.com/store/apps/details?id=eu.chainfire.geolog
I've got it set for a custom profile that updates every 4 hours. Work 12 miles from home so weather is always the same.
When I need GPS for navigation I will bump it up to a more aggressive refresh.
Sent from my HTC One using xda premium
Are you only disabling GPS from the notification?
When you hold the GPS toggle and you are moved to the GPS settings, is it completely off or is access to my location-use wireless networks on?
That, as silly as it sounds, could be your problem.
Sent from my GT-I9500 using xda app-developers app
SchmilK said:
Get this
I've got it set for a custom profile that updates every 4 hours. Work 12 miles from home so weather is always the same.
When I need GPS for navigation I will bump it up to a more aggressive refresh.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Wow, that seems like a pretty good app for controlling location services drain without actually disabling them. I'll give it a go, though I think the problem with my phone might be at the hardware level. I'm pretty sure GPSD is the process that's getting stuck in some infinite loop, so the only workaround for now is to completely disable GPS until I can solve this. Thanks for the recomendation, that app is definitively going to my list of must haves :good:
mazroui said:
Are you only disabling GPS from the notification?
When you hold the GPS toggle and you are moved to the GPS settings, is it completely off or is access to my location-use wireless networks on?
That, as silly as it sounds, could be your problem.
Sent from my GT-I9500 using xda app-developers app
Click to expand...
Click to collapse
Well, as far as I can tell, it makes no difference, the bug happens with the wireless network location aid on or off. If you look at the BBS log, you can see the wakelock is caused not by any particular service accessing location data, but by the GPS itself (the kernel module GPSD as far as I can tell). And really, it should make no difference, in any normal phone, locations services wake up, update, go back to sleep. In my phone it's wake up>GPS gets stuck on and will continue to use CPU time until I kill it with any of the methods explained in the first post. Thanks!
sirius100 said:
Wow, that seems like a pretty good app for controlling location services drain without actually disabling them. I'll give it a go, though I think the problem with my phone might be at the hardware level. I'm pretty sure GPSD is the process that's getting stuck in some infinite loop, so the only workaround for now is to completely disable GPS until I can solve this. Thanks for the recomendation, that app is definitively going to my list of must haves :good:
Well, as far as I can tell, it makes no difference, the bug happens with the wireless network location aid on or off. If you look at the BBS log, you can see the wakelock is caused not by any particular service accessing location data, but by the GPS itself (the kernel module GPSD as far as I can tell). And really, it should make no difference, in any normal phone, locations services wake up, update, go back to sleep. In my phone it's wake up>GPS gets stuck on and will continue to use CPU time until I kill it with any of the methods explained in the first post. Thanks!
Click to expand...
Click to collapse
i've been thru gps wakelocks when i have it on and could only recommend a clear format n reload factory firmware with a PIT repartition to make sure nothing stays behind and check from there if the bug remains, i personally have my my location based apps off by default unless i need their service coz wakelocks only cause trouble... im trying to get help with my phoneapp wakelock getting 1-2 hours of wakelock on a 24 hour period with some random audioout as well
running wanamlite and perseus here with all the bloatware as some of those samsung apps are useful at times
gee2012 said:
Turn off gps if you don't need it. That's what I do and saves much power bro.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
I have never disabled gps from S1 through to S4 and in all those years have never seen gps consume battery. My gps only turns on when an app needs to use it.
But I do remember one in the S2 I did have this exact same problem. Can't really remember how I fixed it though. Possible I did a fresh flash in odin.
Edit: just wondering, have you enabled that new Android security feature 'Android device manager'? Maybe it's trying to locate your phone and won't let gps sleep.
mazroui said:
i've been thru gps wakelocks when i have it on and could only recommend a clear format n reload factory firmware with a PIT repartition to make sure nothing stays behind and check from there if the bug remains, i personally have my my location based apps off by default unless i need their service coz wakelocks only cause trouble... im trying to get help with my phoneapp wakelock getting 1-2 hours of wakelock on a 24 hour period with some random audioout as well
running wanamlite and perseus here with all the bloatware as some of those samsung apps are useful at times
Click to expand...
Click to collapse
I think I might have to do that, full format and repartitioning and see if it keeps doing that.
As for your problem, maybe you already use it, but I find System Tuner Pro a great tool for troubleshooting misbehaving apps.
sxi200 said:
I have never disabled gps from S1 through to S4 and in all those years have never seen gps consume battery. My gps only turns on when an app needs to use it.
But I do remember one in the S2 I did have this exact same problem. Can't really remember how I fixed it though. Possible I did a fresh flash in odin.
Edit: just wondering, have you enabled that new Android security feature 'Android device manager'? Maybe it's trying to locate your phone and won't let gps sleep.
Click to expand...
Click to collapse
With fresh flash you mean with PIT? I've disabled all google location services and it still happens. I've also actually used the Device Manager while the phone was in Deep Sleep, it woke up, used the GPS, then went back to sleep, so go figure. Is there anything I need to backup before repartitioning in case something goes wrong? Thanks!
sirius100 said:
With fresh flash you mean with PIT? I've disabled all google location services and it still happens. I've also actually used the Device Manager while the phone was in Deep Sleep, it woke up, used the GPS, then went back to sleep, so go figure. Is there anything I need to backup before repartitioning in case something goes wrong? Thanks!
Click to expand...
Click to collapse
Weird! As for flashing I'd recommend doing it without the PIT as it's a software / system problem, nothing to do with the partition of the phone.
Sent from my GT-I9505 using xda premium
sxi200 said:
Weird! As for flashing I'd recommend doing it without the PIT as it's a software / system problem, nothing to do with the partition of the phone.
Sent from my GT-I9505 using xda premium
Click to expand...
Click to collapse
Oh well in that case, I've done that at least 4 times, with different build dates and regions and even doing a full /system and /sdcard wipe along with the factory reset from CWR, then flashing, then another factory reset. So far, the problem pops up on every build no matter how little software I have installed.
That's what got me thinking it might be a hardware issue, but then again, I can use the GPS without any problem and then turn it off and the bug doesn't rear it's ugly head, so at least it seems the GPS radio is able to be shut down.
Most threads of people having this problem with different phones got as far as just doing a factory reset or flashing new firmware before it was solved, so when I'm at my 4th firmware flash, this problem is really busting my brain.
Having the same problem here. I have the I9500 with CyanogenMod. I started having the problem when Samsung updated to 4.4.2 now it doesn't matter which ROM I use, the problem persists...
Please let the GPS sleeping in stand by and stop destroying your phone for a different issue you may have!
this:
l2_hsic (): 1 h 13 m 21 s (4401 s) Cntc/wc/ec)8634/4/8634 25.6%
just switch and force your phone to 2G reception for a trial and this will stop consuming your battery.
it call "fast dormancy issue" and related to most of the time to the 3G provider that doesn't send the right info in order to stop the phone seeking for network.
I am not any kind of expert but this check is easy to do and will clarify this point.
partial solution
see my thread here:
http://forum.xda-developers.com/general/help/gpsd-keeping-phone-awake-time-t2846721
basically create shell scripts to start/stop the gpsd process
I'm having exact same problem with my Galaxy S5 SM-G900H exynos variant.
SchmilK said:
Get this
https://play.google.com/store/apps/details?id=eu.chainfire.geolog
Click to expand...
Click to collapse
Geolog is not a good idea to prevent wakelocks concerning GPS and/or com.google.android.gms.icing as the wakelocks caused by these two items are now caused by Geolog. After 3 hours sitting at the desk and not moving the phone, Geolog kept the phone awake for half an hour (27%). So this is NO solution for preventing wakelocks, saving battery or getting the phone asleep!
fipsy said:
Geolog is not a good idea to prevent wakelocks concerning GPS and/or com.google.android.gms.icing as the wakelocks caused by these two items are now caused by Geolog. After 3 hours sitting at the desk and not moving the phone, Geolog kept the phone awake for half an hour (27%). So this is NO solution for preventing wakelocks, saving battery or getting the phone asleep!
Click to expand...
Click to collapse
It worked in 2013....2016 is a different story and must be handled differently.
One thing that I just started doing on my Nexus 6P using "Device Only" mode rather than Battery Saving (battery saving uses wifi, bluetooth and cellular and requires more triangulation, checking in with google to see where it is, as well as more location tracking.)
One problem is that "device only" solely uses the GPS module of the phone which normally consumes quite much power. So this also is not a very preferable solution...
fipsy said:
One problem is that "device only" solely uses the GPS module of the phone which normally consumes quite much power. So this also is not a very preferable solution...
Click to expand...
Click to collapse
With no nap time changed and nothing else forcing things to sleep, I get 1.2%/hour battery drain while at work letting my phone idle.
I think things have changed and a simple GPS check uses less power because it gets your exact location. Compared to the cpu time of getting your ip address, referencing who owns it and where it is located or getting a cell tower and triangulation between other towers to figure out where you are.
Okay, thank you for the explanation! I'll give it a try hoping that this also works on Kitkat (CM11 / 4.4.4) ...
Edit: Tried it. A catastrophe! If I'm indoor where no GPS satellites are available it is constantly trying to fix a GPS position and hence consuming power.
My phone is barely getting 3 hours SOT now for some reason. I am running the Dynamic Kat ROM, rooted, with Greenify on pretty much everything I can, along with Xposed functionality. My alarmmanager has the most wakelocks, but for time of wakelocks in GSam I have TimaService and DHCP as well. Total CPU time for Android System is 37m 40s (99.9% of it is background), 2687 wakelocks. Kernel shows 35m 5s CPU time (all background) and 1h 35m keep awake. This is at 55% battery, 1 hour screen time, and 15 hours since the last charge.
Does anything stand out in the alarm dump?
Code:
Top Alarms:
+2m23s676ms running, 104 wakeups, 104 alarms: android
act=com.sec.epdg.epdg-conn-xfer
Alarm Stats:
com.gsamlabs.bbm +110ms running, 0 wakeups:
+110ms 0 wakes 2 alarms: cmp={com.gsamlabs.bbm/com.gsamlabs.bbm.lib.NotifyingService}
android +4m37s417ms running, 194 wakeups:
+2m23s676ms 104 wakes 104 alarms: act=com.sec.epdg.epdg-conn-xfer
+2m0s374ms 0 wakes 420 alarms: act=android.intent.action.TIME_TICK
+27s967ms 0 wakes 15 alarms: act=com.android.server.action.NETWORK_STATS_POLL
+10s528ms 77 wakes 77 alarms: act=android.content.syncmanager.SYNC_ALARM
+2s878ms 7 wakes 7 alarms: act=android.app.backup.intent.RUN
+1s327ms 0 wakes 12 alarms: act=com.android.server.LightsService.action.UPDATE_SVC_LED
+191ms 5 wakes 5 alarms: act=android.net.wifi.DHCP_RENEW
+25ms 1 wakes 1 alarms: act=com.sec.epdg.RETRY_TIMER_EXPIREDIMS
+3ms 0 wakes 1 alarms: act=android.net.ConnectivityService.action.PKT_CNT_SAMPLE_INTERVAL_ELAPSED
com.outlook.Z7 +18s546ms running, 12 wakeups:
+16s605ms 1 wakes 1 alarms: act=com.outlook.Z7.client.EasSettingSync1
+1s794ms 9 wakes 9 alarms: act=com.outlook.Z7.service.InactivityAlarm
+147ms 2 wakes 2 alarms: act=com.comscore.applications.KeepAliveAlarmReceiver.Outlook.com
com.oasisfeng.greenify +1s50ms running, 34 wakeups:
+1s20ms 34 wakes 34 alarms: act=com.oasisfeng.greenify.CLEAN_NOW cmp={com.oasisfeng.greenify/com.oasisfeng.greenify.CleanerService}
+30ms 0 wakes 1 alarms: cmp={com.oasisfeng.greenify/com.oasisfeng.greenify.CleanerService}
com.sec.android.daemonapp +309ms running, 0 wakeups:
+309ms 0 wakes 1 alarms: act=com.sec.android.widgetapp.ap.accuweatherdaemon.action.AUTOREFRESH
com.android.phone +32s354ms running, 311 wakeups:
+14s372ms 282 wakes 282 alarms: act=com.android.internal.telephony.dataconnection.DataConnection.DC-1.action_retry
+9s251ms 0 wakes 2 alarms: act=com.android.phone.UPDATE_CALLER_INFO_CACHE cmp={com.android.phone/com.android.phone.CallerInfoCacheUpdateReceiver}
+7s743ms 0 wakes 4 alarms: act=com.android.internal.telephony.data-stall
+1s15ms 29 wakes 29 alarms: act=com.android.internal.telephony.dataconnection.DataConnection.DC-2.action_retry
com.samsung.android.providers.context +12ms running, 1 wakeups:
+12ms 1 wakes 1 alarms: act=com.samsung.android.provider.context.action.EXECUTE_TASK cmp={com.samsung.android.providers.context/com.samsung.android.providers.context.TaskScheduler$TaskAlarmReceiver}
com.google.android.gsf +27s560ms running, 164 wakeups:
+15s631ms 64 wakes 64 alarms: act=com.google.android.intent.action.MCS_HEARTBEAT
+9s700ms 45 wakes 45 alarms: act=com.google.android.intent.action.SEND_IDLE
+2s742ms 55 wakes 55 alarms: act=com.google.android.intent.action.GTALK_RECONNECT
com.google.android.googlequicksearchbox +44ms running, 1 wakeups:
+28ms 1 wakes 1 alarms: cmp={com.google.android.googlequicksearchbox/com.google.android.velvet.VelvetBackgroundTasksImpl$Service}
+16ms 0 wakes 1 alarms: act=android.appwidget.action.APPWIDGET_UPDATE cmp={com.google.android.googlequicksearchbox/com.google.android.apps.sidekick.widget.PredictiveCardsWidgetProvider}
com.android.vending +594ms running, 3 wakeups:
+566ms 2 wakes 2 alarms: cmp={com.android.vending/com.google.android.finsky.services.ContentSyncService}
+28ms 1 wakes 1 alarms: cmp={com.android.vending/com.google.android.finsky.services.DailyHygiene}
com.android.providers.calendar +35s802ms running, 108 wakeups:
+35s802ms 108 wakes 108 alarms: act=com.android.providers.calendar.intent.CalendarProvider2
com.sec.android.app.sysscope +1ms running, 0 wakeups:
+1ms 0 wakes 1 alarms: act=com.sec.intent.action.SYSSCOPE
com.sec.spp.push +103ms running, 2 wakeups:
+61ms 1 wakes 1 alarms: act=com.sec.spp.push.ACTION_SEND_PING_MESSAGE cmp={com.sec.spp.push/com.sec.spp.push.heartbeat.HeartBeat}
+42ms 1 wakes 1 alarms: act=com.sec.spp.push.DAY_TIMER
com.google.android.gms +1m46s111ms running, 541 wakeups:
+45s464ms 0 wakes 387 alarms: cmp={com.google.android.gms/com.google.android.gms.lockbox.LockboxAlarmReceiver}
+39s570ms 252 wakes 252 alarms: act=com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVITY_DETECTION
+21s631ms 57 wakes 57 alarms: act=com.google.android.gms.nlp.ALARM_WAKEUP_LOCATOR
+18s782ms 95 wakes 95 alarms: act=com.google.android.intent.action.MCS_HEARTBEAT
+13s413ms 33 wakes 33 alarms: act=com.google.android.intent.action.GCM_RECONNECT
+9s39ms 48 wakes 48 alarms: act=com.google.android.intent.action.SEND_IDLE
+2s291ms 15 wakes 15 alarms: cmp={com.google.android.gms/com.google.android.gms.checkin.EventLogService$Receiver}
+878ms 16 wakes 16 alarms: act=ALARM_WAKEUP288811013
+854ms 12 wakes 12 alarms: cmp={com.google.android.gms/com.google.android.libraries.social.mediamonitor.MediaMonitorIntentService}
+146ms 5 wakes 5 alarms: act=com.google.android.gms.nlp.ALARM_WAKEUP_SENSOR_UPLOADER
+143ms 1 wakes 1 alarms: act=com.google.android.gms.flp.BATCH_FLUSH
+119ms 3 wakes 3 alarms: act=com.google.android.gms.nlp.ALARM_WAKEUP_S_COLLECTOR
+101ms 1 wakes 1 alarms: act=com.google.android.gms.gcm.ACTION_CHECK_QUEUE
+87ms 1 wakes 1 alarms: act=com.google.android.gms.nlp.ALARM_WAKEUP_ACTIVE_COLLECTOR
+66ms 1 wakes 1 alarms: act=com.google.android.gms.recovery.WAKEUP
+28ms 0 wakes 1 alarms: act=com.google.android.gms.common.receiver.LOG_CORE_ANALYTICS cmp={com.google.android.gms/com.google.android.gms.common.receiver.InternalBroadcastReceiver}
+4ms 1 wakes 1 alarms: cmp={com.google.android.gms/com.google.android.gms.analytics.internal.PlayLogReportingService}
com.google.android.inputmethod.latin +1s46ms running, 0 wakeups:
+1s46ms 0 wakes 7 alarms: act=com.android.inputmethod.latin.personalization.DICT_DECAY cmp={com.google.android.inputmethod.latin/com.android.inputmethod.latin.personalization.DictionaryDecayBroadcastReciever}
Same problem, and I'm 100% stock lollipop. Do you have a snap or exynos?
Sent from my SM-N910C
fedecape said:
Same problem, and I'm 100% stock lollipop. Do you have a snap or exynos?
Sent from my SM-N910C
Click to expand...
Click to collapse
im on stock lolli with a custom kernel greenify donation so everything is hibernated.. when i go to bed i have around 3 hours of SOT and i got something like 40% battery left.. idk if this is good or bad
Racinghart91 said:
im on stock lolli with a custom kernel greenify donation so everything is hibernated.. when i go to bed i have around 3 hours of SOT and i got something like 40% battery left.. idk if this is good or bad
Click to expand...
Click to collapse
Better than mine, for sure. Are you usually on WiFi? What's your usage?
Sent from my SM-N910C
fedecape said:
Better than mine, for sure. Are you usually on WiFi? What's your usage?
Sent from my SM-N910C
Click to expand...
Click to collapse
No I am only on wifi at home and thats only in the evening after work. I got to say with brightness on max the sot is around 2 hours at 40 / left.
Use greenify it really works
And disable bloatware you don't need in the app settings menu.
Sent from my SM-N910F using XDA Free mobile app
I would recommend use amplify.
ButI also want to know about com.google.android.gms.flp.BATCH_FLUSH, theres nothing about it on the internet !