yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] joe2262:
Another data point.

Upgraded Beta 3.1 to N82 with 5/13 OC kernel. Today things got sluggish when the battery hit 21% but the sluggishness went away for a while before coming back. Then I remembered the suggestion to record voltages.

20% 3608mV

18% 3621

17% 3610

16% 3575

15% 3601

14% 3606

14% 3587

13% 3596

Note the apparent rise in voltage at 18%, 14% and 13% which correspond to the Nook just sitting there doing nothing. I did get a low battery warning at 15%, when it reached 13% I plugged it in to the AC as I don't generally deep discharge Lion batteries anyway.

Currently the Nook is at 38% and 3936mV and the sluggishness persists, time for a reboot.

Finally, I think the sluggishness starts when the battery dips below 3610mV??
[Nook Color Android Development] martian21:
Framework.jar with IMEI number

I've posted a thread with modified framework.jar files which allow Swype Beta, the free XDA app, HBO Go, and probably others to work.

Thread is http://xdaforums.com/showthread.php?p=14045926#post14045926

This is based on the work of mthe0ry here
[Nook Color Android Development] wumpus11:
This worked nicely for me, thank you. Nook was shutting down at around 30%, now gets close to 0 before powering off. And although I used the above-mentioned battery calibration app, by all reports it would have been enough just to remove /data/system/batterystats.bin.
[Nook Color Android Development] pseudo_nomen:
WiFi Cycling

My WiFi is doing the same thing - cycling connection state every 10 to 30 seconds on my home network which is WPA2 - AES. It connect fine. Then 10 - 30 seconds later it disconnects, and then reconnects. Ad Nausuem.

This happens on every combination of Nightly 81 - 84, stock kernel and Dal's 5/13 2.6.32 emmc OC kernel. My install has consisted of everything from a dirty flash over stock B&N 1.2 to a full bare install over freshly formated system/data/cache/dalvik to various levels of clean installations over Dal's 7.1.0-RC0-encore-2.6.32-beta3.1.zip.

What does work - WiFi is absolutely ROCK SOLID on Dal's beta3.1, both on the included kernel or the 5/13 OC Kernel.

I've tried various combinations of forgetting saved networks and deleting /system/etc/wifi/wpa_supplicant.conf, and forced power-offs, clean reboots and fixing permissions.

I'm kind of at my wits end here. No matter what fixes I try to apply, I cant seem to get the last few nightlies to do anything but cycle connection state every 10 - 30 seconds.

Full LogCat Attached showing 2 cycles of disconnect/reconnect. All the disconnects seem to be preceeded by:

05-22 17:22:14.551 D/EAS SyncManager(1403): !!! EAS SyncManager, onCreate
05-22 17:22:14.557 D/EAS SyncManager(1403): Creating Intent with time(ms)=22876
05-22 17:22:14.574 D/EAS SyncManager(1403): !!! EAS SyncManager, onStartCommand
05-22 17:22:14.613 D/EAS SyncManager(1403): !!! EAS SyncManager, stopping self
05-22 17:22:14.619 D/EAS SyncManager(1403): !!! EAS SyncManager, onDestroy

I'm not sure if this is actually the culprit or not - the only email I have setup is my standard gmail account.

Hopefully the logcat will give a clue to someone that can do something with it.
[Nook Color Android Development] jlt220:
DO NOT FORMAT YOUR SD CARD IN CM7. DUE TO A VOLD ISSUE THIS WILL FORMAT YOUR /BOOT INSTEAD OF THE SD CARD!

****Should be fixed in nightly 13****

is that still accurate or has it been fixed already?
[Nook Color Android Development] joenathane:
That's very old, we are already up to nightly 84.
[Nook Color Android Development] RoboRay:
Yes, it's old, but the warning is still prominently posted with no statement confirming that the issue actually has been corrected.

I guess that's why the question comes up from time to time.
[Nook Color Android Development] joenathane:
Yeah, very true, documentation has never been the best around here, but you can't complain too much, we have some really great and amazing developers and developments around here.
[Nook Color Android Development] jlt220:
I thought it was old, but I just wanted to check. Also it looks like WIFI cycling has become an issue? has there been a fix yet on that?
[Nook Color Android Development] angomy:
Getting errors in device-check-disabled Netflix and default videos player in nightly 84. Netflix gives some odd out-of-cloud error message after trying to log in. Reinstalled it, and after timing out several times on login it gave the same error again. Video player quits out with an error about the music app (??) every time I try to play any video. Music player plays fine.

