yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] jkurl:
I wish I did have more of a detailed Schematic. If there was a way to measure the power of the Bluetooth coming out. I don't have any of that equipment at home but I do at work. I would need to probably open the nook and hook a probe into the jack to measure the power.

You got any ideas how to measure it w/out hooking in the jack on the inside. I am currently looking into what I will need to test this. I am a Electronics Tech in the Military and stationed where our Electronics School is at so we might have the equipment to test it. I am hoping I can get a good read on the signal and see what Dbm the NC is putting out. That will give the devs a better look at where to maybe go w/ this.
[Nook Color Android Development] pokey9000:
We never got much detail from the teardown other than the components inside the wireless module. At this point the most useful tool is probably reading the signal strength out of the module itself against a known BT device at a specific distance. It's not accurate, but it tells us if any changes we might make have an effect.
[Nook Color Android Development] greenleaves:
I have similar issue with N19 now gone back to N18.
[Nook Color Android Development] jkurl:
Ok I used Bluetooth Explorer on my mac to run a test. I am not sure how reliable the test it but it seems to be pretty accurate.

I used the following to test the bluetooth w/ the mac and use 3 different w/ devices and WIFI on.

1. Nook Color

2. Kensington Mouse

3. Jawbone Era Headset

All produced a Tx Power of 3.

Signal Quality

1. Nook Color - 96-100%

2. Kensington Mouse - 84-100% expected from a mouse.

3. Jawbone Era - 100%

Receive Signal Strength Indication (RSSI)

1. Nook Color - mostly around 0 the entire time

2. Kensington Mouse - 0 - (-10)

3. Jawbone Era - Steady -5

Distance Test

1. Nook Color - 15ft (RSSI -15)(Signal Quality 64%)

2. Kensington Mouse - 15+ Feet

3. Jawbone Era - 30+ feet

Tested Nook Color W/ WIFI off on Computer and Nook Color.

Turning Wifi off on both Mac and Nook Color did not improve RSSI or Signal Quality.

I have add links to the test I did so you can see them and tell me what you think.

Nook Color

Kensington Mouse

Jawbone Era

NC Distance Test

NC/MAC W/ WIFI Off.
[Nook Color Android Development] eyecrispy:
Mine seems ok on 19. Same old same old.
[Nook Color Android Development] jkurl:
@pookey9000 where is the bluetooth code located on the Nook Color?
[Nook Color Android Development] KDOG2020:
I am SO tempted to try this again but leary - I just got my Nook up and running after trying to install this last time. Of course I didn't format system/date/cache last time so that could be why it didn't work. I have CWR 3.0.1.0 on it so is that all I need to flash it? I still need someone to explain this EXT3/4 stuff and how it pertains to going from the .68 Froyo I'm on now to the CM7...
[Nook Color Android Development] RoboRay:
CM7 requires the /system, /data and /cache partitions to be reformatted as EXT4. The default EXT3 file system the NC comes with will not work. There are no optional steps in the setup instructions. Skipping those steps will cause the failed installation you encountered before.
[Nook Color Android Development] KDOG2020:
Ok well how do I do that? Or does that happen automatically when done with CWR 3.0.1.0?
[Nook Color Android Development] RoboRay:
Format /system, /data and /cache under the Mounts menu in CWR. DO NOT FORMAT the /boot partition!

Full instructions are here: http://xdaforums.com/showpost.php?p=11452450&postcount=19
[Nook Color Android Development] KDOG2020:
I mean will it do that so its EXT4 file system automatically with 3.0.1.0......

( I also ask cuz those installation instructions state 3.0.0.6....)
[Nook Color Android Development] RoboRay:
I'm not sure, as I used 3.0.0.6 to format, which gives you EXT4 automatically. However, if you are not offered a choice of file systems when you start the format process it is probably safe to assume you are getting EXT4. I'm sure somebody will chime in if this is not the case.
[Nook Color Android Development] pokey9000:
Bluetooth is split between some kernel drivers and the bluez package. The current kernel can be pulled from https://github.com/fat-tire/nook_kernel/ . bluez is part of the Android build.

