bluetooth-lowenergy

问题 I have an application that needs to transmit bursts of data to android device. A sequence of packets during this burst is attached. We observe that during channel change, stack goes too busy and does not transmit anything for ~45-48 ms. This leads to data loss on transmitting device. We cannot hold that amount of data on transmitter to cope with delay in bluedroid. Are there any suggested changes in AOSP / bluedroid that can improve this situation? Any suggestions on where to start looking?

问题 is it possible to connect multiple sensor tags via Bluetooth low energy? In the app provided by TI, the sensor tag is the server, and app is client. So, it is possible for a single client to connect multiple servers? 回答1: YES, it is possible to connect from one application to multiple BLE devices On the other side, at at the moment, Android BLE stack (BlueDroid) seems to have synchronous nature (may be it is inspired by Samsung stack from 4.2 devices , where this behaviour was documented as

问题 is it possible to connect multiple sensor tags via Bluetooth low energy? In the app provided by TI, the sensor tag is the server, and app is client. So, it is possible for a single client to connect multiple servers? 回答1: YES, it is possible to connect from one application to multiple BLE devices On the other side, at at the moment, Android BLE stack (BlueDroid) seems to have synchronous nature (may be it is inspired by Samsung stack from 4.2 devices , where this behaviour was documented as

问题 I would like to know what is the difference between attributes and service in GATT in BLE specification, and where we can find attributes, are they in service, characteristics or in descriptors? 回答1: In summary ... services, characteristics, and descriptors ... are attributes :-) The BLE standard provides the ATT protocol that defines the concept of attributes. All attributes are defined inside a table and they have a handle, a type (with a UUID), a value (and permissions). On top of ATT

问题 I try to connect android to linux via bluetooth low energy GATT mode. There is a example code in Bluez: btgatt-server.c, I use it as server. The Android Side be as the Android official example:Connecting to a GATT Server. That is, use function BluetoothDevice::connectGatt(Context context, boolean autoConnect, BluetoothGattCallback callback). After running, the Android part returned the connection be successful,(the parameter of BluetoothGattCallback::onConnectionStateChange be STATE_CONNECTED

问题 I am working on to scan BLE in Background mode. Issue is not working in Background scan. Its working very fine in Foreground mode. Below is few code lines. dispatch_queue_t centralQueue = dispatch_queue_create("com.XXXXX.BLEback", DISPATCH_QUEUE_SERIAL);// or however you want to create your dispatch_queue_t manager = [[CBCentralManager alloc] initWithDelegate:self queue:centralQueue options:nil]; - (void)centralManagerDidUpdateState:(CBCentralManager *)central { if (central.state ==

问题 This is my first time doing Bluetooth Low Energy in Android project. The project that I am doing is basically to detect all Bluetooth LE devices and connect them to discover their services. I would like to ask if anyone know how onScanResult(), onBatchScanResults() and onScanFailed() methods are being called in ScanCallback? At First, run scanLeDevice() method. BluetoothLeScanner mLEScanner = mBluetoothAdapter.getBluetoothLeScanner(); ScanSettings settings = new ScanSettings.Builder()

问题 As the iOS documentation states, when an iOS application that utilizes BLE as a peripheral moves to background mode, the local name is not advertised and all service UUIDs are placed in the overflow area. The documentation states that they can only be discovered by an iOS device. My overall question is how exactly this happens on a lower level. Using a non-iOS bluetooth packet sniffer, I examined the advertisement data structure from my iOS peripheral app when it was in foreground and in

问题 I am writing a test app in iOS 7 with the Core Bluetooth API. When I am testing the application I found that I am getting the following warning message: TestBluetooth[626:60b] CoreBluetooth[API MISUSE] can only accept commands while in the powered on state Later I debugged app and found that, warning is coming from the following line of code: [manager scanForPeripheralsWithServices:array options:scanOptions]; So can anyone please tell me why I am getting this message in the console? There are

问题 I see that a Bluetooth socket can be of type TYPE_L2CAP, but the constructor for BluetoothSocket seems to be private and I can only find a method to instantiate a socket of type RFCOMM. How can I obtain and use a L2CAP socket? Is it actually supported by Android? 回答1: UPDATE 10/2019 Support is there! Enjoy the new API: BluetoothDevice.createL2capChannel(int) BluetoothDevice.createInsecureL2capChannel(int) BluetoothAdapter.listenUsingL2capChannel() BluetoothAdapter