Hi,
I just migrated my project to the new Graphics 2.0 engine (Build.2076). It looks fine, and even performs better on some low end android devices. But one of my users reported a problem on his Galaxy S2 device. Screen goes blank, like there is no rendering or textures assigned.
Do you encounter any problems on Samsung Galaxy S2? Does S2 support full opengl es 2.0 specs?
best.
I’ve got an S2 and I’ve not come across any device specific problems.
If your user can reproduce the issue, you can always send me a build and I’ll test to see what happens here.
@rakoonic: i really appreciate that. here is my google play url:
https://play.google.com/store/apps/details?id=com.he2apps.kelimelik
its a words with friends clone available in turkish. on the first screen please press green button to create a guest account. i think it would be enough to see the main menu screen correctly.
thanks again 
Installed and started up. Green button takes me to a screen with a red (yeni oyun) and purple (oyunlarim) button, and 3 smaller ones below, green yellow and blue which I assume are web, settings and errr… pacman
That’s what you’d expect, I imagine. Anything else I can try for you?
thank you very much, everything is working as expected. it may be an os issue. ( or an unsufficient memory problem?). could you please tell me your android version?
4.1.2 jelly bean.
If they are running a custom firmware (ie not the stock firmware), that could be the problem
You could have them install a console log app that lets them see what’s going on with the logcat and see what error you are hitting. They need to make sure there is enough free space on the device as well.
Rob
I contacted some of my users and let them sent me their logcat output. There are no error messages, and no exceptions. 3 of them reported that application is running, ie touch events and scene transitions are working but there is nothing visible on the screen. a complete darkness.
Below is a giant logcat output. at line 13259, our test device begin to load my application (com.he2apps.kelimelik) to memory. There following some shared library loading stuff (openal, libvorbis, liblua etc) and and at line 13621 my application writes its first log message (lua code started there).
I feel very frustrated, at least I expected to get some exceptions 
https://drive.google.com/file/d/0B-ir3_lXb5y9VGxybkdlNDVVLXM/edit?usp=sharing
Do you have any suggestions?
Engineering responded to me and basically it’s possible that an error could be happening in Lua before Corona creates any display objects. The engineer suspects that you might be trying to use a service that’s not available on the device and an API is returning nil. He suggest that:
The simplest means of tracking down Lua errors is to set “showRuntimeErrors” to true in the “config.lua” file…
http://docs.coronalabs.com/guide/basics/configSettings/index.html#runtime-errors
Alternatively, you can set up a listener for the “unhandledError” event as well.
There are multiple hardware variations of the SII, like different CPUs and such which makes dealing with Samsung devices more difficult.
Rob
Good point Rob - just for completeness then - I have no probs on mine, and it is a model GT-I9100 with Android 4.1.2. Just in case that helps with comparisions.
Thats the best version of the G2. There is one other model also. The difference being that the other model has a much weaker GPU
I have a Galaxy 2 Skyrocket (SAMSUNG-SGH-I727) which is running 4.0.4 which is another model of the Galaxy 2, it seems to work on that.
I have received tons of email messages from my users. A vast variety of devices seems problematic including galaxy s3, s4, s3 mini, and a couple of galaxy tabs. But I am also certain that some of my users also do not encounter any problems even though they are using the same devices.
I released a new update which is using the old Graphics 1.0 library (Build.1260). All problems are gone. Something should be definitely wrong with the build 2076. Below are some screenshots taken on a problematic device. (some textures are missing, fonts are missing, some textures are garbled etc)
http://imgur.com/QL4qxPI,9Ns5NHf,AFPki4T,YX7fESi#0
http://imgur.com/QL4qxPI,9Ns5NHf,AFPki4T,YX7fESi#1
The S3 and S4 have the same issues with some models having under powered GPU’s, so you could be hitting that as well.
Thanks
Rob
I’ve heard about the weaker GPUs, but I can’t imagine ‘weaker’ being an issue here having seen the screen in question, it really isn’t doing anything in particular, and I doubt the images are even remotely near the texture size limit.
It does seem very odd.
The only thing that strikes me as a possibility might be locale settings or languages - are you using any funny characters in your file names? I really can’t think of anything else 
@rakoonic: no, i am not using any fancy characters in file names. Only some of my file names contain @2x (for autoscaling stuff)
Anyway, I build Corona’s own “Hello World” sample by using Build 2076, and sent it to my testers. 2 of them can not see anything after launch (black screen problem)
Their devices are:
Samsung Galaxy S2 i9100G (full specs here)
LG Optimus L9 P760 (full specs here)
Both of the above devices contain enough ram, and processing power i think (dual core Cortex A9 processor and PowerVR SGX540 GPU).
It looks like Graphics 2.0 is not ready (at least for my user base) - back to build 1260
If even a simple test case doesn’t work properly, then maybe someone from Corona can chime in to ask what info they’d need from these guys to look further into it - if it fails as you describe that does indeed warrant some urgent checking on their part.
I have the same issue with the Razr Maxx which has the PowerVR SGX540 GPU as well. I have a thread about it here: http://forums.coronalabs.com/topic/41369-black-screen-with-20132076-public-build-on-razr-maxx/
I have a similar issue on all iOS devices I tested on. I was able to boil down a reproducible test case and submitted it with a bug, case 28408. Here is the forum thread with details on the iOS bug:
http://forums.coronalabs.com/topic/41677-weird-framebuffer-image-bug-on-ios-devices-in-g-20-builds/