We have successively implemented an app that talks directly to an FTDI chip over USB on an Android 3.1 Tablet (Acer A500) using this code: http://android.serverbox.ch/?p=370
Note that the Samsung Galaxy Tab 10.1 (as of the 3.1 update - trying 3.2 now) lacked some component of the USB structure that allowed random devices to be enumerated. The OS sees a mouse, keyboard, hub, and mass storage device, but everything else it is supposed to expose to apps using the new APIs. A simple test app that shows all USB devices works great on the Acer but fails to show anything on the Galaxy Tab 10.1 with the 3.1 update. Good luck. I only saw this message by accident as I never check this anymore, so if you ask a question and I don't respond, shoot me a reminder direct and I'll check the mailing list message and respond there (so everyone can still see). -Taylor On Tue, Nov 15, 2011 at 4:44 AM, MartyMoose <[email protected]>wrote: > Do you think this would help? > > http://slickdevlabs.com/slick-usb-2-serial-library/ > > > On Nov 14, 9:50 pm, RLScott <[email protected]> wrote: > > By the way, our workaround solution was to abandon the USB-serial > > converter and instead use a Bluetooth-serial module, like the RN-24 > > from Roving Networks. The Bluetooth route is quite doable. > > -- > 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 > -- 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
