| commit | 3537765c21c6adb2fcb44cfff3e7f50e2bc09d59 | [log] [tgz] |
|---|---|---|
| author | Cheney Ni <cheneyni@google.com> | Wed Mar 18 16:37:29 2020 +0800 |
| committer | Cheney Ni <cheneyni@google.com> | Tue Apr 14 17:44:03 2020 +0800 |
| tree | 2fec1648348aff73d698758025c7648d486c7333 | |
| parent | f92966049c67cae0edcea4e8d5648579512d79c1 [diff] |
A2DP: Workaround to clean up previous AVDTP instance while re-enabling If the user disables and re-enables A2dpService quickly, the stack has chances to be still busy at dropping those out-of-date links, and this is highly dependent on the handset. If the handset responds more slowly, it spends more time to disable, but causes the new AVDTP instance won't work. This change checks the previous disabling flag, and cleans up the old instance up before re-enabling. Bug: 135655859 Test: manually Change-Id: I625cfffab6d4df327fb8159aa4b759a09d90e076 Merged-In: I625cfffab6d4df327fb8159aa4b759a09d90e076 (cherry picked from commit 07689d65f4c6fbc8b20dd0890657936fc6d6cb7b)
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"