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

Issue 670184 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

[Kevin] Re-plugged headphone (Bose QC15) did not help to force audio via headphone instead of speaker.

Project Member Reported by chinyue@chromium.org, Dec 1 2016

Issue description

Feedback report ID 17243135921
CHROMEOS_RELEASE_VERSION	8872.56.0


The --dump_s output shows that the headphone (Bose QC15) is not plugged.


=== cras_test_client --dump_server_info ===
System Volume (0-100): 100 
Capture Gain (0.00 - 0.00): 20.00dB 
User muted: Not muted
Output Devices:
	ID	Name
	9	rk3399-gru-sound: :0,3
	7	rk3399-gru-sound: :0,2
	5	rk3399-gru-sound: :0,0
Output Nodes:
	Stable Id	 ID	 Vol   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(519731ad)	9:0	  100       no	            no	         0        	HDMI             HDMI
	(2ba59278)	7:0	  100       no	            no	         0        	HEADPHONE        Headphone
	(72a57953)	5:0	   24      yes	            no	1479932555        	INTERNAL_SPEAKER*Speaker
Input Devices:
	ID	Name
	10	rk3399-gru-sound: :0,4
	8	rk3399-gru-sound: :0,2
	6	rk3399-gru-sound: :0,1
	4	Post DSP Loopback
	3	Post Mix Pre DSP Loopback
Input Nodes:
	Stable Id	 ID	Gain   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(8b6a9a88)	10:0	    0      yes	            no	1479932555        	HOTWORD          Wake on Voice
	(5eb817e4)	8:0	    0       no	            no	         0        	MIC              Mic
	(30b0c661)	6:0	    0      yes	            no	1479932555        	INTERNAL_MIC    *Internal Mic
	(8c74f766)	4:0	    0      yes	            no	         0        	POST_DSP_LOOPBACK Post DSP Loopback
	(8a04af91)	3:0	    0      yes	            no	         0        	POST_MIX_LOOPBACK Post Mix Pre DSP Loopback
Attached clients:
	ID	pid	uid
	5	1491	1000
	7	27850	1000
Num active streams: 1
Last audio active time: 944, 839467791

 
I just tried my QC15 on Kevin, and it was detected correctly.

tringuyen@, is it possible for you to find another Kevin and do some cross-testing?

Comment 2 by dgreid@chromium.org, Dec 14 2016

Owner: nnag...@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 3 by nnagpal@google.com, Dec 14 2016

@dgreid ,is that issue related to ARC++ or chrome web page?

Comment 4 by dgreid@chromium.org, Dec 14 2016

This isn't related to Android.  It just needs to be checked on a few Kevins.

I accidentally assigned this to you, feel free to find another to check it out.

Thanks!
Let me find another Kevin to re-test and provide update.

Comment 6 Deleted

Comment 7 by nnagpal@google.com, Dec 14 2016

Cc: rohi...@chromium.org vsu...@chromium.org
Owner: ----
By mistake I have assigned to avkodipelli so deleting the comment #6


I tested the QC15 on the second Kevin running YT video and same issue, no difference.  New feedback filed under my LDAP. 

Comment 9 by dgreid@chromium.org, Dec 15 2016

Owner: chinyue@chromium.org
From the CRAS log, it says no headphone is plugged


=== cras_test_client --dump_server_info ===
System Volume (0-100): 100 
Capture Gain (0.00 - 0.00): 20.00dB 
User muted: Not muted
Output Devices:
	ID	Name
	9	rk3399-gru-sound: :0,3
	7	rk3399-gru-sound: :0,2
	5	rk3399-gru-sound: :0,0
Output Nodes:
	Stable Id	 ID	 Vol   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(519731ad)	9:0	  100       no	            no	         0        	HDMI             HDMI
	(2ba59278)	7:0	  100       no	            no	         0        	HEADPHONE        Headphone
	(72a57953)	5:0	   39      yes	            no	1481758438        	INTERNAL_SPEAKER*Speaker
