Forum Discussion
App crashes after 20 minutes in GEAR VR
Hello Everyone!
I'm trying to build an application in my Gear VR, something very basic about a tour in 360° with rendered images in a sphere.
Yesterday, after a few test with a lot of users and running during 20 minutes without any interruption, the application crashes withou any message and restart to the oculus home app.
I tried to debug the app and i'm attaching the LOG here in this discussion.
I have no ideia whats is going on, why the application restart after what about 20 minutes?
I'm using the 5.3.4p4 and the lasted OVRPluging.
I already tried to run in other smartphones, and the build configuration is already set to OpenGLES2.
I'm trying to build an application in my Gear VR, something very basic about a tour in 360° with rendered images in a sphere.
Yesterday, after a few test with a lot of users and running during 20 minutes without any interruption, the application crashes withou any message and restart to the oculus home app.
I tried to debug the app and i'm attaching the LOG here in this discussion.
I have no ideia whats is going on, why the application restart after what about 20 minutes?
I'm using the 5.3.4p4 and the lasted OVRPluging.
I already tried to run in other smartphones, and the build configuration is already set to OpenGLES2.
7 Replies
Replies have been turned off for this discussion
- Sorry, your LOG.txt file doesn't include the full logcat from the app. Can you make sure to capture everything from the app's start to finish? Most likely, the app is hitting an error and exiting, but I will need to see the full logcat to be sure.
vrdaveb said:
Sorry, your LOG.txt file doesn't include the full logcat from the app. Can you make sure to capture everything from the app's start to finish? Most likely, the app is hitting an error and exiting, but I will need to see the full logcat to be sure.
i tried the following arguments in command line:
adb logcat -s Unity ActivityManager PackageManager dalvikvm DEBUG
I don't know too much about them, which do you recommend?- It should work fine to run "adb logcat > LOG.txt" immediately after the process exits and then let run for a few seconds to write everything out.
- I capture the LOG some minutes before and after the crash, because there are no way to know the exact moment.
- Thanks, looks like you got it.06-13 20:07:06.461 3534 4038 I ActivityManager: Process com.digitalkey.setin (pid 10218)(adj 0) has died(2334,408)
It isn't clear why it died, but there does seem to be a Samsung service installation in progress when it happens. The UcmService may be interfering with the VRSVC and then crashing the app in the process, but it isn't clear how that's happening. Thanks for reporting this. We'll look into it right away. - Thank you very much for your fast feedback, i'm looking forward for any solution for this problem.
- Sorry, but we were unable to reproduce this. Is it still occurring for you with the latest SystemActivity?
