add device disappear event 74/29474/2 accepted/tizen/common/20141030.230104 accepted/tizen/ivi/20141107.010905 submit/tizen/20141030.031347 submit/tizen/20141030.072151 submit/tizen_mobile/20141119.000000 submit/tizen_mobile/20141120.000000
authorCorentin Lecouvey <corentin.lecouvey@open.eurogiciel.org>
Tue, 28 Oct 2014 09:57:21 +0000 (10:57 +0100)
committerCorentin Lecouvey <corentin.lecouvey@open.eurogiciel.org>
Tue, 28 Oct 2014 10:46:55 +0000 (11:46 +0100)
commit9319c8e659d1194a7682350468da6c8fc6cd58cb
treef419154de1bd0fd9f16a79716dfc318b270cfe83
parentf9fcfc96cb7f0c96df9602d4b7a724fb289afa78
add device disappear event

When BlueZ removes some scanned devices, it previously always trigs the
bond destroy event which is sent by API layer.

This fix consists of adding paired devices to g_list and verify paired
device status when removing device interface and so fire device disappeared
or bond destroy events.

This patch is combined with ea4787499cb21d2bfc744aad7b8ba103efe67845 from
platform/core/api/bluetooth API component.

It also removes static attribute from _bt_adapter_set_status() function in
order to update adapter power status in bt-service-event-receiver.

Change-Id: Idd7406b7add402689edaad06590f7c0b4a14bee5
Signed-off-by: Corentin Lecouvey <corentin.lecouvey@open.eurogiciel.org>
bt-api/bt-event-handler.c
bt-service/bt-service-adapter.c
bt-service/bt-service-event-receiver.c
bt-service/bt-service-event-sender.c
bt-service/include/bt-service-adapter.h
include/bluetooth-api.h
include/bt-internal-types.h