IOIO OTG not connecting on Nexus 7 (2013)

757 views
Skip to first unread message

Luke O'Donnell

unread,
Oct 4, 2013, 4:56:27 AM10/4/13
to ioio-...@googlegroups.com
Hi All,

I've recently purchased a Google Nexus 7 (2013), and am having trouble getting it to talk to IOIO OTG. At this staging, trying another android ROM is the only option i can think of. Any ideas?

Tablet Info:

Model: Nexus 7
Manufacturer: Asus
Product: razorg
ID: JLS36G
Android Version: 4.3
Kernel Vesion: 3.4.0-gcee7856
Current Rom: CyanogenMod 10.2-20130927 Nightly Build

IOIO Setup info:

I have 4 IOIO OTG's, all purchased from Sparkfun in the last 2-3 months. Not sure software/bootloader versions.
I am connecting them to power via a 12v wall adapter, which is rated for 2.0 amps. This is connected to the IOIO via the JTAG port.
The IOIO is connected to the Nexus via the included OTG cable, using new Micro USB cables (i have tried at least 3).
Charge turnpot turned to max.
Switch set to "H"

Symptoms:

I cannot get either Hello IOIO or IOIO Hardware Tester to toggle the Status LED.

What i've tried:

On Stock ROM (android 4.3):

I installed IOIO Hardware Tester on the tablet. I then tried to toggle the LED, without USB Debugging enabled. This did not work. I then tried turning on USB Debugging and tried toggling the LED, this did not work. I also tried toggling USB Debugging on/off a few times, as per the wiki article (albiet for the earlier nexus 7), this did not work.

After trying different OTG and USB cables without success, i figured maybe it was something wrong with the stock rom. So i flashed it with the latest CyanogenMod rom.

On CyanogenMod rom (android 4.3)

I tried everything mentioned as above.

I rooted the device and collected LogCat logs (using CatLog application). Here is the outputs:

Plugging in IOIO WITHOUT USB Debugging, running HelloIOIO:

10-04 18:40:02.753 D/PicasaUploaderSyncManager(28967): battery info: true
10-04 18:40:10.461 D/ACDB-LOADER(202): ACDB -> send_afe_cal
10-04 18:40:10.461 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/.Launcher} from pid 638
10-04 18:40:10.541 D/dalvikvm(638): GC_FOR_ALLOC freed 1119K, 32% free 24243K/35352K, paused 68ms, total 68ms
10-04 18:40:10.601 D/dalvikvm(638): GC_FOR_ALLOC freed 1120K, 34% free 23677K/35352K, paused 58ms, total 58ms
10-04 18:40:14.765 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=ioio.examples.hello/.MainActivity bnds=[600,893][792,1085]} from pid 1131
10-04 18:40:14.765 D/ACDB-LOADER(202): ACDB -> send_afe_cal
10-04 18:40:14.835 D/dalvikvm(638): GC_FOR_ALLOC freed 589K, 32% free 24237K/35352K, paused 61ms, total 61ms
10-04 18:40:14.905 D/dalvikvm(638): GC_FOR_ALLOC freed 1111K, 34% free 23678K/35352K, paused 64ms, total 64ms
10-04 18:40:14.925 D/AccessoryIOIOConnection(1853): No accessory found.
10-04 18:40:14.925 D/AccessoryIOIOConnection(1853): No accessory found.
10-04 18:40:14.925 D/BluetoothAdapter(1853): 1104625560: getState() :  mService = null. Returning STATE_OFF
10-04 18:40:14.925 D/IOIOImpl(1853): Waiting for IOIO connection
10-04 18:40:14.925 V/IOIOImpl(1853): Waiting for underlying connection
10-04 18:40:14.925 V/SocketIOIOConnection(1853): Creating server socket
10-04 18:40:14.925 V/SocketIOIOConnection(1853): Waiting for TCP connection
10-04 18:40:14.925 D/IOIOImpl(1853): Waiting for IOIO connection
10-04 18:40:14.925 V/IOIOImpl(1853): Waiting for underlying connection
10-04 18:40:22.192 D/ACDB-LOADER(202): ACDB -> send_afe_cal
10-04 18:40:22.192 D/audio_hw_primary(202): enable_snd_device: snd_device(2: speaker)
10-04 18:40:22.192 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/.Launcher} from pid 638
10-04 18:40:22.282 D/dalvikvm(638): GC_FOR_ALLOC freed 600K, 32% free 24239K/35352K, paused 75ms, total 76ms
10-04 18:40:22.352 D/dalvikvm(638): GC_FOR_ALLOC freed 1111K, 34% free 23681K/35352K, paused 65ms, total 66ms
10-04 18:40:22.843 D/IOIOImpl(1853): Client requested disconnect.
10-04 18:40:22.843 V/SocketIOIOConnection(1853): Client initiated disconnect
10-04 18:40:22.843 D/IOIOImpl(1853): Client requested disconnect.
10-04 18:40:22.843 D/IOIOImpl(1853): Connection lost / aborted
10-04 18:40:22.843 D/IOIOBaseApplicationHelper(1853): IOIOThread is exiting
10-04 18:40:22.843 D/IOIOImpl(1853): Connection lost / aborted
10-04 18:40:22.843 D/IOIOBaseApplicationHelper(1853): IOIOThread is exiting
10-04 18:40:23.954 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 pkg=com.nolanlawson.logcat cmp=com.nolanlawson.logcat/.LogcatActivity bnds=[984,221][1176,413]} from pid 1131

