On Thursday 29 January 2009, TL Mieszkowski wrote:
Al Johnson wrote:
On Wednesday 28 January 2009, TL Mieszkowski wrote:
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be
convenient
TL Mieszkowski wrote:
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be convenient
to
pause media player to avoid bothering your neighboors. My other phone
behaves like that
I can see how having the sound info in a stack might be
useful (marginally, really), but I can't see it justifying
the use of D-bus. I wouldn't say never, but I really can't
think of any pressing reasons to want to know when the state
changes.
First example on top of my head : you
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be convenient
to
pause media player to avoid bothering your neighboors. My other phone
behaves like that and i find it convenient and
On Wednesday 28 January 2009, TL Mieszkowski wrote:
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be convenient
to
pause media player to avoid bothering your neighboors. My other phone
Al Johnson wrote:
On Wednesday 28 January 2009, TL Mieszkowski wrote:
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be
convenient
to
pause media player to avoid bothering your
Al Johnson wrote:
On Wednesday 28 January 2009, TL Mieszkowski wrote:
KaZeR wrote:
First example on top of my head : you are listening to music via your
headset, and you unplug it : if in a public place, it might be
convenient
to
pause media player to avoid bothering your
On Tuesday 27 January 2009, TL Mieszkowski wrote:
I'm not sure what the status of the Dbus sound stuff is, but I wrote a
little program to choose the alsa state file with a simple gui. Attached is
the code in anyone is interested. All it is is 1 button for each state
file, very simplistic,
Al Johnson wrote:
The FSO API can list and change the alsa scenarios with stack based
management. It will also send a signal on scenario change so that
interested
apps are aware of it. See:
WM8753.pdf pg 27:
MICBIAS CURRENT DETECT
The WM8753L includes a microphone bias current detect circuit which allows
the user to set
thresholds for the microphone bias current, above which an interrupt will be
triggered. There are two
separate interrupt bits, MICDET to allow the user to e.g.
On Wednesday 28 January 2009, TL Mieszkowski wrote:
WM8753.pdf pg 27:
MICBIAS CURRENT DETECT
The WM8753L includes a microphone bias current detect circuit which allows
the user to set
thresholds for the microphone bias current, above which an interrupt will
be triggered.
I think this
Al Johnson wrote:
I think this appears as /dev/input/eventX and should be available in
FSO's
rules.yaml if it isn't available as a direct notification.
Cool, thanks Al
--
View this message in context:
http://n2.nabble.com/Alsa-state-chooser-tp224p2229815.html
Sent from the
12 matches
Mail list logo