Jump to content

Welcome to CyanogenMod

Welcome to our forum. Like most online communities you must register to post, but don't worry this is a simple free process that requires minimal information for you to signup. Be a part of the CyanogenMod Forum by signing in or creating an account. You can even sign in with your Facebook or Twitter account.
  • Start new topics and reply to others
  • Subscribe to topics and forums to get automatic updates
  • Get your own profile and make new friends
  • Download files attached to the forum.
  • Customize your experience here
  • Share your CyanogenMod experience!
Guest Message by DevFuse
 

Sleep of Death


  • Please log in to reply
7 replies to this topic

#1 KSUCat

KSUCat
  • Members
  • 5 posts
  • Country:us
  • Device Model:Verizon Fascinate
  • MOD Version:TSM Ressurection
  • Recovery Image:ClockworkMod

Posted 06 December 2011 - 09:50 PM

Anyone else getting this on their fassy? I like the ROM, but had to quit using it because I kept getting the Sleep of Death and required a battery pull. I was getting this multiple times a day.

Any cures?

#2 sleclerc

sleclerc
  • Members
  • 2 posts
  • Device Model:Samsung Fascinate
  • MOD Version:7-11162011-Nightly
  • Recovery Image:Cyanogen

Posted 06 December 2011 - 10:04 PM

I've gotten this same problem twice in the past day.

#3 aaronjamesbrown

aaronjamesbrown
  • Donators
  • 11 posts
  • Twitter:aaronjamesbrown
  • Country:au
  • Device Model:Nexus One
  • MOD Version:7-11152011-NIGHTLY-N1
  • Recovery Image:ClockworkMod

Posted 06 December 2011 - 10:43 PM

There are many posts about this in many device forums which indicates it's not device-specific. Many forums indicate this problem has been fixed in the latest nightly. I was experiencing the SoD also; since updating to 15NOV11 nightly I haven't seen it. This nightly has been very stable for me, ymmv, but I would suggest trying this.

#4 KSUCat

KSUCat
  • Members
  • 5 posts
  • Country:us
  • Device Model:Verizon Fascinate
  • MOD Version:TSM Ressurection
  • Recovery Image:ClockworkMod

Posted 06 December 2011 - 11:12 PM

View Postaaronjamesbrown, on 06 December 2011 - 10:43 PM, said:

There are many posts about this in many device forums which indicates it's not device-specific. Many forums indicate this problem has been fixed in the latest nightly. I was experiencing the SoD also; since updating to 15NOV11 nightly I haven't seen it. This nightly has been very stable for me, ymmv, but I would suggest trying this.

Can anyone confirm this?

#5 SilentG

SilentG
  • Members
  • 1 posts
  • Country:us
  • Device Model:Fascinate
  • MOD Version:7 Nightly 11.16.11
  • Recovery Image:ClockworkMod

Posted 13 January 2012 - 02:53 AM

I can confirm that since installing nightly 11.16.11 I have not seen SoD

#6 errolroach

errolroach
  • Members
  • 1 posts
  • Twitter:errolroach
  • Device Model:VZW Fascinate
  • MOD Version:CM7 - Nightly 11/16
  • Recovery Image:ClockworkMod

Posted 04 February 2012 - 08:08 PM

I'm on the latest nightly (11/16) and have gotten the SOD twice in the past 24 hours.  Both times requiring battery pulls, then seems to be fine.  Not sure if this is still an issue for anyone else, just thought I'd check.

#7 TomTcom

TomTcom
  • Members
  • 86 posts
  • Country:us
  • Device Model:SCH-i500
  • MOD Version:CM7 Nightly 78
  • Recovery Image:ClockworkMod

Posted 09 February 2012 - 02:16 PM

View Posterrolroach, on 04 February 2012 - 08:08 PM, said:

I'm on the latest nightly (11/16) and have gotten the SOD twice in the past 24 hours.  Both times requiring battery pulls, then seems to be fine.  Not sure if this is still an issue for anyone else, just thought I'd check.

Go with skang rom by makelegs in the xda forum. Its the newest cm7 nightlies with extra goodies. I had the 112 nightly and it wasn't much improvement from 98 for cm7.

Fascinate CM7 Stable

#8 vinsnob

vinsnob
  • Members
  • 2 posts
  • Country:us
  • Device Model:Fascinate
  • MOD Version:7.1 Stable
  • Recovery Image:Cyanogen

Posted 14 May 2012 - 12:50 PM

I changed my wife's Fascinate to CM7.1 stable from stock unrooted to get rid of this problem, but no success.  After 7 days of running CM7.1 without a hitch, the phone simply stops responding - LEDs are on, but the screen is black.  Did a reset with volume up + power.  Installed Advanced Task Killer (despite everyone's opinion that I shouldn't since GB does this on its own) thinking that it may be a memory resource issue.  So we wait and see what happens.

ROM path on this was stock EH03 (with EH03) radios, flashed CM7.1 using CWM.  Still on the EH03 radios, though I'm seeing that the EC09 radio is what CM was built around?  Could the radio be causing this, or is it something else?