The UUID is used for uniquely identifying information. It identifies a particular service provided by a Bluetooth device. The standard defines a basic BASE_UUID: 00000000-0000-1000-8000-00805F9B34FB. Devices such as healthcare sensors can provide a service, substituting the first eight digits with a predefined code. For example, a device that offers an RFCOMM connection uses the short … Read more
This might be a bit late to the party but for me this Python project has worked fine: https://github.com/TheWeirdDev/Bluetooth_Headset_Battery_Level I only had to change the port in line 57 to 3 for my no-name X5 headset. If it hangs or errors with “connection refused” try a different port. The Python program uses AT commands via … Read more
I have finally found a workaround. The magic is hidden under the hood of the BluetoothDevice class (see https://github.com/android/platform_frameworks_base/blob/android-4.3_r2/core/java/android/bluetooth/BluetoothDevice.java#L1037). Now, when I receive that exception, I instantiate a fallback BluetoothSocket, similar to the source code below. As you can see, invoking the hidden method createRfcommSocket via reflections. I have no clue why this method is … Read more
this code worked for me.. //Disable bluetooth BluetoothAdapter mBluetoothAdapter = BluetoothAdapter.getDefaultAdapter(); if (mBluetoothAdapter.isEnabled()) { mBluetoothAdapter.disable(); } For this to work, you must have the following permissions: <uses-permission android:name=”android.permission.BLUETOOTH”/> <uses-permission android:name=”android.permission.BLUETOOTH_ADMIN”/>
No, this is not a bug. This issue was brought up to Google where they responded saying that this was the intended behavior and they won’t fix it. They directed developers to this site where it points out that location permission is now needed for hardware identifier access. It is now the developer’s responsibility to … Read more
The distance estimate provided by iOS is based on the ratio of the beacon signal strength (rssi) over the calibrated transmitter power (txPower). The txPower is the known measured signal strength in rssi at 1 meter away. Each beacon must be calibrated with this txPower value to allow accurate distance estimates. While the distance estimates … Read more
For an iBeacon with ProximityUUID E2C56DB5-DFFB-48D2-B060-D0F5A71096E0, major 0, minor 0, and calibrated Tx Power of -59 RSSI, the transmitted BLE advertisement packet looks like this: d6 be 89 8e 40 24 05 a2 17 6e 3d 71 02 01 1a 1a ff 4c 00 02 15 e2 c5 6d b5 df fb 48 d2 b0 … Read more
Important implementation hints (Perhaps some of those hints aren’t necessary anymore due to Android OS updates.) Some devices like Nexus 4 with Android 4.3 take 45+ seconds to connect using an existing gatt instance. Work around: Always close gatt instances on disconnect and create a fresh instance of gatt on each connect. Don’t forget to … Read more
I’ve managed to fix it, and it actually seems to be a microphone issue. Go to System Preferences -> Sound, select the Input tab and set Internal Microphone as the input (mine was set with my headphones’). Crappy sound goes way after that =) EDIT (May 30 2018): I’ve found out an easier way to … Read more