13 replies to this topic

[hlfx]

Hi , I don't know is this is the correct section to post this but I will try it anyway.

I'm on CM 7.1.0-N1 now , but I was having randomly reboots, sometime like 2 or 3 in a hour , sometime 1 per day.

Today I just update to 7.1.0 , but same issue was happening on 7.0.2

I did tried the following to narrow the issue:

-Change to a new SIM
-reformat SD card
-wipe and factory reset
-upgrade from 7.0.2 to 7.1.0

and issue is still happening most of the time when phone is idle

I ran out of ideas , so I run logcat after the last reboot and I'm attaching it to the post, I tried to read the log but could not find anything useful  , so hope someone with more logcat-reading experience can help me to find what is rebooting my phone

thanks in advance!

EDIT: sorry but I could not find how to attach the file , maybe because Im posting this in wrong section?

I will appreciate any help on how to attach a file or maybe moving the post to the correct forum

Edited by hlfx, 01 November 2011 - 03:34 AM.

[bassmadrigal]

You posted in the right section

My first thought is that you didn't perform a full wipe. When you did it, did you MANUALLY wipe the /system partition? If you haven't, go into recovery and wipe it (under the Mounts and Storage menu) and then reinstall CM and gapps. It shouldn't cause any data loss.

[hlfx]

Hi bassmadrigal ,

Many thanks for your quick reply , I just wipe /system manually and also did another wipe/factory reset , for now I will just keep the phone without any other app and see if the reboot issue appears

Any other idea will be appreciated!

thanks!

Edited by hlfx, 01 November 2011 - 09:03 PM.

[hlfx]

After 12 hrs with no reboot , today in the morning I check my N1 and it was rebooted.......

Could be a HW issue?

There is any expert who can help me taking a look into logcat?

thanks
David

[hlfx]

my N1 just got rebooted after 6+ hrs of working fine , now I run bugreport to obtain a big log file , but the file is generated AFTER the reboot , so I think is not very useful.......

I'm still have some hope that some could help me with log files

thanks!

[bassmadrigal]

For hard reboots (if it shows the X) you need to get the file /proc/last_kmsg, if it is a soft reboot (just goes to the CM logo) you can use adb logcat. I'm not sure how many people here would be any good at reading the log, but you can give it a shot.

But if you have a clean install and are still having the issue, it sounds like it is a hardware issue. You can try and put the phone back to stock and see if it still happens there. There is a guide to do that in the xda N1 wiki.

[hlfx]

Thanks a lot for your reply bassmadrigal , and yes is a hard reboot , I will try to get proc/last_kmsg , I think that will provide me some clue on what is going on.

I also thinking that could be a HW issue (too bad )

Any way , thanks again for the help!

[hlfx]

Last night the phone rebooted again , I did not touch it and today in the morning I get the last_kmsg log, this is the last part:

Quote

[  904.462921] batt:  80%, 3977 mV, -114 mA (-41 avg), 25.5 C, 1084 mAh
[  909.237762] msm_pm_wait_state(2, 0, 0, 0) failed 11011
[  909.237762] msm_sleep(): msm_pm_wait_state failed, 11011
[  909.237762] ARM9 has CRASHED
[  909.237762] smem: DIAG '[WCDMA] 02:02:15 FATAL: WCDMA L1 (mdspsync.c:01765) (0)
[  909.237762] '
[  909.237762]
[  909.237762] Restarting Linux version 2.6.37.6-cyanogenmod-01509-g8913be8 (shade@toxygene) (gcc version 4.4.3 (GCC) ) #1 PREEMPT Wed Jul 27 21:31:24 EDT 2011
[  909.237762]

No errors detected

So it seems there is HW failure, correct?

[bassmadrigal]

Have you tried keeping your phone in 2G mode? I know there were some issues with T-Mobile in the US and having the phone trying to consistently connect to the HSPA+ T-Mobile network (which the phone can't do), and it would eventually cause some sort of build up that would cause the phone to reboot. This was solved with either using 2G, or getting a new SIM card (some people had cards only a few months old).

If that isn't the problem, then it does seem likely that hardware is to blame...

[hlfx]

Hey Bass,

after a lot of research , Im trying a new approach , it seems that the issue could be cause by my radio , so I "downgrade" my radio to the same google use in the OTAs (5.08.00.04) , before I was using 5.12.00.08 , so far no reboot

I will have in mind the 2g approach

cheers!

[Kendor]

bassmadrigal, on 01 November 2011 - 03:40 AM, said:

You posted in the right section

My first thought is that you didn't perform a full wipe. When you did it, did you MANUALLY wipe the /system partition? If you haven't, go into recovery and wipe it (under the Mounts and Storage menu) and then reinstall CM and gapps. It shouldn't cause any data loss.

I'm in the same situation. All of a sudden my phone is acting very flakey, with ramdon reboots. I definitely didn't do a full wipe. I did the upgrade via ROM Manager. Can you share some more explicit detail regarding the steps per above (e.g. 1-download CM 7.1 to SD card 2- reboot into recovery 3- etc...)

[invisiblewave]

My random reboot problem completely goes away if I lower the max CPU frequency to anything other than the fastest setting.

[bassmadrigal]

Kendor, on 15 November 2011 - 12:54 PM, said:

I'm in the same situation. All of a sudden my phone is acting very flakey, with ramdon reboots. I definitely didn't do a full wipe. I did the upgrade via ROM Manager. Can you share some more explicit detail regarding the steps per above (e.g. 1-download CM 7.1 to SD card 2- reboot into recovery 3- etc...)

It depends on whether you are running Amon_RA or ClockworkMod for your recovery. But since most use ClockworkMod, I will tell you about that one.

• Download CM and gapps to your sdcard.
  
• Boot into recovery and perform a nandroid backup (not required, but always a good idea).
  
• Go under the Mounts and Storage menu and select format /system (or wipe - I can't remember the exact wording).
  
• Go back to the main menu and go to the install from zip menu.
  
• Select Choose file from SDCard
  
• Find CM and install that, then do the same thing for gapps.
  
• Reboot the phone.
  
• ?????
  
• Profit.

[jkworth]

I have been dealing with this same issue for many months now. I have reinstalled many time and have even wiped all partitions just to make sure.

I recently looked at the log file and found no errors.

I am hoping that this is something that is being looked in to and resolved. If not then I will have to go back to the stock install.