Issue:
On Android devices, Dim-light from the bottom of the screen is shown on launch.

Details:
-This issue lasts longer with a stack containing sub-stacks (It’s 10.9Mb as a standalone stack.)
-It lasts less than 0.1~0.2 sec with Samsung Galaxy Edge 6. but it varies greatly from 0.1~10 sec depends on the size of stack and specs of devices.
-Low spec devices will have longer dim light in the black background on launch.

Comment:
-Including or Size of copy file doesn’t affect this issue.
-This issue lasts a very short time at the beginning of the launch, it’s hard to catch.
-To make this more visible, set the background of the test stack to black and use low spec device OR add sub-stacks with enough data.

Steps to reproduce:
1. Make a plain stack. (no code, no copy files)
2. Set the background color to black so that the dim light on launch more visible. (It’s hard to see with gray or white background.)
3. Add sub-stacks containing enough data to be 10Mb as a final standalone stack size. (I added two sub-stacks with all kind of objects in them.)
4. Save it as a standalone stack.
5. Test it.

Result:
Regardless of the existence of sub-stacks, both stacks show dim-light on the launch. but the stack with sub-stack shows longer dim-light.
(From shorter to longer last of dim-light from the bottom of the screen)
stack = stack with files < stack with sub-stacks

Please see the tested Video: https://youtu.be/SziawUu8Nsc
The first stack on the video is a simple raw stack just with text, and the second stack on the video has two sub-stacks.

With this bug, LiveCode won’t be a recommended tool for Android app development. Hope this issue fix ASAP.

I filed this bug several times through years, but they never reproduce and confirm this bug. So I filed it again with a video evidence this time.
Please Fix this Bug. It's been years since LC 8 introduced.

@Jellobus: The issue here isn't a bug per-se - its that your main stack is very big (50-60Mb)... In order for the engine to display anything it needs to first load the stack which has been embedded in the executable - decoding and loading 50-60Mb of stackfile into memory is quite a lot, especially on lower powered android hardware.

The solution is to use the standard 'splash stack' approach.

This is where you have a tiny 'splash screen' stack (with maybe an image) which is the stack you choose to embed in the standalone. Then in the 'openStack' handler of the splash stack you *then* load the other stacks and 'go to' them. This means you at least get something displayed on screen whilst the main part of your application is loaded.

@ LCMark: I correct Info. The tested stack was 10.9Mb as .apk file. I was confused with the other stack tested with copy files. ( a lot of copy file doesn't affect the time length of dim-light)

"Splash stack" approach doesn't help because a simple raw stack (no code, no files) shows Dim-light on launch as well. The first stack in the video is a plain raw stack with text. You can see a dim light at the beginning as well. watch 0-20 sec in the video. I launched it 3 times.

Simple plain stack 0-20 sec
Stack + sub stack 21~36sec

In the video, both simple and complex stack show dim light issue on the launch. Just substacks make dim light stay longer.

I have some apps on android, and with an octa-core it is with every app less than a second. And the APK is approx 15MB.
On my older Wiko Android 6, el cheapo phone quad-core, it maybe was a second.

So i can't say that i find it long or annoying. Nor do i see the longer issue you have.
I also don't see it as a DIM-light,i see just a black screen. But maybe you have set the screen brighter, i don't know.

But if the devs can make it start quicker it could help. But i guess you'll have it with either stack at least fora short period because of the engine i guess.

I wouldn't care if it last just a second or less. Unfortunately, this issue stays a lot longer than a second in my case. I lost about 60% of my clients since this issue introduced. Most of them were low spec device users. (*This issue was introduced with LC 8+, LC7 was pretty great)

I like to find a walkaround of this issue. I tried a splash stack approach but I had no luck.

I have a few questions for you. Please let me know if you have time.

1. Does your APK have a substack?
2. What is your build environment? (PC or Mac or Linux?)
3. What is your Java SDK version and LC version?

no sorry i have no substack for mobile. But since my stacks are not that big i use the first card as splash and then move to the second card.
Mostly i do the development on win10-64bits. But since i have a triple boot, i can do Linux(Ubuntu Mate) and MacOs Mojave too.
I use Java JDK_1.8.0_212_x64
LC905rc1 and lc904 and LC950DP1 Indy

@jellobus: Those times sound waaay too long for 'just' a plain stack. I've got a old samsung galaxy tab here which has slightly lower hardware specs than your Samsung J2 and with such a stack, startup is a fraction of a second. I think you need to attach the stacks you are using to the bug report so we can see what its doing - there potentially could be some settings you are using in the standalone settings pane, or some inclusions, or a script which is running on startup causing the long pause.