Plugging in IOIO WITH USB Debugging, running HelloIOIO:

10-04 18:47:05.145 D/dalvikvm(8200): GC_CONCURRENT freed 1099K, 76% free 4948K/20048K, paused 3ms+3ms, total 93ms
10-04 18:47:06.837 I/EntropyMixer(638): Writing entropy...
10-04 18:47:06.847 D/PicasaUploaderSyncManager(28967): battery info: true
10-04 18:47:09.339 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/.Launcher} from pid 638
10-04 18:47:09.349 D/ACDB-LOADER(202): ACDB -> send_afe_cal
10-04 18:47:09.419 D/dalvikvm(638): GC_FOR_ALLOC freed 2159K, 33% free 23738K/35352K, paused 62ms, total 62ms
10-04 18:47:09.710 E/qdoverlay(199): Failed to call ioctl MSMFB_OVERLAY_SET err=Invalid argument
10-04 18:47:09.710 E/qdoverlay(199): MdpCtrl failed to setOverlay, restoring last known good ov info
10-04 18:47:09.710 E/qdoverlay(199): == Bad OVInfo is:  mdp_overlay z=1 fg=0 alpha=20 mask=-1 flags=0x60000 id=2
10-04 18:47:09.710 E/qdoverlay(199): src msmfb_img w=1216 h=1824 format=14 MDP_RGBX_8888
10-04 18:47:09.710 E/qdoverlay(199): src_rect mdp_rect x=0 y=51 w=1200 h=1772
10-04 18:47:09.710 E/qdoverlay(199): dst_rect mdp_rect x=205 y=345 w=790 h=1167
10-04 18:47:09.710 E/qdoverlay(199): == Last good known OVInfo is:  mdp_overlay z=1 fg=0 alpha=42 mask=-1 flags=0x60000 id=2
10-04 18:47:09.710 E/qdoverlay(199): src msmfb_img w=1216 h=1824 format=14 MDP_RGBX_8888
10-04 18:47:09.710 E/qdoverlay(199): src_rect mdp_rect x=0 y=50 w=1200 h=1774
10-04 18:47:09.710 E/qdoverlay(199): dst_rect mdp_rect x=189 y=322 w=822 h=1215
10-04 18:47:09.710 E/qdoverlay(199): Ctrl commit failed set overlay
10-04 18:47:09.710 E/qdhwcomposer(199): configureLowRes: commit failed for low res panel
10-04 18:47:11.021 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=ioio.examples.hello/.MainActivity bnds=[600,893][792,1085]} from pid 1131
10-04 18:47:11.111 D/dalvikvm(638): GC_FOR_ALLOC freed 1726K, 33% free 23725K/35352K, paused 70ms, total 70ms
10-04 18:47:11.151 D/AccessoryIOIOConnection(1853): No accessory found.
10-04 18:47:11.151 D/AccessoryIOIOConnection(1853): No accessory found.
10-04 18:47:11.151 D/BluetoothAdapter(1853): 1104625560: getState() :  mService = null. Returning STATE_OFF
10-04 18:47:11.151 D/IOIOImpl(1853): Waiting for IOIO connection
10-04 18:47:11.151 V/IOIOImpl(1853): Waiting for underlying connection
10-04 18:47:11.151 V/SocketIOIOConnection(1853): Creating server socket
10-04 18:47:11.151 V/SocketIOIOConnection(1853): Waiting for TCP connection
10-04 18:47:11.151 D/IOIOImpl(1853): Waiting for IOIO connection
10-04 18:47:11.151 V/IOIOImpl(1853): Waiting for underlying connection
10-04 18:47:22.412 D/ACDB-LOADER(202): ACDB -> send_afe_cal
10-04 18:47:22.412 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/.Launcher} from pid 638
10-04 18:47:22.502 D/dalvikvm(638): GC_FOR_ALLOC freed 1734K, 33% free 23724K/35352K, paused 76ms, total 76ms
10-04 18:47:22.992 D/IOIOImpl(1853): Client requested disconnect.
10-04 18:47:22.992 V/SocketIOIOConnection(1853): Client initiated disconnect
10-04 18:47:22.992 D/IOIOImpl(1853): Client requested disconnect.
10-04 18:47:22.992 D/IOIOImpl(1853): Connection lost / aborted
10-04 18:47:22.992 D/IOIOBaseApplicationHelper(1853): IOIOThread is exiting
10-04 18:47:22.992 D/IOIOImpl(1853): Connection lost / aborted
10-04 18:47:22.992 D/IOIOBaseApplicationHelper(1853): IOIOThread is exiting
10-04 18:47:25.185 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.android.settings/.Settings} from pid 1131
10-04 18:47:25.265 D/dalvikvm(638): GC_FOR_ALLOC freed 1699K, 33% free 23725K/35352K, paused 69ms, total 70ms
10-04 18:47:25.335 D/dalvikvm(3875): GC_EXPLICIT freed 865K, 31% free 13187K/18948K, paused 4ms+10ms, total 62ms
10-04 18:47:25.355 D/BluetoothAdapter(3875): 1104670432: getState() :  mService = null. Returning STATE_OFF
10-04 18:47:25.375 D/WifiService(638): setWifiEnabled: true pid=3875, uid=1000
10-04 18:47:25.385 D/BluetoothAdapter(3875): 1104670432: getState() :  mService = null. Returning STATE_OFF
10-04 18:47:25.445 D/WifiService(638): setWifiEnabled: true pid=3875, uid=1000
10-04 18:47:25.455 D/BluetoothAdapter(3875): 1104670432: getState() :  mService = null. Returning STATE_OFF
10-04 18:47:31.261 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from pid 3875
10-04 18:47:31.351 D/dalvikvm(638): GC_FOR_ALLOC freed 1731K, 33% free 23723K/35352K, paused 80ms, total 81ms
10-04 18:47:31.361 D/ACDB-LOADER(202): ACDB -> send_afe_cal
10-04 18:47:31.421 W/Settings(3875): Setting bugreport_in_power_menu has moved from android.provider.Settings.Secure to android.provider.Settings.Global.
10-04 18:47:31.431 E/Cryptfs (193): not running with encryption, aborting
10-04 18:47:31.611 I/ActivityManager(638): Displayed com.android.settings/.SubSettings: +252ms
10-04 18:47:32.722 E/UsbDebuggingManager(638): got -1 reading
10-04 18:47:32.722 E/UsbDebuggingManager(638): Communication error: 
10-04 18:47:32.722 E/UsbDebuggingManager(638): java.io.IOException: No such file or directory
10-04 18:47:32.722 E/UsbDebuggingManager(638): at android.net.LocalSocketImpl.connectLocal(Native Method)
10-04 18:47:32.722 E/UsbDebuggingManager(638): at android.net.LocalSocketImpl.connect(LocalSocketImpl.java:258)
10-04 18:47:32.722 E/UsbDebuggingManager(638): at android.net.LocalSocket.connect(LocalSocket.java:108)
10-04 18:47:32.722 E/UsbDebuggingManager(638): at com.android.server.usb.UsbDebuggingManager.listenToSocket(UsbDebuggingManager.java:79)
10-04 18:47:32.722 E/UsbDebuggingManager(638): at com.android.server.usb.UsbDebuggingManager.run(UsbDebuggingManager.java:115)
10-04 18:47:32.722 E/UsbDebuggingManager(638): at java.lang.Thread.run(Thread.java:841)
10-04 18:47:35.605 W/InputMethodManagerService(638): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@42402d40 attribute=null, token = android.os.BinderProxy@427d8940
10-04 18:47:36.646 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/.Launcher} from pid 638
10-04 18:47:36.726 D/dalvikvm(638): GC_FOR_ALLOC freed 1883K, 33% free 23736K/35352K, paused 74ms, total 75ms
10-04 18:47:38.107 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=ioio.examples.hello/.MainActivity bnds=[600,893][792,1085]} from pid 1131
10-04 18:47:38.187 D/dalvikvm(638): GC_FOR_ALLOC freed 1705K, 33% free 23727K/35352K, paused 75ms, total 75ms
10-04 18:47:38.217 D/AccessoryIOIOConnection(1853): No accessory found.
10-04 18:47:38.217 D/AccessoryIOIOConnection(1853): No accessory found.
10-04 18:47:38.217 D/BluetoothAdapter(1853): 1104625560: getState() :  mService = null. Returning STATE_OFF
10-04 18:47:38.217 D/IOIOImpl(1853): Waiting for IOIO connection
10-04 18:47:38.217 V/IOIOImpl(1853): Waiting for underlying connection
10-04 18:47:38.217 V/SocketIOIOConnection(1853): Creating server socket
10-04 18:47:38.217 V/SocketIOIOConnection(1853): Waiting for TCP connection
10-04 18:47:38.217 D/IOIOImpl(1853): Waiting for IOIO connection
10-04 18:47:38.217 V/IOIOImpl(1853): Waiting for underlying connection
10-04 18:47:41.871 D/ACDB-LOADER(202): ACDB -> send_afe_cal
10-04 18:47:41.871 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.HOME] flg=0x10200000 cmp=com.cyanogenmod.trebuchet/.Launcher} from pid 638
10-04 18:47:41.971 D/dalvikvm(638): GC_FOR_ALLOC freed 1701K, 33% free 23724K/35352K, paused 92ms, total 93ms
10-04 18:47:42.461 D/IOIOImpl(1853): Client requested disconnect.
10-04 18:47:42.461 V/SocketIOIOConnection(1853): Client initiated disconnect
10-04 18:47:42.461 D/IOIOImpl(1853): Client requested disconnect.
10-04 18:47:42.461 D/IOIOImpl(1853): Connection lost / aborted
10-04 18:47:42.461 D/IOIOBaseApplicationHelper(1853): IOIOThread is exiting
10-04 18:47:42.461 D/IOIOImpl(1853): Connection lost / aborted
10-04 18:47:42.461 D/IOIOBaseApplicationHelper(1853): IOIOThread is exiting
10-04 18:47:42.502 D/dalvikvm(8200): GC_CONCURRENT freed 449K, 73% free 5191K/18952K, paused 2ms+7ms, total 30ms
10-04 18:47:43.132 D/dalvikvm(1131): GC_FOR_ALLOC freed 7173K, 26% free 31281K/41900K, paused 28ms, total 28ms
10-04 18:47:43.152 I/ActivityManager(638): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 pkg=com.nolanlawson.logcat cmp=com.nolanlawson.logcat/.LogcatActivity bnds=[984,221][1176,413]} from pid 1131
10-04 18:47:43.232 D/dalvikvm(638): GC_FOR_ALLOC freed 1694K, 33% free 23725K/35352K, paused 68ms, total 68ms



