yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
I have produced those logs. What I was doing originally was running

logcat > /sdcard/log.txt

in the terminal. But if you do not get SODs regularly, this file can get quite large.

However, I have found that my device is able to connect to ADB after SOD. So next time you get one, try and connect, I have also, on a tip from keyodi, found that connecting the USB infrequently awakens the device from the grey-screen SOD.

Here is my pastebin, containing dmesg before and logcats and dmesg post-SOD, if anyone wants to compare their SOD logs to mine. However, all of these are test-kernels from keyodi, and I wasn't told what the test parameters were.

The errors with wifi, I have a borked wifi chip, but the wifi/bluetooth is set to off.
[Nook Color Android Development] cybertimber2007:
A logcat is only from boot to the current moment.

So if you reboot after a SOD, the captured logcat will not show anything regarding the SOD.
[Nook Color Android Development] mateorod:
I am not sure if you are responding to me. But if you are, then if you enter that command into the terminal and then wait for SOD , it will save it to SDcard in live time, stopping at reboot.

It can then be retrieved after reboot, reflecting the SOD.

None of which is super pertinent if you can, as I could, still connect to ADB after SOD. But useful if you can't.

The drawback is, as I said, that the file grows quickly, so you wouldn't want to keep it running too long if you are limited in space.

Edit: I am guessing you were saying that that command isn't useful if entered after SOD. Which is true. I meant that I was using it before I had an SOD, in anticipation of that event since capturing it through ADB prevented sleep and therefor ruined the experiment.
[Nook Color Android Development] no_cannabis:
Logcat - yes, but if you spool the logcat into a file with ">" the file will stay on a storage device even after you reboot.
[Nook Color Android Development] raymasky:
For the love of god.. Can someone ease re upload the ROM to some other host? Am I the only person who's facing disconnections?? :
[Nook Color Android Development] no_cannabis:
This was my intention exactly, with only difference I just put my logs on the Google drive and take it from there :) And the fact that I couldn't reproduce the SOD in my case, the darn thing just wouldn't die with the terminal running in the background!

If you spend some time and find some errors before SOD, then you can fine tune logcat to spool only the messages from components that caused the errors, by using "componentname:V *:S" command line switches, where V is for Verbose, and S is for Shut-up :)
[Nook Color Android Development] eyeballer:
Yes, but can you PM me your IP address, so we can check the logs. The host is running without issue..
[Nook Color Android Development] raymasky:
It's a dynamic IP so I dunno if that will help. I'm using flashget and your host doesn't support multi thread and multi part downloads.. Nor will it let a download resume after disconnections. :(
[Nook Color Android Development] dparrothead1:
Have you tried d/l straight to your Nook. That's what I always do and then you don't have to move it.
[Nook Color Android Development] eyeballer:
Most dynamic IPs don't change that often.. if you try to download and send your current IP then we may be able to get some insight.

FYI the host does support multi-part and resuming, so not sure why you're having issues. Of course you can also try downloading without any download manager and/or adblock disabled to see if that helps. Nobody else has reported an issue, so I suspect it's on your end.
[Nook Color Android Development] bigbob23:
I've been busy with other things and just noticed this ROM. I am very impressed! The installation went quite smoothly.
[Nook Color Android Development] SGH-i200:
tablet mode?

I second that! :cool:

Tablet mode is the only thing that I'm missing.
[Nook Color Android Development] dparrothead1:
http://xdaforums.com/showthread.php?t=1944448
[Nook Color Android Development] Longstreet:
? for Devs re logs

I'm not setup with adb, and have used Lumberjack to post a few logs for other roms in the past. Will Lumberjack do for your purposes?

And since I'm not a developer would you like me to post them here or in the General Forum?
[Nook Color Android Development] cybertimber2007:
I had a backlight SOD and was surprised to find that I was able to use adb.

Captured logcat and dmesg before rebooting (survey submitted as well) - ES 1.2, SD install, wifi on, not charging, 36 hour uptime, 54% battery remaining, no non-standard widgets on home screens (only power toggle and google weather).

logcat - http://pastebin.com/kPNYc3EV

