1003749 - [Flame] Can't consistently reopen audio device

Status: RESOLVED DUPLICATE of bug 1011214

(Core :: WebRTC: Audio/Video, defect, P2)

Description

[Alfredo Yang (:alfredo)]

It blocks at http://dxr.mozilla.org/mozilla-central/source/widget/gonk/nativewindow/GonkBufferQueueJB.cpp#388.

Buffers may not release completely especially close the webrtc calling tab without hangup.

Comment 1

[u459114]

Alfredo, do you want to take this issue?

Comment 2

[Alfredo Yang (:alfredo)]

It should be microphone doesn't send pcm data and it causes MSG time stopping. So the local camera preview is dropped on [1]. It can also be reproduced on gUM A/V or A. It can be recovered only by rebooting device.
Video only gUM or webrtc call won't be affected by this.

I will check flame microphone with gonk team.

[1] http://dxr.mozilla.org/mozilla-central/source/content/media/webrtc/MediaEngineWebRTCVideo.cpp#161

Comment 3

[Alfredo Yang (:alfredo)]

The logs are followings when it happened.

05-07 05:59:10.147 E/TrackUtils( 3330): setParameter failed usecase = USECASE_PCM_RECORDING err = -38
05-07 05:59:10.147 E/TrackUtils( 3330): Use case cannot be supported because of DSP limitation

I can't try the latest vendor libraries because my device is DVT and the latest vendor libraries need PVT device.

Comment 4

[Wayne Chen [:xwaynec]]

Hi Tony,

Could you help to check this?
Thanks

(04:57:43 PM) jesup: D/AudioResourceManager(  285):  setParameter USECASE_PCM_RECORDING=true:
(04:57:44 PM) jesup: D/AudioResourceManager(  285): key = USECASE_PCM_RECORDING, value = true, useCase = 1
(04:57:45 PM) jesup: D/AudioResourceManager(  285): checkUseCaseConflict = 1
(04:57:47 PM) jesup: D/AudioResourceManager(  285): usecase = 7 , refCount  =2, maxrefcount =2
(04:57:48 PM) jesup: E/TrackUtils( 2218): setParameter failed usecase = USECASE_PCM_RECORDING err = -38
(04:57:50 PM) jesup: E/TrackUtils( 2218): Use case cannot be supported because of DSP limitation
(04:57:52 PM) jesup: E/AudioRecord( 2218): SetConcurrencyParameterforRemoteRecordSession true - returned error

Comment 5

[Randy Lin [:rlin] - Be Mozillian on 2015/01/26]

Hi Yanan, 
As talked with Wayne, 
We need your help to clarify this issue. 
Thanks a lot.

Comment 6

[Ivan Tsay (:ITsay)]

Have we got any feedback from our partner on this?

Comment 7

[Randy Lin [:rlin] - Be Mozillian on 2015/01/26]

Not yet, I need info to Yanan but I didn't receive any response for this problem.

Comment 8

[Francis Lee [:frlee]]

hi Yanan,

could you please check comment 4? we found several error logs on HAL layer.

Comment 9

[Maire Reavy [:mreavy]]

Updating the title to reflect what we've learned.  This affects getUserMedia and WebRTC calls on Flame.

Comment 10

[Randell Jesup [:jesup] (needinfo me)]

See also patch on bug 1011214; it's possible that's the cause or related.

Comment 11

[Randy Lin [:rlin] - Be Mozillian on 2015/01/26]

Test with gecko:182867:7f5a8526b55a at central on v10F-3 ROM image.
WebRTC using VP8 codec and connect to desktop, 
The symptom changes to broken sound.
You can see this kind of logs keep output on logcat.

D/AudioResourceManager(  301): key = USECASE_PCM_RECORDING, value = true, useCase = 1
D/AudioResourceManager(  301): checkUseCaseConflict = 1
D/mm-camera-intf(  301): mm_stream_read_msm_frame: VIDIOC_DQBUF buf_index 2, frame_idx 2404, stream type 7
D/AudioResourceManager(  301): usecase = 7 , refCount  =0, maxrefcount =2
D/AudioResourceManager(  301): usecase = 10 , refCount  =0, maxrefcount =1
D/AudioResourceManager(  301): updateUsecaseRefCount useCase=1,value=1,desc->refCount=378
D/AudioResourceManager(  301): updateUsecaseRefCount useCase = 1, refCount =379
That means audio HAL layer try to enable/disable audio codec again and again...

Comment 12

[Randell Jesup [:jesup] (needinfo me)]

Filed Bug 1012936 for the audio breakup in calls (this is a different bug, and likely should be marked as a dup of bug 1011214 if we can no longer reproduce it - alfredo?)

Comment 14

[BugBot (nomail) [:suhaib / :marco/ :calixte]]

Clearing the needinfo request since it is pending on an account that cannot answer (a bot, a component watcher, or a disabled account).

For more information, please visit BugBot documentation.