| e90b45e001dcb32f7b59c5e449484759af782fef |
|
19-Apr-2017 |
Jakub Pawlowski <jpawlowski@google.com> |
Expose LE advertiser address for easier PTS tests (4/6)
This patchset adds a hidden method getOwnAddress, that lets app with
BLUETOOTH_PRIVILEGED permission to lear their own addreess. This is done
exclusively for PTS tests.
Bug: 35147497
Test: manual
Change-Id: I5ad554d872f2b772f2bf91642a9648c4018d935c
(cherry picked from commit 779b4fd786c571cb8013f4d94ddacfe7116fb05f)
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| a3129f158e446dae842922b68a350c10cdd28aaf |
|
31-Mar-2017 |
Jakub Pawlowski <jpawlowski@google.com> |
Bluetooth 5 advertising duration refactoring (1/4)
Expose both duration and maximum extended advertising events to limit
advertising time.
Test: manual
Bug: 30622771
Change-Id: I4475c322347899946b39e65026d8009e02c93759
(cherry picked from commit 5204c62f137de9b6c2834391fd329457d3fdbc84)
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| ff32af6dee78aea6889c9b381ff9278eccafcde3 |
|
18-Mar-2017 |
Jakub Pawlowski <jpawlowski@google.com> |
Bluetooth 5 AdvertisingSet implementation (4/4)
Test: manual
Bug: 30622771
Change-Id: Ie1c1588383a83296cabd29a0481f7d80a1168263
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| 16da9217c6e44e7b9bbe3a6c60c1e293d52c7223 |
|
12-Mar-2017 |
Jakub Pawlowski <jpawlowski@google.com> |
Bluetooth 5 AdvertisingSet implementation (3/4)
This patch wires up fist methods of AdvertisingSet, making it possible
to start advertising and stop advertising. It also replaces legacy
implemementation with calls to new implementation.
Bug: 30622771
Test: sl4a ConcurrentBleAdvertisingTest
Change-Id: I843d8fc12ba1928c87e256a0fb6d730c9fa200e6
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| e0750ca056c8561d4a5b7ea14430049bf1d82fc1 |
|
05-Dec-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Expose Bluetooth 5.0 properties to JNI
Bug: 30622771
Test: sl4a ConcurrentBleAdvertisingTest
Change-Id: I6185e6926e7363824aa573c7d65f7ab66f954e52
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| b324a8d0b719065cec10379ad6855852724d9004 |
|
10-Dec-2016 |
Pavlin Radoslavov <pavlin@google.com> |
Replace usage of "vector<>" with "std::vector<>"
This change is needed so we can remove the last instances
of "using std::vector" statements in hardware/libhardware.
Test: code compilation
Change-Id: I6a9fc62152371d1bba6ead71e7ff8c2610799637
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| 911d1ae03efec2d54c3b1b605589d790d1745488 |
|
29-Nov-2016 |
Myles Watson <mylesgw@google.com> |
Apply clang-format to the rest of the tree
find * | grep "\.[ch]" | xargs clang-format --style=file -i
Test: mma -j32
Change-Id: I6fcc9862bb7bc07c2a367ca58fef2b3cd27a6f05
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| a75087effcc8b4a5869fb1673d43b0b9ff6fb8f1 |
|
17-Nov-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Move startAdvertising() logic into native code (2/3)
AdvertiseManager.startAdvertising() was implemented in Java layer for
historical reasons. Now that we have nice native callbacks and tests,
it can be moved into native code, where it will be shared between
Android daemon and bluetoothtbd.
Bug: 30622771
Test: native tests added to cover startAdvertising
Change-Id: Idf5d3c53b6ad21d8c7e239b5b150b88e073bb709
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| d964cf944e23470d696177fb2ddf8df3684290b8 |
|
03-Nov-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Unify advertising API (1/3)
This patch unifies advertising API. On startup, if VSC multi advertising
is avaliable, it will be used, otherwise
BleAdvertiserLegacyHciInterfaceImpl will be used, which provides one
advertising instance.
Test: sl4a tests are passing, all proper tests updated accordingly
Change-Id: I73753962e3a33a980e8a9a1174c8d88611a47e6b
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| a8d73ef2f3d2c9b344162cb15e9dd054c28761de |
|
31-Oct-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Move start advertise method to advertising interface (3/3)
Advertising related code should be exposed through
BleAdvertiserInterface. Move client.listen function into this interface.
Remove reduntant clientif parameter.
Bug: 30622771
Bug: 24099160
Test: no tests necessary
Change-Id: Icc865c062e3d7c4b83bbeea6ff5b08bd2c1c4d9a
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| b209938ba1be00636c77ac1acaab5e736fa7e9fd |
|
31-Oct-2016 |
root <root@pawlowski-linux.mtv.corp.google.com> |
Fix AdvertiseDataParsing test
Test: run LowEnergyAdvertiserPostRegisterTest.AdvertiseDataParsing
Change-Id: Ib9f4dbc1079ae289cc5eeaee9ca7050d308a4ab0
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| c3f6a51615c4f26bce0b8b6e16757610dbd0b45b |
|
27-Oct-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Separate LE scanner and GATT client BTIF interfaces (3/3)
In order to properly separate low level structures associated with LE
scanner and GATT client, their interfaces must be separated first.
Test: sl4a BleScanApiTest
Bug: 30622771
Change-Id: If804632c8e4b08fd15d5b847c7838822cf98d79f
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| 0ecddf398c92324e15a53c9d410646fd7a494b96 |
|
19-Oct-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Change how Advertise Data is passed to BTIF (2/3)
The way that AD data is passed right now put some additional
limitations, i.e. only one manufacturer specific data can be set, or
only one service UUID. By moving AD generation to upper layers, aother
set of limitations is removed.
Test: Covered by BleAdvertiseApiTest sl4a test
Bug: 30622771
Change-Id: Iee48ea30ec4c055eaa1ad0b1678686d261106e76
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| 74ef54b440dc50bb25f587783d80fe5a37070e4a |
|
07-Oct-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Convert advertising HAL from struct into class (3/3)
Bug: 30622771
Test: all related tests were updated
Change-Id: I9695284ae249fa427ae4b2f3e9649da951102c6c
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| 73679d01c70fe84921fc4718e99d4b02af8cc5a9 |
|
18-Aug-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Bluetooth: split setting params and enabling advertising (3/3)
Proper order of commands when starting advertising:
* set parameters
* set data
* enable advertising
This cannot be achieved when setting advertising parameters and enabling
advertising is put together in one function. Enabling before setting
data might cause first advertisements to be empty. If a device with
hardware filter pick up such advertisement, it might fail to properly
recognize our device.
Bug: 30622771
Bug: 19372779
Change-Id: I3a2c1171e301ecfd7cbf1cb8b86cfda0e5fc2382
/system/bt/service/test/low_energy_advertiser_unittest.cc
|
| 67d5a2523314d9757b2472c3e828dbc1015df4fe |
|
13-Jul-2016 |
Jakub Pawlowski <jpawlowski@google.com> |
Separate advertiser from GATT client (4/4)
Bug: 30622771
Change-Id: I761f0bff09aec1047bd512915960021e4fbdc0c8
/system/bt/service/test/low_energy_advertiser_unittest.cc
|