dmesg - http://pastebin.com/5fHT37QF
[Nook Color Android Development] steven676:
If you were logged in to your Google Account when you filled out the form, maybe ... but in any event, I've edited your report to reflect the new information (thanks!).
[Nook Color Android Development] davidr415:
Also worked great for me using TWRP and pa 2.99
[Nook Color Android Development] leapinlar:
I will sign the zip and re-upload. I usually don't have to do that, but will... Done!

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] Dave08:
Both versions failed to flash, same Status 2 error message in TWRP.
[Nook Color Android Development] pastordl:
Thank you, made my day.

Installed fine for me. Installed latest update (12/15), kernal zip, wiped cache, fix permissions. Running great.

Thanks so much.

Oops spoke too soon. The kernal did not install. Tried to install zip and got Status 2 error.
[Nook Color Android Development] deesto-xda:
Maybe I'm doing something wrong?

With 12/13 nightly installed: Settings -> About -> CM Updates, Refresh, download 12/15 nightly, which says "failed MD5 checksum". If I go ahead and click the icon and install anyway, CWM recovery tries to install on boot and says "verification failed". If I disable verification, recovery says it's installing and opening the package and goes back to the main screen after about 2 seconds, and when I boot into the OS, I'm clearly back at 12/13.
[Nook Color Android Development] leapinlar:
That failed md5 checksum means you have a bad download. You need to download it again, not skip it. Never install if the md5 checksum fails. That means the file did not come through right.

---------- Post added at 09:50 AM ---------- Previous post was at 09:46 AM ----------

That error 2 message means I am using an old version of update-binary in the zip. The new TWRPs are finicky about that. The only way to fix it is for me to correct the zip.
[Nook Color Android Development] deesto-xda:
Right. But I've re-downloaded 5 times now with the same error. Something's not right.
[Nook Color Android Development] eyeballer:
The next nightly will have even more kernel fixes. Everything is merged in now, wait for 12/16.
[Nook Color Android Development] JeremyNT:
Overclocking too much? Storage full maybe?
[Nook Color Android Development] deesto-xda:
No, plenty of storage available, and the ZIP downloads fine seemingly, but it just fails the MD5 check (actually, both 12/14 and 12/15 fail), so I thought maybe the source isn't valid? But if nobody else is having this problem, I'm stumped.
[Nook Color Android Development] leapinlar:
Try downloading the file manually, directly from the cyanogenmod site. Or better yet, try the CyanoDelta app on the play store.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] deesto-xda:
Thanks; will try that. But I think I'll wait for 12/16 now, thanks to eyeballer's recommendation.

BTW, took me a bit to realize I was looking for CyanDelta (no 'o') ;)
[Nook Color Android Development] les02jen17:
Yeah, it'll be easier. I hope eyeballer can also do it on PA. :)
[Nook Color Android Development] velizet:
I get "There are no results for CyanoDelta"

Any help?
[Nook Color Android Development] les02jen17:
As what you just quoted said, it should be "CyanDelta", not CyanoDelta.
[Nook Color Android Development] nookle:
I just updated from nightly 12-08 to the most recent 12-16 and am getting weird screen flicker or artifacting when navigating between settings screens. Not sure if it does it elsewhere. Not a show stopper, but it is annoying. Anyone have any idea what's causing it?
[Nook Color Android Development] Homer_S_xda:
I've been using CyanDelta with the sdboot mount script with excellent results. Question: does CyanDelta handle some kind of MD5 check internally?

Homer
[Nook Color Android Development] Mr-Glass:
Thanks eyeballer for the updated kernel in the latest nightly - I had a question that regards the nightly - when using CyanDelta - My understanding was that CD only updated any new changes to the rom, however the changelog on CD seems to only show general CM10 changes - Does anyone know if the kernel is part of that smaller CD download? Thx

EDIT - about tablet seems to show an updated kernel..
[Nook Color Android Development] leapinlar:
They might on the Delta they download, but I doubt they do it on the whole ROM after they modify it.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] Lakland:
I am running the unoffical nighly that leapinlar posted , but i didnt change the kernel that he post later.

The official nightly 12-16 will have all that merged?
[Nook Color Android Development] bigbob23:
Whenever I update with CyanDelta it shows a new date for the kernel in About Tablet.
[Nook Color Android Development] Lakland:
Yeah I am running the latest nightly (12-16) and is running real smooth rock on guys

---------- Post added at 08:17 PM ---------- Previous post was at 08:08 PM ----------

