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
