Gitiles
Code Review Sign In
review.blissroms.org / platform_system_bt / 9d59e3f90a7b2cfd7cbf0b46e5fc5ca9793db86d
commit9d59e3f90a7b2cfd7cbf0b46e5fc5ca9793db86d[log] [tgz]
authorRAJATH R <rajathr@codeaurora.org>Wed Jun 07 14:45:28 2017 +0530
committerJackeagle <jackeagle102gmail.com>Thu Oct 12 08:34:50 2017 +0200
tree3e9ce3d6c8d79b2c2723aa59bfb6f4ff4083dcd1
parentaabe70e42ea078697b4ad9034516476ace84a8d3 [diff]
BT: Features supported changes for system/bt

Fixed Static Analysis Issues
change-id: If389820b427f39e1030013f14d5538d7c99ce9c6

Bluetooth: Add support to send/receive raw command/event.
change-id: Id70d419c19a2b983450ebc113b8d0cca2b36ecf9

BT: Enable SoC logging through developer option.
change-id: I7193d085a1de4aa1e4b0ed6ec16a4812c8dc70b5

Bluetooth: Do not go for inquiry in BONDING State.
change-id: I71b902ae201e32a0fb18fd3bce52fd86e8cbcdd5

Bluetooth: Read BLE vendor capability to proceed on Secure conn.
change-id: I64e79d4e6fff7d9f1b0ea7272250e8155f5888e2

Handling Authentication Failure From the lower layer.
change-id: Ic9003f2b85bbaaa30b201b8a639a9d9b52055ac5

Bluetooth:CoreStack: DUT Stack Logging.
change-id: I6e74bdb1cda4455c50314f67bbcd19accd3c31e4

Bluetooth:CoreStack: DUT Stack Logging set2
change-id: I7a25d751b200e8ece87f9e5fd79ab48d736087cb

Bluetooth: Add debug logs for the remote device information
change-id: I857016c056635907586d8a9d0d577edde4efc34a

Add logs to provide the below remote device information
change-Id: I99f51841716e27ef7170b7566379b975c99a65e0

Change-Id: If276099626b0da9a7c606b8c0463460bfa846921
CRs-Fixed: 2021908
61 files changed
tree: 3e9ce3d6c8d79b2c2723aa59bfb6f4ff4083dcd1
  1. audio_a2dp_hw/
  2. bta/
  3. btcore/
  4. btif/
  5. build/
  6. conf/
  7. device/
  8. doc/
  9. embdrv/
  10. hci/
  11. include/
  12. main/
  13. osi/
  14. service/
  15. stack/
  16. test/
  17. tools/
  18. udrv/
  19. utils/
  20. vendor_libs/
  21. vnd/
  22. .clang-format
  23. .gitignore
  24. .gitreview
  25. .gn
  26. Android.bp
  27. Android.mk
  28. BUILD.gn
  29. CleanSpec.mk
  30. EventLogTags.logtags
  31. MODULE_LICENSE_APACHE2
  32. NOTICE
  33. OWNERS
  34. PREUPLOAD.cfg
  35. README.md
README.md

Fluoride Bluetooth stack

Building and running on AOSP

Just build AOSP - Fluoride is there by default.

Building and running on Linux

Instructions for Ubuntu, tested on 14.04 with Clang 3.5.0 and 16.10 with Clang 3.8.0

Download source

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/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 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/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

Generate your build files

cd ~/fluoride/bt
gn gen out/Default

Build

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.

Run

cd ~/fluoride/bt/out/Default
LD_LIBRARY_PATH=./ ./bluetoothtbd -create-ipc-socket=fluoride

Eclipse IDE Support

  1. Follows the Chromium project Eclipse Setup Instructions until "Optional: Building inside Eclipse" section (don't do that section, we will set it up differently)

  2. Generate Eclipse settings:

cd system/bt
gn gen --ide=eclipse out/Default

  1. In Eclipse, do File->Import->C/C++->C/C++ Project Settings, choose the XML location under system/bt/out/Default

  2. 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"

  3. Goto Behaviour tab, change clean command to "-t clean"