Search Issue Tracker

Won't Fix

Votes

0

Found in

2023.1.0a4

2023.2.0a1

Issue ID

UUM-10243

Regression

No

[Android] When Audio is recorded via bluetooth microphone, playing it lasts only few seconds on specific devices

-

How to reproduce:
# Open AndroidMicrophone testing project
# Build and run on Android device
# Connect Bluetooth headphones
# Press on Ingame Debug Console to see what is happening
# Press Start-2 button, it starts recording
# Press End-2 button, it stops recording
# Press Play and listen to what was recorded

Actual Result: audio is recorded, but it is playing only few seconds and gets cut

Expected Result: audio is recorded and playing without issues

Tested and reproduced on: 

VLNQA00285 - Samsung Galaxy J4 Core (SM-J410F), CPU: Snapdragon 425 MSM8917, GPU: Adreno 308, OS: 8.1.0

VLNQA00380 - Xiaomi MI 8 Lite (MI 8 Lite), CPU: Snapdragon 660, GPU: Adreno 512, OS: 8.1.0

Tested and didn't reproduce:

VLNQA00466 - Google Pixel 4 (Pixel 4), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 12
VLNQA00323 - Galaxy Note 10 USA (SM-N970U), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9.0.0
Galaxy Fold 2 , CPU: Snapdragon 855 SM8250, GPU: Adreno 650, OS: 11.0.0
3.4 Custom Image
VLNQA00342 - Note 20 Ultra 5G INT (SM-N986B), CPU: Exynos 990, GPU: Mali-G77, OS: 10
VLNQA00222 - Google Pixel 2 XL (Pixel 2 XL), CPU: Snapdragon 835 MSM8998, GPU: Adreno 540, OS: 9.0.0
VLNQA00281 - Samsung Galaxy S10e USA (SM-G970U), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 9.0.0
VLNQA00218 - Samsung Galaxy Note 9 USA (SM-N960U), CPU: Snapdragon 845 SDM845, GPU: Adreno 630, OS: 8.1.0
VLNQA00321 - Xiaomi MI 9 (MI 9), CPU: Snapdragon 855 SM8150, GPU: Adreno 640, OS: 10.0.0
VLNQA00336 - HUAWEI Y6p (MED-LX9N), CPU: MediaTek MT6762R, GPU: PowerVR Rogue GE8320, OS: 10
VLNQA00293 - OPPO R17 Pro (PBDM00), CPU: Snapdragon 710 SDM710, GPU: Adreno 616, OS: 9.0.0
VLNQA00430 - OnePlus OnePlus 9 5G (LE2113), CPU: Snapdragon 888, GPU: Adreno 660, OS: 12

This is AAudio bug, which was introduced in 2023

  1. Resolution Note:

    Thank you for your bug report.

    After reviewing the issue and the impact it has on our users our team has decided that this case will be resolved as "Won't Fix".This does not mean that the issue isn’t a legitimate bug, but instead that we are not able to prioritize the fix, at this time.

    The case will now be closed, and will not be reopened unless new information arises that would change the issue’s impact. Please let us know if you have additional information relating to the severity of this bug.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.