Black Screen loading Hello World sample app on Android > 2013.2099

Solar2D Daily Builds and Public Releases
#1

So I built the update for my app today on Windows and loaded it on device running Android 3.2 as normal.  Got a black screen.  Checked my catlog and all was fine.

Strange thing is that the app still takes inputs once you touch the screen as shown via catlog, but no matter what, always a black screen.

Tried HelloWorld sample app as I couldn’t see any errors in Catlog and got a Black Screen also.

Tried a few other sample apps, all black screen, yet they still take inputs.

Can someone please do a build using Windows for Android device using 2013.2109 please to check.

Thank you.

Edit: Just checked on 2013.2096 and my app and sample apps work fine.

Edit 2:  Sample Apps and my apps fail on 2013,2100,2013.2106,2013.2108 also

Edit 3:  Sample apps and my apps work on 2013.2099 also, so something added in 2013.2100 has caused the issue.

#2

What device are you testing them on?

When you look at adb logcat, are you also filtering on Corona messages?  It’s possible that a message that isn’t tied to the Corona activity could be generating an error and if you filter on Corona messages you might miss it.

Rob

#3

Hi Rob,

thanks for the reply.

My device is an Advent Vega.  http://en.wikipedia.org/wiki/Advent_Vega

i looked at all logs, but no errors.  Also if i load the widget demo sample app for instance I still get print statements showing, ie when scroll limits are reached or if i press a row.

The problem is there is no screen display, it’s just always black, no matter what sample app I try.  All is fine on 2013.2099 and prior.

#4

I’ll check with Engineering and see if they know what happened between 2099 and 2100.

Rob

#5

Hi Rob, thanks.

I am running Windows XP, using 2013.2109 for the test.

I created a single line app which is black screen:

[lua]

local testtext = display.newText(“Hello”,160,240,nil,30)

[/lua]

and here is the output from catlog when the app was ran:

