yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] aludal:
It is obvious that at least for YouTube, there was nothing wrong with Eclair code for engaging DSP and HW renderer in perfect sync with audio. Since then, this harmony was brutally broken in Froyo, and GB, and HC. I'm not saying that ALSA updates are the culprit, I'm only asking whether we could roll back some relevant code. Maybe replace the "stock" (Market's) YouTube.apk with the EVO's YouTubeHQ for the time being. Maybe reinstall those 4 infamous "stagefright" stanzas in build.prop and play with them.

I suspect there's nothing wrong with DSP support code as of today, it's just bad environment/faulty handling/outside error, even typo that results in breaking audio sync.

I understand it's way different, but, say, in DirectX (x86, WindowsXP), an audio renderer OUTPUT was a decisive factor to keep A/V in sync in a graph. So, when this OUTPUT becomes interrupted somehow, stripped of clock timings, the picture becomes a slide show with every rendered frame being re-synced with audio at that moment. In other words, a glitch is simple, and the task is to find it -- maybe just to see diffs with what was made for Eclair and how it was broken later.
[Nook Color Android Development] MACLUIS1:
That guy is either a troll or needs some serious medication.
[Nook Color Android Development] :
Haha, yeah.
[Nook Color Android Development] dalingrin:
Oddly enough, almost every device decodes audio in software and not on coprocessors. I'm not entirely sure why that is but seems to be the case across almost every device I've owned.

Keep in mind that because I've backported the Droid/Sholes DSP kernel driver we now use the AOSP DSP userspace files. Meaning, we share all the DSP related code with the Droid now. They have no issue with audio sync or dropped frames. This doesn't definitively eliminate the DSP as part of the problem but I feel pretty confident that our issue is not DSP related at all. One thing that we have nothing in common with other CM devices is the way we handle Alsa and audio. I think this is where we need to start looking.

Keep in mind we share almost nothing in common with the B&N build. This is even more true with the media stack. The stagefright options you saw in the build.prop are not relevant in Gingerbread. Gingerbread removes OpenCore entirely so we cannot disable Stagefright like we could in Froyo.

The move from Eclair to Gingerbread is fairly large jump especially when we are stuck with an old kernel. Luckily all this work to get Stagefright working and our kernel changes will apply directly to Honeycomb when the source is released. Because of this, even if it was possible to rollback changes to something similar to Eclair, I wouldn't want to.

Having flash audio sync issues and dropped frames on non-flash videos tells me that our problem is with audio/Alsa. I haven't looked at the audio pipeline enough in Gingerbread to know where A2DP and regular audio playback diverge. If the issue is not fixed by the time I get back I plan to dive into the audio pipeline and find out. It is definitely odd that A2DP, which requires extra processing to encode for the BT protocol, doesn't have frame rate issues.
[Nook Color Android Development] :
You heard the man, let's get crackin'!

So I don't know a lot about the programming (does MATLAB help?), but is there anything someone like me could do over spring break? Would getting a log from the audio playing on external bluetooth speakers, and gradually pulling it away until it played on the internal NC speaker help?

Maybe a portion of code I can look at to see if there is anything I can gather from it?

Where is the AOSP repository would one find the proper section of code where things may suggest where audio changes and how that affects the framerate?

I'm reading all I can about the Gingerbread code...
[Nook Color Android Development] Snyperx:
I just tried your recommendation with a fresh flash of build 23 and am still having the same issue. BT was working for me.
[Nook Color Android Development] mr_fosi:
Perhaps I can help on the BT issue: the hard-off solution didn't work for me either. Instead, try running ROM manager's "fix permissions", then doing the hard-off.

Worked for me after the plain hard-off didn't.
[Nook Color Android Development] jtbnet:
ALSA would seem to be the root of the BT AudioInput (mic) not working also... I just paired/connected my Moto S9 BT Headset with Mic, and other than the fact that the range was pretty horrendous (Max 9-12in.) before dropout a logcat does note some issues when attempting to open the Input device... this is the logcat from an attempt to start the 'Sound Recorder' app where key clicks are still working fine to the BT output device...

D/ALSAModule( 902): open called for devices 00040000 in mode 0...

E/ALSALib ( 902): external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)

Unknown PCM AndroidCapture

E/ALSAModule( 902): Failed to Initialize any ALSA CAPTURE device: Unknown error

: -2

E/AudioRecord( 902): Could not get audio input for record source 1