Wireless seems pretty stable but I'm not sure how related it is to the Netflix timeouts and cloud error msg.
[Nook Color Android Development] seth.i.simmons:
The Netflix issue seems to be just that - an issue with Netflix itself. There's been a ton if reviews by people with the same issues. Mines not working either, they better get it fixed fast, my months running out! Lol :P
[Nook Color Android Development] GabbleRatchet:
Getting the same Netflix error, but I'm using the version that requires the htc/vision build.prop edit. It worked perfectly on beta 3.1
[Nook Color Android Development] legolee:
just did a clean install of n84 with .32 OC kernel!

the NC is becoming faster and smoother.

finished reinstalling all apps via market & appbrain, so far no system freezes nor SOD.

Shall use it for daily and report back.

I notice scrolling is so much smoother on n84..like scrolling in Plume.

It is still very smooth when cpu is at 300/1200 ondemand!!!

Shall also test PPTP/L2TP/OpenVPN and report back!

You guys are awesome!

p.s. sorry, i am in HK, so cannot test the netfixs

p.s.2. got a SOD..have to hard reboot. ~_~ i think i have only turned off screen for 4-5 times only
[Nook Color Android Development] joenathane:
Loaded it up and so far so good, looks very sexy.
[Nook Color Android Development] skwalas:
Crud. I'm just itching to try this, but I'm not brave enough to be "first". Maybe tenth?
[Nook Color Android Development] fattire:
Just made a quick improvement-- Dalingrin gave the kernel some more breathing room, so I did the same for the alt kernel.

In case anyone was wondering, one scenario where you might have an alternative kernel/ramdisk is if you want to have both the stock kernel as well as Dalin's OC kernel. (CM7 update.zips will only overwrite uImage, remember). Another scenario is you may want to have an alternative recovery or something.

Anyway I updated the link in my post above with the new link.
[Nook Color Android Development] newellj79:
Flashing now...
[Nook Color Android Development] Arbelzapf:
#84 still has the Wifi cycling issue :( Flashing back to beta again
[Nook Color Android Development] biz18434:
I have been running j4mm3r's menu with no issues. I gave your version a try. The menu boots up with no issue but when I select recovery boot I end up with a black screen. I have to power down to restart but now it loads only from the EMMC not the SD card. When I select the N button during boot, I get the boot menu so this time I tried Alternate boot and I got the same result (black screen). I power down and removed my sd card and replaced u-boot.bin with the j4mm3r's menu version and everything boots up just fine. I love your features but for some reason I cannot get my nook to boot right.
[Nook Color Android Development] seth.i.simmons:
So I really want to try out this new uboot, but I'd love to have a flashable .zip to restore my current u-boot if I screw something up. I'd love to make one myself, and get into that, but I'm not exactly sure how to create my own signed .zips. Can anyone point me to a good guide on creating my own, or if not, could someone post a flashable .zip that I could modify to use my current u-boot? Thanks!
[Nook Color Android Development] rhester72:
Version compatible with VG's SDcard image? Pretty please? :)

