yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mazook98:
After testing and benchmarking the Video Test Build for a while yesterday to figure out the best oc /governor settings, (consistent 14-15 linpacks, and 18 nenamark scores) I'm wondering if I should expect to see any improvement with RC4, or will they be about the same (wondering if its worth my time to flash yet, or wait for a few more days)...Anyone sure?
[Nook Color Android Development] dalamchops:
will it be possible to add more codecs to the nook?? Asphalt 5 still say video cannot be played in the intro.
[Nook Color Android Development] Divine_Madcat:
I can't see any reason not to flash....You get the newer SGX SDK, which may help things a little bit. And there are other small fixes. So yeah, if you have 5 min free, i would give it a shot.
[Nook Color Android Development] buffalosolja42:
2 day observation

build ran really good for me despite not being able to connect to wireless networks for some reason, but it was good all the way around besides that keep it up!
[Nook Color Android Development] animatechnica:
same here - got working adhoc even with the 32 nightly
[Nook Color Android Development] dj_L:
Exchange 2010 issue...maybe a fix.

SP1? What is likely happening is that you don't have security setup on the device (passcode for lock screen), and NC is receiving an HTTP 404 during setup (which is never shown to the end user). Nix the mobile profile, setup the account, and then put the profile back (or just give yourself a very permissive mobile profile before hand) and see if that fixes it for you. If not, post back and I'll setup 2010 in a VM and let you know what I find.
[Nook Color Android Development] firehazard:
You didn't describe your symptoms all that well, so I'm making assumptions here.

If you're able to add the account but it doesn't pull up the Exchange policies or email, that likely means you have too many devices added to your Exchange account. Log into your OWA client and go to:

options -> see all options -> phones

From there, delete some of the devices which haven't synced for a while. The next time you add the account to your Nook, it should work.
[Nook Color Android Development] paleh0rse:
Swoops, wrong thread! Ignore me... ;)
[Nook Color Android Development] phfaty:
Does airplane mode work? Whenever I check the box for airplane mode and cancel out of the wifi settings screen, I come back to the wifi settings screen and see that the Airplane mode has been unchecked automatically.

I am on CM7 #32.
[Nook Color Android Development] dalingrin:
I haven't messed with it to be honest. Why would you want to use it?
[Nook Color Android Development] philburkhardt:
There is an issue with airplane mode. Once you turn it on, the nook always thinks it's on. I was having an issue with my wifi not starting up when my nook booted, when I was sure it was on when I shut it off. Turns out it was because I accidentally hit airplane mode once. If you turn airplane mode on, and then turn it off, reboot and look at your settings.db file. It still says airplane mode is on. To fix this, you either have to edit the settings.db file or reflash the ROM.

This might have been more information than what you were looking for. But, in a nutshell, that is the issue with airplane mode.
[Nook Color Android Development] RoboRay:
I've noticed that the Automatic Backlight settings are missing from the CM Display menu, and for good reason since there is no light sensor on the NC. However, this is preventing me from testing something...

Many apps will not set the brightness below a certain point, which appears to be approximately the value of 20, or the standard "Dim" level in auto-brightness. Even some apps that let you enter a numerical value directly still won't go below that point while others, like AdjBrightness will. I would like to reduce the "Dim" value and see if that allows those apps to set brightness to lower levels.

Can anyone tell me where the "Dim" value is stored so I can manually change it?
[Nook Color Android Development] :
long press home doesn't show up full screen...and fixes?
[Nook Color Android Development] mjb413:
So I just flashed cm7 latest nightly on my nc. It was my first non-stock rom on this device. After flash, I will occasionally get areas of the screen that "stick" such as the right corner or bottom. It will work fine for a bit, then appear to think that my finger is left in one spot. Turning the screen off and back on fixes it temporarily. Also, does slingplayer work? I saw that there were some video playback issues, but also found posts with people having working slingplayer. I do have hulu working so, there is some video playback. Thanks.
[Nook Color Android Development] chisleu:
Why are LWP's removed again? They seem to work fine when I put in the LWP/picker apps. Just wondering if I shouldn't be doing that.
[Nook Color Android Development] timoskrempel:
I played around with it in my app Recent Plus and it is dangerous to set it to a lower value. Basically the backlight turns completely off and you can no longer see anything. :-)

