Updated to 1.13 and my S6 is almost catching fire in 2minutes also. When previously could go on for 15min +.. Has there been a bump in native render resolution or how is this even possible? Any insight anyone? Tried to fiddle with cpu/gpu values with no results while debugging gpu values on screen and seeing the choking, still heating up like a stove,,,
Have you tried looking at the log produced by such a run? If only to check to ensure that the once-per-second VrApi log events report the GPU/CPU settings you expect, and see what the temps look like etc.
Just as a data point, on Oculus Utilities 1.12 + Unity 5.3.8f1, the GPU/CPU settings are definitely working as expected on the S6. Seems that the underlying mobile SDK hasn't changed from 1.12 to 1.13 though, it's listed as Mobile SDK 1.0.4.5 for both.
Titans of Space PLUS for Quest is now available on DrashVR.com
Haven´t tried, no idea how to get logs on gearVR tests. So, advice needed for that. I´m trying convert back to 5.3.8f1 if that could provide help for me.
We are using Oculus Utilities 1.12 + Unity 5.4.5f1, and the setting of cpuLevel and gpuLevel works for us on S6. As setting both cpuLevel and gpuLevel as 0, the frame rate does drop and our app can runs much longer (40+mins) on S6 without any overheating message.
However, as we tests the same apk on S7 (with the same version of Android (6.0.1) and same version of GearVR framework (11.0.0) and all the other settings are as the same as we have on S6), the frame rate doesn't drop at all (the adb log still tells you CPU0/GPU = 0/0) and it doesn't really help the heating issue on S7 much...