Display.Save() Bug, time to fix it.

Solar2D General Questions/Discussion
#1

Hey guys,

I posted about this over 6 months ago.  I use the display.save API to take a snap shot of something that the user has created.  It works fine on IOS but on Android (specifically my Galaxy S3), the screenshot gets warped.

here is an example:  image_zps800af279.png

Here is another forum topic about the exact problem: http://forums.coronalabs.com/topic/19690-build-772-displaycapture-image-is-warped-on-some-andriod-devices/

This is a big deal that is limiting my android version of my app.  This has been known about for a long time, can we PLEASE get some progress on getting this bug fixed?

Let me know of any information that might be helpful in resolving this issue. Thanks.

#2

Do you have your bug report ID number where I can go see if I can see anything?  The bug report there was closed.  If you have not filed one, please do, one of the problems is finding the right device combination that seems to demonstrate this issue.  We would like to get it fixed.

#3

Hey Rob,

I just found the old thread from November, it starts here: http://forums.coronalabs.com/topic/27148-creating-facebook-app-for-android-quesiton/page-3

It looks like back them I did open a bug case number, it is: “Case 18621”

No idea if its still open, etc.

#4

I’ve asked the engineers to investigate this when they get back next week.

#5

Sounds good thanks Rob, ill check back next week as well.

#6

Just a bump to remind the team to please take a look at this ASAP, thanks.

#7

They just got back today.  I’ve not heard anything yet.

#8

Thats fine, just wanted to make sure they at least were notified, thanks Rob.

#9

Any updates on this? Sorry but I don’t want this to be put off again for another 6 months.

#10

I posted a workaround on the other thread: http://forums.coronalabs.com/topic/27148-creating-facebook-app-for-android-quesiton/page-3

#11

@Perry,

Thank you for that, I will give it a try and report!

#12

@Perry, unfortunately that was not a solution for me.  Still has a skewed image on my Galaxy S3.

#13

I assume you tried a variety of adjustments to the group size and didn’t just stick with the -2,+2 in my example.  The goal is to get to a size divisible by 4.

What is the exact model of your Galaxy S3?  The one we have here doesn’t have the issue and I’m told that there are many different types of S3.

Here’s a function that will print all the info about a device to the console:

function logDeviceInfo() print("Device Info at " .. os.date( "%c" )) print(" model: " .. tostring(system.getInfo("model"))) print("architectureInfo: " .. tostring(system.getInfo("architectureInfo"))) print(" build: " .. tostring(system.getInfo("build"))) print(" deviceID: " .. tostring(system.getInfo("deviceID"))) print(" environment: " .. tostring(system.getInfo("environment"))) print(" name: " .. tostring(system.getInfo("name"))) print(" platformName: " .. tostring(system.getInfo("platformName"))) print(" platformVersion: " .. tostring(system.getInfo("platformVersion"))) print(" maxTextureSize: " .. tostring(system.getInfo("maxTextureSize"))) print(" maxTextureUnits: " .. tostring(system.getInfo("maxTextureUnits"))) print(" appName: " .. tostring(system.getInfo("appName"))) print("appVersionString: " .. tostring(system.getInfo("appVersionString"))) end

Run that on your device and post the result.

#14

@Perry,

I did just try doing + - 4 on the screen capture and that did work for my device.  However I worry that this will then in turn cause it to not work on other devices? What are your thoughts?

Here is my device log as well:

07-17 10:54:24.522 I/Corona  (9715): Device Info at Wed Jul 17 10:54:24 2013
07-17 10:54:24.522 I/Corona  (9715):            model: SCH-I535
07-17 10:54:24.522 I/Corona  (9715): architectureInfo: ARM Neon
07-17 10:54:24.522 I/Corona  (9715):            build: 2013.1158
07-17 10:54:24.522 I/Corona  (9715):         deviceID: 5ed9be79a19e8253
07-17 10:54:24.522 I/Corona  (9715):      environment: device
07-17 10:54:24.522 I/Corona  (9715):             name: unknown
07-17 10:54:24.522 I/Corona  (9715):     platformName: Android
07-17 10:54:24.522 I/Corona  (9715):  platformVersion: 4.1.2
07-17 10:54:24.522 I/Corona  (9715):   maxTextureSize: 4096
07-17 10:54:24.522 I/Corona  (9715):  maxTextureUnits: 2
07-17 10:54:24.522 I/Corona  (9715):          appName: BoM Touch Current
07-17 10:54:24.522 I/Corona  (9715): appVersionString: 1.0

#15

Do you have your bug report ID number where I can go see if I can see anything?  The bug report there was closed.  If you have not filed one, please do, one of the problems is finding the right device combination that seems to demonstrate this issue.  We would like to get it fixed.

#16

Hey Rob,

I just found the old thread from November, it starts here: http://forums.coronalabs.com/topic/27148-creating-facebook-app-for-android-quesiton/page-3

It looks like back them I did open a bug case number, it is: “Case 18621”

No idea if its still open, etc.

#17

I’ve asked the engineers to investigate this when they get back next week.

#18

Sounds good thanks Rob, ill check back next week as well.

#19

Just a bump to remind the team to please take a look at this ASAP, thanks.

#20

They just got back today.  I’ve not heard anything yet.