Android graphics problem (build 2011.703)

Solar2D Android
#41

Hope this helps… Kind of strange that no one from Corona is posting on this issue as present there are MANY devices affected by this issue.

S1 is SnapDragon 1 and S2 is SnapDragon 2

—Not Working
Galaxy S Plus (S2 - MSM8255T) //SAMSUNG galaxy S±19001(480x800) -OS version 2.3.1-having graphics issue
Sony Xperia (S2 - MSM8255T) sony xperia(480x854) -OS version 2.3.1-having graphics issue
HTC Thunderbolt (S2 - MMSM8655) // HTC thunderbolt(480x800) -OS version 2.2 having graphics issues
HTC EVO (s1 QSD8650) - HTC evo(480x800) -Android™ 2.3 (Gingerbread) having graphics issues
—Working
HTC Amaze (s3 - MSM8260) //HTC AMAZE(540x960) -OS, v2.3.4 (Gingerbread)-working well
Unknown exact Model - SAMSUNG galaxy S-19000M(480x800) -OS version 2.2-working well
Unknown exact Model - SAMSUNG galaxy S-19003(480x800) -OS version 2.2-working well
Unknown exact Model - SAMSUNG galaxy TAB(1024x600) -OS version 2.2-working well
Acer tab-1280x800 -OS version 3-working well [import]uid: 130081 topic_id: 19801 reply_id: 93175[/import]

#42

Hi,

I found one similarity between all the devices.All the devices having graphics issues which runsunder the Android OS version 2.3(GingerBread)

Galaxy S Plus OS version 2.3.1-having graphics issue
Sony Xperia OS version 2.3.1-having graphics issue
HTC incredible OS version 2.3.1 having graphics issues
HTC EVO -Android™ 2.3 (Gingerbread) having graphics issues

please check the os compatibility once again and solve the issue as early as possible.
thanks and regards
Nilesh Gawade

[import]uid: 84082 topic_id: 19801 reply_id: 93244[/import]

#43

Everyone,

We haven’t given up on this issue yet… it’s just that we haven’t found a solution yet. The thing is that it doesn’t look like a bug in our code, but a bug in the OpenGL driver of these devices. We’re getting no GL Errors on our end, yet OpenGL fails to display textures at times on these devices… thus our conclusion that this is a driver bug.

To make things more interesting, try this… when you reproduce this bug where the bitmap is not shown on screen, press the Home button to suspend your app, then go back to your app, and notice that the bitmaps are now shown correctly.

Somehow we have to find a work-around for this issue, but we’ve yet to find one. We’ll keep trying of course. [import]uid: 32256 topic_id: 19801 reply_id: 93324[/import]

#44

I would be a buyer of that explanation if the issue was not present in the 591 build. The fact is that hardware and software has remained static since before 591 and the only thing that has changed is Corona.

To quote Mr. Spock…
“once you remove all other possibilities, the only remaining possiblity, however unlikely, must be true.”

[import]uid: 130081 topic_id: 19801 reply_id: 93406[/import]

#45

You will also notice your last post was in Jan… A whole month of us hanging in the wind while we sit here with builds that cannot be published. Please keep us in the know from now on. It keeps the masses content :slight_smile: Thank you for filling us in today. Knowing it hasn’t been missed eases my stress. [import]uid: 130081 topic_id: 19801 reply_id: 93408[/import]

#46

Joshua Quick,
Hi friend I have noticed that I made the android build from 2011.591 and 2011.704
both are stable versions.But I didn’t found any graphics issue on 2011.591 but the thing is that i cant use 2011.591 because all the code i have written is used most of new functionalities from 2011.704.I tried the same code on 2011.704 and found the graphics issue.

conclusion is:
2011.591:dont have graphics issue for android builds but game runs slowly and slower down the device
2011.704:having graphics issue on android builds but game runs faster and doesn’t slow down your device.
and the graphics issue is for the some of the devices
example:
samsung galaxy s
samsung galaxy s+

both are exactly same devices with the version change but the graphics issue is no there for samsung galaxy s and graphics issue is there for samsung galaxy s+

thanks and regards

Nilesh Gawade [import]uid: 84082 topic_id: 19801 reply_id: 93445[/import]

#47

Husshhh!! ,
so happyyyyyyy.
finally solved the graphics issue.The graphics get replaced with blank rectangles in my android build but finally i changed the code and issue get resolved.

there is problem with using ui.lua file.I used ui.lua file everywhere for the use of ui.newButton in my code and after the long try i got the problem that the graphics issue is because of using ui.newButton and i changed it to display.newImageRect.

from last two weeks i just try try and try for daynight.I changed the graphics,change the code,change the corona versions,tested on multiple device and finally done.

thanks and regards
Nilesh Gawade [import]uid: 95072 topic_id: 19801 reply_id: 93765[/import]

#48

Hi Nilesh,

Congrats! I found a similar work-around.

I was having the problem all over the place with my button class. I had built my own button class. I was using a different display group for the button in each state (normal, pressed, inactive), and I was swapping out “touch” event listeners between the display groups based on the state of the button (i.e. there is a “touch” listener on the “normal” button group, but when the player presses it, I removed that event listener and added a “touch” listener to the “pressed” group to see when the player released the button - very complex!)

I refactored my button class to use a single display group with different graphics resources for the button in different states (normal, pressed, inactive), and I used a single “touch” event listener associated with the group.

