| commit | f3175629208a64b190dde4dcf5f92cacef70d3e9 | [log] [tgz] |
|---|---|---|
| author | Jack He <siyuanh@google.com> | Thu Dec 08 19:29:00 2016 -0800 |
| committer | Jack He <siyuanh@google.com> | Wed Jan 04 16:53:16 2017 -0800 |
| tree | 837d95af3f2cf97424d0c9ebb836356d8c3c6b08 | |
| parent | a22dd221033bb6b4052544c4489934a4ba2a3416 [diff] |
Fix A2DP metrics session duration * Fixed A2DP duration counting. It is now counting from music play start to music play end. * Start logging a2dp connection as Bluetooth sessions. Currently, only A2DP connections are logged. Thus the bluetooth session length will be the total connection length and the length within A2DP session message will be the audio connection length. * Add a audio_duration_millis field in A2DPSession to record audio duration * Add bonded memory constraint for metrics entries * Use a builder mechanism to only build metrics upon dumping * Refactor metrics module into BluetoothMetricsLogger class * Created unit test for BluetoothMetricsLogger Bug: 33694310 Test: Code compilation, Unit test, BtFunhausMetricsTest Change-Id: Iea2a997c4ea074687a5d50860e9229f0e1b82659
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/libchrome 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/libchrome libchrome 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"