black screen at startup

1,045 views
Skip to first unread message

stas z

unread,
Mar 10, 2012, 1:04:21 PM3/10/12
to Kivy users support
Hi, I was wondering if it was possible to create some sort of splash
screen at kivy startup.
On a desktop machine the startup time of a kivy app is pretty short
but on a android phone one has to watch a black screen for some time.
I have watch users hit the 'return' button on the phone as they
thought the app didn't start.
This was on a samsung galaxy s1 so it's not the slowest phone
available.

Thanks,
Stas

Mathieu Virbel

unread,
Mar 10, 2012, 2:57:31 PM3/10/12
to kivy-...@googlegroups.com
Hi,

Normally ,you have a splash screen already during the decompression part. But it look like it doesn't work for you. I already heard that some people don't see the screen, but i never owned a phone with that black screen bug. Dunno what's going on, you can check the java part (src/src/org/renpy/android/SDLSurfaceView.java), and see how the splash screen is done. Mabye you could help to resolve that issue :)

Mathieu

stas z

unread,
Mar 12, 2012, 6:17:54 AM3/12/12
to Kivy users support
I have tested with my own app as well as the "showcase" example from
kivy examples.

Hmmm, logcat tells me everything is fine, but no splash image.
And python dies on the emulator :-( (also without showing a splash)
The apps run fine on 3 different Andoid devices, Galaxy s1, Nexus and
a Archos 10.1 tablet.
None of these devices show a splash nor can I find any errors in the
logs.

BTW, stuff I made with the ren'py port does show the ren'py splash on
the above devices.

stas z

unread,
Mar 16, 2012, 6:45:47 AM3/16/12
to Kivy users support
Any news on this ?
It also doesn't show a splash on the Android emulator.

Mathieu Virbel

unread,
Mar 16, 2012, 9:08:49 AM3/16/12
to kivy-...@googlegroups.com

Well, report it to the python for android, but you could try to fix it too :)

Gabriel Pettier

unread,
Mar 29, 2012, 5:22:15 AM3/29/12
to kivy-...@googlegroups.com
I have the same problem, and some others (shaders examples not working correctly) with my GS too, i'm pretty sure this is a bad implementation of openGL on this model. In fact, if you look carefully with a lot of light, the splash is there, but very very dark.

stas z

unread,
Mar 30, 2012, 1:39:24 AM3/30/12
to Kivy users support
It's not only a problem on the Galaxy S1.
I don't have a splash on a Nexus phone android 2.3, Toshiba folio with
android 3.0,
acrchos tablet 2.4 and HTC 2.3.
So no I don't think it's a GS1 related problem.
Also it's only a problem with the splash screen, everything else
opengl
related work perfectly on all mentioned systems.

On Mar 29, 11:22 am, Gabriel Pettier <gabriel.pett...@gmail.com>
wrote:

Gabriel Pettier

unread,
Mar 30, 2012, 4:33:39 AM3/30/12
to kivy-...@googlegroups.com
Do the shaders exemples works ok on these models?

Mathieu Virbel

unread,
Mar 30, 2012, 5:08:51 AM3/30/12
to kivy-...@googlegroups.com
I rechecked the spash screen again, and i really don't see where the
issue is coming from.

Could you go deeper for us, and try to resolve it ? The involved method
is waitForStart():

https://github.com/kivy/python-for-android/blob/master/src/src/org/renpy\/android/SDLSurfaceView.java#L626

In order to test it, you can just create an apk with a main.py file, and
a "from time import time; time.sleep(10)"

You'll have 10 seconds to see it before the all leave.

On 30/03/2012 07:39, stas z wrote:
> It's not only a problem on the Galaxy S1.
> I don't have a splash on a Nexus phone android 2.3, Toshiba folio with
> android 3.0,
> acrchos tablet 2.4 and HTC 2.3.
> So no I don't think it's a GS1 related problem.
> Also it's only a problem with the splash screen, everything else
> opengl
> related work perfectly on all mentioned systems.
>
> On Mar 29, 11:22 am, Gabriel Pettier<gabriel.pett...@gmail.com>
> wrote:
>> I have the same problem, and some others (shaders examples not working
>> correctly) with my GS too, i'm pretty sure this is a bad implementation of
>> openGL on this model. In fact, if you look carefully with a lot of light,
>> the splash is there, but very very dark.
>>

>> Le samedi 10 mars 2012 19:04:21 UTC+1, stas z a �crit :

Mathieu Virbel

unread,
Mar 30, 2012, 5:22:13 AM3/30/12
to kivy-...@googlegroups.com
On psg4a, they changed something about that (i think):
"Forcibly convert the presplash bitmap to ARGB8888, and use an RGBA
texture, so it works on all Android devices."

Trying to merge the conversion part right now.

Mathieu Virbel

unread,
Mar 30, 2012, 5:35:41 AM3/30/12
to kivy-...@googlegroups.com
Still working after merge on both devices i got.

Try to update, tell me if it's still not working or not.
Then back to the issue :)

Mathieu

Gabriel Pettier

unread,
Mar 30, 2012, 8:47:08 PM3/30/12
to kivy-...@googlegroups.com
I just pulled changes on python-for-android project, built a new default dist (-m "kivy"), and built an apk for touchtracer with  ./build.py --package org.kivy.test --name kivytest --version 0.4 --dir ~/kivy/examples/demo/touchtracer debug

ran it and still no splash on my GS1, did i miss a step, or does it mean it's not fixed?

Mathieu Virbel

unread,
Mar 31, 2012, 6:51:56 AM3/31/12
to kivy-...@googlegroups.com
it mean it's not still fixed. So... could you try to debug it ?

2012/3/31 Gabriel Pettier <gabriel...@gmail.com>:

fvl

unread,
Jun 20, 2012, 6:08:29 PM6/20/12
to kivy-...@googlegroups.com
Hi Mathieu,

I think I have a simple fix for the "black screen at startup" problem in which presplash.jpg refuses to be displayed.  Some OpenGL implementations get confused when textures have a resolution that is not a power of 2.  The default image (found in python-for-android/dist/default/templates/kivy-presplash.jpg) has a resolution of 360x200 which would not display on my tablet.  I replaced it with the attached image (256x256 in resolution) and it works beautifully.

For your reference, the problem might also be related to this issue:

-Fred
presplash-fixed.jpg

krister viirsaar

unread,
Jul 23, 2013, 3:33:57 AM7/23/13
to kivy-...@googlegroups.com
I'm on 1.8 and changing from 512x3?? to 512x512 fixed the same issue on my galaxy tab.
Reply all
Reply to author
Forward
0 new messages