Please see the attached file. It’s supposed to be an image, but it displays like this in some rare case.
Here are what I know:
(1) It seems only Android devices have this kind of problem. No iOS user ever reports this.
(2) Not all Android devices have this problem. I have never reproduced this problem for my own Android devices.
(3) The image is shown inside a container.
Anyone can shed some light on this?
What is the image supposed to look like and what are its dimensions?
I’ve just seen something very similar in an app I’m testing.
It works fine on two Android devices - a Nexus 4 and Nexus 7 both running Android 4.4.2. However, the identical test app on a Motorola Xoom (running 4.0.4) has some display elements, including text, appearing as these smeary lines. There also seem to be some other issues - entirely missing images and an ‘invisible’ scrollview that is however there when you touch it.
This is using the latest public build (I was having some other issues with Android on the daily builds, but that’s another story …)
Hi @joe528,
Would it be possible to submit the entire project in a bug report? Then we could test it on a couple Android devices we own.
Thanks,
Brent
I know the images might be skewed for some Android devices after migrating to G2 when these images are generated by display.captureBounds(). I had reported this problem before and Corona staff replied it worked as design.
After I put images inside containers, I think the problem goes away.
So I am guessing if the user actually is not using the latest version of my app. I am waiting for the user’s response. Hope he/she will respond… but you know the users…
I will submit a bug report if I confirm the user is using my latest version.
The Xoom has a Tegra 2 chipset which we know to be problematic with the last public build of Corona SDK, since you’re a pro subscriber try the latest daily build and see if things are better on those Devices.
Rob
Thanks Rob
I’ve tried daily build 2014.2154 but with the same result on the Xoom.
That build also seems to introduce issues on my other android devices - the scrollview and several other images disappear. All works fine on iOS.
Jerry
Doh! Sorry Rob, for ‘scrollview’ above read ‘tableview’ - the tableview seems to be there when touched but becomes invisible. Works okay in the previous public build.
The user responds that he is using the latest version of my app & his device is Galaxy Tab 3 7"
Can I offer you the APK file first to see if you can reproduce it?
The engineers are going to want the source code so they can see what you’re doing. Just zip up your project folder and file a bug report with it. That way we have the build.settings, config.lua and the assets needed to try and reproduce the problem.
Rob
The problem exists with the latest Corona daily build (2014.2155)
So I filed a bug report for this, Case 29969
For more information, the user downloads my app from Google Play into his 3 different Android devices. Only Galaxy Tab 3 7-inch has this problem. His Sony Xperia S & Galaxy Note 3 don’t have this problem.
I’ve submitted my related bug with the latest daily builds as Case 29950.
We ran the code on a number of devices and cannot reproduce the issue with build 2154.
We ran it on the following devices and all the images and text looked correct.
Galaxy Tab 2 7"
Galaxy Tab 3 10"
Nexus 7
Kindle HD 7"
Galaxy Nexus (v4.0.4)
Motorola Xoom (v4.0.4)
We don’t have a Galaxy Tab 3 7" to test with but we did run it on the Motorola Xoom that was mentioned showing the failure.
@app5. Your case is not related because there are images loading errors in your code. If you looked at the logcat console you will notice it’s failing to load your images. The loading errors is caused by your @low image suffix in config.lua.
The user also has no problem for his other two Android devices (Sony Xperia S & Galaxy Note 3)
I would encourage Corona to manage to get a Galaxy Tab 3 7" to test this problem. The bug looks severe fundamentally that would affect many users’ apps (not just mine) and Galaxy Tab 3 7" should have certain market shares that shouldn’t be ignored at this moment.
We haven’t had anyone else report the problem and I couldn’t duplicate the issue with the Motorola Xoom tablet so didn’t think this issue could be reproduced. I picked up a Galaxy Tab 3, 7" on the way home and just loaded your app. It shows the problem as you described. I’ll have someone look at the issue tomorrow.
Thanks,
Tom
Hello. I encountered the same issue testing masks and containers on my Samsung Tab 3 (7-inch). Similar to @joe528, this issue never showed up when I was testing on the Simulator nor on my iPhone 5.
I made a little test program.
Testing Containers:
-- TEST 1: CONTAINER local mySheet = display.newImageRect("dashboard-main.png", 480,320); local myContainer = display.newContainer(480,320); myContainer:insert(mySheet); myContainer.x = display.contentWidth \* 0.5; myContainer.y = display.contentHeight \* 0.5;
Testing Masks:
-- TEST 2: MASK local mySheet = display.newImageRect("dashboard-main.png", 480,320); local myMask = graphics.newMask( "simple\_mask.jpg" ) mySheet:setMask(myMask); mySheet.x = display.contentWidth \* 0.5; mySheet.y = display.contentHeight \* 0.5;
Surely enough, the same issues came up. On the Simulator and my iPhone 5, I received results that you would expect. On the Tab 3, I received odd results, similar to the ones @joe528 encountered (you’re not alone!).
Is this issue still being looked into? Thank you!
As Tom said in the post above, we have been able to reproduce it on the same device and engineering is looking at it. No ETR yet.
Rob
We are looking into the issue and it seems to only affect the Galaxy Tab 3 7". We isolated it down to masked images causing the problem. Containers are just a group with a mask so any image in a container will fail too.
This issue was introduced in build 2100. In this build we fixed an issue with the Galaxy Tab 2 7". It seems not all Android (or Samsung) graphic drivers are the same and we have to add exceptions depending on the graphics GPU we encounter.
Android may seem like a great platform but we encounter these type of issues all the time because there are so many different Android devices with their own set of issues (even among the same manufacturer).
We will let you know when we have a fix that works across all our test platforms.
Tom
Hey I’m having this same problem any breakthroughs in coming up with a fix. I actually have to exclude Galaxy Tab 3s from games that used to work on the tab 3 since upgrading my games to 2.0. All my games that don’t use scroll view work fine in the tab 3.
Hi @clementcomp7. We just isolated the problem before the weekend. We likely won’t have a fix for it for a few more days and then it will roll out in a Daily build. It won’t be fixed for Starter accounts until we put out a new public build and we don’t have an ETA at the moment.
Rob