yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] DizzyDen:
fattire... one thing I'd like for you to consider is also allowing selection using short power press.... with my fingers it would be nice to be able to hold nook with fingers along the sides and use vol+/- for moving in the menu... and power for selecting.... possibly just adding a button poll for power the same as the "n" button.
[Nook Color Android Development] newellj79:
I'm running n86, 5/23 kernel, and fattires untimely uboot. All good so far.
[Nook Color Android Development] sinanju:
I take that back. I've had the device plugged in all morning, so there was no attempt to sleep. I unplugged it so I could attach it to my laptop to see if there was anything interesting in the logs related to today's GMail IMAP issue and there was a significant delay getting the screen to turn on. So, the WiFi-related SOD I've been having is still there.
[Nook Color Android Development] Xhorder:
Does n87 have the newer "untimely" u-boot ?
[Nook Color Android Development] seth.i.simmons:
Nope, it hasn't been cooked in yet. Just finished tweaking and installing the n87 zip, and the uboot is still the same as n86. Great so far though!
[Nook Color Android Development] xc68000:
I'm running n84 with the stock kernel. Doesn't seem like deep sleep is working. Battery history on tablet tweaks shows wifi as being on 100% and used 18% over 24 hr's of use on battery.

Is this evidence that deep sleep is not working on my system?
[Nook Color Android Development] seth.i.simmons:
Trying installing CPU spy on your NC and see what it tells you after giving it 10min or so to go to sleep.
[Nook Color Android Development] khaytsus:
Delay IS NOT SOD. SOD would only be if your battery was charged enough to run, but the screen absolutely would not turn on. You would have to hit power for 8+ seconds to force a power off, then power back on in order to recover.
[Nook Color Android Development] sinanju:
Which, as I have explained elsewhere, is what happens if your WiFi policy == Always On... that results in an inability to wake the device, aka SOD -- or at least one flavor of, perhaps, several. Since WiFi eventually shuts off when the policy == Off When The Screen Is Off, the device eventually wakes -- a petite mort, if you will.

Thanks for playing, though. Please take a copy of the home game.
[Nook Color Android Development] Chahk:
I keep getting the actual honest SOD very often. It won't wake, and is not listed when I hook it up to USB and do "adb devices". NC reboots with 50%+ of battery power, so it's not turning itself off. Also, /proc/last_kmsg doesn't get created.

Could it be related to WiFi sleep policy? Mine is set to "Never". I'll try with "When screen turns off" for a few days to see if that resolves it.
[Nook Color Android Development] sinanju:
Yes.

Another approach to the experiment is to explicitly shut off WiFi before turning off the screen. The power control widget makes it convenient to do so. The problem with "when the screen turns off" is that WiFi is not immediately disabled. As a result, there is a window between shutting off the screen and WiFi being disabled where attempting to turn the screen back on can result in a delay of up to several minutes.
[Nook Color Android Development] philburkhardt:
Just an FYI...

My Wi-Fi sleep policy has always been set to never, and my WiFi is always on. I have had no SOD issues.

...I'm on n86, be loading up n87 shortly.
[Nook Color Android Development] crashdau:
+1....same here...no wipe b4 install

Edit: noticed My Apps is working and it shows ROM Manager as having an update available. Should we do this update or will that screw up the CWM 3.0.0.6 flashable version we have for the NC?
[Nook Color Android Development] tominabox1:
Updating RM does not effect your CWR (unless you flash the recovery inside RM)
[Nook Color Android Development] spikey911:
Still having issues with AdHoc...Connects perfectly the first time, but when I leave the area and come back, it just does a constant loop...I can never connect again..
[Nook Color Android Development] ericmcintire:
Hi, This is my first Nook Build I have installed but I have experience on the EVO. I just installed the latest version and I can't connect to my wifi because if I click on wireless, I get a FC. I'm assuming the people that are connected did so with a previous build and the settings stuck but as of right now I can't get on the internet with this build. Suggestions?
[Nook Color Android Development] tominabox1:
you can put a link to the wifi prefs on your homescreen.
[Nook Color Android Development] digitalslacker:
long press the home screen > custom short cut > settings > wifi settings >

known issue, started with last night's build.
[Nook Color Android Development] burbank:
I wiped. Installed #7. Was pleasantly surprised that all my purchased apps downloaded automatically via the Market. Getting 7 up and running after a wipe was really quite painless.

