| commit | ff12fc04b4cf4d2d0830c147616e10541662aa65 | [log] [tgz] |
|---|---|---|
| author | Cheney Ni <cheneyni@google.com> | Wed May 15 14:09:49 2019 +0800 |
| committer | Cheney Ni <cheneyni@google.com> | Wed May 15 22:18:17 2019 +0800 |
| tree | 43476353a3c253bf335c86a3b7f4c809b8e8e047 | |
| parent | 5933b4ca59fb01ffd73725a0e59d21dc172deedc [diff] |
While AVDT opened or its AVRC_TIMER_EVT expired, it is no needed to start the 2nd AVDT stream There were 2 cases to start the 2nd stream automatically by the stack: * When the 2nd AVDT opened, the stack would check the 1st stream state to determinate the 2nd should be starting or not. * While the AVRC timer which was fired after AVDT opened was expired, the stack would open the AVRC and start the 2nd stream if the 1st was started. Both of them are unnecessary since all the stream must be controlled by the upper layer. We currently support an active device only, and the 2nd stream will be tracked as remote triggered and suspended immediately. To samplize the behavior, it is better to not start the 2nd stream automatically by the stack. Bug: 132146974 Test: manual Change-Id: I75f39801e9779ee55fa574e30051e01966c61ea3
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
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 ../../../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"