Part of making the BT work is a binary blob that TI calls an init script. bluez's hciattach loads this blob when you attach the UART to the bluetooth stack. From what I can tell this soft-patches the BT module's internal ROM with bugfixes and tweaks some operational parameters (UART rate, flow control, probably some radio features). TI provides customers with a tool that cooks these scripts, but doesn't provide them (or docs for that matter) to anyone who isn't making big orders.
[Nook Color Android Development] KDOG2020:
Also, this can be flashed direct off the card from CWR correct?
[Nook Color Android Development] jkurl:
Ready to test anytime needed. Hopefully the test I did helped but I doubt it. Will look at the kernel and the blues again.

sent from motorola atrix.
[Nook Color Android Development] aludal:
@pokey9000:

Great explanations! Wish I could read your similar description on present status of making IVA2 (DSP) work
[Nook Color Android Development] HotShotAzn:
I'm pretty sure GB/CM7 will only run on EXT4, so if you have GB/CM7 right now, you have EXT4.

I did not format /system, /data, or /cache before flashing CM7 from FroYo and I did not have any problems.
[Nook Color Android Development] dalingrin:
Don't get excited when you see the DSP commit. As of now the DSP is working but the slow video frame rate is caused by something other than the DSP accel.

The end result is youtube and other videos play as they should but at a slow ~8-10fps. This frame rate is constant regardless of the video used. For example, high quality youtube clips play at the same speed as low quality.

Why do I think the DSP is not the issue?

When I force software codecs which are built into Stagefright and separate from OMX, the frame rate is the same as with DSP accel. At first glance this made me think the DSP codecs were not working and as such, I've stated all along that the DSP is nonfunctional. However, after further testing the software codecs I realized the slow frame rate was not a CPU bottleneck. If I limit the CPU to 300mhz the frame rate is the same as forcing 1.1ghz. This tells me the there is some other bottleneck or issue. I then tested with and without the hardware overlay, same result. So, what I am seeing is, regardless of the hardware overlay, software codec, hardware codec, or video bitrate(within reason) used, the framerate is constant.

Incidentally, the Gingerbread n900 port has the exact same video playback issue as we do. See this youtube clip: http://www.youtube.com/watch?v=KiFQk08xqME

The nook video playback with DSP accel looks exactly like that n900 clip.
[Nook Color Android Development] samuelhalff:
Isn't the 'format sdcard from nook bug' repaired in CM7? Haven't tried CM yet, but someone wrote that it corrupted his boot..

I'm not sure of vold compatibility between 2.2 and 2.3. But one could try pushing cicada's vold (0.6.8) to CM7's system/bin. See if that does the trick..
[Nook Color Android Development] Biff Rosco:
I did not test this kernel yet, but wanted to report that I have no issues getting adb (Windows 7) working or mounting the SD. I am using the CM7 1100mhz kernel from the main kernel thread.

The only thing that I had to do to get adb working was delete the driver for the USB Mass Storage Device for the NC, scan for hardware changes, then add the adb driver to the newly found NC device.
[Nook Color Android Development] shad0wf0x:
is working correctly for me with that kernel.
[Nook Color Android Development] lafester:
confirmed. works great, ty.
[Nook Color Android Development] RoboRay:
It was. The power consumption simply gets shifted to the Phone Idle report when you disable the phone APKs.
[Nook Color Android Development] jkurl:
So does that eat more battery or just the same.
[Nook Color Android Development] RoboRay:
The same. Phone Idle is merely how Android reports power consumed by the device while doing nothing. It's like the gas your car burns while you wait at a traffic light.
[Nook Color Android Development] jkurl:
Ok got it. Nice simpleton explanation. I did think it would use more battery but it could be like when you have no wifi it keeps searching or taking up resources which in turn would drain the battery.
[Nook Color Android Development] bonobomidwest:
First off, I cannot tell you how much I appreciate and admire what you guys have done here. Phenomenal. And this may seem silly, but i just love the boot anim, the wallpaper, and the notification bar tweaks and buttons. Just beautiful ;-)

I don't really know how i can help as i am still far to android naive, but i can at least put the machine through the wringer and let you know what is or is not working... Is there a running list we can add to, or is it just USER thread?
[Nook Color Android Development] bonobomidwest:
*EDIT... not actually a [FIX] but a * ;-) MARKET WORKAROUND

This may be an amateruish workaround, but IT WORKS ;-) And i apologise if someone else has figured this out already. but I'm slap-happy with excitement over this right now ;-)

1. I have used my Froyo install to pick up whatever i need from the market (including purchased apps).

2. Then with titanium backup, backup any apps you want (works for purchased apps, and stock B&N NC apps too)

3. The trick is getting them off the sdcard partition easily. To do so i use samba to copy the /sdcard/titaniumbackup folder over the wireless to my PC.

4. Reboot in CM7. Fire up Samba. Copy from the PC to /sdcard/titaniumbackup (alternatively you can copy direct to an sdcard in step 3, works either way)

5. Then with titanium backup restore each app

I would be cautious and do one at a time for now. I am keeping a running list of working apps over in the USERS thread to cut down clutter here.
[Nook Color Android Development] lafester:
i am a little confused. are you getting these from your phone and transferring over?

if so just take the .apk files from data/app folder off emmc drive.

if not i just installed titanium and ran my backup off the sd card no problem.
[Nook Color Android Development] samuelhalff:
How is that a market fix?
[Nook Color Android Development] jkurl:
Sam I am glad you said. I had a response but deleted it.
[Nook Color Android Development] mrty4short:
samuelhalff I know you made the fix for the signal bars and the no service on the lock screen would you know how to implement that on the cm 7 gingerbread?
[Nook Color Android Development] painter_:
dalingrin, I know that you guys are working on a kernel to correct the SOD, but I thought I would report my experance with the 1.1 kernel you posted for CM7.

I loaded the 1.1 kernel this morning and I have had 1 random reboot with the device just sitting on the table and 2 cases of SOD. Other then configuring Gmail and exchange, loading Flash and Angry Birds the device is stock CM7.

On 2.1 I was able to run the 1.1 Kernel without issues, other then the wireless dropping out.
[Nook Color Android Development] Decad3nce:
No custom compiled kernels currently "sleep" by the regular standards. Seems like B&N didn't update their source release along with their kernel/ROM blob release.

We've tried multiple different toolchains, still no go.
[Nook Color Android Development] LeathaLurker:
I was under the impression the nook didn't sleep even in stock
[Nook Color Android Development] jkurl:
I haven't had any SODs yet or any random reboots.
[Nook Color Android Development] samuelhalff:
Once we have a stable build, I'll probably get my hands dirty. Until then, it's a waist of time to get these "detail" fixes pushed to your NC..
[Nook Color Android Development] dang025:
new nightly has recently been released http://download.cyanogenmod.com/?type=nightly&device=encore.

Will this build have a complete market fix?
[Nook Color Android Development] Jewremy:
Hey guys. Is there any way to remove the cell features? For example cell standby, etc. In NF it was just removing the related apks, but when I tried in cm7, everything started forceclosing on me.
[Nook Color Android Development] dalamchops:
thanks, great to finally hear some update on the DSP. I've been using v17 since it came out, and have not had any market issue whatsoever (my apps has shown up every single time i go into market) without messing with default lcd density.
[Nook Color Android Development] bratliff:
Tried 160 but lost my apps. Updated market cm nightly 17. Thanks for all the work.
[Nook Color Android Development] dalingrin:
Updated build posted with fixes that won't make it into tonight's nightly.

Can you check which version of the market you have installed? You can see the version in Settings->Applications->Manage Applications->All->Market
[Nook Color Android Development] aludal:
Thank you dalingrin, for your quite informative answer.

This is so strange... On stock Eclair, I had butter-smooth "HQ" YouTube playing this January, swear to all Android gods. All the next developments (Froyo, HC, CM7) just wiped this "software" (non-hardware Stagefright) option completely.

