yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] ADude:
Part of this is due to over-the-top enthusiasm about each little fix and new version, that it will cure cancer, establish world peace, and get you a weekend alone with the supermodel of your choice. ;)

The result is that word-of-mouth gets around, and so hundreds of people who have no clue about technical issues are flashing things they do not understand.

In the case of this Beta 3.1, as I type this, nandroid restore is re-installing 7.0-stable on my Nook, because I use the Nook to remind me about appointments, and when it is frozen (locked up), it doesn't do that.

That does not mean that the development is going wrong, in fact, it is labeled Beta in a Development Forum, and the purpose of the build is to find bugs.

However, earlier in the thread, someone who probably should only be running Stable asked "so is it okay to install this?". The answer to that question for anything other than Stable should be no. But someone answered "sure, go ahead, it's great". That answer leads to the results you observed.
[Nook Color Android Development] 360Razir:
OK, first full charge via AC power on 3.1 beta with OC kernel and can confirm that the light on my charging cable has not turned green yet, while battery is stating 100%. I have not reset my battery statistics since coming from 7.02 build.

EDIT: The "n" finally went green.
[Nook Color Android Development] iDidItAll4theNookie:
Yeah, trial and error got me this far in life when it comes to this sort of thing. After about 15 years of it (which is scary to think it's been that long), I'm pretty much the "go to" guy for friends and relatives when it comes to technical issues. That's a pro and a con all wrapped in one, since it's great to help people, but sometimes it gets old helping the same person with the same dumb problems over and over again. :rolleyes:

It's not all bad though, as my line of work is full of people ignorant to these type of gadgets, and what I've learned to do for fun has actually put me in a better position for my career. And I end up liking my job more.

Long story short, everyone has to start somewhere. And for all we know, some kid who just nuked his Nook might be a future Developer! I'm sure all the smart people who brought us these fine NC mods have screwed up a time or two, but just look what they do for us now! :D
[Nook Color Android Development] bucketheadmn:
Ok on 3.1 my internet is dropping out, but my NC is still showing me connected to wireless. This is something that I have never had happen before in any other build of CM7.
[Nook Color Android Development] joenathane:
I just wanted to say that this build has been running perfect for me, i haven't had any issues at all, no wireless issues, no SOD, etc. Best build ever...
[Nook Color Android Development] ADude:
When I bought my Nook Color, before flashing anything, I read all about the technical issues. Even at this point, before flashing Beta 3.1, I read all about the details.

In our modern society, the media gives everyone the impression that they know everything about everything. If the economy crashes, does the media ask a panel of PhD economics professors ? No, they ask people on the street who have not graduated high school and who cannot balance a checkbook, what THEY think should be done to fix the economy. "Tweet CNN now with YOUR opinion!" Then they put a scroll across the bottom of the screen with opinions.

Given that climate, it is no wonder that people do not think they have to read a little about the difference between .29 and .32 kernels before flashing their Nooks.
[Nook Color Android Development] ADude:
From:

http://batteryuniversity.com/learn/article/charging_lithium_ion_batteries
[Nook Color Android Development] Ronin3178:
That's why I trust the nook cable more than any software reading, there has to be some monitoring involved in the N light that the manufacturer designed. If its still orange, its not charged fully.
[Nook Color Android Development] djxcee:
This built is very stable. Everything feels snappier too its great!

Can't wait for 2.6.35 :)
[Nook Color Android Development] iDidItAll4theNookie:
Had my notification bar and buttons disappear after wake. Tried restarting AWM and changing the buttons visible, but it didn't bring them back. A reboot fixed it. Everything else seemed to work okay when this happened.
[Nook Color Android Development] hockeyfamily737:
Hahah, I knew this would happen as soon as Dalingrin released this. Like 5 minutes later if you go back about 30 pages in this thread.... LOL! I knew there'd be a bunch of people trying to use the old .29 kernel with this and people trying to use the .32 kernel with the old builds. The writing was on the wall!!!
[Nook Color Android Development] chisleu:
I don't know enough about how it works to make an educated guess, but it's possible. :)

My battery drain is fine since I did a fresh install on a charged NC and stopped using SPB Shell 3d (what a buggy thing!)
[Nook Color Android Development] ADude:
Okay, so I nandroid restored my NC to 7.0-stable because of the lockup/freeze/black screen problem where it does not respond to anything other than a very long power button press (three times in three days, and confirmed by several other users in this thread).

