Video: how to upgrade your IOIO to support Bluetooth

[Ytai]

I made an instructional video to walk through the upgrade process required in order to enable Bluetooth on your IOIO!

Access from this page:

https://github.com/ytai/ioio/wiki/IOIO-Over-Bluetooth

or directly from YouTube:

http://youtu.be/eUKAPP63QtU

Please try to watch carefully and read the page above before asking any questions. If something still doesn't work for you, I'll be happy to help.

Note that this is potentially not the final release, as I'm not 100% done testing. See the "Caveats" section on the page above in order to adjust your expectations. However, this release is probably in pretty good shape.

[Michael Shiloh]

is there a written description of this? i find that i need written
instructions and can't follow a video.

On 10/26/2011 10:14 AM, Ytai wrote:
> I made an instructional video to walk through the upgrade process
> required in order to enable Bluetooth on your IOIO!
>
> Access from this page:
> https://github.com/ytai/ioio/wiki/IOIO-Over-Bluetooth
>
> or directly from YouTube:
> http://youtu.be/eUKAPP63QtU
>
> Please try to watch carefully and read the page above before asking any
> questions. If something still doesn't work for you, I'll be happy to help.

> Note that this is *potentially not the final release*, as I'm not 100%

> done testing. See the "Caveats" section on the page above in order to

> adjust your expectations. However, this release is *probably in pretty
> good shape*.
>
> --
> You received this message because you are subscribed to the Google
> Groups "ioio-users" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/ioio-users/-/77jkZQPCI60J.
> To post to this group, send email to ioio-...@googlegroups.com.
> To unsubscribe from this group, send email to
> ioio-users+...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/ioio-users?hl=en.

--
Michael Shiloh
Artist, designer, teacher, tinkerer, geek
KA6RCQ
www.teachmetomake.com
teachmetomake.wordpress.com
Interested in classes? Join http://groups.google.com/group/teach-me-to-make

[Ytai Ben-Tsvi]

I agree. There currently isn't.

I chose to publish a video first, as it is more accessible to many people, required less work for me, and will probably generate less questions :D

But I do plan to add a written guide on that same Wiki page soon.

[Michael Shiloh]

completely understand. thanks, whenever it comes.

> --
> You received this message because you are subscribed to the Google
> Groups "ioio-users" group.

[evillanueva]

very clear instruction video Ytai. thanks.

[lucas]

HI Ytai,

I tried to follow your video, but I keep seeing the following error message:

The attached IOIO is running a application firmware version that is not 
compatible with the programmer. Expecting version IOIO0200 or higher. 

I am using one 3-month old IOIO board that is never upgraded as the programmer to program a new IOIO board I ordered few days ago. Any suggestion for me to proceed the firmware upgrade or any information I need to look into? 

Thanks a lot!

[Ytai Ben-Tsvi]

You first need to upgrade the application firmware on your "programmer IOIO". This is done by downloading the App-IOIO0300 application firmware, starring it, and power-cycling the programmer IOIO. The yellow LED should light up for a little longer than usual and then everything should work. However, as I mention on the video, some Android devices which have been messed around with by the OEM or the carrier do not handle this function (application firmware programming) well. If this is your case, try to get your hands on another Android just for this specific part. It is a one-time process (until the next time there's an app-firmware upgrade).

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/iCKGXtXpXZ4J.

[James]

Hi Ytai,

I was very excited to see the bluetooth capability demonstrated. I ordered two more IOIO boards (now I have 3) a new bluetooth dongle and decided to replicate your results. My setup is identical to yours right down to the Parrot AR Drone battery :). Following the video step-by-step everything went very smoothly. I connected the new IOIO, it recognized the board (everything green), then wrote and verified the firmware. 

The problem I'm having is that the board doesn't seem to have anything on it afterward. When I reset the power and plug it the USB connection on the phone, logcat doesn't report any usb/adb connection. It appears to be dead.

When I re-wire it back up to the programmer IOIO, it recognizes the board again (everything is green again) and once again I can write and verify the firmware update without issue. I've done this several times have tried writing all 3 bootloaders but none seem to show any signs of life.

Do you have any suggestions for what I can try to bring the IOIO board back to life.

Needless to say I never got bluetooth working.

I haven't tried the 3rd IOIO board for fear of cooking it as well.

Thanks for your assistance. I think you're doing an incredible job on the hardware and supporting and building the IOIO community. Great work!

- James  

[Ytai Ben-Tsvi]

Hi James,

This may be a result of using the wrong firmware version.

Make sure you use the Boot-0300-App-0310 bundle.

Reset the programmed board after programming. Disconnect it completely from the programmer, power it and connect it to the Android. Notice whether the charging icon and/or the debug icon on the Android turn on. Also notice what's happening with the yellow LED on the IOIO.

Let me know the results and we can continue to investigate.

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/NSQXLrh57XkJ.

[James]

Hi Ytai,
I tried again and got it working. As it turns out, it was the power
adjustment screw on the IOIO board. It was turned too low.
When I connected the updated IOIO to my phone and slowly turned up the
adjustment, the USB/ADB lit up on the phone and I was in business.
From there I was able to plug in a bluetooth dongle and pair the IOIO
with my phone. I tried 3 different dongles and they all seemed to
pair.
I'm a bit embarrassed that I didn't think to try that before. I never
had to touch the charging adjustment on my original IOIO board.
Thanks for your help. This should be fun.

[Ytai Ben-Tsvi]

Great! Enjoy.

[dragorn]

In your video you connect programmer 38 to target 38, programmer 37 to target 37.

On my pair of first-gen sparkfun boards (chip id 128) this results in "unknown target connected".

Going from this post: https://groups.google.com/forum/?pli=1#!searchin/ioio-users/bootloader$2036/ioio-users/i3kHlapmZ-g/1GFSNPDywFQJ

I connected programmer 38 to target 36, and programmer 37 to target 35.  It now detects the target properly and can program the firmware.

I'm not sure where the discrepancy lies, but hopefully this can help other users.

[Ytai Ben-Tsvi]

Both should work (assuming, you also connection programmer 36 to target mclr too).

Chances are that you have wiring / soldering problems. Is that possible?

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/hfFxbVqCsP0J.

[mike kershaw]

Used the same wires and flashed in both directions (dev1 flashing dev2, re-cable, dev2 flashing dev1) with no problems on 36,35.  I get "unknown target connected" for 38,37 with programmer hosted on either device, switching the RST pin of course.

Solder joints all look clean, whacked them with some flux and reheated them to be safe, and since dev1 and dev2 work reflexively it wouldn't indicate to me that they have an electrical problem - if 37/38 were bad on one device I'd expect it to fail when acting as the programmer.

These are from the very first run of sparkfun pre-order boards.

-m

[Ytai Ben-Tsvi]

Strange... AFAIK, SparkFun themselves use pins 38/37 for programming. But anyway, can't argue with the fact that it solved your problem...

Thanks for sharing this info, maybe there's something I'm overlooking and this will help others fix a similar problem!

[eConnect]

Archos Arnova 7 G2 works for HelloIOIO and IOIOSimpleApp

[Souk Nomichith]

I don't mean to sound like I haven't read the IOIO wiki because I have read just about every page. Do I absolutely need 2 IOIO boards, PIC programmer, an android device, bluetooth dongle, and a computer to acheive bluetooth functionality? Could it be done with one PIC programmer and 1 IOIO?

[Ytai Ben-Tsvi]

Sorry if that wasn't clear:

You need either a second IOIO or a programmer. So it seems like you are good to go.

Download the hex bundle from the Downloads page, use SPRK0015 or 16 according to your board , connect the programmer (mclr, 3.3V, GND, 38, 37) and GO.

[Souk Nomichith]

Thanks,
Now I need a PIC programmer since I don't have one yet. Will this
programmer work? It's on ebay? http://tinyurl.com/75p8ofs

-Souk

On Dec 5, 11:54 pm, Ytai Ben-Tsvi <yta...@gmail.com> wrote:
> Sorry if that wasn't clear:

> You need *either* a second IOIO *or* a programmer. So it seems like you are

[Ytai Ben-Tsvi]

Yes. But if you go to sure electronics directly and not through eBay it is a little cheaper.

[emooney]

Hey Ytai,

Because I have an HTC Thunderbolt, I borrowed my wife's HTC Evo 4g and successfully ran the HelloIOIO app via USB so I know her phone works. But I want to put the bluetooth firmware on the IOIO so I bought another IOIO. I successfully flashed the new bootloader app onto the 'programmer' IOIO. I know this because I first flashed the Blink app and when I flashed back to IOIO0300, the blinking stopped.

Here's where things start to go wrong. If I have my phone plugged into the IOIO via USB, I hang after selecting '>Programmer>Select'. However, if I unplug the phone, I can hit 'Select' and select the 'Boot-IOIO0300-App-IOIO0310' app and I select 'Sprk0016'. I then plug the phone back in and it just hangs on 'Waiting for target'. I'm assuming I shouldn't be unplugging my phone at any point during this process but the IOIO Manager app just hangs if I don't.

