Game Exiting on Galaxy Nexus and Nexus S

jonparkins · May 10, 2012, 7:31pm

Hello All,

I need a little help does anyone have any ideas on the bug Google has posted to me below? We don’t have either of these devices to test, this is happening on Android 4 (Ice Cream Sandwich) but we also aren’t really sure what the issue could be either, any rough ideas?

Thanks

Bugs:

: Turning off screen on Galaxy Nexus or Nexus S running ICS exits game. Any progress made in a level is lost. This doesn’t happen on XOOM running ICS. [import]uid: 54327 topic_id: 26169 reply_id: 326169[/import]

jonparkins · May 10, 2012, 7:41pm

Also I’m on Build 799, I noticed that 811 has some general display fixes, so I’ll give that a shot for now… Just grasping as straws right now.

Android: Fixed inneractive Android 4.0 graphics glitches and fullscreen display issues. casenum 13543 [import]uid: 54327 topic_id: 26169 reply_id: 106012[/import]

jonparkins · May 11, 2012, 10:58am

Small Update, 811 didn’t help, going to try 812, and finally have a friends Nexus S with ICS to see if I can pull something from the console in Eclipse once the SDK is done updating. [import]uid: 54327 topic_id: 26169 reply_id: 106135[/import]

jonparkins · May 11, 2012, 11:30am

812 didn’t help, I don’t think its anything in code either as they stated its working fine on the Xoom, and works fine on older SDK’s and devices, sigh, Google you make me sad sometimes. I captured a log as well, but it’s a lot of text to drop here if anyone wants to see it.

Or is reading this, or has any ideas [import]uid: 54327 topic_id: 26169 reply_id: 106139[/import]

Joshua_Quick · May 11, 2012, 12:20pm

Hi Jon,

I too have noticed that an Android 4.x device would restart the app upon orientation change. That issue started happening when we started compiling with Android SDK 4.0.3. I haven’t seen the app restart itself when turing the display on/off… unless its a landscape app, in which case an orientation change would suddenly occur once you power on the display. Is your app a landscape app?

The good news is that we have a fix for this in the queue. We plan on releasing this fix sometime in the first half of next week. It involves deploying an updated Android SDK to our server cluster, which we can’t rush and want to make sure we do it right.

Oh, and if you know of any other Android 4.x issues, then please send them my way. I want to make sure that they’re all taken care of by the next Corona SDK release. Thanks! [import]uid: 32256 topic_id: 26169 reply_id: 106154[/import]

jonparkins · May 11, 2012, 1:05pm

That’s great to hear, this is the last hurdle to a Google Feature I’ve been told, I’m excited for it!

We are indeed Landscape, if I see anything else I’ll report in!

Thanks for the reply once again! I’ll wait for the deployment to give it a try! [import]uid: 54327 topic_id: 26169 reply_id: 106164[/import]

jonparkins · May 11, 2012, 1:26pm

A little more feedback from Google in case this aids you at all!

“Jon,
THanks for looking into it. It does look like it has something to do with the landscape orientation since the lockscreen on handsets is in portrait, so when it switches back it restarts. On ICS tablets, the lockscreen is able to change to landscape, so the problem didnt show itself on the Xoom.” [import]uid: 54327 topic_id: 26169 reply_id: 106171[/import]

Joshua_Quick · May 11, 2012, 2:22pm

Yeah… we had to work-around the issue by overriding the “screenSize” configChanges event. That was a new event that was added as of Android API Level 13 whose default behavior is to restart the app.
http://developer.android.com/guide/topics/manifest/activity-element.html#config
[import]uid: 32256 topic_id: 26169 reply_id: 106180[/import]

jonparkins · May 11, 2012, 2:29pm

Is it something I should hack into the manifest? Or just wait for the daily build with your changes that are coming? [import]uid: 54327 topic_id: 26169 reply_id: 106183[/import]

Joshua_Quick · May 11, 2012, 2:41pm

Unfortunately it’s more than just a manifest setting. I recently found out that our Corona built apps was still including an Android API Level 8 library that prevented the build from accepting this new manifest settings, thus causing a build error. This is why we have to deploy an updated Android SDK to our build servers. It was my mistake for not catching this discrepancy, but now I’ve set up the build process to be more future proof to help avoid this issue from happening again.

Sorry for the delay. I know you’ve been fighting to get your app to the marketplace. All I can say is that, on our end, it is really challenging to get an app to work consistently between all of the different types of Android devices and Android versions. At least compared to iOS. But I like to think it’s getting better every month… and I hope you feel the same as well. [import]uid: 32256 topic_id: 26169 reply_id: 106187[/import]

jonparkins · May 11, 2012, 2:51pm

Oh believe me I know how frustrating the Android side of things has been So no worries on that front, things have definitely been getting better, and you guys have been very forth coming with info once we’ve got a back and forth going, for that I am very thankful. We will sit tight and wait for the changes!

