Search Issue Tracker
Fixed in 2.0.0.8
Votes
0
Found in [Package]
1.1.0
Issue ID
1245036
Regression
No
[Adaptive Performance] Bixby button disrupts adaptive performance output
Steps to reproduce:
1. Open attached project
2. Build and run "Automatic Performance Control" scene on Android device
3. Click the bixby button and go back to the app
• Make sure that you are not signed in to the Samsung account and Bixby has not been set up because otherwise this behaviour will not be observed
4. Observe certain outputs in top left corner being disrupted like this:
GPU time freezes
CPU and GPU levels freeze at -1/3
Temp level stuck on -1.00
Temp trend stuck on 0.00
Expected: Clicking the Bixby button and going back to the app should not interfere with Adaptive Peformance outputs
Actual: Clicking the Bixby button disrupts the outputs
Reproduced on Devices:
Samsung Galaxy S20+ 5G (SM-G986B) Mali-G77 Android 10
Samsung Galaxy Fold (SM-F900F) Adreno (TM) 640 Snapdragon 855 SM8150 Android 9
VLNQA00264 Samsung Galaxy S10+ (SM-G975F) Mali-G76 Android 10
Unity Version 2019.3.11f1 (ceef2d848e70)
Tue, 21 Apr 2020 03:45:09 GMT
Branch: 2019.3/staging
Not reproducible on any device that does not have a Bixby button (or bixby funtionality)
Reproduced on Package Versions 1.1.0 through 1.1.6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Web][iOS] Web Player keeps restarting on launch when Native C/C++ Multithreading is enabled
- "Add Scene to Scenes in Build" pop-up reappears after Scene has already been added and another Multiplayer Editor Instance is loaded
- TableEntryAdded event is not triggered when a new entry is added in the Localization Tables window
- The macOS Player is built to a different folder than the selected one when the Player is built on Windows
- Editor memory leak in VisualElement when recompiling in a blank URP project
Add comment