commit | 6fb07fbd0e5eb89efd4e56545a23a5ded93513d4 | [log] [tgz] |
---|---|---|
author | Sumit Deshmukh <quic_sumitd@quicinc.com> | Tue Apr 16 12:38:32 2019 +0530 |
committer | Sumit Deshmukh <quic_sumitd@quicinc.com> | Wed Apr 17 10:36:55 2019 +0000 |
tree | 53324d69760498b4e4b8263ec4b8b2e17264caf6 | |
parent | 4f3cea536ed3d376fb3a6f9006416c87c8164d31 [diff] |
BLE: [IOT] Initiate disconnection when encryption fails during pairing Use case: 1. Keep remote device (IOGEAR Keyboard) in advertising mode. 2. Pair and connect remote device with DUT. 3. Disconnect remote from settings menu. 4. Bring remote device back in pairing mode. (This deletes link key at remote side.) 5. Select remote device for connection from Settings menu from paired devices in DUT. Reproducible Rate: 100% Issue: Device is seen stuck in "Connecting state" in settings app. To recover from this bad user experience, user has to wait till link is disconnected by timeout from remote or has to do BT reset. Root Cause: When pairing is initiated again from DUT (step 5), encryption change event is received with status "PIN or Key Missing" after connection complete but disconnection is not initiated by DUT thereafter. Fix: Trigger disconnection if encyption fails with reason like HCI_ERR_AUTH_FAILURE, HCI_ERR_KEY_MISSING, HCI_ERR_ENCRY_MODE_NOT_ACCEPTABLE etc Test: Checked connection and pairing after remote device deletes link key. In first attempt, disconnection will be issued and in next attempt pairing/connection will be successful. Bug: 130694802 Change-Id: Ie93938a5dc68c6bbd4b6c375c360f09e797f9e77
Just build AOSP - Fluoride is there by default.
Instructions for Ubuntu, tested on 14.04 with Clang 3.5.0 and 16.10 with Clang 3.8.0
mkdir ~/fluoride cd ~/fluoride git clone https://android.googlesource.com/platform/packages/modules/Bluetooth/system
Install dependencies (require sudo access):
cd ~/fluoride/bt build/install_deps.sh
Then fetch third party dependencies:
cd ~/fluoride/bt mkdir third_party cd third_party git clone https://github.com/google/googletest.git git clone https://android.googlesource.com/platform/external/aac git clone https://android.googlesource.com/platform/external/libchrome git clone https://android.googlesource.com/platform/external/libldac git clone https://android.googlesource.com/platform/external/modp_b64 git clone https://android.googlesource.com/platform/external/tinyxml2
And third party dependencies of third party dependencies:
cd fluoride/bt/third_party/libchrome/base/third_party mkdir valgrind cd valgrind curl https://chromium.googlesource.com/chromium/src/base/+/master/third_party/valgrind/valgrind.h?format=TEXT | base64 -d > valgrind.h curl https://chromium.googlesource.com/chromium/src/base/+/master/third_party/valgrind/memcheck.h?format=TEXT | base64 -d > memcheck.h
NOTE: If packages/modules/Bluetooth/system is checked out under AOSP, then create symbolic links instead of downloading sources
cd packages/modules/Bluetooth/system mkdir third_party cd third_party ln -s ../../../external/aac aac ln -s ../../../external/libchrome libchrome ln -s ../../../external/libldac libldac ln -s ../../../external/modp_b64 modp_b64 ln -s ../../../external/tinyxml2 tinyxml2 ln -s ../../../external/googletest googletest
cd ~/fluoride/bt gn gen out/Default
cd ~/fluoride/bt ninja -C out/Default all
This will build all targets (the shared library, executables, tests, etc) and put them in out/Default. To build an individual target, replace "all" with the target of your choice, e.g. ninja -C out/Default net_test_osi
.
cd ~/fluoride/bt/out/Default LD_LIBRARY_PATH=./ ./bluetoothtbd -create-ipc-socket=fluoride
Follows the Chromium project Eclipse Setup Instructions until "Optional: Building inside Eclipse" section (don't do that section, we will set it up differently)
Generate Eclipse settings:
cd packages/modules/Bluetooth/system gn gen --ide=eclipse out/Default
In Eclipse, do File->Import->C/C++->C/C++ Project Settings, choose the XML location under packages/modules/Bluetooth/system/out/Default
Right click on the project. Go to Preferences->C/C++ Build->Builder Settings. Uncheck "Use default build command", but instead using "ninja -C out/Default"
Goto Behaviour tab, change clean command to "-t clean"