yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fattire:
I spent wayyyy too much time on this, but i was really annoyed by the lame-o pastel colors in yesterday's u-boot CM7 logo. I think I've got the palette issues fixed. In fact, I can do any up-to-256 color bmp now.

Also, BN, if you're reading this, you divided by the wrong image dimension in common/main.c.

- bitmap_plot (928,140,1);
+ bitmap_plot (864,140,1);

will perfectly center the charge-the-battery graphics.

Note this should be considered as experimental as always. I changed a bunch of stuff and it's after 4am so who knows what will and won't work.Enjoy.

u-boot.tar.gz
[Nook Color Android Development] Ronin3178:
Here's my last kmsg from this morning @ 98% after watching Netflix, I thought it might only be at lower batt %'s, wrong. It got sluggish, reboot fixed it.

http://db.tt/kFgfM2l
[Nook Color Android Development] deadbot1:
Yes fattire, I believe that they are when I'm getting stuttering and slow downs.

Also noted a strange thing this morn.....plugged in last night at approximately 1 am...only showing 87% and still charging this morn????

Unplugged charger from wall..left cable in NC...light went green and slowly faded out...something messed up with the handling of that power management chip?????
[Nook Color Android Development] newellj79:
Could someone please post the original mlo file (15k)? Yesterday during a moment of being very excited I copied the new mlo (17k) over it without making a back up, very noobish mistake. It sounds like this new mlo is making problems instead of solving them so I would like to go back. Thanks.
[Nook Color Android Development] seth.i.simmons:
Left my nook shutdown overnight, and then started it up this morning and tried netflix immediately and got very stuttery video and then my nook became very sluggish again. So it's very repeatable.

In my aLogcat log, i get a lot of GC_external_aloc cleared, and GC_explicit and GC_concurrent, after which it says paused for a short amount of time (50 to 460 ms usually). So not sure what to do here, since 3.1 was playing flash perfectly before this new u-boot and MLO. Could someone write me up a return to stock MLO and u-boot 1.2? That's the only way I could think of fixing this. Thanks.
[Nook Color Android Development] luciferii:
yesterday morning i was on my nook when the wifi failed... and when i mean failed i mean i thought my wifi card was broken.. the only thing that fixed it was a full wipe and reinstall.. i tried to logcat it but it didnt seem to catch anything.. anyone else have this happen?
[Nook Color Android Development] seth.i.simmons:
Just got a random shutdown at 13%, which is 5% better than my last one, but still not what it should be. Darn MLO didn't even fix that :P
[Nook Color Android Development] :
Hate to add more stuff to the already crazy thread, but maybe someone smarter than I can see a link?

Had (original) 1.2 bootloader +fresh install if beta,oc.

Got a random shutdown at around 38%.

Charged up just a bit, went into cwm, flashed the 1.2 update

Turn it on, the bootanimation just cycles, never enters Oobe.

I hard shutdown, try to reboot, but just get battery to low to boot, wait 15 mins.

So, could there be some sort of initialization that occurs during boot in the kernel that maybe we don't have? Seems weird I would get a random shutdown in beta, but BN 1.2 would "know" we've bottomed out the battery.

Also, what's the difference between "old" and "new" 1.2? Or do people mean 1.1=old, 1.2=new?

