All, I'm looking at getting the Wacom w8001 driver fully functional under Android, and have run into a few issues with Gingerbread. With Honeycomb and Ice Cream Sandwich being more tablet-oriented, I'm hoping that at least some of these issues have been resolved. However, since the source isn't available I can't answer the questions on my own. Googling hasn't turned up much information either, so hopefully someone here can give me a few useful nuggets of information :)
I see that ACTION_HOVER_MOVE was added in API level 12. This is wonderful news, but without documentation on what kernel events need to be sent, impossible to make use of. I'm guessing that Android now checks for BTN_TOUCH > 0 from the kernel before declaring a pointer "down". Is this correct, or does some other event trigger the pointer as being down (e.g. ABS_MT_PRESSURE > 0)? Calibration of pen position is another issue that I've run into under Gingerbread. I understand that in most cases it is unnecessary: your finger can only be placed with so much accuracy. A few pixels of error is entirely reasonable given the physical size of your finger. However, a few pixels of error is not so reasonable when a stylus is being used for precision work. While Gingerbread supports some calibration via its 'idc' files (which calibrate touch size, pressure, etc), position calibration is notably absent. Workarounds exist, but I would hope that a solution has been integrated into Android by now... Does anyone know if this is the case? A third issue concerns the use of stylus buttons and tip vs. eraser data. This information is being sent from the driver, but Android is completely oblivious to it. between EventHub.cpp and InputReader.cpp, the button and tool events are being completely ignored (except, of course, BTN_TOUCH). Additionally, the Android API is not set up to accommodate this kind of information. In addition to the work it's going to take to get Android to stop dropping these events, I'll need to figure out some way to extend (or cleverly use) the Android API. Any ideas? What's involved with getting Google to extend the official API? Finally, just how do I go about doing development work for Ice Cream Sandwich? The source is unavailable, and it seems the best I can do is to make patches against Gingerbread. Unless Google is integrating these patches into Ice Cream Sandwich themselves, I'm failing to see how I can properly develop, build, and test against a missing codebase. Jason --- Day xee-nee-svsh duu-'ushtlh-ts'it; nuu-wee-ya' duu-xan' 'vm-nvshtlh-ts'it. Huu-chan xuu naa~-gha. -- You received this message because you are subscribed to the Google Groups "Android Discuss" 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-discuss?hl=en.
