On Tue, Jan 31, 2012 at 4:01 PM, Dritan <[email protected]> wrote: > I am trying to create a low-level mapping where some button press on > my 22-button device is to be seen as left click, by following this > configuration: http://source.android.com/tech/input/key-layout-files.html > > I know Android is a flexible system and without rooting a device, it > is TOTALLY possible to create your own input device as a mouse + > keyboard + touchpad + braille + whatever kind of input you wish to > send to android. (NOT simulate keys, but actually send the > corresponding byes for "Left Click" or "Right Click" or "move > pointer").
Not at the SDK level. You mentioned that your device uses the Bluetooth HID profile. Find some existing Bluetooth mouse/keyboard/whatever that has the behaviors you want, and reverse-engineer how they're doing it through the Bluetooth HID profile. Or, follow the Bluetooth HID standards, which I am sure are written up somewhere. Or, visit http://source.android.com, click on the Community tab, find the right Google Group that might deal with hardware driver issues, and inquire there about their level of Bluetooth HID support. This Google Group is for development with the Android SDK. It is absolutely is not possible for an ordinary SDK application to inject input events to arbitrary applications on unrooted devices. That would represent a world-class security flaw. > Consider a professional artists who purchases a digital drawing pad > *with* a stylus pen for accuracy and all his/her drawings on the > drawing pad are directly sent to Android as legit mouse or stylus > events. This includes the pressure of the lines drawn as well, without > having to directly simulate each event. AFAIK, all of which would have be handled through the existing Bluetooth HID support, or possibly via patches to improve the Bluetooth HID support. > It just seems that not one Google employee seems to know about this. Oh, I am certain a few do. You will have better luck once you ask on a relevant list, one that would pertain to the functionality of the Bluetooth HID drivers. > books don't help (not one book dares touch on this topic). There is an Android internals book that I know of that is under development, but I don't know how much the author will go into Bluetooth profiles, let alone how much that will be useful to you. Heck, I don't even know when he'll get it done, though I've pestered him about it. > p.s. If I don't get a reply from a competent Google employee (or > really, anyone who's competent in this area), I shall re-post this > question with a different title, every single week. OMG! How will we cope? If only somebody had invented the email filter, so that we can block people who attack us with unwanted messages! Without this, we're doomed! Doomed, I say! -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy _The Busy Coder's Guide to Android Development_ Version 3.7 Available! -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
