Oh. I only got the first part of the error message. Here it is (for google 
to index for other people with same problem):

I/IncomingState( 4331): IOIO Connection established. Hardware ID: SPRK0020 
Bootloader ID: IOIO0400 Firmware ID: IOIO0330

V/IOIOImpl( 4331): Querying for required interface ID

E/IOIOImpl( 4331): Required interface ID is not supported

E/IOIOBaseApplicationHelper( 4331): Incompatible IOIO firmware

E/IOIOBaseApplicationHelper( 4331): 
ioio.lib.api.exception.IncompatibilityException: IOIO firmware does not 
support required firmware: IOIO0005

E/IOIOBaseApplicationHelper( 4331): at 
ioio.lib.impl.IOIOImpl.checkInterfaceVersion(IOIOImpl.java:208)

E/IOIOBaseApplicationHelper( 4331): at 
ioio.lib.impl.IOIOImpl.waitForConnect(IOIOImpl.java:135)

E/IOIOBaseApplicationHelper( 4331): at 
ioio.lib.util.IOIOBaseApplicationHelper$IOIOThread.run(IOIOBaseApplicationHelper.java:58)

Den tisdagen den 13:e maj 2014 kl. 12:49:49 UTC+2 skrev Gustav Sohtell:
>
> Thank you very much!
>
> I did not know the guide was not for the IOIO OTG. That would have been 
> great to point out with big letters on the old page since all google hits 
> pointed to that page :)
>
> I found this line in the logcat:
>
> I/IncomingState( 4331): IOIO Connection established. Hardware ID: SPRK0020 
> Bootloader ID: IOIO0400 Firmware ID: IOIO0330
>
> If that message would have appeared in the app instead of in logcat (which 
> is kind of difficult to read while the IOIO is connected and USB debugging 
> disabled) it would probably also have saved a lot of time.
>
>
> After flashing to 5.03 (which was much easier to do with the correct guide 
> ;)) it worked straight away!
>
>
> Thank you for your help. Now I can start working!
>
> // Gustav
>
>
>
> Den måndagen den 12:e maj 2014 kl. 21:25:00 UTC+2 skrev Ytai:
>>
>> The IOIO OTG has a different bootloader that works with the IOIODude 
>> program running on a PC. No need for an older Android. Read the wiki page 
>> for more details and post again if you have questions.
>> Another suggestion I would make is to start with the precompiled 
>> HelloIOIO.apk from the software bundle to eliminate any chance of you 
>> building the app wrong.
>> Last, always check the logcat output of your app, it will contain 
>> important information on what's wrong, for example using incompatible 
>> software/firmware combinations, which is likely what you're running into.
>> On May 12, 2014 12:18 PM, "Gustav Sohtell" <[email protected]> wrote:
>>
>>> Hello,
>>>
>>> *Background info:*
>>>
>>> I've been having some issues with my new IOIOs. I can't seem to get it 
>>> to work with any newer Android devices. I have managed to compile the 
>>> HelloIOIO version 503 and running it on a Samsung Galaxy Tab 3 10.1. It 
>>> launches fine but the button in the app does nothing on the IOIO. When I 
>>> connect the IOIO it asks if I want to use HelloIOIO to handle my connected 
>>> device but then nothing works. 
>>>
>>> I thought I'd also try on my Nexus 5 when I couldn't get it to work on 
>>> the Galaxy Tab. But then I read that I need to upgrade application firmware 
>>> to be able to use the Nexus 5.
>>>
>>> I read that you couldn't use any new Android version when using the IOIO 
>>> Manager, so I ran it on an old Motorola running Android 2.3.7. This phone 
>>> works with the IOIOs I have. 
>>>
>>>
>>> *What I have tried:*
>>>
>>> I downloaded the newest firmware using a QR-code and it lists in 
>>> Application Images as App-IOIO0500. I starred it and then connected the 
>>> IOIO to the phone... What do I do next? I have read the wiki 10 times and 
>>> all I can understand is that the programming should start automatically? I 
>>> have tried debugging enabled and disabled and I have tried connecting the 
>>> IOIO in different ways. The wiki says "*Turn the IOIO off and on again 
>>> and connect it to the Android device. The yellow LED will light for a 
>>> little longer than usual, signaling the the bootloader is working.*". 
>>> Which LED is this? I have never seen any LED light up at all "*usually*". 
>>> The IOIO manager finds the IOIO because the programmer inside IOIO Manager 
>>> says "*Waiting for target...*" instead of "*Waiting for IOIO 
>>> connection...*" when I connect the IOIO.
>>>
>>>
>>> This is the information I get from the IOIO when connecting to the old 
>>> Motorola phone: I/IncomingState( 8072): IOIO Connection established. 
>>> Hardware ID: SPRK0020 Bootloader ID: IOIO0400 Firmware ID: IOIO0330
>>>
>>>
>>> *My questions:*
>>>
>>> *How do I upgrade the firmware?* I can't make sense of the wiki. All I 
>>> can understand is that I should connect the IOIO and then an LED which I 
>>> have never seen should light up longer than usual.
>>>
>>> *Do you have any other clues to why I can't get the IOIO to work on a 
>>> Galaxy Tab 3?*
>>>  
>>> -- 
>>> 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 [email protected].
>>> To post to this group, send email to [email protected].
>>> Visit this group at http://groups.google.com/group/ioio-users.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

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

Reply via email to