Should I open a ticket on FSO for this? On Thu, Dec 9, 2010 at 15:10, Dr. Michael Lauer <[email protected]> wrote: > Hi Daniele, > >> Greetings, >> sorry for the crosspost, but for this kind of post i guess it's better >> to post on every development list. >> >> I have a need to set idle state to PRELOCK as soon as a phone call >> ends. When the call ends, audio scenario is pulled, and soon after >> that idle state is forced to PRELOCK by my app. >> >> However, changing scenario seems to trigger idle state change to BUSY, >> so vanishing my attempt to force it to PRELOCK, or any other state. >> I could try to sleep for e.g. 2 seconds before forcing PRELOCK, but i >> don't think it's the right way to do this. > > For some reason writing an alsa scenario triggers activity on > an input node which in turn is responsible for moving to the BUSY state. > I wonder whether it's the headphone ctl? If so, we should attempt to > skip that – or fix it in the kernel driver... > > :M: > > >
-- Daniele _______________________________________________ Shr-devel mailing list [email protected] http://lists.shr-project.org/mailman/listinfo/shr-devel
