Force close on startup - Android

Solar2D Daily Builds and Public Releases
#1

We have gotten multiple crash reports on Android in our game Fun Run.

java.lang.RuntimeException: createWindowSurface failed at android.opengl.derived.SwapGLSurfaceView$EglHelper.createSurface(SwapGLSurfaceView.java:701) at android.opengl.derived.SwapGLSurfaceView$EglHelper.createSurface(SwapGLSurfaceView.java:725) at android.opengl.derived.SwapGLSurfaceView$GLThread.guardedRun(SwapGLSurfaceView.java:948) at android.opengl.derived.SwapGLSurfaceView$GLThread.run(SwapGLSurfaceView.java:825)

We have tried with build 937 and 902. Some of the phones affected are:

* OTHER 32 reports
* SGH-T759 ? reports
* LG-P920 4 reports
* LG-P925 7 reports
* LT18i 1 reports
* LG-P925g 1 reports
* LT15i 3 reports [import]uid: 88922 topic_id: 32451 reply_id: 332451[/import]

#2

Is this a known problem that is worked on?
[import]uid: 88922 topic_id: 32451 reply_id: 129438[/import]

#3

Is this a known problem that is worked on?
[import]uid: 88922 topic_id: 32451 reply_id: 129438[/import]

#4

Us too.

LG-P920
LG-SU760
LG-P925g [import]uid: 135827 topic_id: 32451 reply_id: 130381[/import]

#5

Us too.

LG-P920
LG-SU760
LG-P925g [import]uid: 135827 topic_id: 32451 reply_id: 130381[/import]

#6

I guess this qualifies as an “ultra critical bug” (mentioned by Walter) that needs to be fixed for the next public release.

In fact, it needs to be fixed right now otherwise Google Play / Amazon distribution will be a nightmare. [import]uid: 133261 topic_id: 32451 reply_id: 130425[/import]

#7

I guess this qualifies as an “ultra critical bug” (mentioned by Walter) that needs to be fixed for the next public release.

In fact, it needs to be fixed right now otherwise Google Play / Amazon distribution will be a nightmare. [import]uid: 133261 topic_id: 32451 reply_id: 130425[/import]

#8

I just got an app rejected by Amazon because of startup problems on an Android phone:
http://developer.coronalabs.com/forum/2012/11/09/build-947-app-rejected-amazon-not-starting-android-device-motorola-mb865

Might be related.

Best,
Andreas

[EDIT]

I now think this is not related, I explain this in the post I linked above. [import]uid: 107675 topic_id: 32451 reply_id: 130423[/import]

#9

I just got an app rejected by Amazon because of startup problems on an Android phone:
http://developer.coronalabs.com/forum/2012/11/09/build-947-app-rejected-amazon-not-starting-android-device-motorola-mb865

Might be related.

Best,
Andreas

[EDIT]

I now think this is not related, I explain this in the post I linked above. [import]uid: 107675 topic_id: 32451 reply_id: 130423[/import]

#10

Have you guys got a look at this yet? [import]uid: 88922 topic_id: 32451 reply_id: 131091[/import]

#11

Have you guys got a look at this yet? [import]uid: 88922 topic_id: 32451 reply_id: 131091[/import]

#12

Still a problem with build 971 [import]uid: 88922 topic_id: 32451 reply_id: 132414[/import]

#13

Still a problem with build 971 [import]uid: 88922 topic_id: 32451 reply_id: 132414[/import]

#14

