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

why the audio volume captured using oboe lowlatency by aaudio/opensles is obviously lower than non lowlatency mode? #2117

Open
lhran99 opened this issue Nov 20, 2024 · 2 comments
Assignees
Labels
bug P2 normal priority Samsung specific to Samsung devices

Comments

@lhran99
Copy link

lhran99 commented Nov 20, 2024

I find that many android devices have the issue, the audio volume captured using oboe low latency by aaudio/opensles is obviously lower than non low latency mode, here is my test:

device info:
ro.product.brand = samsung
ro.product.manufacturer = samsung
ro.product.model = SM-G988N
ro.product.device = z3q
ro.product.cpu.abi = arm64-v8a
ro.build.description = z3qksx-user 13 TP1A.220624.014 G988NKSU1HVJG release-keys
ro.hardware = qcom
ro.hardware.chipname = SM8250
ro.arch =
| grep aaudio = [aaudio.hw_burst_min_usec]: [2000]
[aaudio.mmap_exclusive_policy]: [2]
[aaudio.mmap_policy]: [2]

step1:
Open the oboetest -> RECORD AND PLAY -> Set the Recorder setting as folllows:
Image

step2:
click the RECORD button and start record for some seconds ,then click STOP, here is the wav:
aaudio recorder with low latency.wav.zip

step3:
set the Perf to NONE, as follows:
Image
and repeat step2, here is the wav
aaudio_recorder_without_low_latency.wav.zip

step4:
Image

The first wav volume is obviously lower than the second one.

When i choose API to opensles, then has the same issue, the was as follows:
opensles_recorder_with_lowlatency.wav.zip
opensles_recorder_with_lowlatency.wav.zip

Then i do the test on other device, here is the result:

SM-S908N G4083 12 weak capture
SM-N960N GB036 10 ok
SM-N986N G9081 12 weak capture
SM-G977N GB037 12 ok
SM-N976N GB044 12 ok
SM-G986N GE067 12 weak capture
SM-N981N GF054 11 weak capture
SM-G996N GH019 13 weak capture
SM-G998N GH020 11 weak capture
SM-G991N GH088 11 weak capture
SM-A325N GH240 11 ok
SM-F711N GH267 14 weak capture
SM-S901N GH269 13 weak capture
Pixel 6a GH698 15 ok
SM-A235M GH484 13 weak capture
SM-S911N GH877 14 weak capture

It seems that 11/16 = 68.75% of devices have the same issue.

@lhran99 lhran99 added the bug label Nov 20, 2024
@philburk
Copy link
Collaborator

@lhran99 - Thanks for raising this issue. I will report this to Samsung.
We are also planning to add more volume and gain testing.

@philburk philburk self-assigned this Nov 24, 2024
@philburk philburk added P1 high priority Samsung specific to Samsung devices labels Nov 24, 2024
@philburk
Copy link
Collaborator

Tracking with internal bug b/381157687 | P2 | [Samsung] gain is very low when recording in non-low-latency mode
that is shared with Samsung.

@philburk philburk added P2 normal priority and removed P1 high priority labels Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug P2 normal priority Samsung specific to Samsung devices
Projects
None yet
Development

No branches or pull requests

2 participants