Input Devices:
	ID	Name
	10	rk3399-gru-sound: :0,4
	8	rk3399-gru-sound: :0,2
	6	rk3399-gru-sound: :0,1
	4	Post DSP Loopback
	3	Post Mix Pre DSP Loopback
Input Nodes:
	Stable Id	 ID	Gain   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(8b6a9a88)	10:0	    0      yes	            no	1481758438        	HOTWORD          Wake on Voice
	(5eb817e4)	8:0	    0       no	            no	         0        	MIC              Mic
	(30b0c661)	6:0	    0      yes	            no	1481758438        	INTERNAL_MIC    *Internal Mic
	(8c74f766)	4:0	    0      yes	            no	         0        	POST_DSP_LOOPBACK Post DSP Loopback
	(8a04af91)	3:0	    0      yes	            no	         0        	POST_MIX_LOOPBACK Post Mix Pre DSP Loopback
Attached clients:
	ID	pid	uid
	1	1440	1000
	3	14257	1000
Num active streams: 1
Last audio active time: 123, 912265666



However I found something interesting from mixer controls state.


The following controls' state from the report:

numid=70,iface=MIXER,name='Headphones Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off
numid=66,iface=MIXER,name='Headphone Switch'
  ; type=BOOLEAN,access=rw------,values=2
  : values=on,on
numid=53,iface=MIXER,name='DAC Soft Mute Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off
numid=71,iface=MIXER,name='Speakers Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=on


And the controls on my machine WITHOUT headphone plugged:


numid=69,iface=MIXER,name='Headphones Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off
numid=66,iface=MIXER,name='Headphone Switch'
  ; type=BOOLEAN,access=rw------,values=2
  : values=off,off
numid=53,iface=MIXER,name='DAC Soft Mute Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=on
numid=70,iface=MIXER,name='Speakers Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=on



And the controls on my machine WITH headphone plugged:


numid=69,iface=MIXER,name='Headphones Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=on
numid=66,iface=MIXER,name='Headphone Switch'
  ; type=BOOLEAN,access=rw------,values=2
  : values=on,on
numid=53,iface=MIXER,name='DAC Soft Mute Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off
numid=70,iface=MIXER,name='Speakers Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off



The control state from the report is inconsistent so I guess something's wrong with the low-level jack detection.

Cc: ka...@chromium.org
To verify if Kevin cannot detect headphone insert we need to run the evtest program and that requires test image.

kalin@ I'm not in MTV, could you please help provide a Kevin with test image for tringuyen@ ?

On test image we can run evtest from console and select '5' for rk3399-gru-sound Headset Jack
And then plug headphone to see if it's been detected correctly.


localhost ~ # evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:	cros_ec
/dev/input/event1:	cros_ec_buttons
/dev/input/event2:	Atmel maXTouch Touchscreen
/dev/input/event3:	Atmel maXTouch Touchpad
/dev/input/event4:	hid-over-i2c 2D1F:0163
/dev/input/event5:	rk3399-gru-sound Headset Jack
/dev/input/event6:	gpio-keys
Select the device event number [0-6]: 5
Input driver version is 1.0.1
Input device ID: bus 0x0 vendor 0x0 product 0x0 version 0x0
Input device name: "rk3399-gru-sound Headset Jack"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 114 (KEY_VOLUMEDOWN)
    Event code 115 (KEY_VOLUMEUP)
    Event code 226 (KEY_MEDIA)
    Event code 582 (?)
  Event type 5 (EV_SW)
    Event code 2 (SW_HEADPHONE_INSERT)
    Event code 4 (SW_MICROPHONE_INSERT)
    Event code 6 (SW_LINEOUT_INSERT)
Testing ... (interrupt to exit)
Event: time 1481775881.784236, type 5 (EV_SW), code 2 (SW_HEADPHONE_INSERT), value 1
Event: time 1481775881.784236, -------------- SYN_REPORT ------------
Event: time 1481775885.123730, type 5 (EV_SW), code 2 (SW_HEADPHONE_INSERT), value 0
Event: time 1481775885.123730, -------------- SYN_REPORT ------------

Kevin took an update this morning and the Bose QC15 is working fine now.  I filed feedback right after it worked just in case the team wants to compare the update data vs other feedbacks I have filed.
This might be irrelevant but I can confirm that my QC25 headphones work with the latest M56 Kevin version.
The latest feedback report: https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=50302073916


The mixer control states are consistent:


numid=70,iface=MIXER,name='Headphones Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=on
numid=66,iface=MIXER,name='Headphone Switch'
  ; type=BOOLEAN,access=rw------,values=2
  : values=on,on
numid=53,iface=MIXER,name='DAC Soft Mute Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off
numid=71,iface=MIXER,name='Speakers Switch'
  ; type=BOOLEAN,access=rw------,values=1
  : values=off


However I found it interesting that the headphone is detected as LINEOUT:


=== cras_test_client --dump_server_info ===
System Volume (0-100): 100 
Capture Gain (0.00 - 0.00): 20.00dB 
User muted: Not muted
Output Devices:
	ID	Name
	9	rk3399-gru-sound: :0,3
	7	rk3399-gru-sound: :0,2
	5	rk3399-gru-sound: :0,0
Output Nodes:
	Stable Id	 ID	 Vol   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(519731ad)	9:0	  100       no	            no	         0        	HDMI             HDMI
	(2ba59278)	7:0	  100       no	            no	         0        	HEADPHONE        Headphone
	(f023442f)	7:1	   75      yes	            no	1481822518        	LINEOUT         *Line Out
	(72a57953)	5:0	   27      yes	            no	1481822444        	INTERNAL_SPEAKER Speaker
Input Devices:
	ID	Name
	10	rk3399-gru-sound: :0,4
	8	rk3399-gru-sound: :0,2
	6	rk3399-gru-sound: :0,1
	4	Post DSP Loopback
	3	Post Mix Pre DSP Loopback
Input Nodes:
	Stable Id	 ID	Gain   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(8b6a9a88)	10:0	    0      yes	            no	1481822444        	HOTWORD          Wake on Voice
	(5eb817e4)	8:0	    0       no	            no	         0        	MIC              Mic
	(30b0c661)	6:0	    0      yes	            no	1481822444        	INTERNAL_MIC    *Internal Mic
	(8c74f766)	4:0	    0      yes	            no	         0        	POST_DSP_LOOPBACK Post DSP Loopback
	(8a04af91)	3:0	    0      yes	            no	         0        	POST_MIX_LOOPBACK Post Mix Pre DSP Loopback
Attached clients:
	ID	pid	uid
	4	5363	1000
Num active streams: 0
Last audio active time: 268, 135381874


I'll try the latest build and see what it detects with my QC15.

My kevin with build R56-9000.15.0 detects QC15 as headphone.


localhost ~ # cras_test_client --dump_s
System Volume (0-100): 100 
Capture Gain (-17.25 - 30.00): 20.00dB 
User muted: Not muted
Output Devices:
	ID	Name
	9	rk3399-gru-sound: :0,3
	7	rk3399-gru-sound: :0,2
	5	rk3399-gru-sound: :0,0
Output Nodes:
	Stable Id	 ID	 Vol   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(519731ad)	9:0	  100       no	            no	         0        	HDMI             HDMI
	(2ba59278)	7:0	   75      yes	            no	1481871492        	HEADPHONE       *Headphone
	(f023442f)	7:1	  100       no	            no	         0        	LINEOUT          Line Out
	(72a57953)	5:0	   75      yes	            no	1481871297        	INTERNAL_SPEAKER Speaker
Input Devices:
	ID	Name
	10	rk3399-gru-sound: :0,4
	8	rk3399-gru-sound: :0,2
	6	rk3399-gru-sound: :0,1
	4	Post DSP Loopback
	3	Post Mix Pre DSP Loopback
