Parent: 33d13bbc5703185ab3f15e4429df324987f3f225
Author: Archie Pusaka <apusaka@chromium.org>
Committer: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2022-01-13 23:34:53
Tree: b128e893d5efcf96525b0c38779e5ce62119bc1e
device: Fix device can't be scanned for 5 mins after reboot After the patches which limit the attempts of doing remote name resolving, there's an issue which prevents BlueZ to RNR new devices for 5 minutes after reboot. It's caused by failed_time is init to 0, and is then treated as the timestamp when the device failed RNR. However, actually there is no failure yet. This patch fixes it by always allowing RNR when failed_time = 0.
Diffstat
| M | src/device.c | | | 22 | +++++++++++++++++- - - - - |
1 files changed, 17 insertions(+), 5 deletions(-)