As for stability... IMHO it's the best iteration yet. I'm lovin' it.
[Nook Color Android Development] j4mm3r:
Hmm... I guess I was too early to say that. Well it includes a default build of the radio interface layer libs so that helps a lot in making the market work. But I used System Panel to check up on the telephony settings and I dont see a deviceId.

I'll wait and watch this space and continue working on it so see if I can come up with a generic solution which can be pushed to the CM builds.
[Nook Color Android Development] buffalosolja42:
Thanks for the heads up haven't tried V7 because V5 was so good to me, v6 gave me the hiccups with menu so went back to v5. I will try it as well and post back.
[Nook Color Android Development] crashdau:
Thanks bubank. I installed w/o wipe and everything is still golden.

Did notice I couldn't get the pc to access the SD card under USB Connect in notification drop-down, but, I turned off USB Debugging and Bam I was able to connect.

Hope that will help someone who may need it.
[Nook Color Android Development] rainmaker002:
I upgraded from v5 to v7 (without wiping anything but cache and dalvik cache) but my wi-fi is still not working. It worked fine on v5 except for a couple of disconnect cycles which were fixed via reboot until this morning when I turned it on, but now it simply says "Connecting..." and then "Disconnected" over and over again in Wi-Fi settings. I wonder if I should be trying a wholesale wipe.
[Nook Color Android Development] buffalosolja42:
Just updated from v5 to v7

As someone pointed yes my apps works :)

Pandora works (been trying to fix all day with v5)

I still need to get my youtube to work (but honestly only time I use it, is when a co-worker sends me a link)

Seems solid (already had wifi setting on home screen so no issue)

I like :) Thanks for all those who put it in the time, and work to make our devices something they weren't designed to be to make us happy.
[Nook Color Android Development] racks11479:
Great! I've just flashed v7 and all seems well except the issues with the settings crashing and my gameloft apps are still FC'ing on me. I'll look forward to see what you can come up with. Thanx for the help. In the meantime. I'm no coder like you, but I'mma see if I can modify that patch again to work with the v7 framework to see if it helps me any for the time being. All in the fun of it! :D
[Nook Color Android Development] crashdau:
Hey racks, what gameloft games are you running? I bought Let's Golf 2 on my Droid X, but I can't get it to run on my NC....I keep getting the message "This is not the original..." something message.
[Nook Color Android Development] newellj79:
I flashed over as well. Everything seems to be working fine. Wifi on occasion takes a couple extra seconds to connect after a long sleep but thats it.
[Nook Color Android Development] rainmaker002:
I went back and reflashed, wiping all. Seems ok now, but it worked fine on v5 for a few days so I'll hold off on judgement for the time being.
[Nook Color Android Development] racks11479:
Its cause its not a valid device. If you have root explorer. Just go into /data/data/com.gameloft.GAND.GloftLetsG and delete the drwmfl.bin file. And just relaunch the game. You might have to do it each time you play if you don't disable wifi before beginning.
[Nook Color Android Development] philburkhardt:
You can also use Droid Wall from the market to permanently block the games from connecting to WiFi.
[Nook Color Android Development] nemith:
Hey PM the gameloft game you are using. I just bought (and returned) UNO and it worked fine as well.
[Nook Color Android Development] Mikey:
THERE WILL BE NO TRANSFERRING OF GAMELOFT APPS ON XDA!!!!

GAMELOFT HAS TO BE BOUGHT.

Would you like to be banned from XDA permanently???
[Nook Color Android Development] paleh0rse:
Same here. I had one with the beta3.1, but none since.

/knock_on_wood
[Nook Color Android Development] boogerboy72:
anyone care to dummy down the difference between 86 and 87
[Nook Color Android Development] dalingrin:
I can't reproduce any SOD and I can't reproduce the battery issues.

Nook has 10% battery right now and still running.
[Nook Color Android Development] :
To reproduce you could flash 1.1 stock, then to nightly.

In theory, at least.
[Nook Color Android Development] sinanju:
Since I can, is there a way to hook the device to the debugger without it charging from USB? If there is, I could at least get logs for you.
[Nook Color Android Development] ziggy34:
only problem I've had was the wifi problem, but #86 fixed that. did have a strange battery problem, but its fine now. thanks dalingrin for all your work, the nook is great now.
[Nook Color Android Development] MACLUIS1:
Forgot, Running 86 with 0523 OC

