| 81e7418b513f391d60019dd3a21ceebe9ca1a81c |
|
19-Aug-2015 |
Hsin-Yu Chao <hychao@chromium.org> |
CRAS: fix various warnings reported by valgrind
BUG=chromium:658162
TEST=emerge valgrind and deploy to DUT. On DUT do
'stop cras' and then 'valgrind /usr/bin/cras' and
watch the output. Use cras_test_client to select
input and output node, playback and record. Connect
BT headset and test A2DP and HFP. Verify everthing
above produces no valgrind warning.
Change-Id: I8c1bd63f9b29427387dcac5388d5be129472e80c
Reviewed-on: https://chromium-review.googlesource.com/401146
Commit-Ready: Hsinyu Chao <hychao@chromium.org>
Tested-by: Hsinyu Chao <hychao@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
/external/adhd/cras/src/server/cras_bt_adapter.c
|
| 03d0bc67305029a07e5cfa3ea762c18d16718afc |
|
24-Aug-2016 |
Hsin-Yu Chao <hychao@chromium.org> |
CRAS: bt_device - Associate with adapter's object path
An issue is observed when the adapter physically got unplugged
and then plugged. This scenario triggers all managed BT objects be
reset and recreated in order: bt devices first, and then adapter at
last. This causes bt device points to NULL adapter because the adapter
wasn't ready while the device was recreated.
Fix this issue by keeping the adapter object path string in BT device
when it's created. And use it as key to look up real adapter when
needed.
BUG=chrome-os-partner:55214
TEST=Difficult to reproduce on built-in adapter, so use external
BT USB adapter instead. Use bluetoothctl to do following:
1. power off built-in adapter.
2. select default adapter to external one.
3. pair/connect a BT headset, and stream audio
4. Unplug external BT adapter, then plug it in again.
5. Wait for BT headset to reconnect, and use it for audio input(HFP)
6. Verify HFP audio still stream.
Change-Id: Ie508be2a97e5a10f8ebcc8d00e523ccdad25ca75
Reviewed-on: https://chromium-review.googlesource.com/374302
Commit-Ready: Hsinyu Chao <hychao@chromium.org>
Tested-by: Hsinyu Chao <hychao@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
/external/adhd/cras/src/server/cras_bt_adapter.c
|
| 1668d94b1813ef49aae6dfce1d59fbeeafbf1b80 |
|
11-Feb-2015 |
Hsin-Yu Chao <hychao@chromium.org> |
CRAS: bt_adapter - Query adapter bus type
For bluetooth audio over SCO, choosing the MTU value significantly
affects the audio quality. Before this change we set the MTU value
to 48 bytes fixed for all platfrms, however this number is not working
well for adapters of non-USB bus type, SDIO for example.
Add the API to cras_bt_adapter to query the bus type, later change
will use it to decide the MTU value to use.
BUG=chrome-os-partner:35957
TEST=Apply full patch set, test bluetooth headset on
Daisy, Nyan, Rambi, Link.
Change-Id: I5044ea61354ae9e31c730680615ea345cf1c0349
Reviewed-on: https://chromium-review.googlesource.com/249080
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Tested-by: Hsinyu Chao <hychao@chromium.org>
Commit-Queue: Hsinyu Chao <hychao@chromium.org>
/external/adhd/cras/src/server/cras_bt_adapter.c
|
| a67190546dcf8a283d9474c5cab24d7a152bf7f8 |
|
01-Mar-2013 |
Scott James Remnant <keybuk@chromium.org> |
CRAS: bluetooth - rewrite for BlueZ 5.2
BlueZ 5.2 brings us support for Bluetooth 4.0 and LE, but at the cost
of a different D-Bus API. It was easier to write fresh clean code
for the new API and remove the old code than incrementally refactor.
BUG=204431
TEST=build and run cras, verify logs
Change-Id: I3147aa7d59535b743425c7d48737f8c70614e5cd
Signed-off-by: Scott James Remnant <keybuk@chromium.org>
Reviewed-on: https://gerrit.chromium.org/gerrit/45103
Reviewed-by: Dylan Reid <dgreid@chromium.org>
/external/adhd/cras/src/server/cras_bt_adapter.c
|