You can set it in a java program with:

android.provider.Settings.System.putInt(getContentResolver(), android.provider.Settings.System.SCREEN_BRIGHTNESS, newvalue);
[Nook Color Android Development] sinanju:
As of today, the best all 'round results of video and audio playback for me are dalingrin's 3/16 kernel with the #34 build.

After a quiet Sunday listening to MP3s and reading with the Kindle reader, the only clicks and pops I got were when stopping MP3 playback, causing the audio device to be released. Having WiFi active seems to create split-second audio pauses/dropouts as more processes are active when the connection is first established -- having the overclock set to 1000 MHz and the governor on Interactive doesn't seem to get rid of that.

Pandora is most problematic as it requires both an active WiFi connection, leading to the audio dropouts until things settle down, and that it appears to close and reopen the audio device between each track, resulting in clicks and pops with each close.

I'm just getting started with Android, so I don't have the chops to chase down the audio issue, though I'm happy to help whomever can however I can.
[Nook Color Android Development] ADude:
Did you ever check those particular issues while using "Madcat's Kernel" and/or Stock Kernel ?
[Nook Color Android Development] sinanju:
Haven't tried the stock kernel, though the clicking problem is there with Madcat's kernel as well. It seems to be directly related to the introduction of HW video support. I don't think it's kernel related, though the more recent kernels seem to exacerbate it a bit -- that's a qualitative assessment I wouldn't bet on. I've tried builds from 28-34 and the problem seem to be after 32 with a DSP-enabled kernel.

That said, I thought the newer kernels were required for HW video... I was surprised to get smooth playback on my test video when I went to build 34 using the 3/16 kernel, but looking at the change log, it appears DSP was introduced on 3/16... I thought it was later.
[Nook Color Android Development] ADude:
HW acceleration works with the stock kernel.
[Nook Color Android Development] KitF:
Try Dalingrin's latest kernel (3/31/11)
[Nook Color Android Development] dalingrin:
Audio issues are almost certainly related to the small buffer size in Alsa required for smooth video playback. It shouldn't be kernel related. I'll look at tweaking the buffer some more.
[Nook Color Android Development] lafester:
you've been quiet lately. hopefully taking a well deserved break :)
[Nook Color Android Development] dalingrin:
Nah, just trying to help Verygreen with a new 2.6.32 Nook kernel.
[Nook Color Android Development] RoboRay:
Yeah, you do need to be careful to not set a value below the "can't see anything!" threshold unless you know how to get the screen back. :)

My past experimentation with AdjBrightness found the NC's lowest usable value to be 4. Unfortunately, most apps won't set a value below 20, which is also the standard value for the "Dim" level. I would like to see if correlation equals causation in this case, or if it's just a coincidence.

I had hoped that the value of the Dim level was stored in a configuration file, like so many other settings are, so that I could easily play around with it and see if it is what's limiting the lower range of some backlight control apps.

And, silly I, just realized that I can even more easily do that testing on my CM7 DInc. Sometimes I'm really slow...
[Nook Color Android Development] sinanju:
I did. I've tried the all but stock. This the best combo so far.
[Nook Color Android Development] sinanju:
Glad to hear you have a line on it. One thing I'll point out though, that might not fit... The popping only seems to happen on a device close... no more need for the buffer. If I had to guess, I'd say garbage was being played after the close. Consistent garbage at that as the pattern of pops is complex and repeatable in a variety of contexts.

I appreciate your efforts...
[Nook Color Android Development] cuoreesitante:
After updating to a newer nightly is the kernel supposed to be reset to stock?

