error when playing A2DP by alsa_aplay

by archerypp » Thu, 23 Jul 2009 19:52:31 GMT


Sponsored Links
 Hi, I want to use alsa_aplay to play A2DP.
After I finished connecting bt headset, I used the following command
and error occurred:
#alsa_aplay -Dplug:bluetooth /file.wav.
##ALSA lib external/alsa-lib/src/pcm/pcm.c:2201:
(snd_pcm_open_noupdate) Unknown PCM bluetooth
aplay: main:590: audio open error: No such file or directory

Have you ever meet this issue?
--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



error when playing A2DP by alsa_aplay

by pavan savoy » Thu, 23 Jul 2009 19:55:49 GMT


 how is the asoundrc file ?

does it have the pcm.bluetooth {
device XX:XX:XX:XX:XX:XX
}

regards,
Pavan






-- 
--Pavan Savoy

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


Other Threads

1. MapView Overlay that does always keeps an item selected?



Are you sure you want to do this? This goes against the standard behavior of
"deselecting" when clicking somewhere on the map (possible to remove a popup
or other obstructing view). But if you really want to...

But right now, whenever I tap on the map and not hitting a marker, the



Keep track of the last selected item. In onTap() if the currentFocus() is
null, setFocus() to the last selected item you saved. If it's not null,
update your reference.

You can also use the same idea but using the OnFocusChangeListener on the
ItemizedOverlay to determine if a new item has been focuses or not.

-------------------------------------------------------------------------------------------------
TreKing - Chicago transit tracking app for Android-powered devices
http://sites.google.com/site/rezmobileapps/treking

-- 

2. Broken Meshes / not synchronous while rendering GlSurfaceView

I haven't run into anything like that myself. I do often run into
issues that can cause the data to be incorrectly offset or otherwise
messed up, however, which might look similar.

The position of the buffer is important when you call glVertexPointer,
for example. So if the way you filled the buffer changed the position,
it has to be rewound or otherwise set back to where you want it before
you call glVertexPointer.

Another rough one was that in Android 1.5 putting an array into a
buffer using a non-zero offset into the array to start from doesn't
work. Works in later versions of Android, however.

Another issue is that the way the glVertexPointer call works is that
it doesn't consume the actual data. It is just setting the pointer to
the data. So changing the data before your other calls actually cause
it be used later on would cause trouble.




-- 

3. New sales have come to a halt Developer console stopped updating?

4. unable to bind to a service

5. Monkey Shines

6. selecting language from within the app rather than by locale of the system settings

7. Does Android support XGA (1024x768) resolution ?