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

Issue 780693 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Testing chromebox using with analog speaker

Project Member Reported by cychiang@chromium.org, Nov 2 2017

Issue description

This is to prevent regression like 775486.
The issue is that ALC283 codec on Chromebox output is not stable so analog speaker plays the noise while there is no audio playing.
It will be hard to test it using chameleon since the noise might not be loud enough to be picked up or clearly identified by microphone.

Kalin, can we add this speaker model into a test item of manual testing ?
We can work on adding the test in the future.
The speaker model is the Logitech one we use in the audio box.

Thanks!
 
There are 2 kinds of analog speaker noise that might happen due to power_save ( issue 775486 ):

1. pop/click sound when device is opened/closed. There's a timeout setting so the pop sound happens after #timeout seconds after device is closed.

2. A hum noise keeps coming out from speaker. This happens when the device is not in use.

Comment 2 by ka...@chromium.org, Nov 2 2017

The user states "I am using an "old" Dell speaker bar which mounts under the monitor", and no specific model is referenced in the bug.
I'll have such powered analog / audio jack speaker(s) be used in FullRelease testing, and reboot scenario should catch this. Having this is mostly a last resort manual verification - there should be a different type of test to check for the solution proposed in  issue 775486 , i.e leaving power save mode disabled on devices with no battery.
Labels: -Pri-2 Pri-3
Owner: cychiang@chromium.org
I'm also leaning towards not to add any manual testing because it doesn't scale. Is there any other idea of automatically testing?
I don't think that kind of noise can be picked up clearly by chameleon
microphone. If speaker volume is not turned loud enough, it is like
background noise. If speaker volume is turned too loud, it might break
current internal microphone test.
Also, we don't know disabling power save mode leads to this kind of noise
until user reports.

Since we already have headphone test in the manual verification, replacing
headphone with 3.5mm speaker, or adding 3.5mm speaker for Chromebox seems
to be a reasonable effort.
Thanks!
Owner: ka...@chromium.org
I talked to Jimmy. If we want to test this automatically, we need a box that can shield the noise from the environment. Before we have it, let's cover this in manual testing.

Sign in to add a comment