Search Issue Tracker
Fixed in 5.6.0
Votes
1
Found in
5.4.2p1
Issue ID
846253
Regression
No
[Android] [GearVR] Anomalous performance with Snapdragon 820 SGS7 devices
How to reproduce:
1. Open user's attached project
2. Open scene 'TestScene'
3. Add devices osig file to Assets/plugins/Android/assets
4. Build and run for Android in VR Mode
5. Wait for the in-game music to stop and close the app
6. Reconnect the USB cable to the device (Otherwise the files created by the app will not be visible)
7. Go to DEVICE-NAME\Phone\Android\data\com.vTime.S7Test\files
8. Copy the 'S7Profile' and 'S7Profile.data' files to project_path\Profiles\GearVR_CPU2_GPU2\S7_x (depending on the cpu)
9. Open profiler (CTRL + 7)
10. In editor's menu bar go to vTime/LoadProfile_x
11. In profiler, inspect 'BehaviourUpdate>LotsOfCPUWork.Update()' on a FPS spike (less than 60)
Expected behaviour: Snapdragon 820 performance similar to Exynos
Actual behaviour: Snapdragon CPU performs ~20% worse
Reproduced on: 5.3.7f1, 5.4.2p3, 5.5.0b11
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
Add comment