yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] fattire:
Looks like this will be in 7.1 as 7.0 is shipping tonight. :)
[Nook Color Android Development] lafester:
too bad 7.0 would have been better with this included :)

not bad though considering where we started. i'm only going to be on 7.0 for one more build anyway :p
[Nook Color Android Development] lafester:
7.0 stable is up :)
[Nook Color Android Development] tubbymac:
Amazing work fattire!
[Nook Color Android Development] fattire:
The u-boot.bin

Okay, due to popular demand, here's the u-boot.bin I used to fix screenshots.

Note that this is a test file for devs only and you use it at your own risk, etc. It will likely break dual-boot devices. It may slap your best friend in the face. Just don't use it. It's untested.

Except that it did make Shootme work for me :)

It's GPL'd so read the license. Source is identical to BN's source release with the following two changes:

in /u-boot/include/configs:

diff omap3621_evt1a.h.orig omap3621_evt1a.h
252c252
< "commonbootargs=console=ttyS0,115200n8 androidboot.console=ttyS0 initrd rw init=/init videoout=omap24xxvout omap_vout.video1_numbuffers=6 omap_vout.vid1_static_vrfb_alloc=y omap_vout_mod.video2_numbuffers=6 omap_vout_mod.vid2_static_vrfb_alloc=y omapfb.vram=0:8M no_console_suspend" \
---
> "commonbootargs=console=ttyS0,115200n8 androidboot.console=ttyS0 initrd rw init=/init videoout=omap24xxvout omap_vout.video1_numbuffers=6 omap_vout.vid1_static_vrfb_alloc=y omap_vout_mod.video2_numbuffers=6 omap_vout_mod.vid2_static_vrfb_alloc=y omapfb.vram=0:3M no_console_suspend" \
322,330c322,330

Additionally the image in tools/logos/o_nookcolor_logo_large.bmp was changed to give the boot a more distinct look.

It would go in /dev/block/mmcblk0p1 (emmc) or /dev/block/mmcblk1p1 (SD) aka "/boot". If you don't know how to put it in there, you DEFINITELY shouldn't be trying this.

But don't bother trying it, as tomorrow there should be a kernel-based version that won't require a different u-boot. Dalingrin's all over that, since he's got like a zillion kernels...

If you do try (at your own risk), back up your u-boot.bin, puhlease, so you can replace later. And if you discover stuff breaking or something, please post here. There's a lot I haven't tried, since i'm still on the .32 kernel.

u-boot.bin.tar.gz
[Nook Color Android Development] Gin1212:
Does this mean he's finally working on the ultra cool top secret honeycomb source kernal with the secret software to push our gpu's and cpu's way past their limits while frying our brains from how loud the speaker has become, as we sit and type with our bluetooth keyboard from 50ft away and watch The Watchmen in 1080p with hardware acceleration!? With a new 20" 1280x1024 display (software based granted) that shoots out the back as it loads up Ice Cream and gives honeycomb the middle finger?
[Nook Color Android Development] samuelhalff:
Thanks fattire. Always great to have you around.
[Nook Color Android Development] 911jason:
Works great Fattire, thanks!!!
[Nook Color Android Development] eozoon:
Thanks, that worked beautifully. Nothing is broken as far as I can see.
[Nook Color Android Development] shad0wf0x:
I would like to thank Dalingrin, Fattire and Mad-murdock as well as the rest of the CM team for all their hard work bringing us 7.0 release! Thanks guys and keep up the GREAT work!
[Nook Color Android Development] ErikJDurwoodII:
What better way to celebrate this thread's 1,000th post?

A stable 7.0 release party!

Even if I'm the only one at it...
[Nook Color Android Development] cybertimber2007:
Kudos to the CM team and all those who have helped reach the CM7-stable goal for the Nook Color!
[Nook Color Android Development] bradputt:
Hi fattire,

could you please post the u-boot.bin file again?

i cannot download the file from the link.

Thanks!
[Nook Color Android Development] lafester:
just tested... download works fine :)
[Nook Color Android Development] bradputt:
serious, megaupload sucks in my country

i'm getting:

The file you are trying to access is temporarily unavailable. Please try again later.

could you please upload using zshare or deposit files?

greatly appericiated :D
[Nook Color Android Development] Jiggity Janx:
So I may be totally shunned for throwing this in here, but from what you posted above I believe the accepted assumption is that the resolution for CM7 (the Nook at large) should be 1024x600 (I reasonably understand it is upscaled).

One thing I found recently that I wanted to ask about was why screen test apps (like ScreenTestToolkit) return a screen resolution value more like 863x1456 (or some skewed numbers close to that)? Is the fact that they are returning values like that important for the multiple discussions I have seen floating around about apps not displaying properly or your discussion above re: memory?

I'm no dev but do come across some things I see that could logically cause concern.
[Nook Color Android Development] MACLUIS1:
Could somebody take a look at the XDA app and see why it doesn's allowed to login?. The Droid Forums app works perfectly and it is from Tapatalk Also. This may not be the proper place but since it is for the benefit of XDA.
[Nook Color Android Development] fattire:
Try "direct download" (the first link)
[Nook Color Android Development] bradputt:
hey thanks fattire, working great!

great job!

Thanks!
[Nook Color Android Development] gordon1hd1:
@fattire are you sure that Nook Color IPS panel is only using 65k color (2 Byte per pixel)? From the B&N Nook Color webpage: http://www.barnesandnoble.com/u/nookcolor-feature-color-touchscreen/379002480/?cds2Pid=35583, it show that NC is 16 million color (3 Byte per pixel).

1024 * 600 = 614400

* 3 byte per pixel (16 million color)

----------------

1843200 bytes for one buffer

*2 buffers

-----------------

3686400 Byte

So shouldn't the correct value to use for vRam for double buffering being 4MB?
[Nook Color Android Development] fattire:
Very possibly... :) I went with 2 as an experiment (just from following the discussion on the TI site) and it seemed to work. But you're probably right.

In any event, I want to see if people have problems with 3M. But I also built a 4M version, so here it is...

(note I haven't tested at all.. just built and uploaded. Your results may very. Think friend-face-slapping vary.) Again, this is for DEVS only. And btw, I really seriously haven't tried it at all.

u-boot.tar.gz

Update: Tried it. Also seems to work. If anyone has problems with the 3M one, or notices a reduction in colors or something, give this one a shot. Thanks for the catch.
[Nook Color Android Development] bradputt:
hi fattire

i have tested the 4m version, yes it works but i can't see any difference in color reproduction between the two, looks the same to me.
[Nook Color Android Development] gordon1hd1:
Have you try playing video with either kernel using both software and hardware decoder? Is there any difference?

Also might want to try run a couple benchmarks like Neocore and others, to see if there is any performance difference. In theory since 3M version can only fit a single buffered frame, you should get better performance from double buffering in the 4M version (in theory :p)
[Nook Color Android Development] bradputt:
Yes, tried to play a few videos. Frankly speaking I don't see any difference in the quality. Still laggy on some 720p videos.

But I'm not really a video expert, sorry
[Nook Color Android Development] chisleu:
Don't use the 4/4 kernel for playing video as it has a stutter issue. The stock CM7 or dalingrin's 3/31 OC kernel is working beautifully.

I will install the 3 and 4 meg version and check colors w/ high quality pictures and hardware accelerated video.

EDIT: No I won't because I'm scared to mount it because I don't know what I'm doing. :)
[Nook Color Android Development] mr_fosi:
Should partitions be wiped before the stable is flashed or will it fir over one of the 2x nightlies?
[Nook Color Android Development] Nburnes:
Def going to have to flash newer one when I am home. I get terrible screen tearing I didn't use to have whilst browsing.
[Nook Color Android Development] gordon1hd1:
Is this with the 3M kernel or the 4/4 kernel? Also can you report back once you check the 4M kernel?

Just another thought about the vRam buffer. Does anyone know for certain that the NC 16million color display use 3 Byte per pixel? I read somewhere that companies are starting to use 4 Byte per pixel displays to added brightness support....
[Nook Color Android Development] Nburnes:
That was 3M with 4/4 kernel. Borrowed a PC from the lab and flashed new 4m uboot, have no problems thus far a.k.a quickly scrolling through thread list.

Edit: Actually his 4/5 kernel he posted in user thread I think. Was supposed to fix Bluetooth again.
[Nook Color Android Development] fattire:
Well that sells me. Move aside 3M, 4M is the future!

:)
[Nook Color Android Development] lafester:
about the only bug left is reboot into recovery from the power menu :)

i suppose voice input through bt would be nice but hardly a bug.

you guys have done an awesome job!
[Nook Color Android Development] Nburnes:
Interesting! I didn't even know reboot to recovery option didn't work. Well, now I do I s'pose...:p
[Nook Color Android Development] Nburnes:
I don't think double posts are allowed, but it looks like I spoke to soon. Screen tearing is still present when moving through web pages. :( And when going back to normal uboot, no tears or anything :(