E/StagefrightRecorder( 902): audio source is not initialized

I/MPEG4Writer( 902): The mp4 file will not be streamable.

D/A2DP ( 902): bluetooth_start

E/MediaRecorder( 2278): start failed: -2147483648

D/ALSAModule( 902): open called for devices 00040000 in mode 0...

E/ALSALib ( 902): external/alsa-lib/src/pcm/pcm.c:2210:(snd_pcm_open_noupdate)

Unknown PCM AndroidCapture

E/ALSAModule( 902): Failed to Initialize any ALSA CAPTURE device: Unknown error

: -2

E/AudioRecord( 902): Could not get audio input for record source 1

E/StagefrightRecorder( 902): audio source is not initialized

I/MPEG4Writer( 902): The mp4 file will not be streamable.

E/MediaRecorder( 2278): start failed: -2147483648
[Nook Color Android Development] aludal:
You're right, and I take my suggestions back. Last TI libaudio commit is even named "Disabled OMAP libaudio HAL layer" back in 2009 :http://git.omapzoom.org/?p=platform/hardware/ti/omap3.git;a=commit;h=1f7293885f0d272b06aadd343c8221fab0b3f687

I see, I see. IVA2 (hardware) might be used in ENcoding audio (like vocoder, speech-to-text, and the like), the DEcoding of audio is hardly a computational problem of a size to be necessarily delegated to FPU. On the Droid's AOSP stuff: is Sholes (earlier Droid) is close enough to NC DSP-wise? Are there any Droid X/2 DSP kernel drivers available?

There's definitely no need to physically roll back anything. Besides, that EVO's YouTube "HQ" foreclosures on me probably not finding relevant/opencore libs.

Encoding it into packets might be performed with IVA2 help, so it's fast enough. Audio stream in video is not of a significant bandwidth anyway. It's decoding it that hiccups. In any case, yes, it's odd.
[Nook Color Android Development] manchucka:
Nope, he's articulate and willing to be corrected.

Sent from my mind using magic
[Nook Color Android Development] MДЯCЦSДИT:
This rom's epicness is increasing exponentally.

Sent from the developer of HoneyBunches and the unroot script.
[Nook Color Android Development] Slack3r:
So many builds o_o
[Nook Color Android Development] bonobomidwest:
Ditto. You are so hugely appreciated dalingrin!!!
[Nook Color Android Development] Bimboy:
Maybe so, but is also exceedingly long-winded, loves to hear him/herself talk, constantly tries to get others to do (largely meaningless) tasks to satisfy whimsy, and spams his meager website in every single post.
[Nook Color Android Development] krweby:
One of the recent nightlies live wallpaper was working but in at least the last two it isn't. Is it me or is it the same for others? I'm on build 26.
[Nook Color Android Development] chisleu:
Yep. Stopped using it because of battery life but I just looked and it is disabled in today's nightly.
[Nook Color Android Development] krweby:
Thanks. At least I know I'm not loosing it.
[Nook Color Android Development] Nburnes:
Works fine on the newest nightly after this. http://nookdevs.com/NookColor_Enable_Live_Wallpapers
[Nook Color Android Development] pgwipeout:
Video Decoding

I tested a video file with the audio stripped out, 640x480 768kbps bitrate H264.

Plays smooth as butter, attempted the same video using different audio formats, all have the choppy framerate.

Will continue trying different formats.
[Nook Color Android Development] chisleu:
Yeah the problem with hardware accelerated video is the sound processing. External sound processing (bluetooth/etc) will make it go smoothly as well. Codec changes will not. Pretty sure the hardware accelerator won't accel 1024 width video, but I'm going to try that now (stripped audio.)

EDIT: No it won't accelerate video that large.

EDIT: It will accelerate 848x480 high bitrate video. Looks great. Wish it would accel 1024x600 video because that would be... epic... I believe it's thought to be a hardware limitation though. Video less than 848x480 are scaled up to 848x480 before going into the acceleration hardware.

If you use the software decoding, it will play smoothly (although I recommend video smaller than 848x480)

http://xdaforums.com/showthread.php?p=12076390 (here I rant a bit about codecs and encoding video for the NC)
[Nook Color Android Development] chisleu:
OKAY.... So here is something interesting. I can play an MP3 flawlessly (with winamp) while playing a hardware accelerated video stripped of audio (with MoboPlayer)

