- May 12, 2023
-
-
Treehugger Robot authored
-
Sal Savage authored
-
David Duarte authored
* changes: Move android.hardware.bluetooth.audio-V3-ndk to static_libs in tests Remove unused android.hardware.bluetooth.audio-V3-ndk in tests Remove android.hardware.bluetooth.audio-V3-ndk from defaults
-
Himanshu Rawat authored
-
Nathan Muggli authored
-
Michał Narajowski authored
-
Chris Manton authored
Bug: 281498218 Test: net_test_main_shim Change-Id: I5212fa766c6f709b708fa3f3f65d0e2b71bfa6aa
-
Michał Narajowski authored
When switching a set of earbuds from LeAudio to A2DP this is the same as disconnecting from LeAudio device and connecting to A2DP device so the new tests are verifying the behavior of the ADM when disconnecting one or both LeAudio devices. Bug: 278761210 Test: atest BluetoothInstrumentationTests Tag: #feature Change-Id: Ie708737c760862af8d0b100134a53c917077b124
-
David Duarte authored
android.hardware.bluetooth.audio-V3-ndk.so is not present on the system image if neither the APEX or the HAL bring it in. Make the test able to work on system image without this library by linking it statically. Bug: 279502784 Fix: 267212763 Test: mma Change-Id: I3ea3fc11d57b7c8149c87608d2149dbe306a5cb8
-
David Duarte authored
Bug: 279502784 Bug: 267212763 Test: mma Change-Id: Idbe70708f65a1e8d7abf2715f3d2ac694e8a2a98
-
Michał Narajowski authored
Previously the TBS access request resulted in no response from the stack which resulted in ATT Timeout. With this change we respond with insufficient authorization. Bug: 263372634 Test: manual and atest BluetoothInstrumentationTests Tag: #feature Change-Id: I8e1a8e2ff6322099d8ccca44ddd47b7286703a16
-
Kyunglyul Hyun authored
-
- May 11, 2023
-
-
William Escande authored
-
Treehugger Robot authored
-
Stephanie Bak authored
-
Sal Savage authored
Problem: The Now Playing List is invalidated when the addressed player changes. This can happen on initial connection, when the Available Players change and a player ID is reused, or directly as a result of an Addressed Player Changed event. Typically, both events come in one after the other, causing one Now Playing list fetch, immediately followed by another. As it stands, the first request always finishes, and the future ones are ignored, despite the list getting cleared/uncached part-way through. This leads to missing data and/or incorrect lists, which can have downstream impact on playing items from the Now Playing List as well. Solution: Let another more recent fetch request for the Now Playing List invalidate the previous requsst and cause the download process to restart. These downloads are typically quick and the wasted cycles downloading sometimes-old-something-invalid data are small, or necessary. Tag: #stability Bug: 177004421 Test: atest AvrcpControllerStateMachine.java Change-Id: Idcc0a21c966622bfd442ae3b2c7cf1d8f06e75d3
-
William Escande authored
-
Treehugger Robot authored
-
Etienne Ruffieux authored
-
Treehugger Robot authored
-
Treehugger Robot authored
-
Treehugger Robot authored
-
Henri Chataing authored
* changes: RootCanal: Implement LL tests for Phy update procedure RootCanal: Implement the LL phy update procedure
-
Treehugger Robot authored
-
David Duarte authored
Bug: 279502784 Bug: 267212763 Test: Presubmit Change-Id: Ibb11f95739fcd86d5ec7239c747449d5cf86724b
-
Eric Shih authored
Bug: 281970923 Test: atest GoogleBluetoothInstrumentationTests Change-Id: I20eb76aad6ecdcdf4cc47289735d72d5c1e2da1f
-
Yun-hao Chung authored
-
Treehugger Robot authored
-
Kyunglyul Hyun authored
When two apps try to create bond to the same remote device, the second call would return false, even when it didn't fail. This is not consistent with the Javadoc, which states that the method should return true if bonding is began. This change makes the method return true when it's already bonding, which allows callers to expect a BOND_STATE_CHANGED intent to be broadcast when the bond is complete. Bug: 269056263 Test: atest BluetoothInstrumentationTests Change-Id: Ic30bb010c09738eecfc8a0285accb4db0ddeeefc
-
Hyundo Moon authored
Currently the BT icon is a private resource in frameworks/base, and it is being used from BT module via private access (@*android). As a result, the icon is not properly shown if the resource ID becomes different between when mainline module is built and when it is run. This CL copies BT icon into BT module and uses it. As the tint color in bt_share.xml is also private, this CL uses a blue color from official Bluetooth website. Bug: 279384742 Test: Sharing via bluetooth shows the correct icon Change-Id: I9d2ac626f294dea17eecebfd70cd1e7a2ae01cd0
-
Duo Ho authored
Test: avatar run --mobly-std-log --include-filter 'ASHATest' Bug: 254077091 Change-Id: Ibda0dbff53344ffb7e2c8158fb4ebc78193482ef
-
Stephanie Bak authored
Bug: 280675681 Test: manual Change-Id: I4b2ec50d79667e9c1c921edd0adb7118725498b1
-
Jack He authored
Bug: 281686068 Test: atest CtsRootBluetoothTestCases:android.bluetooth.cts_root.BluetoothCddRootTest Change-Id: Ifaae28f27c602f5ba44871e2b2107e461934ba15
-
Sal Savage authored
Tag: #stability Bug: 281902051 Test: atest BluetoothInstrumentationTests Change-Id: Ifca537dea679c8f74be9b4b23f50ad5a04b38bbc
-
Sal Savage authored
This test was disabled previous due to a bug, but that bug has been fixed. The @Ignore was not removed. This change removes the annotation so the test can run again Tag: #stability Bug: 260948676 Test: atest BluetoothInstrumentationTests Change-Id: I3ca09ba41681b374c230c3ef8ae6e5d6206a2fc8
-
Qiao Yang authored
-
Jack He authored
-
- May 10, 2023
-
-
Yuyang Huang authored
-
Treehugger Robot authored
-
Treehugger Robot authored
-