I have been using a work around for a problem when having a 4800 Baud and a 19200 Baud input connected. The problem was that the ADB protocol stalled.
The workaround was to hard restart the IOIO from the Android app. But additions I made in the IOIO firmware (causing a longer lasting reboot) made this restarting anoying. Using a Dell Streak 5, I had to upgrade it to Android 2.3.7 (the latest I could find for the Streak) in order to use Android Open Accessory. But it was worth the trouble. I have had no stalls after this :-) Have had it running for a couple of days with a 57600 Baud stream without problems. When using ADB this would have provoked a stall within minutes, or half an hour at most. (And I have verified with a frequency counter that the USB clock adjustment is at the optimum). But now a question regarding the AOA implementation: My Android application "linked" with the IOIOLibAccessory works on the Streak (out of debug mode), but if I try to use Microchip's BasicAccessoryDemo on the same Streak, it is unable to find the com.android.future.usb library. This is strange, because it must be there for the IOIOLibAccessory to work. So does the IOIOLibAccessory do something special to find this package? -- You received this message because you are subscribed to the Google Groups "ioio-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/ioio-users. For more options, visit https://groups.google.com/d/optout.
