yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] swaaye:
Reducing color depth causes banding in some cases because there aren't enough possible colors available. Gradients will look blocky in particular.

16bit color uses much less memory bandwidth because there is less data to transfer, which is why it's faster.
[Nook Color Android Development] ianPhillips1:
It's related to the dsp issue a few posts up. No sound no video past 221

Ian

sent from my ereader
[Nook Color Android Development] jblues1969:
Touchscreen issues with CM7.1

I just upgraded to CM 7.1 Stable. The first day, I am having issues with phantom touches on the touchscreen causing all sorts of havoc. Rebooting stops it for awhile but it always seems to return after being asleep for awhile.

Anyone seen this before? I didn't get any hits when I searched the forum.
[Nook Color Android Development] bonobomidwest:
Well I am sending this via stock cm7 adhoc on an HTC hero using wireless tether (wep ... it's all my poor hero can do). I love that wireless tether bounces mac addresses it doesn't know... never hurts to beef up security... :) so far every device that has tried to steal my adhoc has been an iFad... what a joy to bounce them from my android oasis :)

Gloating aside, in wireless tether why don't you make sure all security is off and once you have the connection working then add in the security options. I've seen a lot of threads reporting device specific issues with the phone properly supporting security options as an adhoc... remember eclair devices like yours and mine are not meant to be adhoc sources. The wireless tether website goes into a little detail on this.
[Nook Color Android Development] bonobomidwest:
90% of the time is great. I think the audio lag is reduced too. But definitely have some stutter at times... actually seems to be particular videos btw
[Nook Color Android Development] donballz:
Tried that but didn't change anything noticeable. Like I said, it worked in 8. Guess I'll just nandroid back.
[Nook Color Android Development] bonobomidwest:
Just checking... I use root explorer... and then reboot... sorry if pointing out the obvious :)
[Nook Color Android Development] Narfx:
Stock is 160. For me and many others some Apps stop showing fullscreen at any resolution other than that. That includes 169.33333, of course. I still can't believe that it works for you or other people.
[Nook Color Android Development] dalingrin:
Afaik, lcddensity is an integer value; 169.33333 is being truncated to 160.

For now, the default value will be 161. This allows Maps and the market apps list to work but causes a few apps not to scale full screen. IMO, a functioning my apps list takes priority until we can find a way to fix both issues.
[Nook Color Android Development] woot1524:
I'm seeing all of this hub-bub about lcd-density, and I'm wondering why I didn't run into any problems. I've got mine set to 210 (I like the larger screen items) via the build.prop edit. I have always used this lcd-density setting in Froyo, so I figured I'd see how it flys on cm7. BTW I'm running the phiremod nook V4 2nd ed rom. I've had zero problems with apps, well one caveat, Crystal Defenders does not scale all the way out (it never did, no matter what rom). But other than that, the market, maps, apps, and games worked like a charm from the get-go.

Are there any apps that will only run on the 169.33333 lcd-density. I'm curious to test the 210 setting out.
[Nook Color Android Development] simon.ponder:
As far as apps not scaling, go into spare parts, uncheck Compatibility Mode.
[Nook Color Android Development] simon.ponder:
If I flash 12 over 11, everything seems to work except the market remembering my apps. If I do a complete wipe through mounts and storage in CWM, and flash 12 I get all kinds of Wifi issues, not being able to discover new networks or recognizing a typed in SSID. Anyone else?

I wanted to do a fresh install because I thought from 11 to 12, our OS went from 2.3.2 to 2.3.3.
[Nook Color Android Development] Narfx:
Done that, google reader still doesn't scale with dpi > 160.
[Nook Color Android Development] jd95:
where do I find market app at? and do I install flash from there
[Nook Color Android Development] tominabox1:
Same here. Did fix some other apps though
[Nook Color Android Development] RoboRay:
Ultra Keyboard also fails to scale full screen at anything other than 160 in CM7. Interestingly, it failed to scale at 200 or less in stock 1.1 with AN3.0... 201+ made it work fine there, but anything above or below 160 breaks it in CM7.
[Nook Color Android Development] subcypher:
You have to load the latest Google Apps from here. You'll want the CM7 Universal link at the top. Flash CM7, then flash GApps, then boot.
[Nook Color Android Development] diomark:
I'm having problems with the Amazon kindle app.

