commit | 2aad5d838605e39450d91e04d786c17e8b6bfc76 | [log] [tgz] |
---|---|---|
author | Cheney Ni <cheneyni@google.com> | Fri Oct 18 17:06:56 2019 +0800 |
committer | Cheney Ni <cheneyni@google.com> | Thu Nov 28 14:26:08 2019 +0800 |
tree | 0ed4d14273a69a4cae283821f3089451b0c238f1 | |
parent | 99d2649f78a9e1398233c431d7a10e49a12c0ea6 [diff] |
A2DP: More clear log messages for both BTA and AVDT SCB handle There were 2 types of handles for the stream control mapping between BTA and AVDT, tBTA_AV_HNDL and for AvdtpScb respectively, and the stack used them to communicate crossing layers. However, both of them were all named *handle* in logs, and was not easy to read. This CL uses bta_handle / bta_av_handle for tBTA_AV_HNDL and avdt_handle for AvdtpScb, and raise the log level to be error if AVDT API failed. Bug: 135655859 Bug: 145326274 Test: Logs changed only. Disconnecting / Reconnecting by A2DP manually Change-Id: I780561ff4fbd3be0ed54376346fbdad3efb845ed
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"