Not sure where to go from here. 

• I've uninstalled and reinstalled all of the QR Code files as well as the IOIO Manager. 
• I've also made sure that the pot is turned all of the way up on both IOIO's. 
• One IOIO is powered by a 5v wall wart while the other is powered by a 9 volt battery. 
• 38 > 38, 37 > 37 and 36 to target mclr (reset)

Any help would be appreciated.

Thanks,

Eric

[Ytai Ben-Tsvi]

"Waiting for target" is good. It means that IOIOManager was able to communicate with your programmer IOIO and is waiting for the target IOIO to be connected.

Did you remember to share a common ground between the IOIOs?

Also, better power them from the same supply, just in case both supplies don't get along.

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/ZP1B69e6y34J.

[emooney]

Thanks so much for the quick reply Ytai. I got one of the two working at least through USB. I'll do the same process tomorrow morning for the other. There's something I probably missed on that one. I can't get the bluetooth working though; I'm banking on my BT Kensington Dongle. It's pretty old ( +2 yrs) and may not be 2.0. So tomorrow, I'm going to see if I can track down one that you recommend and see if that works.

Thanks again for your time. Very much appreciated.

Eric

[Ytai Ben-Tsvi]

BTW, since you are able to program, my current recommendation is to use the release candidate firmware. It looks pretty good and I'll soon release it officially.

Eric

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/SxZpVa1qAwgJ.

[Kasyful Fuadi]

Hi Ytai,

I am facing similar problem: "waiting for target". I waited for some minutes but nothing happened. My IOIO bootloader is 0100 and firmware 0300. 

I re-installed the IOIO manager and re-filled the library. The blink bootloader worked fine. I used Galaxy Tab 10.1 (Honeycomb) to program it (before I used Froyo 2.2 but hang).

Do you have any suggestion? 

Thank you in advanced.

Kasyful

[Ytai Ben-Tsvi]

You don't need to wait at all. As soon as the target is connected correctly the message changes immediately.

As you're getting this message it means that your programmer IOIO is configured correctly.

Most likely this is a wiring / power supply problem.

Make sure all 5 wires that go between the IOIOs are connected correctly and reliably.

[Suekat]

I'm just double checking,

I ordered an ioio just before Christmas from cool components. Do I need to upgrade to use Bluetooth or do boards now come with updated functionality?

Many thanks,

Susan

[Ytai Ben-Tsvi]

I have no idea what hardware and firmware versions each vendor stocks. I only know that SparkFun sell the latest of both, and the rest of the vendors normally just resell from them. However, I don't know how much time the boards sat in their stock, so it may actually be an earlier version.

The best thing would be to contact the vendor directly and ask.

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/Oy3jmYBLjZEJ.

[Suekat]

Thanks for getting back to me,

I'll try that, thanks! Can i check the board itself somehow? It arrived very promptly and i've got helloioio working. I've tried plugging a bluetooth dongle in and my phone can't find it (the light has come on on the dongle) so i'm trying to work out if it's the dongle or the board.

Susan

[Ytai Ben-Tsvi]

Run HelloIOIO over USB. Then check logcat. There should be a log message with all the versions.

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/EmuD5RWPI-MJ.

[Suekat]

Ok, i think this is the right message...

01-02 20:27:41.801: I/ActivityManager(96): Start proc ioio.examples.hello for activity ioio.examples.hello/.MainActivity: pid=1029 uid=10074 gids={3003, 3002}


I'm not sure what it means though?

Susan

[Ytai Ben-Tsvi]

Nope. Look for a message with version numbers, e.g.SPRK0015 or SPRK0016

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/iOFvMeOB05gJ.

[Suekat]

Ah ha! It's SPRK0016. Blimey, this is a bit of learning curve for me :)

01-02 20:47:01.941: I/IncomingState(1029): IOIO Connection established. Hardware ID: SPRK0016 Bootloader ID: IOIO0100 Firmware ID: IOIO0300

So it should be bluetooth enabled?

Susan

[Ytai Ben-Tsvi]

Nope. This version doesn't have Bluetooth support. You'll to go through the upgrade process described in the video.

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/D2yxWO66gBAJ.

[Susan Golton]

Ok, i'll look into getting another ioio board then.

Susan

--
www.susangolton.com

[Suekat]

