[Q] [HELP] CM 9.1 intermittent crashes

Wipster

Member
Aug 1, 2013
8
0
0
Hi all,

I am using CM 9.1 on my HTC Sensation (pyramid), and recently the device has been intermittently crashing to power off.

Here are some details on the software.
Android version: 4.0.4
Kernel: 3.0.36
Baseband: 11.69.3504.00U_11.22.3504.07_M

The crashes can happen in waves, so it powers off I power it on and it boots and I can get to unlock the phone then it crashes again. However it can happen randomly during operation as well, generally after unlocking and might be linked to lack of GSM signal but I cant confirm this.
The crashes do not seem to happen if the device is plugged in, and as the crash is like a battery pull I thought possibly dodgy connection however no amount of shaking and pressing or twisting can trigger it.

I have logcat in *:V and nothing is ejected that looks suspect, it just ends.

I have also logged kmsg, which ended up being huge but doesn't end at any spectacular failure.

My next step if we cant find anything up with software will be to load stock HTC back on and see if the problem is still apparent.
Anyone seen anything like this?
 

Attachments

astar26

Senior Member
Feb 3, 2011
235
44
0
Hi all,

I am using CM 9.1 on my HTC Sensation (pyramid), and recently the device has been intermittently crashing to power off.

Here are some details on the software.
Android version: 4.0.4
Kernel: 3.0.36
Baseband: 11.69.3504.00U_11.22.3504.07_M

The crashes can happen in waves, so it powers off I power it on and it boots and I can get to unlock the phone then it crashes again. However it can happen randomly during operation as well, generally after unlocking and might be linked to lack of GSM signal but I cant confirm this.
The crashes do not seem to happen if the device is plugged in, and as the crash is like a battery pull I thought possibly dodgy connection however no amount of shaking and pressing or twisting can trigger it.

I have logcat in *:V and nothing is ejected that looks suspect, it just ends.

I have also logged kmsg, which ended up being huge but doesn't end at any spectacular failure.

My next step if we cant find anything up with software will be to load stock HTC back on and see if the problem is still apparent.
Anyone seen anything like this?
There are people who report crashes when phone connects to GSM instead of WCDMA, you can lock your phone to WCDMA Only on the testing menu (dial *#*#4636#*#* and go to "Phone information").

Also, changing ROM might help. there is officialy built CM10, and CM10.1 is quite stable (I'm using it myself as a daily driver for a month now). Also there are many Sense ROMs which are very stable.
 

Wipster

Member
Aug 1, 2013
8
0
0
Hi Thanks for replying,
I shall try that however in the UK the signal is pretty poor in my area so I'm not sure how usable it will be, it seems to crash at the end of a call pretty reliably now, here is another kmsg there appears to be a raft of kernel Oops's prior to the end of the log.
 

Attachments

astar26

Senior Member
Feb 3, 2011
235
44
0
Hi Thanks for replying,
I shall try that however in the UK the signal is pretty poor in my area so I'm not sure how usable it will be, it seems to crash at the end of a call pretty reliably now, here is another kmsg there appears to be a raft of kernel Oops's prior to the end of the log.
I do not know how to read a kmsg so I can't help you there, but did you try my advice? Also, you can flash another kernel from the Android Development forum, just find one to your liking that works with CM ICS.
 

Wipster

Member
Aug 1, 2013
8
0
0
I do not know how to read a kmsg so I can't help you there, but did you try my advice? Also, you can flash another kernel from the Android Development forum, just find one to your liking that works with CM ICS.
I did indeed try locking to WCDMA only, however this rendered my phone useless in most of my common locations with no service. So I turned it back, I am able to connect to a GSM network alright.

I have just updated to a nightly of CM10, as there are no stables yet for my phone. The kernel still warns about a stuck clock so there is still an underlying bug in the kernel there or hardware fault, which I will look into. And so far so good, no crashes however I havnt used it much, time will tell.

Thanks
 

astar26

Senior Member
Feb 3, 2011
235
44
0
I did indeed try locking to WCDMA only, however this rendered my phone useless in most of my common locations with no service. So I turned it back, I am able to connect to a GSM network alright.

I have just updated to a nightly of CM10, as there are no stables yet for my phone. The kernel still warns about a stuck clock so there is still an underlying bug in the kernel there or hardware fault, which I will look into. And so far so good, no crashes however I havnt used it much, time will tell.

Thanks
Glad to help. The kanged 10.1 is quite stable (available in the Android Development forum), you could use that. There are also more kernels available, that might work well.
 

Wipster

Member
Aug 1, 2013
8
0
0
Glad to help. The kanged 10.1 is quite stable (available in the Android Development forum), you could use that. There are also more kernels available, that might work well.
Well unfortunatly CM10 crashes just as much, and its looking more like its signal related. I was in a place with either very poor or 0 signal and it was constantly crashing after boot, presumably searching for network.

Maybe its the radio and RIL? I would like to avoid changing these parts though if at all possible.

Edit: Attached is the kmsg for CM10 at a crash.
 

Attachments

Last edited:

astar26

Senior Member
Feb 3, 2011
235
44
0
Well unfortunatly CM10 crashes just as much, and its looking more like its signal related. I was in a place with either very poor or 0 signal and it was constantly crashing after boot, presumably searching for network.

Maybe its the radio and RIL? I would like to avoid changing these parts though if at all possible.

Edit: Attached is the kmsg for CM10 at a crash.
It's probably not RIL. Since the ICS update different RILs don't seem to matter (they work well for all radios). for example - two days ago I changed my radio - and it worked just fine without any further modifications.

You said you used CM10, but did you use albinoman's CM10.1? both ROMs you tried basically use the same kernel (from cyanogenmod), and downloaded from the same site (unless you use a Kang and I'm wrong). even sense ROMs, just to rule out kernel problems.
 

Wipster

Member
Aug 1, 2013
8
0
0
It's probably not RIL. Since the ICS update different RILs don't seem to matter (they work well for all radios). for example - two days ago I changed my radio - and it worked just fine without any further modifications.

You said you used CM10, but did you use albinoman's CM10.1? both ROMs you tried basically use the same kernel (from cyanogenmod), and downloaded from the same site (unless you use a Kang and I'm wrong). even sense ROMs, just to rule out kernel problems.
It was stock CM9 and CM10 I have tried, no other kernels.
With the CM10 image, can I just install a kernel from another ROM and it 'work' or do I need to change roms over to test?

I upgraded the radio (11.76A.3504.00U_11.24A.3504.31_M) using the latest RUU and then plopped my CM10 backup back on and so far so good, signal seems better however I'm sure that's placebo, will keep you posted.

Edit: OK so upgrading the radio did nothing whatsoever. Still crashing.
Attached is a nice crash, stops at msm_pm_power_collapse o_O something to do with shutting down CPU, maybe for clock change, I have changed the minimum clock freq to 384Mhz just in case mine is a device which cant do 192mhz.
 

Attachments

Last edited: