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

Issue 695671 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

CRAS: device is not running but server thinks it is running

Project Member Reported by cychiang@chromium.org, Feb 23 2017

Issue description

From feedback

https://feedback.corp.google.com/#/Report/53852619055

image: 9000.87.1 (Official Build) beta-channel kevin

The symptom is no sound played to headphone.

I checked the log and found that alsa device was not playing.
However, the state variable maintained in cras thought device was playing.
So, cras kept sending samples to device, and samples kept accumulated in the device buffer.
I checked the code path but could not figure out how this can happen.
There was a suspend/resume in the log.
Not sure if suspend/resume might cause this.

Hi Kalin, have you ever noticed this kind of issue ?
Could QA try to reproduce this issue on kevin?

Thanks!
 

Comment 1 by ka...@chromium.org, Feb 24 2017

Cc: sontis@chromium.org
We have not observed such outcome, but we usually do not do long term testing.

Feedback note:
Listening to Google Play, closed Kevin without sleep/locking.  Headphones still in jack & attached to my head.  I think I reopened it once en route to a building and it was fine (music played in headphones) but now there's no sound.


Sridhar,
lets have a Kevin device on the following scenario:
1) Plug headphones
2) Open few browser tabs, with one of them streaming music
3) After some time, close the lid(suspend should happen)
4) After some time open the lid. Check for audio playing on headphones and close the lid again(suspend should happen)
5) After some time open the lid again. Check for the audio. Is it missing.

'some time' could be like short(e.g. 10 sec) or longer(e.g. 5-to-10 min) period of time

Comment 2 by son...@google.com, Feb 24 2017

Not able to reproduce this issue on build 9202.37.0_kevin

Comment 3 by son...@google.com, Feb 27 2017

Not able to reproduce this issue on M56 stable build 9000.87.1_kevin

Comment 4 by son...@google.com, Feb 27 2017

Owner: ----

Sign in to add a comment