Hello,
I am not sure if this would be the rite place to post my doubt,
Actually i am working on ALSA (Blaze board), i am not able to understand
how the set the various audio paths using ALSA.
In the alsa files in mydroid folder,
"mydroid/hardware/ti/omap3/modules/alsa/ " there are files dealing with ALSA
where they are using "plughw:0,0" kind of terminology for few of the devices
like FM, Bluetooth etc...Can anyone explaind what actually "plughw:0,0" term
means....
Thanks in advance for ur help
Sarika
On Tue, Aug 9, 2011 at 1:06 AM, Chris Stratton <[email protected]> wrote:
> On Monday, August 8, 2011 2:10:16 PM UTC-4, Anil wrote:
>>
>> I work for an OEM and am trying to implement an idea - to log all
>> inputs (keystrokes,
>> text field input, browser tests including Javascript, plugging/
>> unplugging SD card etc.) by the testers to have a set of trails that
>> would be useful. I want to do a custom build.
>> So I am trying to figure out the minimal set of points in the
>> framework code at which I can log "this text was input", "this key was
>> pressed". Does such a tool to log trails already exist?
>>
>
> Two "choke points" I can think of would be that it likely comes from two
> kernel drivers (physical buttons and touches) and most likely at some point
> all goes through Binder (though in a very implementation-private manner).
> It may be better to really understand and instrument each mechanism in the
> framework code though.
>
> Converting touch coordinates to drawn controls is going to be tricky - for
> those drawn using framework widgets it's possible, but there's nothing to
> keep an app from doing its own coordinate-to-button conversion. For games
> based on physics engines I'd expect a lot of that.
>
> --
> unsubscribe: [email protected]
> website: http://groups.google.com/group/android-porting
>
--
SarikA
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
