The question is answered, right answer was accepted
[SOLVED] Black screen after launch on Android Device
Hello Unity World !
After a bunch of unsuccesful tries via some others topics, I'm humbly asking for your help.
I'm using Unity 5.3.4f1 Personnal Edition.
I work in a Video Games school, and after the contract with Sony ( which included a Unity build on the PS Vita ) was over, we had to make a build on a chinese tablet with joystick, the GPD Q9, running on Android.
For more understanding of the product, here is some technical stuff :
GPD-Q9 System specs
CPU : 4 cores ARM Cortex A17 @ 1.8GHz
RAM : 2 GB DDR3
GPU : 4 cores Mali T764 @ 650 MHz → 88 GFlops (12x VITA) 2.6 Gvert/s, 2.6 Gpix/s
Shader model 5 (DX11/OpenGL ES 3.1)
ASTC texture compression Tiled deferred hardware rendering architecture
Res : 1024x600
Not bad must I say. But here come the problem in itself : for a week now, there's an annoying bug that none of my collegues of my teachers can fix. When I build it on my GPD, there the launching screen ( made with Unity etc etc ) and then, the first image is correctly rendered, but after this half-second of nothing, BAM, black screen. I thought first that my game just crashed, but no : the sound continue to play itself, the label "Development Build" correctly shows itself in the bottom-right corner of the screen, and the Autoconnect Profiler works like a charm by saying I turn at 50 FPS.
Here are some screens of my Player and Quality Settings, including the Profiler :
http://i.imgur.com/36p0vQM.png
So you can see that I turn at mostly 200 FPS, and sometimes I know that a too high FPS can be occasions for display problems, but I'm really not sure how to fix a FPS limit. Or if this is the problem.
So, I'm asking for your help again :)
Thank you very much for reading, ar for your future answers :)
TL;DR : My android device is rendering the first image of my project before turning totally black, while the game is still running in fact. I'm using Unity 5.3.4f1 Personnal Edition.
EDIT : Problem solved, it was just a scripting problem. Nevermind :)
Follow this Question
Related Questions
Getting crash on specific devices? 0 Answers
Android Size Different [S5] [TAB A] 1 Answer