My phone (Moto G running stock Android 4.4.2 rooted) NEVER ever gets into deep sleep because of these two deadlocks: GCM_CONN_ALARM and GCM_CONN.
I tried blocking them using Wakelock Terminator (either in Google Play Services or in Android System) but it doesn't seem to do anything at all, either with the keyword filter or the total filter.
The wakelocks only stopped when I disabled GcmService (using the Disable Service app), but now I don't get many notifications (Gmail, Twitter, WhatsApp).
Is there any solution in between? Thanks in advance.
santiagoroza said:
My phone (Moto G running stock Android 4.4.2 rooted) NEVER ever gets into deep sleep because of these two deadlocks: GCM_CONN_ALARM and GCM_CONN.
I tried blocking them using Wakelock Terminator (either in Google Play Services or in Android System) but it doesn't seem to do anything at all, either with the keyword filter or the total filter.
The wakelocks only stopped when I disabled GcmService (using the Disable Service app), but now I don't get many notifications (Gmail, Twitter, WhatsApp).
Is there any solution in between? Thanks in advance.
Click to expand...
Click to collapse
Why do you need to go in deep sleep you will miss notifications in deep sleep
I have the same wakelock on my Moto X. IS KILLING"my battery. . Anyone got any ideas. .
gsusx said:
I have the same wakelock on my Moto X. IS KILLING"my battery. . Anyone got any ideas. .
Click to expand...
Click to collapse
Start uninstalling things like FB, whatsapp, viber, Twitter and so everything that may want to sync periodically.
See if you can filter out what is actually keeping the given service active, thus keeping your device awake.
As a last resort, factory reset and start over.
This popped up for me after using my alarm clock. Even after turning off the alarm, it still appears. Did you ever resolve the issue?
Nobody has a between solution? Not disabling it nor allowing it to hog our batteries..
santiagoroza said:
My phone (Moto G running stock Android 4.4.2 rooted) NEVER ever gets into deep sleep because of these two deadlocks: GCM_CONN_ALARM and GCM_CONN.
I tried blocking them using Wakelock Terminator (either in Google Play Services or in Android System) but it doesn't seem to do anything at all, either with the keyword filter or the total filter.
The wakelocks only stopped when I disabled GcmService (using the Disable Service app), but now I don't get many notifications (Gmail, Twitter, WhatsApp).
Is there any solution in between? Thanks in advance.
Click to expand...
Click to collapse
Use Greenify in Boost mode (works with xposed)
Have you solved the problem? I'm also struggling with that wake-lock.
Use greenify and amplify with xposed framework that would reduce the battery consumption and with amplify you can control wakelocks.
Related
anyone have any idea how to reduce this wake lock, have about 1hr + of this wakelock during my sleep
Try turning off, freezing, hangouts and see if it goes away. Just an educated guess. I think it's caused by hangouts syncing
Some good info here: http://forum.xda-developers.com/showthread.php?t=1811365
auggie246 said:
anyone have any idea how to reduce this wake lock, have about 1hr + of this wakelock during my sleep
Click to expand...
Click to collapse
I'm also experiencing this problem. I've tried disabling many Google apps (including hangouts) and disabling Google Play Services that were always running but nothing works. All I know is that it's related to mobile data (It goes away on WIFI, airplane mode or simply turning data off) and that it's not caused by a third party app (Safe mode doesn't help either). Did you ever foind a solution for this?, please let me know. I'm getting real sick of this and I'm considering installing CM or downgrading to 5.0.1, which worked perfectly.
Greetings,
After going through many forums trying to find a solution for these Wakelocks, all I found was switching off Location or Google Location History to get rid of RILJ and using Amplify to increase the interval of Nlp.
However, Turning off location or GLH is not a practical solution for me, and Amplify is not that easy to work with, so I was back to square one.
I found out that Nlp Wakelocks are associated with Google Play Services, Google Services Framework. RILJ is associated with Phone (Telephony) functions.
*The solution:
An Xposed module called (No Wakelock) in the Play Store that is capable of controlling Partial and Full WLs, aligning alarms and controlling sync for the selected apps, including system apps with the donation package.
*The results:
After disabling Partial/Full Wakelocks and enabling Aligning alarms for the aforementioned apps, Location and GLH are On.
They are no longer showing in BBS or WLD. AT ALL.**
Android Device Manager is capable of locating my phone.
SMS/Phone calls are working Fine.
No Frozen Screen, SoD, etc.
Gmail sync is delayed a few hours/minutes, without changing its settings in the module.
** Since everything is working perfectly fine even though these WLs are not showing at all, then what is the Real purpose of having them working in excess like that?
Kindly note that I'm not affiliated with the module or the developer in anyway.
If you would like to use it, please use common sense and do it at your own risk.
Cheers.
What did you disable?
I'd like to know that too
do you have fix for nougat? i use forcedoze and it works well with every service. But google services still trigger wakelock and drain my battery.
However, this problem had a temporary fix, if i switch on battery saver. this problem will stay away for awhile.
But i don't like this kind of method.
im also interesting how to fix it in Nougat
Android 5.1 stock rom, everything is up-to-date.
Yesterday, before to go to bed I've done the following:
I turned off wifi, set the phone to plane mode and activated the power save under the battery settings (which should reduce a lot of things). Before to lock the screen my battery was at 57 %. After 8 hour my battery was at 44 %.
Thanks to "BetterBatteryStats" - BBS - I've found, under the "Alarms" section, that the process com.google.android.gms was reported to be active at 56 %.
I am sure that I don't have other WakeLocks, firstly because no Wake Locks are reported by BBS - and the deep sleep is correctly reported also by BBS, and secondly because the phone is only awake when the screen is on:
I ask to myself: why Google Play Store remains active when there is no active connection on my phone, and when the sync is disabled? Furthermore, under the wifi option I also disabled the option wifi scan always available.
I think I'm on the right way to solve this issue. I've done some research and I installed "Disable Service" from the playstore.
First of all, please keep in mind that I use just few Google Apps: Gmail, Google App (to use the vocal assistant) and the Play Store. With the following changes all these apps still work without issues (at least for now).
last night i left my phone in standby as yesterday (plane mode, wifi turned off and powersave activate): for 8 hours is always stayed at 91 % of charge
Here the services of which I got rid:
LockScreenService
BackupTransport
Googlelocationservice
GoogleLocationManagerService
GcmService
These four services were always active as background processes on my phone.
Then, using Gemini App Manager, I went to Google Play Services, and by going under "AppOps" I turned off the "Wake Lock" authorization.
Furthermore, I also disabled other services related to G apps which I don't use:
com.google.android.gms.drive.api.DriveAsyncService com.google.android.gms.fitness.sync.FitnessSyncAdapterService
com.google.android.gms.games.service.GamesSyncServiceMain
com.google.android.gms.games.service.GamesSyncServiceNotification
com.google.android.gms.drive.metadata.sync.syncadapter.MetadataSyncService
com.google.android.gms.plus.service.OfflineActionSyncAdapterService
com.google.android.location.reporting.service.ReportingSyncService
com.google.android.gms.kids.restrictions.sync.RestrictionsSyncService
com.google.android.gms.drive.metadata.sync.syncadapter.SyncAdapterService
com.google.android.gms.subscribedfeeds.SyncService com.google.android.gms.kids.timeouts.sync.TimeoutsSyncService
com.google.android.gms.fitness.wearables.WearableSyncService
and all services related to Google Drive.
But the above section i'm not sure which is useful, since I never seen these services active on my phone, also because I uninstalled a lot of g-apps (Drive, Games, Plus, Books, News, Music).
I will keep updated this discussion when/if I will encounter some trouble (eg I want to test Google Maps and the GPS).
Dude i got the same problem!! But i play quite a lot with my Mi4c so i sould care what i'm going to stop!
This thing is really annoying anyway :/
How did you uninstall them my ex synced our phones plus added things to spy but its not even letting me forcestop some of them what he has added and is remote using or bridgung....has able to see everything text messages phone calls my pictures everything. ..HELP PLEASE HELP
Insanely high alarms by "com.google.android.location.ALARM_WAKEUP_ACTIVITY _DETECTION"
Hi there, I've been using OOS 9.0.2 and I got some excessive wakelocks by *walarm*:com.google.android.location.ALARM_WAKEUP_ACTIVITY_DETECTION which happens about every 60 seconds. I'm not sure if this is normal or what the culprit could be as the location services are deactivated all the time, yet it occurs. Any idea what it could be? Can it be related to Android Wear?
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Macusercom said:
UPDATE: It appears that Sleep as Android is causing it even when not using the app. I've contacted them now. For me the options are using Greenify during the day for the app, uninstalling it or ignoring it for now.
Click to expand...
Click to collapse
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
spartan268 said:
How did you figure that one out? Just curious. Maybe the next person can use the same tools or methods
Click to expand...
Click to collapse
I wish I could say I simply used a wakelock detector or something like that. I loaded my apps to a secondary device and disabled them one by one. I wasn't sure whether Greenify would prevent it but it did. So greenifying different apps and see if it changes was how I figured it out.
My battery consumption during standby went significantly down. Even though alarms are just the triggers and not the wakelocks, triggering the Network Location Provider every 60 seconds prevents the device from deep sleeping and was a main cause of the standby issues. I suggest to check it for yourself with BetterBatteryStats.
My ALARM_WAKEUP_ACTIVITY_DETECTION exceeded 1000 alarms by the end of the day. While I still get a few Android Wear wakelocks if my smartwatch is not connected. They make up at least 150 too. What I'm trying to say is that I don't say you should have no alarms anymore, but even 150 seem normal for Google Play Services. But over 500 or 1000 definitely isn't normal.
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
oksagi said:
I don't that greenify is needed anymore hence we are on android 9.0 , DOZE does that work pretty good.
Click to expand...
Click to collapse
That's my point. Even with light doze active apps still have a maintenance window and Sleep as Android seems to have permanently used sensors via Play Services. Once greenified it stops using it completely and I went from 1.2%/h idle drain to under 0.7%/h or less. I'm just trying to help people who have the same issue as I do. If no app seems to use any sensor, location etc. you don't need Greenify of course. But it can help with some apps.
This post was originally posted in Moto G5s Plus forum, but I thought/hope to get broader exposure and feedbacks:
I did extensive search and found no fix so far.
Problem: if my phone is locked for maybe 10min, then it will not display notification for incoming Signal, Whatsapp and Google Voice messages, until I unlock the screen and run the apps. In other words, I will not get notified of new messages if the phone is locked for over 10 minutes.
Native Messenger app is not affected, it displays incoming message right away. Gmail is good too.
I do not use Wifi, it is turned OFF. I am on Data 100% with T-Mobile. Stock ROM, rooted with Magisk and TWRP.
I have done "Battery Not Optimized", "unrestricted data", Battery saving mode is set Never, and there is no battery saving apps installed such as Greenify etc.
I have removed and reinstalled these apps from Play store, cleared data and cache, the whole 9 yards.
Still stuck with delayed notification.
Anyone with suggestions?
Thanks,
clu1688 said:
This post was originally posted in Moto G5s Plus forum, but I thought/hope to get broader exposure and feedbacks:
I did extensive search and found no fix so far.
Problem: if my phone is locked for maybe 10min, then it will not display notification for incoming Signal, Whatsapp and Google Voice messages, until I unlock the screen and run the apps. In other words, I will not get notified of new messages if the phone is locked for over 10 minutes.
Native Messenger app is not affected, it displays incoming message right away. Gmail is good too.
I do not use Wifi, it is turned OFF. I am on Data 100% with T-Mobile. Stock ROM, rooted with Magisk and TWRP.
I have done "Battery Not Optimized", "unrestricted data", Battery saving mode is set Never, and there is no battery saving apps installed such as Greenify etc.
I have removed and reinstalled these apps from Play store, cleared data and cache, the whole 9 yards.
Still stuck with delayed notification.
Anyone with suggestions?
Thanks,
Click to expand...
Click to collapse
It's probably caused by a wakelock that triggers after the screen is off for a set amount of time. Or maybe your device has a deep sleep mode that is triggered after a certain time with screen off.
Use Wakelock detector to identify the wakelocks on your device, then research the wakelocks that you find to see if any of them might be the cause of this issue. If you find a wakelock that is causing this, try using an app that can manage wakelocks to enable/disable the wakelock(s) as needed in order to get it working the way you want/need.
Sent from my SM-S767VL using Tapatalk