Obsolete
Status Update
Comments
se...@gmail.com <se...@gmail.com> #2
se...@gmail.com <se...@gmail.com> #3
Interestingly, on the Samsung Galaxy S5 with Android 4.4.2, I was able to connect to 7 peripherals. Go figure?
np...@gmail.com <np...@gmail.com> #4
I solved the issue as suggested by Seich. Modifiying The constants you can reach The limits you want. The only library interested is bluetooth.default.so in /system/lib/hw
en...@google.com <en...@google.com>
ma...@android.com <ma...@android.com>
vi...@gmail.com <vi...@gmail.com> #5
Greetings.
I’ve developed mesh networking library for Android that uses Bluetooth in such way that it doesn’t need Discoverable confirmation from the user each 5 minutes. It also allows background connection between devices thus allowing true seamless mesh networking.
You can try it here:http://underdark.io
I’ve developed mesh networking library for Android that uses Bluetooth in such way that it doesn’t need Discoverable confirmation from the user each 5 minutes. It also allows background connection between devices thus allowing true seamless mesh networking.
You can try it here:
he...@gmail.com <he...@gmail.com> #6
In My humble opinion, there is no limit on number of simultaneous connections in BLE as in BT 2.1 (which has the limit of max 8 active devices in a piconet).
In BLE, Just that as the number of connections grow, the connection interval needs to be increased (frequency of connection needs to be reduced).
So why is the limit set to 7? I am sure we can go higher.
In BLE, Just that as the number of connections grow, the connection interval needs to be increased (frequency of connection needs to be reduced).
So why is the limit set to 7? I am sure we can go higher.
ma...@gmail.com <ma...@gmail.com> #7
Hi,
I have the same problem here on many different devices. None of them is able to connect to more then 6 or 7 BLE devices simultaneously, except one single device: the Samsung Galaxy S4, rooted with Cyanogen Mod CM12 installed. With this device I can easily connect to 12 heart rate sensors simultaneously, subscribe and reliably receive data.
Is this a software setting or does it depend on the used Bluetooth chipset?
I tried to edit the /system/lib/hw/bluetooth.default.so but this is a binary file, isn't it? Do you have to compile an own Android version for this?
It's hard to find actual and reliable information about this topic on the web.
I have the same problem here on many different devices. None of them is able to connect to more then 6 or 7 BLE devices simultaneously, except one single device: the Samsung Galaxy S4, rooted with Cyanogen Mod CM12 installed. With this device I can easily connect to 12 heart rate sensors simultaneously, subscribe and reliably receive data.
Is this a software setting or does it depend on the used Bluetooth chipset?
I tried to edit the /system/lib/hw/
It's hard to find actual and reliable information about this topic on the web.
zh...@gmail.com <zh...@gmail.com> #8
Android OS < 6.0:
mBluetoothDevice.connectGatt(context, false, callback);
Android OS >= 6.0:
mBluetoothDevice.connectGatt(context, false, callback, BluetoothDevice.TRANSPORT_LE);
Ultimately, hardware equipment is needed to completely solve this problem.
mBluetoothDevice.connectGatt(context, false, callback);
Android OS >= 6.0:
mBluetoothDevice.connectGatt(context, false, callback, BluetoothDevice.TRANSPORT_LE);
Ultimately, hardware equipment is needed to completely solve this problem.
ei...@google.com <ei...@google.com>
pa...@gmail.com <pa...@gmail.com> #9
O M G, I'm so glad this is solved. Oh, wait ... it's not. Bummer.
Description
Looking at the debugger messages the failing function is registerClient() inside registerApp(). The function fails with the error code 133.
It seems that is imposed a limit of six periplherals, but the BLE specification states no limits on simultaneous connections.
Some workaround?
Is it a bug or an explicitely imposed limit?
I am using Android 4.4.2 on a Nexus 5 devices