I recharged my NC during the day (unusual), so I took the opportunity to monitor it, and I found that it has now been at 100% for about a half hour, and still orange on the nook cable, so it seems probable that the charging has not changed between 7.00 (.29) and 7.10 (.32). The reports in the thread are likely due to people noticing this charging-while-at-100% issue for the first time, due to reading other people's reports. (Normally one is doing other things while the NC is charging, so people would never notice that it is charging at 100%.)

Some clarification of whether CM7 has any charging code that is at all different from the stock charging code (or whether the NC has entirely hardware control of charging).

The lockup problem is definitely new, though.

And several people have reported having wifi issues for the first time when they installed 7.10 (.32), including me. However, I will make a point of testing wifi tonight under the same conditions (same place and same uses) with 7.00stable (.29), and will report back.
[Nook Color Android Development] bot2600:
Just wanted to pop in and say this has been 100% stable for me and to thank everyone for all of their work. Sleep is working great, no lockups, running 300/1200 smartass, I think ondemand runs better, but the battery seems to go down surprisingly quick with ondemand.
[Nook Color Android Development] JeremyNT:
There's a new nightly up today (5/15), is it still on 2.6.29? I'm too unstable on b3.1 for daily use.
[Nook Color Android Development] bekyndnunwind:
I love .32 so much, but I see the following issues:

When I receive a new email, Gmail keeps playing the notification tone over and over in a loop (until I view the notification or the message). When I got home from work the other day it was playing; the ringtone had been playing for 6 hours... Dal said this was an upstream issue with CM7 itself...

The (rare) SOD that I see, seems to happen after i've recently charged it.

It is difficult for me to press buttons in the corners of the screen. Can't press the search button in the Nook app for example...

Besides that, I love the speed and battery life. Everything else works great!
[Nook Color Android Development] sjwaste:
Maybe I should PM Dal, but...

I'm running the 5/13 beta, with the 5/13 OC kernel (300/1200, On Demand) and the 1.2 u-boot. I am 100% stable. I even get the screen animation when I turn the screen off :)

BUT my battery life is no better than it was on the nightlies. That's to say, I started at 100% last night and after a day off the charger with about 30 minutes of use, I am down to about 60%.

I'm not reporting any partial wake usage, and the stock battery stats tell me its sleeping. However, Spare Parts tells me its "Running" 63% of the time, "Screen On" about 3% - the latter being accurate.

Since I'm not having stability issues but am not seeing the full benefits of the new kernel, maybe I am a good test case. While I'm not a kernel dev, I do have some tech skills, so I can help track things down. I just need to know where to get started. Are there some logs I can send?

I love what the community has done to make the Nook an awesome tablet for me. I'm happy to give back if my particular use case helps, just point me on how to get started.
[Nook Color Android Development] Ronin3178:
Unless you have seen something otherwise, yes.

On another note..... I have experienced my first bug... the tablet tweaks menu crashed on me, it was working great, put it to sleep, next time I woke it up, gone. Nothing, including going into TT and changing from bottom to top, etc, would bring it back. Reboot and it is back. Not bad for a two day run. I still am running this as a daily.
[Nook Color Android Development] deadbot1:
Ok....I have only one issue so far...otherwise perfect.

What I have gotten down to is this...

1. Start with Nook on, screen off( by single press of power button)

2. Plug stock charger in...result is backlight on but screen off. N button has no effect.

3. Press power button once....backlight shuts off.

4. Press power a second time...screen wakes properly.

5. Screen now acts normally (wakes with power or N KEY) until...

6. Remove and replug stock charger or lose power to charger and regain power leads to step 1.

I have had no SOD yet...only this odd behavior. Everything else seems fine. Beta 3.1, 1.2boot, 1.2 OC kernal running 300/1200 smartass. I don't have any logs...can capture if you need.

Edit...

Dropbox link to aLogcat zip. http://db.tt/LCt15lfhttp://db.tt/LCt15lf

Actions here are...

Shut screen off.

Insert cable.

Press N button twice.

Press power button twice.

Restart aLogcat as screen returns to launcher default.
[Nook Color Android Development] gudism:
I agree with this entirely. I am a noob at all this, but I can get around fairly well when it comes to doing stuff like this.

