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 ALSA... Thanks, Alvin Wong On 2月5日, 下午10時40分, Alvin Wong <[email protected]> wrote: > Hi there, > > I am trying to make ALSA sound work in Android, and now I managed to > make sound come out from the speaker, but it is just too loud. > > Actually sound isn't coming out automatically. I need to run `/system/ > bin/alsa_ctl -f /system/etc/asound.state restore` once (in > init.PLATFORM.rc), where `asound.state` is the dump of `alsa_ctl > store` in Angstrom. It seems that after running this command the sound > gets to maximum and *any* sound coming out just sounds terribly, both > internal speaker and headphone (if I plugged one in). > > In Angstrom I have `alsa_amixer` which displays a gui-like control > interface that I can set the sounds, and I know which controls get > modified by Angstrom's interface, so I tried modifying the `value` > values in `asound.state`, making the values lower, but it doesn't seem > to work. The sound is still that loud. > > So I wonder if I really need to run `alsa_amixer` *command line* in > Android in order to config the volume correctly, or are there any > other ways to do that? > > P.S. I uses Android 2.3.7 and the alsa-lib, alsa-utils and alsa_sound > comes from Android-x86. > > Please help, > Alvin Wong -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