Looking at the logcat from the above, it kinda looks like USB Debugging isn't working correctly. I might try another rom, in case this is a bug with this particular ROM.

Thanks

Luke

Ytai Ben-Tsvi

unread,
Oct 4, 2013, 8:49:27 PM10/4/13
to ioio-...@googlegroups.com
Some comments:
  1. If you're using 12V supply, make sure the wire between the supply and the IOIO is as short as possible.
  2. Forget about any Android application for now. If you plug the IOIO to the Android and do not get the open accessory connection dialog, no app can save you from this.
  3. Is it working with a PC?
  4. Try the oscillator recalibration procedure described on the Wiki (IOIODude page).


--
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/groups/opt_out.

laurent nocy

unread,
Oct 19, 2013, 6:25:06 AM10/19/13
to ioio-...@googlegroups.com
Hi,
I have the same problem on Nexus 7 2013 with ioio, and it's working on a PC.
Some news or update about that ??

Eddie Latuta

unread,
Oct 19, 2013, 12:17:01 PM10/19/13
to ioio-...@googlegroups.com

I have Nexus 7 2013 working very well over Bluetooth. In fact I have not experienced any connection problems over BT I have on Galaxy nexus

Ytai Ben-Tsvi

unread,
Oct 20, 2013, 12:26:38 AM10/20/13
to ioio-...@googlegroups.com
I don't have the N7 2013. I'm regularly using the original N7 with the IOIO over USB (host, device) and Bluetooth.
I need more info to be able to understand what's going on:
  1. Does the charging icon on the N7 turn on when you plug in the IOIO?
  2. Make sure USB debugging is off. Does the open accessory dialog pop up when you plug in the IOIO?