[My nooky is alive again!! yeah QUOTE=Lakland;35524296]Yeah I am running the latest nightly (12-16) and is running real smooth rock on guys
[Nook Color Android Development] deesto-xda:
Something is really screwed up on my system after installing the nightly from 12/13: if I let the OS download and try to flash any updated nightly ZIP, the download fails an MD5 check or fails to download completely. After that, permissions get screwed up such that my SD partition is no longer writable, so I can't use Chrome or anything else to download. If I manually download an updated nightly and transfer it to the Nook's SD, and then install via CWM recovery, it says "installing" then "opening" then goes right back to the main recovery menu. Then I reboot and I'm still in 12/13. Any ideas what might cause this? And any way around this besides a full wipe?

Thanks.
[Nook Color Android Development] kwyrt:
Updated from 11/29 to 12/16 nightly. Downloaded manually using stock browser and installed via CWM. Everything went smoothly. The difference in smoothness/responsiveness is definitely noticeable. Fantastic work on this guys. Amazon App Store was practically unusable before and runs smoothly now! Thank you for all the work the devs have put into this. Still can't believe CM10 can run this well on my old NC.
[Nook Color Android Development] leapinlar:
CM10 is really finicky about SD cards. If it sees anything wrong, it sets it read only. So downloading a new ROM with CM10 may not go well. I recommend you download the ROM with your PC and copy it to a CWM bootable card to flash it. The new version may not be quite as finicky since it has a few mods to the kernel.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] declined:
The 12/16 is awesome however i am still getting the SOD problem everytime my nook color goes into sleep mode, any ideas? thanks!
[Nook Color Android Development] leapinlar:
Try getting an app like Tasker to immediately turn off wifi when the screen turns off. There are several apps out there that will do it that are free.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] deesto-xda:
Just tried that and had the same thing happen: downloaded 12/16 on PC, transferred to Nook via wireless LAN, and still CWM recovery installs/opens the ZIP for a few seconds and returns to the main screen, then a reboot puts me back at 12/13. What the heck is wrong, I have no idea.

Regarding the SD card: what would CM10 see that would flip the card to r/o mode?
[Nook Color Android Development] leapinlar:
No, do not transfer to the nook. That is still using CM10. Make a CWM card and do everything by it. That way it completely bypasses CM10.

Could be anything on the SD. How it is formatted, successive read / write errors, lots of things. Just don't use CM10 for any of the file transfers until you get the new version on.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] pastordl:
Thanks for the great pre Christmas present

12-16 running smooth, fast, awesome. Thanks to all who have worked so hard for everyone to enjoy. Lovin'it.

:laugh::D:good::highfive::victory:

Now I can go back to cyandelta for nightly update. Been downloading nightly and copying the 12/8 unofficial kernel and installing moded zip. Worked but was a pain.
[Nook Color Android Development] bigrat:
Was running the special build from a few days ago, flashed the 12/16 nightly today. I noticed an improvement in display response time right away.

Still using stock settings.
[Nook Color Android Development] deesto-xda:
Thanks for that. It turns out that even though the transfers had completed "successfully" through the Nook, when I pulled the SD card and looked at the files, they were all 0 bytes. The fact that the installation completed so quickly in recovery should have been a giveaway.
[Nook Color Android Development] chrishh44:
I'm getting a lot of lag and apps are becoming unresponsive. Any ideas how to fix it?
[Nook Color Android Development] leapinlar:
You running on SD. Are you using a SanDisk class 4 card? You need to be.Those are symptoms of an inferior card.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] chrishh44:
I have a DANE-ELEC class 4 8gig....so if I get a SanDisk it should run smoother?
[Nook Color Android Development] DanAdamKOF:
I went from the 12/07 nightly to the 12/16 nightly and am getting SODs every time the device sleeps. I got nearly none on 12/07.

Basically a stock and untweaked setup, only things to note: CM10 is installed internally, zram is disabled, 1000mhz max speed, on-demand governor, animations are off, no background, and only one homescreen, and I disabled Kernel samepage merging for testing. I/O scheduler did not matter, I got an immediate SOD as soon as the device slept regardless of which was chosen. Kernel samepage merging being on got an immediate SOD with NOOP chosen. Wifi was on and off (I forget under which exact circumstances) and got an immediate SOD each time.

