yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] bonobomidwest:
Well everything was perfect until i installed dal's new kernel today. Then i had a SOD almost immediately afterwards. Did a little experimenting based on the circulating theory that SOD is actually awake but no screen. Plugged it into my PC - the PC ding-dongs and pulls up the nook's drive (suggesting that the nook is awake). I then held power on the nook for a hard shut down, the PC dong-dings as the nook disconnects. Then a regular startup rebooted. no problems since.

Honestly, it was misery for me before (i.e. SOD every time i turned my back on the damn thing), and well worth the effort. Once you have everything downloaded the whole process takes about 10-15 minutes of flashing (not least cos you can do it in one session) and then 5-10 minutes of restoring everything with TB. After that the only minor pain is resetting any widgets you had (TB does a better job of restoring your ADW desktop than ADW does... with TB restoring ADW with data gets everything but the widgets back).

The biggest heartache was the complications with CWM... I'm now not having any problems with it on 3.0.2.1 (i always use the manual restore though).

I had tried just a factory reset before, but that was not enough to fix the SOD. There's something constipating either /boot or /system that only seems to get cleaned out by taking it completely back to stock. If i was feeling particularly masochistic i guess i could restore old /systems or old /boots from backups i have of 96 which suffered SOD, but right now i'm happy and if it ain't broke...

I've just upgraded to 98 and flashed 06/09 over the top of that so i will keep you posted.

Hope that helps
[Nook Color Android Development] jared_c:
Solved my SOD issues...by moving from class 6 SD to class 2 SD

OK, so, as the title says, I've been having SOD issues while running CM7 on a class 6 SD card. Specifically I've been seeing it since we hit the mid eighties in the nightlies. Now, there's been plenty of other problems that I've attributed to the "high speed" SD card as well, things like random FCs on apps (the xda app was probably the worst, never got it to even open), slow boot times, sometimes get stuck in boot loops (restarting the skateboard animation at 5-10 seconds), etc. But worst of all was how flaky the wifi was. I would turn it on and it would be a complete crap shoot to see if it would start up or error out. It would fail reliably if the system was busy, e.g. too close to boot. As my boot process was driven by disk access speed that hints that it would fail if the disk was too busy/queued out too far. It would usually work when I waited two or three minutes before turning it on.

Sometimes wifi would crap out in the middle of a session, this was pretty normal when downloading a new nightly with firefox or dolphin, though strangely not when downloading with opera. When this happened gapps would immediately crash/FC almost without fail. The browser would also crash and then FC when I restart it, over and over, until I reboot...(I never checked if the kernel remounted the drive as read only, but it may have if there were big enough problems, I was always too focused on getting the latest nightly) Wifi would stay errored until I rebooted too.

Now, like I said, I fixed all these issues by purchasing a class 2 SD card. I made no other changes. I literally dd'ed my current setup from the class 6 to the class 2 card. It's been working like a charm for 2 days, no issues.

This suggests two things:

1) at least some of the SODs are caused by slow flash chips. This is probably true for the emmc folks too, as flash chips are like snowflakes, each one is unique. Is there a benchmark tool out there that will allow us to evaluate the emmc on sequential and random read/write speed? That test would prove or falsify this hypothesis.

2) The devs who can't reproduce the SOD could do so by purchasing a class 6 or class 10 card. Shoot, I'd be happy to mail you mine, useless thing that it is.

Edit: see http://xdaforums.com/showthread.php?p=12964262 for a discussion on SD card speeds, benchmarks, and results/symptoms.

Edit 2: a corollary of item 2 above is that a possible solution to SOD is running off a decent SD card instead of emmc. Number one rule of debugging: if something works in one place and not another, always suspect the differences.
[Nook Color Android Development] Colchiro:
My class 6 sdcard crapped out after 5 weeks, then I saw this and ordered a class 4 from Amazon: http://xdaforums.com/showthread.php?t=1005633

There's links to some on Amazon here: http://androidforums.com/motorola-droid-x/348043-replacement-micro-sd-card-recommendations.html
[Nook Color Android Development] bonobomidwest:
VERY Cool

Wouldn't the key issue be if the diffierent NC builds have different eMMC chips - they're probably not using a random assortment for the very reasons that you point out...

...did you image from one uSD to the other? If so then this is something very different from the eMMC SOD I've seen at least, where you can transfer the SOD problem (or remove it) with a CWM backup (which is an image, essentially).
[Nook Color Android Development] jared_c:
Does SOD occurrence correlate with different NC builds? I was under the impression that it didn't. And you don't just see variations in performance from a random assortment of chips, you see significant variations in performance from chips from the same WAFER, much less the same manufacturing lot. It's inherent in the manufacturing process. Fabs just work around it in flash chips by making them slightly oversized, testing them heavily, and simply marking each area with flaws as a bad block. That's why every SD card has a slightly different size. And there are flaws that affect speed directly, you just have to bottleneck the wrong circuit and it will affect a few blocks, a lot of blocks, or the whole chip. Would B&N's spec to their emmc chip provider have ruled all these out? Maybe. But these specs are usually specified with a mean and standard deviation, and there's always SOMEBODY that ends up with a 3 sigma part...

All I'm saying is that there's a lot of variation in hardware, and though we can work around a lot of it in software, it's not guaranteed that any specific workaround will always work.

Anyway.

Yes, I first tried to image directly from one card to the other, but the new card was slightly smaller than the old card (both marked 8G), so that failed. So I set up the new card with verygreen's installer, installed the latest nightly to get the partitions setup, then dd'ed partitions 1, 2, and 3 from the old SD directly over 1, 2, and 3 on the new card. I think those are /boot, /system, and /data. I then mounted both partition 4s (the new one was empty) and copied the files over directly. That partition is /sdcard, and simply gets all the space that's left after the other three partitions are setup, so that's the one that was a different size. So, yes, very close to a direct image, but not exactly. The devil may be in the details, of course.

Do you have a CWM backup that consistently gives SOD? You could MAIL that to dalingrin or fattire or somebody as something reproducible. Or, to save on postage, find some site that allows huge file transfers...
[Nook Color Android Development] jared_c:
benchmark?

So far the best benchmark tool is SD Tools, but he's only testing the SD card, and I'm pretty sure it's just measuring sequential, not small block speeds.

Still looking...
[Nook Color Android Development] jared_c:
J Disk Benchmark 3.0 seems to be closer to what I'm looking for. Will do both emmc and sd card, can vary file sizes, but the smallest file size is 10 MB. I doubt that counts as small block size...shoot this would be a simple shell script. dd from /dev/random to a file, nested in a do loop...I guess it would be easier in python...
[Nook Color Android Development] pmilford:
WiFi off

(Quoting myself below)

I have been having several SOD per day. I found I had to plug into charger to

revive NC - not much fun to use the NC this way.

I turned off WiFi using the system settings menu. I have not had a SOD since

(no SOD for ~48 hours). I turn on Wifi to use it, then turn it off when I am done.

I did see other posts with wifi off and no SOD.

[CPU spy reports 23 hours of deepsleep of about 25 hours since unplugged.

SystemPanel reported cpu usage with screen off has dropped, so I'm sure

applications updating/syncing are behaving very differently too.]

Hope this helps track down the problems.
[Nook Color Android Development] khaytsus:
Anyone had SOD on Daligrin's 0609 OC kernel? I haven't had SOD for the 2 or so days since I started using it, and I regularly get 1 SOD a day.

Not sure it matters, but I have it set to 200/300/600/800/1100
[Nook Color Android Development] ryan5783:
I was having numerous SOD issues per day until yesterday when I changed the CPU governor from Conservative to OnDemand. Since then I have not had one SOD.

Deep sleep is still working. Left the nook last night at 95% battery remaining, was still at 95% this morning. WiFi is set to turn off with the screen, and I have a good number of widgets running.
[Nook Color Android Development] boxcar8028:
Thanks for your advice, it was helpful :) well, I was just about ready to re-flash to stock B&N and start over, but lots of new stuff came out this weekend. I flash 3 new nightlys and dal's new kernel and app. so far my SOD has been to a minimum with some deep sleep. playing with the wifi on and off seems to all so help a bit. but can't seem to pin anything down though.

there's talk about the new OC kernel being the reason for SOD and a modify cfs version of the kernel is available to try here:

http://xdaforums.com/showthread.php?t=925451&page=330

see post 3298

I'll try this tonight and report back.
[Nook Color Android Development] pryonix:
hi guys,

this might seem a tad weird but i have

completely eliminated SOD

from my Nook Color by remapping the home (n) button to "back" instead of "home". Prior to this, I kept getting SOD every other time I try to wake up the nook after leaving it alone for more than an hour

i read somewhere in the xda forums that people who always use their power button to wake their nook up never experience SOD and that i always hated the fact that the biggest key on the nook was useless ("home" is a useless key for me).

this gave me the inspiration to re-mapped the home (n) button to correspond to the "back" key instead by editing /system/usr/keylayout/qwerty.kl (it's a linux text file. i used jota editor to edit it) since i cannot train myself to use the power button instead of the "n" button to wake the nook --->

EDIT: my signature lies. I'm using CM7 96N.
[Nook Color Android Development] sinanju:
Yes. Today.
[Nook Color Android Development] :
Yep. No computer near, so only a last kmsg.

pastebin.com/AtMSvr7v

So fyi. Had troubles with 6/9 kernel, so went to 5/23. Had sod, so flashed back to 6/9 (which I think is captured in the log). Will try things out. Had sod since nightly 98. Only new app has been system panel. If I get sod again, will uninstall system and try again.
[Nook Color Android Development] bradputt:
Hey guys, there's a 6/13 kernel out. It may solve the sod/sleep problems.

Give it a try.
[Nook Color Android Development] khaytsus:
Overall, less? I had one SOD on 0609 in four days or so vs my typical 1/day average.

I'm on 0613 now, see how that does.
[Nook Color Android Development] sinanju:
I loaded it up and, to apply the test that causes SODs for me most frequently, left WiFi on as I turned off the screen.

SOD, right out of the gate. I'm sure it will go away as long as I manually manage WiFi.
[Nook Color Android Development] frankusb:
From a co-worker's Nook:

Description:

Nightly 97

Dalingrin's OC 5/23 set at 1100MHz Max

It happened when I used the power button to shut off the screen. This appears to happen when you have recently turned the screen on and sign in, but decide not to use the Nook so quickly power off the screen. Note that on this last occasion wifi was on since the Nook was recently used. This has happened about 5 times with the same scenario over the last month (not all the same builds or OC kernels). Finally got a last_kmsg.

Unhandled fault: external abort on non-linefetch (0x1028) at 0xfb03e000

Internal error: : 1028 [#177] PREEMPT

last sysfs file: /sys/devices/platform/omap_pwm_led/leds/lcd-backlight/brightness

Modules linked in: tiwlan_drv

CPU: 0 Tainted: G W (2.6.32.9 #63)

PC is at __copy_from_user+0xac/0x3b0

LR is at show_data+0x94/0x118

pc : [<c01efbfc>] lr : [<c0036d0c>] psr: 00000193

sp : df8139fc ip : 0000001c fp : df80f9c0

r10: 00000000 r9 : 00000000 r8 : 00000008

r7 : 00000004 r6 : 00000000 r5 : fb03e000 r4 : df812000

r3 : 00000000 r2 : ffffffe4 r1 : fb03e000 r0 : df813a24

Flags: nzcv IRQs off FIQs on Mode SVC_32 ISA ARM Segment kernel

Control: 10c5387d Table: 9c9e4019 DAC: 00000015

Frank
[Nook Color Android Development] boxcar8028:
Its to bad dal's new kernel 6/13 is not helping everyone with SOD. but I do have to say that for the first time in a long time my nook is now deep sleeping. so far I haven't had any SODs with new kernel (with fingers cross) :)

with SOD, for me I have also found that it helps to turn off wifi and then reboot. turn wifi back on after reboot.

cm7 n100 my nook tweaks setting are: cpu governor set at conservative. stepping at: 300, 600, 800, 1100, 1200.
[Nook Color Android Development] BitingChaos:
Wow, just had my first SOD in many days.

Build 100, clean install, stock kernel. I connected to WiFi at home, tucked my Nook Color away and came to work.

It wouldn't respond to hitting the "n", hitting power, etc. I first thought my battery drained somehow. I held power for a few seconds, released, then held it again. It booted up with 70% battery.
[Nook Color Android Development] boxcar8028:
this is more of a no deep sleep issue then a SOD issue but for me the two are related. I've already posted this in dalingrin's OC kernel thread but thought to also post here so more people can try.

"up tell last night my deep sleep has always been spotty at best, 1-5% here and there but never in a large block of time as in over night and a SOD now and then. but last night I noticed that there was a new wallpaper from cyanogen it was named NO wallpaper so I thought to try it......

well to my amazement my nook totally start to deep sleep normally. I mean really deep sleep for long periods of time and it would start up all the time and this was also true with or with out the OC kernel same results. it didn't matter after charging after a reboot turning wifi on and off all was the same good results with no SOD. but as soon as I added a wallpaper it would revert back to the ****ty sleep as in the past. it didn't matter if the wallpaper was animated or not. but as soon as I go back to NO wallpaper all is well again. I can go back and forth and reproduce this all the time with out having to reboot. can anybody with sleep issues please try this to see if it would work for you".
[Nook Color Android Development] pchoi94:
You know what, I have nightly 97 on mine, and had kept the stock wallpaper on it for a while (meaning a few days) just because I never got around to changing it, never had a single SOD. But I noticed that as soon as I started playing around with trying out different wallpapers (last couple of days), i started getting SODs, multiple a day.

Do you know which build has the option for no wallpaper?
[Nook Color Android Development] boxcar8028:
not sure which build it started on but I know for sure it was on nightly 102, Im on n103 now. today I tried some new non-animated wallpapers and my nook seem to be sleeping fine and with no SODs. so it must had been the live wallpaper that killed my deep sleep
[Nook Color Android Development] bonobomidwest:
First SOD in days

Hi guys,

Is this a big a faceplant for anyone else as it is for me?

I just had my first SOD in days (and it was the monster SOD - as in the screen is off the NC is on, and only a hard shutdown and a powered restart brings it back to life).

This was the first time i had left the NC long enough to enter deep sleep... since... wait for it... installing the one app 50% of us all have in an attempt to resolve this problem... namely battery monitor widget... (i hadn't reinstalled it since a completle wipe i did a while back)

battery monitor widget has some settings that imply it keeps running in the background... I'm wondering if it is interfering with proper entry into deep sleep... i.e. the theory that has been floated for several other apps int he last few weeks

Before casting further aspertions i will now uninstall it and see how i do...
[Nook Color Android Development] pchoi94:
I have never installed the battery widget on my current build yet I have had sleeps of death. Multiple per day lately. Build n97 since it was out.
[Nook Color Android Development] dalingrin:
Multiple per day? Thats just crazy considering I've never had a single SOD.

Anyone having an SOD needs to give as compete information about your setup as possible.
[Nook Color Android Development] ular_king:
I just found out that if you try to install remotely via market.android.com it will SOD!
[Nook Color Android Development] pchoi94:
Hi Dalingrin:

Yes, multiple per day for the past few days for some reason, sometimes 2 or 3 times within 20 minutes. Note: I do not have any of your OC kernels installed, I'm using the stock kernel that came with CM7 N97 build, and I am running at stock 800MHz speed with Conservative governor (as it came). I have not touched OC settings at all. When I have SOD, sometimes I can tell it's awake but the screen is completely off, no backlight. The way I know it's up is because after I press the power button and waiting a bit I can hear a new mail notification. Sometimes I get nothing, but it could just mean no new mail. I try touching the screen, pressing the N button, pressing the volume keys, pressing the power button more, nothing wakes the screen. Then I have to do a hard shut down and boot up again.

This is what I have on my NC:

1. CM7 N97 - Fresh install on a fresh new 8GB Class 2 uSD from Costco (bought new, ran speed tests, then reformatted using the HP format utility doing a full format, which took a pretty damn long time I might add)

2. gapps installed from the link in the size agnostic CM7 thread

3. Apps:

Pulse

Lotto Results (this was installed after the SODs)

Astrid Task/Todo List

Taptu

LauncherPro Plus s32 CLEAR theme

SiMi Clock Widget

Quadrant Standard

SD Tools

Evernote

Angry Birds Seasons

Angry Birds Rio

Angry Birds

2X Client RDP/Remote Desktop

Kayak Flight and Hotel Search

imo instant messenger

Opera Mobile browser

Aldiko Book Reader

ES File Explorer

LauncherPro Plus unlocker

LauncherPro

Youtube

Street View on Google Maps

Twitter

Google Chrome to Phone

Gmail

Facebook for Android

Dr. Seuss books (sideloaded from apks)

Tapatalk (sideloaded from apk)

Amazon App store (sideloaded from apk)

Fancy Widget Pro (sideloaded from apk)

HD Wallpapers (I've since uninstalled this)

4. I have 4 gmail accounts set up for sync, some with mail sync, some with calendar sync, some with contacts sync. it's a mix.

5. I am using a pattern lock screen, I've had it that way since day 1 right after I installed the N97 build.

6. Note: After I saw the post above mentioning wallpapers, I realized that my SOD problems "seemed" to start after I started playing around with different wallpapers. I never had one single SOD until I changed the wallpaper from the stock CM7 wallpaper that came with the ROM. So then I decided to revert the wallpaper back to the same one that came with stock (the android dude on the skateboard), and I uninstalled HD Wallpapers, and I haven't had a single SOD since. This is coming from 2 or 3 days of constant, multiple SODs per day. I have not made any other changes than those two things. Coincidence? Probably. I don't see how changing your wallpaper or installing a wallpaper app can cause SODs. But who knows...
[Nook Color Android Development] dalingrin:
Perfect thank you for posting all the info. Keep us posted on your SODs the change in wallpaper.
[Nook Color Android Development] Ptaaty:
I decided to give CM7 a try again because I heard deep sleep was enabled.

I installed nightly 100 (SD card method)....with the kernel that came with it, no OC, on demand governor.

Initially it did sleep all right....so deep it wouldn't wake up (SOD apparently what it is called). Similar behavior to pchoi94, could tell it was still working in the background just no screen. In fact battery drain was higher than screen off/no deep sleep. To get it back I had to hold power button to turn off then power up (obviously not completely off while in SOD).

So I went to manual toggle on wifi...turning it off and letting the nook go into sleep mode itself using screen timeout (never push the power button). No more SOD....also no more deep sleep. Now I am back to the same continuous battery drain I had before, typical of a device not going into deep sleep, android system as the battery use.

This thread is an attempt to track it down, but I don't really know what or if there is a fix. I guess I can say for me that going into deep sleep has something to do with wifi policy.

Not sure why it won't come out. I believe twice I was able to have it go into deep sleep and actually come out of it, but never goes in at all with wifi toggeled off.
[Nook Color Android Development] slugbug2010:
Ok. I just read this thread all at once. One thing that sticks out to me is this: is there a definition of what SOD and NDS means to everyone?

That was the main reason I was reading. I wanted to find out what is was, if I have it, how to watch for it, etc.

I have had my NC since February but am new to CM7 as of a few days ago. (I was running HC v4 previously and still have that on a different sd card) I am on 102 with Darl’s 6/13 oc’d kernel. I went to bed last night and plugged my nook in. I took it off the charger this morning and it was clearly green. I turned it on at work 4 hours later…..65%. Pressing N did not work so I held the power button for several/many seconds until the cm screen came on. So what does that mean? Is THAT SOD?

I needed to do a back up so I did that. I’ve not turned it off and it’s been sitting on my desk. I can now hit N and the percentage has not dropped at all.
[Nook Color Android Development] schtuka:
So, what would be standard procedures to prevent SOD? What should I look for? Just a little guidance.

I have stock 1.2 and I flashed your Froyo 06/13 emmc and getting one SOD over night. Nothing during the day. It happened at 1200 and 1100 OC via SetCPU on demand and your NookTweaks.

I got one screen with widgetsoid, fancy widget and srceen off widgets on ADW.
[Nook Color Android Development] boxcar8028:
that's the whole point guys, no one has been able to pin this bug down to a fix or a workaround, that's why dalingrin has been trying so hard to resolve this. its not easy, its not connected to one or a combo of things and to make it worst the dev's cant seem to reproduce this. some people had luck messing around with the wifi on and off and re-bootings. people had gone back to B&N stock and started over. for me a clean wipe of data, cache and dalvik and then a fresh flash and install and no live wallpaper helped me with SODs and NDS. Im still having some issues with long over night deep sleep.

http://xdaforums.com/showthread.php?t=925451&page=347

see post 3470:

its good to report that PDB has been fixed with the magic from fattire. so, if you guys can contribute any information about your SOD and NDS issues will be helpful. :)
[Nook Color Android Development] rhester72:
http://xdaforums.com/showthread.php?t=1128278
[Nook Color Android Development] :
Oh thank god. We have a 100% reproducible SOD method now :)

...and Dal got it!
[Nook Color Android Development] khaytsus:
Hopefully this is the same for all "types" of SOD, but what the post describes there is quite different from what I and others have seen where the NC is completely dead.

His post describes something different, and I've seen others say the same, is that their screen is off but the NC is otherwise alive.