I haven't had any SOD in any of the nightlies or combinations. I did have a PBD (Premature Battery Death). My Nook kept on shutting down with about 25% battery capacity with Beta 3.1. But the so called SOD I haven't experience at all.

*HBO Go Working

*Netflix Working

*Deep Sleep Working

*XDA Premium Working

*Hardly any FCs

Any news on Bluetooth Range?
[Nook Color Android Development] rhester72:
Sorry for the dumb question - where exactly does one check the WiFi sleep policy?

Rodney
[Nook Color Android Development] sinanju:
They did their best to hide it.

Settings>Wireless & Networks>Wi-Fi settings, then bring up the menu and select Advanced
[Nook Color Android Development] 12paq:
In wifi settings, hit the menu button.
[Nook Color Android Development] 12paq:
Edit: ha, beat me to it. :)

For logs if you are not comfortable with ADB, there is a market app "alogcat" that can work just fine for tracking some things. But I do not know what dalingrin wants, nor can I replicate any issues, since the .32 kernel was baked into the nightlys, my Nook has been solid. Weird.
[Nook Color Android Development] fattire:
Does everyone think this is a good idea or would it be confusing that you can select in two different ways? It wouldn't be hard to add, I'm pretty sure. But the instructions would need to say something like "MENU/Power toggles selection" would you understand that means menu OR power?
[Nook Color Android Development] :
I think it would be confusing and unnecessary. Also, simpler=better, so why be able to do things two different ways?

I still don't understand what is being asked, and why mess with something that isn't broken :)

Sorry DizzyDen.
[Nook Color Android Development] DizzyDen:
No reason to apologize... as for what was being asked is simply a short power press to duplicate the "n" button behavior... to facilitate leaving fingers along side of the NC while in the menus instead of having to take hand off to press the "n" button..... no worries either way... just a thought to make it even more user friendly is all.

TBH since the power button does nothing in the menu's.... the functionality could be implemented without even changing the prompt... just another thought.
[Nook Color Android Development] :
OHHHHH!!!!

Why didn't you say so!

Hm...

In that menu I have my hand holding it from the bottom, so I like the N, but power makes sense as well. That being said on the whole scheme of things I think most people think of N as enter, and maybe having the power button do this would scare? some people away? Then again if you're in this menu I hope you know what you're doing.

Sure, let's do both :)

It could read "To select, press the n or power button"
[Nook Color Android Development] sinanju:
I was hoping to crank up Eclipse and watch it in realtime, but you can't watch a problem related to discharging the battery or sleeping if you're connected to the USB port and charging/preventing sleep.

Unless there's a way to prevent charging during debugging....
[Nook Color Android Development] TJNooker:
@fattire

I think it would be smart to keep the controls as close to CWM as possible. In my opinion consistency and intuitiveness, e.g. similar controls across similar apps (recovery ~ boot), is more important than trying to make this more ergonomic.
[Nook Color Android Development] Arbelzapf:
Hm...My Apple bt keyboard is still disfunctional after pairing. I was hoping that was a problem with the beta, but it's still there in the recent nightlies, so I guess that's a problem with the .32 kernel update altogether.

