commit | f6ac424a81bad038bbf9a90c7c569dba81978f51 | [log] [tgz] |
---|---|---|
author | Venkata Jagadeesh Garaga <vgaraga@codeaurora.org> | Wed Nov 09 10:40:20 2016 +0530 |
committer | Andre Eisenbach <eisenbach@google.com> | Tue Feb 28 19:01:52 2017 +0000 |
tree | 53cb9c76a17c15bd7ecb766abc3d64beb9318609 | |
parent | 03aae0f5fb4c1f12104f3299dadeeaf262e71e15 [diff] |
Increase max remote ext feature pages to 3 Use Case: DUT unable to pair with Xbox HID device Steps: 1. Turn on BT 2. Start Inquiry 3. Pair with device with three extended feature pages Failure: Unable to pair with HID device Root Cause: DUT not responding for btm_read_remote_ext_features_complete as we are not supporting three extended pages. So Security procedure also not getting started. Fix: Increase max remote ext feature pages to three from 2 as some latest remotes supporting three extended pages. As per spec we can support 255 extended pages. Test: Pair with device with three extended feature pages Bug: 32999575 Change-Id: I061c78a7aaa1ab58a2fc554d026305a0124eee77
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 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 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 ../../../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 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"