Related
I know there might be a dozen threads about this, but its all gobbledygook and nobody seems to have a straight answer.
I just want to ask: What can we possibly do about Froyo draining our battery? Task manager auto-killers aren't working right now it seems.
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Task Managers??? Are you kidding me? My battery life has doubled since Froyo because I dont use task managers or auto killers. Use Fresh Rom, with set cpu with perflock off, change the screen off to 245/245. Most important part is condition your battery...Trust me, i thought it was stupid as well, but it works.
drmacinyasha said:
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Click to expand...
Click to collapse
haha thats funny and true so i like it. i am running froyo official and have noticed an increase in battery. but hey when you get near your computer plug your phone in when you get in your car plug your phone in.
Froyo Killed Your Parents??
Sorry To Hear About Your Parents
R.I.P.
theres not much else u can do..just wait for a fix
I have ota and its the worst batterie ever with out doing nothing not even a phone call it died under an hour i only have gps enable had 3g off 4g to app all close no auto killer
Htc Evil Phone
I have the same problem. I read reports that Facebook 1.3 will not release the partial wake lock. I took FB 1.3 off and the problem persisted.
Here is how to check if you have a problem with your partial wake lock:
goto settings > about phone > battery and compare the uptime and awake time. If they are the same or very very close you have a wake lock problem. A wake lock allows an app to prevent your phone from going to sleep, even if the screen is off. If these times match then an app is creating a wake lock and not releasing it, and therefore your phone never sleeps.
As I said removing FB 1.3 did not solve the problem, but I was able to prove it is a wake lock as using Advanced Task Killer to kill 21 tasks allowed my phone to actually sleep, as indicated by a corresponding difference in the two times. So now that I know this is an app doing it, I will try to narrow it down and figure out which and report back.
OK I just found it. It appears the LED Light widget also causes a partial wake lock. To alleviate you don't need to uninstall it, just remove the widget.
Which led light? From market or the one with 2.2?
Borg1982 said:
Which led light? From market or the one with 2.2?
Click to expand...
Click to collapse
The new "flashlight" app is not a widget...It's actually called LED Light, by picolyl.
I don't have a problem, for me is little better!!!! just buy a new battery that solve your problem
drmacinyasha said:
Turn off 4G
Turn off WiFi
Turn off GPS
Turn down brightness
Stop opening crap
Problem solved.
Click to expand...
Click to collapse
Problem NOT solved. Or maybe 15 extra minutes.
Or don't use it at all, you'll save plenty of battery
Check to make sure that your Google Talk app is not automatically signing in. Go to apps - talk - settings. This is a typical battery drainer
totally forgot about google talk. have flashed a few ROMs back and forth, and now running a stock rooted ROM, I forgot to shut this one off...
use a custom rom, something without sense and try not to have a f***ton of widgets. im running cyanogen nightly and i get about 10 hours before i hit 20%-30% thats when i quit doing stuff and start trying to make the battery last. screen eats most of the battery so turn the brightness down.
my average 10 hours is 75-125 txts 30 + or - min of talk time and 3+ hours of internet (facebook)
oh, and about your parents... they are gone, there isnt an app or a rom that can fix that.
Indeed, the title of this thread is goofy. Froyo has literally killed my parents....... and has done a bad job for my battery life on my phone. Haha!
I guess an apostrophe would not have hurt after the word "parents" eh?
Doing a factory reset will fix your problem... I had the same problem when I updated.
Sent from my PC36100 using XDA App
opie2l said:
Doing a factory reset will fix your problem... I had the same problem when I updated.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I'm having similar issues with my OMJ 2.2 froyo rom. poor battery life, plus it seems laggy and unresponsive. i was much happier with OMJ's 2.1 rom
So, I just went and checked my phone's battery usage and realized it has been awake all day. I'm not sure what's causing this, nor how to fix it. I tried glancing through the forums a bit but I'm pretty busy at the moment and didn't see anything, so I apologize for probably repeating a topic. Oh, I'm running MikG 3.0 with the Less Lionfish 1.4 kernel, Smartass governor and SIO I/O scheduler. Thanks for any help.
sounds like maybe a rogue app. did you restore any apps through Titanium Backup? did you recently download any new apps? How long have you been noticing it? do you have any data syncing in the backround that may be hung up?
app
I think alaman68 is correct. If you reboot your phone, does it happen again? If yes, check your running apps for rogue service. If not, you'll just need to to do trial and error.
Today was the first day I noticed it, and I check my battery usage rather often. I am constantly installing and uninstalling apps, but I don't have anything currently installed that I didn't have before when my phone was normal. I'll reboot my phone and see if it continues.
Brilliancy said:
Today was the first day I noticed it, and I check my battery usage rather often. I am constantly installing and uninstalling apps, but I don't have anything currently installed that I didn't have before when my phone was normal. I'll reboot my phone and see if it continues.
Click to expand...
Click to collapse
wipe the cache and delvik when you reboot
I rebooted it without wiping either cache and it has stopped for now. Should I do that anyways? Thanks for the help, by the way.
In terminal emulator, type dumpsys power.
It'll shoe you if any of your system level apps or sensors are causing it
Sent from my PC36100 using xda premium
Im having the same problem somehow. I thought it might b android Os that was high but that doesnt come up on battery use...
Cm7
Check to see if you have FriendStream removed, I know MikG will allow this through the tweaks. If it's not showing up in your list of apps, it'll lead to a sync problem that will literally keep your phone on constantly. The only way to fix is to wipe and flash again, then don't remove it. You can try to push it back in through ADB, but that didn't work on my phone. I reflashed, and now I'm consistently getting 19 hours with no tweaks applied. Just a heads up. Without FriendStream, you may see the sync icon in your top bar all the time.
I don't have the sync icon or anything, just the ones on the pic but still awake?
If i do clean flash then nandroid restore, will the problem fine back?
What else can b keeping it awake
I don't have friendstrm or any of those Facebook related apps
Nothing comes up on battery use, its simply always awake
cwbeasley said:
Check to see if you have FriendStream removed, I know MikG will allow this through the tweaks. If it's not showing up in your list of apps, it'll lead to a sync problem that will literally keep your phone on constantly. The only way to fix is to wipe and flash again, then don't remove it. You can try to push it back in through ADB, but that didn't work on my phone. I reflashed, and now I'm consistently getting 19 hours with no tweaks applied. Just a heads up. Without FriendStream, you may see the sync icon in your top bar all the time.
Click to expand...
Click to collapse
Will this happen even if you shut autosync off? One of the first things I do when flash a rom is remove friendstream, I never thought of a potential problem though.
Sent from my PC36100 using Tapatalk 2 Beta-4
I don't have any auto sync, and Google apps bakup is off
This will happen with auto sync off.
Sent from my SGH-T989 using xda premium
Download the 'better battery stats' application. It will show you what is causing the wake lock
Sent from my PC36100 using XDA
OK I d.l the app. But I'm having trouble finding what's keeping it on.
What option should I click on.
The first screen does say my phone has been awake for one extra minute compared to the screen on. But I can't find the option where it says what the app is.
Hellp
oscar996 said:
OK I d.l the app. But I'm having trouble finding what's keeping it on.
What option should I click on.
The first screen does say my phone has been awake for one extra minute compared to the screen on. But I can't find the option where it says what the app is.
Hellp
Click to expand...
Click to collapse
When you open the app the first line on top says other. Change it to partial wakelocks. Before checking your wakelocks unplug your phone and don't use it for a few hours.
Sent from my lair.
OK thanks. It ended up being a `audioOut`1which I have no idea what they r since they r not apps. Check them out.
I'm on aokp evo
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Xxxdevilxxx said:
The issue is when i turn the screen off, lets say the time is 2:00PM and i check for notification at 2:20PM. What happens is as soon as the screen turns on the time jumps from 2:00 -> 2:20 PM , shouldn't this be done as a background process so that we shouldn't even see the time jump?
Anyone else facing this issue and any workarounds/fixes?
Thanks
Click to expand...
Click to collapse
Pretty old. Used to happen on my S2 too.
i guess it is an intent that gets activated upon waking of the phone (by turning on the screen)... when you do that, it updates the screen and thats why.
but then again... that is only what i think.. if it should update it while the screen is turned off it would be an active process and use battery
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
malybru said:
Hi,
Does it always jump to the correct time?
I have seen this on different ROMS on other phones.
Click to expand...
Click to collapse
Yes it always jump to the correct & exact time....it seems like a battery saving feature...if it is, other people with S4 should also experience it,no?
Tomo1971 said:
Does it on mine too but only the clock on the main lock screen, the time on the top bar seems to be correct.
Sent from my iPad using Tapatalk (how ironic is that eh)
Click to expand...
Click to collapse
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Xxxdevilxxx said:
For me i have a pattern Lock with time...so the moment i turn it on this is done on the lock screen clock...and yes the timer on the top bar seems to be correct(as in no jump).
Click to expand...
Click to collapse
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
malybru said:
Hi,
I ,too, have the pattern lock screen.
But I have the Lightning Launcher.
So, there is no lag or delay on mine.
Maybe ,try a different launcher and see.
Click to expand...
Click to collapse
oh...will do
New to XDA. Hello all!
I am experiencing this clock lag as well. :/
It doesn't matter if I use a custom lock screen or the Samsung lock screen with "swipe to unlock".
It's easily reproducible, let phone sit for 10-15 min and if you press the unlock button you'll see the wrong time for anywhere from a fraction of a second to a few seconds! and then it will update to correct time. Super annoying if I just want to know the time. Also, I've found that the amount the clock is behind is proportionate to the amount of time the phone as been idle....to a point...
I've seen the clock be over an hour off but it doesn't drift much more than than. Like a few folks mentioned, this should be running in the back ground. What is confusing to me is the clock in the top right is correct, so the phone is monitoring the clock...it's just not updating the lock screen clock.
Hopefully we can find a work around.
Not too keen on a new launcher...at least not until others who have seen that lag switch over and confirm it as a fix...but I don't think it will help, because the lock screen is still a Samsung process not controller by the launcher (i don't think)
Any thoughts?
The clock on the main unlock screen is essentially a widget. As a power saving feature, it only updates as necessary, which would be when you turn your phone on to look at the time. The time at the top of the screen in the notification bar is not a widget, it is a built in process that is always active. That is why it is current and the large clock, "the widget", is off until you turn your phone on to look at it.
My phone does the same thing. As does pretty much everyone's. It is not anything wrong with your phone, it is just the way it is set up. It is usually only delayed by a second or two, at best.
If it is an issue, you can always just remove the widget and use the time at the top of the screen to check. Or try a different app and set the update frequency.
It's not that big of a deal to me, I know it's always off until it refreshes, so I just give it a second to update.
Hi there, I have this problem; my AT&T GS4 does not use the deep sleep state. I have made some research, and from what I understood, this problem has to be a result of any program that keeps triggering the phone to get awake.
So, I have the phone unlocked, rooted and ALL the sensors off, expect from gsm signal. With titanium back I have uninstalled the programs that I´ll never gonna use (mostly AT&T bloadware) and frozen the ones that I don’t want to use right know, but maybe by deleting them I would get into a problem (like S-Voice) or just because some day I would like to give them a try. Finally, there are the programs that I would like to keep, but I don’t want to let them make any cpu use while I am not using them. I used an application called Greenyfi, a good example of why this program is the best for the last propose, is the use of programs like google maps, in where I do want to use it, but, just when I open the app. Also, I used the app “Autostarts” to prevent applications to start after some events (like startup, state change, etc..)
With all that been said, I am steel not getting deep sleep, in any situation. I´am not saying that my battery life is bad, I think I can get easily 4-5 screen time use. But, by not getting into deep sleep, the phone is allways using the cpu at 384mhz, so the battery goes down in a range of 1.5 to 2 % per hour (10 hours of no use and 20% less battery).
SO, for you to see the problem better. I did a little experiment. Restart the phone, put it into flight mode and let it “sleep” for the night, the results are attached.
PD: Whatsapp isn’t the problem; I can froze it and still 0% deep sleep.
PD2: Sorry for the language, I forgot to change it.
Get BetterBatteryStats app. It'll tell you what's keeping your phone awake. Look for partial wake locks.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Get BetterBatteryStats app. It'll tell you what's keeping your phone awake. Look for partial wake locks.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
ok, I did it, and BBS says that in partial wakelocks there is no major problem (20seg out of 1 hour the worst app). BUT, in kernel wakelocks, shows that "MSM_HSIC_HOST", is using the exact amount of time since the phone was turned on (1 hour). So, it has to be this. I´ve reading a huge thread of many people having a similar problem (mmsm_hsic_host been the process that wakes the phone most, but not using ALL the time, but considerable time (between 50% to 10). I ‘keep reading until I found a solution.
http://forum.xda-developers.com/showthread.php?t=1999368
Bro! I am so trying to get my s4 to not go into deep deep sleep, to be able to have a switch or click here button to be able to toggle that option would be the way for me to continue to use unlimited 4g tether because i was told to use hotspot vpn shield to prevent tim lee mobile from sniffing my data to see if i were tethering ! Although the vpn just told me that the application goes in to deep sleep (aka it turns off!) That's right folks the application turns off without you knowing until it's too late, so let see where to go from here. ??
revized said:
Bro! I am so trying to get my s4 to not go into deep deep sleep, to be able to have a switch or click here button to be able to toggle that option would be the way for me to continue to use unlimited 4g tether because i was told to use hotspot vpn shield to prevent tim lee mobile from sniffing my data to see if i were tethering ! Although the vpn just told me that the application goes in to deep sleep (aka it turns off!) That's right folks the application turns off without you knowing until it's too late, so let see where to go from here. ??
Click to expand...
Click to collapse
Keep it plugged in and in developer options click stay awake and it should stay on when plugged in.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
[email protected] said:
Keep it plugged in and in developer options click stay awake and it should stay on when plugged in.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
sweet thanks bro! maybe i can just manually push the power button once to turn off the screen while charging to save on screen back light usage. or is this just possible in my imagination?
revized said:
sweet thanks bro! maybe i can just manually push the power button once to turn off the screen while charging to save on screen back light usage. or is this just possible in my imagination?
Click to expand...
Click to collapse
Yes if you have developer mode to stay awake while plugged in and want to turn the screen off at any point just hit the power button to lock/shutoff the screen.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
well the hotspot shield vpn by anchors inc. makes thier app shut down when the phone goes into standby said the tech guy today because it still shut off.
so i suppose i need to prevent standby
ok i got to the bottom of this , hotspot shield vpn by anchors inc.are liars , the tether app auto prevents standby and i also i enabled the developer stay awake optiion. it turns out the application will turn off when no data is being sent for sometime and i have a feeling that it is in their favor for whatever reason otherwise the app would have an option to not shut off
now i was looking into getting termenal_ide to ping google every so often say every 3 or 5 minutes ,
i ran it and it was pinging like a mad man , more then once per second , i though i might get blacklisted for a false ddos
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