| commit | 96036cda893b40851a409405922c07a4ffb98166 | [log] [tgz] |
|---|---|---|
| author | Nitin Shivpure <nshivpur@codeaurora.org> | Tue Mar 13 12:01:48 2018 +0530 |
| committer | Jakub Pawlowski <jpawlowski@google.com> | Wed Mar 14 23:52:02 2018 +0000 |
| tree | d9aefb1343846a23b7d574bb1b9440a51b117666 | |
| parent | 3d60c4b14ba1e89719b09da3f2c4208c553a6f3c [diff] |
SMP: Update device type as BLE while deriving LTK from LK Usecase: 1) Install the same system version and CtsVerifier.apk on 2 DUT's 2) Pair both DUT's using BT Settings Menu. 3) On DUT execute Bluetooth Test -> Bluetooth LE Secure Server Test -> Bluetooth LE Sever Test. 4) On remote device execute Bluetooth Test-> Bluetooth LE Secure Client Test -> Bluetooth LE Client Test Expected Result: All test cases can be passed. Observed Result: All test cases cannot be passed. Root Cause: DUT supports secure connection & LE privacy and during BR/EDR pairing LTK is derived from LK, but device type is not updated and is still BR/EDR instead of LE. Later when Gatt server starts advertisement with random address so while creating LE connection from gatt client to gatt server, gatt client is not able to resolve random address due to incorrect device type, It re-initiate LE paring with gatt server. Fix: Updating device type as BLE while deriving LTK from LK. Test: CTS test case can pass with above steps. Fixes: 74728232 Change-Id: I1f2c5b54d17a58615f7c2ceb954e54619b165489
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/system/bt
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 system/bt is checked out under AOSP, then create symbolic links instead of downloading sources
cd system/bt 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 system/bt gn gen --ide=eclipse out/Default
In Eclipse, do File->Import->C/C++->C/C++ Project Settings, choose the XML location under system/bt/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"