Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.3.67f1
Issue ID
UUM-120638
Regression
No
[Android] Audio sound is lower in the Player compared to the native music player
Reproduction steps:
1. Open the attached “IN-116369” project
2. Build and Run the Android Player
3. Transfer the “BGM.wav” file to the Android device
4. Play the “BGM.wav” using the native Audio player
5. In the Player, slide the top slider to the right to play the music at the highest volume
6. Compare the volume
Expected result: The volume of both are similar
Actual result: The volume of the Native Audio player is significantly higher
Reproducible with: 2022.3.67f1, 2023.1.0a12
Not reproducible with: 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a1
Fixed in: 2023.1.0a13
Reproducible environments: macOS 26.0
Not reproducible environments: No other environments tested
Reproducible with these devices:
VLNQA00641 - Google Pixel 9 (Pixel 9), CPU: -, GPU: Mali-G715, OS: 15
VLNQA00526 - samsung Galaxy A12 (SM-A125F), CPU: Mediatek MT6765 Helio P35 (12nm), GPU: PowerVR Rogue GE8320, OS: 12
Not reproducible with these devices:
VLNQA00521 - Galaxy S22 Ultra USA (SM-S908U), CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno 730, OS: 14
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “FMOD failed to set the software format to the custom sample rate…” warnings are thrown as System Sample Rate value is being changed in Audio section of Project Settings window
- VFX Marquee selection does match the visual indicator
- “Invalid AABB aabb” errors are spammed when “Infinity” value is entered in Collider Component fields
- Editor Role does not sync with the MPPM Play Mode Scenario Role when entering Play mode
- Long asset names cause overlap with the “Find” function in search result tabs
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.