No. Trying to write an Android application that handles this will not be the solution. At least if you want to use A2DP Sink role. The fact is that Android, as you mentioned it, does not implement the API calls to BlueZ (the bluetooth stack Android uses till Jelly Bean 4.1) regarding A2DP sink capabilities. … Read more
Edit: Fixed some errors. There’s no good information on the internet about this – and lots of it is wrong – don’t trust anyone! In particular, these two things are not true: RFCOMM and SPP (Serial Port Profile) are two names for the same thing. (They are however very closely related.) There’s no need to … Read more
This turned out to be a problem with the Debian Squeeze bluez default configuration. If anyone else hits this problem, disable the pnat plugin by editing /etc/bluetooth/main.conf: DisablePlugins = pnat Then restart bluetoothd. $ sudo invoke-rc.d bluetooth restart No changes were required to the PyBluez code.
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
Try to change your code for creating RfcommSocket: sock = zee.createRfcommSocketToServiceRecord( UUID.fromString(“8e1f0cf7-508f-4875-b62c-fbb67fd34812”)); for this code: Method m = zee.getClass().getMethod(“createRfcommSocket”, new Class[] { int.class }); sock = (BluetoothSocket) m.invoke(device, 1); Also try to change argument value in range 1-3 in this m.invoke(device, 1); When connection will be Connected, but aborted when you try reading, call in … Read more