Something else to note (unrelated to SODs), I tried to update through Settings, and noticed something weird. Whenever I did so, my router went nuts and my internet got unreliable, with massively fluctuating speeds and pings, and eventually dropping the Wifi connection, needing a reboot. I haven't tried an update via this method since rebooting, so I don't have anything conclusive to say here, but I felt it was worth mentioning.

The performance seems a little better though. Whoever posted that the Amazon App Store was horrible before and is usable now is correct. Using the UI seems a little smoother too. Scramble With Friends still bogs down, can't tell if it's less than usual.
[Nook Color Android Development] WoodmanMN:
I installed 1216 earlier, and had immediate SOD issues. I tried the usual WiFi settings, and long battery life app. No changes. Every time phone goes to sleep for a few minutes.
[Nook Color Android Development] EAK128:
Just updated it to 12/16 this morning, no issues to report. Coming from 12/05 build definitely notice the improvement in speed and snappiness. Keep up the great work guys!
[Nook Color Android Development] Peoplephobic:
This 12/16 nightly is awesome. I never expected Jelly Bean to run this smooth on the Nook Color.
[Nook Color Android Development] leapinlar:
Yes, much smoother.

Sent from my Nook HD+ Running CM10 on SD
[Nook Color Android Development] Dave08:
Exactly the same here. I'm getting SODs even if WiFi is manually turned off prior to going to sleep. It's definitely not an issue with WiFi delaying in turning off. Wish I could get 1216 to sleep normally because it's nice and smooth when it's running.
[Nook Color Android Development] steven676:
Can I ask all of you (and anyone else experiencing SOD on the 12/16 nightly) to provide the information asked for in this post? Also, if you could confirm what build you were running prior to this one, and whether or not you experienced SOD on that build, that would be helpful.
[Nook Color Android Development] Lakland:
I am running the 12-16 nightly. This is the one. Smooth, fast. I do not have any sod so far, I mean is excellent. Thank you cm developers. Let me know any info you may required to continue improving this (so far I am please and I am comparing with Samsun tab 2 p3113)
[Nook Color Android Development] memman:
I'm on 12-16 and it's smooth as silk. Only one problem, which has followed me around for a few nightlies. After just a few minutes of use, the stock browser becomes unresponsive. It's the only app doing that. Reinstalling gapps didn't help. Any ideas?
[Nook Color Android Development] sisterchick:
+1 to 1216 running smoothly with no SOD thus far and good battery life with stock settings. Thank you, devs.

---------- Post added at 05:12 AM ---------- Previous post was at 05:07 AM ----------

Did you fix permissions in recovery already? You might want to clear browser app data and cache in system settings too.
[Nook Color Android Development] webyrd:
1216 running fine here also, did have browser freeze once immediately after install, has not happened since I ran fix permissions.

MSBN QI0CM9PJ23L

DATE 12/25/2010

CODE OMAP3630 ES1.1

CYTTSP

OMAP3ISP REVISION 15.0
[Nook Color Android Development] khaytsus:
I'm also getting almost 100% SOD's on sleep after updating my daughters NC from CM7.2 to CM10 12/16/2012 last night.

Did a full wipe and restored her games with TiBu, using gapps-jb-20121011-signed.zip gapps. Did not restore any system apps or data etc. I'll also post in the other thread.

CM7 ran perfectly on it, but... well, it's GB ;) I did nandroid, but I'll leave it as-is for a few days and see if I can figure out anything. Might do another factory reset and see how it behaves then add apps once at a time.
[Nook Color Android Development] bigrat:
I have not updated to the 12/17 nightly, staying with 12/16. No SOD issues. Performance continues to be great. Stock settings for memory, cpu, scheduler. Wifi is set to "Keep Wifi on during sleep only when plugged in."
[Nook Color Android Development] duane1221:
12 16 Nightly report

I had been experiencing SOD's with nightlies since the 11/16 nightly,

I upgraded to the 12-16 nightly via the CM updater. After reboot things were a little choppy on the gui and sluggish in general. After several successful sleeps and wake ups, I got a SOD no backlight. I went to recovery, cleared cache and rebooted. Since then it has been running smooth. Slept overnight, unplugged without SOD and did not lose much battery life.

