This is a known issue. It has to do with a limitation of Android services. Some folks have suggested that registering an activity to the ATTACHED event and have that activity start the service would fix this. If I find a more elegant solution I will fix the example app.
On Sat, Oct 25, 2014 at 11:23 PM, Adam Wootton <[email protected]> wrote: > I'm not sure if this due to something I'm doing wrong, but it seems that > the IOIO is only able to connect (using IOIOService) when the device is > first plugged in and the USB_ACCESSORY_ATTACHED intent is fired. If I try > to manually enumerate accessories like so : > > UsbManager manager = (UsbManager) getSystemService(Context.USB_SERVICE); > UsbAccessory[] accessoryList = manager.getAccessoryList(); > > in an app that is launched while the IOIO remains connected, no > accessories are found. However, cycling the plug fires off an intent which > is picked up perfectly fine and the connection is established. Is there > something I need to do to make this work, or does the IOIO only report its > existence when it is first plugged in? > > -- > 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.
