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

Issue 807001 link

Starred by 1 user
Status: WontFix
Owner:
mlamouri@chromium.org
Closed: Jan 2018
Cc:
pnangunoori@chromium.org
█ sandeepkumars@chromium.org
nyerramilli@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Web Audio API produces no sounds whatsoever on Android

Reported by bitgr...@gmail.com, Jan 29 2018 
Steps to reproduce the problem:
1. Go to https://jsfiddle.net/3m59vvjt/
2. Press run
3. Hear no sound

What is the expected behavior?
A beep

What went wrong?
No sound on Android, no exceptions thrown. I have a device with Chrome 53 and it works there.

Did this work before? Yes Only tested in 53 and it worked

Does this work in other browsers? N/A

Chrome version: 64.0.3282.123  Channel: stable
OS Version: 6.0.1
Flash Version: 

How can't I find issues about this - doesn't anybody use WebAudio?
WebAudio fail Android.js
380 bytes View Download

Comment 1 by bitgr...@gmail.com, Jan 29 2018 

Works in mobile Firefox, not in Opera

Comment 2 by pnangunoori@chromium.org, Jan 30 2018

Labels: Needs-triage-Mobile

Comment 3 by pnangunoori@chromium.org, Jan 30 2018 

 Issue 807000  has been merged into this issue.

Comment 4 by sandeepkumars@chromium.org, Jan 30 2018

Cc: nyerramilli@chromium.org pnangunoori@chromium.org sandeepkumars@chromium.org
Components: Blink>WebRTC>Audio
Labels: hasbisect-per-revision FoundIn-66 FoundIn-59 FoundIn-58 FoundIn-57 FoundIn-56 FoundIn-55 FoundIn-61 Triaged-Mobile FoundIn-64 FoundIn-65 FoundIn-62 FoundIn-63 FoundIn-60 Target-66 RegressedIn-55
Owner: mlamouri@chromium.org
Status: Assigned (was: Unconfirmed)
Tested the issue in Android and able to reproduce the issue. 

Steps Followed:
1. Launched the Chrome 
2. Navigated to https://jsfiddle.net/3m59vvjt/
3. Did not heard the sound

Chrome versions tested:
64.0.3282.123

OS:
Android 6.0.1

Android Devices:
Samsung S7 6.0.1

Using the per-revision bisect providing the bisect results,
Good build: 55.0.2876.0
Bad build: 55.0.2877.0

You are looking for a change made after 422111(GOOD), but before 422112(BAD).

CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+/b121dd8b9380574db8d6ebee851c1dfd61369cda

From the CL's above, assigning the issue to the owner concerned.

@mlamouri: Could you please look into the issue, and assign it to concerned owner if this is not related your change.

Please navigate to below link for log's and video--
go/chrome-androidlogs/807001

Note: This issue is not observed in Desktop.

Thanks!!

Comment 5 by mlamouri@chromium.org, Jan 30 2018

Status: WontFix (was: Assigned)
This was on purpose: we require a user gesture for cross origin iframes in order to use autoplay. In trunk/Canary/Dev, the restrictions are different and similar on desktop and mobile.
►

Sign in to add a comment