IOIO connection problems

[tyimofej]

I have a IOIO V1 board (Bootloader 3.11 Firrmware V4.). I can connect it via USB to LG Optimus 2x running 4.2.2 CM based rom.

The same board, cannot connect to my HTC One X, running 4.3.1 CM. It is recognized as a accessory, but the connection never build up.
The same, cannot connect to my Nexus 7, running stock 4.4.2. Recognized, no connection.
My only clue so far, that the first phone does not support USB host, the last two does. Sadly, I cannot find out how to disable USB host feature on Android.


I have a IOIO Mint as well. Via USB, cannot connect to any of my androids.
Via Bluetooth, I can pair it, but never could connect in the Bluetooth settings. HelloIOIO sample app not working. But, strangely enough, an app from the PlayStore (IOIO Hardware Tester by F. Adamczyk) can connect and work with the board (still not being connected in the android settings)! Bootloader 3.04 Firmware 3.24.

Any ideas, how can I make my boards work properly?

Cheers,

Tyimofej

[Ytai Ben-Tsvi]

You first said you have V4 firmware, then V3.24. Not sure which is the right one.

Could it be that you're running an app build against v4 or v5 IOIOLib against a v3 firmware? This cannot work (and the logcat output will indicate this incompatibility).

The solution is to either downgrade IOIOLib or upgrade the firmware.

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

[tyimofej]

Hello

I have 2 boards, that is why you can read about different firmwares.

Indeed, one of my problems was, that my Lib version did not match the Firmware version.

Now, I can connect via Bluetooth. But, still, no connection via USB on Android 4.3.1 , neither on 4.4.2.

USB debug off, battery charged, "USB Accessory connected" message shown. But, no connection.

 

Appreciate any help.

Tyimofej

[Ytai Ben-Tsvi]

Try upgrading both the firmware and IOIOLib to version 5.

--

[phiron]

Hi everybody,

first thank you very much for making this project! It is a fantastic idea!

I tried the whole day to make the helloIOIO work and I have to admit that it is very frustrating and far away from working out of the box :-(

I have a nexus 7 with android 4.4.2 installed.

I installed firmware / Lib 4 and 5 and none of them worked.

While connected the IOIO to my tablet it says USB debug mode and that it is charging.

I tried the IOIO Hardware Tester App and it does not recognize my IOIO board:

IOIO Hardware: N.A.

IOIO Bootloader: N.A.

IOIO Firmware: N.A.

Connections Type: N.A.

...

I really want to try out IOIO but I assume it's not working with the nexus 7 and 4.4.2?

Please help me, I would be grateful if you could give me some directions.

Thank you very much, and keep up the great work with IOIO.

P.

[phiron]

OK.

I've managed to connect the IOIO OTG with my nexus 7 (2013) and android 4.4.2.

- firmware / Lib ver. 5 installed

- Power & USB Debug activated when IOIO connected

- Disable USB Debug

- Enable MTP -> settings -> storage -> upper right 3 dots -> enable MTP

- Restart App and it will ask for the USB

That worked out for me, hope that helps.

Thank you, P.

[Ytai Ben-Tsvi]

What's MTP and are you sure it's actually related?

[tyimofej]

Hello

Following Phirons method, I also managed to connect on Android 4.3.1 via USB (firmware 4v).
MTP PTP ADB USB_STORAGE NONE are possible values of persist.sys.usb.config (media device, photo device, adb, usb drive) settings somwhere deep in the system. You can read the value by getprop persist.sys.usb.config command in the local terminal.
According to documentation, three should be a ACCESSORY value as well, but I never managed to switch it on (setprop persist.sys.usb.config ACCESSORY) .
You must be root to use the setprop command.

Tyimofej

[Brad E]

The options under "connect as" in "USB computer connection" are grayed out whilst I have an active USB connection so I'm not able to complete the fourth step in phiron's method. Even with mtp already on and if I take the USB in & out to switch between I still can't manage to get my nexus 7 Android 4.4.2 talking to my IOIO V1 with firmware 5 & simply running the Hello IOIO from the 5.0 app lib package talking over USB.

The IOIO is recognized once connected, and an alert prompt asks me once USB debugging is turn off if I would like to "Open Hello IOOI when this USB accessory is connected?" and then again when I run the app to "Allow the app Hello IOIO to access the USB accessory?." But the LED light just does not. turn. on... :| Tried both digital IO pin 0, and a LED of my own which I know turns on in pin 13.

I've tried the USB connection on two different boards, both of which are able to work fine via bluetooth.

Any thoughts?

Brad

[Ytai Ben-Tsvi]

If the dialog box pops up it is not a problem with the hardware or phone setup, but with the app.

Please try the pre-compiled HelloIOIO.apk taken from the latest software bundle. Also check the logcat output of the app.

--

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.

[Brad E]

Agreed regarding the hardware & phone setup.

The app I am using is the HelloIOIO.apk taken from app5.0 on the downloads page. Neither that nor the app named "IOIO Script" from the play store are working properly.

The IOIO Script app informs me"IOIO not connected" when the button is pressed.

Would it matter if a V1 chip was put on an OTG board? /

--
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/mi6TCoHG9I4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ioio-users+...@googlegroups.com.

[Ytai Ben-Tsvi]

Wait, what?

And logcat...

[Brad E]

If the microchip from a V1 IOIO board was soldered onto an OTG IOIO board.

Oh, I didn't know you could check the logcat without an active USB connection between computer running eclipse and the android. How is that done?

[Ytai Ben-Tsvi]

You do need a USB connection typically. You can view it after the IOIO is unplugged, the log gets retained on the Android.
I wouldn't assume that moving the PIC between the boards should work. What firmware is it running? There have been some pin changes between the revisions.

[Brad E]

Ah, awesome tip, did not know that, thanks!

It was upgraded with IOIO Manager to App-IOIO0500 using "Boot-IOIO0311-App10100400".....oh, wait o_o... would that cause a problem?? *face palms* it seemed to install the v5 firmware just fine. 

[Ytai Ben-Tsvi]

The two boards have slightly different circuits wired to the PIC pins and they also have different PICs. You'd need to recompile the v2 firmware to run on the older PIC if you want that to work.