| commit | fff98c5eb69e2c91b1e5edf4618cc051664cffa7 | [log] [tgz] |
|---|---|---|
| author | Sal Savage <salsavage@google.com> | Thu Jun 04 13:35:39 2020 -0700 |
| committer | Sal Savage <salsavage@google.com> | Thu Jun 18 15:42:27 2020 -0700 |
| tree | 64076eddda6220b9aaefaec8a716e5b8b522d090 | |
| parent | 197ed6d47ff3bbc93b618cf9bc597bf873457cd5 [diff] |
Don't query for metadata on playing status These removed lines of code were for a problem that no longer seems to exist with other phones. It was a band-aid at best, having us pull metadaa on 'playing status' when a phone really should have just been sending the update to us anyway. Pulling metadata here causes a bad user experience with cover artwork where the new metadata is interpreted as a track change in Java land and cover artwork can be redownloaded. This happens primarily with non-database aware players after a BIP reconnect where we're guarenteed nothing about the handle we receive. Tag: #compatibility Bug: 158232844 Test: atest BluetoothInstrumentationTests Merged-In: Idb88e7c1e1553319cb26eba2c18e3cd2bbd552cc Change-Id: Idb88e7c1e1553319cb26eba2c18e3cd2bbd552cc
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"