I just thought maybe there was a simple solution buried in there, my day job is for a fairly big game developer so I fully 100% understand what you are up against

Thanks again Joshua! [import]uid: 54327 topic_id: 26169 reply_id: 106190[/import]

Joshua_Quick · May 18, 2012, 2:54pm

The newest daily build now fixes this issue. Sorry to keep you waiting.

Just to let you know, we do have another show stopper issue where Corona apps using the newest daily builds will crash on Nook Color… and likely other Android devices that use the same GPU. That issue will be fixed in tomorrow’s daily build, Saturday. [import]uid: 32256 topic_id: 26169 reply_id: 107559[/import]

jonparkins · May 18, 2012, 4:29pm

Awesome. I grabbed today’s build and submitted it worked great on the nexus devices we were having issues with. We aren’t on nook at all so hopefully google won’t notice but I can fire up another build tomorrow to be safe. Thanks for the heads up and I’ll let you know if I hear anything from google qa. [import]uid: 54327 topic_id: 26169 reply_id: 107576[/import]

jonparkins · May 31, 2012, 3:21pm

Hi Joshua,

I was just looking over the Android reported errors on the developer console and I saw this guy has occurred 5 times, I don’t know if it’s something of use to you or not, but I figured I’d pass it along.

java.lang.RuntimeException: createWindowSurface failed
at android.opengl.derived.SwapGLSurfaceView$EglHelper.createSurface(SwapGLSurfaceView.java:691)
at android.opengl.derived.SwapGLSurfaceView$EglHelper.createSurface(SwapGLSurfaceView.java:715)
at android.opengl.derived.SwapGLSurfaceView$GLThread.guardedRun(SwapGLSurfaceView.java:936)
at android.opengl.derived.SwapGLSurfaceView$GLThread.run(SwapGLSurfaceView.java:809) [import]uid: 54327 topic_id: 26169 reply_id: 109584[/import]

jonparkins · May 31, 2012, 3:25pm

One more for good measure. These are all running on 819 I believe. Which ever build fixed the initial problem in this thread, and then the build after that for the Nook issue you mentioned. I can’t check till I get home from work.

java.lang.IllegalArgumentException: Make sure the SurfaceView or associated SurfaceHolder has a valid Surface
at com.google.android.gles_jni.EGLImpl._eglCreateWindowSurface(Native Method)
at com.google.android.gles_jni.EGLImpl.eglCreateWindowSurface(EGLImpl.java:90)
at android.opengl.derived.SwapGLSurfaceView$DefaultWindowSurfaceFactory.createWindowSurface(SwapGLSurfaceView.java:473)
at android.opengl.derived.SwapGLSurfaceView$EglHelper.createSurface(SwapGLSurfaceView.java:689)
at android.opengl.derived.SwapGLSurfaceView$GLThread.guardedRun(SwapGLSurfaceView.java:936)
at android.opengl.derived.SwapGLSurfaceView$GLThread.run(SwapGLSurfaceView.java:809) [import]uid: 54327 topic_id: 26169 reply_id: 109587[/import]

Joshua_Quick · May 31, 2012, 3:31pm

Hi Jon,

The “createWindowSurface failed” error should have been fixed in build 819. It was a bug that we accidentally introduced in build 797 when we attempted to fix rendering issues on Kindle Fire and Nook Tablet. Yeah, if you can confirm this for me then that would be great. Perhaps try it with the newest daily build too. If the crash is still happening to you, then can you tell me what make and model of your Android device is please? Thanks! [import]uid: 32256 topic_id: 26169 reply_id: 109588[/import]

jonparkins · May 31, 2012, 3:38pm

Ok it could be that someone has an older build and didn’t update, but it looked like it said it was for our latest. Its not happening to me, its just what is reported on the Android Developer Console, unfortunately that’s all the info it gives. I’ll verify what build I’ve got, and I’ll do our next Android update with the latest daily build too.

Thanks! [import]uid: 54327 topic_id: 26169 reply_id: 109589[/import]

george18 · June 6, 2012, 12:43am

Hi Joshua, we’re seeing the same error reported with an android build on version 824. [import]uid: 135827 topic_id: 26169 reply_id: 110412[/import]

Joshua_Quick · June 6, 2012, 11:51am

George,

Can you give me anymore detail? Such as the make, model, and OS version of the Android device please? And does this exception happen to you every time on app startup? Also, does this error happen to you when running a sample app that is included with the Corona SDK? Thanks!

I ask because we can’t reproduce the error on our end. This may be a very specific device issue. [import]uid: 32256 topic_id: 26169 reply_id: 110532[/import]

george18 · June 6, 2012, 1:47pm

Hi Joshua We’ve gotten bug reports for the droid x2 and the Samsung exhibit. [import]uid: 135827 topic_id: 26169 reply_id: 110552[/import]