Normally, it's fine - but occasionally, it logs me out. Coincidentally, wifi is always on the fritz when that happens.

It logs me out while wifi is doing the disconnected/connected dance. and upon wifi working again forced me to log in. This re-registers the device as a new device, and it then forces me to remove my downloads/redownload them from archives.

In the amazon kindle management page, I can see "Mark's android 2" "mark's android 3", etc. (caught on to this as it was complaining that I had too many device registered..)

Anyone else see this behavior? Wanted to point out that it's only happened ~5 times while reading a 500page book.. and always, at the same time as wifi was acting up..

-mark

ps - I normally use the nook app - but still have some books in kindle that I was reading..
[Nook Color Android Development] Paul22000:
Anyone else having an issue with Wifi turning itself off immediately?

I click to turn Wifi on, and while it's turning on, it turns off. Then it just cycles between "Turning on..." and "Turning off..." repeatedly and forever.

Though I've learned that if I toggle Airplane mode on or off it stops the wifi from auto-cycling. After a few times of this, the Wifi then connects and acts like normal.

This happens every time I have to turn the wifi on.

Anyone else experience this?

I'm on v8 I believe. I'll update to v12 if someone can confirm they had this and then it disappeared after going to v11 or v12? I'd rather not update unless someone can confirm this, because everything else is working absolutely flawlessly for me.
[Nook Color Android Development] rainmaker002:
I had this exact problem last week. Because wi-fi wasn't working, I had to flash a new version. It has not happened since.

As stated by several others including myself, I seem to always be able to get Wi-Fi back up and running by fiddling with the Advanced settings on when to put wi-fi to sleep. Changing it to "never", and then changing it right back to where you want it, seems to work fine for that.
[Nook Color Android Development] wpnyc2009:
Wifi seems fine on CM7 v12

Paul,

I got a few cycles of WiFi when i first flashed v12 last night, but now it's steady. Been tethered allday to my phone and it's working great.

Cheers m8!:)

edit: running at >200 density: everything works great and looks awesome. GMaps is squirrely; as is, WeatherBug. GReader is working & looking well. I won't be using GMaps much so I don't mind.
[Nook Color Android Development] Foetus:
Google reader is a weird animal. At 160 and 201+, it scales just fine.... Anything else, and it scales to a phone-like size. Maps, however, seems to crash at anything other than 160 with this ROM. You basically have to choose which app you care about. Maps not working at all, or Google Reader looking funky.
[Nook Color Android Development] jd95:
I'm having issues with like Sherk kart crashing and some other apps. Yet love the progress of cm7
[Nook Color Android Development] koopakid08:
Clean screen, lock/unlock it, download and run nook screen recalibrate, then when you can get a screen protector.

---------------------------------
[Nook Color Android Development] paleh0rse:
Is it plugged in when that is happening? If so, it's a known issue with all Nooks since release -- the solution is to unplug it.

If it's happening when it's not plugged in, then try the recalibration steps described in the last post.
[Nook Color Android Development] paleh0rse:
I'm getting stuck in a boot loop after flashing n221 on top of 7.1stable. :(

Anyone else experience this?

Perhaps it's time for a full wipe again...
[Nook Color Android Development] ianPhillips1:
7.1 was buggy for me, but as soon as I flashed the next nightly it was fine again,221 was the last good "as shipped" I just flashed 229 after inserting the audio.lib from 221 and it business as usual.

Edit,didn't mean to quote

Ian

sent from my ereader
[Nook Color Android Development] skwalas:
I wipe batt stats whenever the battery starts to drift, which can take a long time. The fix they out in place is not perfect: it does not seem to account for the drop in batt performance that occurs over many charge cycles hence the occasional wipe.

And no, wiping batt stats does not have any negative effects, but best practice would be to do a couple of complete charge/drain cycles so the algorithm can set the range properly.
[Nook Color Android Development] borrego:
Just for anyone who is interested, the above also works for N229
[Nook Color Android Development] boxcar8028:
yeah, confirming what borrego said…

did that last night and it worked like a charm.
[Nook Color Android Development] runhopskipjump:
Could someone please upload the libaudio.so from n221 please. I am getting an error when I attempt to download n221 from the site. Thanks.
[Nook Color Android Development] chungylau:
It has been 2 days since I installed N177, and no SOD yet. Keeping my fingers crossed. Better than the stable version.
[Nook Color Android Development] harpo1:
Yeah anything older than 223 is throwing up a 404 Not Found Error so would someone please upload the libaudio.so.

