yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] khaytsus:
Hey guys, per Dalingrin's posts in the CM7 Dev or General thread, he's been unable to reproduce Sleep of Death. A lot of folks have seen it but it's hard to pin down a pattern in forum posts, so I created a google spreadsheet form to track builds and configuration people are using.

Dal has looked over the form and gives his thumbs up, so let's fill it out! The idea here is to fill out for EVERY SOD you have, filling out the latest information. If you remember the details, feel free to fill out recent SOD info.

If anyone sees anything I should update/modify or add, let me know. Also, if anyone wants an Excel file from either or both forms for analysis, please let me know and I'll send it. One thing to note here is it's impossible to see folks who are saying No on the Results form vs their answers, so the raw data could be useful.

Anywho, link is here, please fill it out guys! This form is to query you on what build you're using and how you have some things set up. Please fill it out every time you have SOD, and folks who do NOT have SOD are also encouraged to fill it out!

https://spreadsheets.google.com/spr...ormkey=dFZrS0tOdTVwZ0pnaWpqSTQwaDFmcmc6MQ&ifq

And here's a summary page of the responses so far:

https://spreadsheets.google.com/viewanalytics?formkey=dFZrS0tOdTVwZ0pnaWpqSTQwaDFmcmc6MQ

New Form!

And there's also a second form to track some answers to Widgets and Apps that sync/run all the time below. I did set the answers as No/Yes so you should just be able to click the ones you have installed/use and the rest you can just skip over and it'll default to No. Probably only fill out this second form once, as this is just to query the apps/widgets folks are running.

I am looking for feedback on additional apps, but since I have SOD on this set of "stuff" I figure it's good enough to start with. Honestly my confidence that this will be what figures out SOD is fairly low, but it should just take a few minutes, unless you're really aligned with me and have a bunch of the same stuff ;)

Like the previous form, folks who have and have not experienced SOD are encouraged to submit their data.

Appreciate it guys, hopefully it continues to help out the CM7 gang understand why we're seeing SOD.

https://spreadsheets.google.com/spr...US&formkey=dHRMVklTSTgzT1htRkZRYWFfTmQ5WHc6MQ

And here's the direct link to the results so far..

https://spreadsheets.google.com/viewanalytics?formkey=dHRMVklTSTgzT1htRkZRYWFfTmQ5WHc6MQ
[Nook Color Android Development] khaytsus:
Semi-informative form changelog for Form 1 (Build and Settings)

Added Nightly 83, 84. Added non-default OC kernel for folks using 1100 or such, added eMMC vs SD Install, and added SOD Yes/No so folks NOT having the issue can provide their data too

Added N/A to battery questions for folks NOT having SOD, added Never to frequency of SOD question for No SOD folks. Also modified existing questions to say SOD or Normal Sleep.

Semi-informative form changelog for Form 2 (Widgets and Apps)

TBD
[Nook Color Android Development] boxcar8028:
thanks khaytsus, great idea. I hope this will help us all with SOD and no deep sleep :D
[Nook Color Android Development] sinanju:
May I also suggest that people who are experiencing SODs:

1) Press the power button once to turn the device on.

2) If the screen does not turn on, DO NOT PRESS THE POWER BUTTON AGAIN... just let the device sit for a while -- at least several minutes

3) After about 5 minutes, try pressing the power button again.

There is evidence to suggest that at least some subset to of SODs are actually the device just taking an extraordinarily long time to wake -- long enough for people to assume it's dead and reboot.

Normally I can wake the device by pressing power or "n", but in my most recent apparent SOD, the power button did not wake the device, nor did the "n" button. After about 5 minutes, the power button worked. Once, it woke about 3 minutes after pressing the power button.
[Nook Color Android Development] boxcar8028:
thanks sinanju, but I have read this somewhere before to, but my nook is set to go back to sleep in one minute. so how does this work? does the back to sleep clock setting only start after a full wake. but this is still a bug. a 5 min wake up is just as bad as a true SOD

maybe we should call it "SO5MW" sleep of 5 min wake :D
[Nook Color Android Development] 12paq:
at the risk of cluttering a dev thread,

Hey khaytsus, nice job!

Hopefully this will help clear up sod or sod-a-like or sod assumed issues. Lol :)
[Nook Color Android Development] Moxie3000:
A couple of things:

1. Need to add all builds that are compatible with kernel .32 like N83 and N84. I'm on N83 and I just got my first confirmed SOD.