This (mostly) fixed the problem across the board. I have no idea why…

Hope this helps. [import]uid: 76436 topic_id: 19801 reply_id: 93767[/import]

#49

Hmmm… so the UI library makes this issue more likely to occur. That’s a pretty big clue. Thanks for sharing that. Isolating this issue has been quite a chore, because so much has changed between release versions. [import]uid: 32256 topic_id: 19801 reply_id: 93846[/import]

#50

MaCai,
thanks buddy but instead of this complex programming i preferred newimage with event listeners and even you can add button effect to it by minimising the alpha and scale.

Joshua Quick
welcome man but i have also submitted the bug for android ads. Inmobi Ads not getting displayed in our android phones .InMobi works well for the IOS builds.While not for android builds but Inneractive ads displayed correctly.I tried by changing the ads-app ID but still it not displaying.
the only change in IOS and Android is that INTERNET permission is needed I have also added this.
thanks and regards
Nilesh
[import]uid: 95072 topic_id: 19801 reply_id: 94369[/import]

#51

Hi Nilesh,

I think you and I are saying the same thing. I used to do something pretty complex with my button class, but now I just use three images (newImage) in a single display group and have a single event listener to manage the player touches and releases.

When I used multiple display groups and was switching event listeners in and out, I was seeing the bug. Now I’m not.

Basically, I refactored my code from something complex (and pretty stupid) to something simple and obvious… and it works a lot better.

Bottom line for people with this issue: see if there’s a way of implementing your code in a “simpler” way.

Good luck! [import]uid: 76436 topic_id: 19801 reply_id: 94448[/import]

#52

Everyone,

Find the links of our first game in corona sdk

http://itunes.apple.com/in/app/outcome-2012-free-iphone-edition/id507644210?mt=8
https://play.google.com/store/apps/details?id=com.outcome2012

thanks and regards
Nilesh [import]uid: 95072 topic_id: 19801 reply_id: 95058[/import]

#53

Everyone,

There was a new Corona bug introduce in build 759 where images would disappear on apps that use masks. This typically only happens on Android devices with low end graphics hardware. If your app uses masks, then I recommend that you revert to build 758 or older to work-around. I don’t want that issue to be confused with the one MaCai was originally talking about on this thread. [import]uid: 32256 topic_id: 19801 reply_id: 95280[/import]

#54

Nilesh,

We have your bug report about the graphics issue that you are running into. I have not seen a bug report from you in regards to InMobi. That’s off topic on this thread so if you can give me the bug report number that was assigned to it, then we’ll discuss it separately via our bug tracking system. Thanks! [import]uid: 32256 topic_id: 19801 reply_id: 95282[/import]

#55

Hi,
Here is the bug title “InMobi ads not get displayed in the android devices” i dont have but id because it was submitted from our licence version account.
Anyway this is the new bug ID :=case #13100

thanks and regards
Nilesh
[import]uid: 95072 topic_id: 19801 reply_id: 95355[/import]

#56

Hi, I’m having the same problem Joshua is writing on post #52 (images disappearing when using mask on Android). Is there any solution you’re working on?
Currently, I can build the app with build 758 and it’s working ok, but any other builds after that show the same problem.

I have a HTC Desire S.
[import]uid: 9158 topic_id: 19801 reply_id: 99646[/import]

#57

shedder,

The masking issue that you’ve mentioned is a different problem than the one mentioned by other people on this thread. The problem you are seeing is a bug in Corona that was introduced in build 759 when we improved rendering performance. Fixing that is a top priority issue for us. We plan on resolving this issue in the next few weeks.

The other HTC issues that are mentioned on this thread is a much tougher problem and we have yet to solve it. That issue does not happen to most Corona developers and only seems to happen under particular circumstances which we have yet to determine. Even though we have reproducible test case for this issue, the scripts are complex enough that they don’t really help us isolate the problem yet. This is a top priority issue for us to solve too, but we can’t say when it will be fixed until we discover the root cause of it. [import]uid: 32256 topic_id: 19801 reply_id: 99844[/import]

#58

Everyone,

This issue is now fixed. The fix will be made available in daily build #882.

It turns out that this issue was caused by an OpenGL driver bug. That is why this issue only occurred on particular Android devices. It also made this bug very difficult to reproduce and isolate, especially since there were no errors in our code and it turned out it was the OpenGL driver that was doing the wrong thing. It took us a really long time to track it down… but we’ve finally nailed it.

In any case, the upcoming daily build has a work-around for this issue. If you can let us know if this daily build fixes this issue for you, then that would be much appreciated. Thanks! [import]uid: 32256 topic_id: 19801 reply_id: 120379[/import]

#59

Everyone,

This issue is now fixed. The fix will be made available in daily build #882.

It turns out that this issue was caused by an OpenGL driver bug. That is why this issue only occurred on particular Android devices. It also made this bug very difficult to reproduce and isolate, especially since there were no errors in our code and it turned out it was the OpenGL driver that was doing the wrong thing. It took us a really long time to track it down… but we’ve finally nailed it.

In any case, the upcoming daily build has a work-around for this issue. If you can let us know if this daily build fixes this issue for you, then that would be much appreciated. Thanks! [import]uid: 32256 topic_id: 19801 reply_id: 120379[/import]