1. AFAIK, popping the accessory dialog when an accessory connects is an Android thing that cannot be disabled. The only way to avoid that is that the user defined an app to be the default app for this accessory, in which case the app will get automatically launched whenever the accessory connects. As an ugly workaround you might be able to register a "no-op" activity as the default handler to make it sorta behave like what you describe. 2. The fact that the incompatible() method was called is an indication that the connection to the IOIO has succeeded. The incompatibility is between the IOIOLib version against which your app was built and the firmware version. The basic rule is (major version of firmware) >= (major version of IOIOLib). So if you want your app to be compatible will both the old and new versions of firmware you'd need to build it against IOIOLib v3.x. I argue that this is probably not a great idea, since several bugs have been fixed between v3.x and v5.x, but that's up to you to decide whether or not it's worth it. And of course, I'm assuming you don't care about the newer features.
On Sat, Jan 10, 2015 at 1:57 PM, Paul McMahon <[email protected]> wrote: > And another question: > > I have two IOIO boards, one with "new" Application Version, and one with > "old". > Both have > Hardware version: SPRK0020 > Bootloader version: IOIO0400 > > New Application version: IOIO0500 > Old Application version: IOIO0330 > > I'm finding that on the New board, I can connect to the board with Android > Debugging on or off, but with the old board, I can't connect either way. > In fact, with the Application version IOIO0330 and ADB enabled (my old > configuration), I see the incompatible() routine gets called. > > I don't want to have to force my users to upgrade their IOIO boards, if > possible. I was expecting ADB mode to continue to work with the old > Application Version, even if I updated my own app code to use AOA. > Do I need conditionals in my code to work with the old Application Version? > > thanks > > > > On Saturday, January 10, 2015 at 3:42:58 PM UTC-5, Paul McMahon wrote: >> >> Thanks. I was able to get it all working. >> >> Now, I have a new request--I do not want any application launched >> automatically, nor any app interrupted if the IOIO gets connected. I >> removed the intent filters from my manifest, so now it doesn't ask to >> automatically launch my app on connection. But I still get a message like >> this every time: >> >> IOIO Standard Application >> No installed applications work with this.... >> >> I need the IOIO connection and disconnections to be completely silent, >> and have my app just pick it up and start using it when connected. >> >> Is there a way to do that? >> >> thanks >> >> >> >> >> On Saturday, January 10, 2015 at 3:17:20 PM UTC-5, Ytai wrote: >>> >>> This probably has to do with the way your project is set up. Make sure >>> to depend on the IOIOLibAccessory library project and carefully compare >>> your AndroidManifest.xml and your project.properties file to those of >>> HelloIOIO. >>> >>> On Sat, Jan 10, 2015 at 10:08 AM, Paul McMahon <[email protected]> >>> wrote: >>> >>>> 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]> 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 >>>>>> >>>>>> >>> -- > 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.