Okay I had nightly 200 on my NC. Extracted the libaudio.so and here it is.

View attachment 760143

I had to zip it up because .so files aren't an approved upload file. Anyway extract and do your thing.

Edit: I added this to nightly 230 and everything is working as it should.
[Nook Color Android Development] dvdivx:
http://forum.cyanogenmod.com/topic/16323-cm7-discussion-of-nightlies/page__st__1680

Looks like they have a thread with someone posting modified releases. Modified 230 is working fine with no FC issues. It's odd they haven't had an official fix at this point since it must be a known issue.
[Nook Color Android Development] waylo:
Great. I was using wakelock on the release, that actually DID NOT work. Then I used a wifi lock program, which seems to work pretty well. Though the wifi cutting out is not really a problem anymore.

I'm guessing you are not running any programs to keep it awake?

Would love to get that great battery life back.
[Nook Color Android Development] dalingrin:
Proper fix here: http://review.cyanogenmod.com/#change,9338

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

Reminder: if you want good video playback you should use the Conservative governor. Ondemand has a tendency to go back down to 600mhz too quickly and this results in video hitching/stuttering.
[Nook Color Android Development] boxcar8028:
sweet, thanks man
[Nook Color Android Development] ronjan:
Since I did not want to download N221 just for the sake of the libaudio.so, I replaced from the stable 7.1.0 release - happy to inform it also works :). Also please remember to reset the permission of the replaced file to rw-r--r-- and restart !!!
[Nook Color Android Development] mikedmeyer:
+1; it's very strange that this issue hasn't been resolved in the official nightlies yet.
[Nook Color Android Development] dalingrin:
Yeah really strange....its called being busy with other things. Feel free to fix. You could also not use the nightlies, they are considered unstable after all.
[Nook Color Android Development] runhopskipjump:
+1. I was going to reply but the man himself beat me to it. Hello Dal. I hope all is well.

Mikedmeyer, don't get all butt-hurt over the reply. Just one of those rookie mistakes of a passionate nook lover. We have come along way with this device with alot of hardwork, planning and feedback. There is no need to rush now.
[Nook Color Android Development] newellj79:
I just built from source. the libaudio problem is fixed so should be implemented in whatever nightly is released after n230.
[Nook Color Android Development] patruns:
Yes, it is in the next nightly. You can see it in the change log and Dal also mentioned it in another forum....
[Nook Color Android Development] frankusb:
Dalingrin,

Props for all of your work.

In the event that someone wanted to fix it, could they really? There are several binaries in CM7 git for encore, including one recently changed to address the audio. It might be appropriate to start leaving a path for others to follow.

I only ask because I know you have other favorite hobbies now.

thanks,

Frank
[Nook Color Android Development] ianPhillips1:
Thx Dal! As always .....you are a superstar

Ian

sent from my ereader
[Nook Color Android Development] dvdivx:
Well I know you have a life and it would take a while. By the way Dalingrin is that your photo on the cm forum?
[Nook Color Android Development] mikedmeyer:
Sure, no problem. Point me to the svn project and give me write access. I can revert to the old version of libaudio.so in less time than it took you to write that sarcastic reply.
[Nook Color Android Development] frankusb:
If you had reviewed the changes you would realize the solution was not a revert of libaudio.so.

His point stands, don't use the nightly builds expecting bug free operation. Also, since the project is open source, others can submit changes.

Complaining about the time to fix problems is weak sauce.

Frank
[Nook Color Android Development] malisha1:
I installed the latest stable build. I'm seeing a lot of freezes. I have to shut down and restart very often. Any advice?
[Nook Color Android Development] boxcar8028:
has anyone flash n231 yet?

damn i'm at work:mad::mad::rolleyes:
[Nook Color Android Development] koopakid08:
You obviously do not know what you are talking about. CM is open source. Go ahead and submit your fix.

You really shouldn't mess with Dal. He'll code up an Android robot to hunt you down ;)

---------------------------------
[Nook Color Android Development] koopakid08:
How did you update? First try fixing permissions and if that doesn't work then try a clean install.

