Revert "Use FindDevice to get device object path" partially 09/157009/2
authorSeungyoun Ju <sy39.ju@samsung.com>
Fri, 20 Oct 2017 11:49:36 +0000 (20:49 +0900)
committerPyun DoHyun <dh79.pyun@samsung.com>
Tue, 24 Oct 2017 00:03:38 +0000 (00:03 +0000)
commit21b18618ce364e2775e96591a0fcd89185048936
tree2640913b5e06fb863de9aa930f1efc2fe3a9f8cb
parentebef700c9bf506d2030a90ae634136e07708f905
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: Idf6190b749249de28ed5cc50ef9e44438c214339
Signed-off-by: Seungyoun Ju <sy39.ju@samsung.com>
bt-service/bt-service-common.c