Hurray! I followed the tutorial as described and got both ioios updated. Now i'm having issues finding the ioio via bluetooth. The led in the dongle is flashing but i think it's a too-expensive dongle - it's this one http://www.maplin.co.uk/miniature-bluetoothandreg-dongle-v2.0-class-i-with-100m-range-224839

I really need to get this working this week, do you think this one has a better chance of working? : http://www.amazon.co.uk/gp/product/B004Q6BAPI/ref=ox_sc_act_image_1?ie=UTF8&m=A3MA6DZ6DU3WOX

I ordered a super cheap one but it has to come from hong kong and delivery date is 1st feb (eep!)

Susan

[Ytai Ben-Tsvi]

I don't know. I can only testify for the ones I tested and the ones reported to work on this forum.

The only tip I can give is don't trust the names Android presents when scanning. One of the devices you see might be the IOIO in disguise :) Try to pair and see whether the 4545 PIN works. If it does, your IOIO will then appear as IOIO.

PS. They're ripping you off :)

Susan

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/ROnCmQLwpZcJ.

[Adam Brown]

I'm assuming the IOIO I just bought from RobotShop will have the older firmware, so I'm looking into a PICKit3 to upgrade the firmware. Does this one look solid?
http://www.sure-electronics.com/goods.php?id=1128

[Ytai Ben-Tsvi]

That's the one I'm using. It's great.

On Tue, Jan 10, 2012 at 10:20 AM, Adam Brown <adamw...@gmail.com> wrote:

I'm assuming the IOIO I just bought from RobotShop will have the older firmware, so I'm looking into a PICKit3 to upgrade the firmware. Does this one look solid?
http://www.sure-electronics.com/goods.php?id=1128

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/NquvQL5fStwJ.

[Ricky Barrette]

Do I need to update my IOIO for bluetooth if my logcat output is:

IOIO Connection established. Hardware ID: SPRK0016 Bootloader ID: IOIO0300 Firmware ID: IOIO0311

[Justin]

Ytai,

This is what both of my new IOIOs directly from SparkFun report without having reprogrammed the firmware as described in the video:

Firmware version: IOIO0310

Bootloader version: IOIO0300

Hardware version: SPRK0016

IOIOLib version: IOIO0311

So shouldn't these work with a Bluetooth dongle as is without having to upgrade the firmware on either IOIO? From everything I've read, it sure sounds like it should, but I can't get any bluetooth dongles to light up at all (like they're not even powered by the IOIO??) ...and so obviously I can't find them when I've tried to scan/pair from multiple Android phones.

So far, here are the combinations of hardware I've tried:

I've tried two phones: an HTC G2 and an HTC Sensation both from T-Mobile. Both IOIOs worked fine connected to either phone via a USB cable and I've run all your example apps on the IOIO without problems this way. So far I've learned a whole lot about how the software/API works and I love it! I just REALLY want to get this working wirelessly, but no bluetooth dongle I've tried yet seems to broadcast it's ID from the IOIO so I can pair with a phone.

I've tried 5 different USB dongles now including these first two you recommended on your site that I ordered from DealExtreme:

http://www.dealextreme.com/p/super-mini-bluetooth-2-0-adapter-dongle-vista-compatible-11866

http://www.dealextreme.com/p/ultra-mini-bluetooth-3-0-usb-dongle-65631

http://www.dealextreme.com/p/ultra-mini-bluetooth-2-1-edr-usb-2-0-dongle-37665

http://www.amazon.com/Rocketfish-Rf-Mrbtad-Micro-Bluetooth-Adapter/dp/tags-on-product/B001D8CCYK

...and some other older one I had laying around that I can't find a link to online

I've tested all 5 dongles on USB ports in two different PCs and they all light up their little status LEDs and function just fine connecting/pairing to either of the two phones mentions above. So I think I've ruled out bad dongles or bad BT hardware in the phones.

By any chance, does the current adjust potentiometer setting on the IOIO effect the power level to the dongle? Should I be messing around with that while scanning for BT devices from the phone?

Any other tips you have on debugging this would be greatly appreciated? I thought about sniffing the USB data lines between the IOIO and BT dongle to see if there are any signs of life at all.

Or maybe I should just go ahead and upgrade the firmware anyway as you described in the video to be sure it's got the right versions in case it's just not reporting the correct versions, or something corrupted the firmware?? I'm just afraid of making things worse. What was the Sparkfun warranty on these little guys again? ;)

Thanks,

Justin

PS. I've been following a couple of your projects online for some time now (like your POV globe--very very impressive! I'd love to ask you more questions about that some time ...on another forum!)

[Justin]

