It seems that my IOIO bricked two different Bluetooth dongles. They both worked fine with the Hello IOIO App and were found immediately by Android. One of the dongles had the address 00:15:83:3D:0A:57 with a Cambridge Silicon Radio Ltd. Chipset.
After debugging some twi-stuff the first dongle lost its address, now shown as IOIO (00:00). I changed the dongles, but after some more debugging the next dongle was set to 00:00, too. Windows and Android show them now both as IOIO (00:00). So it is not an Android Bluetooth bug and the app “Bluetooth Class Zero” does not help in any way. This app was suggested to solve a similar problem, but it doesn’t find the IOIO at all. Plugged in the pc, the dongles worked before and their addresses were to see using the Windows device manager. Now they don’t. They seem to be bricked by the IOIO-OTG (Version 3.30). Is this a known problem? I couldn’t find it with Google. What can I do to avoid crashing the next dongle? Thanks for any help! -- 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/groups/opt_out.