I posted about that in the Bluetooth Experience thread before and the behaviour hasn't changed: Pairing works flawlessly, even the range seems to be good. I didn't get 2m distance before (but that's only monitoring logcat and the status bar icon as I can't tell if it'd actually work at that range). The problem seems to be (to me at least -watching logcat) that it does not pick up a keychar map like it did before. It just pairs and then does nothing. Chisleu seemed to be able to reproduce that on his NC
[Nook Color Android Development] fattire:
Heh. Okay, I'll leave it as-is. Speaking of CWM, originally I had orange text and everything too but nemith thought it might throw people who thought they were in CWM accidentally or something so I changed to green :)
[Nook Color Android Development] TJNooker:
Put it this way, I'll be fine with a brunette even if I'm used to redheads because their "controls" are in the same place and function mostly the same.

P.S. Let's go ahead and kill this metaphor right here. I know where this can go. ;)
[Nook Color Android Development] :
I haven't ever tried it... but the 4 pins of the USB are as follows:

1 - VCC - Red

2 - D- - White

3 - D+ - Green

4 - GND - Black

VCC is power, GND is ground and D- & D+ are for data. So you could try cutting the Red VCC wire... with micro-USB cables being so cheap; why not try?
[Nook Color Android Development] sinanju:
Just discovered I can run over WiFi... no need for the cable. Trying it now.
[Nook Color Android Development] dexx0008:
two battery version or the older 3 battery?

I can get my old 3 button to connect and pair fine, but can do nothing afterwards. Doing so with the newer 2 battery version it pairs and connects the same but actually works. This is with the firmware update applied to the 3 battery version. I also read someone who had not yet applied the firmware update to his older 3 battery version was not able to connect either.
[Nook Color Android Development] ADude:
Definite +1
[Nook Color Android Development] ADude:
I am assuming that "Never" is to allow Wifi to get mail and sync while the screen is off, with the disadvantage of using more battery.

Is that correct ?

Any comments on advantages/disadvantages of the settings would be helpful.
[Nook Color Android Development] newellj79:
Hmmm, why not make cyan?
[Nook Color Android Development] Arbelzapf:
I have the 2 battery version (bought it the day BT was enabled for the Nook ;) )
[Nook Color Android Development] fattire:
You mean... like true cyan?
[Nook Color Android Development] newellj79:
I didn't actually look at the illusion, but I mean cyan as in the blueish stock color that CyanogenMod uses, like when the older nightlies use to say android before the boot animation.
[Nook Color Android Development] TJNooker:
That was pretty cool.
[Nook Color Android Development] dexx0008:
I'll try mine tonight on nightly 86 that i flashed this morning.
[Nook Color Android Development] paleh0rse:
+1

Obvious color choice is obvious. ;)
[Nook Color Android Development] RoboRay:
Wow, yeah, make it like that! :D

But the "CM" standard color would also work.

Or maybe plaid. Can we go to plaid?
[Nook Color Android Development] abs99:
I finally went through the process of a full wipe and install of 1.2 rom before re-installing Dal's first .32 release. Since completing the process, I've eliminated the battery of death issue . . . the battery calibration is now fine where the device was force shutdown around 20% battery.

Until we determine the reason for the battery calibration issue, I think we should remove the u-boot from the overall ROM install since it seems like it may re-introduce the battery calibration issue? Can anyone verify this?

One recommendation, just to be sure everyone is doing this, after flashing a new ROM, I always wipe the Cache and the Dalvik Cache (but not data) through ROM Manager. I think if this isn't done, especially Dalvik Cache, it can cause strange behavior. Just to be safe, for those having problems, if you haven't wiped these caches after flashing the new ROM, please do so and see if your issues continue.
[Nook Color Android Development] :
Removing the uboot would not fix anything. In fact it would probably "break" installs from people who don't know what's going on w/CM7.1 atm.

Flashing to 1.2 is great and has fixed the problem for everyone I know, but the 1.2 bootloader is still needed, and removing it from the zip wouldn't make problems go away.
[Nook Color Android Development] Chahk:
No, because true cyanogen is colorless. :p
[Nook Color Android Development] abs99:
Would you know the answer to this: if I've already gone through the full 1.2 install process to fix the battery calibration and if I then go ahead and install the latest nightly (which includes the 1.2 u-boot), will the system revert back and recreate the battery calibration problem?
[Nook Color Android Development] :
Don't think so. It's based on a 1.2 bootloader (afaik) but just modded for our use. So if it was fixed with flashing to 1.2, it should maintain the same. I just updated the bootloader so we'll see if it rememebers (I got down to 3% before the shutoff).
[Nook Color Android Development] paleh0rse:
I did the full wipe and stock 1.2 install before using these nightlies and the modded uboot, but I still suffer PBD in n86.

