Develop Reference

Unity3D spotlight glitch on Samsung S6 and S7 edge

We are developing a motorbikes racing game under Unity 5.3.4p4 for Android.
I have a spotlight attached to a gameobject (the motorbike), the farther it is from the center of the world (0, 0) the more unstable/shaking it becomes when moving. I've tested on many devices with different GPU and Android versions but this only happens in Samsung Galaxy Edge S6 and S7 devices (MALI GPU).
Does anyone has the same problem or know any solution for this?.
Thanks for your time.
EDIT:
After a lot of testing there seems to work fine only using Deferred instead of Forward rendering and enabling OpenGLES3, at least for the S7, the S6 has the same problem no matter what I do.
I've also tried downgrading to Unity 5.2.5 and upgrading to unity 5.3.5 without success.
As #Paul-Jan says, it seems it also affects iOS: https://community.unity.com/t5/Graphics/Problems-with-spotlight-on-mobile-precision-issue/td-p/2473711

Cordova/Phonegap slow performance with Open Layers on new Tablet, but fine on new phone

I have developed an application which uses Cordova/Phonegap on Android to display Open Layers 3 maps.
It is quite similar to this project:
https://github.com/netgis/ol3
I have found that the application runs smoothly on the Samsung Note 4 running Kitkat V4.4.4, and runs fine on an old S2 running Jellybean (almost equally well in fact), but it runs terribly slowly on a bran new Galaxy Tab Pro 12.2 running KitKat V4.4.2.
I was wondering if there is any Cordova/Phonegap expert out there who might know why.
The only difference between them that I can see is the version of android! V4.4.4 and V4.4.2.
I have discovered threads on SO which generically say that WebView can be a problem and cause slow performance, but I'm getting great performance on my Note 4, and the S2 runs better than the tablet does using Jellybean.
I'm not sure code would be useful to show here, essentially I have a Cordova Android application with a single HTML document with Open Layers 3 map embedded, that's it.

The problem turns out to lie with WebView, which uses the default Android browser. For some reason this browser restricts CPU support if you're trying to use GPU acceleration (enabled by default), but doesn't provide GPU acceleration itself (it's really strange but true).
Apparently KitKat has this problem prior to Android V4.4.3. So if you're running V4.4.4 you won't encounter this performance problem as it has been fixed (as it uses Chromium instead of the default browser).
Here's one of many references I've found which corroborate this:
https://code.google.com/p/chromium/issues/detail?id=315111
Some devices haven't yet been updated to this level, here are my completely up to date devices:
The tablet uses Android V4.4.2
The S2 uses Android V4.0.2
The Note 4 uses Android V4.4.4
The S2 uses Jelly Bean and is therefore fine, the Note 4 uses the updated KitKat and also runs fine, but the tablet struggles with the application to such an extent it is unusable owing to it being below V4.4.3.
For me, the majority of suggested solutions on SO are to disable hardware acceleration, but these suggestions are unsuitable as my application really does require hardware acceleration to render maps efficiently.
The solution is to take this problem away completely by forcing the use of Chromium irrespective of the OS Version through the use of Crosswalk.
There are plenty of resources I've found to use Cordova in synergy with crosswalk:
https://crosswalk-project.org/documentation/cordova.html
https://blog.nraboy.com/2014/10/use-crosswalk-ionic-framework-android-apps/

Android Font Kerning: Nexus 7 vs. Galaxy Tab 2

I'm currently developing an application that was originally meant to be run solely on Nexus 7 and Android 4.2. However, there was a change of plans and now it is meant to run on the Galaxy Tab 2, Android 4.1.1 instead.
I am using a custom font that rendered great on the Nexus 7. However, when downgrading the version of Android and switching to the Galaxy Tab 2, the font kerning got completely messed up and looks terrible. Spacing is way off from what it should be.
Any tips to point me in the right direction for fixing this issue? I don't have the slightest idea how to fix this, except for switching to a different font, which is less than ideal.

Sounds like you may have run across the kerning problem described here: Android Custom View code stopped working correctly in Jelly Bean 4.2
It is possible to work around it.

OpenGL ES 2.0 doesn't render on Android 4.0.3

I'm writing completely native OpenGL ES 2.0 game engine for Android. Previously I developed with Samsung Galaxy S (Android 2.3.3) and now with Samsung Galaxy S II (updated to Android 4.0.3). I didn't try the engine on Galaxy S II while it still had Android 2.3.3 (hardware specific problem?).
Now the engine runs and renders fine on Android 2.3.3 (tested on Galaxy S), but it doesn't render on Android 4.0.3 (tested on Galaxy S II). The problem is similar to this: OpenGL Renderer not working on Ice Cream Sandwich
Everything else works without problems on 4.0.3 except the rendering, nothing appears on the screen. I managed to render a single triangle on 4.0.3 but a vertices extracted from a model won't render (using glDrawElements()) with or without textures.
I hope there is a simple solution for this.
Cheers

I should have checked GL errors earlier. The problem occurred with glDrawElements(), where I used GL_UNSIGNED_INT (GL_UNSIGNED_BYTE and GL_UNSIGNED_SHORT are only allowed values). Android 2.3.3 didn't seem to care about that. I changed it to GL_UNSIGNED_SHORT and now it works perfectly.

camera issue in emulator 2.2 in android

i am suffering with a problem that in android 2.2 emulator, camera doesn't work. it closes down the camera automatically. But this problem is not happening in android 1.5 emulator.
Why it is happening? can any body help?

This is a known issue and has been asked several times on SO - here are some pointers to possible solutions. However, the camera emulation in 2.2 is known to be buggy:
Removing the stencil buffer
Switching to 2.1 or 2.3
So you have two options: Either you try to follow the directions, given by the correct answer in the first thread or switch to an emulator running on either 2.1 or 2.3+.