Very puzzling, indeed! As far as I can remember from my searches of IVA2/DaVinci architecture, for video it supplies couple of hardwired codecs, plus hardware overlay. Hardware codecs are limited by mostly bandwidth (if we talk about H.264, wmv9 and such), whereas hardware overlay (renderer) is meant for fixed resolutions (for our device, 1024x600 and strictly 169.3333 dpi, no dithering scaling after that -- or it's software-only). In this context, I don't understand all these strange figures of 160...161 dpi, etc., in CM7 builds

I wonder then how far they moved from their "native" density, to achieve this?

I wonder whether any of recent related OMAP code (stagefrightHW, rendererHW, etc.) was taken into consideration, or even tried. Sure, it was meant for compiling against 2.6.32...36, but anyway.

I'm running CM7 v17 with the latest Market and @169.3333. My Apps are there, work fine. Market itself is very sluggish, and I can't get my location, but it's most probably I adb-installed just half of what was there in the new Gapps package. In any case, that v17 was sort of a proof of a concept to me -- just to try BT and to see some weird artefacts of wrong density or whatever, heh. But I'll leave to my blog, as all my searches of VOME engine in AOSP 2.3.

Thank you again, and hope you'll share more of your grievances and discoveries in achieving a perfect CM7 for NC.
[Nook Color Android Development] dalingrin:
Note that lcd_density is an integer value only. Additionally, when using mdpi, 160 is the default lcd density. Any other lcd density with mdpi involves interpolation. If you compare 160 and 169.x you can see that the images used for icons are significantly more blurry at 169.

The reason I chose 161 instead of 160 was to workaround a Market bug that caused the my apps list to fail to load. In my limited testing it seems Market 2.3.4 may have fixed the issue. If so, I plan to switch back to 160 which has the best image quality and best app compatiblity with the exception of Google Maps. However, 160 will need more testing with the latest Market to make sure the "my apps" list is completely fixed.
[Nook Color Android Development] hootyburra:
I would be happy to test this if someone can send me in the right direction. I am still quite a rookie. I am running the 19 nightly now but can update to test the LCD density. I just need some info on what to do.
[Nook Color Android Development] aludal:
Sure I know that there was such a "convention" in Android 2.x about mdpi, hdpi, 160, 240, etc. I just don't like them as kernel/graphic drivers/whatever building parameter.

As for integer, or with decimals value, there would be no problem if there would be assurance in FPU working. Yet, if it declared integer somewhere already, I wouldn't mind if it could be 170 then. Again, I couldn't care less what they do with ever upgrading Market apps, I'm much more concerned by malfunctioning DSP. In other words, I would love to try CM7 build of 2.6.3x with 170 dpi.

I just checked again, nothing is blurry in my icons at 169.3333. When talking about integer figures of 168, 169, 170, 171, and possibly 172 in my blog as the best for NC, I mostly meant the best font rendering at a given autohint level, with no FPU. Though I won't be surprized if the figure of 169 or 170 would turn magical in a sense that DSP/videos will start to work as expected.
[Nook Color Android Development] bonobomidwest:
Too late dude.

BTW, what's with the removal of adhoc wifi you mentioned in the changelog for the test build? Or have I misunderstood (again)

Wilco...

... Reflashed the latest GAPPS from CM...

... Market and maps work (still at 161) ...

... Set to 160 ...

... Rebooting ...

... Rebooting ...

... :) ...

... Good Morning! and...

... Market works great (including my apps), but Maps is DOA as usual...

I'm not sure about other folks but i care much more about maps working than having exactly the right density... so my vote would be to leave it for what it's worth...

... thanks as always dude.
[Nook Color Android Development] dalingrin:
the lcd_density doesn't affect videos or the DSP.

The problem with densities greater than 160 is the interpolation that must happen. I just checked for good measure and the icons are definitely not as sharp. Additionally, you will see artifacts from the interpolation such as gradients on the Gingerbread keyboard and the notification drop down.

In my testing I saw no difference in font rendering.

Keep in mind that another motivation for moving to 160 is that afaik, all apps scale properly to full screen. Any deviation from the mdpi standard 160 causes some apps not to scale to full screen. An example is Google Reader. If you click on an article to read, it will give you a libwebcoreview but it does not scale to full screen at >160.

Rest assured, video playback and scaling is done with absolute resolution, so the lcd density value does not affect it. The video is decoded then pushed to the overlay(GPU).
[Nook Color Android Development] barrist:
video still not working, tried the test build. i also flashed the oc kernel, could that be why?

new rotary lockscreen looks right now though
[Nook Color Android Development] tgallant21:
changed to 160, rebooted and now nothing in my apps....

changed back to 161 rebooted and now I have my apps again

market v2.3.4
[Nook Color Android Development] :
A few observations:

The CM7 dude during boot has an arrow that spins nicely (not stuttering) now (running OC w/1.0 GHz on boot).

Everything is more responsive/smoother.

Market works (My Apps, everything) at 160.

Let me know if you need anything else tested.
[Nook Color Android Development] runhopskipjump:
I had the same expirence. I flashed the cm7 3/15/11, updated gapps and the 3/13/11 kernel. After setting density to 160 and rebooting, my apps no longer appears. Could it be te kernel?

Nooking with Encore
[Nook Color Android Development] actorman46:
It it's so snappy, even if video isn't working yet.
[Nook Color Android Development] dalingrin:
Yessir that is why. I forgot that I didn't push my 2.6.32 DSP driver backport to the overclock kernel. I have it built and am uploading now.