But, I am not going to flash any Beta stuff, as I would rather let the dev's and the really really knowledgeable folks do the testing etc for the devs feedback. (also cos I have 4 young kids and just dont have the time to be testing things etc)

For now, I will sit back, read these threads, and when the smoke has cleared and its ready to rock as a stable....then I'll jump on it! (cant wait!)
[Nook Color Android Development] gteo:
Hi installed the Beta 3.1 to Nook color, working well and battery life is good, but there is no gmail and adroid market apps there, after flash with gapps-gb-20110307-signed.zip, indicated installed ok, when re-boot, still not seeing gmail and android market apps, have tried few times, still same. Am i doing the wrong procedures or wrong zip file ?

Pls help
[Nook Color Android Development] ADude:
Okay, I did the same uses of wifi just now with 7.00 stable (.29) that I did with 7.10 Beta 3.1 (.32) last night, in the same location.

The result is that wifi worked flawlessly with 7.00 (and I previously reported wifi failures with 7.10 Beta 3.1, the same thing reported by others in this thread).

So, there is a data point that there is some new wifi problem introduced by 7.10 Beta 3.1, as I have never had wifi problems before.
[Nook Color Android Development] 360Razir:
Gmail is now a standalone app and is downloadable from the Market, therefore it is not included in the Gapps file that you used (which, btw, is the correct one).

What "market apps" are you referring to?
[Nook Color Android Development] mjb413:
beta 3.1 with overclock kernel works great here. 3 days, 87% battery. simply amazing.

only issue is, i believe, app specific. I have tried to use the modified netflix apps and it seems as if it is playing at double speed? anyway. thanks for the great work dal. hardware video decoding works well for me. hulu streaming is a bit stuttered. most other flash video streams fine.
[Nook Color Android Development] moesasin:
Noob Friendly Instructions(1.2 UBoot+Overclock+ CM7 beta 3.1)

all required files are already on the bootable CWR image.

Requirements:

Nook Color

atleast 1GB micro SD card

CM7.1-beta-3.1-mrm3.net.zip

Win32 Disk Imager

USB SD card reader(a must have, you cannot use the nook for writing to the SD card during this process)

Instructions

1. Download all of the above files and put them in a convenient location. only extract the files Win32 Disk Imager, and CM7.1-beta-3.1-mrm3.net.zip

2. Open Win32 Disk Imager, select CM7.1-beta-3.1-mrm3.net.img and write the image to your SD card.WARNING THIS WIPES THE ENTIRE SD CARD

3. Wait for it to finish.

4. Reboot your nook color with the SD card in. It should now boot into clockworkmod(CWR)

5. clockwork mod is an environment to install roms and programs before the operating system boots to navigate use the volume buttons for up and down. home to select and power as the back button.

6. Navigate to Mounts and Storage. format all of the following: data, system,and cache. Each require you to separately navigate down to YES to wipe.

7. After you have formatted the above. Go back to the home screen using the power button and select install zip from SD card, choose zip from sdcard, update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip

8. After it has finished the install from SD. Hit the power button until you can select reboot system now DON’T CLICK IT. Remove the SD card. Select reboot system now.

10. Your device will now reboot with Gingerbread installed. The first boot up should take about 5 minutes and on the screen you will see in this order…loading…android…then a fancy boot animation.

11. Insert SD card again and boot into CWR. Now install these files in this order….Update-BN1.2-uboot.bin.zip…..update-cm7-dalingrin-2.6.32-emmc-051311.zip……Nook Color Google Apps.zip

12. Reboot, then login to market

13. To overclock: Settings>cyanogenmod settings>performance> CPU Settings> set max to 1200mhz>governor on demand.

For more noob friendly how to guides check out my site in the signature.
[Nook Color Android Development] hockeyfamily737:
Here's the thread regarding the Netflix app and how to get it to work correctly. There are a couple of different build.props you can use......http://xdaforums.com/showthread.php?t=1078123
[Nook Color Android Development] fattire:
This u-boot.bin needs some testing by developer-types. It's a custom 1.2 u-boot with a new splash and some small modifications from verygreen to hopefully work on SD as well as EMMC, easier power-button down on start, and other nice things like some debug stuff removed.