12-23 12:09:01.560 I/ActivityManager(135): Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.gmail.icysparkapps.test320480/com.ansca.corona.CoronaActivity } from pid 220
12-23 12:09:01.600 I/am_pause_activity(135): [1082430912,com.android.launcher/com.android.launcher2.Launcher]
12-23 12:09:01.620 I/ActivityManager(135): Start proc com.gmail.icysparkapps.test320480 for activity com.gmail.icysparkapps.test320480/com.ansca.corona.CoronaActivity: pid=2988 uid=10063 gids={}
12-23 12:09:01.600 I/am_task_to_front(135): 11
12-23 12:09:01.600 I/am_new_intent(135): [1081809248,11,com.gmail.icysparkapps.test320480/com.ansca.corona.CoronaActivity,android.intent.action.MAIN,NULL,NULL,274726912]
12-23 12:09:01.610 I/am_on_paused_called(220): com.android.launcher2.Launcher
12-23 12:09:01.620 I/am_proc_start(135): [2988,10063,com.gmail.icysparkapps.test320480,activity,com.gmail.icysparkapps.test320480/com.ansca.corona.CoronaActivity]
12-23 12:09:01.700 I/am_proc_bound(135): [2988,com.gmail.icysparkapps.test320480]
12-23 12:09:01.730 I/am_restart_activity(135): [1085726632,11,com.gmail.icysparkapps.test320480/com.ansca.corona.CoronaActivity]
12-23 12:09:01.850 I/ActivityThread(2988): Pub com.gmail.icysparkapps.test320480.files: com.ansca.corona.storage.FileContentProvider
12-23 12:09:02.070 D/dalvikvm(2988): Trying to load lib /data/data/com.gmail.icysparkapps.test320480/lib/liblua.so 0x406ea4c0
12-23 12:09:02.090 D/dalvikvm(2988): Added shared lib /data/data/com.gmail.icysparkapps.test320480/lib/liblua.so 0x406ea4c0
12-23 12:09:02.090 D/dalvikvm(2988): No JNI_OnLoad found in /data/data/com.gmail.icysparkapps.test320480/lib/liblua.so 0x406ea4c0, skipping init
12-23 12:09:02.090 D/dalvikvm(2988): Trying to load lib /data/data/com.gmail.icysparkapps.test320480/lib/libjnlua5.1.so 0x406ea4c0
12-23 12:09:02.100 D/dalvikvm(2988): Added shared lib /data/data/com.gmail.icysparkapps.test320480/lib/libjnlua5.1.so 0x406ea4c0
12-23 12:09:02.110 D/dalvikvm(2988): Trying to load lib /data/data/com.gmail.icysparkapps.test320480/lib/libjnlua5.1.so 0x406ea4c0
12-23 12:09:02.110 D/dalvikvm(2988): Shared lib ‘/data/data/com.gmail.icysparkapps.test320480/lib/libjnlua5.1.so’ already loaded in same CL 0x406ea4c0
12-23 12:09:02.110 I/dalvikvm(2988): threadid=1: recursive native library load attempt (/data/data/com.gmail.icysparkapps.test320480/lib/libjnlua5.1.so)
12-23 12:09:02.110 D/dalvikvm(2988): Trying to load lib /data/data/com.gmail.icysparkapps.test320480/lib/libopenal.so 0x406ea4c0
12-23 12:09:02.160 I/OpenAL_SLES(2988): alc_opensles_init
12-23 12:09:02.160 D/dalvikvm(2988): Added shared lib /data/data/com.gmail.icysparkapps.test320480/lib/libopenal.so 0x406ea4c0
12-23 12:09:02.160 D/dalvikvm(2988): Trying to load lib /data/data/com.gmail.icysparkapps.test320480/lib/libmpg123.so 0x406ea4c0
12-23 12:09:02.180 D/dalvikvm(2988): Added shared lib /data/data/com.gmail.icysparkapps.test320480/lib/libmpg123.so 0x406ea4c0
12-23 12:09:02.180 D/dalvikvm(2988): No JNI_OnLoad found in /data/data/com.gmail.icysparkapps.test320480/lib/libmpg123.so 0x406ea4c0, skipping init
12-23 12:09:02.180 D/dalvikvm(2988): Trying to load lib /data/data/com.gmail.icysparkapps.test320480/lib/libvorbisidec.so 0x406ea4c0
12-23 12:09:02.180 D/dalvikvm(2988): Added shared lib /data/data/com.gmail.icysparkapps.test320480/lib/libvorbisidec.so 0x406ea4c0
12-23 12:09:02.190 D/dalvikvm(2988): No JNI_OnLoad found in /data/data/com.gmail.icysparkapps.test320480/lib/libvorbisidec.so 0x406ea4c0, skipping init
12-23 12:09:02.200 D/dalvikvm(2988): Trying to load lib /data/data/com.gmail.icysparkapps.test320480/lib/libalmixer.so 0x406ea4c0
12-23 12:09:02.210 D/dalvikvm(2988): Added shared lib /data/data/com.gmail.icysparkapps.test320480/lib/libalmixer.so 0x406ea4c0
12-23 12:09:02.210 D/dalvikvm(2988): No JNI_OnLoad found in /data/data/com.gmail.icysparkapps.test320480/lib/libalmixer.so 0x406ea4c0, skipping init
12-23 12:09:02.210 D/dalvikvm(2988): Trying to load lib /data/data/com.gmail.icysparkapps.test320480/lib/libcorona.so 0x406ea4c0
12-23 12:09:02.460 D/dalvikvm(2988): Added shared lib /data/data/com.gmail.icysparkapps.test320480/lib/libcorona.so 0x406ea4c0
12-23 12:09:02.770 D/dalvikvm(2988): GC_CONCURRENT freed 172K, 7% free 5696K/6087K, paused 7ms+4ms
12-23 12:09:02.870 I/am_on_resume_called(2988): com.ansca.corona.CoronaActivity
12-23 12:09:02.930 D/libEGL  (2988): loaded /system/lib/egl/libGLES_android.so
12-23 12:09:02.950 D/dalvikvm(220): GC_CONCURRENT freed 1938K, 23% free 14240K/18439K, paused 5ms+5ms
12-23 12:09:02.950 D/libEGL  (2988): loaded /system/lib/egl/libEGL_tegra.so
12-23 12:09:03.150 D/libEGL  (2988): loaded /system/lib/egl/libGLESv1_CM_tegra.so
12-23 12:09:03.170 D/libEGL  (2988): loaded /system/lib/egl/libGLESv2_tegra.so
12-23 12:09:03.230 I/ActivityManager(135): Process com.google.android.apps.maps (pid 2009) has died.
12-23 12:09:03.230 I/am_proc_died(135): [2009,com.google.android.apps.maps]
12-23 12:09:03.240 D/OpenGLRenderer(2988): Creating OpenGL renderer caches
12-23 12:09:03.240 D/OpenGLRenderer(2988): Enabling debug mode 0
12-23 12:09:03.240 D/OpenGLRenderer(2988): Layers will be composited as regions
12-23 12:09:03.310 I/am_proc_died(135): [2019,com.noshufou.android.su]
12-23 12:09:03.310 I/ActivityManager(135): Process com.noshufou.android.su (pid 2019) has died.
12-23 12:09:03.330 D/dalvikvm(2988): Note: class Landroid/opengl/GLWrapperBase; has 250 unimplemented (abstract) methods
12-23 12:09:03.360 V/GLSurfaceView(2988): glGetString(7937) returns NVIDIA Tegra;
12-23 12:09:03.510 I/ActivityManager(135): Displayed com.gmail.icysparkapps.test320480/com.ansca.corona.CoronaActivity: +1s905ms
12-23 12:09:03.510 I/activity_launch_time(135): [1085726632,com.gmail.icysparkapps.test320480/com.ansca.corona.CoronaActivity,1905,1905]
12-23 12:09:03.620 V/Corona  (2988): > Class.forName: network.LuaLoader
12-23 12:09:03.620 V/Corona  (2988): < Class.forName: network.LuaLoader
12-23 12:09:03.620 V/Corona  (2988): Loading via reflection: network.LuaLoader
12-23 12:09:03.890 D/dalvikvm(2988): GC_CONCURRENT freed 388K, 10% free 5762K/6343K, paused 9ms+7ms
12-23 12:09:07.920 D/dalvikvm(220): GC_CONCURRENT freed 1925K, 23% free 14242K/18439K, paused 8ms+8ms
12-23 12:09:11.090 D/RIL     (101): open port errro!
12-23 12:09:12.430 I/TabletStatusBar(187): DISABLE_BACK: yes
12-23 12:09:12.770 D/dalvikvm(187): GC_FOR_ALLOC freed 797K, 13% free 8990K/10247K, paused 108ms
12-23 12:09:12.940 D/dalvikvm(220): GC_CONCURRENT freed 1922K, 23% free 14242K/18439K, paused 5ms+7ms
12-23 12:09:12.950 D/dalvikvm(187): GC_FOR_ALLOC freed 34K, 12% free 9216K/10375K, paused 85ms
12-23 12:09:13.060 D/dalvikvm(187): GC_FOR_ALLOC freed 235K, 14% free 9216K/10631K, paused 79ms
12-23 12:09:13.170 D/dalvikvm(187): GC_FOR_ALLOC freed 234K, 14% free 9216K/10631K, paused 85ms
12-23 12:09:13.310 D/dalvikvm(187): GC_FOR_ALLOC freed 227K, 14% free 9225K/10631K, paused 81ms
12-23 12:09:13.440 D/dalvikvm(187): GC_FOR_ALLOC freed 221K, 14% free 9247K/10631K, paused 81ms
12-23 12:09:13.520 D/dalvikvm(187): GC_FOR_ALLOC freed 157K, 15% free 9247K/10759K, paused 62ms
12-23 12:09:13.590 D/dalvikvm(187): GC_FOR_ALLOC freed 156K, 15% free 9247K/10759K, paused 60ms
12-23 12:09:13.660 D/dalvikvm(187): GC_FOR_ALLOC freed 156K, 15% free 9247K/10759K, paused 57ms
12-23 12:09:14.850 I/TabletStatusBar(187): DISABLE_BACK: no
12-23 12:09:14.820 I/am_pause_activity(135): [1085726632,com.gmail.icysparkapps.test320480/com.ansca.corona.CoronaActivity]
12-23 12:09:14.830 I/am_task_to_front(135): 2
12-23 12:09:14.830 I/am_task_to_front(135): 15
12-23 12:09:14.840 I/am_on_paused_called(2988): com.ansca.corona.CoronaActivity
12-23 12:09:14.860 I/am_resume_activity(135): [1087297488,15,com.nolanlawson.logcat/.LogcatActivity]
12-23 12:09:14.860 I/am_on_resume_called(2935): com.nolanlawson.logcat.LogcatActivity
 