Rodney
[Nook Color Android Development] Ronin3178:
Here are my data points, (flashed the 5/23 OC kernel at about ~3x%, but I haven't have any early shutoffs b/t 3x & 2x in the few charges either.

25% 3668mV

24% 3653

23% 3655 23% 3660

21% 3603 21% 3630

20% 3590 20% 3629

18% 3612 18% 3624

17% 3601 17% 3616

16% 3565 16% 3616

15% 3585 15% 3604

13% 3575 13% 3606

Now, this may be obvious to some, but since I work with UPS batteries for work, this made sense to me once I saw it. When a battery is being drained, and the load lightens, it will come back up in voltage some. The second data point for each %age when I got it was after a few seconds of sitting in the Battery Booster app watching the voltage. This app and probably the whole system, drops the %age at a certain voltage, if it raises back up it will not raise the %age. If the device is rebooted however, it will compare the voltage to % list and may assign a higher %age.

Anyway, this may be a mute point, I haven't seen any posts in a while about early shutoffs.
[Nook Color Android Development] nemith:
Already is.
[Nook Color Android Development] nemith:
This is more of a beta test. This will be included with the CM7 update.zip eventually for those who want a .zip.
[Nook Color Android Development] sinanju:
Issues I still have as of #84 with the Dalingrin 5/23 kernel (though I have these issues with the stock kernel):

- Frequent delayed screen power on if it was powered off with WiFi active (WiFi off when screen off policy)

- MP3 audio playback skips -- probably about 1/minute, which represents a step backward from .29

I don't know about the battery, yet -- I'm tired of playing Angry Birds to burn down the battery. I have an older device on my network that requires me to use WEP, so I'm not having the WiFi issue.
[Nook Color Android Development] khaytsus:
It's pretty easy.. Get CWM on SD card, put the new u-boot stuff there, boot up using it, mount the SD card, copy your current u-boot.bin to the SD card and perhaps go ahead and copy it in the /boot as well so you have a copy in the device.. Then copy the new u-boot.bin into /boot.

Sorry, don't have my CWM card with me or I'd give you exact commands on what partitions to mount, etc, but if you've done any of the above before it should make sense. You could also use adb from a CWM card to do the change or restore the change.

A flashable zip for one file is kinda silly, especially when it's changing frequently ;)
[Nook Color Android Development] cpuks:
Excuse me but this is latest custom u-boot? I should put it onto Nook Color with root explorer? I found on CyanogenMod wiki that latest nightlies deliver custom u-boot - where can I find it?
[Nook Color Android Development] rhester72:
Negatory. Straight into eMMC.

Rodney
[Nook Color Android Development] junkrobot:
I just went back to try to verify this, but I can't seem to find any mention of whether nightly 85 plus the new OC kernel will solve the problem of early shutdowns at around the 30-20% mark. Anyone have any idea?
[Nook Color Android Development] victle:
It can only boot from SDCard if select from the bootmenu. All other shortcuts default to eMMC.

@fattire: Could you change it to default boot from the same place as the custom u-boot:

- When the custom u-boot.bin is on the eMMC, the uImage + uRamdisk are loaded from eMMC

- When u-boot.bin is on the SD card, the uImage + uRamdisk files are loaded from SD card.

This is for the people running CM7 off SD card.

Many thanks!!!
[Nook Color Android Development] rhester72:
So here's the weird thing - if I create a u-boot.device (on either partition 0 or 4) with a value of "0", it still goes straight into eMMC...but if I just hold the n key down on boot and leave the defaults (SD/normal) on that menu and tell it to boot, it boots to SDcard instead of eMMC. WTF?

Rodney
[Nook Color Android Development] seth.i.simmons:
Yea, I would just use that one zip to do all of my u-boot updates in the future, but its cool. Actually never knew you could do all that with CWM, good to know that!
[Nook Color Android Development] fattire:
So if I'm understanding you right, you're trying to use it with an SD card and it keeps loading to EMMC? Is this right?

Like I said I haven't tried it yet w/SD so wasn't sure what would happen... what happens when you let it boot "through" off of SD without any menu pressing at all?
[Nook Color Android Development] fattire:
Are you booting off emmc or sd in the first place? Also the defaults are emmc/normal not sd/normal. And finally, if you choose SD/normal shouldn't it do what its' doing, which is booting to SD card?

I'm a little confused...
[Nook Color Android Development] victle:
If no button pressed, or pressing power+n, vol+ vol-, will boot to eMMC. Can only boot off SD images if press n to go to bootmenu and select SD from there. Please see my post and modification request above. Thanks!
[Nook Color Android Development] rhester72:
Sorry - in my initial post I indicated that I'm booting off VG's 1.2.1 SD image - and the default when booting off SD (at least as far as the menu is concerned) is definitely SD/normal, though I assume it's just determining that from where the u-boot is located. It's just odd to me that it wouldn't bootstrap all the way up off of whatever media it started from (i.e. default to eMMC for eMMC installs and SD for SD installs).

Rodney
[Nook Color Android Development] paleh0rse:
With respect to all involved, this whole uboot menu thing seems like it should be in a separate thread, and we should be focusing purely on CM7 nightly dev at this point...?
[Nook Color Android Development] fattire:
Well this u-boot should end up in the cm7 nightlies...

Re: the SD bootup. I see. The problem then people are having is with using the u-boot on the SD and booting from the SD.... okay I guess i'll have to actually burn a bootable SD and try it out...
[Nook Color Android Development] paleh0rse:
oh...

Will there be a way to turn it off or opt out? I'm not so sure it's a good idea to display alternate boot option(s) if/when they're not actually installed -- IOW when someone uses just a standard install of CM7 on emmc, they shouldn't see the vol+/vol- option at startup, since it wont actually do anything. Make sense?

I guess we could always go back in and re-install stock 1.2 boot files after each new nightly... would there be any actual performance improvements we'd lose out on?
[Nook Color Android Development] fattire:
Yeah I'm guessing the final version boot screen will look different. I just threw up that "menu" as a quick illustration of what it can do. One option is to not say anything, as people won't know what "alt-boot" means, for example. I can see arguments for both providing full information as well as not including everything. Also, I realized I hardcoded the emmc-boot with the keypresses, so I have to fix that, probably this afternoon. So if you're using SD, standby.

There are fixes to this u-boot besides the cosmetic and the boot menu. They include SD-support stuff from verygreen + more breathing room for larger kernels from Dalingrin + other things. You can install stock 1.2 u-boot, but they may not work as well especially with newer nightlies...
[Nook Color Android Development] rhester72:
Might not be worth the effort, but perhaps build the menu based on "auto-detection" of whether the features are available or not based on the presence (or not) of the required uRecImg/altRecImg, etc. files? The less hardcoding, the better...but good lord do I dig the graphics and menu layout, which is why I was jonesing for it to work with VG's image. It looks -fantastic- and really sets CM7 apart!

Rodney
[Nook Color Android Development] sinanju:
I finally got my laptop back and I've been able to monitor the log set to verbose while playing MP3s. I'm getting audio dropouts pretty regularly, but they are not coordinated with anything coming out of the logs. Unlike previously, there are no delayed write messages... GC messages don't coincide with the dropouts, nor does the only other frequent activity in the log: EAS SyncManager waking up several times/minute.

Very frustrating.
[Nook Color Android Development] pbcal:
No deep sleep on #84 with OC

I have updated my NC to #84 with latest OC kernel and now it does not sleep. Spareparts is showing its 100% running.:mad: Coming from beta 3.1 when it used to sleep without any battery drain.
[Nook Color Android Development] Arbelzapf:
Okay so I just did a complete wipe to see if I would still have the Wifi cycling issue on a fresh system and yes sir, I still have the Wifi cycling issue.

I even did the 1.2-restore dance beforehand to rule out that possibility and also to maybe get rid of the 25% shutdown if it's still there on the nightlies.

Just wanted to point that out. It doesn't seem to be related to a faulty install
[Nook Color Android Development] paleh0rse:
Fair enough. As always, I'm looking forward to what you guys come up with! :)
[Nook Color Android Development] :
Yeah, I think it has to do with the new OC kernel. I'm still on beta, but updated to the latest kernel and it's sleeping fine right now. When it wasn't I restarted, and it seems to have fixed it. logs and such are normal.
[Nook Color Android Development] :
Is there a GUI way I can drop in the new bootloader? I know I could use terminal or adb, but to lazy to type and no cable on me atm. Could I trick root explorer into showing my other partitions?
[Nook Color Android Development] khaytsus:
Nah, it's fine here.
[Nook Color Android Development] abs99:
original .32 release better?

I have been testing the various CM7 releases from this thread since they first came out and I keep reverting back to the original release from Dal. I suspect that a lot of folks had not updated their original uboot to 1.2 which caused quite a bit of confusion before it was identified as a problem. I can state with absolute certainty that in the original build, my Wi-Fi is completely stable on a WPA2 connection and that my signal strength is also superior to either of the two beta builds or the new nightlies. I also never experienced the edge sensitivity issue corrected in the later builds except in rare circumstances. I do not use bluetooth so I can not attest to bluetooth performance. Using that original build with the original 800mhz kernel, I have never experienced any slugishness on wake or strange shut downs. The ONLY problem I have regularly observed pertains to the battery levels being off which appears to be some kind of issue with the 1.2 setup. I have not tested video extensively on this build however.

Bottom line, I would suggest folks go back to the original build and retest if experiencing strange behavior in the newer betas/nightlies.

Also, if people can post feedback on this and have similar experiences as I have perhaps we can persuade Dal to apply his overclock code to this original kernel version . . .

For reference, I am talking about the build named: update-cm-7.1.0-encore-2.6.32-signed.zip .
[Nook Color Android Development] lafester:
85 + new oc is running great so far.

thank you thank you thank you :)
[Nook Color Android Development] variable47:
Same here. This is my first use of the .32 kernel and all seems well with the world. :) Good job devs!!!
[Nook Color Android Development] taylor.fowler:
For the lazies...

