New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 591772 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Closed: Mar 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug

Blocked on:
issue 308143



Sign in to add a comment

[tricky] 3.5mm headphone doesn't play audio after unplug > suspend > replug > resume

Project Member Reported by helenzhang@google.com, Mar 3 2016

Issue description

Google Chrome : 50.0.2661.11 (Official Build) dev (64-bit)
Platform : 7978.4.0 (Official Build) dev-channel tidus 

What steps will reproduce the problem?
1. Sign in with hdmi-hidmi connected 
2. Plug in 3.5mm headphone 
   make sure audio can be heard via 3.5mm headphone 
3. Unplug 3.5mm headphone 
4. Run "powerd_dbus_suspend"
5. Plug 3.5mm headphone 
6. Resume ( press any key 0 

What is the expected output? 
Audio plays via 3.5 mm headphone 

What do you see instead?
Audio can not be heard via 3.5 mm headphone
Audio plays via HDMI (see screenshot attached) 

2/2 
starting from step 6, unplug-plug will never make 3.5mm heaphone outout selected, Mic jack however is selected fine. 
- Unable to reproduce the issue on veyron-jaq. 

Feedback report: 
https://feedback.corp.google.com/product/208/neutron?lView=rd&lRSort=1&lRFilter=1&lReportSearch=user:helenztest&lROrder=2&lReport=6824844504
 
We just reverted hychao's cl for stable device id feature in R50 yesterday. Please wait for the new build and test it again.
additional observation:
- plug hdmi
- plug usb heaphone 
- plug in 3.5mm headphone 
result : 
- audio output is NOT switched from usb headphone to 3.5mm headphone 
- removing usb headphone, then 3.5mm headphone is selected  

Comment 4 by ka...@chromium.org, Mar 3 2016

Cc: keta...@chromium.org
Helen, did you selected manually (at any point after recovery) any of the audio nodes in the menu? If yes - wait for a newer build so the reverting change takes effect.

Helen, can you see if any other test scenarios, but with single peripheral make this issue to reproduce? I am wondering if more simple UX is affected.

Jenny, this build is potential dev-channel candidate. Should this be expected on all platforms?
+ketakid@


#3: 
- It's not manually selected
- Tricky is a box, hdmi has to be connected.
- Jaq is non-box device. it does not have the issue.  

correction: #5 is replied to #4

Comment 7 by shrawan@google.com, Mar 3 2016

Seeing same issue on panther with M-50(7978.4.0) too.
helenzhang@, I think the reverted cls are not picked up in M-50(7978.4.0). Wait for another build.
JennyZ@ is this beta blocking? are we simply waiting to confirm that the CLs have been reverted?
Owner: jen...@chromium.org
Status: Assigned (was: Untriaged)
Assigning to jennyz@.
Jennyz@ Please update with latest status since this bug has not been updated in 5 days.
Blockedon: 308143
Labels: -M-50 M-51
Status: Fixed (was: Assigned)
Tried this on R51-8001.0.0, is fixed. The fix of the issue needs the audio stable device id feature implemented for R51,  issue 308143 . So it won't be fixed in R50. 
Status: Verified (was: Fixed)
Verified ChromeOS 7978.10.0 / 50.0.2661.20, 3.5mm headset works with no issue. 

Sign in to add a comment