Talk about narrowing it down.. haha. What a trip.
[Nook Color Android Development] chisleu:
Thanks. I pushed the latest Phiremod 5.1 version of LiveWallpapers and the picker. I already had the libs.
[Nook Color Android Development] miniaturepeddler:
Question on the nightly builds:

If you want to update your current cm7 do you simply flash with the most recent nightly or does this require reinstallation of your apps and customizations?

(I installed build 26 yesterday and so far I'm very happy: Flash 10.2 successfully installed and works, youtube app installed and works. I have had some problems with Softkey aborting and restarting several times during use. Quadrant score of 1250. Music apps working well - Pandora.)

Thanks!

Robyn
[Nook Color Android Development] dantheman_:
Just flash over if you're flashing a new nightly.
[Nook Color Android Development] chisleu:
I have a wonderfully modified/configured phiremod 5.1 here that I don't want to lose, but I am considering flashing CM7 latest over it. Any ideas on potential stupidity and negative negativity that must ensue?

Doing this because my CM7-26 (+live wall paper apks) allowed me to use jumpgate which is my New Favorite Thing(tm) and after installing Phiremod 5.1, I can't download it anymore.

EDIT: yeah that doesn't work... don't flash CM over phiremod.
[Nook Color Android Development] ericmcintire:
yxplayer

Hey guys... just wanted to let you know I've installed "yxplayer" free version onto my nook and I've run a test with the latest version and the audio and video both play fine with very few frame skips.... the file information is follows: 720x480 .mpg file 29 fps... not sure if this information helps but it couldn't hurt... I'm not streaming the audio, just playing it from the nook.. will take a video if you guys want.
[Nook Color Android Development] dalamchops:
that's because you're using software decode.
[Nook Color Android Development] ericmcintire:
Gotcha, sorry to bother then, just trying to contribute.
[Nook Color Android Development] aludal:
I'm glad that I'm not alone in pursuing hardware acceleration in video for NC. Eclair (A2.1. YouTube "HQ" of my old post) shows that it can be achieved. Which means generally, that lost frames are from whatever reason (ALSA?) throttled but they are synced, and hardware (HD) rendered. There should either a simple thing -- like a bad config/init record, or a complex thing of a special TI-flavored Adobe Flash Player plugin sort.

In other news, there's not much left for CM7 to get into a snappy and beautiful CM7 Release Candidate. Some say 3D stuff is under par. I would say: calm down, the chip is 2 year old, meant for some smartphone, never did it... In any case, it's a Hollywood story. The only thing that is missing is B&N is pissed like hell and decides to develop the NookColor2 on TI OMAP 4440.

On CM7 front, personally I would put Laucncher Pro there and add Gapps in an easier install , but it's just me, and CM7 for NC wizards have their rules. Plus I don't like a hairthin in notification, some artifacts (=wrong play with DPI, again)

Otherwise, the magnificent powers of CM are something to behold. Hopefully they will produce CM8 for NC that misery Moto Xoom will envy.
[Nook Color Android Development] krweby:
I downloaded the vision nightly and pulled the files from it. Then made a cwr update file from it. all of the built in ones even work. Now I can flash it after every nightly.
[Nook Color Android Development] rckymtnrfc:
Please share...I miss LWP.
[Nook Color Android Development] chisleu:
Yeah, I'm working on one as well. Although when you unzip the new nightly on top of your installation (unless you are formatting system) then it shouldn't remove your programs.

I think I'm going to install phiremod's AWD Launcher. I've already installed several things from the phiremod 5.1 (his version of miui player is the best!)
[Nook Color Android Development] krweby:
here you go.

http://www.megaupload.com/?d=PNTD92BZ
[Nook Color Android Development] krweby:
I haven't looked at the script in the nightly but when you flash it I think it removes the system files or some of them first before installing the new ones. That is why the live wallpapers where removed the last time.
[Nook Color Android Development] chisleu:
I didn't know it did that. I didn't see anything in the script. He formats /emmc but not system. I think system only gets formatted if you do it.

Maybe it does (I'm frequently wrong. :) ) or maybe it did once before. Or maybe it explicitly deleted the live wallpapers when he removed it from the new package.
[Nook Color Android Development] krweby:
It might have been the one time. I haven't looked at it. But I know that the live wallpaper was there then it wasn't. And I didn't install it or remove it. I'll have to poke around. I'm getting ready to flash build 30 I'll see what happens this time. :)
[Nook Color Android Development] racks11479:
Just an FYI, the whole partition is formatted. So it's wiped before installing new nightly. If you don't want it to, just remove the first line below from the script and it will only update without formatting the partition.

-Racks
[Nook Color Android Development] krweby:
You beat me to it. :p I was just looking at the script. I'll just keep flashing the LWP after. That way if there are any nasties will get removed when installing.
[Nook Color Android Development] dalingrin:
Either I or nemith will fix our build process to include LWPs in the nightlies. I was under the impression that it was already fixed but apparently not.
[Nook Color Android Development] krweby:
Thank you.
[Nook Color Android Development] cybertimber2007:
Dalingrin, any chance you can also enable ipv6 in the kernel?

Edit: Adds "Please" :) Even if it's down the road.
[Nook Color Android Development] pavlos46:
hey man are you back?