Ah okay. That confirms that 2.3.4 did not fix it. Thanks.

Because of some changes in Gingerbread 2.3.3 our system was using a different pixel format. I recently disabled that pixel format because its not properly supported in our GPU driver. Should make things a little quicker(compositing was broken before the fix).
[Nook Color Android Development] tgallant21:
hey quadrant works...
[Nook Color Android Development] racks11479:
Test build 3/15

Video works, a bit choppy as you stated. But a good start! :)

Much more responsive

Changed LCD density to 160 no "My Apps", Maps FC

I just use Maps 5.0 and it works for me at 160 till a fix

Changed back to 161 my apps shows

Love the rotary lock

I'd prefer to stay at 160 as the icons are much sharper and clearer, less blurry.

Thank you guys for all your. Hard work!!!

Edit: Just flashed your updated 3/16 1.1 OC and it is crazy responsive. Wow.
[Nook Color Android Development] aludal:
I've got it. That is, I think I've got it, as it doesn't explain why I don't observe blur/fuzziness of icons, or gradients/stripes in my keyboard at my 169.3333.

Sure I hope GPU's shaders (as hardware renderers) operate at absolute/physical resolution parameters which are around 169.4 and don't take that stupid 160 (or 161) value into account. Yet something that most probably wasn't present at Eclair seeps through, starts interpolation, and the whole video processing falls back to software. Your CPU at 300 MHz giving you the same lousy fps may mean there's not much work for software decoding in the first place, but software overlays are much harder to issue in time.

I wonder whether some relevant code could be borrowed from AOSP 3.0.1 and or OMAP3/4 git for A 2.3. Sure, the best way to solve that enigma would be a direct kidnapping of that TI engineer who is responsible for the whole video system.
[Nook Color Android Development] :
NVM, Market is messed up with new OC kernel at 160.
[Nook Color Android Development] :
Quadrant!

Just to say I did it...

Quadrant Standard Score running newest everything:

1223 (@ 1.1GHz) :P
[Nook Color Android Development] :
Interesting...

As darlington said, it doesn't matter the quality on the youtube app, it seems to be about the same framerate. The clock speed of the processor also does not seem to affect the fps.
[Nook Color Android Development] pavlos46:
Ok I am just thinking here,

Could the problem be sound, that the system is trying to sync sound and is continually recalibrating as something is amiss.

Pavlos
[Nook Color Android Development] barrist:
Thanks! working now, although like you said framerate is pretty bad. youtube through the browser same as before. watchable in 360p choppy anywhere above.

great start though, i have no doubt that it'll be improved soon!
[Nook Color Android Development] RoboRay:
That leaves me wondering why it's set to 169.33333 by default in the stock Eclair system that ships on the NC. :confused:
[Nook Color Android Development] newellj79:
My video not working. V21 and 3/16 kenrel. Anythoughts?
[Nook Color Android Development] barrist:
Don't think it's in the latest nightly. have to use dalringin's test build
[Nook Color Android Development] newellj79:
Duh....thanx man. I missed it..
[Nook Color Android Development] Canadoc:
If I don't want to lose adhoc but want to try the DSP firmware how can I save adhoc? Would need it for tethering

From 1.1 Nook Color with 1.1 ghz overclock
[Nook Color Android Development] soup006:
Quadrant still crashes for me even after updating to 21 and 3/16 oc kernel.
[Nook Color Android Development] barrist:
you need to use the test build

i got a similar score, definitely looks like the 2d/3d is capped to 15fps
[Nook Color Android Development] newellj79:
Use the test build at the beginning of this thread.
[Nook Color Android Development] Canadoc:
Tried the test build and bootlooped

From 1.1 Nook Color with 1.1 ghz overclock
[Nook Color Android Development] KDOG2020:
WELL THATS JUST GREAT. I jut got it on and it managed to get all the way into it ONE time. Then I installed googelapps after word and now it gets all the way into the first android guy on the skateboard then a little bit into the other android guy for something (I believe the market) and then restarts over and over, a loop. What now?
[Nook Color Android Development] chisleu:
So flash the test build and then the kernel?

Do we need to format any of the partitions? (I'm coming from the CM7 "16" BT-enabled build.)

Do I just use the "backup&restore -> backup" to backup the device before I install those zips?

First time updating after CM7 install. Loving CM7.