2. Not everyone maxes out their clock with the OC kernel. I keep mellow at 1100.
[Nook Color Android Development] Awats:
You might want to accommodate those of us that aren't having the problem as another data point. I am running what I perceive as the same exact same setup as those with the problem and I don't have it.

Just a suggestion.
[Nook Color Android Development] khaytsus:
Added 83 and 84.. For the kernel OC I didn't want to put TOO many choices, but I've added one for OC Kernel, not-default speed. Hopefully people put it in the notes, but I have a feeling it's more around OC/not OC vs frequencies. Good info either way!

Good suggestion, only problem is that the numbers wouldn't mean much. So if I had daily SOD's (I don't, like 2-3 a week) and you never have SOD, you'd have one "No" against my 7 "Yes". However I think you're right that if you have the same config as most other people have and yet you never have SOD there's some other variable to consider. I've added a column for SOD Yes/No. Thanks for the suggestion!

I've also added a question about eMMC or SD, although I don't think it matters, but regardless it's one more thing to capture. You suggested it too, by your signature ;)
[Nook Color Android Development] angomy:
Thanks for doing this, it's interesting to read the results so far to see what people have been experiencing.

I think you were right (in an earlier post in PBD thread) and I was possibly not waiting long enough between power button presses to see if my Nook would wake up by itself -- while I was trying for several minutes, I may have been inadvertently turning it off/confusing it during an SOD by trying to hard boot it too soon after previous hard boot attempts.

My nightly 85 install isn't SODorPDBing until ~20% so it'll be a while till I can add information to your OP, I'm afraid. (at 89% now).
[Nook Color Android Development] TubeShaped:
Yesterday I had a SoD too. I'm on nightly 87 with dalingrin 5/23 at 1.1ghz. Just one thought from my side, couldn't it be an overheating problem due to overclocking? I wasnt able to turn it back on unless I waited some time....
[Nook Color Android Development] philburkhardt:
I don't think having to wait is the norm with SOD. I don't ever have to wait. Just hold the button until it powers all the way down, and then turn it right back on. Also, my temp doesn't seem to fluctuate much. It's always between 80 - 89 degrees Fahrenheit, and I've been overclocked since January.
[Nook Color Android Development] chisleu:
set wifi to turn off when the screen is off, or manually turn it off when you put it to sleep and see if you can get it to happen then.
[Nook Color Android Development] philburkhardt:
My wifi is set to turn off when the screen is off. I have had it set like that for about a week. I still get SOD.

EDIT: n91 is up! Lets see if it changes anything.
[Nook Color Android Development] Awats:
I updated to 91 and last night. I shut it off at 58% and it was at 7% this morning. Before with 86, it's might lose 1%. I do notice that wifi is on now when I hit the button whereas before it would take 10-15 seconds to come on. Hmmm, maybe it's set to keep the wifi-on during sleep. Not sure why it would have changed.

I need to play with it more but if it continues I will drop back to 86.

EDIT: And now I don't. Dunno ...
[Nook Color Android Development] painter_:
I was not suffering with SOD on any nightly. I flashed n91 yesterday and reflashed dal's 1.2 emmc kernel. Today I had three SOD's.

Normally I use the power button to wake up my nook, each of the three SOD's I had today I pressed the N button.

I have tested a little since the three SOD's and if I press the power button the nook comes to life. If I hit the N button nothing, subsequently hitting the power button does nothing. Could be nothing but thought I would report it.

Leaving the Nook sit for 5 minutes after an SOD did nothing but kill 5 minutes.

update:

I reflashed the rom and kernel and it seems fine now.
[Nook Color Android Development] khaytsus:
Hmm, I'll try waking mine with Power button, I always wake it with the N.
[Nook Color Android Development] daugh016:
I've never experienced one and I only wake using the power button. Using nightlies and Dal's latest.
[Nook Color Android Development] boxcar8028:
SOD is still alive

how is the SOD and deep sleep issues with everyone on n91 or higher? Im on n93 and is still getting SOD and no deep sleep.

n94 I see "Wifi: Minor change in SDIO release behavior" in the change log. does anyone know if this is something to do with SOD. does the SDIO release behavior have something with the nook waking up?

Im starting to think SOD has something to do with the recovery of the screen after a sleep. I mean the system is up and running I can hear the beep sound when I press the volume buttons and I the hear the notification sound so I know the system is up and running it only the screen that is not. the waking up of the screen may have some kind of conflict with the wifi or something else waking up at the same time. just my guess. not sure.

cm7 stock n93
[Nook Color Android Development] khaytsus:
91 and 94, deep sleep is fine for me...
[Nook Color Android Development] skwalas:
Deep sleep works just fine for me on 94, without the 0523 overclock kernel. I lose deep sleep whenever I flash the kernel.
[Nook Color Android Development] paleh0rse:
The same is now happening to me when I try to run the 5/23 OC on n94. :(

I'm back to 925 MHz on base n94, and deep sleep works perfectly again...
[Nook Color Android Development] bonobomidwest:
A question, a thought and a promise:

Q: I never had SOD on 7.0.3. But I now have SOD every time the device is left off for a prolonged time. And it will only wake if the charger is plugged in, regardless of battery level. Is this even the same problem?

T: If Dalingrin is never having the SOD problem, then perhaps there is something obvious about how dalingrin installs updates or sets up to his NC that avoids the problem - Dal could you PLEASE post a step by step (i know this sounds silly) on how you flash an update to your NC (e.g. do you always format /data etc.)

P: Promise to add my data to the sheet when I have a few minutes later today
[Nook Color Android Development] khaytsus:
For me, charger has nothing to do with it. I get zero response with Power or N button. I've waited 5+ minutes, I've hit volume buttons, touched the screen, even tried adb, pinged it, etc.. No response from anything. I have to hit the power button for 8+ seconds, then turn on normally (Power for 3-4 seconds) and it boots up.

There are folks who say that for them it seems like the screen won't turn on but the device is otherwise awake, as if they hit the volume keys they hear the max/min beep noise.

Dunno what to make of the different varieties myself..
[Nook Color Android Development] boxcar8028:
yeah, this SOD and no deep sleep issue is a tuff one to pin down. has anyone ever heard or tried this workaround?

re-flash to original B&N rom 1.1 or 1.2 and then flash back to a cm7 nightly build n91 or higher with the .32 kernel. some people say this has worked for them with SOD and no DS. not sure if you'll need to un-root or not. it sounds a little like the PBD trick of flashing into honeycomb from SD and then flash back to cm. maybe I'll try this, but was really hoping for a solution from cm. if I do try this I'll report back for sure.
[Nook Color Android Development] khaytsus:
Yikes, let us know, I know I won't be doing that ;)

Yeah unfortunately so far the stats have a lot of info and not one single thing is pointed out which isn't blindly obvious.. like Wifi On by default... can't point at Overclocked vs Not Overclocked, stock kernel vs Overclock kernel (at any speed), Wifi Sleep Policy, being out of range while asleep, etc, etc... No real patterns emerging, anyone else see anything I'm missing? Here's the URL if you don't have the responses URL on hand..

https://spreadsheets1.google.com/sp...cs?formkey=dFZrS0tOdTVwZ0pnaWpqSTQwaDFmcmc6MQ

Next step... Apps? Not sure I'll find anything real conclusive there either, but I can do it. Only problem is getting a list of apps that "everyone" is using. I can put my apps in, and I typically have daily SOD, but my SOD isn't necessarily the same exact root cause as someone elses. Plus there's at least two variations of SOD.. One you can hear beeps and it seems alive but no screen, other it's stone cold dead.. I see the latter.

By the way guys, if anyone wants an Excel file of the results for either form just let me know, maybe you can analyse it better than I.
[Nook Color Android Development] khaytsus:
Everyone, I'm updating the OP.. I have another form up. Sorry I can't read everyones minds, but the list you're about to witness is basically every Widget and App that runs full time on my NC, plus anything else I could think of...

I did set the answers as No/Yes so you should just be able to click the ones you have installed/use and the rest you can just skip over and it'll default to No.

I am looking for feedback on additional apps, but since I have SOD on this set of "stuff" I figure it's good enough to start with. Honestly my confidence that this will be what figures out SOD is fairly low, but it should just take a few minutes, unless you're really aligned with me and have a bunch of the same stuff ;)

Appreciate it guys, hopefully it continues to help out the CM7 gang understand why we're seeing SOD.
[Nook Color Android Development] tiffanydawnn:
Just throwing this out there, but I had SOD a few times after installing CM7 on my new nook. After installing juice defender and letting it manage my wifi on and off, I haven't had a SOD yet (about 2 weeks).
[Nook Color Android Development] khaytsus:
I would use Setting Profiles Lite for this, but I've considered it just to compare... Just hate waiting for wifi to reconnect.
[Nook Color Android Development] pmilford:
Interesting SOD data point

HI,

I didn't have any SOD under 7.03.

I upgraded to n87 with 5/23 overclock kernel at 1.2GHz.

I went on vacation for 3 nights with no wifi signals available - I didn't

have a single SOD (and battery life was excellent too - didn't need to

charge while away, though with few hours of eBook reading use only.)

When I returned home, had SOD that night. Upgrading to N94, stock kernel

and still getting SOD overnight and sometimes when off for a while during the day.

I have unsecured WiFi with an apple airport extender. WiFi set to notify

when open network is available. There is at least one other low power

network visible with WEP.

I looked at the systempanel log/graph of the system state today, and the

NC seemed to be running overnight, though I could only wake by plugging

it in this morning.

Hope this helps!

Peter
[Nook Color Android Development] boxcar8028:
alright, I have been playing with the wifi setting on my nook trying to find a pattern of behavior that causing SOD and no deep sleep (NDS) new acronym :D, here's what I have witness:

1) wifi sleep policy set at, when screen turns off: NDS no SOD