EDIT: Got enough battery on 1.2 stock to boot up. Showing 20% and dropping. Will discharge until shutdown, then fully recharge, discharge, then back to beta (if you guys haven't figured out a solution by then :P I hate stock)
[Nook Color Android Development] seth.i.simmons:
I think that what happened with the MLO is that we kept the one from 1.1 when we flashed the 1.2 u-boot, so now everyone thinks flashing the 1.2 MLO will fix the battery issues, which for me, it doesn't seem to have fixed it, and it messed up my flash somehow.
[Nook Color Android Development] sinanju:
New MLO didn't help

... still got an unexpected shutdown with the battery reported in the mid 20s. Plugging it in didn't result in the "please wait" message expected when the battery is too flat to boot.
[Nook Color Android Development] deadbot1:
Fattire ...does the MLO have anything to do with setting up the power management chip?
[Nook Color Android Development] joenathane:
Those with video stuttering issues try this mlo and tell me if you see any difference, it seems to have fixed the issue for me, I just want confirmation on the off chance that I am completely insane.
[Nook Color Android Development] SCWells72:
Rebooting now to try this out. I'm hoping it does because I'm close to going back to 7.0.3 with the OCed .29 kernel. I'm finding .32 much smoother overall, in particular the Webkit-based browsers and things like Pulse are silky smooth relative to a .29 kernel-based install, but between random lock-ups, the inability to use adb from my work Windows 7 machine (my Mac at home seems fine), and the video stuttering that leaves the entire OS in a flaky state until I reboot, I'm having trouble keeping it as a daily driver. If this fixes the video stutter, does anyone know how to resolve (or at least minimize) the adb issue and the random lock-ups?

And don't read me wrong. I'm not trying to dismiss the AMAZING work here at all. Once these little issues are worked out this REALLY makes a huge difference in the overall smoothness of almost everything, and it's clearly stated as beta, so that sets the proper expectation.

UPDATE: Nope, didn't fix it for me. I just tried to view something on Netflix that played 100% smoothly under a .29 kernel and it still stutters terribly. Admittedly I'm "only" OC'ed to 1100 under .32 vs. 1200 under .29, but I'm pretty sure it wouldn't stutter this badly at 1100 under .29. Thoughts?
[Nook Color Android Development] joenathane:
The only other thing I changed was to use this uboot, i pulled it directly from the update, what was strange was it had a different file size than what I was already using. If this doesn't fix it for you then I'm going to have myself committed.

oh yeah and double check your OC settings, some how my settings switched themselves to 800mhz conservative, no idea how that happened...
[Nook Color Android Development] newellj79:
I will try it after work but where does this one come from?
[Nook Color Android Development] joenathane:
It comes from the official 1.2 update, or I got it from a man in a dark alleyway, said he worked for the government and that if i valued my life I wouldn't do what i'm doing right now, said tha
[Nook Color Android Development] Deaks2:
So I think I found my solution. As mentioned by someone else, I wiped my nook, flashed the B&N 1.2 official ROM, getting all the goodies from the /boot partition, then wiped again, installed 7.10 beta and the .32 OC kernel.

Last night I ran the unit down, at 15% I got the low battery warning, at ~4% the unit shutdown, and when I plugged it in I got the "your nook cannot power up right now, wait 15 mins" msg.

It looks like I have full battery capacity again.
[Nook Color Android Development] :
So I did this but my shutdown percentage raised!

Can you tell me in what order you drained/charged/flashed things?

I flash 1.2 (at about 80%), then straight to beta and oc, and didn't work.

Now I drained it on 1.2 (got warning then shutdown prompt), charging on 1.2.

Will maybe drain again and then flash beta.

Let me know how you did it :)
[Nook Color Android Development] Deaks2:
i) wipe (system, data, cache, dalvik, sd-ext)

ii) flash bn 1.2

iii) boot bn 1.2

iv) wipe (system, data, cache, dalvik, sd-ext)

v) flash 7.10 beta, .32 kernel, gapps

vi) profit!
[Nook Color Android Development] fattire:
There are so many kernels and stuff floating around now and people are using odd combinations of things. Plus there are two issues I guess- stuttering (excessive garbage collection), and the battery issue. For all I know the garbage collection stuttering is some upstream thing. I was hoping MLO might have something to do with the battery issue (ONLY), but even though it seemed to fix early power drops for me, apparently not for others. Seems to be no clear correlation, so I suspect all the focus on MLO was misplaced.

I do find reports interesting that flashing 1.2 then reflashing CM7 seems to fix the battery issue. Maybe something there is clearing/recalibrating the battery.
[Nook Color Android Development] :
Well thanks for looking into it fattire. We all appreciate the effort.

Something a bit different, but I've been wondering for a while now...

Why is it:

a) I can only clear dalvik by clicking dalvik, and when it has the no-no-no-yes-etc menu, backing out will wipe dalvik (without freezing), but clicking yes freezes

