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
I like keeping my wifi on while my screen is asleep so that I can receive chat messages or e-mails without being at my computer. I never had this problem while running ICS on an unrooted TF201, but ever since I installed the upgrade to JB my wifi will always disconnect after the screen has been asleep for a few minutes. I've checked every setting I can think of. In the Wifi Advanced menu, I have it set so Wifi is always on, and in the ASUS customized setting I have Disconnect network during sleep to off. Under Power Saver I have Enable low battery settings off, set Low battery level to 0%, and even set Wifi OFF to off. Despite all of this, it seems like the tablet under JB goes into some sort of deep sleep and disconnects the wifi after about 5 minutes of inactivity.
I have noticed that this problem does not occur when the screen is on. I also have the dock, and set the screen to always on during meetings in the event that I don't need to enter any notes for a few minutes so I don't have to fool with any delays from screen wake .
Is there some setting I'm missing? Is it a hidden setting that I could access by rooting? Or am I dealing with something internal to the build that I can't change at all? This may not seem like a huge deal to most, but it has become one of my main uses for the tablet when I'm at home. I'm very disappointed with JB so far even though the wifi does feel more responsive on the Prime after the update (when it's not sleeping, of course!).
EDIT: I noticed this evening that the wifi turns off even when I'm running something that uses it while the screen is off. I was listening to Pandora, and about 5 minutes after the screen went off, my music stopped. When I turned the screen back on, I saw that the wifi had indeed become disconnected.
hey,
I have exactly the same problem with my tablet. I have checked every option, I did a factory reset several time, I have checked it on 2 different routers but it is still disconnecting the wife when it goes in the sleep modus. Did you or anyone else find a solution?
hi guys
i am having some weird problems with my s3, sometimes when i set my screen time out to 30 seconds. sometimes my s3 screen will not turn off, sometimes this happens while charging, sometimes after getting my battery pack full charge my screen will not also turn off, and the most recent event taht just happened is someone just gave me an phone call and i was not able to answer that call; after that event the screen of my s3 did not turn off. i think it was turned on for about an hour.
is the screen timeout features has bugs? if i set it to 30 seconds this weird event happens; to fix this trouble i need to press the power button manually. if i set it to 15 seconds i think it works ok but the time span is too short for me and right now i am trying to observe the 1 minute screen time out. but for me the 1 minute option is too long.
has anyone of you guys also felt that setting the screen timeout feature to 30 seconds is buggy? and what were your solutions to this problem?
thanks guys
I am experiencing a similar problem however I cant pin it down to a certain circumstance or some up with a solution. The problem seems to have started for me after the Jelly Bean update.
Do you have developer options under settings enabled? If so, do you have "stay awake" ticked or un-ticked?
Also there are couple of widgets causing a problem with screen timeout, like "Extended Controls". If you have that installed, uninstall and check again.
bnbasarir said:
Do you have developer options under settings enabled? If so, do you have "stay awake" ticked or un-ticked?
Also there are couple of widgets causing a problem with screen timeout, like "Extended Controls". If you have that installed, uninstall and check again.
Click to expand...
Click to collapse
I have checked the setting and the "stay awake" is unchecked. Yesterday it was staying on all of the time, but today it only seems to do it when it is on the charger. To weird... I only have a few widgets I am using, Calendar, weather bug, flip book and Google play Music. are any of these causing a known problem?
Conzo427 said:
I have checked the setting and the "stay awake" is unchecked. Yesterday it was staying on all of the time, but today it only seems to do it when it is on the charger. To weird... I only have a few widgets I am using, Calendar, weather bug, flip book and Google play Music. are any of these causing a known problem?
Click to expand...
Click to collapse
Do you have Smart Stay enabled under Settings > Display
I know that if my phone is in certain places in the room when I have been using it and just put it dowb the screen stays on as Smart Stay is detecting that I am still looking at it even though I am not just try turning Smart Stay off for a day and see if it stops doing it.
Conzo427 said:
I have checked the setting and the "stay awake" is unchecked. Yesterday it was staying on all of the time, but today it only seems to do it when it is on the charger. To weird... I only have a few widgets I am using, Calendar, weather bug, flip book and Google play Music. are any of these causing a known problem?
Click to expand...
Click to collapse
These are not the "usual suspects" but what I can suggest is removing all of them and adding one by one while checking the time out. Its not the best way but its the only way to identify since its not a common problem :/
bnbasarir said:
These are not the "usual suspects" but what I can suggest is removing all of them and adding one by one while checking the time out. Its not the best way but its the only way to identify since its not a common problem :/
Click to expand...
Click to collapse
I will give this a shot and see what happens. I had used these widgets on my old phone without a problem, but it is worth a try.
ag4751 said:
Do you have Smart Stay enabled under Settings > Display
I know that if my phone is in certain places in the room when I have been using it and just put it dowb the screen stays on as Smart Stay is detecting that I am still looking at it even though I am not just try turning Smart Stay off for a day and see if it stops doing it.
Click to expand...
Click to collapse
I initially thought is had something to do with smart stay as well as I did have it enabled, however turning it off did not solve the problem.
Anyone have a solution? I am experiencing the same issue where the screen does not time out... It will work when i do a reset.
I have tried to disable all widgets and thought that worked, but later determined it was still happening. it really seems sporadic. The problem persists consistently for a period of time, but then will work fine for a while, then go back to not working. My battery is dead now because I missed a call, the screen turned on, and never turned off. I am just discovering this 3 hours later... There has to be a solution. I may have to do a master reset, but I just did one due to reception issues and don't want to go through it again. Who knows if it will even solve the problem.
I've noticed this issue since first getting my S3 in July. So I do know it happened with 4.0.4 and now with 4.1.1. I've never used the "Stay Awake" option in the dev options and it still remains off. I've had the issue with both "Smart Stay" on and off. I've tested it with all screen time out times, as well as going through the trouble of factory resetting the device and nothing changed. The only solution I've found is reboot the phone and it will work again for a day or so until I notice it again. Very annoying and would love to find a solution to this!
I am having the same problem with my AT&T galaxy s III only a hard reset (pull battery) will fix it but it comes back at random times. Any updates on this?
Same problem here, it's strange because it just happens randomly.
Some days I will look at my phone and it appears to have a miraculous 50% battery drop. I too keep screen timeout set to 30 seconds...any insight here would be awesomely appreciated.
AT&T Galaxy S3
SGH-I747
You need to check for wakelocks,
Wakelocks can be used by other apps to wake your screen, and keep it on.
I discovered it by using Wakelock app :
Wakelock detector at GooglePlay
Hi.
I've got a problem with a sudden drop in the battery work time of my phone. Deep sleep not working or working for a while. I checked all applications and did not find any guilty app. Somehow, after a few days, I came to that, the deep sleep stops working after phone contact with a USB cable. It makes no difference whether it's plugged to the charger or the computer.
I checked in BetterBatteryStats, what could be wrong - it's kernel wakelock: musb_wake_lock, which is probably not allowing the handset to go sleep, so I need everytime to reboot my phone. I did factory reset, reflashed phone few times (stock ROM's, CM9) - it did not help.
Do you have any suggestions?
I have exactly the same problem with the exact same kernel process name taking up cpu with the exact same scenario too!
So, bump?
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.