| commit | 1e148c3fa5711700e87743394138559b600579b8 | [log] [tgz] |
|---|---|---|
| author | sravan voleti <quic_svoleti@quicinc.com> | Fri Jan 17 14:14:37 2020 +0530 |
| committer | sravan voleti <quic_svoleti@quicinc.com> | Fri Jan 17 14:16:39 2020 +0530 |
| tree | 280c14d03925b5c6b902d880ed85c8bde4e7bce3 | |
| parent | 0083002b344ff13afd86ef53232ca1b5948df334 [diff] |
Hid: Fix connection issue with legacy mouse
use case:
1) Pair and connect mouse from DUT
2) Unpair mouse from DUT UI
3) Try to pair from mouse, SDP connection from dut
should fail during pairing.
4) Scan the mouse from DUT and initiate pairing.
Observed Results:
Pairing stuck in bonding state.
Root cause:
On sdp failure cases, HID incoming connection flags not cleared
and leading to HID connection and pairing failure in next outgoing pairing.
Fix:
Reset hid incoming connection flags when sdp fails,
to fix connection issue with specific HID mouse.
Fixes: 147856205
Test: Tested above use case with legacy mouse, issue not observed.
Change-Id: I11b5d52a78f861cc270d0736c912cd40f1b76d6d
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"