b) Clicking on wipe battery stats does nothing (I've just deleted the file manually w/Root Explorer).

Always running latest CWM, have even overwritten recovery w/stock, then flash again, as well as reflashing CWM.
[Nook Color Android Development] TJNooker:
More of the same...

The new MLO didn't work for me either. This time the battery made it to 20%, then cut out just like before.

FWIW, the changes I made this round were:

1. Flashed /boot extracted from BN 1.2 that was posted here.

2. Reflashed CM 7.1 Beta 3.1

3. Reflashed gapps

4. Reflashed the 5/13 OC kernel for .32

5. Cleared the caches & rebooted

6. Charged to 100%

7. Ran Battery Calibration
[Nook Color Android Development] deadbot1:
Got a four hour bus ride home at 4. Will try to do the whole reinstall Mamba...if I can keep a decent data connection.

Edit: scratch that...how about four hours worth of logs...ill put her through the paces
[Nook Color Android Development] newellj79:
Hmm cant check right now becuz I'm at work but if it extracts to roughly 17k I'm running it right now, someone posted it awhile back. I haven't had problems but I have heard that it effects some people flash playback. I wish someone would upload the original one we had.
[Nook Color Android Development] newellj79:
When nightly 81 comes out tomorrow supposedly running the .32 kernel, should we all upgrade to it?
[Nook Color Android Development] :
Only if everyone else is doing it :P

Since 81 will beta +other crap, I think we may still have the problem we have now.

Also, what is all this jazz?

http://review.cyanogenmod.com/#change,5367

"This should fix issues with formatting NookColors with 4G /data

instead of the normal 1G /data and formatting in recovery"
[Nook Color Android Development] paleh0rse:
My plan for tomorrow (emmc):

1) full wipe

2) reinstall stock 1.2

3) full wipe

4) install n81, 5/13 OC, 5/03 Gapps

5) begin testing and discussing nightlies again

At that point, since the nightlies will theoretically have all the benefits (and issues?) of the beta, I'll be putting the beta to rest. :)

IMO, I think it's important we all do the same in order to eliminate a lot of the confusion that exists right now...
[Nook Color Android Development] :
Here here!

I think flashing bn 1.2 is key (after wiping everything).

This should definitely be the standard going forward.

An option (although maybe not the best) would be to backup your rom, then advance restore only data (although data has the battery file in there, so yeah...) but at least you can keep your apps (if you have a million of them).
[Nook Color Android Development] lafester:
the newest nooks have a different partition set up to take advantage of the new app store.
[Nook Color Android Development] seth.i.simmons:
I'm downloading 1.2 BN as we speak, I'm gonna try wiping everything, installing 1.2 (I will still be able to boot into CWM if I use the one that's supposed to keep CWM, right??), then wiping everything again, and flashing n81. Hope it works!!

Edit: so whens nightly 81 supposed to drop?? Its not available in RM or on the CM site... are all of y'all talking about n80?
[Nook Color Android Development] mutant13:
81

Update kernel to 2.6.32 with new SGX, BT

Added SGX binaries from B&N 1.2 update.

New-style BT support backported from .35

uim-sysfs temporarily put into encore board dir.

http://review.cyanogenmod.com/#change,5085
[Nook Color Android Development] paleh0rse:
This:

http://www.engadget.com/2011/05/20/psa-new-nook-color-partitioning-only-leaves-1gb-for-music-othe/
[Nook Color Android Development] :
Oh nooooooo!!!

That's dumb :P
[Nook Color Android Development] canteli:
So after two days, things are slightly different and wanted to share my experience as I'm reading now that many are flashing/wiping/reflashing bn 1.2 and saying this procedure "cures" the issue somewhat, while I'm pretty sure it'ss a bunch of unnecessary steps. Since I wrote the quoted message, I haven't recharged my nook yet, and I'm currently at 15% of battery, so I'm 9% below what used to be the lower limit before. Of course I didn't flash/wipe anything since (I am on the bn 1.2 boot though).

In light of all this, I tend to conclude that the battery calibration I did really worked, and this is how I did it:

1) Charged to 100% (supposedly)

2) Used the "batterycalibration" app that's in the market(this guy: https://market.android.com/details?id=com.nema.batterycalibration&feature=search_result).

3) Kept the Nook running, while never replugging it, until it turned off on its own (at 24%)

4) Kept the Nook plugged overnight while powered OFF.

So the bottom line is that, at least for me, it took two full charging cycles, and one discharging cycle in between, to really see the supposed effect of the battery recalibration. I think this alone is a proof that reflashing the boot partition can't really be helpful (otherwise what's happening in my case would not have any reasonable explanation.)

