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

Issue 703301 link

Starred by 2 users
Status: WontFix
Owner:
█ cederberg@google.com
Last visit > 30 days ago
Closed: Mar 2017
Cc:
hychao@chromium.org
█ bkemler@chromium.org
█ royans@chromium.org
█ mnilsson@chromium.org
harpreet@chromium.org
█ cederberg@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Dual Jabras (Two Jabra Speakers) are treated as single device

Project Member Reported by dsunk...@chromium.org, Mar 20 2017 
Chrome Version: 57 / 9202.54.0 / 57.0.2987.115
OS: Chrome
Google Hangouts: 1.3.103.1
WCS: chat_web_connection_server_20170313.05_p0
Device: Panther (Could be common across all cfm devices)

What steps will reproduce the problem?
(1) Clear tpm and run the OOBE setup.
(2) Both the jabras are detected as one. OOBE test run on only one jarba speaker.
(3) Join a hangouts session. 
(4) From the app, increase or decrease the volume using hotrod remote, only one of the speaker's volume gets changed. 

Note: Setup has been tested with both below:
1. Two Jabras connected to USB ports on panther directly.
2. Two Jabras connected on C2G cable (usb hub)
3. One Jabra plugged in directly and other using C2G hub. 

On all the setups, the results are same.

What is the expected result?
OOBE should detect both the speakers. Volume sync should be there on both the speakers.

What happens instead?
Can control volume on only one speaker. 

This is a regression as one of the below defects were verified on M57 release earlier. 

Bugs related to the issue: 
https://buganizer.corp.google.com/issues/33468729
https://buganizer.corp.google.com/issues/31035967
https://bugs.chromium.org/p/chromium/issues/detail?id=623272
log-032017-120656.tar.gz
693 KB Download

Comment 1 by hychao@chromium.org, Mar 20 2017 

According to audio_diagnostic log, only one of the Jabra device is in 'active' state. So I think it's an issue in Hotrod app layer.

Comment 2 by harpreet@chromium.org, Mar 20 2017

Cc: royans@chromium.org
Labels: ReleaseBlock-Stable
Dinesh, does this repro across all CFM devices?


Marking this as RBS for CFM devices.

Comment 3 by harpreet@chromium.org, Mar 20 2017

Labels: -ReleaseBlock-Stable
Nevermind the RBS since it looks like an app side issue.

Comment 4 by dsunk...@chromium.org, Mar 20 2017 

Yes, this happens on Guado as well. 

But when further tried to repo this issue, it looks like the issue is with Meet App (Thror UI). 
When I disabled the setting in admin page to launch hangouts app at startup, the issue is not seen. 

Jabras are detected separately on OOBE screen. But when we assign Meet app and then on the screen we navigate to Hangouts app, the issue exists for the first time. When we join the call for second time (without rebooting), using hangouts two jabras are detected fine.
MeetApp_Issue.png
132 KB View Download

Comment 5 by cederberg@google.com, Mar 21 2017

Owner: cederberg@google.com
I'll look into this, seems like a frontend bug though.

Comment 6 by abodenha@chromium.org, Mar 21 2017

Status: Assigned (was: Untriaged)

Comment 7 by cederberg@google.com, Mar 23 2017

Status: WontFix (was: Assigned)
Yup. Frontend issue most likely as I can repro on M56 (9000.80) as well as M57 (9202.54). Closing this and tracking it in http://b/36550709
►

Sign in to add a comment