Unity3D build .apk file run on Android 4.1.2 screen is blue

Archived Forums Questions & Answers
1

Hi,
I am build Unity3D .apk file run on Android 4.1.2 screen is blue, I put file in folder Download install, I run game but screen is blue and nothing else !
How solve is problem ?
Thanks!

3 Answers

3
2

It’s just a guess, because of lack of information, but try to check in File → Build Settings

You should have scene aded to the list.
I assume that you have something in your scene and camera is in the correct position

19333-buildsetings.png

Then I have to ask you to provide more information. There might be alot of problems. Is your screen "blue" default camera background color? or is it another "blue"? On what phone you are trying to install this build? Check that it supports current compression, with which your textures are imported. Maybe your gameObjects are out of camera field of view. All of this needs to be debugged.

 –

could you provide screenshot from your mobile phone? Also make sure that the scene is loaded

 –

Did you make sure that the scene has been loaded? You may use logcat to see Debug.Log() Do you have your camera created with script or it is in the scene by default? If it's added to the scene with script, then you may have a problem with script execution order.

 –

Thanks for help but camera is standard, camera have not script , I build .exe file all right. I think to build simple example after that look what will happen

 –

Thanks for help but camera is standard, camera have not script , I build .exe file all right. I think to build simple example after that look what will happen

 –
3

Check that the maincamera is tagged as camera

Enable development build setting on android build. This worked for me ![alt text][1] [1]: http://i.imgur.com/8wWaM7z.png

 –

Make sure your camera is enabled in the game and rebuild

 –

write your email I will send file and play you and look )

 –

You can send me your apk here nedelkosm@gmail.com

 –

Thank you !

 –
4

I posted this answer here already: it may be related to a problem where the Start() method of a script is not called correctly on Android. Try to either add a new startup scene which does nothing but load your actual startup scene, or use some backup to the Start() method you may suspect to fail. In my case using OnEnable() as well worked.

Have a look at this blog post for more details.