Re: [BlueZ PATCH v1] adv_monitor: Mark the device as lost on device_lost_timeout
From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date: 2021-10-04 22:47:50
Hi Manish, On Mon, Sep 27, 2021 at 11:30 AM Manish Mandlik [off-list ref] wrote:
Friendly reminder to review this patch. :) Regards, Manish. On Tue, Sep 21, 2021 at 6:13 PM Manish Mandlik [off-list ref] wrote:quoted
Mark the device as lost on device_lost_timeout so that it can be found again next time. Verified this by adding a monitor using bluetoothctl and confirming that the DeviceLost event is getting triggered when bt peer stops advertising and DeviceFound event gets triggered again when the bt peer restarts the advertising. Reviewed-by: Yun-Hao Chung <redacted> --- src/adv_monitor.c | 2 ++ 1 file changed, 2 insertions(+)diff --git a/src/adv_monitor.c b/src/adv_monitor.c index 715ac5904..a55e1ea2d 100644 --- a/src/adv_monitor.c +++ b/src/adv_monitor.c@@ -1892,7 +1892,9 @@ static bool handle_device_lost_timeout(gpointer user_data) g_dbus_proxy_method_call(monitor->proxy, "DeviceLost", report_device_state_setup, NULL, dev->device, NULL); + dev->lost_timer = 0; + dev->found = false; return FALSE; } --2.33.0.464.g1972c5931b-goog
Applied, thanks. -- Luiz Augusto von Dentz