Android 5.1.1 display failure

Question

Hi, we are having problems running application on our Android device (5.1.1). The problem is that after starting the app the display shows the sreen as on the image bellow:

alt text

Does any of you know what the problem can be?

Answer 1

Answer by dilippatil · Dec 31, 2015 at 01:38 PM

Mostly of this issues comes because of player setting regarding rendering. Please try with following settings under Other Settings tab in player settings 1. Automatic graphics API should Disable 2. In GraphicsAPI set OpenGLES2 3. Multithreaded Rendering should Disable 4. Static Batching should Enabled 5. Dynamic Batching should be enabled 6. GPU skinning and virtual reality both should be disabled 7. Device filter ARMv7

Add comment · Show 5 · Share

fermmmm · Dec 31, 2015 at 10:08 PM 1

Share

I disabled Automatic graphics API, then changed the order, first OpenGLES2 , second OpenGLES 3. It worked!. But this is still a problem because with this change, all the devices that support OpenGLES 3 will use OpeGLES 2, right? There is no documentation about this setting.

MCoburn · Jan 01, 2016 at 01:23 AM 0

Share

As far as I'm aware, you'll need to test on a non-OpenGL ES3 device. I'm not sure if ES3 will run in backwards compatibility mode for OpenGL ES2 GPUs like the older $$anonymous$$ali and Adreno chips.

If you specify "only OpenGL ES2" then regardless of what the GPU supports above ES2, it'll force the GPU to run the game in ES2 mode.

alvarog · Jan 02, 2016 at 12:18 AM 0

Share

Both @dilippatil and @fermmmm tips fix rendering in my case.

Please, @dilippatil, can you explain why those settings should be set to that values? For example, why $$anonymous$$ultithreaded Rendering should be disabled and how it affects rendering?

Matthew_83 · Jan 28, 2016 at 09:45 AM 0

Share

Can verify this works... thanks

Samsung J1 S$$anonymous$$-J100y Android Ver: 4.4.4 $$anonymous$$ernel Ver: 3.14.0-429194

XxxIgnasxxX · Mar 28, 2016 at 01:22 PM 0

Share

Where I can find these settings because I cant find them?

Answer 2

Answer by fermmmm · Nov 19, 2015 at 09:13 PM

I have the same issue, bug report: https://fogbugz.unity3d.com/default.asp?746102_g5sm8uav5vrdvpvv

Add comment · Show 1 · Share

Munchy2007 · Nov 19, 2015 at 10:25 PM 0

Share

I did some testing, and it broke somewhere after Unity version 5.0, earlier Unity versions don't suffer from the same problem, at least on the Samsung phone I tested it on.

Answer 3

Answer by MCoburn · Nov 20, 2015 at 12:59 AM

What is the rendering set as? OpenGL ES 2.0, ES 3.0 or "Automatic" ?

You might want to try just compiling for OpenGL ES 2.0, then 3.0 and see if it's a rendering issue. Although that device has a Adreno 306 GPU... Maybe the GPU drivers that Samsung has in their firmware are faulty, which happens from time to time.

Add comment · Show 1 · Share

Munchy2007 · Nov 20, 2015 at 03:11 PM 0

Share

I tried with both 2.0 and 3.0, same problem.

I can't help thinking that as the problem doesn't happen with Unity version 5.0 and below that it is something that has been introduced into Unity rather than a problem with the phone drivers.

That's purely speculation on my part though.

Answer 4

Answer by Digl · Nov 27, 2015 at 11:17 AM

I've had the same issue too, exporting from Unity 5 to a new Samsung Galaxy J1 (Android 4.4.4).

I did some testing on other Android Unity games too - the same error occurs when opening (PikPok's) Four Letters, but Rocket Bunnies plays just fine. Four Letters was released March 2015, whereas Rocket Bunnies was <2010.

But, Four Letters was still released before Unity 5.

Both of these games run fine on my Samsung Galaxy S2 (Android 4.1.2).

Seems to me like a device specific issue - have there been any driver updates?

Add comment · Show 2 · Share

Munchy2007 · Nov 27, 2015 at 02:03 PM 0

Share

As far as I know the phone has the latest software installed. However I haven't had the chance to test Unity 5.2.3f1 builds on it yet.

Although building my latest game with 5.2.3f1 (currently using 5.2.2f1) breaks it in odd ways without any runtime or compile errors,

MCoburn · Jan 01, 2016 at 01:21 AM 0

Share

As far as I know, Unity's 5.2.x branch has been horrid. I've had numerous issues regarding it, and I've just stuck with 5.1.4.

Android 5.1.1 display failure

4 Replies

Your answer

Welcome to Unity Answers

Follow this Question

Related Questions