I have the OC'ed kernel on nightly #33, but after updating to #34 the OC options are no longer there. In fact I tried to re-flash the OC'ed kernel and it was not working (says flashed but can't OC in CM7).
[Nook Color Android Development] 360Razir:
I am not using the traditional CM7 nightlies, per say, but using the Tablet Tweaks (TT) version instead, but that is getting updated nightly as well and is consistent with the main pipe of CM7, so we are most likely in the right church, if not the wrong pew.

Anyway, when I put on a new CM7 TT, the kernel gets overwritten, so right after the new nightly finishes installing, I just go and flash the latest kernel from dalingrin. I just got done doing this very thing about 10 minutes ago and I have no problems with getting my NC to show 1100Mhz in the Performance/CPU Settings area.
[Nook Color Android Development] cuoreesitante:
Ok thanks. Just wanted to make sure if it was normal. I guess I should get the newest kernel everytime I update.
[Nook Color Android Development] rogerdugans:
The overclock kernel hasn't been getting updated as often as nightlies or Tablet Tweaks, but I usually check there every day or two anyway.

Just in case he's added more Magic to it. ;)

The answer is definitely "yes" however- new nightly is a new rom with a new kernel so back to the stock CM7 oc of 925. Flash the oc on top each time to keep going up to 1100mhz.
[Nook Color Android Development] bonobomidwest:
More info. In my case local sdcard playback is flawless (I use winamp because most of my music is WMA). However when streaming tracks end in a complex pattern of pops and clicks. In the case of streaming from my media server using 2player, each track in the playlist ends with two pops and a series of very quiet clicks, and then freezes. The player says it is still playing the stream but is also at the end of the track. Hitting ffwd correctly starts the next track. So it seems like audio streams are not communicating that a track has ended properly. This would fit with your Pandora experiences.... dalingrin is this helpful? Does it make sense?
[Nook Color Android Development] chisleu:
Just installed the new nightly with the tablet tweaks merged.

The problem of the market not showing live wallpapers is back.

I have installed LWP but certain live wallpapers such as jumpgate and silhouette are not available as they are in dalingrin's builds and the tablet tweaks builds.
[Nook Color Android Development] fattire:
build 37 didn't include LWs. I think that should be fixed tomorrow.
[Nook Color Android Development] chisleu:
Cool. Understand that I installed LWP and could see some LWP's in the market, but certain ones don't show up. Looking forward to LWP coming back. I don't use them except to show off.
[Nook Color Android Development] dalingrin:
LWP will be fixed in the next nightly.

In terms of the audio pops/clicks. I've confirmed that the pops go away with a sufficiently large buffer. Unfortunately, anything above 4k causes video frame rate to suffer with the DSP. The large audio buffer with the DSP seems to be a known problem with other devices as well. I'm hoping to dive into audio and McBSP this weekend so we'll see what I can find. Audio/McBSP is also what is holding back the 2.6.32 kernel right now.
[Nook Color Android Development] lafester:
what would we do without you :)

hard to believe you are this close to having the new kernel ready.

excellent work as always!
[Nook Color Android Development] chisleu:
Is 2.6.32 the kernel that fixes SoD that has caused so much ruckus?

Good luck! I'm still reading :(
[Nook Color Android Development] violinbf:
I have nightly 37 installed with the 4-04 overclocking kernel. I did a full wipe before installing this nightly.

For some reason, my nook's N button doesn't work as "home" i am not sure why. Is there a way to remap this? I dug around in the settings and cant find it. Obviously there is always the software home in tablet tweaks, but I am used to using the N button.

Is this a bug or is there a way to fix this?
[Nook Color Android Development] chisleu:
It does by default. There is a configuration setting to change it, but for the life of me I can't find it right now.
[Nook Color Android Development] bonobomidwest:
As per usual, you rock :)

having got a reliable way of inducing the problem if I want to :), I'm happy to test anything you come up with.
[Nook Color Android Development] Divine_Madcat:
Dal - since you have been really cranking on the new kernel, perhaps this is a good time to ask. I have been racking through the code, because i am sometimes confused about our 3D performance numbers; do we know exactly what clock speed our GPU's are running at? I know we are running at a higher resolution than other comparable devices, but it still feels like the GPU could be doing better.

AS i mentioned, i looked in the code, but the GPU portion seemed a bit more difficult for a non kernel versed user to figure out... ;)
[Nook Color Android Development] dalingrin:
What makes you think the GPU should be performing better? The benchmarks I've run place it where it should be. The clock should be 200mhz but I haven't looked at it in a while. It set in the bootloader. We can't overclock it until we raise the base dpll clock.
[Nook Color Android Development] Divine_Madcat:
The only thing that seemed off was the number of triangles (among other benches) compared to the same GPU in the Droid X.

