Sorry for the late reply. Multi-device support is advertised as being possibly flaky. To the best of my knowledge from experimenting with this shortly after developing BT support, the problems are inherent in the Android's BT stack, which is out of our control. What I've seen is that on some Android devices, but not all, trying to establish a BT connection might very negatively impact an existing one. The way the IOIO application framework works, while your app is running, it will try establishing a connection with any IOIO that you have *paired* to the Android, even if it is not there. There mere attempt to talk to it is what's causing the problems. Thus, either leave only one IOIO paired or have all your paired devices in range or return null from createIOIOConnection(...) for all but one device. Again, my impression at the moment is that this is a problem that is unrelated to the IOIO stack.
On Wed, Nov 26, 2014 at 2:32 AM, Ian Molesworth <[email protected]> wrote: > I've tried this with several different boards and firmware versions but > the only way to stop the poor communications it to unpair all but one IOIO > BT dongle at a time. > > > > > -- > 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.
