IOIO not working with Samsung Galaxy S3

[Kyle Moss]

I have read several of the topics on this page and I noticed that there are issues with phones that have Android 4.3 or newer working with the IOIO.  I just purchased my IOIO-OTG and it will not work on my Samsung Galaxy but it will on my old Motorola Droid.   I am able to update the firmware using IOIODude from my PC.  I also tried a Bluetooth dongle sold by Sparkfun but it didnt work.  I believe that is an issue with the dongle however.   Anyway, I know there are some issues with ADB and now you have to use AOA, but I have debugging turned off on my phone when testing and it does nothing.  I have even downloaded the IOIO Hardware Tester and it doesn't connect on my Galaxy S3 at all.  Help??!!

[Ytai Ben-Tsvi]

AFAIK this phone should be working with AOA.

Let's tackle this one step at a time:

Regardless of the Android software (even if you've never installed any IOIO-related software on the Android), as soon as you plug in the IOIO to the Android with USB debugging turned off, you should get the OA pop-up dialog. Have you gotten this far? If not, are you getting any indication that the Android is being charged when the IOIO is connected? If not, I would suspect either the power supply, or the current-limiting trim-pot on the IOIO (turn it all the way clockwise) or something wrong with the cabling.

On Fri, Apr 4, 2014 at 10:30 AM, Kyle Moss <ktmoss...@gmail.com> wrote:

I have read several of the topics on this page and I noticed that there are issues with phones that have Android 4.3 or newer working with the IOIO.  I just purchased my IOIO-OTG and it will not work on my Samsung Galaxy but it will on my old Motorola Droid.   I am able to update the firmware using IOIODude from my PC.  I also tried a Bluetooth dongle sold by Sparkfun but it didnt work.  I believe that is an issue with the dongle however.   Anyway, I know there are some issues with ADB and now you have to use AOA, but I have debugging turned off on my phone when testing and it does nothing.  I have even downloaded the IOIO Hardware Tester and it doesn't connect on my Galaxy S3 at all.  Help??!!

--
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 ioio-users+...@googlegroups.com.
To post to this group, send email to ioio-...@googlegroups.com.
Visit this group at http://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.

[Kyle Moss]

Ytai,

    Thanks for your response.  When I plugged my phone into the IOIO-OTG via USB I did get a prompt to associate helloIOIO with the device.  However I never could get the LED to turn on.  This was using the most recent version of the application software and with the IOIO-OTG updated to the most recent firmware.  I also made sure that debugging was turned off.  I then switched to the IOIOSampleApp included with the most recent release, compiled and BAM!! it works.  Thanks for all of your work on this device and the software.  Keep up the excellent work!!!

[Ytai Ben-Tsvi]

Glad you're good to go!

This might have to do with they way you've built the app. The pre-compiled HelloIOIO.apk should work. Let me know if it doesn't.

[Kyle Moss]

I actually transfered the pre-compiled app and tried it as well.  I tried the last 3 versions of the helloIOIO app, I used IOIODude to try the last three versions of the app firmware, and tried every combination in between.  Both using the pre-compiled apps and compiling them myself.   I have no idea why it would not work on the Galaxy phone.  However, the other app did so I'm very happy.   Like i stated in my initial question, all of the versions worked fine on the phone with Android 2.3.  For some reason there is just some minor issue that i was facing with the AOA on the newer phone.   Obviously there is some communication going on since I am prompted on my phone to use the helloIOIO app in association with the IOIO, but then it just isn't able to communicate and control the LED.  Who knows but if any one else has an issue I was just tell them to check the other app and see if it works.

[Paul McMahon]

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!

[Ytai Ben-Tsvi]

Upgrade the firmware.

[Paul McMahon]

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

[Ytai Ben-Tsvi]

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.

[Paul McMahon]

Yes, that's what I'm doing now. Working through some build issues.

- Paul

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 ioio-users+...@googlegroups.com.

[Paul McMahon]

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!

[Ytai Ben-Tsvi]

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).

[Paul McMahon]

Thanks for the help.

Just now, I am able to talk to IOIO over both generations of phones, from a version of the sample app that I compiled.

I'll back out my changes one by one, to stay as close to stock code as possible.  Then I'll port over to my own app.

I think I'll be OK from here on out.  I guess the main lesson is that for the newer phones, I can't rely on ADB.

Great support !!!!!