Bug on Nexus 10? Objects are being rendered transparently and device desktop is showing through.

Solar2D General Questions/Discussion
#1

We had someone at Google Play take a look at our app, with a possibility of it being featured.
On most devices it seems to be fine, but on a Nexus 10 there is a very odd graphical bug.
When they sent us a screenshot of the bug last night, it seemed to only be occurring on non-imageRect objects (i.e. newRects, newCircles, newRoundedRects), and only on objects that had some kind of semi-transparency:

http://i48.tinypic.com/4huu5l.png

As you can see, the devices desktop is showing through those objects.

We then quickly changed those objects to use newImageRect hoping that would be a temporary fix, but today we have received these screenshots from them:

http://i46.tinypic.com/2hgv6te.png
http://i48.tinypic.com/65cowk.png

The app is transparent in lots of places now, even on opaque imageRects!

Does anyone at Corona know why this has happened? It’s a bit embarrassing for us that having done the work to get it potentially featured, we have a real big glitch hit us at this point.

I think it’s definitely worth looking at ASAP.
[import]uid: 84115 topic_id: 33984 reply_id: 333984[/import]

#2

Update:

The second image is slightly misleading, the bug here is exactly the same as in the first image. The reason more of the desktop is showing through is that our pause screen has a semi-transparent rect covering the whole screen to darken it slightly.

We have now replaced all of our newRects, roundedRects, newText etc with newImage and newImageRects and have sent it back to Google, so hopefully we have a short term fix which will allow us to get the app featured.
However I’ll say again that I think it needs to be investigated ASAP.

Just to sum up the situation that the bug arose:
*Nexus 10
*Non-image objects
*object.alpha < 1.0 [import]uid: 84115 topic_id: 33984 reply_id: 135115[/import]

#3

Hi Alan,
I agree this is odd (one of the oddest things I’ve seen), especially since it appears to be on one device. I’ll discuss this with our Android engineers and see if they can determine any reason why it’s happening.

In the meantime, can you workaround this by placing a solid white rectangle at alpha 1.0 behind everything? I know that’s not a permanent solution, just suggesting it as a possible temporary fix…

Regards,
Brent [import]uid: 200026 topic_id: 33984 reply_id: 135216[/import]

#4

A rect behind behind everything did not work, that was the first thing we tried. Any objects which cause this bug seem to ‘cut through’ everything else drawn behind them.
As I say, we replaced all primitives and text with images which has worked as a temporary fix though. [import]uid: 84115 topic_id: 33984 reply_id: 135230[/import]

#5

Update:

The second image is slightly misleading, the bug here is exactly the same as in the first image. The reason more of the desktop is showing through is that our pause screen has a semi-transparent rect covering the whole screen to darken it slightly.

We have now replaced all of our newRects, roundedRects, newText etc with newImage and newImageRects and have sent it back to Google, so hopefully we have a short term fix which will allow us to get the app featured.
However I’ll say again that I think it needs to be investigated ASAP.

Just to sum up the situation that the bug arose:
*Nexus 10
*Non-image objects
*object.alpha < 1.0 [import]uid: 84115 topic_id: 33984 reply_id: 135115[/import]

#6

Hello Alan,

Wow… I’ve never heard of such an issue on any other Android device before. It’s probably an OpenGL driver bug that we’ll have to work-around on our end. Unfortunately, we do not currently have a Nexus 10 to test with at the moment. Nor does the remote testing service that we use have one either. We can’t fix this issue until we have a device to reproduce it on. I’ll talk to management about buying this device for future testing.

So, at the moment, your only option is to exclude Nexus 10 support on Google Play until we can come up with a solution.

If it makes you feel any better, Corona apps work fine on the Nexus 7. We regularly test on that device. [import]uid: 32256 topic_id: 33984 reply_id: 135497[/import]

#7

Not too sure that excluding the Nexus 10 would be a good move given that we are speaking to Google Play about featuring the app.
Our temporary fix of replacing all primitives and text with images seems to be holding for the moment.
The person who found the bug was actually someone at Google Play, so not someone who has time to test our app again and again to see if it’s definitely fixed.
We’d much prefer that we were able to assure them that the app works on their latest devices, if your management says you are able to purchase a Nexus 10 do you have any idea on when that would happen? [import]uid: 84115 topic_id: 33984 reply_id: 135510[/import]

#8

We’re looking into buying one now, but we’re finding that it’s sold out where we normally buy our devices. Probably due to the holiday season. It looks like we’re going to have to order online, which due to shipping, means we can’t look into it this week.

In the meantime, I suggest that you file a bug report so that it’ll get queued in our bug tracking system and so that we can notify you when it is fixed. You can do so by clicking the “Report a Bug” link at the top of this webpage. [import]uid: 32256 topic_id: 33984 reply_id: 135517[/import]