2) wifi turn off: NDS no SOD

3) wifi sleep policy set at, never: deep sleep but would get SOD

next I think I'll try installing a battery saving app. to see if would help with my SOD and NDS issues. maybe perhaps just like how "Android Assistant" was the trick for fixing airplane mode bug. I'll report back after my findings. with fingers cross. :)
[Nook Color Android Development] khaytsus:
See my note in blue above..

Keep it up, turn off wifi before shutting off the screen for a while. Be our champion :) It at least isolates Wifi OR "something data related".
[Nook Color Android Development] skwalas:
Khaytsus, can you post a link to the actual table of responses instead of the summary graphs? I'd like to dig through but need to see the responses by individual. Just for the first survey, since the second one doesn't have enough responses to do much with.
[Nook Color Android Development] TubeShaped:
sorry wrong topic
[Nook Color Android Development] boxcar8028:
Not much free time last night. I was not abel to test battery saving apps for SOD and NDS but I will try later this week. But I was abel to confirm that with my sleep policy set at "screen turns off" I would get SOD and NDS....

Have you guys checked out this thread:

http://xdaforums.com/showthread.php?t=960537&page=282

starting at post 2817

=======================

It seems that dalingrin is working on a fix for deep sleep and is asking for information from users and to post there dmesg, logcat and the output of /proc/wakelocks. I don't know how to generate these logs but for those who can please do so and provide them to dalingrin. :)
[Nook Color Android Development] boxcar8028:
I'll try this tonight, thanks Khaytsus. I'll keep reporting any of my observations that maybe helpful in killing this f-ing bug. I wish I know more about linux and programing but I'm just a hobbyist who loves tinkering. :D
[Nook Color Android Development] khaytsus:
Duh yeah I guess I can just make it a public viewable link can't I..

