meta data for this page
  •  

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		Previous revision
linux:bluetooth:bluez [2018/08/24 13:59] – created niziaklinux:bluetooth:bluez [2022/11/10 10:49] (current) – niziak
Line 1: Line 1:
-Not possible to enable constant BLE discovery: BLE discovery works for 10 seconds, then it waits 5 second and start again.+====== bluez ====== 
 + 
 +====== Debug ====== 
 + 
 +<code bash> 
 +MGMT_DEBUG=1 /usr/local/libexec/bluetooth/bluetoothd -n -d -f /etc/bluetooth/main.conf 
 +</code> 
 + 
 +====== Issues ====== 
 + 
 +Not possible to enable continuous BLE discovery: BLE discovery works for 10 seconds, then it waits 5 second and start again.
  
 <file | adapter.c> <file | adapter.c>
 #define IDLE_DISCOV_TIMEOUT (5) #define IDLE_DISCOV_TIMEOUT (5)
 ... ...
- /* +/* 
-  * In case the restart of the discovery failed, then just trigger + * In case the restart of the discovery failed, then just trigger 
-  * it for the next idle timeout again. + * it for the next idle timeout again. 
-  */ + */ 
- trigger_start_discovery(adapter, IDLE_DISCOV_TIMEOUT * 2);+trigger_start_discovery(adapter, IDLE_DISCOV_TIMEOUT * 2);
  
 ... ...
- if (adapter->no_scan_restart_delay) +if (adapter->no_scan_restart_delay) 
- trigger_start_discovery(adapter, 0); + trigger_start_discovery(adapter, 0); 
- else +else 
- trigger_start_discovery(adapter, IDLE_DISCOV_TIMEOUT); + trigger_start_discovery(adapter, IDLE_DISCOV_TIMEOUT); 
- break;+break;
 </file> </file>
 +
 +There is a condition in Bluez, to restart discovery immediatelly (without 5 second idle), when Discovery Filter is set.
 +