Input Nodes:
	Stable Id	 ID	Gain   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(8b6a9a88)	10:0	    0      yes	            no	1481871297        	HOTWORD          Wake on Voice
	(5eb817e4)	8:0	    0       no	            no	         0        	MIC              Mic
	(30b0c661)	6:0	    0      yes	            no	1481871297        	INTERNAL_MIC    *Internal Mic
	(8c74f766)	4:0	    0      yes	            no	         0        	POST_DSP_LOOPBACK Post DSP Loopback
	(8a04af91)	3:0	    0      yes	            no	         0        	POST_MIX_LOOPBACK Post Mix Pre DSP Loopback
Attached clients:
	ID	pid	uid
	0	4685	656365
	2	6750	0
Num active streams: 0
Last audio active time: 177, 685066541



tringuyen@ I'm wondering maybe your QC15's impedance is higher than the headphone detection threshold so it was not detected. And the new R56-9000.15.0 build includes lineout support so your QC15 is detected as LINEOUT.

Possible. I have a Sentry chromebook running 56.0.2924 beta; can I feedback on it to see what it detects?  
Does the Sentry chromebook detect your QC15? If yes then that sure would help.

Just filed feedback on my Sentry DVT under my LDAP; yes, Sentry/Elm/Lulu have been working fine with my QC15 but I'm not sure if they detect it as lineout instead of headphone though.
Link to sentry feedback: https://feedback.corp.google.com/product/208/neutron?lView=rd&lReport=50519156142

Interesting that the QC15 is detected correctly as Headphone on Sentry:

=== cras_test_client --dump_server_info ===
System Volume (0-100): 100 
Capture Gain (0.00 - 0.00): 20.00dB 
User muted: Not muted
Output Devices:
	ID	Name
	11	sklnau8825max: :0,6
	10	sklnau8825max: :0,5
	9	sklnau8825max: :0,4
	5	sklnau8825max: :0,0
Output Nodes:
	Stable Id	 ID	 Vol   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(34cb7f6c)	11:0	  100       no	            no	         0        	HDMI             HDMI/DP, pcm=6 Jack
	(48b0443e)	10:0	  100       no	            no	         0        	HDMI             HDMI/DP, pcm=5 Jack
	(7a4f63c9)	9:0	  100       no	            no	         0        	HDMI             HDMI/DP, pcm=4 Jack
	(9e934263)	5:0	   48      yes	            no	1482253901        	HEADPHONE       *Headphone
	(72a57953)	5:1	    4      yes	            no	1481909632        	INTERNAL_SPEAKER Speaker
Input Devices:
	ID	Name
	8	sklnau8825max: :0,3
	7	sklnau8825max: :0,2
	6	sklnau8825max: :0,1
	4	Post DSP Loopback
	3	Post Mix Pre DSP Loopback
Input Nodes:
	Stable Id	 ID	Gain   Plugged	L/R swapped	      Time Hotword	Type		 Name
	(bb46462c)	8:0	    0      yes	            no	1481909632        	UNKNOWN          (default)
	(a6476c33)	7:0	    0      yes	            no	1481909632        	UNKNOWN          (default)
	(61aab6ba)	6:0	    0       no	            no	         0        	MIC              Mic
	(4ce2eaa5)	6:1	    0      yes	            no	1481909632        	INTERNAL_MIC    *Internal Mic
	(8c74f766)	4:0	    0      yes	            no	         0        	POST_DSP_LOOPBACK Post DSP Loopback
	(8a04af91)	3:0	    0      yes	            no	         0        	POST_MIX_LOOPBACK Post Mix Pre DSP Loopback
Attached clients:
	ID	pid	uid
	0	4106	656365
	2	842	1000
	4	11198	1000
Num active streams: 1
Last audio active time: 848, 787488177

We might want to re-calibrate Kevin's headphone detection if there are more similar reports.
Owner: cychiang@chromium.org

Sign in to add a comment