http://www.glbenchmark.com/compare....Barnes & Noble Nook color&D2=Motorola Droid X

Again, i don't mind being wrong; or at least more educated. And if the GPU is at a full 200Mhz, that is good for me. As for overclocking it, i have read some comments that aren't too optimistic, though if you think there is a way to do it, i am alllll for it.. Anyway, sorry to pester you. :)
[Nook Color Android Development] fattire:
Until tonight's nightly you can just do this from adb shell:
[Nook Color Android Development] mrty4short:
I synced and built with the prebuilt kernel and market fix found here http://review.cyanogenmod.com/#change,3244 all paid apps can be downloaded but wont show up in the my apps section in the market. It just says no downloads from android market is there a fix for this everything else seems to be working.
[Nook Color Android Development] dalingrin:
Internal storage won't be fixed in tonights nightly. Still working on it. Vold doesn't like more than 4 extended partitions so I'm looking for a workaround.
[Nook Color Android Development] timekeeper:
Thanks for the info. It's no biggie, I don't need the space and don't have enough apps to require that space anyways.
[Nook Color Android Development] Canadoc:
Any way we can get a thread devoted to nightlies to update us as to what changes are being made.
[Nook Color Android Development] cosine83:
Having issues connecting to wireless networks secured with WEP or WPA. It's happening at the stage trying to get an IP. It will hang then the wifi cycles off and on. I'm also using the 1100mhz kernel.
[Nook Color Android Development] fattire:
a corrupted wpa_supplicant.conf maybe?

You could try

(or move it somewhere as this will remove all your wifi network settings)

