Hi Ivan, On Thu, Mar 3, 2016 at 1:24 PM, Ivan Deviatkin <devyatkin.ivan@xxxxxxxxx> wrote: > Hi Kurt, > >> On 2 March 2016 at 21:42, Kurt McAlpine <kurt@xxxxxxxxx> wrote: >> Hi Luiz, >> >> I too am having some with BlueZ 5.37 from git (I pulled today). >> >> I do see this but my android device cannot discover the GATT service within the >> app. It is possible to pair with it, but not discover the services or even the >> device within the app. >> >> I've tired "Bluetooth LE Scanner" and nRF Master Control Panel" >> >> Ivan if you have any success with this could you let me know how you did it? > > Unfortunately I have cloned BlueZ today too and have exactly the > same issues as you. > I believe some more investigation and fixes are required to make it work. > After removing the device, turn off/on the bluetooth, discover the device using Android UI and then connecting using nRF master, or whatever else since this apparently is bluedroid fault, this is the outcome http://ix.io/oMm It does connects, we do start sending responses but as soon as we send any ATT request ourselves Bluedroid just seems unable to send any request anymore. The spec is quite clear that we can send request as well regardless if we are the peripheral or not, perhaps we can disable our discovery when acting as a peripheral but not all profiles have the GAP Peripheral must be the GATT server only and it is too bad the test specification actually don't test this because now there are probably a ton of Android devices just broken in this regard. -- Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
