commit | ce55abda88b2c621096f871afe3c03db32bf3854 | [log] [tgz] |
---|---|---|
author | En-Shuo Hsu <enshuo@google.com> | Mon Mar 07 12:31:27 2022 -0800 |
committer | En-Shuo Hsu <enshuo@google.com> | Mon Mar 14 19:00:13 2022 -0700 |
tree | 5dcb160f465d9ae19a1a887106bf66a5c48a3d71 | |
parent | fb2277f353d20a915b38221cf4e6ae59e9f17ae0 [diff] |
floss: Add call status and hook to CLCC callback The report of the call status indicator is required for some headset to work properly. Add a call_status private field and abstract the set of the call status to a private helper function for better readability in the ConnectionStateCallback. Also hook the CLCC callback to reflect the correct call status. We sent HF the following +CIND thus the call status index should be 1. +CIND: ("CALL",(0,1)),("CALLSETUP",(0-3)), ... Got +CIEV: 1,1 when SCO connection started > HCI Event: Synchronous Connect Complete (0x2c) plen 17 Status: Success (0x00) Handle: 257 Address: 7C:96:D2:8B:F8:BC (OUI 7C-96-D2) Link type: eSCO (0x02) Transmission interval: 0x0c Retransmission window: 0x02 RX packet length: 60 TX packet length: 60 Air mode: CVSD (0x02) < HCI Command: Sniff Subrating (0x02|0x0011) plen 8 Handle: 256 Max latency: 0.000 msec (0x0000) Min remote timeout: 0.000 msec (0x0000) Min local timeout: 0.000 msec (0x0000) < ACL Data TX: Handle 256 flags 0x00 dlen 22 Channel: 449 len 18 [PSM 0 mode Basic (0x00)] {chan 65535} 19 ef 1d 0d 0a 2b 43 49 45 56 3a 20 31 2c 31 0d .....+CIEV: 1,1. 0a 55 .U Got +CIEV: 1,0 when disconnect > HCI Event: Disconnect Complete (0x05) plen 4 Status: Success (0x00) Handle: 257 Reason: Connection Terminated By Local Host (0x16) < HCI Command: Sniff Subrating (0x02|0x0011) plen 8 Handle: 256 Max latency: 750.000 msec (0x04b0) Min remote timeout: 1.250 msec (0x0002) Min local timeout: 1.250 msec (0x0002) < ACL Data TX: Handle 256 flags 0x00 dlen 22 Channel: 2563 len 18 [PSM 3 mode Basic (0x00)] {chan 2} RFCOMM: Unnumbered Info with Header Check (UIH) (0xef) Address: 0x63 cr 1 dlci 0x18 Control: 0xef poll/final 0 Length: 14 FCS: 0x0e 0d 0a 2b 43 49 45 56 3a 20 31 2c 30 0d 0a 0e ..+CIEV: 1,0... Tag: #floss Bug: 213408429 Test: Build, flush, put to HFP mode, start then stop call, capture btsnoop and verify +CIEV commands show up at when the call starts/stops with correct call status BYPASS_LONG_LINES_REASON: Bluetooth likes 120 char lines Change-Id: Ib9af4bf0ebe695ede4614703a6d0ca2adf5478a8
Just build AOSP - Fluoride is there by default.
Instructions for a Debian based distribution:
You'll want to download some pre-requisite packages as well. If you're currently configured for AOSP development, you should have most required packages. Otherwise, you can use the following apt-get list or use the --run-bootstrap
option on build.py
(see below) to get a list of packages missing on your system:
sudo apt-get install repo git-core gnupg flex bison gperf build-essential \ zip curl zlib1g-dev gcc-multilib g++-multilib \ x11proto-core-dev libx11-dev libncurses5 \ libgl1-mesa-dev libxml2-utils xsltproc unzip liblz4-tool libssl-dev \ libc++-dev libevent-dev \ flatbuffers-compiler libflatbuffers1 openssl \ libflatbuffers-dev libtinyxml2-dev \ libglib2.0-dev libevent-dev libnss3-dev libdbus-1-dev \ libprotobuf-dev ninja-build generate-ninja protobuf-compiler \ libre2-9 debmake \ llvm libc++abi-dev \ libre2-dev libdouble-conversion-dev
You will also need a recent-ish version of Rust and Cargo. Please follow the instructions on Rustup to install a recent version.
mkdir ~/fluoride cd ~/fluoride git clone https://android.googlesource.com/platform/packages/modules/Bluetooth
build.py
is the helper script used to build Fluoride for Linux (i.e. Floss). It accepts a --run-bootstrap
option that will set up your build staging directory and also make sure you have all required system packages to build (should work on Debian and Ubuntu). You will still need to build some unpackaged dependencies (like libchrome, modp_b64, googletest, etc).
To use it:
./build.py --run-bootstrap
This will install your bootstrapped build environment to ~/.floss
. If you want to change this, just pass in --bootstrap-dir
to the script.
The following third-party dependencies are necessary but currently unavailable via a package manager. You may have to build these from source and install them to your local environment.
We provide a script to produce debian packages for those components. Please see the instructions in build/dpkg/README.txt for more details.
cd system/build/dpkg mkdir -p outdir/{modp_b64,libchrome} # Build and install modp_b64 pushd modp_b64 ./gen-src-pkg.sh $(readlink -f ../outdir/modp_b64) popd sudo dpkg -i outdir/modp_b64/*.deb # Build and install libchrome pushd libchrome ./gen-src-pkg.sh $(readlink -f ../outdir/libchrome) popd sudo dpkg -i outdir/libchrome/*.deb
The googletest packages provided by Debian/Ubuntu (libgmock-dev and libgtest-dev) do not provide pkg-config files, so you can build your own googletest using the steps below:
git clone https://github.com/google/googletest.git -b release-1.10.0 cd googletest # Main directory of the cloned repository. mkdir build # Create a directory to hold the build output. cd build cmake .. # Generate native build scripts for GoogleTest. sudo make install -DCMAKE_INSTALL_PREFIX=/usr # Optional steps if pkgconfig isn't installed to desired location # Modify the source (/usr/lib/x86_64-linux-gnu) and target (/usr/lib) based on # your local installation. for f in $(ls /usr/lib/x86_64-linux-gnu/pkgconfig/{gtest,gmock}*); do \ ln -sf $f /usr/lib/pkgconfig/$(basename $f); done
Note: Handled by --run-bootstrap
option.
Run the following to install Rust dependencies:
cargo install cxxbridge-cmd
Note: Handled by --run-bootstrap
option.
For host build, we depend on a few other repositories:
Clone these all somewhere and create your staging environment.
export STAGING_DIR=path/to/your/staging/dir mkdir ${STAGING_DIR} mkdir -p ${STAGING_DIR}/external ln -s $(readlink -f ${PLATFORM2_DIR}/common-mk) ${STAGING_DIR}/common-mk ln -s $(readlink -f ${PLATFORM2_DIR}/.gn) ${STAGING_DIR}/.gn ln -s $(readlink -f ${RUST_CRATE_DIR}) ${STAGING_DIR}/external/rust ln -s $(readlink -f ${PROTO_LOG_DIR}) ${STAGING_DIR}/external/proto_logging
We provide a build script to automate building assuming you've staged your build environment already as above. At this point, make sure you have all the pre-requisites installed (i.e. bootstrap option and other dependencies above) or you will see failures. In addition, you may need to set a --libdir=
if your libraries are not stored in /usr/lib
by default.
./build.py
This will build all targets to the output directory at --bootstrap-dir
(which defaults to ~/.floss
). You can also build each stage separately (if you want to iterate on something specific):
You can choose to run only a specific stage by passing an arg via --target
.
Currently, Rust builds are a separate stage that uses Cargo to build. See gd/rust/README.md for more information. If you are iterating on Rust code and want to add new crates, you may also want to use the --no-vendored-rust
option (which will let you use crates.io instead of using a pre-populated vendored crates repo).
By default on Linux, we statically link libbluetooth so you can just run the binary directly. By default, it will try to run on hci0 but you can pass it --hci=N, where N corresponds to /sys/class/bluetooth/hciN.
$OUTPUT_DIR/debug/btadapterd --hci=$HCI INIT_gd_hci=true