Hmm, I posted a long comment (copied down below) last week, but it never seemed to show up here saying "Your post has been sent for review and will appear after it has been approved."

Anyhow, I think I solved my own problem, but I kind of wanted others to know about it lest they get as frustrated as I was getting...

The current adjustment potentiometer seems to make all the difference in the world when powering the BT dongles. I forgot that apparently my particular phone (G2) doesn't need the current adjust on the IOIO set very high in order to connect/communicate with it via USB cable, so it didn't occur to me sooner to fiddle with it in order to get the bluetooth dongle to operate. Like I mentioned below, the BT LED wasn't lighting at all, when I increased the current allowance slightly, it finally lit up, but still wouldn't pair. I had to crank it most of the way up for this particular dongle (http://www.dealextreme.com/p/ultra-mini-bluetooth-2-1-edr-usb-2-0-dongle-37665) to finally broadcast it's ID for my phone to pick it up. Now it works beautifully! I'm so happy!

My original post that never showed up for the record:

[Ytai Ben-Tsvi]

Ricky, this version has problems with certain phones. If it works on yours, you should be good.

On Thu, Jan 19, 2012 at 11:50 PM, Ricky Barrette <arsenic...@gmail.com> wrote:

Do I need to update my IOIO for bluetooth if my logcat output is:

IOIO Connection established. Hardware ID: SPRK0016 Bootloader ID: IOIO0300 Firmware ID: IOIO0311

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/Y8YcLuyn5zsJ.

[Jeff Eberl]

Is it new? Because the new ones coming from sparkfun have bluetooth already. I bought mine a couple months ago and it supported bluetooth already.

On Jun 12, 2012 5:55 PM, "Randy Kuntz" <randol...@gmail.com> wrote:

Looking at the schematic, am I right thinking it could also be programmed using a PICKIT2? If so, how?
I can't get my hands on another IOIO at the moment and would love to take advantage of the Bluetooth features...
Thanks!

On Wednesday, October 26, 2011 7:14:40 PM UTC+2, Ytai wrote:

I made an instructional video to walk through the upgrade process required in order to enable Bluetooth on your IOIO!

Access from this page:

https://github.com/ytai/ioio/wiki/IOIO-Over-Bluetooth

or directly from YouTube:

http://youtu.be/eUKAPP63QtU

Please try to watch carefully and read the page above before asking any questions. If something still doesn't work for you, I'll be happy to help.

Note that this is potentially not the final release, as I'm not 100% done testing. See the "Caveats" section on the page above in order to adjust your expectations. However, this release is probably in pretty good shape.

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/LHzNW1mhV9sJ.

[Ytai Ben-Tsvi]

Yes, it is possible, albeit tricky.

PK2 doesn't support the PIC24FJxxxDAxxx out of the box. You'd need to hack your device file by replacing the following device file in your PK2 standalone application dir:

https://docs.google.com/open?id=0B4WsgbOl9eLMNjVjOWM2MTktYTMxOS00MTMxLTk5MDItZDUzMzYyYjVmMzE3&authkey=CI6K6eII

Backup your old file, and don't trust this device file for devices other than the above - I hacked it quick and dirty by overriding scripts that were in use by other devices too... but it works :)

You have the hex files on the downloads page on the wiki.

You need to connect the PK as follows:

>1 - mclr

  2 - 3.3V

  3 - GND

  4 - 38

  5 - 37

And you need to manually select the chip.

[FelixG]

Hello

To have a faster and easy overview of the supported devices, I created this following page in the Wiki.

https://github.com/ytai/ioio/wiki/Supported-Devices

 I would be happy, if we also make a entry in this page if we know if our device is supported or not.

Cheers

Felix

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.
To post to this group, send email to ioio-...@googlegroups.com.

To unsubscribe from this group, send email to ioio-users+unsubscribe@googlegroups.com.

[Ytai Ben-Tsvi]

This is a great initiative!

I would appreciate if you:

1. Format this as a table.
2. Include the firmware versions (bootloader, app) - since some Androids may work with certain firmware, but not with other.
3. Add a comments column.

BTW, this can serve as an initial reference: http://droidalyzer.com/devices.html

THANKS!!!

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/CNp9r1Yl3iEJ.

To post to this group, send email to ioio-...@googlegroups.com.

To unsubscribe from this group, send email to ioio-users+...@googlegroups.com.

[Randy Kuntz]

Thanks, it worked quite well!
Turns out my ASUS USB-BT211 isn't supported anyway :)

To unsubscribe from this group, send email to ioio-users+unsubscribe@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/ioio-users?hl=en.

--
You received this message because you are subscribed to the Google Groups "ioio-users" group.
To post to this group, send email to ioio-...@googlegroups.com.

To unsubscribe from this group, send email to ioio-users+unsubscribe@googlegroups.com.

[FelixG]

Nice to hear this. I made the changes. Is there a interesting information missing? You wrote app? Do you mean the app the user uses to test the IOIO, like HelloIOIO?

https://github.com/ytai/ioio/wiki/Supported-Devices

Am Samstag, 7. Juli 2012 10:03:16 UTC+2 schrieb Ytai:

This is a great initiative!

I would appreciate if you:

1. Format this as a table.
2. Include the firmware versions (bootloader, app) - since some Androids may work with certain firmware, but not with other.
3. Add a comments column.

BTW, this can serve as an initial reference: http://droidalyzer.com/devices.html

THANKS!!!

[Ytai Ben-Tsvi]

It's important to also note the bootloader version. I'd also shorten column header to just "USB" or "Bluetooth" (to leave more space for comments).

Other than that - perfect.

Please post at the end of the "which devices support IOIO thread" to point to this page.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/-yH6uHGBoYkJ.

To post to this group, send email to ioio-...@googlegroups.com.

To unsubscribe from this group, send email to ioio-users+...@googlegroups.com.

[FelixG]

Changes were done. Thank's for the hints and adding your two phones.

I also made a new page in the wiki for the bluetooth dongles I tested in the last few month. The range was especially for me very interesting.

https://github.com/ytai/ioio/wiki/Supported-Bluetooth-Dongles

Am Samstag, 7. Juli 2012 21:21:14 UTC+2 schrieb Ytai:

It's important to also note the bootloader version. I'd also shorten column header to just "USB" or "Bluetooth" (to leave more space for comments).

Other than that - perfect.

Please post at the end of the "which devices support IOIO thread" to point to this page.

[Randy Kuntz]

Added my unsupported device (ASUS). As the list may eventually get much longer, would you consider sorting it by vendor?

[Randy Kuntz]

Also, the Android Device fields seem rather irrelevant for the unsupported BT devices...
Should I dropp them?

[FelixG]

Dear Randy

Sorting by vendor is a nice idea. 

For the supported dongles my idea was to sort it by range and if the range is similar by similarity of the hardware (big/small dongle).

For the unsupported ones, we can sort it maybe also by manufacturer (Hama, Asus, ...).

To the irrelevance of "Android Device" field. I thought, I take the same fields like for the supported ones. I thought, that maybe some dongles have problems with special phones or Android versions. Because of this this, this field could be useful.Maybe one phone is more accessible  than an other. For example with the two dongles I wrote "buddy". I tested them with my Nexus S. Maybe with an other phone they work fine.

Felix

[Ytai Ben-Tsvi]

Agree with Felix. Some Android phones have problems with supporting Bluetooth SPP, and some phones apparently don't work with specific dongles.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/Cgrp4hj7mhoJ.

To post to this group, send email to ioio-...@googlegroups.com.

To unsubscribe from this group, send email to ioio-users+...@googlegroups.com.

[Randy Kuntz]

Did not think of that. It makes perfect sense to retain those fields!

Good job gents!

[FelixG]

Hello alltogether

I wrote a little Android app, which you can use to test your bluetooth connection or in general your IOIO board.

The app will show you, when you are connected to IOIO and displays some status information about the IOIO board. If you want to post any questions here, these information are very useful for answering on questions (e.g. bootloader version, firmware version, used bluetooth dongle).

For all those who don't know which IOIO version they use or for those who want to check a IOIO board shortly, please download this app and check it:

IOIO Hardware Tester

On the wiki are two pages about Supported-Devices and Supported-Bluetooth-Dongles. I would be very happy, if you use the Feedback button of the IOIO Hardware Tester app to send me the information of your phone, that I can update these two wiki pages! You will see which information you are sending because it is an email; feel safety.

Cheers

Felix

Am Montag, 9. Juli 2012 11:13:29 UTC+2 schrieb Randy Kuntz:

Did not think of that. It makes perfect sense to retain those fields!

Good job gents!

 

On Sun, Jul 8, 2012 at 9:04 PM, Ytai Ben-Tsvi  wrote:

Agree with Felix. Some Android phones have problems with supporting Bluetooth SPP, and some phones apparently don't work with specific dongles.

On Jul 8, 2012 11:46 AM, "FelixG" 

wrote:

[wan]

hi Ytai, 

It seems that when i follow through the video, my phone doesnt even recognize the IOIO connection. there isnt 'waiting for target'. instead, it has 'waiting for ioio connection'. May i know what could possibly be the reason for this. As i used the App-0310 bundle already. 

Thanks in advance

[Ytai Ben-Tsvi]

This means that your programmer IOIO can't communicate with the Android for whichever reason.

Things to check first:

1. Are you getting a charging icon on the Android? If not, set the trim-pot all the way clockwise, and check that you're using an adequate power supply.
2. Are you getting the debug (ADB) icon? If not, make sure USB debugging is on.
3. Is your Android on the supported devices list?

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/-wdyowhaXk8J.

To post to this group, send email to ioio-...@googlegroups.com.

To unsubscribe from this group, send email to ioio-users+...@googlegroups.com.

[wan]

hi, 

thanks for the reply. i got the trim-pot clockwise already and there's a charging icon now on my htc one x. Now, the bootloader 3.0+ app version3.10 is nowhere to be found at wiki downloads anymore. I tried getting it straight from github, but it doesnt list down the supported hardware. is there a QR for the bootloader 3.0 + app 3.10?

To unsubscribe from this group, send email to ioio-users+unsubscribe@googlegroups.com.

[Ytai Ben-Tsvi]

Just grab the latest one.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/lHDnf4TzaWIJ.

To post to this group, send email to ioio-...@googlegroups.com.

To unsubscribe from this group, send email to ioio-users+...@googlegroups.com.

[wan]

Thanks for the reply. Now, i can program and verify. The dongle now has blinking lights on it. but my phone is unable to identify the IOIO via bluetooth. what could be the possible reason..

Sorry if i were to ask amateur questions but i really appreciate the help. thanks

To unsubscribe from this group, send email to ioio-users+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/ioio-users?hl=en.

[Ytai Ben-Tsvi]

Can you see if a PC can identify the dongle? If so, it may be an Android problem.

Also, note that on first use, the dongle may appear on the available devices list with the wrong name. This is an Android quirk resulting of the fact that the Android want attempt to query the device name if it thinks it knows it already. So just try pairing with every device on the list, and if it responds to the "4545" pin, it is probably the right one.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/uVodRok80sUJ.

[Allan Breck]

James, your comment here about the IOIO trim pot adjustment on the 5V USB line is really helpful & significant, thanks. It's what I needed to get the BT working and discoverable.

 

On Wednesday, November 9, 2011 3:31:45 AM UTC-5, James wrote:

Hi Ytai,
I tried again and got it working. As it turns out, it was the power
adjustment screw on the IOIO board. It was turned too low.
When I connected the updated IOIO to my phone and slowly turned up the
adjustment, the USB/ADB lit up on the phone and I was in business.
From there I was able to plug in a bluetooth dongle and pair the IOIO
with my phone. I tried 3 different dongles and they all seemed to
pair.

[Tux Leonard]

Hi,

this hint resolved my problem.
I tried 4 different BT dongles and none of them worked. Unless I
adjusted the 5V USB. I turned the trim pot clockwise and now it works
fine.

Btw. thanks a lot for this great work.

Roy

2012/12/28 Allan Breck <fieldi...@gmail.com>:

> --
> You received this message because you are subscribed to the Google Groups
> "ioio-users" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/ioio-users/-/xXxC63OpbA0J.

[Jeff Eberl]

First off, This belongs in it's own thread. You are having trouble getting started. I'm assuming you are trying to connect via USB. Do you get a charge notification when you plug in your phone? If not, try turning the trim pot on the board all the way clockwise. Do you get a debugging notification when you connect the IOIO? If not, do you have debugging enabled on your phone? I read in a blog post somewhere that they hid the debug option somewhere. If none of that works, what happens when you power the IOIO and then connect some other USB device into it (like a mouse, or a thumb drive)? The Yellow LED should come on. Stick with the IOIO hardware tester, it's a good tool to test things out. When you get it connected via USB, you'll be able to tell which version of the firmware you have, and you might have to upgrade to get bluetooth.

Also, is anything hot when it's on?

On Mon, Dec 31, 2012 at 8:32 AM, yves-pierre cuenot <ypcu...@gmail.com> wrote:

A question for you:

I received my IOIO bord a few days ago. Date on the board is 4/6/11. Number on chip is PIC24F J256. Version PPDEV-10748 from RELCHRON.

Do I need to upgrade my IOIO? Why? Do I need another IOIO board to do so? If so I am disappointed.
Moreover my android versions all around me are only 4.2.1 and 4.1.2. As far as i understood not compatible with IOIO manager for upgrading.

I am trying to get it work for many 10th of hours now and never succeed in getting the yellow LED on!...
I use a Nexus S 4.1.2. I also tried on a NEXUS 7 4.2.1 without success nether.
I tried by downloading the Hello IOIO from eclipse.I get the app on my phone but LED doesn't go on. I also tried with other apps like:
IOIO Hardware Tester: not connected
IOIO Controler :No answer on Input PINS
IOIO Seek: cannot switch the buttons

I am waiting in the next days for a BT dongle from Amazon according to your compatible list but I am afraid it will not work nether.

The only life sign is the red LED on. I use 12VDC.1,25 A max. The 12V,  3.3V and 5V is perfect (I checked)
The charging signal is ON on my phone when I connect the IOIO on it BUT the not the ADB. Is that normal?? (I tried with and without the debugging mode activated in case of)

I am a beginner and i am sure I miss something. Please tell me how to check if my board is OK or not. If not I need to send it back. (Maybe the yellow LED doesn't work  :-))

Regards from south of France

On Wednesday, October 26, 2011 7:14:40 PM UTC+2, Ytai wrote:

I made an instructional video to walk through the upgrade process required in order to enable Bluetooth on your IOIO!

Access from this page:

https://github.com/ytai/ioio/wiki/IOIO-Over-Bluetooth

or directly from YouTube:

http://youtu.be/eUKAPP63QtU

Please try to watch carefully and read the page above before asking any questions. If something still doesn't work for you, I'll be happy to help.

Note that this is potentially not the final release, as I'm not 100% done testing. See the "Caveats" section on the page above in order to adjust your expectations. However, this release is probably in pretty good shape.

--

You received this message because you are subscribed to the Google Groups "ioio-users" group.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/1GkOI5PwCwYJ.

[claus]

Same happened to me, already bought 3 of em :) As the ioio connected to the Nexus 7 would charge the Nexus I was guessing that the USB voltage was fine. Looks like the dongle needs just a bit more! Would be nice to have that in the bluetooth docs ...

[yves-pierre cuenot]

Hi Jeff,
thank you for taking time to answer me the last day of 2012...
Happy New year!

My Phone: Nexus S  4.1.2
My IOIO: from RelChron (Amazon) PPDEV-10748    3  DR3.09 (according to the Invoice)

-Yes I am trying to connect via USB
-YES I do get a charge notification when plug IOIO on my phone
-YES my debugging mode is activated (I can check by connecting to my PC)
-NO I DO NOT GET a debugging notification when connecting to IOIO. (even acting on the trim pot)
-NO the yellow LED doesn't light on when i connect a mouse to the IOIO
-NO there is no hot part on the board

I found on this link that :
"When IOIO detects that a device supports ADK it will try to establish the app connection over ADK. Your existing apps will not detect the IOIO anymore. "

https://github.com/ytai/ioio/wiki/IOIO-Over-OpenAccessory-Beta

Could it be the reason ?

Thank you one more time for your help.

Regards

[Jeff Eberl]

The ADK shouldn't be getting in the way of the ADB. Ytai has mentioned before that it checks ADB first, and if it's on, it won't try ADK.

It sounds like your phone is set up correctly. I think the mouse test is telling us there's something wrong with your IOIO. Either it's the hardware is busted, or the firmware is wrong somehow.

The IOIO firmware is two parts, the first part is a bootloader. It starts when the IOIO is first powered, and then when it detects a USB connection, it tries to update the second part, the app layer. If there's no update, it blinks the yellow LED, and then starts the app layer. It will blink if it sees a USB mouse. So try that test again, make sure you just powered up your IOIO (so it's still in the bootloader part of the firmware) and plug in a USB mouse. The yellow LED should blink, which means it stopped the bootloader and started the app layer. Once it's in the app layer, it won't blink again unless commanded to by the android. I'm not positive, but it should blink with any USB device, so try more than one, like another mouse, keyboard, or usb key.

At any rate, a new IOIO should be working with firmware you don't have to upgrade. If this test fails, then try to send it back and get one that works.

To view this discussion on the web visit https://groups.google.com/d/msg/ioio-users/-/48G3CN3VB8kJ.

[yves-pierre cuenot]

Jeff,

I proceeded to a few other trials with USB keyboard and USB key but the yellow led never blinked.

So I started the return procedure to Amazon.

Thank you anyway to help me to conclude that this device is out of order.

Next step when I receive a new one...

Regards