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
websi
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 f
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. Pr
After a make clean && make I obtain that at system startup.
D/AudioHardwareALSA( 1985): Mixer: element name: 'Master'
D/AudioHardwareALSA( 1985): Mixer: master 'Master' found.
D/AudioHardwareALSA( 1985): Mixer: route 'Master' found.
D/AudioHardwareALSA( 1985): Mixer: route 'Master' found.
D/Audio
Solved.
Use these info as guide for ALSA on x86.
Remember to make clean!
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
asound.conf must be fixed:
+device 0
-device 16
On 3 Giu, 13:36, Luca Belluccini wrote:
> Solved.
>
> Use these info as guide for ALSA on x86.
> Remember to make clean!
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http:
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,
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 ( 691):
external/alsa-lib/src/control/control.c:909:(snd_ctl_open_noupdate) Invalid
CTL AndroidPlayback
E/AudioHardwar
control.c @ line 909 what is trying to do?
On 4 Giu, 07:50, Nimit Manglick 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 ( 691):
> external/a
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 al
Yes. Can you post your conf? Did you placed asound.conf into /system/
etc/ ?
On 4 Giu, 15:23, Nimit Manglick 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, &ctl_conf);
> if (err
ALSA will NOT work unless you have a valid asound.conf customized for
your audio controls.
1. Use, "alsa_amixer contents" to get the controls and their values
2. Create asound.conf based on the above result
3. Put it in /system/etc/ folder in your Android-target and check.
On Jun 4, 6:23 pm, Ni
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 crashin
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
explicitely.
http://code.google.com/p/patch-hosting-for-android-x86-support/wiki/ALSA
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
-~--~~~~--~~--~--~---
Typo in your manifest file, twice alsa-lib as project path.
On Jun 12, 11:03 am, Luca Belluccini wrote:
> http://code.google.com/p/patch-hosting-for-android-x86-support/wiki/ALSA
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
websi
ty
On 12 Giu, 12:03, Androidphan wrote:
> Typo in your manifest file, twice alsa-lib as project path.
>
> On Jun 12, 11:03 am, Luca Belluccini wrote:
>
> >http://code.google.com/p/patch-hosting-for-android-x86-support/wiki/ALSA
--~--~-~--~~~---~--~~
unsubscribe:
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 wrote:
> 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
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 ps
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 wrote:
> Hi Androidphan.
>
> I can launch alsa_aplay -l and audio card is listed.
>
> Launching alsa_aplay file.mp3 and it tells me "unable to inst
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 wrote:
> Hi Androidphan.
>
> I can launch alsa_aplay -l
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/ServiceM
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 wrote:
> Hi Luca .
> Thanks your help.
> I have made "make cle
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 0
my sound works but i havent a good buffer size...
that what i did...
cd ~/mydroid/external
git clone git://android.git.k# chmod 0666 /dev/binder
# chmod 0666 /dev/ashmemernel.org/platform/external/alsa-lib.git
git clone git://android.git.kernel.org/platform/external/alsa-utils.git
cd ~/m
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 believ
Both alsa_amixer and alsa_play will not work.
I did not investigated about it, but the business is to get the card
recognized correctly by the ALSA layer.
Once you are sure of that and placed a first "stub" of alsa.conf, at
bootup you should see something in logcat notifying what is working
and if
28 matches
Mail list logo