---------------------------------
[Nook Color Android Development] dcrews:
Are you using beautiful widgets? If so, uninstall it. It's what caused all my problems.
[Nook Color Android Development] psiphi:
I can confirm BW causes issues when wifi on... (switched to fancy widgets for now)
[Nook Color Android Development] stolenmoment:
Works great. Downloaded at work, flashed on the subway (again!).
[Nook Color Android Development] MechaGen:
+ 1 n231 seams to have fixed the audio playback issues.

Sent from Tapatalk, NOOK Color CM7 Nightly's!
[Nook Color Android Development] boxcar8028:
thanks guys. yeah, just flash n231 smooth, vary nice.
[Nook Color Android Development] Arbelzapf:
Looks like the OMAP support patch has finally been merged. I wonder what it will bring
[Nook Color Android Development] andyrubin1:
what's the proper way to donate to dalingrin?? iwant to see ics on the original nook color... can anyone post the donate link here??? thx!!!!!!!
[Nook Color Android Development] Arbelzapf:
I think there's a link in his Nook Tweaks app
[Nook Color Android Development] patruns:
Try it. 232 has been posted for download.....
[Nook Color Android Development] Arbelzapf:
Nice :)

Going to try it right now
[Nook Color Android Development] residentorca:
http://fineoils.blogspot.com/2011/10/nook-color-breaking-news-updated-ti.html

"it's mostly about borrowing the whole Audio/Video pipeline, decoding, encoding, rendering, from Froyo, in an obvious attempt to use hardware decoding and hardware video rendering wherever possible, and at every ste"]"...it's mostly about borrowing the whole Audio/Video pipeline, decoding, encoding, rendering, from Froyo, in an obvious attempt to use hardware decoding and hardware video rendering wherever possible, and at every step."
[Nook Color Android Development] dalingrin:
That's wrong, where did you see that? It has nothing to do with Froyo beyond the fact that Ti made OMAP specific optimizations mostly for OMAP4 starting in their Froyo branch on OMAPZOOM. The changes are largely for managing additional framebuffers that are used in 3D devices and devices with HDMI. The changes don't borrow anything from Froyo.

As of right now, it will have no affect on the Nook because our kernel doesn't support the overlay changes that were made to accommodate HDMI and 3D.

Any volunteers to make a 2.6.35 kernel port?
[Nook Color Android Development] tom123il:
This works VERY nice on my Nook Color. Can't think of a thing needed, well maybe a mic. input ;)
[Nook Color Android Development] Arbelzapf:
Thank you for clearing that up, dal. Too bad it has no effect on our nook. This looked like a massive undertaking.
[Nook Color Android Development] msaraiva:
Most certainly from here:

http://fineoils.blogspot.com/2011/10/nook-color-breaking-news-updated-ti.html

I think he said that because on the changes there are a bunch of things that were ported from the Froyo branch.

So, we need 2.6.35 to take advantage of the recent OMAP merges?
[Nook Color Android Development] residentorca:
There's a hyperlink above the quote now. Thanks for clarifying and for your continued work on NC!
[Nook Color Android Development] dalingrin:
Yes. At this point I am not sure what, if any, advantage it would bring to the Nook Color or OMAP3. If you look at the changes, 99% of them are just hdmi and 3D(stereoscopic) related.

However, even if we can't use OMAP_ENHANCEMENT to any great benefit, we will likely need 2.6.35 DSS changes in order even think about using ICS. So, it really would be great if someone knowledgeable could take on the 2.6.35 port.
[Nook Color Android Development] chungylau:
It has been about 5 days now with N177. I had the SOD once, and that was when the battery level dropped below 20%. Not sure if there is due to the low battery or not. Other than that, it has been very stable. I had more frequent SOD's with the stable release.

I do not use any other app to control sleep behavior. It always connects to WiFi quickly after being awakened from sleep. I get very good battery life.
[Nook Color Android Development] miniaturepeddler:
updated to 225 (10/26 nightly) and I had an interesting experience, it was like I had performed a clean install, my google accounts were wiped, requiring re-registration and most of my apps disappeared.

Not that it was all bad, I did take the time to reinstall from the android market and the amazon app market, and used my titanium backup to restore data to apps.

I have the cleanest install that I've had in ages, and all my video apps are working very well. (youtube, tv.com, netflix)

Did anyone else experience this when they updated their nightly?
[Nook Color Android Development] BlindWolf8:
Facebook issues?

Hi guys,

A friend who has a Nook Color with CM7 on it has had issues with Facebook for a few weeks. The application force closes on her each time it is opened. She mentioned that this did not happen to her until I updated her ROM from...maybe 180-ish to the newer nightlies. I've been using nighlies as a daily driver on my Nexus S with no issues but she keeps having these issues on her Nook Color. A backup and a wiping of data/cache did not resolve the issue so it must be a ROM-based issue. Anyone else having issues with Facebook?
[Nook Color Android Development] waylo:
Oh, if you have wifi turn off when the screen goes off, that's not a trouble free version then. That's the fix in general. I'm looking for a version where if the wifi is kept on with screen off, it doesn't Sod.

I heard beautiful widgets might be the culprit, so I've installed an alternate, turned off any wake lock programs, and we'll see.
[Nook Color Android Development] koopakid08:
It's the app. Look here: http://xdaforums.com/showthread.php?t=1272132

---------------------------------
[Nook Color Android Development] patruns:
It is not nightly related. The current Facebook app looks for a GPS, which the Nook does not have. Users have been installing a fake GPS app to get around this.

https://market.android.com/search?q=fake+gps&so=1&c=apps

My guess is that someone updated the Facebook app on her Nook.
[Nook Color Android Development] BlindWolf8:
Thanks again to the both of you. I didn't update Facebook so either she did or the Market did automatically. She'll be happy now. :)
[Nook Color Android Development] patruns:
If she didn't do it on purpose you might want to tell her to never check the box for auto update when she installs an app. :)
[Nook Color Android Development] psychoace:
You might want to tell her to get friendster or something because tether GPS can be kind of unstable. I've had it crash a few times and it kept crashing until I rebooted even after killing it in a task manager.
[Nook Color Android Development] BlindWolf8:
Sounds like a plan. Thanks again! :)
[Nook Color Android Development] MechaGen:
I had a similar problem after installing CM7 n231 on my wife's Nook. Found out that she had FaceBook version 1.7.x and it force closed all the time. Installed a backup copy of 1.6 and problem solved!

Sent from Tapatalk, NOOK Color CM7 Nightly's!
[Nook Color Android Development] patruns:
Yes, the prior app version wasn't insisting on a gps.....
[Nook Color Android Development] falkor165:
Ok so I am running dualboot on emmc and to do updates easiest is to create titanium backup dl newest nightly i want then go to install, then titanium restore to get back apps and data. Will this keep my dualboot? Also would it be best to get on 1.3 before worrying about cm7 updates, trying to get this thing setup as a replacement for my wifes laptop.
[Nook Color Android Development] boxcar8028:
just flashed n235 so far smooooth. all seems to be okay.
[Nook Color Android Development] zequav:
Flashed 235 and now I have the phone signal bars sitting there between the battery and wifi icons :(. How did people get rid of them? I rebooted 4 times, still there.
[Nook Color Android Development] ianPhillips1:
Its definitely a bug for me, it happened once to me a billion nightlies ago and all I did was go to settings /cm settings/ interface/status bar tweaks/ and change the signal type to dcb and back to signal bars and it went away. Only now it goes away and comes right back. Not sure why it wont stay away but I am getting insane SOD's from 233 and 235 (have never had them) and I can't help but think its related to the signal bar issues.

Ian

sent from around the corner
[Nook Color Android Development] dvdivx:
Irritating Radio bars still in 236 as well. Might have to downgrade to another nightly as I don't know how to get rid of them. Downgraded to 232 which does not have the radio bars.
[Nook Color Android Development] boxcar8028:
yeah, got the phone signal bar to. its not the theme. its this way on stock to. looks odd on a tablet that doesn't have a phone.
[Nook Color Android Development] keyodi:
This change is causing the radio bars to get displayed: http://review.cyanogenmod.com/#change,7259

...

...

Edit: Nevermind I was wrong...It is getting the correct value, but it's still has something do with this change.
[Nook Color Android Development] stolenmoment:
So, can we set this somewhere?
[Nook Color Android Development] bigbob23:
I'm not seeing the radio bars, but now have a small image of an airplane next to the battery icon. I thought it might indicate airplane mode, but wireless is still working. :confused:
[Nook Color Android Development] keyodi:
Try this to remove the signal bars but it will come back each time the WiFi is enable/disabled: Settings/Cyanogenmod settings/Interface/Status bar tweaks/Alternate signal display/ --Select Signal text then select Signal bars