Until this is resolved, don't bother with any app.

Craig Shultz

unread,
Oct 23, 2013, 6:41:05 PM10/23/13
to ioio-...@googlegroups.com
I've got a nexus 7 2013 and can confirm that the latest ioio build should work on it.

One weird issue I was running into was the usb MTP protocol being disabled on my device. When it was disabled the ioio simply wouldn't connect. Maybe you could try and play around with that?

You can access it under settings, then storage, then in the upper right there is a button with three dots on it. Click it and the usb computer connection comes up.

This is all on the stock Rom.

Derek Fluegge

unread,
Mar 5, 2014, 12:50:12 AM3/5/14
to ioio-...@googlegroups.com
Hi Ytai,
Which BT dongle are you using with your original N7? I haven't had any luck with the mini Dongle that Sparkfun sells and the OTG. I also tried an old Jabra BT that I had lying around and it worked okay until I started doing multichannel AI, and it kept resetting.

Thanks in advance, and great work on getting the board out!

Ytai Ben-Tsvi

unread,
Mar 5, 2014, 11:37:58 AM3/5/14
to ioio-...@googlegroups.com
Hey,
I'm not using anything special. I'm using some dirt-cheap dongles I could find on Amazon. Make sure the trim-pot is all the way clockwise (common problem causing intermittent connection). Otherwise try the oscillator recalibration process (described on the IOIODude wiki page) and/or a different dongle.

