commit | adb8ebebfafc0f5cce4ef96ab5b123619d731ad9 | [log] [tgz] |
---|---|---|
author | Satish Kodishala <skodisha@codeaurora.org> | Fri Feb 24 15:09:01 2017 +0530 |
committer | Pavlin Radoslavov <pavlin@google.com> | Mon Jul 31 22:53:02 2017 -0700 |
tree | c1d0c74bfb7d0ca0956d48c962e84fa582093c16 | |
parent | 1d76361d37c582e44fa62aa7b05b32b318e50028 [diff] |
Use the correct AVDTP version-specific features Failure: A2DP is not reconnected after power cycling DUT BT. Root cause: AVDTP v1.3 feature request (AVDT_GetAllCapReq) sent by DUT as remote supports the same, but this 1.3 feature is not completely supported by DUT which leads to erroneous behavior. Fix: Use AVDT_GetAllCapReq request only when both host and remote AVDTP version are 1.3 and above. Test: 1.Pair to CarKit; 2.Connect to CarKit; 3.Do BT power cycle @ DUT Bug: 35657623 Change-Id: I66c2d7d8fe8506b74282bcca93595e1cbf5c2565 (cherry picked from commit 9cd9ef4c3818d2c7949f52703b3c2ba0e0f43f2f)
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 git clone https://android.googlesource.com/platform/hardware/libhardware
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 ../../../hardware/libhardware libhardware 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”