| commit | ef617c38469e82666362b0b0e9c23fc0ebda2f17 | [log] [tgz] |
|---|---|---|
| author | Nitin Shivpure <nshivpur@codeaurora.org> | Mon Jul 30 18:14:54 2018 +0530 |
| committer | Myles Watson <mylesgw@google.com> | Thu Aug 23 21:24:44 2018 +0000 |
| tree | 183ab7471d0d58f215b7b775e7529468cecd4b1e | |
| parent | 73a19a852f9d108188f61bc1b156c9a761fbbb46 [diff] |
L2CAP: Handle no idle timeout (0xFFFF) Precondition: 1. DUT acts as GATT server. 2. Remote acts as Gatt Client Use case: 1. Remote device starts BLE scan 2. Remote device connects to DUT 3. Remote device keeps on sending notifications to DUT Expected result: Connection should be active after 18 hours Observed Result: Connection is dropped after 18 hours due to l2c_link_timeout. Root Cause: L2CAP is not properly handling no idle timeout(0xFFFF) and 65535000 ms timer gets started after BLE connection, leading to connection getting dropped after 18 hours. Fix: If there is no L2CAP dynamic ccb and no idle timeout is configured for GATT or any other fixed channel, then cancel existing LCB timer. Test: No BLE disconnection seen after 18 hours Bug: 112249120 Change-Id: I58766564cf62efb7af0869035115459bae37c558
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"