Derek Fluegge

unread,
Mar 5, 2014, 12:35:17 PM3/5/14
to ioio-...@googlegroups.com
Thanks Ytai, I will try some other BT dongles. I've already gone down the IOIOdude route, and tried everything I found searching the topic. I would like to note that my IOIO v1 pairs with the same BT and N7.

Steven Davidson

unread,
Mar 27, 2014, 6:26:51 PM3/27/14
to ioio-...@googlegroups.com
One weird issue I was running into was the usb MTP protocol being disabled on my device. When it was disabled the ioio simply wouldn't connect. Maybe you could try and play around with that?

Thanks Craig, MTP was switched off on my Nexus 7 (2012, kitkat) and switching it on gave me the Open Accessory popup and got HelloIOIO working.  Before that, I had tried every combination I could think of (the board was working when connected to my Mac, checked using HelloIOIOConsole.jar).

Joseph Legris

unread,
Sep 6, 2016, 9:39:08 PM9/6/16
to ioio-users
Hi YTai,

Are you able to say why some BT Dongles work with the IOIO-OTG and others don't? Is there an article that explains this in some detail?

Thanks!

--
Joe Legris

Ytai Ben-Tsvi

unread,
Sep 7, 2016, 12:03:11 AM9/7/16
to ioio-...@googlegroups.com

I've definitely seen some dongles in the past that are what's called a USB compound device, meaning they apart as a USB hub with one or more devices hanging off of it. Those aren't supported since hubs are not supported. There might be similar quirks with other dongles.


To unsubscribe from this group and stop receiving emails from it, send an email to ioio-users+unsubscribe@googlegroups.com.

To post to this group, send email to ioio-...@googlegroups.com.
Visit this group at https://groups.google.com/group/ioio-users.
For more options, visit https://groups.google.com/d/optout.

Joseph Legris

unread,
Sep 11, 2016, 10:31:28 PM9/11/16
to ioio-users
I just tried the Sparkfun WRL-09434 with the IOIO-OTG and my old Nexus 7, running Android 5.1.1, and it works like a charm! This was my third dongle (the Asus USB BT-400 and aa no-name "Version 3.0" device both failed to connect, just as your wiki suggests). Thanks!

--
Joe Legris
Reply all
Reply to author
Forward
0 new messages