Netflix 1.81 is running better than ever . And I even upped the processor max to 1100 and it still slept all night without a SOD. Screen responsiveness is also very good.

The only problem is it is running so well now, I am afraid to reboot :)

Update: Unfortunately, rebooting did cause SOD's to start again. After rebooting and setting the performance setting back to default then letting the Nook go to sleep on its own is getting the no back light SOD every time now.

Here is a link the the dmesg on a SOD - http://pastebin.com/8v9wJeVs

Second testing update. Setting CPU max at 600, I/O at BFQ, zRam disabled seems to not have the SOD's. I have had it running with these settings for over two hours and over 20 sleeps with no SOD. The 800 setting did still give a SOD.

Thanks for all the work on this.
[Nook Color Android Development] stolenmoment:
I got a SoD this morning, first in weeks. I've already done the survey. Installed the 1217 nightly, but the NC was unresponsive after being idle and out of WiFi range for maybe ten minutes. WiFi is set for "Always On".
[Nook Color Android Development] deesto-xda:
After finally getting a nightly to update, I've been running 12/16 and it seems great, no freezes, just the same problem as a few others where the web browser (and Chrome as well) is painfully slow to load any page.
[Nook Color Android Development] khaytsus:
I did a factory reset, formatted system, flashed 12162012, no gapps.. Booted, didn't turn on wifi.

Took me 25 suspend cycles to SOD, but it eventually did. Turned on wifi, took about 12 cycles.

Didn't bother to reinstall gapps/apps just yet since it SOD's pretty much 9/10 times with wifi on or off, power connected or not.

Nevermind, I restored apps and installed a wakelock app from the market, so far it's not SOD'ing. I'll update if it SOD's on me. I'll give this a day or so, see how it works out. My kiddo is 7, she's not very patient when it comes to things not working perfect. :)

So far it's been about an hour, lost a few percent on the battery, but no SOD.
[Nook Color Android Development] mrapollinax:
Not to nitpick but Wakelock will actually not allow your device to sleep thus no SOD.

I'm currently running the nightlies and haven't run into a SOD with the 12/16 build at all. Some slowness... but I think that is more of a memory issue more than anything else as it is not consistent.
[Nook Color Android Development] khaytsus:
I realize that, thus the reason I did it, and the reason I posted it... There are non-sleep related reasons for a device to freeze, SOD just happens to be a freeze going in/out or during sleep.

I wish I didn't have the SOD's, but wakelock will do for now as a workaround and hopefully there's something I can help in the meanwhile.. Test kernels, builds, etc..
[Nook Color Android Development] deesto-xda:
It turns out that I'm still unable to download or transfer files to SD, ever since the first flash to CM 10, and even after multiple successful upgrade flashes. Files either say they've "completed" and end up being 0 bytes (like upgrades via CM itself), or they fail outright (which happens when trying to update via CyanDelta). Some directories (like cyandelta and cmupdate) contain files with non-alpha garbage characters for names. But when I pop the SD out and plug in into a USB reader on my PC, I can read and write files without a problem, and can use these valid files to upgrade. Any idea what's going on?
[Nook Color Android Development] Dave08:
If this just started with CM10, maybe it's your SD. Check out this comment by leapinlar in another thread. Do you have another SD you could try in your NC?
[Nook Color Android Development] hwong96:
Format SD card using CWM recovery.
[Nook Color Android Development] mingolianbeef:
Hey I'm working on AOKP for this in the near future, how stable is this build, and does it have Bluetooth support.? Also

1. Does it already OC to at least 1GHz

2. What doesn't work (besides what's already listed)

3. How is battery life.?

Nvm, saw the OC thing.
[Nook Color Android Development] steven676:
For those experiencing SOD with 12/16 (and later) nightlies ...

The changes in this kernel should be included starting with the 12/22 nightly -- there's no need to flash this over a 12/22 or later nightly build.

... could you please flash the attached kernel and report whether you still SOD? (Corresponding source code: https://github.com/steven676/ti-omap-encore-kernel3/tree/845dfa45a187e505b15ba29c196ac3cb1001f1fc) (Note: you can flash this over any build, but it will replace your existing default kernel.)

NOTE: If you have an ES1.2 device, the attached kernel won't make any difference for you -- please speak up if you have an ES1.2 device and are experiencing SOD with nightlies from 12/16 or later.