There's nothing preventing code compiled against API 10 to run on an Android with API 9 as long as the code does not use any code that's not supported by 9. All the IOIO libraries know how to gracefully degrade when certain features they depend on are not available in runtime. The IOIOLibAccessory library needs to be compiled against a "Google-APIs" version of Android. I don't know what usb.jar is, but you don't need any such weird workarounds to get the code to build. Please refer to the Eclipse troubleshooting page on the wiki if you're seeing any build errors. You're over-complicating things: if you'll include both all libraries (IOIOLib, IOIOLibAccessory and IOIOLibBT) with your app you'll get seamless support for all modes without having to worry about it in your app. ADB (I guess this is what you mean by "ADK") mode does not work on newer Android devices (>= 4.2.2).
On Sun, Apr 27, 2014 at 7:03 PM, Paul McMahon <[email protected]>wrote: > OK, I'm able to build the sample app with API set to 18, but having lots > of trouble with API-10. In fact, my app needs to work down to API 8. I > tried importing the google APIs #10, and declaring the minSDKversion to 10, > using android library com.android.future.usb.accessory, adding usb.jar to > the build path, but still no luck. > > I'm thinking it'll be too much trouble to support accessory mode for newer > phones and ADK for older phones. Is there no way for me to use ADK mode > for all phones? > > thanks! > > > On Sun, Apr 27, 2014 at 3:52 PM, Paul McMahon <[email protected]>wrote: > >> Yes, that's what I'm doing now. Working through some build issues. >> >> - Paul >> On Apr 27, 2014 2:39 PM, "Ytai Ben-Tsvi" <[email protected]> wrote: >> >>> Put you app aside for a second. The next logical step would be to try to >>> build one of the sample apps from source yourself. Once that's working, >>> modify it to suit your needs. >>> Most likely, your app is missing IOIOLibAccessory and/or some manifest >>> declarations. >>> >>> >>> On Sun, Apr 27, 2014 at 10:47 AM, Paul McMahon <[email protected] >>> > wrote: >>> >>>> Thanks for the quick reply. That allowed me to run the sample >>>> application, but my own application still fails to detect the IOIO on this >>>> phone. My application is not based on the Android Open Accessory standard, >>>> but I understood that conversion wasn't strictly required. Do I need to >>>> update my app to get it to work on this phone? >>>> >>>> My hesitation is that my app needs to run all the way down to API 8, >>>> which is before OpenAccessory is supported. >>>> >>>> thanks >>>> >>>> >>>> On Sunday, April 27, 2014 12:42:49 PM UTC-4, Ytai wrote: >>>> >>>>> Upgrade the firmware. >>>>> On Apr 27, 2014 9:41 AM, "Paul McMahon" <[email protected]> wrote: >>>>> >>>>>> Hi, >>>>>> I came across this thread because I'm searching for the reason I >>>>>> can't talk to my IOIO with one of my phones. >>>>>> I've been using IOIO for nearly a year now, with an old android 2.3.7 >>>>>> phone. I now want to understand why I can't get it working with my new >>>>>> phone, running 4.3.1. The phone is a Samsung Galaxy S2X. >>>>>> >>>>>> On recommendation of this thread, I installed the precompiled >>>>>> IOIOSimpleApp.apk, and it's not working. When I connect the phone, it >>>>>> prompts for the openaccessory, which I accepted and made default. I'm >>>>>> unable to control the LED with the app. I've tried with and without the >>>>>> MTP mode set, and USB debugging. Nothing is working for me. When I >>>>>> connect IOIO with the cable, it auto-launches the IOIOsimple app. >>>>>> >>>>>> This IOIO was purchased within the last month. I'm not sure which >>>>>> firmeware is on it, but my test was with the precompiled binary from >>>>>> 0503. >>>>>> I figured surely this was a valid combination. >>>>>> Can you suggest next debug steps? >>>>>> >>>>>> thanks! >>>>>> >>>>>> >>>>>> -- >>>> 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. >>>> >>> >>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "ioio-users" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/ioio-users/hxXBw7pIsOw/unsubscribe. >>> To unsubscribe from this group and all its topics, 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. >>> >> > -- > 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. > -- 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.
