Rooted NOOK won't wake up... some times.


Last Updated:

  1. RedheadTarn

    RedheadTarn Well-Known Member

    So here's the problem I'm having... Some times when I turn off the screen on my nook, after a few minutes it won't wake back up. Neither the home button nor the power key will turn the screen back on. The only thing I can do is to hold the power key for 10 seconds our so which would normally turn it off, then release and hold the power button again for 10 seconds or so until the screen flashes and it begins to boot up from a powered off state. I cannot find any pattern to when it does this and I have re-wiped and reinstalled cm7 but it still happens about 2-3 times per day. Anybody else run into this?

    Advertisement
  2. bobstro

    bobstro Well-Known Member

    That sounds like the "Sleep of Death" (SoD) problem that a lot of people have been encountering. The problem is associated with wifi. What firmware are you running? CM 7.2 RC0 Mirage has a number of fixes that reduced these significantly on my NC. Older CM versions are particularly susceptible, but general consensus seems to be that CM nightlies resolved it for the most part.
  3. colchiro

    colchiro Well-Known Member

    Your wifi should be set to never turn off (advanced settings).

    If it's older than CM7.1 stable, I'd update it. Is it installed on your NC (emmc) or on the sdcard?
    RedheadTarn likes this.
  4. bobstro

    bobstro Well-Known Member

    I'm fanatical about battery life. I like to keep wifi shut down when I'm not using it, except maybe for quick polls. I have had good luck on my NOOK color using Juice Defender to shut wifi off when the screen goes off, then letting it fire up every hour or so for a poll. Of course, this depends on how you use your device, but for me, battery life is paramount. My NC is my "long haul" device that I want to get at least two days out of if possible.

    I'd previously used Green Power, but it didn't seem to work well on the NC for some reason.

    On my NOOK Simple Touch, I've got it down to using Tasker to only enable wifi when a select handful of apps are running. That device is much simpler, though, but you could do the same thing on a NC is you really want granular control.

    Despite doing this, I rarely get the SoDs these days. I'm on B&N 1.4.1 now, but CM 7.2 RC0 Mirage was very solid using this same technique. Most of the SoD complaints I see are on CM 7.1 stable or older nightlies. Until we get CM9, the Mirage variant seems to be the most up-to-date CM going.
    RedheadTarn likes this.
  5. RedheadTarn

    RedheadTarn Well-Known Member

    Thanx, hadn't heard the term Sleep of Death yet. I'm running cm7.1 stable off of the emmc, and no real problems other than this. Is the cm7.2 mirage build pretty stable? I might try it out.
  6. bobstro

    bobstro Well-Known Member

    I found it very stable while I used it for most of December and January. I've reverted back to B&N 1.4.1, but not for any reasons related to the Mirage release. Since development of CM 7.1 has stopped so the developers can focus on CM 9, this seems to be the only place of active development. It incorporated a lot of fixes that were pending in nightly 253 and they've continued to add improvements.

    I read that there was supposed to be an official 7.2 stable eventually, but haven't heard anything about it in over a month.

    I'd suggest at least trying it out.
  7. RedheadTarn

    RedheadTarn Well-Known Member

    Ended up flashing cm7.2, and so far I love it. Everything seems snappier and smoother and I haven't had a sleep of death yet either.


    Feb 16, 2012: Update: a week later and haven't had any sleep of death issues after going to 7.2, also still seems smoother and more responsive than before.

Share This Page