Try to put a tiny delay on startup:init(), that should do the trick.
Thanks Jon,
I have changed my code and I still am getting a 4 to 5 second delay on startup without ever seeing my initial banner.
My last two lines of code now look like this:
local startup =require( “startup” )
timer.performWithDelay( 1000 , startup_init(), 1 )
Prior to the buggy cornona code this never happened.
I would really appreciate someone from Corona support helping me out on this.
Regards,
Arthur
You have to get rid of the trailing brackets in startup_init() or there will be no delay. So
timer.performWithDelay(1000 , startup\_init)
Jon,
You are my new hero!!! Thanks! After all of these months that bloody black screen is gone!
Have a great day. You made mine!
Thanks!
Arthur
Glad that helped
By the way in case you didn’t try shorter delays, you can probably go down to 100 or less.
Is anyone seeing this bug back again?
I am seeing it again on my iOS apps… (Corona build 2449)
Hi Renato,
I’ve not seen it. Did you try the stuff posted in here? I’ve found you need at least a half second delay.
Arthur
I can’t believe this HUGE issue still exists!
I’m facing it in Android builds for the last months’ corona versions:
tap > black screen > default.png > home screen > app first screen
instead of :
tap > default.png > app first screen
It shows up even in Corona samples (eg Hello World and Composer).
It affects only apps with portrait orientation. Not visible when changing build.setting to landscape with exactly the same app code.
I really can’t believe this!!
Reminds me of the “alpha” days back to 2010…
The flickering lasts about 300 ms on a LG G2 with no other apps running. The duration is not significant but the effect breaks the user experience from the very beginning. All other apps made with other platforms are starting 100% smooth on my devices.
The flickering happens only on fresh app starts (not loading from memory) and only after the initial install of the apk (close the app with task manager and repeat the “exit and fresh load again” until you see the flickering).
The corona version I use is the latest public. The same happened with a version from the summer public builds.
This happens only with portrait orientation. Apps in landscape start smoothly for a reason. This makes me believe that the effect has nothing to do with memory and performance etc, and instead is just an awful bug…
There are a lot of published apps that are affected. Take for example a corona showcase: http://coronalabs.com/case-study/crossing-the-finish-line-with-bibs/
However, there are some portrait apps that are not affected, eg: http://coronalabs.com/case-study/my-days-tracking-fertility-and-ovulation/
PLEASE, do something for this. It should be the priority No.1 for the team. It affects every single app that is published.
@Magenda What you are describing is different than the issue that was happening on iOS builds. The problem described in this thread was:
tap > default.png > black flicker > app first screen (or manually continued default.png, then “app first screen”)
You may want to start a different thread about the issue you are experiencing. Regarding your issue though: Admittedly, I’m not a regular Android user, but in all of the dev testing I’ve ever done on (a limited number of) Android devices, I’ve only ever seen “tap > black > app first screen”. It was my understanding that Android devices don’t display the Default.png image like iOS devices do. All of my testing has been in portrait mode only (I’ve never tested an app that uses landscape mode or both).
Can you clarify what you mean by “Home screen” showing up between default.png and app first screen?
Thanks
Rob
Rob,
It is like the whole app starts with the black screen / default.png for 200ms, then it leaves the screen for another 200ms and you can see the device’s home screen (the wallpaper with the app icons etc) and finally it shows the first screen of the app.
It is like a flickering to the user eyes that breaks the feeling of a quick and smooth app start.
Hi @Magenda. As @drewns pointed out, Android never shows a launch image. Because many people asked for it, Corona SDK will show a “Default.png” file if it exists and after a small delay, it transitions to the opening page you have setup.
I just ran several Corona SDK built apps (Portrait only too), some older some built with the latest 2511. I didn’t see any “Home screens” between the showing of Default.png and the showing of my Main screen. Now there appears to be a cross fade, perhaps around 300ms long, but it was pretty much just black. This was a Google Nexus 7 1st Gen with Android 4.4 installed.
Rob
Thanks for your reply!
Lets take this to the barebones: I’ve taken the “HelloWorld” sample project from Corona 2511 and I removed the Default-568h@2x.png file. No other changes at all! The compiled file is this apk:
https://www.dropbox.com/s/gf25zi9t70d30m0/HelloWorld1.apk?dl=0
Doesn’t get any simpler than that. No special code, no Default.png, no complexities… just a simple portrait app compiled with the newer Corona build and run on a modern android device (Snapdragon 800).
I still see the flickering after closing the newly installed app with the task manager and running it again. The flickering is shortt (it lasts about 100ms) but it is there. During this time I can see the icons of my device homescreen.
(The same applies if I choose to leave a Default png in the project files. )
@community
Can you also see this (rapid) flickering when freshly re-running the apk above on your devices?
Compare HelloWorld.apk start with an other app’s start (not built with Corona), after you close all the apps with task manager and run them from zero.
@Magenda, just tested your apk here and I didn’t see your problem.
Tested on:
Samsung Galaxy S1 (2.3.6)
Samsung Galaxy S3 (4.3)
I’ve installed your .apk file on my Nexus 7 (4.4) and I don’t see any flicker.
Now I believe you are seeing something, but, it’s not something everyone is seeing and may be isolated to something going on with your device.
Rob
Is anyone seeing this bug back again?
I am seeing it again on my iOS apps… (Corona build 2449)
Hi Renato,
I’ve not seen it. Did you try the stuff posted in here? I’ve found you need at least a half second delay.
Arthur
I can’t believe this HUGE issue still exists!
I’m facing it in Android builds for the last months’ corona versions:
tap > black screen > default.png > home screen > app first screen
instead of :
tap > default.png > app first screen
It shows up even in Corona samples (eg Hello World and Composer).
It affects only apps with portrait orientation. Not visible when changing build.setting to landscape with exactly the same app code.
I really can’t believe this!!
Reminds me of the “alpha” days back to 2010…
The flickering lasts about 300 ms on a LG G2 with no other apps running. The duration is not significant but the effect breaks the user experience from the very beginning. All other apps made with other platforms are starting 100% smooth on my devices.
The flickering happens only on fresh app starts (not loading from memory) and only after the initial install of the apk (close the app with task manager and repeat the “exit and fresh load again” until you see the flickering).
The corona version I use is the latest public. The same happened with a version from the summer public builds.
This happens only with portrait orientation. Apps in landscape start smoothly for a reason. This makes me believe that the effect has nothing to do with memory and performance etc, and instead is just an awful bug…
There are a lot of published apps that are affected. Take for example a corona showcase: http://coronalabs.com/case-study/crossing-the-finish-line-with-bibs/
However, there are some portrait apps that are not affected, eg: http://coronalabs.com/case-study/my-days-tracking-fertility-and-ovulation/
PLEASE, do something for this. It should be the priority No.1 for the team. It affects every single app that is published.