#6

I can confirm that the new daily build of 2013.2111 does NOT fix this issue.

At the moment I can no longer test any apps on Android as my device shows black screen on loading any app including sample apps.

The Event Sound sample app for example will still play the audio ok on the device, but constant black screen.

What concerns me most is that it is highly unlikely that only 1 device from the thousands of Android devices are affected, meaning there will be users downloading apps made using 2013.2100 and above that will simply not work.

As I mentioned earlier,  there are no errors in catlog loading the app and the apps still take inputs and play sounds as per normal as can be seen via print statements in catlog.  Just a constant black screen.

I really need this fixed as soon as possible.  Not just for me but for any users that download apps for Android using SDK 2013.2100 and above.  There will be a greater chance of the app not showing visuals on various devices.

PS I have tested on a Samsung Galaxy SII and everything is fine.  Something from 2013.2099 and 2013.2100 has broke a certain number of android devices displaying graphics.

EDIT:  and it’s not good!  Just tried some sample apps on a CNM Touchpad 7.  Same problem.

So out of three devices I can test on, two don’t work! 

Also tried using a Mac to build just in case it was a windows thing, but still the same, black screens!

Corona guys this is a big thing, please fix!!!

#7

Well my suggestion for now is to use 2099 for your testing.  I’ll press engineering on this later in the week.  Most everyone is gone for the Holidays.

