diff options
| author | Sven Gothel <[email protected]> | 2020-05-27 06:31:53 +0200 |
|---|---|---|
| committer | Sven Gothel <[email protected]> | 2020-05-27 06:31:53 +0200 |
| commit | 18737033bb25e6adb3aa8d43e898647f1d2fe1ad (patch) | |
| tree | 42236f9928e614b4828217e1821e8e7baaabeb13 /examples/direct_bt_scanner00 | |
| parent | a4e4b5d6579e3b943bc8c122cfb7323202c913d8 (diff) | |
HCI le_connect: COMMAND_DISALLOWED handled 'softer' / applications may ignore a failure as connect will happen
Investigating this situation a bit further.
Diffstat (limited to 'examples/direct_bt_scanner00')
| -rw-r--r-- | examples/direct_bt_scanner00/dbt_scanner00.cpp | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/examples/direct_bt_scanner00/dbt_scanner00.cpp b/examples/direct_bt_scanner00/dbt_scanner00.cpp index 65d39c46..0b783482 100644 --- a/examples/direct_bt_scanner00/dbt_scanner00.cpp +++ b/examples/direct_bt_scanner00/dbt_scanner00.cpp @@ -217,6 +217,7 @@ int main(int argc, char *argv[]) if( doHCI_Connect ) { if( 0 == device->connectDefault() ) { fprintf(stderr, "Connect: Failed %s\n", device->toString().c_str()); + // we tolerate the failed immediate connect, as it might happen at a later time } else { fprintf(stderr, "Connect: Success\n"); } |