223 replies to this topic

[scubastevegk]

So this problem had been biting me all the way through the nightlies, and still happened when RC1 arrived.  I did a full wipe (/system, /data, and /cache) and did a fresh install of RC1, and had been completely problem free....until now.

At seemingly random times, the phone will become totally non-responsive.  I can't wake it up at all when this happens.  I've tried the power button, the trackball, calling the phone, texting the phone, and plugging it into the wall charger - none of them produce any reaction.  I'm pretty much left with no other recourse but to pull the battery and restart.  When I call the phone, it rings 5 times before it goes to voicemail, so it would seem that the network can see the device since it doesn't dump straight to voicemail.

Does this happen to anyone else or does anyone have any suggestions?  I'd be happy to provide some logs or other data if anyone can point me to what might be helpful.

Thanks in advance!!

[cabila]

Same problem since two days ago.
It doesn't wake up if it passed two or three minutes.
Not possible to wake up with trackball enabled trought Cyano settings.
I resolved it formatting all from recovery also Dalvik cache.

I think the problem will begin again.


PD. Also Cyano 7 has done unexpected resets in my two Nexus.  


Javier

Edited by cabila, 22 February 2011 - 05:51 PM.

[bassmadrigal]

When this does it, have you tried connecting the phone to the computer and seeing if you can use adb?

[ale_x_ela]

Same to me.
I had this problem at 6.0 after i installed 32gb SD.
On 4gb it worked good.
Didn't tried on 7.0 with 4gb.

But as i was pressing power button (at 6.0) menu buttons was lighted up.
Nothing in 7.0

It worked good for one day and the problem started to appear.
The only way to get it back, is by removing the battery.

Can i try to do something? i don't want to go back to 6. Thins one is just awesome!!
Please fix this bug...

thnax a lot for all work you do!

[scubastevegk]

I haven't tried adb yet - I'll give it a shot next time it happens.  Anything in particular I should try if it works?

[bassmadrigal]

Get a logcat. It could give you the reason it is hanging. dmesg might help too.

You can just type adb shell (need usb debugging turned on). Then type su and try both commands. If you use the redirect symbol "<" (without quotes) you can send the output to a file. Example would be "dmesg > /sdcard/dmesg-output.txt". Then you can look over the file on the computer (it is a long file) and towards the bottom, it will hopefully give you the reason it locked up.

[scubastevegk]

bassmadrigal, on 22 February 2011 - 02:44 PM, said:

Get a logcat. It could give you the reason it is hanging. dmesg might help too.

You can just type adb shell (need usb debugging turned on). Then type su and try both commands. If you use the redirect symbol "<" (without quotes) you can send the output to a file. Example would be "dmesg > /sdcard/dmesg-output.txt". Then you can look over the file on the computer (it is a long file) and towards the bottom, it will hopefully give you the reason it locked up.

Don't know why I assumed basic Linux output wouldn't apply here  

Thanks!

[ojai00]

What's happening when the phone becomes unresponsive? I experienced an issue where when I receive a call or tried to make a call the phone would hang between 5 and 10 seconds. If the person didn't give up on the call and was still on the line then I would be able to hear them. If you're experiencing this issue, then the Dewonkificator application fixed it for me. I believe it's a bug with the CM7 nightlies and RC. [ADDON] CM7 Dewonkificator [v1.3 02/16/11]

Hope this helps.

[cabila]

My problems with the "non-responsive" issue have starting again.

[kilometers]

I have this problem too since the nightly releases. On this one I did a full format of my SD card and started everything from scratch with the RC1. After one day of use it started doing this to me.

I noticed that if I have it plugged in via USB or the power cable this problem does not occur. Like never. It only happens when it's not plugged in and charging. Also, if you plug your phone in when it stops responding instead of pulling the battery your phone will restart.

Edited by kilometers, 22 February 2011 - 06:17 PM.

[scubastevegk]

ojai00, on 22 February 2011 - 03:09 PM, said:

What's happening when the phone becomes unresponsive? I experienced an issue where when I receive a call or tried to make a call the phone would hang between 5 and 10 seconds. If the person didn't give up on the call and was still on the line then I would be able to hear them. If you're experiencing this issue, then the Dewonkificator application fixed it for me. I believe it's a bug with the CM7 nightlies and RC. [ADDON] CM7 Dewonkificator [v1.3 02/16/11]

Hope this helps.

That's the weirdest part - nothing is really happening on the phone.  Just out of nowhere, I'll go to wake the device up to do something, and it won't wake up.  I can't figure out what the common thread is - it's driving me crazy!  I've been lucky enough to never experience the call wonkiness - I've been expecting it to hit me sooner or later, but I've managed to avoid that to this point.

@kilometers, I agree - I've noticed it's NEVER happened when the phone is plugged in.  However, I've not noticed the phone rebooting when I plug it in after it happens.

[bassmadrigal]

ojai00, on 22 February 2011 - 03:09 PM, said:

What's happening when the phone becomes unresponsive? I experienced an issue where when I receive a call or tried to make a call the phone would hang between 5 and 10 seconds. If the person didn't give up on the call and was still on the line then I would be able to hear them. If you're experiencing this issue, then the Dewonkificator application fixed it for me. I believe it's a bug with the CM7 nightlies and RC. [ADDON] CM7 Dewonkificator [v1.3 02/16/11]

Hope this helps.

His problem is unrelated to the wonks (which btw, may be fixed in tonight's nightly). His phone will lock and not come back from it (wonks will come back sometime between 5 and 25 seconds).

[jmejiaa]

I have ha da similar issue, however it vibrates when it receives a message and the trackball lights. The screen does not light up and nothing I do works.

[scubastevegk]

So my phone locked up just now, and I plugged it into my laptop to check adb.  Nothing showed up in the adb devices list, but I can now verify the behavior of the phone rebooted after it gets plugged in.  I would say after about 45-60 seconds of the phone being plugged into my laptop, the reboot took place.

Obviously dmesg isn't any use after the reboot.  I pulled off a logcat dump, and I'm going through it to see if anything of value is there, but I'm not expecting it after a reboot.

[scubastevegk]

Just got my first one of these on a 2.3.3 build - did a full wipe (system, data, and cache) before I installed.  Was hoping 2.3.3 would be the solution, but no luck!  I don't see much discussion of this in other threads - is this a rare thing?  Any others experiencing the same problems?

[scubastevegk]

I'm back to my belief that this has something to do with Bluetooth.  On earlier nightlies, I would have problems at other times, but lately, I only seem to have trouble after Bluetooth disconnections.  Twice today, I was using my phone for Bluetooth audio in my car.  After I stopped the car and tried to wake my phone to look at my email, it was unresponsive.  Is there any way to stream some kind of logging to a file so it can be retrieved after the phone has rebooted?  I'd like to see if there's any concrete backing to my feeling.

[msm]

Have the exact same issue but not sure that Bluetooth is causing this. This happens to my N1 with RC1 and nightlies even though BT is off. Phone works fine on 6.1.

[samarium]

scubastevegk, on 23 February 2011 - 02:12 AM, said:

So my phone locked up just now, and I plugged it into my laptop to check adb.  Nothing showed up in the adb devices list, but I can now verify the behavior of the phone rebooted after it gets plugged in.  I would say after about 45-60 seconds of the phone being plugged into my laptop, the reboot took place.

Obviously dmesg isn't any use after the reboot.  I pulled off a logcat dump, and I'm going through it to see if anything of value is there, but I'm not expecting it after a reboot.

After it reboots look at /proc/last_kmsg it might give some hints.

[philoscience]

samarium, on 04 March 2011 - 11:01 AM, said:

After it reboots look at /proc/last_kmsg it might give some hints.

Just checking in to say I've been having this same problem on nightly 12 and now 13. Tried full-wipes with no change.

[msm]

Did anyone find a solution to this problem? I wonder is the CM guys know that there is this bug for some N1 phones.

It's seriously annoying that I can't upgrade to CM7 or Kan-Go-Rama without the phone permanently switching off...