[QTExtended] cannot store alsa state
openmoko at mazikeen.demon.co.uk
Thu Dec 18 14:12:01 CET 2008
I'm not certain on QTExtended, but /usr/share/openmoko/scenarios/ is the usual
location on most of the distros. You can use any filename you like, but the
applications will only use the filenames they expect. I don't know if these
are configurable or hardcoded in QTExtended. The names should be fairly
self-explanatory when you see them in the directory. The phone will probably
spend most of its time using stereoout.state so that the ringtone or music
playback happens through the speaker. When you pick up a call the dialler
will switch it to gsmhandset.state, and back to stereoout.state when you hang
up. It may use headset.state and gsmheadset.state if the wired headset is
plugged in, or gsmstereoout if the speakerphone setting is used.
To use a state file manually run:
alsactl -f /path/to/file.state restore
On Thursday 18 December 2008, Giorgio Marci wrote:
> Where are stored these files? there is a specific file state to store or
> can i store any file in any directory? and if yes, how can i set alsa to
> use that particular file?
> ----- Original Message -----
> From: "Al Johnson"
> To: community at lists.openmoko.org
> Subject: Re: [QTExtended] cannot store alsa state
> Date: Thu, 18 Dec 2008 11:58:50 +0000
> On Thursday 18 December 2008, Giorgio Marci wrote:
> > I adjust the volume on QTExt 4.4.2 using alsamixer and then i'd
> like to
> > store its state, but the command
> > alsactl -f path_to_file.state store
> > doesn't seem to work and, after that i make or receive a call, the
> > returns to default!
> > How can i save the alsa state permanently?
> The command looks correct, but you need to give it the right path and
> for the state you are trying to modify. You could always take a copy
> of the
> file before and after, and diff them to check your changes have been
> saved. I
> assume you know there are multiple state files that the applications
> switch between as required.
> Openmoko community mailing list
> community at lists.openmoko.org
More information about the community