commit | dedbea205c70dc0992cf3d97e50cfcdcd1e07e15 | [log] [tgz] |
---|---|---|
author | Sal Savage <salsavage@google.com> | Fri Feb 28 13:33:22 2020 -0800 |
committer | Sal Savage <salsavage@google.com> | Tue Jan 12 13:51:41 2021 -0800 |
tree | 3f913132321e2a2958afc6fd360e5ad0ce80ca6b | |
parent | bafad7996436a7c8483f6f2edccc599ad290f829 [diff] |
Pass BIP client status down and use it to decide to send image handles The new avrcp architecture has the design such that all requests to Java are agnostic of which device is asking for them. However, image handles are not meant to be sent if there is no BIP connection with that device. Rather than invalidate the previous design assumption, this patch sends that status down to the connection handler and device objects to use when building response packets. The image handles, if included, will be automatically removed if there is no client connection. If no image handles are sent, none will be included. Tag: #feature Bug: 153076316 Test: Build, flash, make sure existing metadata isn't impacted and is still sent when requested. Make sure imge handles are sent, when they exist, if and only if we've connected a client on the Java side BIP OBEX server. Change-Id: If252abe120188df2bcdabed22382fba070d17f32
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"