Hi Paul,
A couple of questions on the issues raised in this thread (POSSIBLE BUG?: Exported APK failed to detect gyroscope?)
I use an AIO Android VR Headset running Android 5.1 NIBIRU VR interface. (MagicSee M1 NIBIRU Version 2.1, I will have the MagicSee M2 & M3 NIBIRU V3 in a week or two, so I will have to see if this issue continues)
Running the compiled APK starts and reads the Gyro sensors correctly. The app works as designed and as it does In the AppGameKit Player.
On app exit, however, 'END' command, the app doesn’t appear to actually end the app, I know this is common on Android devices and the apps may be suspended or hidden but it also appears the AppGameKit APK is not releasing the gyro sensors.
The main NIBIRU interface no longer responds to device rotation, and the device must be either rebooted. Or use the NIBIRU hardware command button to end the app instead.
If I use the NIBIRU Hardware button to end the app, the Gyro appears to be released and the NIBIRU interface works correctly, however the next time I load my app (APK) the Gyro is over sensitive like its reporting at twice the normal rate, for example 180 physical rotation shows in the app as 360
Could this be a bug in AppGameKit?
If I reboot it all works correctly again.
And my other question, In Android, on resume from suspending or hide, where is the entry point? Does the app jump directly into the loop or run all the code from the start of the code file?
Thanks.
