Revert "Use FindDevice to get device object path" partially 18/162518/1
authorSeungyoun Ju <sy39.ju@samsung.com>
Fri, 20 Oct 2017 11:49:36 +0000 (20:49 +0900)
committerDoHyun Pyun <dh79.pyun@samsung.com>
Mon, 4 Dec 2017 05:30:01 +0000 (14:30 +0900)
commit711aba58ffff71614a9d6965139a0d5b54c84fe5
tree119b466fbdcae4415fc90812bae408a5d16bc476
parent73a2a04079e10d7e0f19d954ba3792dd43807c45
Revert "Use FindDevice to get device object path" partially

This partially reverts commit 30314c18fea269785f2c25d6f7dcd765008ad7a7

[Problem] Application couldn't make BREDR connection when remote device
 supports BREDR and LE both.
[Cause & Measure] Wrong device object path is used for BREDR connection.
 When a remote device supports BREDR/LE, bluez has two
 device object which has same bdaddr but different bdaddr_type. In this
 case, FindDevice call returns the first searched device's object path.
 To solve this issue, instead of FindDevice call,
 object path should be constructed from address.

Change-Id: If5fb0041906ec7564cc30d88be16479c3078c85e
Signed-off-by: Seungyoun Ju <sy39.ju@samsung.com>
Signed-off-by: DoHyun Pyun <dh79.pyun@samsung.com>
bt-service/bt-service-common.c