Any news on the DSP/sound issue ...

Thanks for all the great work.
[Nook Color Android Development] frenetic:
I feel left out, not having a BT speaker to output to so I can try these videos that don't work completely right now.
[Nook Color Android Development] chisleu:
If you don't jump around a bunch, pause/unpause repeatedly/etc, then MoboPlayer can play 854x480 600kbps mp4 in software with near-full frames. It is very watchable. Once you start jumping around/pausing/etc you will mess up the sync more than it is otherwise. So for now, there is something that is usable until the problem is found.

Funny thing is, I can play a mp3 in the background and watch a movie w/ hardware accel that has the audio stripped out and both play perfectly. Very strange indeed.
[Nook Color Android Development] tjsooley:
hi guys I am using the newest nightly (3/23) and bluetooth doesn't work, any ideas?
[Nook Color Android Development] cybertimber2007:
Do a hard reboot (hold power until it shuts off), then boot back up and see. If it still doesn't, try enabiling via settings > wireless (seems to work for me first time over widget). If not, try a soft reboot...

If still fails, send a logcat.
[Nook Color Android Development] DairyKnight:
You need to turn it on first thing after rebooting. After using the device for a while the option won't work.
[Nook Color Android Development] 360Razir:
I am not sure what constitutes "awhile", but CM7 has been on my NC for about 28 hours now and I just got BT activated. I don't really have a need for it at the moment, but wanted to check it out anyway.

By simply doing a hard turn off and then turning the NC back on, my BlueAnt Q2 headset connected without issue. May just have to invest in good BT stereo headphones once video is working well.

Thanks for the tip on how to get it enabled.
[Nook Color Android Development] tjsooley:
I can turn it on right after reboot thanks
[Nook Color Android Development] rcmsmas:
I have been trying to install nightly 30, and it keeps getting stuck at the boot up with the cyanogen logo. I tried resinstalling, wiping dalvik, fixing permissions, etc. For some reason, it will run off of the SD card (albeit slowly), but can't get past boot up from internal memory. Any ideas? I tried searching the thread but couldn't find anybody with a similar problem.
[Nook Color Android Development] AWiseMonkey:
I sometimes have to boot it 2-3 times before BT will turn on...
[Nook Color Android Development] fattire:
This looks cool while everyone's waiting for HC.
[Nook Color Android Development] Fishfoot:
Hey Guys,

I'm running nightly 22 and having an issue with charging. I have been using non-stock chargers to charge my nook and I really wasn't having any problems. Then about a week ago the nook just stopped charging. I left it overnight and it still remained basically dead.

I found a post somewhere where somebody said boot into CWM and wipe the battery stats. I did. It worked. Everything was fine for a week and now the problem is back. I can do the same thing again but I'd love to know:

1) Why this is happening.

2) Is it fixed.

3) What I can do to troubleshoot this so that if somebody else is having a problem we can fix it.

I'd be glad to post information, I just don't know what to post.

Thanks
[Nook Color Android Development] Fishfoot:
Also, not to hijack here and post back to back... but....

How does one get started working on this project? What and where do I get information on developing for this project?
[Nook Color Android Development] xawen:
Basics on getting the source and compiling the build can be found here. There's plenty more information about building CM, signing up for Gerrit so you can make code commits, and other CM dev info out on the web if you run into issues.

Most of the NC devs can be found in #nookie on freenode so that's always a good place to get an idea what's actively being worked on.
[Nook Color Android Development] :
Re: CM7 nightlies

