Wow, that's pretty cool. I was able to get IOIOBridge to debug the Accessory connection part of my application. I can debug at the same time as having IOIO poll some inputs.
My problem now is that my app connects properly when using the bridge, but when I go back to mission mode, I find that the setup() routine is not being called anymore. Any idea why that might not be? thanks for the quick response!! On Saturday, January 10, 2015 at 11:48:56 AM UTC-5, Ytai wrote: > > There aren't any debug steps as this is currently the intended behavior. > It is indeed inconvenient in some cases, but I couldn't find a better way > to make the same firmware automatically detect the right mode and use it. > Anyway, this isn't really a catch 22. You have several options for online > debugging of a IOIO app: > 1. Use the IOIO over Bluetooth and ADB over either Wi-Fi or USB. > 2. Use IOIO in USB device mode if your Android supports being host and ADB > over Wi-Fi. > 3. Use IOIO bridge with the IOIO connected to your development PC over USB > or Bluetooth and the ADB over either Wi-Fi or USB. In this mode you can use > an Android emulator too if you want. > > Use any one of them during development and eventually switch to your > desired mode. > On Jan 10, 2015 8:39 AM, "Paul McMahon" <[email protected] > <javascript:>> wrote: > >> >> 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] <javascript:>. >> To post to this group, send email to [email protected] >> <javascript:>. >> 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.
