Hi Patrick,

In regards to the Android client POST issue you may need this patch: 
https://gerrit.iotivity.org/gerrit/#/c/9801/

Thanks,

Tim Kourt
Intel Open Source Technology Center


From: iotivity-dev-bounces at lists.iotivity.org 
[mailto:iotivity-dev-boun...@lists.iotivity.org] On Behalf Of Patrick Bla? via 
iotivity-dev
Sent: Friday, July 29, 2016 4:38 AM
To: iotivity-dev at lists.iotivity.org
Subject: [dev] BLE issue: Linux <-> Android

Hi,

I'm trying to connect a linux device (Raspberry Pi 3 / laptop running arch 
linux) to an android device using the "SimpleServer" and "SimpleClient" 
provided in the examples of IoTivity 1.1.0.

I followed the tutorials regarding both platforms and installed Bluez 5.36 / 
5.37 either from official repositories or compiled it from source for the 
Raspberry. The laptop runs Bluez 5.37-2, all have the experimental mode 
enabled. I tried both release and debug versions for both platforms and 
architectures. I also tested the onboard BLE and an external USB BLE adapter 
for the raspberry.

The connection from android to android device works fine, but crashes after a 
POST message is sent (should be esay to fix, did not investigate further).

I was not able to connect arch linux <-> raspberry nor raspberry <-> raspberry 
due to some error:

ERROR: BLE_CLIENT: Failed to enable GATT notifications: 
GDBus.Error:org.bluez.Error.Failed: Operation failed with ATT error: 0x01
ERROR: BLE_CLIENT: Characteristic set up for GATT service at 00:1A:7D:DA:71:13 
failed.

I then tried to connect the raspberry (running as SimpleServer) to an android 
device (running the SimpleClient app with CT_ADAPTER_GATT_BTLE set), but the 
connection is not established successfully.

Android log: http://pastebin.com/qjgvdF9P
Raspberry log: http://pastebin.com/jrUu6Wv8
Raspberry hcidump: http://pastebin.com/MtuFMS5K

According to the hcidump from the raspberry, the error occurs because of a

"bdaddr C0:EE:FB:D0:8A:FE reason 0x0f
 Reason: Connection Rejected due to Unacceptable BD_ADDR"

error, which seems plausible because C0:EE:FB:D0:8A:FE is not the BDADDR of the 
android device but its wifi MAC address! The correct BDADDR is 
76:FC:27:49:40:80.

Can somebody relate to any of these bugs, I literally tried everything I could 
find to get the connection to work on any of these devices. My overall goal is 
to get a stable BLE connection between the raspberry (server) and an android 
client. If somebody has sample code to get this to work, I would really 
appreciate if you could share with me.

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20160729/313b8229/attachment.html>

Reply via email to