Re: IOIO-OTG not working with Samsung Galaxy S2 (SCH-R760)

[LimitlessLED LED]

try a shorter usb cable

On May 12, 2013 1:22 PM, "Travis Wyatt" <travis....@gmail.com> wrote:

I'm having some trouble getting a phone to work with the IOIO-OTG if anyone can offer some help?

Samsung Galaxy S2 (SCH-R760)
Android 4.0.4

With ADB debugging enabled on the phone, after plugging in the USB cable from IOIO-OTG to phone, IOIO Hardware Tester continues to read "Status: Not Connected"; although the battery symbol shows that the phone is charging. When plugging the phone into the computer, I get the "USB connected" and "Android debugging enabled" statuses (which I didn't get when plugged into the IOIO). ADB over USB works on the phone as I was able to install HelloIOIO from Eclipse to the phone (but HelloIOIO had no effect on the IOIO status LED). I've also tried both applications with ADB disabled (in hopes OpenAccessory might work) but I get the same results (charging the phone but no IOIO connection). I also tried turning the "chg" all the way clockwise on the IOIO.

When I try plugging in another phone, a Motorola Triumph for example, into the IOIO it works as expected and IOIO Hardware Tester reports:
Device Name: Triumph
Android Version: 2.3.7
IOIO Hardware: SPRK0020
IOIO Bootloader: IOIO0400
IOIO Firmware: IOIO0330

I've tried a few other phones with the IOIO with success as well.


The logcat when running HelloIOIO then IOIO Hardware Tester from the Samsung Galaxy S2 (with a filter of "ioio") produces:
05-11 13:10:15.882: I/ActivityManager(1903): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=ioio.examples.hello/.MainActivity bnds=[0,254][120,405]} from pid 2134
05-11 13:10:16.072: I/ActivityManager(1903): Start proc ioio.examples.hello for activity ioio.examples.hello/.MainActivity: pid=2757 uid=10047 gids={3003, 3002}
05-11 13:10:16.117: D/IOIOConnectionRegistry(2757): Successfully added bootstrap class: ioio.lib.impl.SocketIOIOConnectionBootstrap
05-11 13:10:16.122: D/IOIOConnectionRegistry(2757): Successfully added bootstrap class: ioio.lib.android.accessory.AccessoryConnectionBootstrap
05-11 13:10:16.122: D/IOIOConnectionRegistry(2757): Successfully added bootstrap class: ioio.lib.android.bluetooth.BluetoothIOIOConnectionBootstrap
05-11 13:10:16.182: D/IOIOImpl(2757): Waiting for IOIO connection
05-11 13:10:16.182: D/IOIOImpl(2757): Waiting for IOIO connection
05-11 13:10:16.232: I/ActivityManager(1903): Displayed ioio.examples.hello/.MainActivity: +181ms (total +22s309ms)
05-11 13:10:33.347: D/IOIOBaseApplicationHelper(2757): IOIOThread is exiting
05-11 13:10:33.347: D/IOIOBaseApplicationHelper(2757): IOIOThread is exiting
05-11 13:10:37.356: I/ActivityManager(1903): START {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10000000 pkg=ioio.example.ioiohardwaretester cmp=ioio.example.ioiohardwaretester/.MainActivity bnds=[0,103][120,254]} from pid 2134
05-11 13:10:37.527: I/ActivityManager(1903): Start proc ioio.example.ioiohardwaretester for activity ioio.example.ioiohardwaretester/.MainActivity: pid=2781 uid=10063 gids={3003, 3002, 3001}
05-11 13:10:37.662: D/IOIOConnectionRegistry(2781): Successfully added bootstrap class: ioio.lib.impl.SocketIOIOConnectionBootstrap
05-11 13:10:37.667: I/dalvikvm(2781): Could not find method com.android.future.usb.UsbManager.openAccessory, referenced from method ioio.lib.android.accessory.AccessoryConnectionBootstrap.openStreams
05-11 13:10:37.667: I/dalvikvm(2781): Could not find method com.android.future.usb.UsbManager.getInstance, referenced from method ioio.lib.android.accessory.AccessoryConnectionBootstrap.onCreate
05-11 13:10:37.667: I/dalvikvm(2781): Could not find method com.android.future.usb.UsbManager.getAccessoryList, referenced from method ioio.lib.android.accessory.AccessoryConnectionBootstrap.open
05-11 13:10:37.667: D/IOIOConnectionRegistry(2781): No runtime support for: ioio.lib.android.accessory.AccessoryConnectionBootstrap. Not adding.
05-11 13:10:37.667: D/IOIOConnectionRegistry(2781): Successfully added bootstrap class: ioio.lib.android.bluetooth.BluetoothIOIOConnectionBootstrap
05-11 13:10:37.747: D/IOIOImpl(2781): Waiting for IOIO connection
05-11 13:10:37.867: D/IOIOAndroidApplicationHelper(2781): IOIOThread is exiting
05-11 13:10:38.147: I/ActivityManager(1903): Displayed ioio.example.ioiohardwaretester/.MainActivity: +677ms
05-11 13:10:40.322: D/IOIOImpl(2781): Waiting for IOIO connection
05-11 13:10:50.967: D/IOIOAndroidApplicationHelper(2781): IOIOThread is exiting

