My phone is not sleeping itself down after the time elapses.anyone else noticing this, its making me think its draining my battery.
Just tested this myself, and on a one minute sleep timer, my phone did properly go to sleep.
Mine sleeps fine too.
mine sleeps fine as well. Do you have any particular app running? For example, if you have AT&T Navigator running it will not sleep. There are a few other apps that provide the ability to prevent it from sleeping. So, are you on the main screen or in an app when it doesn't sleep?
Cannot say I've had this problem. Worked at its default of 1 min, and still works after I changed to 3.
I am trying to id the app if any that is causing it but with no task manager its impossible.
I do notice an issue with the camera app. If the camera button gets pressed then the phone will stay on and not sleep, for me at least.
It goes off on it's own mostly...thanks for the reports as I work through this. I may need a hard reset anyway, hey why not Ill add a microSD at that time.
Related
Having a weird issue happen on my Tab recently. Every time i 'lock' the screen or allow the screen to power down the GPS goes to sleep with it. Even if i have a GPS app open, it'll lose the position as the GPS has gone to sleep. The Green GPS icon in the notification bar is still 'on', but the GPS has gone to sleep.
Cannot figure out what is telling the GPS to power down on standby, but something is. Stock rom, not running ATK or anything similar. Suggestions?
same problem here... i'll try to let the tab go to sleep after 30", without switching off display ...
Same issue here with a rooted but nothing else Sprint Tab. Sleeping gps after 1 or 20 minutes, cannot find any reason why. The green button indicates its on, but toggle it off and immediately on and it works instantly. Any suggestions on why or how to disable gps sleep?
Made for an annoying 2000 mile trip to reset every 5 or 20 miles...
what you guys flashed ? ? , what you have done flashed already , pls do re-flash and maybe it will work .. if it doesn't work and this is 90% will not . pls . go back to your stock rom and then flash the rom back
It probably goes to sleep when the screen is off because it's not like youll be using it, also why do you kept it on, such a battery drain
swyped from a galaxy far far away...
I used the update.zip from the Samsung site to update to EB13, everything went off just fine except my Epic now takes an average of 2 seconds to wake from sleep after pressing the power button, sometimes going up to 4 or 5. Not the worst thing in the world, but pretty annoying.
I narrowed it down to my non-usage of the lock screen. I typically run without using a lock screen at all (disabled via SwitchPro Widget). If I turn the lock screen back ON, my Epic wakes from sleep either instantly or within 1/2 a second. With the lock screen disabled (no pattern lock either), it's super slow to wake.
Anyone have any ideas on what I could try?
Mine works just fine, but I'm using the lock screen, try uninstalling that widget and see if it corrects the problem when you use the lock screen.
Small update to this. I had an idea to move all the apps that I had moved to the SD card back to the phone to see if that helped. It does. With the lock screen on, my Epic comes back from sleep instantly every time. With lock screen off it varies between 1/2 and 1 second.
The apps I moved to SD were ones I hardly used.. I don't know why that would have an effect on the wake time?
Mine seems a bit slow too. But it's not the 4 or 5 seconds you described. It seems like it's about one second, when it used to be anywhere between instantly and half a second.
It's kind of annoying because the delay is just barely too long to where I start second guessing myself on whether or not I pushed the button in all the way or not.
Go to your display setting and reset your horizantal calibration accelerometer... that fixed my phone waking up issue...
Sent from my SPH-D700 using XDA App
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
toxicsociety said:
Unfortunately, I had already tried recalibrating. I do, however, have no lock on and widget locker running. Do any of you use either of these?
Click to expand...
Click to collapse
I use the same program as you do and I have the exact same problem So your not alone.
Mine is slow to wake also, about a second. When its plugged into the charger its instant, weird.
I'm glad we aren't alone though. Hopefully if this is a big enough issue, people will look into it. And also, they've pulled the EB13 update from Sprint and Samsung's website.
It's causing problems with reading media from the SD card and also has data issues. So hopefully in the new one, they will fix this problem too?
Looks like it's No Lock, from what I can tell. If you disable it, it comes on instantly. If it's enabled, it takes it a moment to wake up.
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?
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Well what case have you got?
I have no such problem on my Portenzo hardback case.
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Click to expand...
Click to collapse
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
sfhub said:
On mine, if you lose WiFi connection while it is asleep it won't magnetic wake.
Click to expand...
Click to collapse
Same. WiFi on or off seems to work okay... WiFi on and searching is always touch and go for me. Hopefully it can be fixed pretty easily in software down the road... before it starts to actually bother me.
Noticed this on mine as well. Different than my 2012 model but not a real problem
Sent from my Nexus 7 using Tapatalk 4
RKight said:
I just got my case today and my N7 doesn't always wake when I open the cover. I'd say it works about 80% of the time and it seems worse after the tablet has been sitting for a while. Almost as if it's sleeping too deeply to wake. A press of the power button fixes it but I'm wondering if anyone else is having this issue. If not, I need to think about whether I have a bad case or a defective tablet.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
WilliamG said:
I've found that it does actually wake up, eventually. I just tested it myself. When I got my Poetic slimline case, I was obviously messing with the Nexus 7 and it worked every time. I'd left the device sleeping (wifi set to not run during sleep, BT off), and when I grabbed it just now and opened the flap, nothing happened for almost 10 seconds. Crazy. However, it did eventually sleep/wake by itself. When I closed the cover and then opened it, it instantly awoke. So it seems like after the device has been sleeping for a while it just takes it a bit to wake up. Of course you can just hit the power button, too..
Click to expand...
Click to collapse
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
negroplasty said:
With WiFi set to stay on during sleep it works fine even during very long sleeps, like overnight. It's almost a non-issue for me since I always have WiFi on and if I go out I just remember to toggle it off or turn on tethering on the trusty old N4.
Click to expand...
Click to collapse
Yeah. All I know is I have the wifi set to not run during sleep, and all seems fine, - just that it takes the Nexus a good number of seconds to come alive after it's been asleep a while.
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
RKight said:
I decided to wait patiently and see if it would wake on its own. It did but took a full 20 seconds. On my first gen N7, it woke instantly every time. Hopefully it's something they'll eventually fix.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Same for me.
I noticed if WIFI is ON, or device is connecting to power/USB. The wake will works perfectly and instantly.
But if WIFI is OFF or not USB connection, the wake is not function after closed the cover for few seconds.
WilliamG said:
lol should start a contest! Whose Nexus 7 2013 takes the longest to wake up?!
Click to expand...
Click to collapse
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
hyperxguy said:
mine...mine...
Last night (I timed) it took 30seconds.
This morning (1st wake of the day, didn't exactly timed) it was more than a minute.
USPS has had my replacement "out for delivery" since early yesterday ... but never made it.. talk about the
organization in trouble... I usually see the man parking his truck in the shade, taking his time.
Click to expand...
Click to collapse
That's impressive! I'm sure it's a bug that affects all Nexus 7 2013 devices, but it's still lame.
For anyone having this issue, I found a thread on the Google product forums about this. That's apparently how they became aware of the other issues that have been reported. If you could, please post your problem in this thread: http://productforums.google.com/forum/m/#!category-topic/mobile/android-devices/8MTpqfFmw8Q
Sent from my Nexus 7 using xda app-developers app
Are we sure this is actually an issue? Based on the threads I'm reading about this, the cover only seems to wake the screen when you open it while things are running that would normally keep the N7 out of deep sleep. Isn't the tablet being able to enter deep sleep mode successfully a good thing?
The reason I say this is because a lot of you, including myself are reporting that when Wifi is off, and the tablet is unplugged, opening the cover won't wake the screen if it's been closed for a long time but it will after just short periods. This indicates deep sleep being entered successfully. If the cover is able to wake the screen in that mode, I'd be more worried that deep sleep mode isn't being entered successfully.
I guess the main question is: Is 4.3 along with the Nexus 7 hardware actually designed to only be able to be powered on by the power button itself during deep sleep? Do not services have to be running in the background constantly in order to allow something else to wake the screen? For example, in order for one of those 3rd party screen apps that use either proximity sensors, or light sensors or position sensors (shake) in order to wake your screen to work, all of the better ones I've seen not only require administrator permission, but also running background services.
In other words, they use the hardware sensors inside the Nexus 7 to wake the screen but also require some kind of additional resources running in the background. Which means resources being consumed. Smart covers also use hardware inside the N7 to wake the screen but without an app consuming resources in the background to so do. Which means NO resources consuming battery or memory, which is a good thing.
I'm not so sure I even WANT this fixed if it's going to mean my tablet has to have stuff running in the background in order for it to work. If Google can make it so that's not the case, then I have no problem with it. I could be completely wrong as well, I'm just speculating so if Google says it is actually a software bug then I guess I am.
omnius1 said:
Do not services have to be running in the background constantly in order to allow something else to wake the screen?
Click to expand...
Click to collapse
I guess that depends on the magnetometer chip they are using. If it can generate an async interrupt on a change in magnetic field, then that is one thing, if it has to be polled, that's something else. I don't find it too great a hardship to occasionally have to press the button, so if it is doing this to save more power, that suits me.
I think this thread is about all the "odd" things happening, specifically to the some 2013 Nexus 7 (some people don't have this problem).
I also have the 2012 N7 and the Nook HD+ with smart covers, both are running JB4.3.
Both can go into deep sleep and whatever (wifi on/off, things running or not) and will wake up in an instant as normal.
This is not normal !!
By the way, I received the replacement and similar results. I didn't expect it to fix the issue anyway as I think this is similar
to the tough issue with some N7s (I don't have this issue) which is a google problem.
A little off-topic about deep sleep... my Nook HD+ can sleep for a whole day and only take 1% of the battery.. best I've seen.
Edit: just in case somebody thinking about a ROM problem, I've tried multiple ROMs including stock.. all have same issue.
Moko smart cover is the best
It should wake up within a second, at worst, period. Ideally it'll wake up "almost instantaneously". There's something wrong.
I wish the mods would merge these two threads so the nonsense is at least in one place.
Mine sometimes will wake after a delay and will sometimes just sit and do nothing at all until I press the power button. It has turned on after a 30 second delay, after being idle all night, but has also completely failed to turn on after being idle for just five minutes. This thread is definitely aimed toward the odd inconsistences and what I indeed perceive to be a problem.
Sent from my Nexus 7 using xda app-developers app
Like the title says, my phone stops going into deep sleep about 3 days after a reboot. I need to reboot the phone for it to go to deep sleep again. Would anyone know what might be causing this?
Japultra said:
Like the title says, my phone stops going into deep sleep about 3 days after a reboot. I need to reboot the phone for it to go to deep sleep again. Would anyone know what might be causing this?
Click to expand...
Click to collapse
In my opinion, that's not a bad thing. It's better to restart any device with an OS on it at least once a day or two maximum.
A computer device that stays on for days is similar to a human not getting sleep. Things slow down and become fragmented. VRAM, Page File, etc start getting cluttered.
I'm not surprised your phone won't enter deep sleep after three days of being on. After that much use, you'd have used various apps and services causing wakelocks.
That's what I experience, at least.
FiddleGoose said:
In my opinion, that's not a bad thing. It's better to restart any device with an OS on it at least once a day or two maximum.
A computer device that stays on for days is similar to a human not getting sleep. Things slow down and become fragmented. VRAM, Page File, etc start getting cluttered.
I'm not surprised your phone won't enter deep sleep after three days of being on. After that much use, you'd have used various apps and services causing wakelocks.
That's what I experience, at least.
Click to expand...
Click to collapse
My S6 didn't do this though. I could go for a couple weeks without restarting it and it would still enter deep sleep.
I had a similar problem. For me it wasn't every three days, but usually 24-36 hours. But same issue, suddenly wouldn't go into deep sleep and a restart would fix it.
I found my issue to be gas buddy app and it trying to poll locations via bluetooth. Google it, there are lots of threads on it, but basically due to bad programming it would just jam on.
I figured this out as i could get my phone to go into deep sleep by turning off bluetooth, so that might be a quick easy test for you.
Also remember my in case (and unfortunately for a lot of other people) it was the gas buddy app. but others have reported the same issue with other apps.
i don't know if android's implementation on bluetooth location is busted, or the way the apps are using it.