yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] Awats:
Sound Interrupted

I don't know the specific build when it started (90's maybe) but I've noticed a periodic interruption of the sound when playing MP3. It's not a stutter (delay or stall) or a breakup. It sounds like some process is kicking in for a fraction of a second and taking over the audio. The music doesn't lose beat so it's still playing during the cut out.

I've turned Wi-fi on and off, with or without the OC kernel and its still there. I tried timing it but it's not a consistent rate of interruption.

I searched and while I found people commenting about it, I didn't see any known solutions.

Any ideas would be appreciated.
[Nook Color Android Development] newellj79:
Could its b a notification activating?
[Nook Color Android Development] Awats:
I was thinking that too but I disabled anything I could think would do that and it still happened. I am still poking around.
[Nook Color Android Development] rhester72:
You can always try silencing notifications and see if it still happens.

Rodney
[Nook Color Android Development] GirLuvsDroid:
Where are you guys finding a working change log for the nightlies? I've tried the link in the second post of this thread several times, but the change log never populates. If someone could point me to the right link for the change logs, I'd be grateful.
[Nook Color Android Development] Awats:
I use this:

http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] Awats:
Yeah, I tried that. No change.
[Nook Color Android Development] bdubs4200:
This, I would LOVE to find!
[Nook Color Android Development] rhester72:
CyanogenMod Settings/Tablet tweaks/Interface/Choose unhide button (defaults to a button we don't have in hardware *LOL*)

Rodney
[Nook Color Android Development] bdubs4200:
Thanks a ton rodeny!

CM7 ( INSERT LAST NIGHTLY HERE)
[Nook Color Android Development] GirLuvsDroid:
Thanks to Awats and ace7196 for the nightlies change log link, but I think that's the same one from the 2nd post and it's mostly a blank black page for me.
[Nook Color Android Development] :
There is a full page of changes from N91-105. Maybe a browser issue for you where the page isn't loading or rendering properly?
[Nook Color Android Development] seth.i.simmons:
I've found that I can't get the changelog to show in IE9. If your running that, you might wanna try Firefox or Chrome.
[Nook Color Android Development] Ronin3178:
I can confirm it loads properly on my D1, stock browser.
[Nook Color Android Development] bigbob23:
Grey lettering on a black background isn't exactly designed for readability :p
[Nook Color Android Development] GirLuvsDroid:
Thanks to everyone who responded to my question about the CM7 nightlies change log. I was able to load it successfully on my NC using DolphinHD.
[Nook Color Android Development] Awats:
Strange that it took that, but cool!
[Nook Color Android Development] sisterchick:
You know...I've never liked the Gingerbread look with the black menus much either! Those of us with bifocals need not apply!
[Nook Color Android Development] EGOvoruhk:
Anyone know what dalingrin's latest commit does?

"Update wl1271 firmware, module and kernel"

Better WiFi or Bluetooth range? FM enabled? What kind of secrets does it hold!?
[Nook Color Android Development] :
Just installed the latest nightly to my sd card and I seen to have lost root. Anyway to fix this without reflashing? Did anyone else experience this after installing?

Sent from my Nook Color
[Nook Color Android Development] humble:
i can confirm this. to fix use Rom Manager, go to "Download ROM" then to "Extras" you will see "Superuser 2.3.6.3 efgh"(down it). then since we dont have root privileges reboot into recovery and install from there.
[Nook Color Android Development] mooja:
Thanks for the su download. Mine did the same. I wonder why 106 doesnt have su?
[Nook Color Android Development] MadMikeSS:
Where does it download to? I can't seem to find it after downloading it and rebooting into recovery.

Edit: nevermind, I did a search in root explorer and found it the one one folder I didn't look. haha.

Must have been some oversight by whoever built 106, can't imagine why they would miss putting su into a custom rom like that..
[Nook Color Android Development] pavlos46:
Any chance of a Bluetooth kernel for stock 1.2.

and wifi location services ?

:D
[Nook Color Android Development] luciferii:
this is the cm7 thread not 1.2 nootered thread.
[Nook Color Android Development] Wipeout:
Same here, but humble's post showed me how to fix it. :)
[Nook Color Android Development] bekyndnunwind:
Just flashed 106, and lost root as well...

Attemped to reboot into recovery to flash superuser.apk (downloaded it through rom manager). It failed.

Trying to download manually and put it on my SD card - will report back if this works...

EDIT: Flashed latest Superuser.zip from link a few posts down and everything is OK. Using 6/17 OC and wirelrss mouse with USB host kicks a$$!
[Nook Color Android Development] newellj79:
Latest flashable superuser if u loose root when flashing n106.

http://db.tt/GDhtfZ8
[Nook Color Android Development] :
Can anyone else not reproduce the reproducible SOD after 106?

:D
[Nook Color Android Development] DizzyDen:
I took a different approach....

Backup cm_encore_full-106.zip to cm_encore_full-106-su.zip to indicate it has fixed su

Extract cm_encore_full-106 to a folder called cm_encore_full-106-su letting it overwrite existing file if you get that prompt (you will in 7zip... this has been asked about before... windows is case insensitive so there are two files windows reports as duplicate)

Added su from N105 to N106-su /system/xbin

Used FileCompare to copy lines referencing /system/xbin/su from N105 to N106 files

\META-INF\com\google\android\updater-script
\META-INF\CERT.SF
\META-INF\MANIFEST.MF

Using WinRar... added entire folder contents from cm_encore_full-106-su to cm_encore_full-106-su.zip. This will keep both of the "duplicate files" intact in the zip file

And of course I ran my IMEI generator on that zip file.

Note that superuser.apk is still installed by N106... just not su.
[Nook Color Android Development] khaytsus:
That'd be awesome, I'll be watching for it. using stock ROM for a few days..

Seriously, why isn't su in 106, and apparently 105? What else is missing I wonder.
[Nook Color Android Development] 12paq:
Often its just a simple human error. Have you ever looked at the code of even a small patch? It's like some lengthy advanced alien code language to me, lol. If you miss a comma or a duplicate file or image.. and fail. Its got to be easy to miss somthing. You guys are damn lucky I'm not the one maintaining theses builds. Lol. :)
[Nook Color Android Development] philburkhardt:
What would be the benefit of doing this:

