Search Issue Tracker
Fixed in 2017.2.X
Votes
3
Found in
5.3.3f1
Issue ID
784238
Regression
Yes
[Android] UI performance regression on most Adreno 305 devices
To reproduce:
1) Open attached project and scene in it
2) Make sure it autoconnects to profiler
3) Build and run on device
4) Open profiler, see the subpar performance
DUT:
Motorola Moto G (Adreno 305) (Android 5.1) (Reproduced)
HTC One mini2 (Adreno 305) (Android 4.4.4) (Reproduced)
Samsung Galaxy Tab 4 10.1 WiFi (Adreno 305) (Android 4.4.4) (Reproduced)
Samsung Galaxy S4 mini (Adreno 305) (Android 4.4.4) (Not reproduced)
Sony Xperia Z (Adreno 320) (Android 5.1.1) (Not reproduced)
Samsung Galaxy S4 (Adreno 320) (Android 5.0.1) (Not reproduced)
HTC Droid Incredible X (Adreno 320) (Android 4.1.1) (Not reproduced)
Motorola Moto X (Adreno 320) (Android 4.4.4) (Not reproduced)
Samsung Galaxy S3 AT&T (Adreno 225) (Android 4.1.1) (Not reproduced)
Sony Xperia S (Adreno 220) (Android 4.1.2) (Not reproduced)
HTC Sensation XE (Adreno 220) (Android 4.0.3) (Not reproduced)
HTC Desire 500 506e (Adreno 203) (Android 4.1.2) (Not reproduced)
Samsung Galaxy S5 Neo (ARM Mali-T720) (Android 5.1.1) (Not reproduced)
Samsung Galaxy Note 10.1 2014 WiFi (ARM Mali-T628MP6) (Android 4.4.2) (Not reproduced)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Add comment