:(
[Nook Color Android Development] GrillMouster:
Some pages back someone posted that they went back to stock B&N 1.2, then installed the CM7 beta3.1 or some nightly .32 version that didn't include the u-boot (so the u-boot from stock B&N 1.2 remained). This got rid of the battery problem...until he flashed fattire's u-boot and the problem returned.
[Nook Color Android Development] EnTg888:
I have the latest nightly (includes fattire's custom u-boot) and it does not have the battery problem (went down to 10%, at which case I decided to charge it).

However, back in the beta 3.1 days, there was a time when it shut off prematurely; however, on the next discharge, it did not. Can anyone confirm that the battery problem never occurs twice in a row? It might just be a calibration thing.
[Nook Color Android Development] TheMainCat:
Noticed today with CPUSpy that "deep sleep" is being listed as unused on my Nook. I am running N87 with 5/23 OC, and the "untimely" u-boot. I used to see how long the "deep sleep" was prior to this version. Anyone else seeing this?
[Nook Color Android Development] :
Just came back to comment on this. After having it go into deep sleep quite a lot, I booted into SD HC, played around, then ejected and came back to eMMC beta 3.1. It didn't go into DS until I turned off wifi. Will mess around with stuff...but when it's not in DS is usually hovers around 600 MHz. Maybe something to do with the keep awake + sleep + screen stuff? I'm not on usb or anything, just thinking out loud...
[Nook Color Android Development] khaytsus:
If it wakes up without hard powering off, it's NOT SOD. Get a freaking clue.
[Nook Color Android Development] ansleyj44:
I posted this in response to someone in the users forum, thought I'd share my observations.

Also note that I have sleep policy set to turn off when the screen is off if that makes a difference. And it is definitely not connected to USB.

"This might be specific to me, but I've noticed it twice now, once on beta 3.1 and once today with nightly 86, both running oc.

So I'll charge my nook to full overnight and unplug it in the morning, turn it on to check it out, maybe using one percent battery or like 15minutes worth of play, then put the screen to sleep and leave for work. Come home 8 hours later to find it never got into deep sleep. The battery has run down 10 to 15 percent and cpuspy confirms it han't used deep sleep.

The first time this happened I thought it was my live wallpaper preventing deep sleep, but once I rebooted it had no problem with deep sleep, live walls and all.

Today, same thing happened. Came home to find a12 percent drain, no deep sleep according to cpuspy. I checked some email then turned off the screen, and curiously, it went into deep sleep after about 5 minutes.

I have no idea what this means, but maybe someone else does"
[Nook Color Android Development] sinanju:
And, if your WiFi sleep policy is Never, it frequently won"t wake. Why is this a difficult concept for you?
[Nook Color Android Development] odub303:
Just wanted to throw my experience in with the whole deep sleep issue. The only way I have been able to get the cpu to sleep consistently (setting aside the fact that it won't wake sometimes) is on n86 and 87 with the stock kernel. Any time I try to use the 5/23 OC kernel, the system allows the cpu to go to deep sleep until a reboot, after which I can no longer get the cpu to go to deep sleep. Just based on my personal experience, it seems to me that the problem may be caused by the OC kernel. Then again, I have not performed repeated tests to keep confirming.
[Nook Color Android Development] philburkhardt:
That's not always the case. At least a couple of us have said we don't have that problem with the wifi sleep policy set to never.
[Nook Color Android Development] khaytsus:
Because you're saying it's SOD. If it does wake up, it's not SOD. Period.

You might try to figure out the reason, as said, not everyone has the problem. Probably an app you are using..
[Nook Color Android Development] sinanju:
I don't doubt it. It doesn't always happen for me, either. I'm sure there is more than one factor and guess there is more than one flavor of SOD
[Nook Color Android Development] sinanju:
It seems you know exactly what causes SODs... I'm sure many would like to know, if you would care to share. Are you that sure they're not just a device taking 30 minutes -- or 3 hours -- to wake?

I am trying to figure out the reason... and posted logs. You, on the other hand, seem to be generating a great deal of heat and precious little light.
[Nook Color Android Development] fattire:
Cyan is Cyan is Cyan buffalo buffalo

Okay...

here's a new one. Call it "Cyan Edition".

Changes:

Some internal fixes to not check for keypress so much & rearrange detection.

Notification that no key presses were detected with simple "Loading..."

(If you see "Booting normally" it means it detected some presses but not recognized ones... so maybe you missed a button somewhere)

Big long probably too wordy explanation in menu for what Alt boot is.

Ditto on choosing the default boot device

Oh, and you wanted cyan. You *GOT* cyan!

Probably more that I forgot.

J4mm3r explains well what the "u-boot.default" file is for. The basic idea is that you can tell your SD card to "boot through" to emmc by default. That way you can boot from the SD card only on those occasions you want via the menu. So for example, you can have a CM7 SD card but have it normally boot "through" to stock (or whatever else) on emmc... unless you choose SD manually from the menu.

Thanks to Khaytsus for testing.

u-boot.tar.gz (cyan edition)