Open GoogleCodeExporter opened 9 years ago
Does anyone check this problem?
Original comment by michaelw...@gmail.com
on 31 Mar 2010 at 3:04
I know how to solve now, thank you.
Original comment by michaelw...@gmail.com
on 7 Apr 2010 at 2:02
How did you solve it?
Original comment by alexande...@gmail.com
on 17 Apr 2010 at 10:44
Hi michael,
How did you solve that Issue...?
Please reply....
Original comment by ckumar...@gmail.com
on 23 Jun 2010 at 7:38
He solved by using the alsa_amixer command to enable the capture device. Also,
need to create a symbolic link to alsa_arecord from alsa_aplay.
Original comment by bmcc...@gmail.com
on 13 Jul 2010 at 9:07
I m getting this error on using alsa_arecord,created by sym link to alsa_aplay
arecord: main:496: bad speed value 0
Original comment by mfasi...@gmail.com
on 13 Aug 2010 at 8:57
Hi ,
I am also trying the play the audio through the FAST TOOL , I am getting same
error :-
I/ ( 1060): [purpose] Playing STEREO sound with WIRED HEADSET (NORMAL
MODE) at 44100 Hz
I/ ( 1060): Opening the output stream
D/AudioHardwareALSA( 1060): openOutputStream called for devices: 0x00000004
D/ALSAModule( 1060): open called for devices 00000004 in mode 0...
D/ALSAModule( 1060): open called for device AndroidPlayback_Headset_normal
E/ALSAModule( 1060): status_t s_open device: Unknown error: -16
E/ALSALib ( 1060): external/alsa-lib/src/pcm/pcm.c:2201:(snd_pcm_open_noupdate)
Unknown PCM AndroidPlayback_Headset
E/ALSAModule( 1060): status_t s_open device: Unknown error: -2
E/ALSALib ( 1060): external/alsa-lib/src/pcm/pcm.c:2201:(snd_pcm_open_noupdate)
Unknown PCM AndroidPlayback
E/ALSAModule( 1060): status_t s_open device: Unknown error: -2
E/ALSAModule( 1060): Failed to Initialize any ALSA PLAYBACK device: Unknown
error: -16
Could you tell me how did you solve the problem ?
Original comment by narendra...@gmail.com
on 23 Nov 2011 at 10:12
Hi,
How to use that alsamixer command.
Can you please give me detailed steps to overcome that error.
My project is stopped due to that.
Original comment by Vvn2...@gmail.com
on 20 Jun 2014 at 6:56
Original issue reported on code.google.com by
michaelw...@gmail.com
on 29 Mar 2010 at 1:49