Hi again,
Well I just found that before starting service media (stopped
actually) and run alsa_ctl store, the mixer values are what I've set.
But after starting media, the mixers goes to their maximum values. Is
there a way to solve?
It makes me wonder that I am missing something in managing
Thanks Glenn,
On 27 August 2011 04:32, Glenn Kasten gkas...@android.com wrote:
Some (but not all) Android devices do have ALSA kernel drivers. But
even for those devices that do have ALSA in the kernel, the
AudioFlinger part of mediaserver generally takes over the audio
output. So in short,
On Jul 28, 12:29 pm, Diego diego.rond...@kynetics.it wrote:
Next problem I get (yeah, not finished yet!) is a buffer overflow
issue in AudioFlinger which prevents audio recording to succeed.
Inspecting the code I found out that disabling the second condition of
the if in
On Jul 23, 3:45 pm, amr.has nourha...@hotmail.com wrote:
so the problem is in change SND_PCM_STREAM_CAPTUR by
SND_PCM_STREAM_PLAYBACK ??
can u explain more details about this solution
I hadn't found the solution at the time; I've found it recently.
In openInputStream method (donut branch
so the problem is in change SND_PCM_STREAM_CAPTUR by
SND_PCM_STREAM_PLAYBACK ??
can u explain more details about this solution
thanks
amr hassan
On Jul 22, 4:42 pm, Diego diego.rond...@kynetics.it wrote:
On Jul 19, 4:16 pm, Diego diego.rond...@kynetics.it wrote:
Another step: I found out I
On Jul 19, 4:16 pm, Diego diego.rond...@kynetics.it wrote:
Another step: I found out I can use busybox's fuser. I get:
# busybox fuser /dev/snd/pcmC0D0p
1788
# ps | busybox grep 1788
media 1788 1 17636 1212 afe0c51c S /system/bin/
mediaserver
So the pcmC0D0p is opened
On Jul 15, 6:18 pm, Diego diego.rond...@kynetics.it wrote:
On Jul 13, 6:38 pm, Diego Rondini diego.rond...@kynetics.it wrote:
I don't get while I see the err = ... line multiple times, and it's not
clear to me what's happening in this method. Can anybody help me?
Ok, found out some more:
On Jul 13, 6:38 pm, Diego Rondini diego.rond...@kynetics.it wrote:
I don't get while I see the err = ... line multiple times, and it's not
clear to me what's happening in this method. Can anybody help me?
Ok, found out some more: the err = ... line is present several times
because the
On 14 Lug, 01:56, Ashwin Bihari abih...@gmail.com wrote:
If you are starting a port to a new board, why are you starting with
such an old version of Android? You should start with Gingerbread and
at the worst FroYo..
The device I'll use isn't powerful enough to run Froyo smoothly, it
has just
Any success with this problem?
Please, some info about result.
On 15 сен, 06:19, ani anish198519851...@gmail.com wrote:
http://alsa.opensrc.org/index.php/.asoundrc
If you don't understand anything do let me know about it or you can
ask alsa mailing list.
On Sep 14, 7:18 pm, Yogesh Sharma
Hi
My Observations -
Audio players read /system/etc/asound.conf or ~/asoundrc file to get the
hardware info. I was not having these files, so player was sending output
stream to default device (which was midi in my case). So player was working
fine but I was not getting any sound. I Created
http://alsa.opensrc.org/index.php/.asoundrc
If you don't understand anything do let me know about it or you can
ask alsa mailing list.
On Sep 14, 7:18 pm, Yogesh Sharma mails.yog...@gmail.com wrote:
Hi
My Observations -
Audio players read /system/etc/asound.conf or ~/asoundrc file to get
Its playing sound properly, actually my asound.conf was not proper as
I am using external audio driver.
On Sep 13, 8:21 am, ani anish198519851...@gmail.com wrote:
check from where are these logs coming unable to attach.
I think your kernel has not created properly your device files for
2010/9/13 yogi mails.yog...@gmail.com
Its playing sound properly, actually my asound.conf was not proper as
I am using external audio driver.
Hi yoji,
would you please show us what exactly the root cause? I want to check
whether it's the same problem with mine.
--thanks
wxc200
On Sep
check from where are these logs coming unable to attach.
I think your kernel has not created properly your device files for
mixers.
In case it has not then you need to first fix that or you can get help
from alsa mailing list(Very good group and they reply most of the time
if your question is
Hi,Misa
1.
I have wm8987 driver for my board,my kernel version is 2.6.24.7
supplied by the board vendor ,and I have porting the android driver to
it,before porting the alsa ,I can run eclair well ,wifi ,phone module
etc can work well.
and here are my .config file in the kernel root dir
1313 #
Hi,
Could you give me some clue?
look at the strace log:
1399 mmap2(NULL, 4096, PROT_READ, MAP_SHARED, 11, 0x8) = -1
ENXIO(No such device or address)
The first address is NULL,why?
Is this the error from the mediaserver src or alsa src or they are
not compatible in eclair?
Thank you
--Weber
Hi,
I still have a question :If alsa are not added to the system ,are
there other solutions to make the system generate sound ?Is alsa the
only way?
Thanks
--Weber
On Jul 26, 10:53 pm, Weber qvbs...@gmail.com wrote:
Hi,everyone
I now want to porting alsa to eclair.My board are smdk6410,the
I found the way to solve this may not proper.
copy libgstaudioflingersink.so to your plugin path with alsa and than
try
gst-launch-0.10 -v audiotestsrc ! audioconvert ! audioresample !
alsasink
it will work.
if it shows the device is busy than
do
stop media
Regards,
Nilly
On Jun 22,
yes im aware alsa needs the nodes in that folder which would be fine
for one of the devices i am developing for (nokia n810) whoes audio
codec creates said files but the other device - nokia n800 does not as
although alsa detects the audio system it does not create pcm devices
as i think
Your sound device nodes must appear in /dev/snd/,
the Android's init creates them in that dir.
Or you must have troubles.
BTW, the modern alsa lib doesn't need asound.conf
anymore. So don't bother about it.
On 3月21日, 上午5時15分, DJ_Steve steve103...@gmail.com wrote:
hello,
my first post here, im
possibly but scurrently i have discovered that it appears the devices
i am attempting to port to need to use dsp to access sound, i have the
dspgateway kernel modules inbuild but i cannto get the alsa dsp plugin
to load i get errors repeatedly giving errors during loading xx .so
file.
any ideas
Can you check logcat messages for this:
Settings Sound display Phone ringtones
One more question,
I have sound files in system/media/audio, but only 'Silent' shows on
Settings Sound display Phone ringtones.
How to show sound files here?
--
unsubscribe:
/system/media/audio/ringtones check here...if your files are present
or not.
If present then it should be listed in your settings as well.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
To unsubscribe, reply using remove me
/system/media/audio/ringtones check here...if your files are present
or not.
If present then it should be listed in your settings as well.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Hi,
The error
aplay: main:590: audio open error: Device or resource busy
is because the alsa is being used by media server, hence you need to
stop it using
#stop media
Then run
#alsa_aplay
On Mar 31, 5:37 am, abukustfan abukust...@gmail.com wrote:
Thanks ani!
I can get my sound when
Hi Srikant,
Yes, I tried it yesterday and it works!
Thanks
On Apr 1, 12:57 pm, Srikant w.sreeka...@gmail.com wrote:
Hi,
The error
aplay: main:590: audio open error: Device or resource busy
is because the alsa is being used by media server, hence you need to
stop it using
#stop media
Thanks ani!
I can get my sound when playing video now, but alsa_play still not
working.
This time it complaint
# alsa_aplay
aplay: main:590: audio open error: Device or resource busy
One more question,
I have sound files in system/media/audio, but only 'Silent' shows on
Settings Sound display
Hi,
I use the original media player from AOSP android-2.1_r1 branch and
add external/alsa-lib, external/alsa-utils, hardware/alsa_sound from
master branch.
HAVE_HTC_AUDIO_DRIVER := false
BOARD_USES_GENERIC_AUDIO := false
BOARD_USES_ALSA_AUDIO := true
BUILD_WITH_ALSA_UTILS := true
was defined in
Hi Srikant,
It still shows the same error with following commands.
# stop media
# alsa_aplay -D hw:0,0 sample.wav
ALSA lib external/alsa-lib/src/confmisc.c:143:(snd_config_get_bool)
Invalid type for nonblock
ALSA lib external/alsa-lib/src/pcm/pcm_hw.c:1445:(_snd_pcm_hw_open)
Invalid type for
Hi all,
I added a debug code in alsa-lib and I got below message at boot.
D/( 644): '/dev/snd/controlC0' open failed with mode '2'.
(external/alsa-lib/src/control/control_hw.c:391)
D/( 644): '/dev/snd/controlC0' open failed with mode '2'.
try with this alsa_aplay -D hw:0,0 Dil_Vil.wav some.wav
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
To unsubscribe from this group, send email to
android-porting+unsubscribegooglegroups.com or reply to this email with the
Hi,
It shows below error.
# alsa_aplay -D hw:0,0 sample.wav
ALSA lib external/alsa-lib/src/confmisc.c:143:(snd_config_get_bool)
Invalid type for nonblock
ALSA lib external/alsa-lib/src/pcm/pcm_hw.c:1445:(_snd_pcm_hw_open)
Invalid type for subdevice
aplay: main:590: audio open error: Invalid
I think your media player which you mentioned was playing some music
will not be able to play if alsa_aplay itself is not working.
Because your device itself is not opening.
Is your media player using some other driver other than alsa
--
unsubscribe:
Hi,
Try doing:
#stop media
before alsa_aplay.
-
On Mar 26, 12:08 pm, abukustfan abukust...@gmail.com wrote:
Hi,
It shows below error.
# alsa_aplay -D hw:0,0 sample.wav
ALSA lib external/alsa-lib/src/confmisc.c:143:(snd_config_get_bool)
Invalid type for nonblock
ALSA lib
It would be better if you ask alsa mailing list these questions.
# alsa_amixer -c 0
# alsa_aplay -l
shows my devices info correctly.
Check whether your device nodes are getting created or not.
It should be
/proc/asound/card0/pcm0P -Playback device
/proc/asound/card0/pcm0C -Capture device
If
After I modified some codes in alsa-lib, no more Invalid type for
card error from logcat.
but below message shows.
--
I/ServiceManager( 677): Waiting for sevice
media.audio_policy...
W/AudioSystem( 677): AudioPolicyService not
libasound_module_rate_speexrate.so is an alsa plugin which needs to be
downloaded.
aplay runs because it works directly above your driver layer i.e. your
driver supports 8k playing.
Whereas libasound_module_rate_speexrate.so is loaded by the platform
code.
Try downloading this file.
--
I guess your asound.conf file doesn't match your drivers.
Please google for this file and details.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
To unsubscribe from this group, send email to
I moved my hooks to asound.conf unfortunately without a change on the
behaviour.
an example out of the asound.conf:
pcm.AndroidPlayback_Speaker_normal {
type hooks
slave.pcm {
type hw
card {
@func refer
I tried to make a hook in alsa.conf. Is this the right place for it?
It should be 'asound.conf', you can check below link for
reference:http://git.omapzoom.org/?p=platform/vendor/ti/zoom2.git;a=blob;f=asou...
alsa.conf loads asound.conf if I understood that right.
But does it mather if I
Hi, All:
Based on Sean's answer, we must do mixing in Android, low level dmix/
dsnoop cannot be supported anymore.
Now, I have to run a existed library with Android UI, which need
access ALSA device, but integrate it into Android is complex. And,
maybe I can not get the source code, only binary.
On 01/18/2010 05:27 PM, ani wrote:
The pcm_dmix.c is not compiled in the Android alsa lib.
I have compiled this c file and DMIX is working for me.
My questions are still the same:
a.Can we use the ALSA mixer(DMIX-i enabled in my system) for mixing
streams instead of android mixer?If yes
No, dmix requires posix shared memory and Android doesn't support it.
This (http://gitorious.org/android-on-freerunner/platform_bionic/
commit/f7fc4a3c25d71017f8327563d182396e35a259cd) is the change which
we need to do to enable shared memory in android and then we need to
back port some changes
Answer From Sean McNeiL:
The simple answer to your questions below is that POSIX shared memory
will not be supported by Google, so this is all moot. The commit
mentioned below will most likely never be accepted by Google. You can
use the dmixer support if you like, but you'll have to do a number
Hi,
I still not getting the sound and I m clueless to proceed further .
Inlined below is the log message for audio application
W/HAL ( 972): load: module=/system/lib/hw/copybit.omap3.so
error=Cannot loa^M
d library: load_library[984]: Library '/system/lib/hw/
copybit.omap3.so' not foun^M
Hi All,
Audio is working in Android, After intergrating the donut alsa
in Android it was working, In my earlier post it was due to the
hardware fault for not working.
Regards
Fasil
On Dec 14, 8:15 pm, Fasil mfasi...@gmail.com wrote:
Hi,
I still not getting the sound and I m
Hi
here are the contents of the alsa_amixer controls command
alsa_amixer all controls
numid=5,iface=MIXER,name='Master Mono Playback Switch'
numid=6,iface=MIXER,name='Master Mono Playback Volume'
numid=1,iface=MIXER,name='Master Playback Switch'
numid=2,iface=MIXER,name='Master Playback Volume'
The hardware is AC97
The asound.state states it as WM9705WM9710.
Thanks.
On Oct 13, 3:44 pm, Claw praveengudisa...@googlemail.com wrote:
Hi
here are the contents of the alsa_amixer controls command
alsa_amixer all controls
numid=5,iface=MIXER,name='Master Mono Playback Switch'
mixer controls are dependent of your hardware (not mentioned). You
should have some controls to specify active output path (like a mux)
or to enable speaker output (when hardware can route same audio to
different outputs). Do 'amixer controls', names are usually
self-descriptive.
-Misa
The prototype of AudioHardwareALSA::openInputStream is changed.
The derived class in hardware/alsa_sound/ needs to be updated.
I believe this such a problem has been fixed at least one month ago.
I don't understand why you still encounter it.
Make sure you have synced the latest code.
On 9月23日,
nobody knows how to set the buffer size???
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
Hi Luca .
Sorry to bother you again.
My sound still not work.
I has used alsa_aplay command to play a mp3 file or wav file but it
doesn't work.
# alas_aplay -f cd /data/123.mp3
# Playing raw data '/data/123.mp3': signed 16 bit Little Endian, Rate
44100 Hz, Stereo.
And launching alsa_amixer -c
One wild guess is alsa_amixer might be segfaulting because of lack of
ncurses support (Not sure though). Default argument to alsa_amixer is
'controls' which should show up an ncurses based interface.
But, it should not prevent ALSA from working properly. Double check your
asound.conf, if you
there are 2 of these structures defined in
hardware/alsa_sound/AudioHardwareALSA.cpp. Look for
static StreamDefaults _defaults
one is for playback, and one for record. You are interested in the one
for playback. There are 2 things that are meaningful for this issue in
this structure: latency
thanks for reply.
static StreamDefaults _defaults = {
devicePrefix : AndroidRecord,
direction : SND_PCM_STREAM_CAPTURE,
format : SND_PCM_FORMAT_S16_LE, //
AudioSystem::PCM_16_BIT
channels : 1,
sampleRate :
Check it in, android-src/hardware/alsa_sound/AudioHardwareALSA.cpp file.
You may try with a value of 768 for the buffer-size.
There is an InputStream class and an OutputStream class. set the value for
buffer-size there.
On Mon, Jun 22, 2009 at 7:50 PM, xro romanen...@hotmail.com wrote:
hi.
Is it possible to set the buffer size?
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
when i look my proc i have that:
cat /proc/asound/cardX/pcmXY/subX/prealloc
8
cat /proc/asound/cardX/pcmXY/subX/prealloc_max
8
so it says that the max buffer is 8k. rigth?
so what can i do?
--~--~-~--~~~---~--~~
unsubscribe:
On which platform are you?
Try to get inspired by
http://patch-hosting-for-android-x86-support.googlecode.com/files/asound.conf,
changing controls (you can get them by alsa_actl store)
On 19 Giu, 08:54, xro romanen...@hotmail.com wrote:
i'm really noob in sound...
how can i create i good
Exactly what happened to me:
I have been struggling on it for 2 weeks!
A very strange error happened: it was printing an error but not
printing a test printf I placed in a code section which MUST be
executed.
On 19 Giu, 05:03, ehung ehung1...@gmail.com wrote:
Hi Luca .
Thanks your help.
I
thanks for reply...
i'm on a APF27 plateforme... It's based on ARM processor. So Androids
works... I just have to fix the sound...
If i understand i have to begin with
ctl.AndroidPlayback {
type hw
card 0
}
ctl.AndroidRecord {
type hw
card 0
}
And after
i did the alsactl store and that build a asound.state
i have to transform asound.state in asound.conf?
and how?
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
You can try and look at the sample that Luca Belluccini gave you. It's
not that hard if you tried.
On Jun 19, 11:39 am, xro romanen...@hotmail.com wrote:
i did the alsactl store and that build a asound.state
i have to transform asound.state in asound.conf?
and how?
In each
{ name 'Speaker Playback Switch'value
[ true true ] }
{ name 'Line-Out Playback Volume' value
[ 64 64 ] }
{ name 'Line-Out Playback Switch' value
[ true true ] }
{
In asound.state you'll see all kind of controls.
They all have a name and a value.
You need to put the names and values in your asound.conf
On Jun 19, 11:49 am, xro romanen...@hotmail.com wrote:
It's easy for you but not for me...
I try to fix the sound since 2 days
How can i know what
You know how to do. So could you give me just an exemple that would be
great...
i give you my asound.state. Can you just put the first lines of
asound.conf... I hope i will be able to understand...
state.IMX-ALSA {
control.1 {
comment.access 'read write'
I tried to do my asound.conf
Someone could say me what is wrong
ctl.AndroidPlayback {
type hw
card 0
}
ctl.AndroidRecord {
type hw
card 0
}
pcm.AndroidPlayback {
type hooks
slave.pcm {
type hw
card 0
thanks for ur help...
should i do like that? (for each)
hook_args [
{ name 'Master Playback Volume' value.
0 64}
{ name 'Master Playback Volume' value.
1 64}
{ name 'Master
What is this error?
E/AudioHardwareALSA( 1912): Unable to set buffer size to 16384:
Invalid
argument
someone knows it?
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
Remember to set the system properties on init.rc files
On 19 Giu, 14:05, xro romanen...@hotmail.com wrote:
What is this error?
E/AudioHardwareALSA( 1912): Unable to set buffer size to 16384:
Invalid
argument
someone knows it?
--~--~-~--~~~---~--~~
thanks for help...
i put this properties for the sound:
setprop alsa.mixer.playback.master Front
setprop alsa.mixer.capture.master Capture
setprop alsa.mixer.playback.earpiece Master
setprop alsa.mixer.capture.earpiece Capture
setprop alsa.mixer.playback.headset Master
i finally found my error...
it was in the AudioHardwareALSA.cpp...
there is a bug with the buffer Now i comment the test in line
606... It works
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:
thanks for response...
Are you sure? i did a chmod -R 777 /dev and chown -R root audio /dev/
snd and it's always the same...
i think that is because of the alsa lib!
do you know something?
--~--~-~--~~~---~--~~
unsubscribe:
You can add the following to system/core/init/devices.c to
automatically set the correct permissions.
{ /dev/snd/, 0664, AID_SYSTEM, AID_AUDIO, 1 }
On Jun 18, 8:09 am, xro romanen...@hotmail.com wrote:
thanks for response...
Are you sure? i did a chmod -R 777 /dev and
i did it but i always have error... Why?
when i boot:
[42949564.78] snd_imx_pcm_open Playback stream @:
0xd39cbb00
[42949564.78] imx_ssi_get_dma_tx_channel =
13
[42949564.79] playback
supported
[42949568.21] snd_imx_pcm_open
Hi Luca .
Thanks your help.
I have made make clean and make again.
The libraries seems to link correctly.
Because I got the some log information about alsa before I have never
seen.
The log message is showing below.
..
I/ServiceManager( 2106): service 'media.audio_flinger' died
I'm guessing that the files in /dev/snd/ doesn't have the right file
permissions.
On 17 jun, 19:38, xro romanen...@hotmail.com wrote:
hi,
i'm porting android an a apf27 plateform... It works...
But there is no sound... So i installed the ALSA lib and compiled...
Now i can't boot android...
Hi Luca.
I have follow your tips on wiki to implment alsa function.
I have built the libaudio.so, alsa_ctl, alsa_amixer and alsa_aplay on
android system.
I use a aplayer application to test the alsa function, but the audio
still not work.
Could you give me some suggestion?
Thank in advance.
If you give some more information on your soundcard, errors, logcat
etc.
We can't do anything with more information.
On Jun 16, 9:22 am, ehung ehung1...@gmail.com wrote:
Hi Luca.
I have follow your tips on wiki to implment alsa function.
I have built the libaudio.so, alsa_ctl,
Hi Androidphan.
I can launch alsa_aplay -l and audio card is listed.
Launching alsa_aplay file.mp3 and it tells me unable to install hw
params.
Launching alsa_amixer -c 0, it has show some information below.
Simple mixer control 'Master' ,0
Capabilities: pvolume pvolume-joined
E/MediaPlayer: Unable to to create media player.
It seems a MediaPlayer issue, not ALSAAudio.
Issues are at high floors =)
On 16 Giu, 10:52, ehung ehung1...@gmail.com wrote:
Hi Androidphan.
I can launch alsa_aplay -l and audio card is listed.
Launching alsa_aplay file.mp3 and it tells me
Alsa amixer will not work correcly.
Never worked.
Remember that if you built before without ALSA support, do a
$ make clean
There's something wrong in build phase: without clean libraries are
not linked correctly.
On 16 Giu, 10:52, ehung ehung1...@gmail.com wrote:
Hi Androidphan.
I can
Typo in your manifest file, twice alsa-lib as project path.
On Jun 12, 11:03 am, Luca Belluccini lucabellucc...@gmail.com wrote:
http://code.google.com/p/patch-hosting-for-android-x86-support/wiki/ALSA
--~--~-~--~~~---~--~~
unsubscribe:
Hi Luca,
I have checked out alsa-lib, alsa_sound from android git, and it doesn't
generates any file with the name asound.conf , it generates alsa.conf in
system/usr/share/alsa.conf (I cross checked Android.mk file ) which I copied
in system/etc with the name asound.conf. But the system is
Alsa build doesn't include or create asound.conf file. You have to put one
by yourself and alsa.conf is different from asound.conf. If you are sure
about the alsa device files getting created with proper permissions
(/dev/snd/*), you can try alsa_mixer with -c option giving card number
control.c @ line 909 what is trying to do?
On 4 Giu, 07:50, Nimit Manglick nimitandr...@gmail.com wrote:
I followed the steps... I checked out alsa-lib , alsa-utils and alsa_sound
from android git repository.
But The system is getting crashed on start up.
the logs are :-
E/ALSALib (
Its trying to look for soem configuration settings it seems teh code snippet
is as below :-
err = snd_config_search_definition(root, ctl, name, ctl_conf);
if (err 0) {
SNDERR(Invalid CTL %s, name);
return err;
}
plus the error its throwing from some config.c fiel also.
Yes. Can you post your conf? Did you placed asound.conf into /system/
etc/ ?
On 4 Giu, 15:23, Nimit Manglick nimitandr...@gmail.com wrote:
Its trying to look for soem configuration settings it seems teh code snippet
is as below :-
err = snd_config_search_definition(root, ctl, name,
Well, you need to have the following lines in BoardConfig.mk for ALSA
to be built:
BOARD_USES_GENERIC_AUDIO=false
BOARD_USES_ALSA_AUDIO=true
BUILD_WITH_ALSA_UTILS=true
Since, your BoardConfig.mk didn't have the BOARD_USES_GENERIC_AUDIO
set to false, it still is using stub audio which is like a
I did it. Here a mail I sent to some people involved in ALSA.
I successfully bring up Android on ASUS EeePc. Wifi, LAN, Keyboard are
working.
The last step is ALSA.
I enabled ALSA kernel support for it and specifically adding Intel HDA
support.
All sysfs and devfs nodes are created correctly.
Those error messages in system startup will vanish as soon as you put
a proper asound.conf file covering all the audio controls into /system/
etc directory. One way to write a asound.conf is to look at the output
of alsa_mixer contents command and writing the asound.conf
accordingly.
On Jun 3,
Addendum:
At init, there's a logcat message saying:
Using stubbed audio hardware. No sound will be produced.
But before it there's no additional error code or something similar.
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
HI,
I directly placed asound.conf file in
/cupcake/out/target/product/generic/system/etc and generated a image which
I flashed into board. My asound.conf file is mentioned below. Kindly give me
some pointers If there is any syntax mistake or any mistake I have done.
I am working on i.MX31 PDK
Thanks,
I appriciate if any relevent pointers given w.r.t my problem with ALSA.
Best Regards,
Rajesh
On Thu, May 21, 2009 at 2:39 PM, ssum...@gmail.com wrote:
check it out
http://www.sumitsaxena.mysite.com/
i need to ur help to improve this site .
On 21-May-2009
Rajesh,
The asound.conf you are using contains information of controls for
TWL4030 chip, and I think that´s not the one in your system. You need
to create a new asound.conf for your codec.
-Misa
2009/5/21 Rajesh N rajesh.andr...@gmail.com:
Thanks,
I appriciate if any relevent pointers given
Check your asound.conf file.. Its syntax may be wrong! Or you may post it
here so that the group can provide you some pointers.
On Wed, May 20, 2009 at 5:46 PM, Rajesh N rajesh.andr...@gmail.com wrote:
Hi All,
I have built android filesystem with ALSA downloaded from git, I
changed
Hi,
I had the same situation, you can try to use alsa_aplay -D device
-f formate music_file. If you don't know which device can use, please
use alsa_aplay -L, you will see ...
example for:
front:CARD=Intel,DEV=0
HDA Intel, ALC888 Analog
Front speakers
Hi,
Excuse me, what portion do need to post? I caught the log and
couldn't find any key about alsa, media etc.
BR,
On May 15, 2:54 pm, Androidphan niels.kee...@tass.nl wrote:
What are your errors on logcat?
On May 15, 4:03 am, xhor...@gmail.com xhor...@gmail.com wrote:
Hi All,
Do you have entries in /dev/snd ?
And what's in /proc/asound/cards ?
On May 15, 10:27 am, xhor...@gmail.com xhor...@gmail.com wrote:
Hi,
Excuse me, what portion do need to post? I caught the log and
couldn't find any key about alsa, media etc.
BR,
On May 15, 2:54 pm, Androidphan
1 - 100 of 140 matches
Mail list logo