Attached is a CWM flashable zip to update your u-boot.bin to fattire's newest with the boot menu. It *should* (as in it did on mine, and that's what the script is designed to do) create a backup of your current u-boot.bin with a .bak extension should you care to revert.

Thanks fattire...it looks a LOT better than the pastel skateboard guy :) AND it's functional.
[Nook Color Android Development] fattire:
Try, try again...

Heheh.. Wanna do it again?

Okay, this has some improvements over yesterdays u-boot menu:

* Now tested by two people (verygreen & Khaytsus, thanks!) on SD. They tell me it works from SD.

* Better notification of what it's doing and why.

* UI Improvements

* Text improvements (explanation of what "Alternate boot" is, etc.)

(updating the other links as well...)

Please read previous notes on running at your own risk, etc. But I'd be interested in hearing comments/problems.

u-boot.tar.gz
[Nook Color Android Development] :
Can't I just use 7zip to drop in the new boot into the zip?

If so, I have a new flashable zip ready
[Nook Color Android Development] taylor.fowler:
Poor timing, sir.....but who am I to argue?
[Nook Color Android Development] :
Any word on a battery calibration fix?
[Nook Color Android Development] taylor.fowler:
Yep. Just drop it in the boot folder in the .zip and it's good to go.

Like I said, it's for the lazies. :)
[Nook Color Android Development] angomy:
Using fattire's (untimely ;)) updated u-boot.bin on verygreen's SD install. Was running nightly 85, going to flash latest OC kernel to see if I run into any problems. Booted into SD install by default fine.

