The IOIO for Android that I recently purchased has shown up!!! I haven’t had time to play with it or even know much about how to start playing with it, but I will be figuring it out quickly. If you’re not sure what it is, a quick description from their website is:
The IOIO (pronounced “yo-yo”) is a board specially designed to work with your Android 1.5 and later device. The board provides robust connectivity to an Android device via a USB or Bluetooth connection and is fully controllable from within an Android application using a simple and intuitive Java API - no embedded programming or external programmer will ever be needed!
So setup as it’s default use, it’s not using the new Google Open Accessory (ADK) protocol, which is what I really want to develop with once I get far enough along in Android programming and being able to do some prototypes on the board. I figure once I get far enough along, that I’ll be turning on blinking LED’s, and from there the worlds the limit, even though I do know what I want the end result to be with it.
The bad news at this point is that the ADK firmware on it is still very beta. Even to update the device, I need a PIC programmer capable of programming PIC24FJ128DA206. So that means until it comes out of beta, I can’t use it for the ADK protocol or I ask some EE friends if they have one laying around. Even if I take the friend route to update it to the beta, it still has the following problematic caveat:
Due to problems with the accessory library implementation (i.e. the Android OS code supporting the protocol) – the IOIO connection will not be properly closed when pausing (and exiting) your IOIO app. When the app is resumed (restarted) it will hang. The current workaround is to physically disconnect and reconnect the IOIO (or power-cycle it).
This is because of a problem in the Android OpenAccessory library preventing the app from gracefully closing the ADK connection. To work around this problem, detach and re-attach the IOIO when that happens (or power-cycle it). Another option is to force-close the app.
Not something that I would call usable in a real life situation. Hopefully it does get resolved though. At this point though, since my original plan is for a single use at this point, if all else fails, I’ll just use their implementation of the communication protocol for the initial project. Either library I use in the end, both will be good learning experiences on making and developing for new accessories to work with Android.