Hello
I've been reading about the event log service wakelock but i still can't find an answer for that, some people are freezing apps that i don't have. My phone is currently running under the stock rom + faux kernel and i have like 3 apps, that's all, i only use it as a music player, all the time is in airplane mode.
Do you know something related to the issue?
Another problem is, when using wifi, the processors stucks at 256 MHz and that drains battery as hel l, i can't find an answer for that D:
In the screenshot the problem seemed to be not as bad, but sometimes that wakelock is the number 1 partial wake and runs for hours
Related
This have been bugging me for very long. It not only affects my Google Talk, it also affects my Whatsapp, preventing them from getting messages on time.
Note that this only happens on 3G. I have no problem with Wifi.
I am able to get Google Talk / Whatsapp to push messages and get it's notification when I first booted my phone. The push stops when the phone is being idled for more than 5 to 15 minutes. I do not know why this happen, but when I look at *#*#8255#*#*, all timers listed froze and when I pressed on the "Send heartbeat to server" it does nothing (The heartbeat counter suppose to increase).
I tried to start the Google Talk app, and it started off with a fresh login (Means it logout while it was in idle state).
The two devices are, Stock DXLP9 unrooted and Lastest version of SlimROM with everything unchanged. No task manager involve on both affected devices.
I'm not sure if it's a carrier issue.
Is there anyone here that can help me solve this mystery?
I got the same problem here.
It's surelly related with some power saving thing.
I'm using WanamLite 12 with Siyah kernel 3.3.2.
My workaround was open terminal emulator and let it ping Google.com forever. It keeps the connection alive then I can receive msgs on IM+ Pro in real time.
AkaMod said:
I got the same problem here.
It's surelly related with some power saving thing.
I'm using WanamLite 12 with Siyah kernel 3.3.2.
My workaround was open terminal emulator and let it ping Google.com forever. It keeps the connection alive then I can receive msgs on IM+ Pro in real time.
Click to expand...
Click to collapse
I have tried your term emulator method and it does not work for me.
I have recently realised something that is very different that I did comparing to my friends.
They have "Automatically sign in" and "Automatic away status" checked in Google Talk.
I am currently trying this out to see if it works for me.
I will update again.
I have exactly the same problem.
I don't have a GSII, but a Sensation and a Galaxy Nexus.
After a while with screen off phone disconnect from google servers.. On galaxy nexus the bars change to grey color.
I did everithing.. nothing changed...
After Months, i get what it is the problem. The Operator..
Simply, switch from H3G, to Vodafone... The miracle happens
Google talk always connected, push notification of gmal, whatsapp and FB are instantaneous..
I found my own solution and it works for me.
I'm not sure if this works for others but here's what I've did.
Bought Tasker
Load Application GTalk, Wait 10 seconds, Go Home
Repeat this every 10 minutes.
I am not worrying at all as this consume very little battery.
I do see quite a number of wakelocks, but my battery life comparing to before has only lessen by an hour to two.
After using the method mentioned above, I now practising to switch off my phone while I'm asleep to save battery and still, my phone is able to last me through 2 full days (2x 16 hours) for my normal use as before.
Until I get S3........................
Hallo Iv got an Asus Padfone and have an annoying bug when my screen goos of and my phone enters stand-by all data connections are served wifi and mobile.
I can still revive calls but my whatsapp and other programs don't receive updates unless i unlock the phone.
This is very annoying since I have missed a lot of conservation some are 10 hours old.
I have done some research and I'm not sure whats cosing it but I think its something with the deep sleep mode of the processor thud doesn't wake properly.
when I check my cpu status I can see my processor is 96% of the time off line 2% active at 384MHz and 2% at other speeds.
Sow I think my phone cant wake when it needs to.
I have done a factory reset several times and tried diffident firmwares.
I also have tried software like wake lock but the sleep mode just overrides it.
Do you gays have any idea how to solve it like modifying the build.prop ore kernel?
Thanks
*note: I'm not using any power saving apps or settings
Greetings,
I had been using my Xperia Neo V with Cyanogenmod 10 (10-20130519-NIGHTLY-haida) for the last 2 months. It was all ponies and rainbows for me for the first 6-7 weeks.
Issue:
Now I'm facing with a random and ridiculous overnight battery drain issue since a week ago. Ridiculousness here is being referred to the amount of the drain (almost 60% overnight) and to the fact that there's no particular change of use of the phone by me,comparing with the days before. As you can see in the screenshots, the main actor here is "Operating System". I don't really know what this drain is related to, so I was not able to do comparisons of use.
Facts:
-Mobile Data was active but only at 2G
-Location services were off
-Bluetooth and all other possible signals were off
-No active apps, all were hibernated with Greenify
What might be the reason of this problem and what would you advice me to try?
Thanks in advance.
what kernel are you using? overclocked?
maybe you can try re-flash the rom
60% overnight is way high battery drain
You should try to see a pattern. Does it happen after specific usage "ritual" or just purely random?
It may be kernel bug/core system bug. Try dumping dmesg and logcat when it happen next.
I would start by trying to flash other kernel.
Install BetterBatteryStats (ther's an SDA thread); It will give you better info of what is draining your battery. In addition to that, you can post your logs in the thread (BBS thread) and they will provide better help.
Good luck
Edit: here's the link http://forum.xda-developers.com/showthread.php?t=1179809
Install wakelock detector app uninstall those... Try greenify too
Firstly we have to know what kernel are you using...
2.6.32.9 or 3.x.x version?
Hi there all, thank you for replies, and here are some extra info;
Fresh facts:
- Kernel: 2.6.32.9-FXP [email protected] #1
- Not overclocked
New observations:
So far I don't see any pattern as to what could possibly be the reason for this issue.
The last time I faced with this, the phone was fully charged and on 2G mode I left it on my desk (my wi-fi router was located next to it, keep it in mind so that it might be a clue coinciding with the BetterBattery logs I will reveal next) and after 3 hours, when I went to check if there were any calls, nearly 30% was drained. Comparing with the initial drain issue (which is a 60'ish% drain overnight) I can say it's the same issue within a proportionate period.
Well takin' a quick look at the BetterBatteryStatus report, drain was mainly caused by some wake thingy called "rx_wake". I don't really know much about all these wake calls in Android system but I googled it and reached to a brief conclusion that it's somehow related with Wi-fi connection. So I'm suspicious that maybe my Android system is perpetually sending wake calls related to a Wi-fi signal even when the Wi-fi mode is off on my phone (only relation I could make here is that I left the phone next to my wi-fi router)
I attach the screenshot and BetterBatteryStatus logs to this post, thanks in advance for your further comments.
Further comments, anyone?
Post the logs in BBS thread. There people has more knowledge and they can help you.
Issue Solved on Galaxy S - Will fit all I assume
Hi
I face the same issue from the day I install the ROM (CM 10.1.2)
I browse the Internet and found the issue
The issue is Wi-Fi and mobile network location
When it is on in this version it turn on the Wi-Fi not only on GPS request and No GPS status
You need to shout it down and issue solved
To change this setting:
System Settings -> Location access and disable the "Wi-Fi mobile network location"
Nachum
Device: Galaxy S3 i9300. Cyanogenmod 10.2. Googy Max kernel 1.8.0.
Suddenly that wakelock appears in BBS, and Wakelock detector. CPU keeps in 200 MHz, never go to deep sleep.
Didn't change anything this last couple of days, apps nor configuration nor any.
Google it and the info is confused to me, many technical stuff and weird code things.
In one old XDA thread someone fixed this very problem changing the SIM card for a new one. Didn't work for me.
Sometimes rebooting the phone solves everything, but then after a while thÃs battery eater wakelock pops up and brings devastation with it.
Please, some help with this will be appreciate
Hey guys,
I have a "little" problem with my S2. Whenever I leave wifi on and let the screen go off, my phone will get into SoD (sleep of death) and I can't wake it up. This will happen sooner or later.
I have this problem with every ROM I can think of. It's been a long time since I used a stock ROM, so I don't know if this only happens on Custom-ROMs.
Finding out that wifi (or my data connection) was causing those problems was a long process with a lot of frustration and trial and error (catlog won't work or doesn't show anything regarding the problem).
I tried to get rid of this problem with the APP "PNF - Push Notification Fixer" by reducing the heartbeat intervall of the wifi and mobile to 5 and 6 minutes (15 and 28 before) this seemed to reduce the frequency of the SoDs, but they are still happening.
I can get rid of the problem almost all the times with deactivating wifi when I let the screen go off or lock the phone myself. I get the same result when I turn off "Wifi optimization" in advanced wifi setting, but this is draining my battery pretty fast.
So basically I can use my wifi only when the phone is on the charger (no deep sleep at all) or if I turn it off when I lock the phone (something like 30 seconds can sometimes be enough to get the phone into SoD).
With data on and the screen locked I only experienced one SoD and this seemed to happen when I lost my signal at all.
So my conclusion is, that whenever I lose my data connection (might it be wifi or mobile) my phone does seem to get stuck in deep sleep at that moment or the moment it tries to reestablish the connection (the problem most propably got less after using PNF, because my router would kick my phones connection after a few minutes (10 would be my guess) of inactivity and this prevented a long enough inactivity. But they still happen (SoDs)). When I turn both wifi and mobile off and let it go into deep sleep this is no problem and no SoDs happen.
The SoDs were less but also happened when I were on CM11 M11 official, but got really frequent when I switched to Markox89's version of CM.
This is no rant or anything, I just want to get to the core of this problem and wanted to see/ask if there is something different in the Wifi module or wifi settings in this build and what could cause this very annoying problem.
Maybe someone else has this problem, too. Maybe my hardware is just faulty and I have to live with this :/
If it wasn't for this problem this ROM would run pretty smooth and flawless.
Does anybody else have the same problem or somehow knows how to get rid of it? This would get a lot of frustration out of my everday life :victory:
My setup right now:
- Markox89's CM11 Mod (22.11) (4.4.4)
- Lanchon's TRIM Kernel for CM 22.11 (same problem before using TRIM)
- Lanchon's Music bug fix (same problem before using Music bug fix)
- Modem: XXMS4
EDIT:
- XPosed with Xprivacy
- common apps like Threema, Telegram, whatsapp...
Tl;dr: my phone gets stuck in deep-sleep (SoD) if I leave wifi on when my screen turns off. no problem with mobile on or both data connections off. Halp?
@xhoster try to clean flash a rom and try it without all those apps you are using and then you can see or its app related or rom related. If it's rom related then I think some people already posted before there.
Also maybe try a custom kernel.
Try these things, I can't help you further then this atm.
Also mybe logcat the issue so you can read where it goes wrong.
FINAL EDIT: The problem seems to be the wifi driver all along!
Flashed the Apolo Kernel and this solved my SOD problem only had two since then and those seemed to be APP related!
Happy right now
It's seems to be the xposed framework! Tried it with a fresh installation after RomNuke and the phone was sleeping for 45 minutes and nothing happened, installed xposed and 10 minutes later I got a SoD. Tried it with the 2.7 beta 1 and the 2.6.1 stable version. Both gave me a SoD when I left wifi on...
Is this a known problem or has anybody ever had this problem?
When I tried it, I didn't even installed any modules, just the framework.
EDIT: I am going to test a bit more to see if it really is xposed or just the phone hanging whenever a connection is lost.