Build/Settings:

https://spreadsheets.google.com/spr...Z0pnaWpqSTQwaDFmcmc&hl=en_US&authkey=CO223NEK

Apps/Widgets:

https://spreadsheets.google.com/spr...zT1htRkZRYWFfTmQ5WHc&hl=en_US&authkey=CJL93Vc
[Nook Color Android Development] khaytsus:
That's for folks who never get Deep Sleep, not folks who get Sleep of Death.
[Nook Color Android Development] boxcar8028:
well, for me the two goes hand and hand. If my nook is in deep sleep it will not wake up on its own. so for me SOD is related to NDS.

I think dalingrins fix for the deep sleep bug can also help people with SOD.
[Nook Color Android Development] bonobomidwest:
[no sod, no pbd, functional deep sleep, 1% battery drain over 12h]

Okay folks... I have been plagued by a combination of SOD and PBD whenever i have tried upgrading from 7.0.3 to any of the nightlies. As you may remember i asked if we knew what Dal was doing on his installs that might explain his lack of the issue... so i decided to pursue that route of inquiry myself.

In a nutshell i tried every route of updating i could onto my existing clean stable, virgin, untouched, and well behaved 7.0.3 install. Every possible combination caused issues...

So inspired by this post I decided to go for a teardown install from stock. The instructions in this post are a little excessive, so i experimented to find the minimal route that would work. I have now had the NC running for at least 24h without a single issue (before i was suffering SOD every time the NC screen was off for more than a few minutes).

HERE IS THE RECIPIE - this requires some prep work, but only one session in CWM. You might want to flash a bootable CWM just in case on a SEPARATE card.

