| commit | b5268c5b7fdac521781b3e39558b8884c77bb3fe | [log] [tgz] |
|---|---|---|
| author | Ugo Yu <ugoyu@google.com> | Thu May 23 19:54:41 2019 +0800 |
| committer | Ugo Yu <ugoyu@google.com> | Wed Jun 05 02:12:24 2019 +0000 |
| tree | 13499ec46b18ba987ffed5b6810ad06ca48885fb | |
| parent | 50e6566d981142198508c5f38468f8cfabacf536 [diff] |
DO NOT MERGE Separate SDP procedure from bonding state (1/2) - Do not stay in bonding state if the device is paried but still discovering service. - Report BOND_BONDED to Java after authentication for a classic Bluetooth device is completed. - Send BONDING event to Java when static identity address is first obtained during crosskey pairing - Send BONDING event to Java for the initial random address before send BONDED event - Do not send bond event for static identity address when SDP is done. - Make sure pairing control block always get cleaned up when both SDP and pairing are done - Send empty UUIDs to Java layer to unblock bonding intent broadcast when SDP fails Bug: 79703832 Test: runtest bluetooth, regression test Change-Id: I60d8883e6d095b440cce49686a2049c8b5660235 Merged-In: I8a98ba2178039e25c65fc701855066a8788312e6
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"