snapShot items distort when device returns from standby.

Audio and Graphics
#1

Well, the title says it all, I’m using the snapshot to make a duplication of a text object so I could work some blur magic on it, and use it behind the text so I’ll have a glow effect, and it works just fine, but when I have these snapshots on my screen (Android and iOS, phone and tablets) and the device switched to standby, when it comes back on, the snap shot is completely color distorted, please see files attached for example.

How can avoid this??

Thanks.

#2

Hi @formatc,

This happens on both iOS and Android, and on every device you’ve tested on? Which specific devices are those? And which build of Corona are you using?

Best regards,

Brent

#3

I’m not at my work computer at the moment, but I believe I use build 2100 (or the first official graphics.2 version), and I’ve tested on these devices:

iPhone 4/4S/5 with OS 6.2 and 7 each, on Galaxy S2/3, on iPad (retina) 2 and on Galaxy note 3;

And it happens on all of them, when returning from stand by, for a second we see the screen normally, then there is some kind of refreshing of the screen, and them every element created with a snapShop gets all mixed up to different degrees and colors.

#4

Hi @formatc,

When you have a chance, could you try this using a more current public build, i.e. #2189?

Thanks,

Brent

#5

Back at my desk at work, I’m using build number 2161, but I’ll get the build you recommended and have a try, and update of any changes.

#6

I’ve installed the latest build (#2220) and it’s not any better, it’s even worst…:

(these were taken on my Galaxy S3).

#7

I’ve seen this on the snapshot documentation:

When an app is suspended, the Android OS removes all OpenGL textures from memory. When the app is resumed, Corona must reload all images, but the capture image no longer exists in memory. If you need to restore a snapshot image in Android, one solution is to save the returned capture image to file via the display.save() function.

but this does not account for the distorted thing that remains instead of the image, also, it does not account for the same issue we see on iOS.

#8

i’ve resolved the problem by saving the snapshop I’m generating to a local file, and then before generating the snapshot I check to see if the file exist before I make and save the snapshot, if it does I load the local image instead, if it does not exist, I make the snapshot and save it then load the newly saved image, and thus I also eliminate the use of the actual snapshop which for some reason causes the app to run slower then it should (probably memory overload???), this solved my problem, but it’s a work around, not a fix to the bug presented.

#9

Hi @formatc,

May I ask you to file a bug report/project for this? Just the buttons example would be good.

Thanks,

Brent

#10

Yep, I can do that.

#11

Hi @formatc,

This happens on both iOS and Android, and on every device you’ve tested on? Which specific devices are those? And which build of Corona are you using?

Best regards,

Brent

#12

I’m not at my work computer at the moment, but I believe I use build 2100 (or the first official graphics.2 version), and I’ve tested on these devices:

iPhone 4/4S/5 with OS 6.2 and 7 each, on Galaxy S2/3, on iPad (retina) 2 and on Galaxy note 3;

And it happens on all of them, when returning from stand by, for a second we see the screen normally, then there is some kind of refreshing of the screen, and them every element created with a snapShop gets all mixed up to different degrees and colors.

#13

Hi @formatc,

When you have a chance, could you try this using a more current public build, i.e. #2189?

Thanks,

Brent

#14

Back at my desk at work, I’m using build number 2161, but I’ll get the build you recommended and have a try, and update of any changes.

#15

I’ve installed the latest build (#2220) and it’s not any better, it’s even worst…:

(these were taken on my Galaxy S3).

#16

I’ve seen this on the snapshot documentation:

When an app is suspended, the Android OS removes all OpenGL textures from memory. When the app is resumed, Corona must reload all images, but the capture image no longer exists in memory. If you need to restore a snapshot image in Android, one solution is to save the returned capture image to file via the display.save() function.

but this does not account for the distorted thing that remains instead of the image, also, it does not account for the same issue we see on iOS.

#17

i’ve resolved the problem by saving the snapshop I’m generating to a local file, and then before generating the snapshot I check to see if the file exist before I make and save the snapshot, if it does I load the local image instead, if it does not exist, I make the snapshot and save it then load the newly saved image, and thus I also eliminate the use of the actual snapshop which for some reason causes the app to run slower then it should (probably memory overload???), this solved my problem, but it’s a work around, not a fix to the bug presented.

#18

Hi @formatc,

May I ask you to file a bug report/project for this? Just the buttons example would be good.

Thanks,

Brent

#19

Yep, I can do that.