Any help would be greatly appreciated.

Thanks,
Travis

--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Travis Wyatt]

I've tried with multiple USB cables, including a 1.5 ft USB cable (http://www.newegg.com/Product/Product.aspx?Item=N82E16812119354) but that didn't work either. :-(

[Ytai Ben-Tsvi]

From the log, your phone doesn't seem to support AOA (or at least not in backward compatibility mode).

I happen to know that our friend LimitlessLED on this thread might have a patch for IOIOLibAccessory that will work with the standard API, which may or may not be supported, although I will be very surprised if that matters.

I have no idea why ADB is not working, as it really should with this version of Android. The supported devices page on the wiki confirms that the S2 with 4.0.4 should be fine.

What's your power supply?

[Travis Wyatt]

I've tried powering the IOIO-OTG with a 5V wall adapter (https://www.sparkfun.com/products/8269) with no luck; also tried using an 11.1V LiPo battery (http://www.amazon.com/25C-11-1V-2200mAh-LiPo-battery/dp/B002DVBJTK/ref=sr_1_2?ie=UTF8&qid=1369356572&sr=8-2&keywords=11.1v+tenergy+lipo+2200) into the VIN/GRND pins and same problem. :-(

I've also recently acquired a Motorola Milestone phone and it has the same issue and talks perfectly w/ ADB on my Mac.

I have 2 IOIO-OTG boards and they both act the same. I happen to have an IOIOv1 board that I will try next week and report back on that.

At this point I've only been able to get the IOIO-OTG to work with my two older phones (Motorola Triumph and HTC Droid Incredible) but not with my two newer phones (Samsung Galaxy S2 and Motorola Milestone).

To be fair, this is a unique Galaxy S2 apparently (US Cellular version) so I couldn't use the common CyanogenMod on because of minor differences from the more common versions of the S2...? But I tried to use the IOIO-OTG prior to installing CyanogenMod (using the stock rom) and had the same problems.

Thanks,
Travis

[Ytai Ben-Tsvi]

When you connected the phone to your PC did you have to install any custom driver, or did you use the one by Google?

Another thing that might be happening is that your phone might present itself as a USB hub (I've seen one that does that), which would be perfectly fine with your PC, but not with the IOIO. Can you check that too?

[LimitlessLED LED]

i would focus on what sample apps you are trying, and not use the ioio service. just use hello ioio, after a phone reset. and also replug the device. and check your power supply. and check that you 3.3v on the pic side of the circuit when powered up.  does the usb connected popup come from the android status bar when you plug it in?

[Travis Wyatt]

When I connected to my Mac I didn't have to install any drivers. I can't remember now what drivers I installed for the Windows system I tried it on. I thought it was drivers from Samsung but when I went back to look for them I couldn't for the life of me find the drivers from Samsung, so not really sure.

I'm sorry to trouble you for you time, but I looked around the forums and couldn't find how I can check if the phone is acting as a USB hub (even though I seem to have seen you explaining that to someone on a thread I stumbled on some time ago)?

Thanks for your time in trying to help me,
-Travis

[Ytai Ben-Tsvi]

See here:

http://www.tekkie.ro/mobile-development/osx-list-usb-devices-lsusb-equivalent/

Compare the report with/without your Android plugged in.

[Travis Wyatt]

From what I can tell the Samsung Galaxy S2 (SCH-R760) does act as a USB hub. :-(

I attached the log of before plugging any phones into my Mac and the logs from having my old Motorola Triumph plugged in and then the Samsung Galaxy S2.

So...does that mean that I can't use the S2 with the IOIO or is there a workaround?

Thanks!
Travis

[Ytai Ben-Tsvi]

Yes. It looks to be too that your S2 is behind a (built-in) hub.

There's no workaround, unless you're considering implementing hub support on our USB stack a workaround...

What I don't understand is how other people got it to work. Perhaps there are different S2's. Bluetooth should work though, if that's any good for you.

[Travis Wyatt]

Ya, I imagine some S2's work; as this phone has been a challenge to do anything with since I got it. Seems that this version (which is meant for US Cellular) had a lot of changes from the more common variants as I had to find a custom Cyanogenmod build and even the rooting process was different from the more common S2 process. Why they had this one be a USB host vs. the more common S2 configuration is beyond me, seems like a pretty drastic change for a phone that carries the same model name.

Anyways, thanks a bunch for all your help and for your work on the IOIO!

I'll be just sticking with the older Droid Incredible that I have, as I need the lower latency and higher bandwidth that USB offers.

Thanks again!
-Travis

[Justin Trzeciak]

Hello all, I can confirm this issue happens with the Sprint Galaxy S2 as well (SPH-D710). Thank you for putting an end to a few hours of painful debugging.