commit | 2bc59e595600c8058e0e8afe16b2602c03baba55 | [log] [tgz] |
---|---|---|
author | Pulkit Bhuwalka <pulkitb@google.com> | Thu Mar 22 14:34:33 2018 -0700 |
committer | Pulkit Bhuwalka <pulkitb@google.com> | Sat Apr 28 13:44:07 2018 -0700 |
tree | bc0e28a80bf2f5a775863ca2255930946e2c48ef | |
parent | 41b84de18cbe730bafd54b8afef71e19c495fce8 [diff] |
Add ability to modify IO capability of Bluetooth device Redirects all access to Bluetooth IO capability from macros. This allows it to be config determined but fall back to #define values to maintain backward compatibility. There is also the addition of methods to set IO capability properties. Since these are done at the adapter level, it reuses set_adapter_property from the bluetooth interface by adding new property configs. Bug: 36015413 Test: Created a test activity to modify values using the API and pair with different settings. Default value is picked up from macro. Change-Id: I7b80ea70cef4eacab91d20a58e745281aed273cd (cherry picked from commit 7a5281f7ffe6860f15fcc088c63b1109f98c0e0e)
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"