Hey guys,
I experienced bad wakelocks with the Honor 6. The phone was active for about 85% with screen off. I figured that G+ (which I am not using) and the Backup wakelock were by far the worst locks. I disabled the automatic backup and deactivated G+, I hope that fixed the issue. Has anybody made similar experiences?
Related
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.
Hi guys,
I got a really annoying issue with my 1+1, got my phone for 2/3 months.
I did already a lot to fix this issue but couldn't find a fix.
Battery status: battery savings..
Pics:
http ://imgur.com/a/dMmVb
Does anyone know a trick to fix the android system draining bug?
Your screenshots show absolutely no information. You need root and one of the following apps,
- BetteryBatteryStats
- GSam
- Wakelock Detector
Root required. From that point on, you'll know what app is causing your battery to drain via partial wakelocks and alarms.
Have you tried a fresh stock install of 38 r? Ota seems to result in poorer performance. Assuming your using 11s?
Disable "wake lock" and "stay awake" in Privacy guard to Google play services.
Okay so I have experienced this wakelock since I got this phone and I never really knew what caused it as "Android System" was the top consumer and looked like it was the thing that caused the wakelock.
So today I decided to use Wakelock Detector and I found something called "C2DMHandlerThread" that's hiding in the normal "Android System" bunch of apps in battery management information.
What is it and how do I stop it from waking up my device without factory reset (Which worked for another XDA User)?
Any help is appreciated!
c2dm is an old android API, you'll have to track down the app using it
I also have this wakelock
I also have this wakelock.. did you resolve?
Same on Mate 9. Only getting 30% deep sleep due to this!
kazprotos said:
Same on Mate 9. Only getting 30% deep sleep due to this!
Click to expand...
Click to collapse
Try turning on flight mode during the night, wakelock seems to be gone when it's enabled...
Sent from my Honor 8 using XDA Labs
Kind of defeats the purpose of a smartphone for me. Haven't had more than 1% loss at night in a phone for years!
In disable service only thing I can pick that might bd related is in android system > com.huawei.android.pushagentproxy.push service
Scared to disable and maybe brick
I'll make a nandy and try it later on.
Is there a way we might be able to lower the wl frequency or completely turn it off?
Hi guys,
after several days of research on google and in this forum I still couldn't find out what's the issue with my new Galaxy S7 device so I'm posting it here and hope for you to help me out.
I also had the same issue on my Galaxy S6 before but it was way worse because of the smaller battery.
The phone is not even a week old and I have issues with it to go into deep sleep mode since day one. I even installed BBS and Wakelock Detector with granted rights for the battery stats but I wasn't able to find out what causes the problem (it's the exynos model by the way).
The Kernel Wakelock stats in the Wakelock Detector App don't show unusual usage anyway, those who are always on top (also with my Galaxy S6) are the "PowerManagerService.Display", "13960000.decon_f" and "PowerManagerService.WakeLocks" followed by "mmc0_detect" and "bbd_wake_lock" (I will post a photo later, I am currently at work in my break) which hold the phone awake around 20-25% so it isn't always in deep sleep or doze mode.
All the google research said that the decon_f thing is connected to the DOT/SOT which I cannot confirm in my case. I still don't understand what the problem could cause because I didn't even use it for a week. When I set up the phone I did it clean without copying apps or using the backup from my Google account so I don't think that could be a reason for it.
I appreciate your help guys, thanks!
I don't really now much about your problem (sorry for that), but if you're rooted i can really recommend you the app ForceDoze. It activates the Doze Mode right after you turn off your screen and lets you black-/whitelist apps, which are/aren't allowed to make wakelocks. It also gives you the ability to control other doze related settings.
It's not rooted and I don't want to trigger the Knox counter so I think I will stay with the stock configuration. I'm really wondering what could cause it, never had those issues on my Redmi Note 4
I am running into a Wakelock issue and I am completely stumped. For some reason, my phone refuses to go into deep sleep for hours on end. Better Battery Stats shows that the phone spends the majority of its time with the CPU at its lowest frequency, but refuses to go into deep sleep. The issue started when I clean flashed LinageOS back when I tried 14.1. Since 15.1 has recently released, I tried to have another go, yet the problem remains. I am using a Oneplus 5.
The very weird thing about these Wakelocks is, is that they are completely invisible. Wakelock Detector isn't showing any specific wakelocks (Advanced mode enabled), but does show that the phone isn't entering the deep sleep state. Not even for a single second. Better Battery Stats shows the same thing, with zero seconds spent in Screen off (deep sleep) and all the time spent in Screen off (Awake). No application is listed anywhere that's causing these wakelocks. They aren't visible under partial wakelocks nor kernel wakelocks.
Now this is where things get bizarre. I tried removing all my applications and reinstalling them one by one to find out if it was an app that was causing the issues. Each time I installed an app, I would check whether the phone would go into deep sleep when I wasn't using it. It turns out that the phone stopped going into deep as soon as Whatsapp was installed. Yet Whatsapp would never register more than a few seconds of wakelocks each passing hour.
I'm not sure where to even begin to try and solve this issue. Has anyone else ever experienced these kind of invisible / hidden wakelocks, and if so, how did you manage to fix these issues? Thank you very much in advance for helping me out
Nobody with a similar problem to mine? It's really killing battery life for me
Mushoz said:
Nobody with a similar problem to mine? It's really killing battery life for me
Click to expand...
Click to collapse
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
IanHodgson said:
I think I may have something similar happening with WhatsApp. My stats show lots of time spent with CPU on and screen off. Wakelock detector shows WhatsApp at the top of the list. But I don't really understand how to solve it other than deleting WhatsApp, which I don't want to do. Did you get anywhere with it?
Ian
Click to expand...
Click to collapse
No, I still have the same issue unfortunately. Though my issue seems to be slightly different than yours in the sense that Whatsapp is very low in the list. The total minutes of Wakelock is far below the total minutes of awake (screen off). But uninstalling Whatsapp instantly solves the wakelock issue. Out of interest, what phone are you using and what rom?
Mushoz said:
Out of interest, what phone are you using and what rom?
Click to expand...
Click to collapse
Redmi Note 4, Pixel Experience Oreo 8.1
I got here through a google search. I am not sure it's whatsapp causing this (haven't removed it yet) but on a Moto G3 with LOS 15.1 unofficial by Rahul I have the same symptoms.