...over this?:

You still end up with the superuser.apk in your system/app/ folder. All of the backing up and editing seems like a LOT of extra work, no?
[Nook Color Android Development] DizzyDen:
Just a clean install... and actually it isn't much work at all.

Also as I stated in my post... superuser.apk IS installed via the official nightly... just su isn't.
[Nook Color Android Development] Ronin3178:
Think I will just wait a day or two for 107.
[Nook Color Android Development] philburkhardt:
Ahh, got it. I was reading that backwards :rolleyes:.
[Nook Color Android Development] TJNooker:
Same here. Easy to fix.

For those that don't know, there's a reboot into recovery option in the power menu. Once you download SU, hold your power button until the power menu comes up. Hit reboot, then select the reboot into recovery option, and then hit Ok.
[Nook Color Android Development] Nburnes:
Yea......just needed to download su from Rom Manager then flash in recovery.
[Nook Color Android Development] mjchung:
Anybody notice an accelerometer glitch in n106? It won't go back into portrait mode after switching into landscape. A reboot fixes orientation, but as soon the accelerometer kicks in, orientation locks again. n99-105 did not have this problem.

Currently running Dalingrin 061311, o/c at 1300.
[Nook Color Android Development] 12paq:
No problem here on 106, 061711, oc at 1300.
[Nook Color Android Development] :
Hrrrm..how do I go about updating su on a CM7 verygreen sdcard install? Are the steps the same as what's already been posted?
[Nook Color Android Development] oldman_58:
Look on your SDCARD

clockwook/download

keep drilling down till you find the zip file
[Nook Color Android Development] I Am Marino:
I'm gonna stick on whatever nightly I'm on for a few days.
[Nook Color Android Development] newellj79:
C

I can get portrait at 180 degrees, that's is upside down, and landscape on both sides, but no portrait right side up.

FIX EDIT.... check 0 degree box in settings/cm/display for some reason it isnt cheched by default in n106. All good now.
[Nook Color Android Development] oldman_58:
I have two nook colors

NookC-1 is getting a lot of SOD, There is no LAST_KMSG in /proc I assume it is because the system is locked, Deep Sleep works great

Nightlies 105, 106 6/16 kernel

NookC-2 is working great same setup, Sleeps well

I just downgraded NookC 1 to Kernel 6/13 see if it makes a difference.

Any suggestions?

∞====∞=================

