Nabi - Image issue on device resume

Solar2D Android
#1

Hello,

Some months ago I had an issue with Nabi devices (couldn’t find the post), where when we submitted the apk for publishing they would kick it back to us saying something like:

-UI errors happens if suspend resume the device in certain pages

What happens is some of the image assets, instead of being reloaded when the app suspends then resumes, instead end up being black rects.  And it’s random.  For instance, in the same scene with a play, pause, and retry button, sometimes the play button will be replaced by a black rect, and it will be the size of the play button.  Sometimes it’ll be the pause button, and the play button is just fine.  Other times nothing happens… as I said, random.

Before when I posted this issue, someone recommended this block of code, which worked for all builds up to this point:

local function onKeyReceived( event ) if event.phase == "down" and event.keyName == "back" then system.request( "suspendApplication" ) return true end end Runtime:addEventListener( "key", onKeyReceived )

However, with a most recent submission to Nabi, even with the code above they told us they were getting the same issues again.  Oddly, we’ve had projects before AND after this that have gone through, and this one for some reason didn’t.  I’m kind of tempted to resubmit to see if it does come up again, but am wondering if anyone else may have experienced the issue and have some ideas.

#2

They had also given us their logs when the issue occurred after suspending/resuming:  http://bit.ly/1BMjpIa

Doesn’t seem to help much, though.

#3

I’ve seen this problem in the past due to some setDefault configurations. Here’s a forum post explaining their problem and solution.

#4

I don’t use the setDefault method at all, nor am I tiling any of my images… I wasn’t aware of it, but is it actually necessary for Nabi builds? Also, this issue only happens when the device is suspended then resumed… the images otherwise load and are viewed just fine until that occurs, whereas that user *seems* to have had issue in just general testing for their app.  We publish to Google/iOS/Amazon/Nook as well, and all those builds are completely okay, too, even when the app suspends/resumes.  We’ve only ever encountered this issue for Nabi builds.

#5

Understood. It was more of a possibility than a concrete reason.

Are you using the latest daily build? Also, one would presume, from a cursory glance at the Nabi website, they use a custom ICS Android build. Would I be right in saying that, or is it pretty much vanilla with a Nabi skin on top?

#6

They had also given us their logs when the issue occurred after suspending/resuming:  http://bit.ly/1BMjpIa

Doesn’t seem to help much, though.

#7

I’ve seen this problem in the past due to some setDefault configurations. Here’s a forum post explaining their problem and solution.

#8

I don’t use the setDefault method at all, nor am I tiling any of my images… I wasn’t aware of it, but is it actually necessary for Nabi builds? Also, this issue only happens when the device is suspended then resumed… the images otherwise load and are viewed just fine until that occurs, whereas that user *seems* to have had issue in just general testing for their app.  We publish to Google/iOS/Amazon/Nook as well, and all those builds are completely okay, too, even when the app suspends/resumes.  We’ve only ever encountered this issue for Nabi builds.

#9

Understood. It was more of a possibility than a concrete reason.

Are you using the latest daily build? Also, one would presume, from a cursory glance at the Nabi website, they use a custom ICS Android build. Would I be right in saying that, or is it pretty much vanilla with a Nabi skin on top?