Nexus one not waking

kobecamp2009

Senior Member
May 7, 2010
112
1
0
Pasadena
mylifeisandroid.com
okay so when my n1 is in sleep, it takes like 3 tries to wake it up. The first time I press the unlock button the unlock screen comes and then goes back to sleep instantly. The second time the lights for the back menu home and search light up and that's it. the third time it works. I'm on froyo. anyone else with this problem?
 

lorin.bute

Senior Member
Apr 4, 2009
393
1
0
I have a similar issue.
Sometimes just the capacitive buttons light up and not the screen. I have to make 2 or 3 tries to get it to turn on. Its rare, but its there. It only happened on 2.2.
 

Palitu

Member
Mar 13, 2008
25
0
0
ok good, me too!

was just looking for this topic.

mine doesnt always turn anything on at all. sometimes the light go on, others nothing. Also trying to turn off the phone is hard as it sleeps straight away with out opening up the power menu.

I have a stock N1, which recently updated to Froyo, with the same problem.

any ideas would be great!

cheers,
 

Palitu

Member
Mar 13, 2008
25
0
0
i think it may be a hardware button issue.

I have tried turning mine off (had to pull the battery out) and then to turn it on.

It should turn on readily as it has nothing to do with the OS at that point.

any ideas?
 

Jack_R1

Senior Member
Aug 9, 2009
4,365
962
0
No HW button issue described. HW button works - if it didn't, lights wouldn't go on. It's a wrong reaction on the button, at least that's what OP describes (and me too).
 

rtx101

Senior Member
Apr 16, 2010
93
83
0
Hanoi
Your N1's power button is dying, it's a known HARDWARE issue. I experienced all of that what you may think a software bug, nut dear friends, prepare to meet HTC or Google for warranty. My N1's power button is dead, I couldn't swap for a new one because I bought it in my country where no official distributor for N1 yet. Sad!
ps: you may try to search for "N1 power button" and see there are more and more reports about this problem.
 

Jack_R1

Senior Member
Aug 9, 2009
4,365
962
0
I've read more than one or two threads on power button issues, and I know what I'm talking about. My power button DOES power up the phone when the battery is taken off the first shot, it DOES wake the phone from standby, it DOES register long presses - there was even one time when a second press was long, and suddenly the screen woke up with power menu, while the first press left it dark with touch button light going on.
Doesn't look even a bit like HW to me. HW would leave the phone dead, non-responsive to touches, or create a loose touch which would translate into several touches - none of those would EVER turn into a phone being on with screen off, and suddenly snapping back to screen on when the SCREEN is touched several times.
 

rtx101

Senior Member
Apr 16, 2010
93
83
0
Hanoi
:) Take your time! As for me, I'm using my N1 for 3 months now for the power button to completely dead with everyday use (I didn't use any app to trackball-wake).
As I said, all the things you are yelling I have been through. And I, too, thought it was software problem.
I tried both MCR and Cya with no hope.
Good luck!
ps: One of my friend just told me about his N1's power button issue right after hearing me telling about mine.
 

dylanrjones

New member
Feb 5, 2010
1
0
0
Corrupt SD Card

I had the same issue. I'd press the power button, the bottom four buttons would light up but no screen wake. Only way to get out of it was to pull the battery. It would happen maybe 30-40% of the time. (Nexus One Froyo FRF72)

I think it was due to a corrupt MicroSD card. I recently installed a 32gb card and put some music on it using songbird and possibly didn't safely remove. That's when I started getting issues. Removed the SD card completely and it worked fine. Changed back to the old card and no issues. Then formatted the 32gb and tried again, worked fine. Then I tried to transfer more music, there was an error and I got the same problem. (Cheap ebay card from Hong Kong, that'll teach me).

Anyway, I'd be interested to know if that solved anyone else's problem, because all I see on forums are that it's a faulty power button, but that didn't seem to be the case in my situation.

Cheers,
Dylan

-Witty esoteric statement about science/technology.
 

jimbobalu

Senior Member
Jan 26, 2010
214
6
0
Minneapolis
Mine is doing kinda the same weird thing but a little different.

When I push the power button the screen comes on but is unresponsive to touch. If I press the power button again the screen dims and then turns off, the home keys light up and then the trackball glows white. The phone then does not respond to the power button for around 10 secs and repeats this behavior 4 or 5 times until it actually starts working correctly and I can swipe my finger to get to the home screen.

It usually does this after being inactive for a period of time, like after sitting overnight.

FRF91
LancherPro Beta 0.6.7.2(maybe the problem?)
 

Jep4444

Senior Member
May 25, 2010
232
16
0
Toronto
Mine is doing kinda the same weird thing but a little different.

When I push the power button the screen comes on but is unresponsive to touch. If I press the power button again the screen dims and then turns off, the home keys light up and then the trackball glows white. The phone then does not respond to the power button for around 10 secs and repeats this behavior 4 or 5 times until it actually starts working correctly and I can swipe my finger to get to the home screen.

It usually does this after being inactive for a period of time, like after sitting overnight.

FRF91
LancherPro Beta 0.6.7.2(maybe the problem?)
i have almost the same issue, although mine happened twice when i was on EPE54B but it's been far more common on FRF91

the only difference is my power will continue to turn the back light on and off no matter if the screen has already timed out or not
 

bigmout

Senior Member
Oct 8, 2007
476
81
0
okay so when my n1 is in sleep, it takes like 3 tries to wake it up. The first time I press the unlock button the unlock screen comes and then goes back to sleep instantly. The second time the lights for the back menu home and search light up and that's it. the third time it works. I'm on froyo. anyone else with this problem?
I have exactly the same issue. Over in the general forum, there's another thread on this issue. Many, myself included, are reporting that this problem started after the FRF91 update. Can you confirm?
Your N1's power button is dying, it's a known HARDWARE issue. I experienced all of that what you may think a software bug, nut dear friends, prepare to meet HTC or Google for warranty. My N1's power button is dead, I couldn't swap for a new one because I bought it in my country where no official distributor for N1 yet. Sad!
ps: you may try to search for "N1 power button" and see there are more and more reports about this problem.
Read again carefully. Are you sure your hardware problem was identical to what the OP described? I've noticed a lot of people with obvious hardware problems (i.e., the power button is completely unresponsive) posting on threads like this when they actually have a different problem. It's very confusing.
Could be your cpu was too busy to accept any inputs.
I have a thread about it here:
http://forum.xda-developers.com/showthread.php?t=692874
This sounds VERY promising -- thank you britoso!

PS: Are you guys getting the unresponsive unlock slider like britoso describes?
 
Last edited:

Zephyron

Senior Member
Jan 12, 2010
337
12
0
I had this problem when I first flashed CM6 yesterday. Even after wiping and reflashing it was the same. Only way to get out of the black screen was to do a soft reset, power + vol down + trackball. I finally found out that my SD card malfunctioned and was corrupt. I tried reformatting the sd card in an microsd card reader but windows said it could not be reformatted. I finally switched back to another microsd card that was working, wipe and reflashed cm6 and the problem went away. Try backing up all the data on your microsd onto your computer then reformat it and wipe then reflash to see if it works

Edit: ughhhh it just happened again, but not as bad as before, turns back on after second try... maybe i didnt press the trackball hard enough
 
Last edited: