yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] :
Since nightly 97 (or right around there) I got an SOD where I could hear the beep on the volume changing to max. I have NEVER had an SOD before. I thought it was just a fluke, but then it happened again. I didn't really do any documentation (since somewhere around there I flashed the newest kernel, and didn't know which caused what). I also installed battery monitor pro. I went from having a day with three or so SODs to maybe 1 per day after uninstalling BMP, but I also flashed the latest nightly, so again...not sure what's up. I just hope the devs get some insight as to what may fix it. Maybe one fix will fix all varieties! (crossing fingers)
[Nook Color Android Development] NuShrike:
This effing sucks.

Build 103 of CM7 -- complete SOD. Won't restart while plugged in with normal micro-usb and power button held for 8, more or less. Will have to wait until I get home and plug in the nook microusb, I guess.

The only change I've done recently was turn WiFi policy from turn off with screen, to never turn off.
[Nook Color Android Development] :
Sounds like PBD, not SOD.
[Nook Color Android Development] NuShrike:
Nope. Got home, plugged into Nook cable, finally rebooted, 85% battery. PBD impossible.
[Nook Color Android Development] paleh0rse:
Actually, if it required the charger to be plugged in, that IS more in line with PBD than SOD. In fact, that's always been what differentiates the two problems.

That said, PBD doesn't normally occur at anything close to 85%, so it sounds like you had a different type of kernel panic altogether. Grab the last_kmsg by chance?
[Nook Color Android Development] gt50:
SOD started occurring for me after I upgraded to versions of CM7 with the 2.6.32 kernel. I held off from upgrading until I read reports that AES seemed to be working on wifi. I stayed on N75 for a while.

After upgrading to the newer versions a few weeks ago, I experienced SOD. I have been fighting with this for weeks. Some nightlies seemed to be better than others. A couple of times I was able to get several in a single day. I tried different max cpu speeds (800 and 925), and all of the governors with no luck. Wifi is set to always on.

Yesterday I disabled the "disable lock screen" setting, and my nook seems happy now. No SOD in the last day. I am currently running N121. My battery life seems to have drastically improved also while asleep. Seems to be about 0.5% per hour drain while sleeping.

I think N111 was when I started using the nightlies again after waiting. I had some issue installing and had to use my sdcard to do a fresh install. Up until this time I had used the standard lock screen.
[Nook Color Android Development] Jdoggjp85:
SOD

Hey guys

I Usually don't post but i read every post here. I just wanted to post to see if i can help, now i have never had SOD until recently going from 7.0.3 to latest nightly and 6/30/11 kernel. It was happening very randomly for me sometimes it would be fine and sometimes it just didn't wake up and after rebooting the battery was drain dramatically. what i started doing was disabling the wifi and the background data sync and that seem to be a workaround for me. 2 weeks going that way and no problems. i Know that might be an inconvenience because you wont receive emails or what not.
[Nook Color Android Development] dalingrin:
Are you signed into Latitude in Google Maps. If so, you might try signing out and then keep your wifi and data sync on.
[Nook Color Android Development] Jdoggjp85:
im not sure to tell you the truth but i will check tonight and i will report back with you guys.
[Nook Color Android Development] TheAmazingDave:
Two SoD's today, I've logged them both. I never had any before switching to the 6/30 kernel.
[Nook Color Android Development] Jdoggjp85:
So far after signing out of latitude no sod yet. Will do give it a day or so more of testing.
[Nook Color Android Development] khaytsus:
Yeah, same here, for about two weeks I've had wifi disabled at screen off (Tasker or Setting Profile Lite, the Advanced options in the Wifi menu for me seem to do nothing) and I haven't had a single SOD in a few weeks.

As said, you'll have to track down anything holding wakelocks if you were previously using wifi all the time as you're probably going to expose some, the biggest one I had was Latitude. I just cleared data on Maps, as I don't need latitude there, although it was handy to see where folks were on the tablet. Maybe I'll try it again, they made some battery improvements recently.

The good thing is I also went from charging every night with reasonable usage, sometimes every two days if I didn't use it a lot, to 2-4 days between charges. Wifi on kept email, accounts, market, weather, etc syncing..
[Nook Color Android Development] I Am Marino:
Anytime I leave wifi on and my screen goes off, that's usually a big part of my SODs.
[Nook Color Android Development] Jdoggjp85:
sod

ok after a 2 days or so of signing out of latitude its been going with out any issues.
[Nook Color Android Development] GunBalina:
I got a few SOD before, but today I got several in a row.

Got several while using talk and letting the screen go off, while the app was on screen (it would not happen if I was in the desktop).

Got two while using greader, once again, it would only happen when the app was on screen.
[Nook Color Android Development] Phatdawg:
SOD's that I have now come up with a message about theme crash when it reboots. Not sure if this is a generic message for SOD.
[Nook Color Android Development] dalingrin:
interesting observation.
[Nook Color Android Development] GunBalina:
Today I got another one, but I was on the home screen. So maybe it's unrelated. Still, I was running talk and greader. I will try to get some more SODs and make sure that they always happen.
[Nook Color Android Development] crandy2:
Right after N136 came out, I posted my problem here http://xdaforums.com/showthread.php?t=960542&page=433 Post 4321.

I got no reply, so I thought I would post the followup data here, since it seems to be related to SOD (I guess).

I had the problems mentioned in the referenced post, then flashed back to N128 and the "SOD" problem totally went away. Flashed back to N136, and they reappear.

I found where people had mentioned pressing the power button and waiting up to 5 minutes. After pressing and waiting, I find that it does come back up after about 2 minutes. When it returns, all the apps I had open with I pressed the power button to turn off the screen are now closed. I get a screen on animation no matter whether this is checked or not.

I am attaching a zipped copy of my last_kmesg. Any help or comments would be appreciated.
[Nook Color Android Development] dabiddabird:
Idk if this doesn't work for everyone or its simply being overlooked. But for me I would get SOD since cm7.0.3 and even on nightlies.

Before I would leave wifi to sleep when screen off and after an hr or so I would get SOD. Changed it to wifi always on put to sleep again hr or so later SOD. Changed to sleep when plugged in same after hr or so SOD.

However, if I manually turn wifi off before I put my Nook to sleep I will not get any SODs. Ever since I have been doing this I have not had one SOD.
[Nook Color Android Development] DigitalMD:
I know 136 build caused problems for several people. It totally hosed my boot and I had to repartition the Nook and return to stock and reinstall CM7 to get going again. I skipped 136 and went to 138 and all is well again. I suggest you return to 133 or go to 140 build.
[Nook Color Android Development] khaytsus:
136 is fine.. You must have had some other issue, I've been on it since it released.
[Nook Color Android Development] Jdoggjp85:
Ok same issue again, definitely not latitude is wifi related for sure. I went back to turning wifi of and sync off again to prevent is from sod.
[Nook Color Android Development] paleh0rse:
Same story here... n136 was rough. lol
[Nook Color Android Development] STaria:
One of the first things I did after flashing CM7 was set the WiFi sleep policy to off when the screen is off. I still got a SOD pretty soon after that.

On another poster's suggestion I left the sleep policy at "never" and set up a Tasker profile to turn wifi on/off with the screen. Haven't had a SOD since, about 2 weeks.

So yea, give Tasker a try. The built in sleep policy just doesn't seem to do it.
[Nook Color Android Development] Phatdawg:
I'd just like to hear from the devs about what they think is going on in regards to SOD with the nook at this time. It appears to be narrowed down to wifi connection and it seems to be such a pervasive issue. A lot of us would like to have information push while asleep and so this really limits the tablets quite a bit.

Since both phiremod and miui run of CM7, I am sure they get SOD as well. I have gotten SOD on the MIUI rom a few weeks ago before i reverted to straight up CM7.
[Nook Color Android Development] Phatdawg:
http://xdaforums.com/showthread.php?t=1185524

The above thread in the general section mentions that adjbrightness to being an issue with SOD.

It appears to be that the nook is still "on" as we all know but the "screen" won't turn on. So the function appears to be with that particular call, if adjbrightness, causes the SOD routinely, perhaps seeing how that program causes this, might give us a solution.

Crossing fingers.
[Nook Color Android Development] rhester72:
There's no doubt this is _a_ form of SOD (and, like the last one to be fixed, is quite reproducible). Unfortunately, I still believe there are yet-to-be-discovered issues with the wifi driver that are causing the majority of them.

Rodney
[Nook Color Android Development] Phatdawg:
I don't doubt that the wifi issue is one of them but I wonder if the way _OUT_ is all the same.

For example there may be a lot of ways to induce SOD, but the solution may all be an issue with the wake process as opposed to going to SOD.

I guess what I am saying is that something puts them into this state in particular but the way out may all be the same and hence solving the wake part of it might be all that's needed as opposed to what's inducing the system to SOD.
[Nook Color Android Development] rhester72:
dalingrin doesn't seem to think so, and given the first wifi SOD fix didn't fix any others, it seems unlikely.

Rodney
[Nook Color Android Development] Phatdawg:
I have recently downloaded droidwall and am going to try to keep my wifi on always and gradually add/remove services over the next few weeks to figure out which app(s) may be a problem.

So far, I started up droidwall and enabled all of the wifi that I normally would expect and of course, I got the SOD. I am going to remove all wifi permissions today and start adding them one by one.

I hope some others here will be able to try this approach and maybe we can get a list of offending programs over time.

Thanks, as I find issues, I will post them here.
[Nook Color Android Development] Stamgastje:
I'm not using this ROM, but I experienced SODs with two other ROMS: teppic74's Pre-rooted Stock Froyo (2.29.405.5) and more recently, baadnewz's InsertCoin STOCK 1.0.9. In both cases, the SOD happen only when I'm (temporarily) out of reach of 3G (WCDMA) networks while the phone is sleeping and the problem completely disappears when I disable the use of 2G (GSM) networks, i.e. setting the "Network mode" to "WCDMA only" instead of "GSM/WCDMA auto" (see this topic).
[Nook Color Android Development] Animec:
I dunno 'bout SoD or wifi issues, but I've had to revert to 7.03 because, with more recent builds, the display will sporadically refuse to turn on. It looks just like SoD and takes forever to hard reboot, but it's clearly just the display that's off. If there's a game running I can hear the game. When I press the N button, the sound stops and I assume it returns to the home screen.

It's a damned shame because the recent builds are otherwise pretty fantastic!
[Nook Color Android Development] stolenmoment:
I just had a wild thought. While pursuing something else, I noticed that in /system/usr/keylayout/qwerty.kl, the HOME and POWER buttons are marked WAKE. However, they act more like WAKE_DROPPED (that is, when the button is pressed and the screen is off, the screen wakes up, but the press isn't passed to the app).

So clearly, there's some code somewhere that treats HOME and POWER specially, ignoring or modifying the setting in qwerty.kl. Could some inconsistency with this be making these buttons not behave as expected? Or is this necessary to get the long-press behavior right?

I also can't help but think that plugging in the charger while the NC is off and getting the backlight on has something to do with SOD, but I don't know what. In this state, HOME cannot get the screen to turn on, but a long press on HOME brings up the "Recent" panel (although you have to tap POWER twice to see it), and screen touches are listened to.

The other thing I was chasing was setting the vol+- buttons to take effect but not wake up the screen; change them from WAKE to nothing. Now, when adjusting the volume while the NC is in my bag, the touchscreen is still disabled and I don't get phantom touches from the bag itself.
[Nook Color Android Development] leapinlar:
Have the devs completely given up on trying to solve SOD?

I know there is a lot of chatter in the other threads on work arounds, like using third party programs like Tasker and Green Power to turn off wifi when the screen is off, and there has been some success with those. But those work arounds do me no good because I need wifi on when the screen is off. I use Google Voice to text and wifi needs to be on to receive a text when the screen is off.

I have my own work around that simply prevents the NC from ever going into deep sleep so I can keep wifi on all the time. (I use SoftLocker Free). That makes battery life worse, but I plug in every night anyway so it works for me. This allows me to have all the benefits of the new nightlies (except deep sleep) without having SODs.

However, I have friends that have NCs and also use Google Voice to text with me and they are not a techie like I am and I have recommended to them that they stay on 7.03 to avoid SOD. I will not advise them to go to a 7.1 version until SOD is fixed.

I am just trying to find out if there is hope for getting SOD fixed.
[Nook Color Android Development] dustrho:
Alright, so with the SOD crap going on with the NC, which is the absolute best and most stable CM version for this device? I've been running nightlies on it, and I am constantly having SOD with mine.
[Nook Color Android Development] :
Just turn off wifi on screen off. Problem solved.

Grab a log as well (wireless adb) to help the problem.
[Nook Color Android Development] leapinlar:
If you want to keep wifi on all the time, the most stable version to use is 7.03. All of the newer versions use the updated kernel that lets the NC go into deep sleep to save battery. Unfortunately, deep sleep and full on wifi eventually leads to SOD. The reason 7.03 is stable is the devs purposely disabled deep sleep to avoid problems. Therefore the battery life on 7.03 is not as good as the newer versions. But it is very stable with no SOD.
[Nook Color Android Development] tightwad:
I had my first SOD experience. Up until today I hadn't had a single Deep Sleep mode...so the battery ran down fast. I am using 7.1 stable. I don't have a ton of apps or widgets.

I am trying to determine which app or setting change allowed it to Deep Sleep. It did the SOD after I allowed it to go to sleep while in the mail app.
[Nook Color Android Development] leapinlar:
I don't think there is a 7.1 stable. The only 7.1s that are available are the 7.1 RC1 (release candidate 1) and the nightlies. None of those are stable. And all of those suffer from SOD. Are you saying you have been running a 7.1 version and you have never been in deep sleep? How do you know? Have you been checking with CPUSpy? Deep sleep per se is not bad, in fact it is good. It saves on battery. It is mainly when you have wifi activated while the screen is off that there is a problem. It seems that deep sleep and having wifi on while trying to sleep is when SOD happens and you can't wake it up.
[Nook Color Android Development] tightwad:
You're right, I did mean RC1. I actually wanted it to Deep Sleep, to save the battery. CPUSpy is the tool I have been using to monitor it.

I haven't made any adjustments to the wifi on/off settings.
[Nook Color Android Development] leapinlar:
The only thing I can think of that may have been preventing your 7.1RC1 from deep sleeping before was an installed app that was putting a wake lock on your system. Some apps do that if they need your device awake all the time. To keep the wake lock on, the app needed to run a service constantly in the background. You may have uninstalled/disabled that app or updated it to a newer version that did not have the wake lock. That would then allow your NC to deep sleep and could eventually lead to SOD if you had wifi set to stay on with screen off.

Not sure this helps you, but it's the only thing I could think of.
[Nook Color Android Development] arachne:
Well, 7.1 stable has been out for several weeks now, and I am sad to say that these problems still seem to remain in the stable version. I am running CM7.1 from an SD card and I have only run this stable version, never nightlies. My wifi is set to always be on. I am running a fraction of the number of apps you are, partly because my installation is so new! I still get heaps of SODs daily. My solution is to shut down the Nook Color whenever I'm done and reboot it when needed. Sigh.

I'm surprised nobody has commented since before 7.1 stable was released. I'm not a dev, and I wouldn't know where to look for logs etc, but I'd be happy to contribute information if someone can tell me what would be most useful for them to know.
[Nook Color Android Development] khaytsus:
Turning the NC off is easier than just turning off wifi? Do it manually, or let something like Setting Profiles Lite do it for you automatically... Another option is enabling a wakelock all of the time, with a penalty of standby time being greatly reduced.

It's not as if the problem has been ignored, I'm sure the devs have spent countless hours trying to reproduce and understand the issue. There are three workarounds, use one. Or keep turning it off....
[Nook Color Android Development] GTT1:
I recently posted a thread on this problem.

I can make it occur on a regular basis. With my Nook it occurs whenever I turn it off by pressing the power button. After being off for several minutes it will not wake with a press of the N or power button and I have to long press to turn off the NOOK then long press to reboot.

This problem started about a month ago when I was using CM 7.1 RC on SD which had been installed since it first came out. I hadn't updated anything or installed any new apps for months. The only changes that occurred to my NC were the change to different market app that occurred automatically and auto updates of ROM Manager.

My work around is to simply let it go to sleep itself, I have set it for 2 minutes inactivity. It also doesn't occur when I plug it in to recharge and turn of the screen with the power button.

Not sure if this can help anyone solve this SOD problem and I also don't know if it is what others are calling SOD
[Nook Color Android Development] leapinlar:
Seems there is news on this item. See my post in the CM7 general discussion thread, here:

http://xdaforums.com/showthread.php?p=19171304
[Thunderbolt General] mademan420:
I noticed on yesterday about 5pm, my Tbolt switched over to 4G:D for about an hour then went back to 3G:( I was getting around 15MB down and 3MB up testing it with various speed test. I also tested it with the Netflix app and in less that 5 seconds, the movie was streaming. Anybody else notice this in this HSV area?
[Thunderbolt General] Braggo:
Hey Huntsville buddy, I haven't had 4g turned on but you can be for damn sure I will right now. I'll post back if I see anything.
[Thunderbolt General] mademan420:
Alrighty....Just trying to spread some GOOD news for a change. Be sure to post again if I happen to get another glimpse of the "White Unicorn". LOL!!!
[Thunderbolt General] Character Zero:
Dang I must have missed it. I guess you have to be looking at your phone at the right time. Although I live in Madison, but 4G should get to me right? But since I work in Huntsville maybe I will be able to at least enjoy 4G during the work hours.
[Thunderbolt General] Eurasianman:
I noticed it yesterday too. I guess they were doing some testing. My guess is perhaps they'll turn it on next week... Thursday? Regardless, at least we know they have 4G towers up in HSV. Now just a question of when they will turn it on permanently.
[Thunderbolt General] Braggo:
I live in Huntsville but it's basically Madison and also work in Madison. From what I understand it should extend out here also. I know that Montgomery's 4g supposedly extends to Troy and some other cities so there should be no way we don't see 4g in Madison also.
[Thunderbolt General] Character Zero:
There hasn't been a press release so who knows when it goes live for real. I think I have my 4G off last night, I hope they flip the switch for a little bit this weekend.
[Thunderbolt General] mademan420:
Yeah I stopped by the VZW store on Uni dr. when I saw this yesterday and the REP said that once its turned on permenantly for this area, it will strech past Decatur. Im hoping this is the case since I live in Madison as well. He wouldn't give me a definiate time frame but he said it should be by the end of June.
[Thunderbolt General] Braggo:
By the end of June would be amazing. When I bought my Thunderbolt I honestly was thinking Fall at the earliest.
[Thunderbolt General] abn75:
Man I'm surprised Huntsville doesn't have 4g yet. They turned it on here in mobile last week
[Thunderbolt General] mademan420:
You know....I was thinking the exact same thing. Then I remembered that BHAM doesnt have it yet either. It seems like(at least in AL) that VZW in turning on 4G in reverse order rather than going from largest to smallest of bigger cities.
[Thunderbolt General] abn75:
Yeah it does seem of how the bigger cities don't yet have it while we do. I'm not complaining mind you
[Thunderbolt General] greenfday6:
I didn't notice 4g, but I'm on CM7 so who knows if I would have seen it. While I want 4g my battery wants it more.
[Thunderbolt General] mademan420:
So how's CM7? Been thinking about jumping the broom but with 4G so close, I want to be able to use it when its available.
[Thunderbolt General] greenfday6:
I was on 4g on 565 at about 6:45 today. Did a quick speed check before I lost it, 6444kbps down 13542kbps up.
[Thunderbolt General] greenfday6:
Battery life is still pretty bad, but over everything is working. Even got 4g today as you can see from my post above.
[Thunderbolt General] bamaredwingsfan:
I thought I read a while back where I65 an us hwy 31 was supposed to get 4G coverage. If so, that would pretty much cover Cullman city. where I live. Any else heard this?
[Thunderbolt General] cemysh33:
Yes Huntsville, AL will be getting 4G in about 30-45 days. So will decatur. Mobile and Montgomery already have it turned on. They have been testing the network in the are. My TB has been switching back and forth from 3-4g. I have customers come in the store asking this all week. It just around the corner!!!
[Thunderbolt General] Character Zero:
Dang I keep missing the temporary 4G. Oh well I will be driving though Nashville soon, so I will get at for a little bit.
[Thunderbolt General] mademan420:
WOOT WOOT!!!
[Thunderbolt General] k2trill:
It's working right now
[Thunderbolt General] Character Zero:
Still on 3G at the Arsenal.
[Thunderbolt General] mandog202:
NICE, I live out in Toney but work in Huntsville, I‘ve been keeping lte turned off, turning it on now!

no LTE near space and rocket center / research park yet

Sent from my BAMF 1.7'd Thunderbolt
[Thunderbolt General] droidisawesome:
No LTE in Research Park. I did notice that I had 4G a couple of days ago for just a few minutes before it went away.