After downgrading the kernel, lost Wifi... ant back 6/16 kernel...
[Nook Color Android Development] mjchung:
Thank you! I love it when the answer is so simple and elegant. As they say in the airplane safety announcements, 'the nearest exit may be behind you'.
[Nook Color Android Development] gudism:
Wondering if anyone has any ideas on this. Deep sleep has been working fine for me since about nightly 87 (I think), but since I have installed k9 email app (after flashing 95), the nook seems to spend probably 55-60% at 300 and 35-40% in deep sleep.

I am figuring it is a setting for my email and when it checks mail, but looking at my settings I can't seem to think what it could be.

does anyone have anything to offer with this?
[Nook Color Android Development] luciferii:
anyone know if su is back in nightly 107?
[Nook Color Android Development] :
Was for me. I didn't have to flash su manually or anything this time.
[Nook Color Android Development] newellj79:
Your avatar rocks!
[Nook Color Android Development] jbwalters:
Nightly 107 is not allowing the home screen to display portrait mode, only landscape, regardless of the rotation settings. Applications display only in the portrait mode with rotation turned off, and only in the landscape mode with rotation turned on.
[Nook Color Android Development] Ronin3178:
Not for me, everything looks normal. N107 eMMC/OC 6-18
[Nook Color Android Development] jbwalters:
I will reflash and wipe dalvik...
[Nook Color Android Development] openallnight:
N107 and 06/18 Kernel 2 issues

1)Wifi stays in Connecting state for 2-3 minutes after which it goes to disconnected.

2)Display opens up in Landscape mode by default and rotation setting for 0 Deg has to be manually set for portrait to work in default upright location

Anone else have the same?

Edit: hmmm after one deep sleep wifi came back up.
[Nook Color Android Development] jbwalters:
I also just found that I had to enable zero degree rotation.
[Nook Color Android Development] junkrobot:
That's strange. I had no landscape/portrait issues and I didn't touch any settings from the get-go with 107 and the 6/18 kernel. Everything seems pretty normal.
[Nook Color Android Development] domin8:
For those running oc kernel at 1300 what are your steppings? I'm at 1200 now ans feel like toying with it a little bit :-)
[Nook Color Android Development] 12paq:
125/400/800/1100/1300

125 five was an earlier minimum limit, not sure if it still is..

1300 works on some Nooks as well as 1325, some can push it farther, not me I get stuttering in the gui after 1325. 1275 max seems to work for many, some seem happy with 1200. Your milage may vary. Just make sure you uncheck "apply on boot" in the tweeks app and I do it in the CM cpu settings also, so if you crash you can restart, hopefully. Lol.

Have fun. This tweek app is amazing.
[Nook Color Android Development] Ronin3178:
Back on 100, I was stable at 1350 as my last step. But with 106 & 107, it didn't like 1350, so I dropped it down to 1325.

That being said, I use 350/ 650/ 950/ 1250/ 1325
[Nook Color Android Development] I Am Marino:
I'm running 300/600/950/1200/1300 no issues with lag, etc.

Still rocking the Incredible with the XDA Premium App.
[Nook Color Android Development] Nburnes:
300, 650, 875, 1175, 1300 for myself.
[Nook Color Android Development] Awats:
Does the Tweaks OC override the Settings OC?
[Nook Color Android Development] vgupman:
Does anyone know what bugs exist or are being worked on for the latest nightly builds or where I could find out? I've been running 103 for a while and can't find any. It seems better to me than the stable because I don't experience premature battery death at 30 percent on this nightly build as I do on the latest stable.
[Nook Color Android Development] :
Uncheck "set at boot" in the cm settings of if you are using the tweaks app.
[Nook Color Android Development] aludal:
You can call this a troll as much as you wish, but there are too many nagging questions that are not answered. Sure, the nightlies are not supposed to be a source of bug reports that are meant to be taken into any account, and people playing with them are just silent lab rats, so CM7 devs can easily discard any questions on:

-- how's moving to 2.6.32...37 kernels going on?

-- any successes in engaging SGX/DSP hardware? Open GL ES 2.0 drivers? Ffmpeg decoders with HW support, HW overlay?;

-- Bluetooth, FM?

-- There's TI code of Adobe Flash Plugin for Froyo, can it be "dropped in"?

-- I couldn't find VOME engine (VisualOn.com) promised for AOSP 2.3, how scalable is it for the NC?

-- Playing with so called LCD density is a snake oil, and I hope devs will revert to simple physical density of 169.3333 for NC;

-- No sign of anybody playing with a non-linear touch sensitivity scheme, like in more sensitivity to edges and corners. If it it takes a separate calibration app, be it.

