Black screen during 2 secondes at launch application

[Julian]

Hi,

I have finish an application that i create since 1 month, i have install the apk on my phone and when i launch the application i have a black screen during 2 seconde whit the title on the top.
I don't know why i have this, so i have found this topic who talk this problem : https://groups.google.com/forum/#!msg/mitappinventortest/M98RajcM6EY/kAKISprtAwAJ;context-place=searchin/mitappinventortest/black$20screen$20appinventor$202%7Csort:date

I have try to optimize all my image but the problem is still here.

On the topic it's say :

Another trick is to load assets only after Screen initialize is finished, for example by using a clock that waits half a second or so before it fires and then you can do what needs to be done. Disable it also ofter it fires once!

But i don't know how i can make this.
Can you help me.

Thanks
Best regard

[Boban Stojmenovic]

Unfortunately, It's common behavior with apps made with App Inventor.

I do not know if this even works as it will probably also produce a black screen..

On the topic it's say :

Another trick is to load assets only after Screen initialize is finished, for example by using a clock that waits half a second or so before it fires and then you can do what needs to be done. Disable it also ofter it fires once!

There is a possibility to add a image as backrund or so to remove the black screen but it requires the use of third parties software to achieve this.

Here you can see the MIT companion app with and without manipulation https://photos.app.goo.gl/LXDHA3lA4Wh8J05B3

Boban

[Julian]

Hi,

Thanks for help.

When you say :

it requires the use of third parties software to achieve this

Have you any name of third parties software that i can test to remove the black screen ?

Best regard

[Boban Stojmenovic]

There are a couple that I've used and there are many more available online.

AppToMarket outdated, but it can still be used with some exceptions.

ApkModder requires membership in the forum as well as donation to be used.

Apktool is the one I usually use because it is constantly updated.

Note: Both AppToMarket and ApkModder use Apktool to achieve the final result but they have a user-friendly GUI Apktool has not.

Boban

[Boban Stojmenovic]

For training purposes only if you make this work with AppToMarket, then I can upload the necessary files and description for black screen removal.

New version AppToMarket 4.1

Other tutorials that you can take a look at on my page http://baasapps.com/ for training purposes.

Questions related to AppToMarket or Apkmodder are answered only in the respective forums..

Boban

[Julian]

Hi,

Thanks for you help and your link.
I will test this and i hope if it's work

Best regard

[Chris Ward]

Hello Boban

I have used AppToMarket 4.1 to produce a new APK, setting the debug value to True in the manifest (works fine producing a final, signed APK too but I'm still refining the app).

I'm very keen to learn how to remove the black screen!

[Boban Stojmenovic]

Hi Julian & Chris,

I will try to do a tutorial later in the evening or as late this weekend, as there has been a lot of requests about this lately..

Will post a link to it when it is ready.

Boban

[Chris Ward]

That's very kind of you Boban, thanks!

[Julian]

Thanks Boban ;)

[Boban Stojmenovic]

Hope this can be of any help http://baasapps.com/app-inventor/splash-screen-mit-ai2/

Boban

[Chris Ward]

Well, that works "straight out of the box" Boban, very good step-by-step instructions!

Thank you very much indeed - I'm sure a lot of AI2 Users will need this.

Chris

[Chris Ward]

One thing to be aware of is that AppToMarket v4.1 does not retain the edited manifest. It also deletes the additional files baastheme.xml and colors.xml, so it is necessary to keep a copy of these files out of ATM's path.

Also, changing Min SDK Ver/Target SDK Ver does not seem to result in a change of the manifest?

However the manifest includes:

platformBuildVersionCode="22" platformBuildVersionName="5.1.1-1819727"

.... doesn't that relate to Android Lollipop? If so, not great because I understand that a large number of phones in use are on KitKat or lower.

[Boban Stojmenovic]

One thing to be aware of is that AppToMarket v4.1 does not retain the edited manifest. It also deletes the additional files baastheme.xml and colors.xml, so it is necessary to keep a copy of these files out of ATM's path.

Yes, each time you decompile the same or new app, the files gets overwritten.

Also, changing Min SDK Ver/Target SDK Ver does not seem to result in a change of the manifest?

https://groups.google.com/d/msg/apptomarket/Zat8613UslA/Jogh-GOyFAAJ 

usually I use the highest Min SDK 14 and nothing for Target SDK as it's not recommend, otherwise you will lose some features with apps made with MIT..

