Search Issue Tracker
Fixed
Fixed in 5.0.0
Votes
0
Found in [Package]
5.0.0
Issue ID
APB-57
Regression
No
[Android] Android Adaptive Performance calls android.app.GameManager.getGameMode() every frame, costing 1ms on the main thread
Reproduction steps:
1. Open the attached “IN-85543” project
2. In Build Settings, make sure that “Development Build”, “Deep Profiling”, and (optionally) “Autoconnect Profiler” is selected
3. Build and Run the Android Player
4. Profile the Player
5. Observe the Profiler
Expected result: Adaptive Performance does not call “AndroidGame.get_GameMode()” every frame
Actual result: Adaptive Performance calls “AndroidGame.get_GameMode()” and costs around 1 ms every frame
Reproducible with: 5.0.0 (6000.0.32f1, 6000.1.0a9)
Couldn’t test with: 5.0.0 (2021.3.46f1, 2022.3.55f1) (Adaptive Performance Android is not supported)
Reproducible environments: Windows 11 (24H2)
Not reproducible environments: No other environments tested
Reproducible with these devices:
VLNQA00591 - samsung Galaxy S23 (SM-S911B), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 14
Could not test with these devices: (Devices unsupported, the package supports Android OS 12+)
VLNQA00403 - Galaxy Z Flip3 5G (SM-F711B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00480 - samsung Galaxy S21 5G (SM-G991B), CPU: Exynos 2100, GPU: Mali-G78, OS: 11
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 5.0.0):
fixed in 5.1.2