I figured out the problem. My application did not have permission for the networking component. It turns out the root cause was that I was not merging the manifests from the dependent IOIO libraries. This was basically setting the following in project.properties:
manifestmerger.enabled=true Does anyone know how this normally gets set? Is it a manual thing, or is there a setting somewhere in the manifest editor or project properties UI that I am missing? On a related note, it seems that the Moto-X (ver 2) is not using Open Accessory, but reverts to USB device mode. I sort of expected Open Accessory to just work. Is there something else I may be missing to enable this functionality? I am depending on all the appropriate libraries. The IOIO Simple App also does not use Open Accessory mode. Thanks, Mark. On Friday, 2 January 2015 11:38:48 UTC-5, Mark Melvin wrote: > > Hi all, > > I have an application that works fine on the PC, and I am now porting it > to android. It uses the led/dio, and twi0. I have yet to test the TWI part > of things (for now it is completely commented out), but I am seeing > repeated disconnects and reconnects flooding the log when I run my skeleton > app. It seems to run fine (I flash the led in my setup method), but I > assume these messages are not normal. Is there anything specific I can > look for when trying to narrow this down? I am using the ioio-otg with a > Moto-X (2nd gen), and the IOIO is powered by the Moto-X via an OTG adapter > cable. > > Thanks, > Mark > -- 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.
