App Randomly Crashes on Certain Devices

Solar2D Android
#1

HI all,

I occasionally get reports from customers that my Corona-created apps don’t make it beyond displaying the default png loading image on certain Android devices. I now have 7 different Android devices and all apps load perfectly on all of them. Obviously I can’t afford to buy every Android device out there so I’ve got a range from budget devices to the higher end ones. Like I say - apps run fine on all of them.

Is there anything obvious I should be looking out for in this situation? Has anyone else experienced this random issue with apps just not loading on some devices?

As usual, iOS works 100% across the board.

Any ideas would be really helpful.

Thanks,

Ian

#2

Maybe you could get them to send you adb logs?

It depends on what you do during load.

I recently found that my app crashes on a device with less memory than my testing devices. I’ve had to implement ability for user to switch between graphics resolutions, so that they can choose lower graphics [although their screen would suggest using xhdpi graphics, it’s better to use hdpi]. Also, I’ve implemented a new graphics loader, which will load imagesheets with 50ms delays, in order for garbage collector to have time to release more memory.

Also… largeHeap setting in build settings does some additional magic.

The easiest thing to do is to enable the large heap setting, if you have already done that, try loading your assets with delays.

#3

Thanks for the response. I’ll certainly try those things.

Frustrating to say the least when people are having issues that I can’t replicate on any devices!

Thanks again,

Ian

#4

Maybe you could get them to send you adb logs?

It depends on what you do during load.

I recently found that my app crashes on a device with less memory than my testing devices. I’ve had to implement ability for user to switch between graphics resolutions, so that they can choose lower graphics [although their screen would suggest using xhdpi graphics, it’s better to use hdpi]. Also, I’ve implemented a new graphics loader, which will load imagesheets with 50ms delays, in order for garbage collector to have time to release more memory.

Also… largeHeap setting in build settings does some additional magic.

The easiest thing to do is to enable the large heap setting, if you have already done that, try loading your assets with delays.

#5

Thanks for the response. I’ll certainly try those things.

Frustrating to say the least when people are having issues that I can’t replicate on any devices!

Thanks again,

Ian