or even rm/mv the whole directory (I believe it's recreated automatically)...

Dunno if it'll fix the problem, but might be worth a shot. If you don't feel like rming it, you can also just check it out and see if it looks correct. Anyway, that's a place to start checking.
[Nook Color Android Development] fattire:
Keep an eye on gerrit for proposed edits. Also, you can subscribe via twitter to CM Source to see what's getting checked in to Cyanogenmod source in real-time.
[Nook Color Android Development] foxdl99:
As a rule, they don't do changelogs due to the other avenues previously mentioned (github, cmsrc via twitter, etc.). Those are the best ways to see what changes are taking place, you'll just get yelled at if you keep asking about them. Another approach is just to look through the appropriate forums.
[Nook Color Android Development] Canadoc:
are the info on twitter specific to the NC or all CM work?
[Nook Color Android Development] timekeeper:
All CM builds, mostly.
[Nook Color Android Development] fattire:
Quick note (I posted in general disc too). This won't make it into the nightly this evening, but the following change to /system/build.prop may be interesting if you are using the market:

build.prop:ro.build.description=passion-user 2.2.1 FRG83D 75603 release-keys

build.prop:ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83D/75603:user/release-keys​

(thanks nemith)
[Nook Color Android Development] cosine83:
Tried deleting just wpa_supplicant.conf, issue still present. Removed directory, wifi no longer worked (error when turning on). Reflashed (for the stock kernel and wifi config), same issue. I have three other devices connected to this network (phone [HTC Evo Shift 4G], PSP, and laptop) with no issues. Any ideas?
[Nook Color Android Development] fattire:
Is there something "weird" about the network? is it 802.11n or g? Does it appear but just not connect?

Do you see anything in adb logcat that could suggest the problem?

Some perhaps-helpful info:

The program "wpa_supplicant" is the program that actually is doing the wifi connection. "wpa_cli" is a command-line application to interface with that program that may help you debug the issue.

So type:

$ adb shell
# wpa_cli

You can see all the neat stuff wpa_cli can do from by typing "help". You get commands that do everything from scanning for a network (type "scan" and then "scan_results") to trying to connect to one, etc.

Using wpa_cli, you can also change the log-level that shows up in "adb logcat" with "log_level #" (where # is the level you want to see in logcat.) You can get really detailed information about why things might not be connecting, where your system is having trouble, etc.

As you may have guessed, wpa_supplicant.conf referred to above is the configuration for the wpa_supplicant program.

Good luck!
[Nook Color Android Development] cosine83:
It's an N network configured with WEP. I think specifically WEP due to incompatibility with the Nintendo DS WiFi Connection typically is WEP-only (except newer games and DSes). As soon as my NC is charged I'll get to the logs. My laptop isn't currently setup with adb or anything and I won't really have much time for this stuff except late at night. Woo road trips.
[Nook Color Android Development] jkurl:
Is this fix just to get market working or will if fix the problem w/ not being able to download paid apps?
[Nook Color Android Development] likearaptor:
New nightly posted: http://mirror.teamdouche.net/get/cm_encore_full-3.zip
[Nook Color Android Development] Clienterror:
Thanks! 9mb bigger than last nights. Ill take that as there are some big changes.

Sent from my Nook Color.
[Nook Color Android Development] likearaptor:
It looks like the kernel is bigger in this new one. I am flashing it now to see what is working. I might not be able to post tonight what I see different though, my wife wants me to head to bed
[Nook Color Android Development] antony617:
Yes I've test it before.

On stock 1.0.1/1.1 rooted, it can be installed and ran, but as the IMEI refreshes each time, I have to activate the app every time I opened it.

On NF, It can be installed but didn't allowed me to start, saying "device is not supported".
[Nook Color Android Development] dalingrin:
I think its about where its supposed to be in comparison with the Droid X. The SGX 530 was bottle necked at small screen resolutions. Then on the Nook we have 60% more pixels and we have slower memory. A double whammy.
[Nook Color Android Development] Divine_Madcat:
Fair enough. The screen res doesn't help, but the memory being slower certainly doesn't help. Ah, so little time, so much to overclock. ;)
[Nook Color Android Development] starkruzr:
There is also less RAM allocated to the GPU in the kernel on the NC than there is on the DX.

Drop into a terminal and do a "free" on both systems. The NC will report about 400ish MB available total, the DX will report 300-something.
[Nook Color Android Development] Divine_Madcat:
Oy.. of all things, our nook could use a larger frame buffer. I wonder how easy that would be to fix.....
[Nook Color Android Development] samuelhalff:
Regarding the CM7 screenshot problem (blank/black screenshots only).

I'm absolutely not a kernel dev, but could this be of any use?

http://elinux.org/Android_on_OMAP#.2Fdev.2Ffb0

Or maybe the issue has been fixed in the upcoming kernel. If that's the case, just ignore this post.

Thanks.

Sam
[Nook Color Android Development] fattire:
To answer your first question, the same issue currently appears in .32.

I've found a discussion of what may be the problem here. Namely, too much video ram may be assigned, so that the screenshot that's being taken is of the wrong framebuffer, one that's totally unused when SGX kicks in. So lets see... if I understand what they're talking about:

1024 * 600 = 614400

* 2

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

1228800 bytes for one buffer

*2 buffers

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

2457600

That's less than 2.5 M that we need.

Look at /proc/cmdline -- I think omapfb.vram=0:8M means 8MB is being assigned.

As an experiment, I changed the following file in u-boot.bin's source. Thanks to BN for generously providing us with the code.

In u-boot/include/configs/omap3621_evt1a.h, line 252

from:

"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" \

to:

"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" \

Popped in the new u-boot.bin, and rebooted. Here is the result from ddms:

This can probably be done in-kernel so no changes to uboot will be necessary.

I have not investigated how this may or may not affect anything else involving video. This is just a quick experiment. I invite others to test.

Welcome to the world of screenshots.
[Nook Color Android Development] fattire:
BTW-- for clarity, the 'ddms" I refer to above is the Dalvik Debug Monitor Service, which is part of the Android SDK. It's a java app you can use on your computer for grabbing screenshots from your device over USB as well as being an easily-filterable alternative to logcat.

It's in the /tools directory, kinda where adb used to be.

I dont' wanna go crazy with these, but here's another just to demonstrate moving images as well as the tablet tweaks in full-screen:

I'm guessing DSP video won't work as the overlay data will not be in the regular framebuffer... so you'd probably get a black square or something.

But I could be wrong.
[Nook Color Android Development] chisleu:
neeto. I want screenshots in eclipse. :D
[Nook Color Android Development] lafester:
excellent work fattire!