Rob

#8

This might be due to an unwanted plugin. The similar thing had happened to me and I got a plugin replaced and now it’s working fine for me.

#9

Thanks for the possible solution, but there is only one line of code in the main.lua, also using the standard config and build settings that come with the sample apps so I’m not using any plugins.

#10

So I’ve been working on migrating my Graphics 1.0 project to 2.0 and I seemed to have most of it working in the simulator, I built for Android, ran via adb and was simply faced with a blank (black) screen.

Attached is a log that indicates some sort of ParseException.

 

I also tried to build FrameAnimation1 (Corona Sample) for my device and also got a black blank screen but with no evident error indicated by adb.

My Android device is an Optimus 2x P990 running Cyanogenmod 7.2 based on Android 2.3.7 and using build 2013.2100 .

 

Tried a Huawei-U8665 (Aka Huawei Fusion 2 on Att) on Android 2.3.6 and my app runs just fine. I remember Corona apps used to run just fine on my O2X a much more powerful Tegra 2 device than the Huawei so I’m wondering what the issue is…

 

#11

Since I migrated to graphic 2.0, I keep getting complains from my users
like “your App doesn’t work, I see just black screen” or “graphics
disappearing”. I started to get low rating because of that. Is there any
chance for us to go back to graphics 1.0? I tried to compile with old
Corona, but Play Store generated an error messages, old Corona versions
don’t seem to conform to latest Play Store update.

#12

The trouble is that everything seems to work fine for most of us, developers - and then we get bad reviews from unhappy users with devices where App doesn’t work. How about giving us the last working version in the meantime?

#13

@petsvar, do you know what devices they are getting black screens on?  We really need to know this information.

Rob

#14

Hi,

I’m getting the black screen error on an Android 2.3 (Motorola Atrix). I was trying to compile something that had been developed by a friend on graphics 1.0, but I couldn’t download his version since I’m not Pro. I reconfigured the app a bit so that it works just fine on Corona’s simulators, but it is just coming up with the black screen when I put it on my phone. How soon do you expect this to be resolved? Although I enjoyed working with Corona’s SDK, I am not sure if I want to pay $49/month just to properly compile a single app.

#15

Just want to add that after checking the other devices added by users:

LG P990 Optimus 2X Chipset: Nvidia Tegra 2 250 AP20H

Motorola Atrix Chipset: Nvidia Tegra 2 250 AP20H

Advent Vega (mine): Nvidia Tegra 2 processor

Possible Link?

Seems more than a coincidence.

If anyone else has a Tegra 2 chipset, can you please build “Hello World” sample app using 2013.2100 or above and post your findings.

#16

@Rob:
Users report: Optimus L9, DROID RAZR, Samsung Ace 2

#17

Going back to OpenGL 1.1 (public build 1202) seems to fix my problem for now. Thanks!

#18

Noticed that 2014.2119 had load of bug fixes and maintenance.

However it still doesn’t fix the issue with Black Screens on devices with Nvidia Tegra 2 processors that was introduced in 2013.2100.

Urgently need this fixed.  I’m paying for PRO yet unable to gain the benefits of daily builds.

#19

Engineering is actively looking into it. 

Rob

#20

Hi Rob,

Thanks for the info.  Any update on this yet as it’s still the same as of 2014.2122?

It’s pretty urgent, as there are fixes for widgets that I’ve now programmed in but unable to test on device.  Also, wouldn’t want to release for Android knowing there is now a set group of devices that will now not work.