#9

Hi Alan,
I agree this is odd (one of the oddest things I’ve seen), especially since it appears to be on one device. I’ll discuss this with our Android engineers and see if they can determine any reason why it’s happening.

In the meantime, can you workaround this by placing a solid white rectangle at alpha 1.0 behind everything? I know that’s not a permanent solution, just suggesting it as a possible temporary fix…

Regards,
Brent [import]uid: 200026 topic_id: 33984 reply_id: 135216[/import]

#10

Hey guys - having as many key devices in the office as possible is a big priority for us. The Nexus 10 has been elusive, but we will have one in the office in the next 24 hours. I want to emphasize that we take this seriously.

We’ll have more info on this asap.
[import]uid: 10668 topic_id: 33984 reply_id: 135531[/import]

#11

A rect behind behind everything did not work, that was the first thing we tried. Any objects which cause this bug seem to ‘cut through’ everything else drawn behind them.
As I say, we replaced all primitives and text with images which has worked as a temporary fix though. [import]uid: 84115 topic_id: 33984 reply_id: 135230[/import]

#12

Hello Alan,

Wow… I’ve never heard of such an issue on any other Android device before. It’s probably an OpenGL driver bug that we’ll have to work-around on our end. Unfortunately, we do not currently have a Nexus 10 to test with at the moment. Nor does the remote testing service that we use have one either. We can’t fix this issue until we have a device to reproduce it on. I’ll talk to management about buying this device for future testing.

So, at the moment, your only option is to exclude Nexus 10 support on Google Play until we can come up with a solution.

If it makes you feel any better, Corona apps work fine on the Nexus 7. We regularly test on that device. [import]uid: 32256 topic_id: 33984 reply_id: 135497[/import]

#13

Hello Alan,

We’ve just received a Nexus 10 today and tested some of our sample apps on it. Unfortunately, we were not able to reproduce this issue. All apps that we’ve tried so far are being displaying correctly.

Would you mind sending us your project (or a link to your project) so that we can reproduce this issue for ourselves please? You can do so by clicking the “Report a Bug” link at the top of this web page.
[import]uid: 32256 topic_id: 33984 reply_id: 135822[/import]

#14

Not too sure that excluding the Nexus 10 would be a good move given that we are speaking to Google Play about featuring the app.
Our temporary fix of replacing all primitives and text with images seems to be holding for the moment.
The person who found the bug was actually someone at Google Play, so not someone who has time to test our app again and again to see if it’s definitely fixed.
We’d much prefer that we were able to assure them that the app works on their latest devices, if your management says you are able to purchase a Nexus 10 do you have any idea on when that would happen? [import]uid: 84115 topic_id: 33984 reply_id: 135510[/import]

#15

We’re looking into buying one now, but we’re finding that it’s sold out where we normally buy our devices. Probably due to the holiday season. It looks like we’re going to have to order online, which due to shipping, means we can’t look into it this week.

In the meantime, I suggest that you file a bug report so that it’ll get queued in our bug tracking system and so that we can notify you when it is fixed. You can do so by clicking the “Report a Bug” link at the top of this webpage. [import]uid: 32256 topic_id: 33984 reply_id: 135517[/import]

#16

Hey guys - having as many key devices in the office as possible is a big priority for us. The Nexus 10 has been elusive, but we will have one in the office in the next 24 hours. I want to emphasize that we take this seriously.

We’ll have more info on this asap.
[import]uid: 10668 topic_id: 33984 reply_id: 135531[/import]

#17

Ok I’ve filed a bug report with out code in it.
We’ve heard back from Google after making our own changes and they say it looks better now, but since our change was simply to change all of the primitives to images, the underlying problem is still there. [import]uid: 84115 topic_id: 33984 reply_id: 135880[/import]

#18

We did try a sample project containing rectangle and circles instead of images… and that didn’t reproduce this issue on our Nexus 10 either. I’m curious as to what is different about your app compared to ours. If you don’t want to send us your full project, then how about a stripped down version of it? Otherwise, we’re at a loss on how to reproduce this issue. Anything you can do to help us isolate this issue would be greatly appreciated. Thanks. [import]uid: 32256 topic_id: 33984 reply_id: 135938[/import]

#19

Sorry that last post should have said “with OUR code” not “with out code” - i.e. I’ve already sent you the full project. I didn’t strip it down in case I somehow took out whatever is causing the bug. [import]uid: 84115 topic_id: 33984 reply_id: 135954[/import]

#20

Okay, great! [import]uid: 32256 topic_id: 33984 reply_id: 135977[/import]