I believe Chromium team uses a RSSI threshold as low as possible (2) for two reasons: - They were experimenting with RSSI for proximity. - So that they can surface accurate values to JavaScript since Bluez notifies Chrome right away when the RSSI changes On Wed, Apr 27, 2016 at 10:47 AM, Luiz Augusto von Dentz <luiz.dentz@xxxxxxxxx> wrote: > Hi Francois, > > On Wed, Apr 27, 2016 at 11:01 AM, Francois Beaufort > <beaufort.francois@xxxxxxxxx> wrote: >> --- >> src/device.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/src/device.c b/src/device.c >> index 5269ee8..1caeee7 100644 >> --- a/src/device.c >> +++ b/src/device.c >> @@ -85,7 +85,7 @@ >> #define MIN(a, b) ((a) < (b) ? (a) : (b)) >> #endif >> >> -#define RSSI_THRESHOLD 8 >> +#define RSSI_THRESHOLD 2 >> >> #define GATT_PRIM_SVC_UUID_STR "2800" >> #define GATT_SND_SVC_UUID_STR "2801" >> -- >> 2.7.0 > > Do you guys have any numbers here? This will probably spam more the > bus with the same device being notified more often, also some > controllers may not sense that small variation on RSSI or employ some > filter for duplicated values although HCI inquiry don't seem to > support that. > > -- > Luiz Augusto von Dentz -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