Was able to flash OC kernel, however, while it boots into SD and recovery fine, it's not booting alternate (EMMC unrooted stock 1.2)

Just sits at the "booting into alternate...." and does nothing :|
[Nook Color Android Development] angomy:
I'd made a fresh install of this with the latest 1.2 verygreen and it was exhibiting Flash-based video problems for me (system slowdown). Unlike nightly 83-85, where the only Flash-related problem I've run into is with the modded apks for Netflix that have chipmunk voices.
[Nook Color Android Development] paleh0rse:
I love that I'm finally able to tell when I've successfully pushed the buttons to enter recovery! Very slick my friend, very slick. :)
[Nook Color Android Development] fattire:
Yah, I was like... "hey wait a sec...I can do this :)" Seems insane that it wasn't there before...
[Nook Color Android Development] paleh0rse:
I fully retract any/all concerns I voiced about you messing with uboot. I'm sold!
[Nook Color Android Development] biz18434:
fattire, yes that is right. It keeps loading to EMMC. The same thing happens when I let it boot "through" off the SD card without any menu pressing at all.

When I press n button, I get the menu and if I select recovery boot I get a black screen. If I press the power button and n button, I boot into the EMMC recovery. My nook is stock and I run everything off the SD card. Thank You for all your hard work.
[Nook Color Android Development] fattire:
Try the new one.
[Nook Color Android Development] angomy:
Fattire, noobish question: Is the boot into alternate hanging because my EMMC stock is unrooted? Wasn't sure if this mod needed to push files to EMMC as well.
[Nook Color Android Development] altimax98:
forgot to rotate the pic.... but

:)

Nightly 85 1.2GHZ .32 kernal Performance Uboot 5/23 = Fastest ive seen so far on my device
[Nook Color Android Development] rickypreacher:
gapps market

I loaded latest cm7 nightly and i load gapps but the gapps want come up and when i finish can so one help me
[Nook Color Android Development] fattire:
The alt boot is for starting up a third kernel rather than the regular one or recovery. Its sort of a newish boot feature. You need to decide what you'd like it to be/do and set it up accordingly.... an example might be a backup non-overclocked kernel if you're using an oc one as your regular uImage... aside from a new kernel you also set up an alternate ramdisk to go along with it. This might be oh I dunno another recovery like amon ra recovery (if it exists for encore). Or maybe with some clever partitioning you might have a nookbuntu or nookie froyo or even a totally separate cm7 alt boot setup... or keep stock and cm7...

Hope that makes sense. I'm on my phone now but that's the short answer.
[Nook Color Android Development] biz18434:
Thank You, I tried the new one but I had no luck. It would only boot my Atl image which is Verygreen size-agnostic SDCard v1.2.1. However when I switched out my SD card and loaded my CM7 sd card everything worked great. Could it be an HC issue not related to your great work?