• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Power button

alanbingham27

Well-Known Member
I bought my daughter a N7 for Xmas there and I am just wondering is it normal that you have to hold the side power button down for like 10-15 seconds before it actually turns on? Find it odd as my S3 is turned on within 2 seconds.
 
I bought my daughter a N7 for Xmas there and I am just wondering is it normal that you have to hold the side power button down for like 10-15 seconds before it actually turns on? Find it odd as my S3 is turned on within 2 seconds.

If the device was fully powered down, then I wouldnt say its all that strange. Holding it for a few seconds should start it up as well though
 
press and release instantly should turn the screen off and or back on if its just in standby.

press for about 3 seconds and release if its been "turned off" should see "google" on the screen and it will boot up.

10-15 seconds press when ON and not responding will shut it down, and 10-15 seconds when OFF will boot it up but you shouldnt have to hold it that long, it more of a force boot.

I dont power off my Nexus 7 often, I just leave it in "Standby" by turning the screen off with a quick press of the power button, that way it should turn on instantly when needed.
 
I just timed 3 seconds until the 'Google' came on.

Do you have "fast boot" enabled? I think its in the power settings.

Just curious. I don't think it would affect how fast it turns on, just how long it takes to boot.
 
There is a weird issue I've noticed sometimes where the Nexus 7 won't come out of standby/wake up (it IS running and working fine otherwise with music playing, receiving notifications, USB debugging is fine etc, just that the screen doesn't turn on). You can sit there pressing the power button, but the screen never comes on.

When you hold the power button for 15 seconds or so, it performs a hard reset, which forces an instant shutdown and it reboots (giving the appearance that it was off).

As for how to fix it, I don't know. It used to happen to me constantly on stock 4.2.1. I flashed a nightly CM10.1 and the problem went away, so it might just be a bug and not a hardware issue. But I wouldn't consider rooting and flashing a custom ROM a "fix" per se. So I guess we will have to wait for Google to release an update.
 
Back
Top Bottom