Blue Walkabout style on Android 5.1.1

[rwrx]

I have tried sample application and when I switch to Walkabout style in device with Android 5.1.1 (API 22) I get this screen:

I have also tried it on device with Android 4.0.3 (API 15) and on this device I can't see any map with any of the styles. I think that at some point in the past it worked on Android 4.0.3.

I have also tested it on devices with Android 4.4.2, 6.0.1, 7.0 and 7.1.2 and on these devices it worked correctly.

[matteblair]

Hey @rwrx, thanks for testing our stuff on all these devices - it's super helpful for Android development!

The "blue" effect has come up before on other devices. We eventually tracked down the cause and determined that it's due to certain GPUs failing to handle a "dependent texture lookup" in our terrain shader. "Dependent texture lookup" was not commonly supported by mobile GPUs until fairly recently, and some GPUs still have bugs like this when it happens.

These cases will become increasingly rare as phones and drivers are updated, but as you've shown it's not impossible to find cases like this. We don't have a work-around for this right now, but it will often be corrected by updating the OS on the affected device.

Can you tell us the model of phone that produced this effect? With enough samples we ay be able to narrow the problem down to a specific GPU manufacturer.

[rwrx]

Thank you for your answer. I am sorry I forgot to add device models. That device with Android 5.1.1 is Honor 4C (hi6210sft) and device with Android 4.0.3 is HTC EVO 3D (X515m).

I am planning to use Tangram ES in my app for offline maps so I have just tested it because I have lots of users using Android 5 so I just wanted to make sure if it is working correctly on all Android versions and accidentally I have this one strange device :).

[rwrx]

@matteblair Is it possible that this could be resolved in Tangram ES itself?

[matteblair]

@rwrx it's possible that this has been fixed in Tangram ES but unfortunately I don't have any of the impacted devices, so I can't say for sure.

[rwrx]

I can confirm, that on both of the devices I mentioned above is this issue still occurring.