Bluetooth audio stalled after suspend-resume |
|||||||||
Issue descriptionAudio playback to a Bluetooth headset (BH-M20C) on Kevin stalls after multiple suspend/resume cycles (in an attempt to reproduce b/63782186). Build: 9799.0.2017_08_01_1333 (Test Build - mka) developer-build kevin: Steps: 1) Pair the Bluetooth headset 2) Perform multiple suspend/resume cycles 3) play /usr/share/chromeos-assets/input_methods/input_tools/sounds/audio_initiate.wav Expected result: audio_initiate.wav is played on the BT headset Actual result: play blocks, has to be terminated with kill -9 According to the GUI the headset is paired and audio output is routed to Bluetooth. The blue LED on the headset blinks slowly, which indicates that the headset hasn't switched off. bluetoothctl shows information on available BT devices, so apparently communication with the BT controller is working. [BH-M20C]# info Device 00:6A:8E:16:E6:D1 Name: BH-M20C Alias: BH-M20C Class: 0x240404 Icon: audio-card Paired: yes Trusted: yes Blocked: no Connected: yes LegacyPairing: no UUID: Headset (00001108-0000-1000-8000-00805f9b34fb) UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb) UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb) UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
,
Aug 3 2017
Reproduced again, it took a few dozen suspend/resume cycles.
,
Aug 3 2017
Reproduced with kevin-release/R60-9592.73.0, ~40 suspend/resume cycles. Disabling and re-enabling Bluetooth does not fix the problem, nor does routing audio output to the internal speaker.
,
Aug 4 2017
,
Aug 7 2017
,
Aug 24 2017
,
Oct 19 2017
mka@ -- Do you still see the issue on latest builds? I have tried on M-63 10032.7.0 build on kevin and haven't seen the issue
,
Oct 19 2017
I haven't tried it lately. Through how many iterations did you go?
,
Oct 19 2017
Thank you for providing more feedback. Adding requester "pbathini@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 19 2017
I have tried more than ~10 times.
,
Oct 20 2017
,
Oct 20 2017
Since pbathini@ can't reproduce this with ~10 suspend/resume cycles, we'll close this as won't fix. Please re-open the bug if you reproduce this.
,
Oct 23 2017
According to my earlier comment #3 it took 40 iterations to reproduce this, so 10 suspend/resume cycles are not enough to be confident this is fixed. Supposing a repro rate of 1/40 (or 2.5%) there is a 78% chance that the issue does not occur in 10 cycles.
,
Nov 20 2017
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by mka@chromium.org
, Aug 3 2017