Search Issue Tracker
Fixed in 4.6.1
Votes
21
Found in
4.3.4f1
Issue ID
604438
Regression
No
Enabling gyroscope on Samsung Note 3 adds big cpu overhead
With gyroscope disabled, the CPU overhead is 4-7 ms. With gyroscope enabled the CPU overhead jumps to 20-30 ms with occasional spikes to 100-300 ms.
Reproduced on:
Samsung Galaxy Note 3 LTE (SM-N9005) with Android 4.4.2
Reproduced with:
Unity Version 4.3.4f1 (e444f76e01cd)
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
- OnTriggerExit2D events are not triggered when disabling Collider, despite "Callbacks On Disable" being enabled
- [Android] [Vulkan] UI that is activated after a delay flickers when a Scriptable Render Pass goes over it
- [Linux] Characters are converted to Latin letters when using IME on Linux
- [Ubuntu] Possible for Create menu to show sections with no options inside
- [Usability] Not possible to set Editor Window text colour to be default black without workaround
Nesvi
Dec 17, 2014 22:42
EDIT - Works well in LG G3, it's fixed. Thank you.
Nesvi
Dec 17, 2014 22:31
I'm still having this issue with the LG G3.
TheHellTerrier
Jul 16, 2014 11:50
Yep, same here, old Nexus7 and Nexus7 2013 are fine, Galaxy Note2 is fine, but my Note3 with 4.4.2 glitches and stutters continuously.
I've tested this on each version of Unity since 4.3.4f1 (currently 4.5.2f1) and the problem is still apparent.
I've also tried setting the minimum API level to all the values (9 to 19) with no difference.
I've tried disabling multi-threaded rendering with no effect.
I've tried setting the script execution order for the class reading the gyro to both before and after 'default time' with no effect.
Bit of a downer as the Note3 size and resolution makes a nicer VR display than the Note2 or Nexus7.