I don't play with nightlies yet as I see there's nothing to play with actually. However I'm quite curious what is so snappy with the latest (8th) nightly, UI? "3D" wallpapers? Transitions? Eliminated A/V desync? What would be a progress in Neocore/Linpack benchmarks (if Quadrant won't work for any reason)?

Note that I never ask about Gapps/Market in CM7 as I feel these can just muddy the testing experience. Android 2.3 is a known resource hog compared to Android 2.2, what is so attractive in the idea of CM7 for NC compared to CM6?
[Nook Color Android Development] rickpref:
So far so good with Nightly 8. The force close in wireless settings is gone. Also wireless is more stable..not crashing on sleep. Everything is pretty stable since Nightly 7 but feels a little more responsive in 8.
[Nook Color Android Development] donballz:
Just flashed the emmc recovery and then nightly 8 using the recovery.

Things seemed to be ok. Then I went and selected Reboot into Recovery in ROM manager to make one more mod and the screen just went blank and never came back on.

I am hoping the battery is just really dead but I don't see how that could be. Normally when you pulg it in dead you get the "Too dead to turn on" screen. Not ever getting that. I am a sad panda.
[Nook Color Android Development] chli:
I tried this last night and it made my nook boot only in CWR.

I had to flash the original boot back (from my bootable recovery SD) and flash CM7 on top of it to be able to return to the CM7 desktop.

Maybe I did something wrong since it was the first time I used Rom Manager.
[Nook Color Android Development] chli:
What did YOU do to progress on any of these items?

As for your question about the snapiness if you read the changelog you can figure it out.

My understanding is that they found a workaround to the GC issue when scrolling lists.
[Nook Color Android Development] spikey911:
Ok, I will..

I once gave a car to someone who was in desperate need...Told them everything that it needed and they were happy as a clam..

Week later I get phone calls on a daily basis about everything under the sun wrong with the car..Even wanting me to fix things for FREE...

I will never do that again...

You come off with an attitude (not just in this thread) and it is not right to do so with these kind people doing this stuff for free...

Please be patient like everyone else.
[Nook Color Android Development] {Diemex}:
I'm still running the very first Cm7 from friday,

one question: Is hardwaredecoding videos and audio functioning now or will it only be suppoerted in the final version?
[Nook Color Android Development] Biff Rosco:
The my apps market fix worked the first time I opened market, but not thereafter.

Coming from nightly 2. Nightly 8 seems to be working well (aside from known issues) and snappy on included kernel. Great work CM Nook team!
[Nook Color Android Development] nemith:
It's called a nightly for a reason. The focus right now is the DSP.

But i'll give a rundown (just this once)

how's moving to 2.6.32...37 kernels going on? -- On the list, but not a high priority

any successes in engaging SGX/DSP hardware? -- Highest Priority, but not going well.

Bluetooth, FM? -- Probably not going to happen for a long time. FM is completely worthless as it has no traces from the chip to the headphone jack. This means no antenna. BT on the other hand is possible, but it's the lowest of the priorities right now as it's not in stock either

There's TI code of Adobe Flash Plugin for Froyo, can it be "dropped in"? Upstream omapzoom has some code for this, but it may be OMAP4 only. Worth a shot only after dsp is fixed

I couldn't find VOME engine (VisualOn.com) promised for AOSP 2.3, how scalable is it for the NC -- No idea what you are talking about, but i can guarantee no one is looking at it.

Playing with so called LCD density is a snake oil, and I hope devs will revert to simple physical density of 169.3333 for NC -- It's a nightly, get over it. That being said, stock NC runs a pixel density of 160 which is native for our screens (although the math works out to 169.33333). Although using 160 breaks a lot of applications. I don't think this setting is a float either... I could be wrong, but i've only seen integer values.

No sign of anybody playing with a non-linear touch sensitivity scheme, like in more sensitivity to edges and corners. If it it takes a separate calibration app, be it. -- You're assuming what the problem is. It seems that the touchscreen snaps to the edge, has nothing to do with linear touch sensitivity. The kernel does remove 4px from the touchscreen all around which seems to have helped quite a bit, but that is about as far as it's going to go without a serious kernel hacker

TL;DR: It's a work in progress. If you want something done, help out and submit code!

P.S. This will probably be the last time i respond to a thread like this.
[Nook Color Android Development] nemith:
Read the commit messages for what has changed.

