I'm having this issue as well.  I'm trying to convert my app to use 
OpenAccessory.  I can connect to the phone over ADB wirelessly, but only if 
ADB is enabled on the phone.  When ADB is enabled, the openaccessory code 
doesn't get triggered.  So I have a catch-22 here--I can't simultaneously 
have an ADB connection and OpenAccessory.  Separately, both work fine.
I have the same problem with HelloIOIO app.

Can you suggest some debug steps for me?
thanks



On Thursday, April 25, 2013 at 1:20:47 AM UTC-4, dakman05 wrote:
>
>
> I am also having an issue with wireless adb and openaccessory conflict... 
> is the attached the latest bootloader/firmware for v1? would it make a 
> difference if I upgrade.... I would like to debug using adb while taking 
> advantage of openaccessories low jitter and fast responsiveness.. 
>
>
> On Thursday, April 26, 2012 5:27:38 AM UTC-7, Roman Reibnagel wrote:
>>
>> Hello,
>>
>> I've got a problem when I want to debug my app over wireless ADB. When I 
>> connect the IOIO and the Wireless ADB is running, ADB seems to get closed. 
>> When I run adb devices in the shell, no devices are attached. When I 
>> restart the wireless adb on my phone, I can start debugging, but then the 
>> IOIO is not recognized by the app. 
>> I also tried start debugging without IOIO connected, but as soon as I 
>> connect the IOIO the debugging sessin gets closed.
>>
>> I'm using the Hello Ioio App with the IOIO connected as an Open 
>> Accessory. My phone is a Nexus S running Android 4.0.4!
>> Sometimes debugging is working, but only 1 in 10 times. Is there anything 
>> I am doing wrong?
>>
>> Regards from Austria!
>> Roman
>>
>

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