Based on the reports from above and on some “*” reviews because the game wouldn’t start I excluded now the following devices on Google Play (I guess the list will be growing, only 4000 downloads so far:
https://play.google.com/store/apps/details?id=com.frozengun.freeze

Bad devices (okay, maybe not bad, but they don’t want to run my game!):

HTC
HTC One S(ville)
HTC One S(villec2)
HTC One SV(k2ul)

LG
LG-P920(cosmo_268-06)
LG-P920(cosmo_454-XXX)
LG-P920(cosmo_466-92)
LG-P920(cosmo_505-XXX)
LG-P920(cosmo_515-XXX)
LG-P920(p920)
LG-P920(cosmo_VDF-XXX)
LG-P920(cosmo_TMO-XXX)
LG-P920(cosmo_OPT-XXX)
LG-P920(cosmo_OPEN-CN)
LG-P920(cosmo_MOR-XXX)
LG-P920(cosmo_MEA-XXX)
LG-P920(cosmo_H3G-XXX)
LG-P920(cosmo_EUR-XXX)
LG-P920(cosmo_ESA-XXX)
LG-P920(cosmo_CIS-XXX)
LG-P920(cosmo_BAL-XXX)
LG-P920(cosmo_525-05)
LG-P920(cosmo_525-01)
LG-P925(p925)
LG-P925(cosmo_310-410)
LG-P925g(p925g)
LG-P925g(cosmo_302-720)
LG-SU760(su760)

Motorola
XT910(umts_spyder)
DROID RAZR(cdma_spyder)
DROID RAZR HD(vanquish)
MB865(edison)
Atrix(olympus)
Droid Bionic(cdma_targa)

Samsung
Exhibit 4G(SGH-T759)

Sony Ericsson(4)
LT18i(LT18i)
LT18a(LT18a)
LT15a(LT15a)
Xperia Arc(LT15i) [import]uid: 133261 topic_id: 32451 reply_id: 133186[/import]

#15

I’ll bring this up to the team!
[import]uid: 199310 topic_id: 32451 reply_id: 133218[/import]

#16

Have you filed a bug report with a project that demonstrates the problem? We can’t debug your project code so you need to give is a short test case that shows the problem. Saying you have reported crashes and a list of devices doesn’t really help us determine if there is a problem in CoronaSDK.

There are many things that you can do in your app that will cause problems and are not bugs in Corona. Android devices are all over the map in terms of hardware implementation and speed which change the dynamics of how your code interacts. If it’s a Corona bug you should be able to create a short test case that demonstrate the problem or demonstrate it with our sample code. [import]uid: 7559 topic_id: 32451 reply_id: 133224[/import]

#17

Based on the reports from above and on some “*” reviews because the game wouldn’t start I excluded now the following devices on Google Play (I guess the list will be growing, only 4000 downloads so far:
https://play.google.com/store/apps/details?id=com.frozengun.freeze

Bad devices (okay, maybe not bad, but they don’t want to run my game!):

HTC
HTC One S(ville)
HTC One S(villec2)
HTC One SV(k2ul)

LG
LG-P920(cosmo_268-06)
LG-P920(cosmo_454-XXX)
LG-P920(cosmo_466-92)
LG-P920(cosmo_505-XXX)
LG-P920(cosmo_515-XXX)
LG-P920(p920)
LG-P920(cosmo_VDF-XXX)
LG-P920(cosmo_TMO-XXX)
LG-P920(cosmo_OPT-XXX)
LG-P920(cosmo_OPEN-CN)
LG-P920(cosmo_MOR-XXX)
LG-P920(cosmo_MEA-XXX)
LG-P920(cosmo_H3G-XXX)
LG-P920(cosmo_EUR-XXX)
LG-P920(cosmo_ESA-XXX)
LG-P920(cosmo_CIS-XXX)
LG-P920(cosmo_BAL-XXX)
LG-P920(cosmo_525-05)
LG-P920(cosmo_525-01)
LG-P925(p925)
LG-P925(cosmo_310-410)
LG-P925g(p925g)
LG-P925g(cosmo_302-720)
LG-SU760(su760)

Motorola
XT910(umts_spyder)
DROID RAZR(cdma_spyder)
DROID RAZR HD(vanquish)
MB865(edison)
Atrix(olympus)
Droid Bionic(cdma_targa)

Samsung
Exhibit 4G(SGH-T759)

Sony Ericsson(4)
LT18i(LT18i)
LT18a(LT18a)
LT15a(LT15a)
Xperia Arc(LT15i) [import]uid: 133261 topic_id: 32451 reply_id: 133186[/import]

#18

I’ll bring this up to the team!
[import]uid: 199310 topic_id: 32451 reply_id: 133218[/import]

#19

Have you filed a bug report with a project that demonstrates the problem? We can’t debug your project code so you need to give is a short test case that shows the problem. Saying you have reported crashes and a list of devices doesn’t really help us determine if there is a problem in CoronaSDK.

There are many things that you can do in your app that will cause problems and are not bugs in Corona. Android devices are all over the map in terms of hardware implementation and speed which change the dynamics of how your code interacts. If it’s a Corona bug you should be able to create a short test case that demonstrate the problem or demonstrate it with our sample code. [import]uid: 7559 topic_id: 32451 reply_id: 133224[/import]

#20

Hi Tom,

I’m used to filing bug reports for Coronalabs SDK, already did a few (and with my other dev account at the second company, too).

But how should I do this? I don’t have any of these devices I get the reports from the customers where Coronalabs app just crash on startup.

But take for example the Motorola MB 865:

* I got reports from Google Play customers about a crash on startup - so I excluded it on Google Play

* my game was rejected by Amazon for the Android appstore, because they tested it on a Motorola MB 865 and it crashed on startup. The Kindle version is fine, and the compiled for Android version worked on almost all Android devices, too. But not on the Motorola. When I uploaded the next update they didn’t test on the Motorola, so the game is live now on Amazon. But as soon as someone with a Motorola MB865 donwloads it I will get a bad rating - because on Amazon Android appstore devs cannot exclude certain devices, this is much better on Google Play

And there’s nothing bad my game does on startup, the game runs fine across almost all devices, e.g. the Samsung devices (there’s only the problem that you have to exclude the ARMv6 devices manually when you upload the binary the FIRST TIME, you cannot change this later!), NOOK devices, all iOS devices…

I think the worst thing that I’m doing is using flurry analytics, this seems a bit unstable.

So no, I cannot buy these devices and compile testcases. That’s the reason for using a multi platform dev system like the Coronalabs SDK or Adobe AIR for mobile - this should be done by the companies providing the SDKs.

My game “Freeze!” for example (out now on all major App Stores, iTunes, Amazon, NOOK, Google Play, Samsung) has now about 15.000 Downloads on Google Play in the first few days (freemium) and has already more than 400 ratings with an average of 4.5 / 5. But the ratings would be even better if there would be these “*” ratings for devices where the game crashes on startup.

But hey - on the other hand it works on about 95% of all devices, so this is great, too! :slight_smile:

Best,
Andreas
[import]uid: 133261 topic_id: 32451 reply_id: 133408[/import]