Hi ksan,
I think you misunderstood. I meant the fixes in the daily builds for widgets specifically 2013.2109, not my own.
I should have been clearer.
Ahh sorry about that. In any case thanks for exploring this issue. I’m sure we will all benefit. Thanks
No news yet.
Rob
I can also reproduce this on 2100 with my app on a Samsung Galaxy Tab 10.1, which uses the Nvidia Tegra 2 chipset.
Documented here:
Wonder how far back they tested that public release. The Galaxy Tab 10.1 was released in 2011, so really not that old a device.
We were finally able to duplicate the problem with an old Motorola Xoom tablet with the Tegra 2 chipset. We are looking into a fix now but it seems there is an bug in the OpenGL driver that is causing problems.
I’ve been having a problem with some things (camera on a poly, snapshots) not updating on the device (iphone 4 with ios6) for a little while now, but haven’t pinned it down enough to do a bug report. I basically get a blank screen on app start up on device, though I noticed if I turned the device on and off, there would be *one* update to the display. (So if it was “camera”, it would be displaying one image from the camera frozen).
So I suspected it was related to something I read a month ago from Walter (can’t find it now), regarding screens that don’t do anything (no moving elements on it). So I put a little moving dot in a runtime loop on the screen, and it “fixes” the problem.
[lua]
–temp fix for Corona bug (display won’t update unless something is moving)
local bug = display.newCircle(0,1,1,1)
bug.alpha = .05
local function moveBug()
bug.x = bug.x + .001
end
Runtime:addEventListener(“enterFrame”, moveBug)
[/lua]
Glad you were able to duplicate it. Considering how little changed – if your build notes are correct – seems like not much happened between 2099 when it was working and 2100 when it wasn’t.
What changed was a shader fix for the Galaxy Tab2 (black screen issue too). We are now sending the shader commands in the proper sequence but it’s failing on the Tega 2 drivers. This seems to be a know bug based on a stackoverflow.com search.
Hi people,
I’m having just the same problem, black screen on my 10 inches tablet with Android 3.2.1.
My simple game works fine in every device but in my Packard-Bell G100W.
I’m using 2100 and my last test was just adding a Hello World Sample… but still black screen.
My app was working fine on 2013.1137 but i updated to fix problems with admob… now i have admob banner showing but black screen in the rest of screen, althougth i can listen game sounds and even touch screen and make movements.
Just wanted you (specially Corona Stuff) to know that.
Thanks and i hope it can be solved soon.
@roboward, this sounds like you are having a different issues. Can you look in the Console log on your iOS device (Using XCode’s Organizer) and see if you’re getting any errors?
Rob
Hi Rob,
Sorry i didn’t mention that only compiled to Android Devices, i’m developing on Windows platform.
Anyway, I went back to release 1202 and it works in all devices included my 10’’ Tablet. Some issue with Graphics 2.0, if you need some log of Android devices just let me know.
We know about a problem on Android devices running a Tegra 2 chipset and we are looking into a solution. If you download 2123, the console should print out a message that shows the device information we can use. You can use adb logcat to view the console log. If you do not know how to do this or need adb setup, please read this tutorial:
https://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Rob
Yes i know how to download the console log log but i can’t download 2123 because, for the moment, i own just a starter license.
The Packard-Bell G100W is also using a Tegra 2 chipset. This will be fixed in an upcoming daily build once the engineers work out what the issue is. Then the next public build will also pick up the change. We don’t have an ETA on when that will be yet.
Rob
I can confirm that my app now loads on device after updating to 2014.2130 but:
http://forums.coronalabs.com/topic/43261-horrible-text-bug-in-20142130-no-text-just-rectangles/
Happens in both simulator and Android device.
There will be a new daily build soon that addresses this…
Rob
Build 2130 fixes the Android black screen issue. Build 2131 will fix the black rectangle “Text” bug that was introduced in build 2130.
Just wanted to confirm that we are back in business with the 2014.2135 update. Black screen on my android tablet is fixed, as well as the newText rectangles.
Thank you to the Corona team for getting these fixes out to the community. I for one are very appreciative. 
Great news! Hope we are close to a public release, and that public release goes through a complete testing suite. I know a lot of people would like to move to this.
The black screen problem is still happening periodically on Android device. When will a final fix be available for this issue?