0. Full backup using

a. CWM for a flashable restore

b. ADW for partial restore of desktop

c. Titanium Backup (TB) (user apps + data) for more complete restore of desktop & apps

1. Flash CWM 3.2.0.1

2. All downloads are made on the nook (using whatever browser you please) to the download folder on the SDcard

3. Download SamuelHaff's 1.0.1 restore to stock (download #2 in this thread)

4. Download Nemith's flashable stock 1.2 update (the stock, NOT the keep CWM option, from this thread)

5. Download latest gapps from the CM7 wiki (got to the bottom of the page)

6. Download latest CM7 nightly (#96 in my case)

7. Summon some courage

8. REboot into manual recovery (i.e. CWM)

9. Format /data, /cache, and /system

10. Wipe dalvik cache

11. Flash Samuelhaff's restore to stock

12. DO NOT REBOOT

13. Flash Nemith's 1.2 update

14. DO NOT REBOOT

15. Flash Nightly

16. DO NOT REBOOT

17. Flash gapps

18. NOW YOU CAN REBOOT :)

19. You will now reboot into a completely virgin android / cm7

20. Follow the standard virgin android setup instructions.

21. You should now be on the virgin CM7 screen. Open market and download TB.

22. From TB restore all user apps you want WITHOUT DATA

23. Restore ADW (or whatever launcher you are using) WITH DATA to get as much of your desktop back as possible.

24. Restore DATA for apps you might not want the pain of resetting accounts or user information for (e.g. in my case, dolphin, gmail, touchdown, craigslist, etc), or games you might not want to lose progress in.

25. Return to desktop.

26. Run ROM manager. DO NOT BELIEVE IT WHEN IT SAYS CWM IS FLASHED OTHERWISE REBOOT TO RECOVERY WILL CRASH, flash an older version of cwm, then flash the latest on top.

27. Return to desktop and reset the widgets that have broken.

28. Reset any CM7 options you prefer.

29. Enjoy

I personally like this method because it requires just the NC, and just the flashed CWM.

Hope that helps!
[Nook Color Android Development] bonobomidwest:
Okay i take it back... flashed the latest CWM and back to the stupid bootloops. I'm sticking with 3.0.2.8 folks!
[Nook Color Android Development] khaytsus:
Clockwork cannot cause boot loops in CM7, it is an entirely different kernel and ramdisk.
[Nook Color Android Development] bonobomidwest:
I think we've disagreed on this before. :) There's a lot of documentation of the problem in the CM7 user thread when 3.2.0.0 was intriduced. Also the OP for the CWM thread mentions this issue too.

Perhaps we are thinking of something different - what i am describing is that the NC boots normally (i.e. what you're getting at i think, that normal boot does not involve CWM) unless you have asked it to boot into recovery, at which point it either fails and boots normally, or it bootloops.
[Nook Color Android Development] bonobomidwest:
It looks like once 3.2.x.x is flashed, even though you can flash 3.0.2.8 there is some kind of fight... there's a few threads popping up where smarter people than me are adb-ing into the boot directory and seeing files that shouldn't be there reappear.

Anyways, for those of us who are not android devs, the solution i have found was to boot from my CWM bootable SD (because any attempt to boot to recovery failed). Reflash the nightly to overwrite the /boot. Then in rom manager, reflash 3.2.0.1 - even though this is so instantaneous it looks like nothing is being flashed, it magically fixes the problem :) Just reflashing 3.2.0.1from rom manager without reflashing the nightly's /boot does not fix the problem

Go figure
[Nook Color Android Development] boxcar8028:
I flashed n97 + dal's new kernel 6/9 last night and was really hoping for a fix to my SOD and NDS issues. all is running well, new kernel is so smooth and zippy. but I'm getting lots of SODs. I think I'm getting deep sleep but cant be for sure because of SOD. after rebooting all logs in cpu spy has been re-updated. I think I'll flash n98 without OC kernel and see what happens.

cm7 n97 + OC 6/9 conservative gov min300 600 800 1000 max1200
[Nook Color Android Development] boxcar8028:
so, I just want to make sure that re-flashing to original B&N rom 1.1 or 1.2 and then flash back to a cm7 nightly has worked for you in fixing your SOD and NDS issues. I have read this before but is a little reluctant to try because of all the work that is needed. do you think a factory reset can also work? or is it the same thing. maybe I'll just need to bite the bullet and just do it.

btw: how is your nook running now? is all still well. :)