Just wondering: Is there a way to actually install the recovery on the emmc for CM7? Why do we have to boot from uSD everytime? Just curious...
[Nook Color Android Development] stinky634:
Install the CWM from ROM manager once you get CM7 booted up and installed. Then you can ditch the SD card.
[Nook Color Android Development] chisleu:
I install nightlies from CWM. Only when I don't need to format anything though. Most nightlies can flash on top of nightlies.
[Nook Color Android Development] cybertimber2007:
Although this is true, you should get in the habit of formatting cache and davik-cache. Sometimes "dingleberries" get in there and cause problems in builds where such problems should not be! YMMV
[Nook Color Android Development] acme2ajax:
Hi All,

I am running CM7 via sd card.....

I was runing build 30 and updated to 31 as soon as it was released.

I have noticed a wifi error in the latest build.....

In build 31, I switched off wifi, as i wasnt using it and had to save battery life.

However, when i try to switch it on again ( after say 10-15 minutes, it doesnt connect. The Wifi option shows error. I have to boot into emmc and then reboot to sd card for wifi to work again.

This problem doesnt occur in build 30. I was able to switch the wifi on successfully after 15 min.

Just wanted to provide some info.....as there are quite some wifi issues for nook color, and this is my addition to it :)
[Nook Color Android Development] chisleu:
Not having that issue and I turn mine off/on a lot. There have been a lot of reported problems (cycling, etc) but I've not had any of those issues at all. Maybe there are different hardware revisions? Wouldn't think so, but you never know.
[Nook Color Android Development] mr_fosi:
may we please have wifi ad hoc mode back?

I'm using the march 17 nightly and I use a WM mobile and the tethering mode is ad hoc. The usefulness of my encore has been radically diminished since I can't get web access when I am out and about.

Why was ad hoc removed? Does it conflict without other services? Can we have it back?
[Nook Color Android Development] chisleu:
I believe it was linked to poor wifi performance.
[Nook Color Android Development] jtbnet:
Problem being I've never really had problems with WIFI except releases where it was broken... with adhoc enabled it might take a wifi off/on to switch modes but that can be the case on most devices and once bacl on infrastructure my wifi had always been rock solid...

So I think the folks with wifi issues are having issues unlike;ly related to adhoc enabled, unless they are switching adhoc/infra/adhoc/infra frequently...
[Nook Color Android Development] RoboRay:
I never use ad hoc and all of the constant wifi cycling issues went away for me when ad hoc was disabled. That's a good enough reason to me for leaving it disabled by default. If you do need it, it takes maybe 30 seconds to turn it back on.
[Nook Color Android Development] lafester:
the problem was not easily fixed by cycling wifi on and off.

it would not connect at all requiring multiple wipes and reboots to fix only to have it come back again next time you turned on the device.

the problem was largely resolved with ad hoc removed however it did come back once. at that point i switched form wpa2 to wpa2-psk. so far so good and hoping to never see that wifi signal turning on and off by itself again.
[Nook Color Android Development] mr_fosi:
I figured that there was a reason that it was removed. Thanks for the info. :)

I thought that ad hoc support had been removed from the kernel. I'm very interested in learning how to turn ad hoc back on, if anyone is willing to give me a primer or point me in the right direction.
[Nook Color Android Development] newellj79:
Please excuse my ignorance but could somebody please explain what ad hoc is?
[Nook Color Android Development] painter_:
How about using the search feature. When I used it I found this thread. It tells you how to how to set up adhoc and switch between them.
[Nook Color Android Development] painter_:
This may help you understand. http://tinyurl.com/5s8lk73
[Nook Color Android Development] acme2ajax:
Hi Chisleu....

I am unable to understand hardware revisions....Do you mean that they did some revisions in the nightly 31 so that wifi now works?

I switched back to build 30 after build 31 failed in wifi for me....

So should i install build 31 again?

Regards
[Nook Color Android Development] norazi:
I am running nightly 13 or so with dalingrins OC kernel from back when nightly 13 was new.

if i wanted to flash the latest nightly (30?) do I need to flash the latest OC kernel on top?
[Nook Color Android Development] KitF:
Yes. Unless you don't want video or bluetooth to work.
[Nook Color Android Development] britoso:
is accelerated video playback perfect yet? (compared to froyo)
[Nook Color Android Development] fattymcdirty:
is there any eta for the "sleep of death"-bug? this one and the video playback make me think of switching back to froyo until they are fixed... :/
[Nook Color Android Development] RoboRay:
The first rule of CM is...