commit | 78c3072dd3f2646f1b236df728925de03cf09d19 | [log] [tgz] |
---|---|---|
author | Sanket Agarwal <sanketa@google.com> | Wed Feb 22 11:55:34 2017 -0800 |
committer | Myles Watson <mylesgw@google.com> | Mon Apr 17 22:52:44 2017 +0000 |
tree | da3572d6e01a382e58c8919367c14bf3289a9e59 | |
parent | 4300644dd602d86f227d74f8b8e161696d0a84c9 [diff] |
BTA HF_CLIENT: Always reply to +BCS Phones don't like when we don't reply to +BCS codec-negotiation. We were having this behavior because not always do we want to accept a connection request over SCO. Instead of not replying to +BCS (which is essentially a codec negotiation) we rather refuse the SCO request when it comes in. This creates other issues such as some phones trying to connect SCO in an infinite loop but it still keeps interoperability with other devices such as iPhones and Microsoft phones intact Bug: b/35469963 Bug: b/35431871 Bug: b/35419773 Test: SCO (Phone Audio) test with iPhone, Microsoft and Nexus phones Change-Id: I5319edcb4da9d66c6d6b3a49742248c90dee98e6 (cherry picked from commit 39b51f299b5fc97352b83be9eb08949b2c63e5e1)
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”