Ah, Yes, this is a known problem on certain Androids, which I knew but totally forgot about. Glad to hear things are now working OK.
On Thu, Mar 6, 2014 at 10:51 AM, Ping li <[email protected]> wrote: > Hi Ytai > > Thank you. The problem is fixed. I paired 2 Bluetooth dongle with the PAD, > when 1 of them is working with IOIO, the android will regularly check > if another one is available. I unpaired the unuseful dongle, then the > problem disappeared. > > 在 2014年3月5日星期三UTC-5下午8时09分21秒，Ytai写道： > >> I don't have a specific recommended dongle. Look at the "supported >> dongles" page on the Wiki. >> >> Configuration wipe is *not* reprogramming. It involves entering >> bootloader mode with pin 1 shorted to GND. Please read the IOIODude wiki >> page for more info. >> >> >> On Wed, Mar 5, 2014 at 8:56 AM, Ping li <[email protected]> wrote: >> >>> Hi Ytai >>> >>> I did not see the same problem when using a USB connection. >>> What is your recommended dongle? And "Do a configuration wipe on the >>> IOIO in order to recalibrate the oscillator " means to reprogram the >>> firmware of IOIO and connect to a PC or Android device? >>> >>> Thank you >>> >>> >>> 在 2014年3月4日星期二UTC-5下午5时56分44秒，Ytai写道： >>> >>>> By overloading the connection I meant trying to push data at a higher >>>> rate than the channel can handle. If all you have is I2C transactions this >>>> should never happen. Opening a lot of analog inputs or digital inputs that >>>> change very rapidly etc. are examples for things that can generate high >>>> data rates. >>>> >>>> Anyway, try over USB. >>>> >>>> - If you don't see those problems over USB, the things to try are: >>>> - Use a different dongle. >>>> - Do a configuration wipe on the IOIO in order to recalibrate >>>> the oscillator (see wiki). >>>> - If you are still having those problems over USB, it is likely a >>>> problem with your app. Try to reduce the app until you isolate the >>>> problem. >>>> If you can't, send the minimum possible code that exhibits this problem >>>> and >>>> I'll take a look. >>>> >>>> >>>> >>>> On Tue, Mar 4, 2014 at 2:26 PM, Ping li <[email protected]> wrote: >>>> >>>>> The app is to read a accelerometer(ADXL345) and a gyroscope(ITG3200) >>>>> via the same I2C port. After every read, there is 10ms sleep. What is >>>>> meanning of the "overloading the connection"? how to fix it? >>>>> >>>>> 在 2014年3月4日星期二UTC-5下午5时20分34秒，Ytai写道： >>>>>> >>>>>> What does the app do? You might be overloading the connection. >>>>>> >>>>>> >>>>>> On Tue, Mar 4, 2014 at 2:10 PM, Ping li <[email protected]> wrote: >>>>>> >>>>>>> Hi Ytai >>>>>>> >>>>>>> I have a problem when using Bluetooth to read the IOIO. After >>>>>>> Bluetooth connection, the program can work well and can read the >>>>>>> sensors by >>>>>>> IOIO via I2C. But, during running, the android device attemp to connect >>>>>>> with IOIO again, that will cause the Wireless communication becaming >>>>>>> slow >>>>>>> so that I lost some data. I copied the log for you reference. Can you >>>>>>> help >>>>>>> me understand what is the reason? >>>>>>> >>>>>>> The Blue log shows the now speed; >>>>>>> The RED log is the attempting to connect again >>>>>>> The PINK log shows the read&write becomes slow. >>>>>>> >>>>>>> Thank you >>>>>>> >>>>>>> Li Ping >>>>>>> >>>>>>> Log: >>>>>>> 03-04 16:57:44.391: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.406: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.414: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.414: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.422: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.438: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.446: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.446: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.453: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.469: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.477: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.477: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.485: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.500: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.508: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.508: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.516: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.524: V/BluetoothIOIOConnection(7187): Attempting to >>>>>>> connect to Bluetooth device: IOIO (A3:10) >>>>>>> 03-04 16:57:44.531: I/BluetoothPolicyService(334): >>>>>>> getBluetoothDataTransferAllowed >>>>>>> 03-04 16:57:44.531: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.539: D/BluetoothPolicyService(334): MDM: >>>>>>> isProfileEnabled = true >>>>>>> 03-04 16:57:44.539: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.539: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.547: D/BluetoothUtils(7187): >>>>>>> isSocketAllowedBySecurityPolicy start : device null >>>>>>> 03-04 16:57:44.555: V/BluetoothService.cpp(334): createDeviceNative >>>>>>> 03-04 16:57:44.555: V/BluetoothService.cpp(334): createDeviceNative >>>>>>> 03-04 16:57:44.555: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.555: V/BluetoothEventLoop.cpp(334): >>>>>>> onCreateDeviceResult >>>>>>> 03-04 16:57:44.555: V/BluetoothEventLoop.cpp(334): >>>>>>> onCreateDeviceResult >>>>>>> 03-04 16:57:44.555: E/BluetoothEventLoop.cpp(334): >>>>>>> onCreateDeviceResult: D-Bus error: org.bluez.Error.AlreadyExists >>>>>>> (Already >>>>>>> Exists) >>>>>>> 03-04 16:57:44.555: V/BluetoothService.cpp(334): >>>>>>> discoverServicesNative >>>>>>> 03-04 16:57:44.555: V/BluetoothService.cpp(334): ... Object Path = >>>>>>> /org/bluez/1179/hci0/dev_00_15_83_15_A3_10 >>>>>>> 03-04 16:57:44.555: V/BluetoothService.cpp(334): ... Pattern = , >>>>>>> strlen = 0 >>>>>>> 03-04 16:57:44.571: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.766: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.766: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:44.789: D/STATUSBAR-NetworkController(429): onReceive() >>>>>>> - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE >>>>>>> 03-04 16:57:44.789: D/STATUSBAR-NetworkController(429): >>>>>>> refreshSignalCluster: data=0 bt=false >>>>>>> 03-04 16:57:44.797: D/STATUSBAR-SignalClusterView(429): >>>>>>> mSeparateMobileGroup=8 >>>>>>> 03-04 16:57:44.797: D/STATUSBAR-SignalClusterView(429): >>>>>>> mSeparateMobileGroup=8 >>>>>>> 03-04 16:57:44.797: D/STATUSBAR-SignalClusterView(429): >>>>>>> mSeparateMobileGroup=8 >>>>>>> 03-04 16:57:44.797: D/STATUSBAR-NetworkController(429): >>>>>>> refreshSignalCluster: data=0 bt=false >>>>>>> 03-04 16:57:44.797: D/STATUSBAR-SignalClusterView(429): >>>>>>> mSeparateMobileGroup=8 >>>>>>> 03-04 16:57:44.797: D/STATUSBAR-SignalClusterView(429): >>>>>>> mSeparateMobileGroup=8 >>>>>>> 03-04 16:57:44.805: D/STATUSBAR-SignalClusterView(429): >>>>>>> mSeparateMobileGroup=8 >>>>>>> 03-04 16:57:44.906: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:44.922: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:45.039: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:45.039: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:45.383: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:45.399: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:45.531: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:45.531: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:45.688: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:45.703: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:45.789: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:45.789: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:45.930: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:45.946: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> 03-04 16:57:46.086: V/BluetoothSocket.cpp(7187): readNative >>>>>>> 03-04 16:57:46.086: V/BluetoothSocket.cpp(7187): writeNative >>>>>>> >>>>>>> -- >>>>>>> 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. >>>>>>> >>>>>> >>>>>> -- >>>>> 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. >>>>> >>>> >>>> -- >>> 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. >>> >> >> -- > 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. > -- 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.