Things will get done when they get done.
[Nook Color Android Development] openallnight:
I have a newb question regarding LCD density

1)I removed the LCD density from build.prop and everything but maps works fine.

2)I set lcd density to any value between 160 and 180 maps works but google reader comes up in a smaller screen.

I understand default nook density is 169.3333. How is that value set if not set in build.prop? Why does maps not work at default value (if nothing is set). Is that caused by some Kernel change? Can I launch maps with a different density value so I can get (1) to work?

thanks!
[Nook Color Android Development] nemith:
Yes the default is 160. The native resolution. Setting it to anything else is a hack at best.

The 169.33333 number is the math done assuming the screen is exactly 7".

Setting the DPI to something besides 160 causes Android to interpolate or extrapolation pixels to make it work. This is why they look less sharp.

Maps was never designed to work on a 1024x600 display with a 160dpi. Go figure.

There is not a way to set DPI per application. Hopefully when HC goes AOSP it will have support for these displays.
[Nook Color Android Development] donballz:
At this point I have to assume my device is completely bricked. Total hardware failure, I don't think CM7 was the cause. Maybe just coincidence.

Does anyone know how much they would charge me to refurbish it?
[Nook Color Android Development] bartimeus:
Attempt to boot it using the bootable CWR floating around here and then flash a new rom from that.
[Nook Color Android Development] Homer_S_xda:
Before you take/send it in. Try one of the CWM SDcards or even Froyo on an SDcard. If that boots, you can try several approaches to get the partitions back to a working condition. Unless you somehow changed the boot order, it should always boot to a valid SDcard install.

Homer
[Nook Color Android Development] nemith:
Let it charge for a while.

An no, don't start this CM7 brick my Nook crap. CM7 cannot do that.
[Nook Color Android Development] donballz:
Am I speaking English? I said it wasn't cm7 so get over yourself.

Its still charging but I think its a lost cause.
[Nook Color Android Development] tj!2k7:
If your nc has really gone belly-up due to hardware failure, you should be able to exchange it for a new one as it comes with a 1-year warranty.
[Nook Color Android Development] dalingrin:
My guess is that you tried to format an SD card while running CM7. Vold is terrible and finds our /boot partition first and thus formats /boot. I did the same thing once...I have a big red disclaimer in the Developers thread stating this.

If this is the problem then you should be able to boot off an sd card.

From there you can restore your emmc /boot fairly easily.
[Nook Color Android Development] Awats:
Ah, thanks. I never set it anyway.
[Nook Color Android Development] :
Best I can give you is a running changelog. As of the wifi fix last night, the nightlies are indeed awesome.

http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] :
Still having problems with Su in n107. Superuser.APk says the most recent version is installed but all if my existing apps wont let me grant Su privileges. The only one that seemed to work properly was dalgrins nook tweaks

Sent from my Nook Color
[Nook Color Android Development] Nburnes:
Su hasn't been a problem for me on the newest nightly. You should try forgetting the applications in the allow list, then running and allowing them.
[Nook Color Android Development] :
Hmm. No apps listed under superuser.apk list besides the nook tweaks one.

Sent from my Nook Color
[Nook Color Android Development] Nburnes:
What apps are you having problems with then specifically, that need root access?
[Nook Color Android Development] :
Apps like Root Explorer (to enable R/W), NookColor Calibrate, Battery Calibrate, Terminal, etc.

I don't know if it matters but I'm running off SD Card. I guess I'll just flash back to N105 and see if that fixes things.
[Nook Color Android Development] Nburnes:
When you open them, what happens exactly?
[Nook Color Android Development] domin8:
Cool thanks guys for the tips, ill give them a shot a little later. I was having issues because I checked apply at boot on both cm settings and tweaks app.. ill play with it now :-)
[Nook Color Android Development] :
Ok...flashing back to N105 didn't fix anything. Updating to N106 must have borked something in my settings that is being retained.

BatteryCalibration - Gives a ROOT YOUR DEVICE FIRST! error

Titanium Backup - Sorry could not acquire root privileges

Root Explorer - No errors but when I click on Mount R/W it does nothing

Nook Screen Recalibrate - No errors but when I click on Re-calibrate it does nothing (normally it recalibrates and then reboots automatically)

Terminal - Gives permission denied when I type Su

SD Speed Increase - Could not write to file error when I try and apply changes

Nook Tweaks - I get the superuser allow or deny prompt when I try and apply any changes. This is the only app that seems to work.