However the manifest includes:
platformBuildVersionCode="22" platformBuildVersionName="5.1.1-1819727"
.... doesn't that relate to Android Lollipop? If so, not great because I understand that a large number of phones in use are on KitKat or lower.

It's MIT's build platform, so just ignore it..

Boban

[Chris Ward]

I see, thanks for that advice Boban - it really is an Android jungle :)

Concerning the Splash Screen, how can a short text be added above the icon image?

Edit: Sorry, another question - how to set the background color? I have tried to change it from white to orange:

..\temp_myDecompiles\res\drawable\baas_splash.xml

<?xml version="1.0" encoding="utf-8"?>

<layer-list xmlns:android="http://schemas.android.com/apk/res/android">

    <item

        android:drawable="@color/orange"/>

    <item>

        <bitmap

            android:gravity="center"

            android:src="@drawable/ya"/>

    </item>

</layer-list>

 

..\temp_myDecompiles\res\values\colors.xml

 

<?xml version="1.0" encoding="utf-8"?>

<resources>

<color name="orange">#FFFFC800</color>

</resources>

 

 

[Boban Stojmenovic]

Try with lowercase letters..

<?xml version="1.0" encoding="utf-8"?>
<resources>

<color name="white">#ffffff</color>
<color name="orange">#ffffc800</color>
</resources>

#ffffc800 or #ffc800 

[Chris Ward]

...you beat me to it :)

[Chris Ward]

Well, tried to be clever by adding text as an image:

<?xml version="1.0" encoding="utf-8"?>

<layer-list xmlns:android="http://schemas.android.com/apk/res/android">

    <item

        android:drawable="@color/orange"/>

    <item>

        <bitmap

            android:gravity="center"

            android:src="@drawable/in"/>

    </item>

</layer-list>

....where "@drawable/in" is a 144x144 image text in.png, leaving ya.png as the App Icon. Unfortunately App2Market has eyes in the back of it's head and throws an error :)

So, next attempt, replace the image with text:

<?xml version="1.0" encoding="utf-8"?>

<layer-list xmlns:android="http://schemas.android.com/apk/res/android">


    <item
        android:drawable="@color/orange"/>

    <item>

            android:gravity="center"
            android:text="Initialising..."
    </item>


</layer-list>

...gets compiled by App2Market, but fails to install on the device.

[Chris Ward]

Actually my remark is incorrect, the app is recompiled and it does install on the device, but it does not run - a pop-up message says it has unfortunately closed :)

[Chris Ward]

I returned to the idea of using a text image on the Splash Screen ("Loading" Screen is the proper name apparently). Failed before, works really well now! So, after editing the Manifest:

..\temp_myDecompiles\AndroidManifest.xml

<application android:debuggable="true" android:icon="@drawable/ya"  android:theme="@style/Theme.BaasTheme"  android:label="My App" android:name="com.google.appinventor.components.runtime.multidex.MultiDexApplication">

..\temp_myDecompiles\res\drawable\baas_splash.xml:

<?xml version="1.0" encoding="utf-8"?>

<layer-list xmlns:android="http://schemas.android.com/apk/res/android">

    <item

        android:drawable="@color/orange"/>

    <item>

        <bitmap

            android:gravity="center"

            android:src="@drawable/in"/>

    </item>

</layer-list>

..\temp_myDecompiles\res\drawable\:

..\temp_myDecompiles\res\values\colors.xml:

<?xml version="1.0" encoding="utf-8"?>

<resources>

<color name="orange">#ffc800</color>

</resources>

I think it's important to note that no other files should be in the folders, as shown here. Also note that AppToMarket v4.1 was used.

Thanks again for your most excellent help Boban. I hope it works for Julian's app too. 

[Boban Stojmenovic]

Great that you solved this for yourself.

Boban

[Harry Mangurian]

I am unclear on what causes the problem in the first case.
Is it a bug in AI2 ?

[Chris Ward]

I can't take any credit there Boban, you did all the tricky stuff and presented it in an easy to follow way.

[Chris Ward]

Hi Harry

As I understand it, Android is the main culprit as most Apps greater than tiny take a few seconds to load. Keep in mind that most Android smart phones in use are not the super-fast flagship models, which probably can load apps faster via the brute force of the CPU.

There should be ways to reduce the load time of apps, starting with multithreading, making use of all CPU cores available. That is something the MIT guys can work on (perhaps they are?). 

In addition, having a loading screen instead of just a blank, black screen let's the User know that the App is doing something and has not crashed. This where Boban's Android XML files make a huge difference. AI2 certainly should have a proper, customisable loading screen (perhaps the MIT guys are working on that too).