Edit: Also seems to happen in some games. What I mean by screen tearing is a single vertical line showing up with the image(s) jarred, then they fit back together fine.
[Nook Color Android Development] fattire:
Hmm. Maybe 5M? <shrug>

Anyone else having these issues? I haven't had a chance to try yet.
[Nook Color Android Development] gordon1hd1:
Ya looks like if we assume 4 Byte per Pixel 5M should work, lets see if that fix the tearing issue:

1024 x 600 x 4 Byte x 2 Buffer = 4,915,200 Byte
[Nook Color Android Development] Nburnes:
Well I'll gladly test whatever happens. Need to get my own machine set up still.
[Nook Color Android Development] jtbnet:
I found that for most of the SDcard installs the u-boot.bin just ignores the attempt to Hold Nook Key to boot to Recovery... there are a couple u-boot.bin that work fine around ... I posted this one a while for folks to fix the problem and I deliver it on the SDcard template I put together in another thread but it's not actually used in that template as it uses j3mm4r's multi-boot u-boot.bin...

Just remove the extra extension I used to get it to post here and move it to you /boot partition and N key should work for recovery again....
[Nook Color Android Development] fattire:
Okay... (don't) test this. It's 5M. Which would assume 4 bytes per pixel, which Dalingrin suggests may actually be right. Though who knows what they're doing with all that info per pixel...

Interestingly, BN commented out in the u-boot source a line which does set 5M.

Anyhoo. Here it is. Screenshots still work w/this, but I haven't put it through the rigors y'all will.

u-boot.bin.tar.gz

And here's another one where the video numbuffers has been reduced from 6 to 3, unused vid2 is eliminated, and no_console_suspend was removed too, for good measure. Still 5M.

u-boot.tar.gz
[Nook Color Android Development] Nburnes:
Well I (haven't) flashed it, and it (hasn't) produced any tearing thus far! This (doesn't) go for both of them.:cool:

Time for bed though, classes in the morning. (Won't) test more tomorrow.
[Nook Color Android Development] fattire:
Something else (not) to do.

To follow up on this from a while back, here's something else (not) to test:

While online, (don't) go to Settings->Date & Time settings, and (don't) make sure your time zone is correct but (don't) set your time to something wacky and wrong.

Then from the shell, (don't) type:

date

to see the currently set date. Then (don't) type:

/system/xbin/ntpd -Np pool.ntp.org

Now (don't) wait like 30 seconds and (don't) type:

date

to (not) see if the time is corrected.

Then (don't) hit home and then go back to Settings->Date & Time settings and set the date so it (doesn't) register on the notification bar.

Don't do any of that. And certainly don't report any observations here.

If this turns out (not) to be a good way to (not) keep time synced, it might (not) be good to (not) set it up as an always-(not)-running service, which could (not) be done in 2 lines or so in the init file. (Not.)
[Nook Color Android Development] :
Not sure if the CM7 devs would be into updating the CM7 encore nightly with a fix, but as far as I know the Nook app is unable to download ebooks from Barnes and Noble when running CM7 from the sd card.

I'm not sure if the fix would be related to this solution:

http://xdaforums.com/showthread.php?t=966339
[Nook Color Android Development] bradputt:
Hi fattire,

i followed everything and indeed it jump back to the correct time and date.

BTW your don't don't not not is making me dizzy.;)
[Nook Color Android Development] fattire:
It should stay in sync so long as you're online. Let me know if you notice any significant drift.

Dunno if this is something to just have running or whether to have a toggleable box in tablet tweaks (or date/time settings)... I was thinking something like

Sync Time/Date Using Internet ☒

Time will be synced using the Network Time Protocol
[Nook Color Android Development] tj!2k7:
IMHO, a toggle option in date&time settings would be the way to go. :)
[Nook Color Android Development] cybertimber2007:
I've actually wondered for awhile why this isn't in android period (for non-cellular devices which don't have cell towers to get time from)
[Nook Color Android Development] fattire:
The nice thing is ntpd is in CM7 busybox making it easy to add :)
[Nook Color Android Development] chisleu:
I (don't) know what you are saying and I'm still (not) confused.
[Nook Color Android Development] Nburnes:
Anyway I (didn't) do that this morning. It totally (didn't) update time fine. But it didn't obviously stick after a reboot. Went back to the wonky time I set.
[Nook Color Android Development] violinbf:
I have a strange issue when streaming mp4 video from cnet's site. I frequenty get the "this video cannot be played" error and I have to restart the video. It seems to be random, but happens pretty frequently. I am using the stock player. I think this has to do with the dsp because software decoding doesn't crash like this. Any idea as to why this happens? I'm using cm7.0 final.
[Nook Color Android Development] chisleu:
one could make an init script and place it in /system/etc/init.d/ if one were so inclined. I may include this in my personal cm7 addon rom.
[Nook Color Android Development] fattire:
Yeah, I was thinking it would go as a service in init.encore.rc on the ramdisk. Something vaguely like:

service ntpd /system/xbin/ntpd -Np pool.ntp.org
user root

This would keep it as an always-running daemon. If you wanted the ability to turn it on/off, you'd need to start/stop it.

If you do add it to a userinit.sh, let me know how practical it is. Of course I could try it, but I'm realizing it's more fun to get volunteers.
[Nook Color Android Development] chisleu:
I have fruit ninja and no need for ntpd so tours might take a while.
[Nook Color Android Development] k4str0:
I just want to take a moment and thank the devs for the hard work they put into getting custom ROMs running on the Nook Color. Your hard work made me buy this device in the first place. After seeing how well the device ran, I also bought my wife one. We are both now happily running CM7 with Dalingrin's kernel and not looking back. I use the Nook everyday and each time I use the device I'm thankful that you guys put so much hard work into getting this to run.

I use to dev for CM in the past and just don't have the time right now but will most certainly be contributing in the future. Once again, thank you from your loyal users and keep up the great work! Cheers!
[Nook Color Android Development] ADude:
Maybe because there is already an Android App called "ClockSync" to do it ?
[Nook Color Android Development] chisleu:
Seriously. I was marveling at this today. I can't believe how much so few people have accomplished in such a short time. Impressive. Bravo.
[Nook Color Android Development] 911jason:
Agreed... I will definitely be making my future Android device purchases based on what these guys are buying! :D
[Nook Color Android Development] chisleu:
Cyanogen tweeted that the g2x was going to be his next phone! :)
[Nook Color Android Development] tj!2k7:
+1.. first thing I do when someone mentions an Android device I'm not familiar with, is to check if it can run CM. =)
[Nook Color Android Development] chisleu:
Unless something falls out of the sky, I won't be running any portable devices that won't run CM7.
[Nook Color Android Development] a in yul:
picked up a nook, using CM7; thanks again, donate button used; really like the NOOK now that is is on CM..:)
[Nook Color Android Development] chisleu:
Yeah I wish the word would get out, because if people only knew...
[Nook Color Android Development] Tenburn:
Agreed. I'm saddled with a Fascinate right now and probably not going to change anytime soon, but I'll never get another phone that doesn't run Cyanogenmod.
[Nook Color Android Development] fattire:
Even better... get a device that doesn't run CyanogenMod...

...and make CyanogenMod run on it :)
[Nook Color Android Development] chisleu:
Holy crap. I have been struggling to heytapatalk to work for weeks. Flashed cm7 n39 and it is working now! So happy.

Sent from my cm7 nook color
[Nook Color Android Development] ADude:
Is there a list ?
[Nook Color Android Development] chisleu:
http://www.cyanogenmod.com/devices
[Nook Color Android Development] ADude:
Okay, I'm sorry, but that is not allowable. :eek:

The link needs to be something like:

http://www.fbwop.na/230957720bf20t57a
[Nook Color Android Development] fattire:
Try http://kan.gd/abq
[Nook Color Android Development] MДЯCЦSДИT:
Screen on/off anime yet?
[Nook Color Android Development] joenathane:
Man, you are really annoying. Would you stop spamming the threads with that question?
[Nook Color Android Development] chisleu:
But is it working yet? Seriously. This is important.
[Nook Color Android Development] Divine_Madcat:
Indeed. The CRT animation is the only reason people should even consider using Gingerbread...

Without it, we are all truly dust in the wind.
[Nook Color Android Development] joenathane:
I never thought about it that way.... now that you say it, i guess it is important, the most important thing to happen in our lifetime. I wonder how one could find the answer, maybe flash the latest nightly? hmmmm.... That might be just crazy enough to work!!!

Might I add, you sir, are a scholar and a saint for pointing that out.:D
[Nook Color Android Development] chisleu:
Bring it home Kansas.
[Nook Color Android Development] MДЯCЦSДИT:
im getting no lockscreen or animation
[Nook Color Android Development] RoboRay:
Are you sure?
[Nook Color Android Development] MДЯCЦSДИT:
What do you mean are you sure? I had a lockscreen the whole time that ive been using this since the first release. And now I dont have one! :mad:
[Nook Color Android Development] Divine_Madcat:
Go to CM7 settings, and in the Tablet tweaks section, you can turn it back on.

And for the love of all that is good, please stop asking about the stupid CRT animation, it is not working yet...
[Nook Color Android Development] chisleu:
Everyone's got all the time to get useless stuff like video/audio, bluetooth, VPNs, 3d performance, and probably other stuff 1% of people want, but EVERYONE wants the screen off animations. It's like the only reason to use 2.3 android. Get it straight. You guys get paid untold tens of thousands of dollars a year and we expect everything now. Obviously.

Thanks for understanding.

(sorry, I took my pain medicine early. stupid back...)
[Nook Color Android Development] rigy73:
I am having problems with my bluetooth, i can receive files fine but when i try to send files it fails. Anyone knows anything about this?
[Nook Color Android Development] DizzyDen:
The range for outbound BT from the nook sucks badly... as a BT receiver it seems to be much better.... I attribute it to the antenna situation.
[Nook Color Android Development] rigy73:
I am trying to send files by putting the phone on the tablet, how closer can it get?
[Nook Color Android Development] joenathane:
Wrap your nook in duct tape, it will amplify the signal. If it still doesn't work, try first wrapping your nook in tin foil before you wrap it in duct tape.
[Nook Color Android Development] tjsooley:
I tried to view the change log and the twitter page would not load.

What was changed between stable and nightley 39?
[Nook Color Android Development] Nburnes:
cm_encore_full-39.zip

Issue 3418: Show statusbar on ADW swype and fix velocity (android_frameworks_base)RTL bug fixes: (android_frameworks_base)Traditional Chinese: Translate "(un)registration failure" (android_packages_apps_CMUpdateNotify)add offmode charging for htc (android_bootable_recovery)harmony: CHANGELOG - add pershoot as a maintainer for harmony
[Nook Color Android Development] tjsooley:
are there any 1.1 oc voodoo sound kernels based on n39?
[Nook Color Android Development] Divine_Madcat:
The kernels aren't really related to the CM7 versions... but the 4/13a kernel + ALSA sound fix are the best combo for n39..
[Nook Color Android Development] gordon1hd1:
Hi guys, been out of the development loop for the NC for last 2 weeks, RL stuff took most of my time. Just out of curiosity, what is the current issue with the 32 kernel that is causing us to stay with the 29 version?

Also is there any active development to refine the BT functionality? From what i read a while back, the community consensus was that the NC have the hardware antenna to make BT function property, with longer ranges, but the current BT development work just hasn't figure out how to active the antenna yet, has this been changed?

PS: Just finally got around to flash CM7 stable last night, coming from Nightly 30, WOW such progress in such short time.
[Nook Color Android Development] tjsooley:
Thanks you have a link to it?
[Nook Color Android Development] combustiblemonkey:
RTFM

...seriously.
[Nook Color Android Development] ADude:
Look for a thread with [KERNEL] in the title.
[Nook Color Android Development] ADude:
They have not finished getting the 32 kernel to work properly with the NOOKcolor (*) to make it support all the functionality of the 29 kernel.

Both the devs are taking the weekend off, and will resume work on the 32 kernel around Tuesday (probably after finalizing the last changes for the 29 kernel).

Meanwhile B&N will release their 2.2 update any day (hour) now, so there will be B&N's new 2.2 kernel to either modify or use as an example.

( * I just noticed this is the official spelling ;) )
[Nook Color Android Development] skwalas:
Uhhh, are you sure about this? The video threads are dripping with 413a/alsa instability issues.

Or is there a trick to it? sticking our tongues out to the left or something?
[Nook Color Android Development] Divine_Madcat:
Well yes, different kernels are having various issues/gains; i simply meant that pretty much any kernel made in the last month will work with any CM7 version.
[Nook Color Android Development] silentjess:
kept clicking thanks but my browser ain't allowing that!

Big Thanks to CM7 Team. i love the updates, the changes, all the work you've done.

even my xperia x10 is running cyanogenmod.
[Nook Color Android Development] atomclock:
This bug is still in update - 54.

I noticed that update - 54 had some work done to the StaticLayout function so I though I would give it a try and this bug is still there.