(The B&W "skulls" version a couple months back was easy. Turns out, a slightly larger graphic w/the right palette is harder. Even now the colors are a little Miami Vicey. But it beats plain ol' "Loading...")

This is still in development. I have not been able to test the screen when you run out of battery, for example.

It's based on 1.2 u-boot source generously provided by BN. Try at your own risk (have a backup bootable SD and consider an archival u-boot too, JIC). See the GPL for terms. I promise nothing :) If you don't know what to do with a u-boot.bin file, don't worry about it.

thx to verygreen for his contributions and bandroidx for testing.

u-boot.tar.gz
[Nook Color Android Development] hockeyfamily737:
This is a very nice guide, but it doesn't belong here. It's going to become lost in obscurity within 48 hours. That being said.....Most "noobs" should not be flashing a beta anything anyways....Just my opinion.
[Nook Color Android Development] gteo:
Tks for advise. There is no Android marketplace in Nook Color, and not asking to setup gmail's login and etc after done Gapps.
[Nook Color Android Development] mjb413:
Thanks so much. I had looked at several other threads such as the one in the g-tab section and the general apps section, but didn't check out our general section. works great now.
[Nook Color Android Development] chisleu:
I think the performance of on demand is better than smart ass. It's way less than the old interactive on .29.
[Nook Color Android Development] gteo:
I managed to get the Gmail 2.3.4 and market 2.3.4 and installed ok, but unable to run, when click, white screen appear and close. If i get the correct gmail and market apps or need to do setting in Nook color.

Pls help.
[Nook Color Android Development] jmak10:
I'm running the 5/13 beta, with the 5/13 OC kernel (300/1200, On Demand) and the 1.2 u-boot and have noticed the following issues;

1. WiFi sometimes drops out

2. The screen will shut off sometimes upon completion of a flash video running from Dolphin HD. It acts like the power button was pressed to put the unit into standby. Pressing the power button turns the screen back on. I am using Flash version 10.3.

3. Had one SOD that required holding the power button in for over a minute to get the unit to boot up.

I have changed the OC kernel to 300/1100, On Demand and haven't experienced any issues yet but have only been using this setting for a short time.

Thanks,

jmak
[Nook Color Android Development] RoboRay:
NOT just your opinion, it's a fact. A Dev forum is not the place to teach or learn the basics. A step-by-step "Newbie Guide" should be in the General thread, not the Developer thread.

And, of course, Test build information does not belong in the General thread at all.
[Nook Color Android Development] Ronin3178:
I just did a test on dolphin HD, watched a flash video, my screen did not turn off after the video was over. I have 10.1 installed it looks like. What are you settings for screen timeout? Mine is like 10 mins.

5/13 oc 300/1200 smartass

EDIT : Also just had my second early shutoff, this time battery was showing 13% and just shutdown, the time before that was @ like 9% I think. 7.0.2 was going until at least 5% for me before.
[Nook Color Android Development] seth.i.simmons:
Same here, smartass seems a little laggy compared to ondemand, personally. Especially when scrolling. Is there any way you (dalingrin) could include interactive in the next kernel update?? So we could have ondemand, smartass, AND interactive?? That would be awesome, since interactive worked so well for me in .29 kernels.
[Nook Color Android Development] jmak10:
My screen timeout delay is set to 5 seconds. Also, this is an intermittent problem and doesn't happen all the time.
[Nook Color Android Development] Divine_Madcat:
In watching other phones (specifically the Incredible), the smartass gov went through several changes and tweaks by many people to get things right. I am not surprised that the first release of it here is exhibiting the same issues it has elsewhere...
[Nook Color Android Development] Canadoc:
Having similar.issueshere. have had a few SOD. SometimesI close.the screen an furlough nothing is showing onscreen it is still illuminatedall black.

So far this has not been much better than when we had first gotten nookie froyo in terms of stability
[Nook Color Android Development] BitingChaos:
Documentation for anything Android is horrible. That is because things change so quickly.

Now, some stuff may be documented well, but it may also be old info.

I found a thread on some stuff that seemed "new" - from Feb/Mar 2011. Turns out the data was old, inaccurate, and just plain _bad_. Now, maybe at the time of writing, it was the best, most of up to date documentation. But things change so much, and very quickly.

What good is a "Newbie Guide" if it just tells you how to set up your device about 20 versions behind before people read it? What do you base the guide on? 7.0.3 with battery draining? What if someone find it after 7.1 final is out?

I say a Beta/Alpha/pre-alpha build thread is just as good as any to jump into this stuff.

If you want a problem-free, worry-free experience, then there is iOS. If you want to jump into something that may lose all your stuff, break, and give you a migraine trying to figure out, then there is Android.
[Nook Color Android Development] 12paq:
yup, and remarkably stable for 1st beta release within days of the source release. A testament to the solid dev work we are lucky to share a device with.
[Nook Color Android Development] khaytsus:
Interesting... I ran the beta 3.1 build at 800mhz on the kernel included in the ROM itself for 24h, no problem. Bumped it up to 925mhz and within an hour I tried to wake it up to do something and it was dead, had to hold power for 30s and boot back up again. This is SOD, right? I've been told a few times it's not, so maybe there are a few definitions of it...

I previously ran at 1.3ghz stable for days on end, so pretty sure it's not a problem with my CPU being unable to do 925. But not sure what else to make of this.

Back to 800mhz to continue stability testing.
[Nook Color Android Development] :
IF YOU GET AN SOD:

Can you pretty please grab this?

/proc/last_kmsg
[Nook Color Android Development] furius:
noob questions:

- what is SOD?

- will this build be merged on CM nightly?

- after updating uboot to 1.2, can I restore my CM7.0.2 backup or do I need to restore previous uboot? In that case, where can I found it?

I'm running beta 3.1 since two days, without big problems except for some rare occasionally freeze or reboot...

Thanks!
[Nook Color Android Development] 12paq:
yup. any advice on how to cut and paste the correct info from the file? Also, in /proc/ I only have /kmsg/ not "/last_kmsg/", and /kmsg/ will not open in a file editor and when I pull it via adb its huge..

I tried to view it in terminal for kernel panic, but.. fail.
[Nook Color Android Development] ADude:
Sleep Of Death

Hopefully not before the two major bugs are fixed.

In Clockworkmod Recovery, choose "Nandroid Backup" and it will make a backup of everything, including the boot partition. That is the most reliable way to backup and restore.
[Nook Color Android Development] khaytsus:
Nope, as several people said, it does not exist.
[Nook Color Android Development] RoboRay:
That does not change the fact that this thread is not the correct place to provide such entry-level information or to ask newbie questions.

The creators of XDA specifically disagree with you, which is precisely why they maintain seperate Developer and General forums.
[Nook Color Android Development] MACLUIS1:
Correct me if I'm wrong, but I thought Sleep Of Death meant that the NookColor wouldn't fall into Deep Sleep. Therefore, rather than sleeping it's actually draining your battery. Not some sort of comma!!!!.

Could somebody please clarify this.
[Nook Color Android Development] Divine_Madcat:
Nope, it has NEVER meant that. The fact that (with CM7) that it wont go to deep sleep was the patch to avoid the SOD. The SOD is, and has always been, where the device will not come out of standby, and requires a hard shutdown and reboot (or, if you are lucky and have adb responding, an adb reboot.
[Nook Color Android Development] :
Two versions of SOD. The real one and the mis-named one.

Real SOD=will not wake from sleep.

Mis-named=doesn't go into deep sleep.

The Real SOD has shown its head again for some people with the latest Beta.

The mis-named one is gone from beta, but still there in nightlies and stable (although it is much better than before).
[Nook Color Android Development] Chahk:
No. Sleep of Death is when NC does go into deep sleep, but is unable to wake from it by any means, other than a hard reboot (holding Power button for ~8 seconds.)
[Nook Color Android Development] 360Razir:
On new beta, I have had it where I push the "n" to wake the device, but instead, it does nothing. Also, holding power button (not long enough for a hard shutdown) does nothing. However, holding the "n" for about 8 seconds wakes up the screen. That is definitely a new one for me.
[Nook Color Android Development] newellj79:
R u a moderator?
[Nook Color Android Development] deadbot1:
Please take all pissing contests elsewhere.

Simply put...if you have to ask what this is or even think you may be a noob..stay with the stable releases.

If you know what this is..stay on target..lets get these bugs squished.
[Nook Color Android Development] zeus_chingon:
Please read the following moderator post. Specifically "common misunderstandings" section.

http://xdaforums.com/showthread.php?t=1069298