Hope this will help other.
[Nook Color Android Development] :
Okay ladies and gentlemen...the end all be all for the battery (confirmed by at least one of the person, so that's good enough, right :D) Doing this got me down to 2%, then it shutdown with no warning (bad? Or is this standard for CM7.1?), but once I plugged in the charger it said to wait 15 mins and try again (good!). I really hope this works for all of us. I've been not studying and trying to get this to work, so here we go...
[Nook Color Android Development] :
N81 isn't up yet. We're just talking here...

Check back later tonight.
[Nook Color Android Development] lschroeder:
I install CMW Stock Froyo 1.2 on my emmc (keep CWM) a while back before we were talking about the battery issues. I did a factory restore instead of Wipe data/system/cache/dalvik. I did not wipe anything else. I then used [ROOT][BN1.2-FROYO] MiniRooterV2 for Stock Froyo 1.2 + Stock/OC Kernel, installed Amazon app and my acquired daily free Amazon apps, also used Amazon to install free app File Expert which I set File Explorer Settings > Root Exploxer to on. From my previous backup of emmc SDcard of Titanium Backup files and a sideloaded Titanium Backup I restore users apps from Phiremod v6.2 plus the hulu flash fix.

I next loaded verygreen SDcard 1.2 with beta3.1, gapps, OC 1200. It was me that caused him to fix it to 1.2.1. I did a hack to make 1.2 work. I again sideloaded TB and its files, restoring the user apps I wanted plus hulu fix.

Can I now reboot my MiniRooterV2 Stock Froyo 1.2/OC and run it down. I have an extra 8GB SDcard that I could use verygreen's 1.2.1 to reload with a clean beta3.1, gapps OC. Could I use the clean beta3.1 one to run things down, then boot from my second good beta 3.1 SDcard and run it down to make sure everything is ok? Remember I did a Factory restore before CWM 1.2 without clearing anything else? Should I just use the Advanced Restore DATA option instead? Can someone tell me how to do this?

Though of one more SDcard option. Use nightly 81 when available and TB current 3.1 SDcard and restore it to nightly 81.
[Nook Color Android Development] camalus:
???? The suspense is killing me. Lol
[Nook Color Android Development] keyodi:
It looks like the 2nd partition is formatted then updated with some files when bn 1.2 is installed. I wonder if that clears something to resolve the battery issues.

updater-script in the romrestore.zip

*format("vfat", "/dev/block/mmcblk0p2");

Edit: NM, the romrestore.zip is not run during the install. It's just installed on the boot partition. The only files I see installed on the boot part with bn 1.2 are: MLO, romrecover.zip and charging.zip. Maybe replacing the charging.zip is the fix???
[Nook Color Android Development] :
Pretty sure you'll be good. I think anyone who has been on stock 1.2 and has at least used it a time or two can get away with doing this all. But that's just me.
[Nook Color Android Development] :
All the info is there. Does the XDA app not show quoted stuff? Check the site :D
[Nook Color Android Development] SCWells72:
So perhaps here's something useful. My current install was created using verygreen's size-agnostic SD card CM7 installer and update-cm-7.1.0-RC0-encore-2.6.32-beta3.1.zip, then the only thing I did was apply update-cm7-dalingrin-2.6.32-sdcard-051311.zip for the OC kernel. I've noticed that I don't see "Read Forever", just "Loading" and then the CM7 animated logo. Does that mean I don't have the right u-boot.bin? Is there a manual step to add that, perhaps?
[Nook Color Android Development] seth.i.simmons:
It does, I don't think you quoted anything :P
[Nook Color Android Development] seth.i.simmons:
You have the right u-boot (1.2) its just VGs is tweaked for using it in an SD build.
[Nook Color Android Development] paleh0rse:
I think there's a profile in SetCPU named after you... :P
[Nook Color Android Development] SCWells72:
Great. Thanks! Here's another weird thing I've seen. I've kind of fallen in love with the FlexT9 keyboard that was free last weekend on the Amazon Appstore, but it does something very strange under 3.1 beta that it doesn't do under 7.0.3 with the .29 kernel. When used in landscape mode, the focused text field is expanded to fill the non-keyboard portion of the screen. It works fine in portrait mode under 3.1 beta/.32 kernel, and it works fine in both orientations under 7.0.3/.29 kernel. Does that make sense to anyone? Any idea what the difference might be?
[Nook Color Android Development] seth.i.simmons:
Its a setting on most keyboards, just check the settings and see if anything talks about "full screen in lanscape" or anything.
[Nook Color Android Development] SCWells72:
Yeah, unfortunately it's not. I'd seen the setting in ThumbKeyboard in the past so that was the first thing I checked, but there's nothing in their preferences to switch the mode. I reported it to Nuance tech support and they requested screenshots which I provided. They logged it as a legitimate bug, but given the behavior difference between 7.0.3/.29 where it works and 3.1 beta/.32 where it doesn't, obviously there must be something outside of a checkbox to make it behave properly.

UPDATE: I've since changed my daily driver back to 7.0.3/.29 and as a result no longer experience this issue. I think I'll give a little more time for the .32 kernel to stabilize (I was getting quite a few lock-ups) before moving up. Hopefully by then whatever impedance mismatch was causing this with .32 will be resolved.
[Nook Color Android Development] :
Thanks a lot, now people are asking what I'm laughing at :D
[Nook Color Android Development] ali3n69:
Ok curious question will nightly 81 be considered the newer and better build of cm7 with .32 kernel or is the beta builds features just making its way into nightly? pretty much should I run n81 when released or beta3.1 still to have the latest bug fixes and features?
[Nook Color Android Development] xc68000:
you really shouldn't assume anything with a 'nightly' build. on the scale of stability/useability it goes rc > beta > nightly.

because your asking the question, I would stick with the beta until another one is release by dal.
[Nook Color Android Development] 12paq:
Good question, time will surely tell.
[Nook Color Android Development] ali3n69:
I understand the process of rc>beta>nightly but that truly doesnt seem the case with cm7 as the beta had .32 kernels before the nightly it actually seems on a different build path altogether. that is why I ask the question. because arnt the nightlies made from dals help as well?
[Nook Color Android Development] Nburnes:
Just to mess around, I built it up to "Reduce Call Answer Delay (android_frameworks_base)". http://cm-nightlies.appspot.com/?device=encore

Booted up just fine with the stock .32 kernel included. Then flashed OC kernel and I haven't seen anything weird from it. Very fast, on/off animations, 2.3.4, Mount to USB, BT and it does sleep, according to CPUspy.
[Nook Color Android Development] ali3n69:
Thanks this is what I was wondering about I guess time will tell.
[Nook Color Android Development] MACLUIS1:
And the range of BT, any progress?.
[Nook Color Android Development] :
Geez Nburnes, you're such a tease!

Posted link (or PM), or it didn't happen :P
[Nook Color Android Development] deadbot1:
http://db.tt/6Tc5Nab

http://db.tt/OmaCrdi

http://db.tt/kXdyJe1

http://db.tt/TQnbHIw

Here's a few hours worth of logs...not sure if it got caught but I had bad stuttering leading to a total lockup at end.
[Nook Color Android Development] :
BT range is much better in beta. Should be the same in this coming nightly, since both have new drivers.
[Nook Color Android Development] MACLUIS1:
I didn't notice any difference in Beta. At least not my Motorola Sd10.
[Nook Color Android Development] Arbelzapf:
Oh by the way : Bluetooth keyboards seem to be broken. Just for the record
[Nook Color Android Development] victle:
I got bt range of 5 feet with this beta build and .32 kernel when connecting to the gps on my phone, pretty impressive. Much better than previous versions I think.
[Nook Color Android Development] MACLUIS1:
I believe the problem is Bluetooth transmission. The GPS from your phone would be reception. It can't transmit audio farther tan 1 feet I think.
[Nook Color Android Development] flipper2006:
Quick question. i was using last weeks nightly, i think 74 and i went to install the 80 build but after it was done with the load and gets the android screen on the bottom (for 10 seconds), then cursor goes to upper left with a line and nothing else (normally it would say android with the logo in the center of the screen).

I rebooted, but no luck..i have a nandroid and TB backup so im ok, but just wondering why it happend. it was rock solid with 74 other then a very painful problem where when i plugged in usb cable and went to connect to computer, the window would blink right off and never allow me to connect to PC. I figured this might have had it fixed so i updated. Now i have nothing , lol.

I will wait for 30 minutes to see if anyone replies before reloading..
[Nook Color Android Development] hirano:
Is this new nightly better than the beta?

What about flash movies cache/buffer error?

And the usb mount support was included or you used that app?
[Nook Color Android Development] :
My bluetooth keyboard works fine with beta
[Nook Color Android Development] newellj79:
I think 80 is one if the builds that u need the. 32 kernel for. Nightly 77 was like that. Give it a shot before u restore your backup, it can't hurt. Use dalingrins kernel link in the op of his oc kernel thread, I believe its under test kernels.
[Nook Color Android Development] MadMikeSS:
I had to flash the OC kernel with 80 when I updated. Moved up from 78 where I needed it as well, tried to just flash 80 by itself and ended up with just the frozen cursor in the top corner, went back in to recover, flashed the OC Kernel, booted up fine.
[Nook Color Android Development] flipper2006:
Thanks both you guys. I will try that. I wish i knew that. It's getting confusing using Cy7 for Vibrant and Nook. Very simular now and some of the steps get mixed up :)
[Nook Color Android Development] joe2262:
Oops, forget it.