Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

onErrorBeforeClose and onErrorAfterClose are not called when a headset plugged in and out #893

Closed
taemincho opened this issue Jun 15, 2020 · 3 comments
Assignees
Labels

Comments

@taemincho
Copy link

Android version(s): 10
Android device(s): Samsung S10
Oboe version: 1.4 - stable (1.4.2)
App name used for testing: LiveEffect
(Please try to reproduce the issue using the OboeTester or an Oboe sample.)

Short description
(Please only report one bug per Issue. Do not combine multiple bugs.)
onErrorBeforeClose and onErrorAfterClose are not called when a headset plugged in and out

Steps to reproduce

  1. Launch LiveEffect
  2. Select Auto select for both Recording device and Playback device
  3. Select AAudio for APIs
  4. Press Start button
  5. Plug in a headset (w/ microphone)
  6. Plug out the headset

Expected behavior
When plugging in a headset onErrorBeforeClose and onErrorBeforeClose are called, so that should be able to switch Recording and Playback devices to headset speaker and mic.

Actual behavior
onErrorBeforeClose and onErrorBeforeClose are not called and the phone mic and speaker are used for audio recording and playback

Any additional context
If select OpenSL ES for APIs, onErrorBeforeClose and onErrorBeforeClose are also not called. However, recording and playback devices are switched to the headset speaker and mic as expected.

If applicable, please attach a recording of the sound.

@taemincho taemincho added the bug label Jun 15, 2020
@philburk
Copy link
Collaborator

philburk commented Jun 15, 2020

This is a known issue on some P devices.
There is a tech Note here with more detail:

https://github.com/google/oboe/blob/master/docs/notes/disconnect.md

Do you have an exact build number for the device with this problem? We can add a list of affected devices to the Tech Note.

@philburk philburk self-assigned this Jun 15, 2020
@taemincho
Copy link
Author

build number: QP1A.190711.020.G973FXXU4CTC9

@philburk
Copy link
Collaborator

It may have taken a while for the fix to propagate out to various Q devices.
Closing this because the root cause was fixed and we now check for this in QA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants