Related
Hello,
I recently noticed an issue with my wifi (stock 2.3.3), where an app that needs to update regularly didn't seem to be doing it when the screen was off. As the phone always sits on its dock when I'm at home, I "solved" the issue by making the screen never turn off.
However, today I decided to give SIPdroid another go, as I tested it when I first got my phone and it wasn't working properly. I found out why, the second I put the phone to my ear, the screen turns off and the sound cuts. If I take the phone away, I suddenly get all the audio high speed as it catches back up.
A bit of googling showed this to be a known issue, the wifi goes into power saving mode when the screen turns off - on SIPdroid there's an option to keep the screen off and it seems to work well, it just dims the screen instead. But that's still an unnecessary battery drain.
I had trouble finding any recent info on the issue (within the past 6 months), maybe I was just using the wrong keywords. So I thought I'd ask here. Does anyone know anything about this issue? Is it likely to be fixed in the next version of android if it ever comes to the desire HD? Maybe there's a fix out there already (preferably without rooting and/or installing custom rom, my phone is just right as it is now...).
Settings>Wireless & Networks>Wifi settings>Hit 'Menu'>Advanced>Wifi sleep policy>Never
That'll prevent the wifi turning off when the screen turns off.
Sent from my Desire HD using xda premium
I tried that before posting, it makes no difference whatsoever (besides, the sleep policy is either never or 15 minutes, this problem occurs the second the screen goes off).
If u re root: change radio... try anyone.
stock: mmm default reset to try. (i think)
No:
http://code.google.com/p/sipdroid/issues/detail?id=268
http://code.google.com/p/sipdroid/i...Status Priority Milestone Owner Summary Stars
Reading through the comments, it seems a more general android problem. A reset wouldn't fix it.
Also:
http://code.google.com/p/android/issues/detail?id=9781
I'm now on my third nexus 7 and in general absolutely love the device but I'm getting fed up with the issues.
My first device suffered from sever flickering, the second had the backlight bleed and now the third refuses to wake after the screen is turned off about fifty percent of the time.
This is not the same issue as people are reporting in other posts as the charger is never connected when I have a problem. It doesn't matter if the screen times out or if I press the power button to after I finish using the device.
I'm using the stock ROM (with the 4.1.1 update), no root and have only installed the kindel app so its about as vanilla as can be.
The second nexus I had did this once but I had already organised the return and didn't think much of it.
Anyone else having similar issues or able to recommended a fix as this nexus is perfect in every other way?
Factory reset, leave it that way for a while, does it happen? If no, then you probably have an app doing something wonky.
Turn off automatic backlight, manually set it to around 40% and see if the flicker and the "SOD" goes away.
As the poster above said, turn off automatic brightness and see if that fixes it.
Nospin said:
As the poster above said, turn off automatic brightness and see if that fixes it.
Click to expand...
Click to collapse
Automatic brightness is on my N7 (and other devices) 100% of the time... No SOD problems here.
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
THANKS!
Just got my first nexus 7 yesterday and after pretty much falling in love, was dismayed about the unexplained black outs for no apparent reason. Could not wake up the device afterward without holding down the power key for 10 sec then leaving it alone for a while.
After reading your post, I realized that the incidents occurred after switching from manual to automatic brightness in a dimly lit room, followed by mysterious recoveries when moving to brighter room. I will monitor, but hope for the best. (Will probably just use manual settings as I found the automatic mode to be too dim in all settings anyway - old eyes!)
I am already pretty raw on this point as I just spent the last 10 years or so with a laptop that would not wake up from sleep, and just learned to live with it after wasting SO much time trying to get to the bottom of it. If you have saved me from that, or from having to exchange the n7, I owe you big time. Thanks again!
Compusmurf said:
lol, so far there's not an issue for you. But some have noticed that depending on the brightness settings it reads when you power on the screen, it can "think" it's either too bright or too dark and leave you with a screen you can't see.
This gets mistaken for "SOD" because you never see the screen-Why? Because it looks like the ratio for the lowest automatic brightness setting is a bit, um, TOO low. LOL
Most other devices won't exhibit this using stock settings, but the N7 will.
Click to expand...
Click to collapse
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
seven2099 said:
did you solve it or what?
I have the exact same issue and I'm about two second from returning this crap
so annoying
Click to expand...
Click to collapse
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
seven2099 said:
well that didnt fix anything.
Its a hardware issue, so i'm going back to stock and see what I can do, because if not, this baby is going back
Click to expand...
Click to collapse
i have similar issue with forced sleep, it cannot waken sometimes. TnT
anyone can help?
Further investigation shows this has nothing to do with brightness and that all tablets with this issue should be returned/exchanged immediately.
Quick google search will allow you to find that comes directly from Asus support.
Total fail, asus ftl
new tab rendered more quality issues. opened it at the shop, returned it immediately and went samsung.
Asus will always be asus.. too bad cuz my tf300 was pretty decent in terms of quality, just had wierd screen lift and squeecky issues.
Galaxy Tab 2.0 7inch is a much better choice now.
I have exactly the same problem with my current device. About 30% of the time, the power button would just stop working so I couldn't turn the unit on or off, unless I plugged it in to the charger. It didn't turn on for a full day once so I did a full factory reset which included re-flashing the stock rom and the problem persisted, the button would still not work! So I packaged it up for return and left it sitting for a couple of days. Just before I went to post it, I checked that the issue remained and to my surprise it turned itself back on again! I kept it and since then, it has only happened once.
I do intend to return it though, but only when I hear Asus are shipping units which are built properly. Clearly a hardware issue but pretty weird since it seems random and is not reproducible by any means I know of.
I am experiencing a similar issue. Does setting a manual brightness fix the issue?
It is my 3rd Nexus now with exactly the same problem.
I found out that the Nexus is in APX-mode (NVFlash) when it's in this state (SoD). Windows tries to install a APX driver when it is connected via USB.
The problem occured always with 16GB Nexus. A friends 8GB works fine.
Nexus 7 (C9) - Stock Rom 4.1.2. - locked - not rooted
Turning off the auto-brightness fixed the issue for me. Minor workaround to a major problem.
My screen randomly turns on and sits at the lock screen for a few seconds for no apparent reason. There are no pending notifications, etc. I assume there might be a rogue app causing this, but I don't have that many installed and even less apps doing any background tasks. Any idea on how to find the culprit?
I found this bug report where some apps are mentioned, but I'm not running any of them.
https://code.google.com/p/android/issues/detail?id=39625
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
I noticed that the phone wakes up whenever it reconnects to Wi-Fi. I was changing some router settings last night and I constantly saw the phone waking up shortly after the router rebooted. However, this is not the only scenario where it does it.
Mine has done the same, no idea why, only seen it the once, but it certainly happened, sitting three feet away from me, and suddenly Bingo! its on.
Mine wakes every few minutes. Certain apps (tasker, facebook etc) and syncing seem to cause it to happen more often but even if I disable most apps it still happens. I've been unable to identify the source with better battery stats. It happens bone stock and on CM10.1. I'm still getting better battery life than my GNexus but it's maddening.
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
ludovicien said:
Mine too. It will do it a few times in succession then be still for a while before starting again. No apps open and google sync off.
Click to expand...
Click to collapse
So my Nexus 4 doesn't want to go to sleep.
- I have sleep set to 15 seconds
- Dream is off (just in case)
It just stays on. It doesn't matter if it's on the the lock screen or at the home screen. I'm guessing some app is keeping it awake. It just started last night, but I don't think I have installed any new apps. Maybe it from an update.
solved
My phone's screen also used to wake up randomly. it was very annoying, especially at midnight
finally, I found out the reason by using "Wakelock detector" app which is freely available in market.
here is XDA thread about WLD: WLD at XDA Thread
the cause of problem was ad Notification, it was holding "full wakelock" (you can see it in screenshot)
good Luck!
Refer Wakelock Detector at XDA
Ramdom screen wake up issue solved
Dear all,
I was experiencing random screen wake issue in my XOLO PLAY smartphone.
The problem was with the AppLock software. After upate is this issue appreard. Earlier AppLock was there and no issue was experienced.
I am writing to AppLock team to fix the bug.
:angel:
All the best
Regards
nitin5062
hcedillo said:
On the Galaxy Nexus this issue was sometimes caused by a flaw in the micro-USB connector. I sincerely hope that is not the case with the Nexus 4.
Click to expand...
Click to collapse
U made an account to post THIS only?
Hi guys,
I have upgraded my n9005 to KK for a while now. And it seems that with KK 4.4.2 randomly break my auto brightness from time to time. This issue occurs the same time when an incall screenoff stop working.
To begin with, after a while of usage the auto brightness feature breaks where it did not adjust automatically. I got a very dim brightness level eventhough it's a night time. Also the auto brightness level doesn't work as well. But when I turned this feature off the brightness slider works again. Now while this is happening and I'm on the call my screen won't turn off automatically during the call or when I have finished my call the screen wont turn on. So for both issues I have to manually activate the screen via Home/power button. Moreover, I have notcied that while this is happening when I entered Camera app, the screen will be fixed on the landscape mode only and there is no way I can make portrait back again.
To be even more surprise, these issues will be gone and come back from time to time without restarting. However, upon restarting everything works fine for a while.
What I have tried to solve this issue:
- Reflash stock firmware (official version of my country)
- Clear dalvik
- Flash stock firmware (latest version from DBT)
Still I'm unable to solve these issues. I'm wondering that have any of you guys are facing these issues as well? I have searched and it seems that I'm only one having these problems. I just want to know whether this is only software or hardware related
Thanks
SoKoOLz said:
Hi guys,
I have upgraded my n9005 to KK for a while now. And it seems that with KK 4.4.2 randomly break my auto brightness from time to time. This issue occurs the same time when an incall screenoff stop working.
To begin with, after a while of usage the auto brightness feature breaks where it did not adjust automatically. I got a very dim brightness level eventhough it's a night time. Also the auto brightness level doesn't work as well. But when I turned this feature off the brightness slider works again. Now while this is happening and I'm on the call my screen won't turn off automatically during the call or when I have finished my call the screen wont turn on. So for both issues I have to manually activate the screen via Home/power button. Moreover, I have notcied that while this is happening when I entered Camera app, the screen will be fixed on the landscape mode only and there is no way I can make portrait back again.
To be even more surprise, these issues will be gone and come back from time to time without restarting. However, upon restarting everything works fine for a while.
What I have tried to solve this issue:
- Reflash stock firmware (official version of my country)
- Clear dalvik
- Flash stock firmware (latest version from DBT)
Still I'm unable to solve these issues. I'm wondering that have any of you guys are facing these issues as well? I have searched and it seems that I'm only one having these problems. I just want to know whether this is only software or hardware related
Thanks
Click to expand...
Click to collapse
Kinda noticed this while I was briefly on kk. If you're on AT&T keep in mind that it was not the official release, and bugs are present.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
sireniankyle said:
Kinda noticed this while I was briefly on kk. If you're on AT&T keep in mind that it was not the official release, and bugs are present.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
Thanks for letting me know that this is common for KK on N9005. LOL I thought it was HW related issue though
when turning my wifi off it seems it goes into some weird loop of turning on and off constantly by itself, it doesn't seem to be trying to connect just flipping the wifi switch on and off none stop.
noticed it because i had a huge battery daring overnight and while trying to fix it i saw the switch going off and on all the time.
when turning it back on it seems to connect normally .
did a network setting rest but it did nothing ...
I'm guessing a factory rest will fix the problem but I'm hoping to avoid such a overkill solution :crying:
does anyone else had this problem and can help me fix it?
thanx!
avivzamir said:
when turning my wifi off it seems it goes into some weird loop of turning on and off constantly by itself, it doesn't seem to be trying to connect just flipping the wifi switch on and off none stop.
noticed it because i had a huge battery daring overnight and while trying to fix it i saw the switch going off and on all the time.
when turning it back on it seems to connect normally .
did a network setting rest but it did nothing ...
I'm guessing a factory rest will fix the problem but I'm hoping to avoid such a overkill solution :crying:
does anyone else had this problem and can help me fix it?
thanx!
Click to expand...
Click to collapse
This was on a new custom rom ?
Or did it just happend on a rom that have worked perfect for days?
And have you seen which app or system app been casuing the drain?
LyLu said:
This was on a new custom rom ?
Or did it just happend on a rom that have worked perfect for days?
And have you seen which app or system app been casuing the drain?
Click to expand...
Click to collapse
original samsung rom.
just happened (i have the device for a a while everything was fine) its the android system that drains the battery in the battery status.
when i leave the wifi on it stops and works fine ...
Have you turned off ''Keep Wifi During Sleep''? I know this can drain battery.
It's not so easy to troubleshoot on an orginal none rooted phone.
You can try clearing dalvik and cache.
Turn it off and then on holding power and vol down button, then clear cach/dalvik and restart.
Try uninstall update beaming service for samsung then restart
If still persistent try uninstall update microsoft onedrive and skype then restart, just in case
I found it after factory reset (forgot internal data backup :crying and update all apps, this problem occuring after the last 3 updates (beaming, onedrive, & skype) which more suspect beaming service update make that problem
Your not alone
You're not the only one who suffer from this exact problem, on Friday or Saturday the same problem started occurring with my phone too, WiFi turns on and off in a loop and huge battery drain!
I saw an increase of 6% of battery drain per hour, so I ended up on 9% total drain every hour. :crying:
I have original Samsung Rom and phone worked prefect until now, no settings or apps installed before this happened either.
What rom version are you guys on?
I'm having the same issue. However, I'm on PhoenixX Rom. Major battery killer and has only just started happening within the past few days.
Since my phone has been unplugged, 3 hours ago, looking at BetterBatteryStats, It is showing com.google.android.gms as having quite a LOT of wakeups. 40 per hour (everything else is about 2). Don't know if this is normal as I don't remember it before the Wifi issue.
Looking into what the wake ups are caused from, Location and heartbeat were the major culprits. So i have turned of WIFI scanning when not on and also the body sensors for Google Play. We shall see.
LyLu said:
What rom version are you guys on?
Click to expand...
Click to collapse
See attachment.
Easy fix. Just disable Wi-Fi scanning.
the_scotsman said:
Easy fix. Just disable Wi-Fi scanning.
Click to expand...
Click to collapse
its not a fix at all . it dosnt scan for wifi , just turning it on and off non stop.
like pressing the light switch agin and agin
I had this after installing "GoodLock" software from Samsung! Uninstalled and everything is ok
same here, just noticed I wasnt on Wifi and the switch is just flicking on and off by itself. Standard S7 with all the updates installed
Been struggling with the same for some days (4 - 5) I haven't been able to get exactly whats triggering this. I'm on stock rom with root. I've reinstalled firmware clean again and re downloaded my apps but it is still happening randomly. Some times after a few attempts to switch wifi on (even when it is toggling by itself) it manages to keep on. Sometimes restarting makes it work again. One thing I'm almost certain its that this usually happens after I turn wifi OFF and then try to turn it back on.
It's been crazy and the phone starts to overheat after a while off this on-off loop.
Any ideas?
its very wierd it started to all of us in the past few days-weeks . seems like samsung has a bug they need to hurry up and fix.
AT&T just pushed out the October Security update for the S7 family, I'm guessing something that came along with it is creating the problem.
mine did a software update last week and I've been away in airplane mode so it could have started then. I've just disabled scanning and that seems to have got round the issue and I'm now connected to WifI
I'm not sure whether it is a Samsung Issue or a Third party one... It is true that something recently affected all of us, but as far as I know, it could be a third party app that wasn't well developed for our phone.
I've noticed the same problem on my phone and it's also only started up in the last few days. On stock Sammy rom, unrooted. Will be monitoring this thread to see if the experts here can narrow down the culprit.
I had the same issue and I was able to stop the toggle by turning off the wifi scanning in Location - Improve Accuracy - WiFi scanning. It's a fix for now. I think it may be an app that may have been updates that is persistently looking for location updates.