worldWind error in android level 23

[mardani-h]

hi guys i use worldwind sdk and when i run my app earth shape is incorrect but i run app on android level 19 work good i think open Gl library dont work correct in android level 23 tanks for help

[pdavidc]

Hello, and thanks for reaching out to us. We're not seeing this problem with Android SDK 23, and need more information about your environment. Can you send us the device make and model, Android OS version, and log output?

[mardani-h]

hi my device is samsung galaxy note 4 and then i update to android 6 open gl library dont work correct my device has cpu exynos 5433 - mail t760 i think this problem for update 6 for may device

On Tue, Sep 6, 2016 at 8:07 PM, David Collins notifications@github.com wrote:

Hello, and thanks for reaching out to us. We're not seeing this problem with Android SDK 23, and need more information about your environment. Can you send us the device make and model, Android OS version, and log output?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/NASAWorldWind/WorldWindAndroid/issues/62#issuecomment-244991895, or mute the thread https://github.com/notifications/unsubscribe-auth/AK2hor-fGp9EqGTZXF3lQSOWJEw4MYoJks5qnYjUgaJpZM4J0lBR .

[SimoneMike]

I am also seeing the same issue on the Panasonic FZ-B2 tablets running SDK 23. The version is 6.0.1 running on the tablet.

I installed the latest example APK to test and make sure it wasn't an engineering error on my part. The example APK also exhibits the behavior where no globe is displayed.

[jgiovino]

I have seen similar issues with past experience where we exceed the bounds of the shader's float data type. The image above shows a lot of ones and zeros in the vertex coordinates. Please verify when updating OS's the GLES stack did not get downgraded to a SW renderer. It would be interesting to see both "OpenGL driver version" under "About tablet" before and after upgrade. One way to force this type of behavior is to run the application on the AVD and make sure to NOT select "Use Host GPU". BIG IF, this is in fact the reason THEN the solution is to normalize the world coordinate system prior to passing vertices down the GL pipeline. In other words, change the world units from meters to kilometers or some multiple thereof.

[Skalaw]

Also problem with LG-K350 API 23

[ComBatVision]

I have Samsung Galaxy Note 5 and Samsung Galaxy Tab S 8.4 with the same bug. I think most of Android 6.0 Samsung devices should have this bug.

[zglueck]

@pdavidc @jgiovino would utilizing the highp float precision type in the vertex shader help with the situation? It currently uses mediump:

https://github.com/NASAWorldWind/WorldWindAndroid/blob/master/worldwind/src/main/res/raw/gov_nasa_worldwind_basicprogram_vert.glsl#L6

[Andro-Samurai]

the screenshot of GALAXY S6 - ANDROID 5.1

Also it appears in: 1- DEVICE Device Galaxy J7(2016) (j7xelte) Manufacturer Samsung Device type Phone Device language Polish CPU make Samsung CPU model Exynos 7870 Native platform armeabi-v7a, armeabi RAM (MB) 2048 Screen size 720 × 1280 Screen density (dpi) 320 OpenGL ES version 3.0 OS Android 6.0

2- DEVICE Device Galaxy S7 (herolte) Manufacturer Samsung Device type Phone Device language English CPU make Samsung CPU model Exynos 8890 Native platform armeabi-v7a, armeabi, arm64-v8a RAM (MB) 4096 Screen size 1440 × 2560 Screen density (dpi) 640 OpenGL ES version 3.1 OS Android 6.0

3- DEVICE Device A3-A40 (acer_jetfirefhd) Manufacturer Acer Device type Tablet Device language English CPU make Mediatek CPU model MT8163 Native platform armeabi-v7a, armeabi, arm64-v8a RAM (MB) 2048 Screen size 1920 × 1200 Screen density (dpi) 240 OpenGL ES version 3.0 OS Android 6.0

4- DEVICE Device Galaxy TabS 10.5 (chagalllte) Manufacturer Samsung Device type Tablet Device language English CPU make Samsung CPU model Exynos 5420 Native platform armeabi-v7a, armeabi RAM (MB) 3072 Screen size 2560 × 1600 Screen density (dpi) 320 OpenGL ES version 3.0 OS Android 6.0

5- DEVICE Device Galaxy S6 (zeroflteatt) Manufacturer Samsung Device type Phone Device language English CPU make Samsung CPU model Exynos 7420 Native platform armeabi-v7a, armeabi, arm64-v8a RAM (MB) 3072 Screen size 1440 × 2560 Screen density (dpi) 640 OpenGL ES version 3.1 OS Android 6.0

6- DEVICE Device Galaxy S7 Edge (hero2lte) Manufacturer Samsung Device type Phone Device language English CPU make Samsung CPU model Exynos 8890 Native platform armeabi-v7a, armeabi, arm64-v8a RAM (MB) 4096 Screen size 1440 × 2560 Screen density (dpi) 640 OpenGL ES version 3.1 OS Android 6.0

7- DEVICE Device Lenovo A2016b30 (A2016b30) Manufacturer Lenovo Mobile Device type Phone Device language Portuguese CPU make Mediatek CPU model MT6735M Native platform armeabi-v7a, armeabi RAM (MB) 1024 Screen size 480 × 854 Screen density (dpi) 240 OpenGL ES version 3.0 OS Android 6.0

8- DEVICE Device Galaxy S5 Neo (s5neoltecan) Manufacturer Samsung Device type Phone Device language English CPU make Samsung CPU model Exynos 7580 Native platform armeabi-v7a, armeabi RAM (MB) 2048 Screen size 1080 × 1920 Screen density (dpi) 480 OpenGL ES version 3.0 OS Android 6.0

[jgiovino]

These images do in fact look like the GPU float has been exceeded.

You can try highp in both vert and frag shaders but since its happening on this many devices it probably is not the issue.

I have been able to normalize world coordinates on SW renderers using the previous 'WorldDroid' WorldWind implementation from Trilogis.

We need to track down the GPU chipset for the devices below and see if its failing on 'like technology' then we can track down that graphics stack.

Bottom line, for each of the 8 devices listed lets figure out the GPU technology backing it.

If they are in fact on different SoC's then we need to see if they are sharing common GPU core logic and/or common dri/drm drivers.

v/r,

Jeff

---

From: Andro-Samurai notifications@github.com Sent: Sunday, January 22, 2017 6:00:31 PM To: NASAWorldWind/WorldWindAndroid Cc: Giovino, Jeffrey D.; Mention Subject: Re: [NASAWorldWind/WorldWindAndroid] worldWind error in android level 23 (#62)

[1bug]https://cloud.githubusercontent.com/assets/25287348/22186916/46b39852-e106-11e6-9632-947a6d68968d.png

the screenshot of GALAXY S6 - ANDROID 5.1

Also there it appears in: 1- DEVICE Device Galaxy J7(2016) (j7xelte) Manufacturer Samsung Device type Phone Device language Polish CPU make Samsung CPU model Exynos 7870 Native platform armeabi-v7a, armeabi RAM (MB) 2048 Screen size 720 ? 1280 Screen density (dpi) 320 OpenGL ES version 3.0 OS Android 6.0

2- DEVICE Device Galaxy S7 (herolte) Manufacturer Samsung Device type Phone Device language English CPU make Samsung CPU model Exynos 8890 Native platform armeabi-v7a, armeabi, arm64-v8a RAM (MB) 4096 Screen size 1440 ? 2560 Screen density (dpi) 640 OpenGL ES version 3.1 OS Android 6.0

3- DEVICE Device A3-A40 (acer_jetfirefhd) Manufacturer Acer Device type Tablet Device language English CPU make Mediatek CPU model MT8163 Native platform armeabi-v7a, armeabi, arm64-v8a RAM (MB) 2048 Screen size 1920 ? 1200 Screen density (dpi) 240 OpenGL ES version 3.0 OS Android 6.0

4- DEVICE Device Galaxy TabS 10.5 (chagalllte) Manufacturer Samsung Device type Tablet Device language English CPU make Samsung CPU model Exynos 5420 Native platform armeabi-v7a, armeabi RAM (MB) 3072 Screen size 2560 ? 1600 Screen density (dpi) 320 OpenGL ES version 3.0 OS Android 6.0

5- DEVICE Device Galaxy S6 (zeroflteatt) Manufacturer Samsung Device type Phone Device language English CPU make Samsung CPU model Exynos 7420 Native platform armeabi-v7a, armeabi, arm64-v8a RAM (MB) 3072 Screen size 1440 ? 2560 Screen density (dpi) 640 OpenGL ES version 3.1 OS Android 6.0

6- DEVICE Device Galaxy S7 Edge (hero2lte) Manufacturer Samsung Device type Phone Device language English CPU make Samsung CPU model Exynos 8890 Native platform armeabi-v7a, armeabi, arm64-v8a RAM (MB) 4096 Screen size 1440 ? 2560 Screen density (dpi) 640 OpenGL ES version 3.1 OS Android 6.0

7- DEVICE Device Lenovo A2016b30 (A2016b30) Manufacturer Lenovo Mobile Device type Phone Device language Portuguese CPU make Mediatek CPU model MT6735M Native platform armeabi-v7a, armeabi RAM (MB) 1024 Screen size 480 ? 854 Screen density (dpi) 240 OpenGL ES version 3.0 OS Android 6.0

8- DEVICE Device Galaxy S5 Neo (s5neoltecan) Manufacturer Samsung Device type Phone Device language English CPU make Samsung CPU model Exynos 7580 Native platform armeabi-v7a, armeabi RAM (MB) 2048 Screen size 1080 ? 1920 Screen density (dpi) 480 OpenGL ES version 3.0 OS Android 6.0

- You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/NASAWorldWind/WorldWindAndroid/issues/62#issuecomment-274367333, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQqdwYV4_L7ZcnFKqrgIlH2gw4grFqNXks5rU9-PgaJpZM4J0lBR.

[Andro-Samurai]

@jgiovino I'v tracked down the GPU chipset of the devices All of them have a Mali series GPU, to be exact Mali-T(number) Please check them out https://en.wikipedia.org/wiki/Mali_(GPU)#Variants do you notice anything?

Thanks

[jgiovino]

Interesting read… https://community.arm.com/graphics/b/blog/posts/benchmarking-floating-point-precision-in-mobile-gpus it seems to focus on precision related to the fragment shader and not the vertex which is where are problem seems to lie,. http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.dui0363d/CJAFCCDE.html this does not explicitly state the floating point architecture for the vertex shader only implies by stating “the geometry processor”

Looking at the problem backwards we can calculate the number of bits for the exponent is required to represent world coordinates defined as meters.

Value = (-1)^s (1+sig) 2^(exb-bias) assume zero bias

6376136 = 2 * 2^e = 2^(e+1) e > 21 that only requires 7 exponent bits in twos compliment

So maybe the question is: Do the Mali GPUs have 7 or less exponent bits in their vertex shader’s lowp floating point numbers? This doesn’t seem to pass the sniff test does it?

From: Andro-Samurai [mailto:notifications@github.com] Sent: Tuesday, January 24, 2017 5:19 PM To: NASAWorldWind/WorldWindAndroid WorldWindAndroid@noreply.github.com Cc: Giovino, Jeffrey D. jgiovino@mitre.org; Mention mention@noreply.github.com Subject: Re: [NASAWorldWind/WorldWindAndroid] worldWind error in android level 23 (#62)

@jgiovinohttps://github.com/jgiovino I'v tracked down the GPU chipset of the devices All of them have a Mali series GPU, to be exact Mali-T(number) Please check them out https://en.wikipedia.org/wiki/Mali_(GPU)#Variants do you notice anything?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/NASAWorldWind/WorldWindAndroid/issues/62#issuecomment-274957707, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQqdwRR3j2LskNpcfgPrlfOqbQWIsdCDks5rVnjjgaJpZM4J0lBR.

[ComBatVision]

Devices with the same GPU works normally on previous Android. So I think it is not a hardware issue of chip.

[jgiovino]

So somewhere between the pipeline and the GPU our vertecies are being mushed. That seems to now point to a driver, or reverting to a SW stack. I wonder if specifying gles version in the shaders could help.

version 100

From: Sufaev [mailto:notifications@github.com] Sent: Wednesday, January 25, 2017 9:06 AM To: NASAWorldWind/WorldWindAndroid WorldWindAndroid@noreply.github.com Cc: Giovino, Jeffrey D. jgiovino@mitre.org; Mention mention@noreply.github.com Subject: Re: [NASAWorldWind/WorldWindAndroid] worldWind error in android level 23 (#62)

Devices with the same GPU works normally on previous Android. So I think it is not a hardware issue of chip.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/NASAWorldWind/WorldWindAndroid/issues/62#issuecomment-275115881, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQqdwVTh2243cfTy33aDs0qrgbf2Mxwyks5rV1a7gaJpZM4J0lBR.

[Andro-Samurai]

Even though most of affected devices are running API 23 but there is an incident that it did not work properly on API 22.

Also I found out that it worked on the same device if the CPU was different; for example: it did not work correctly with Galaxy S7 Edge (hero2lte) CPU make: Samsung, CPU model: Exynos 8890, API: 23 but worked perfect with Galaxy S7 Edge (hero2qltevzw) CPU make: Qualcomm, CPU model: MSM8996, API: 24

[Andro-Samurai]

Hello Guys,

I think this bug is the most important one to fix because it affects nearly 50% of the people because the affected devices are (unfortunately) the most popular devices by far. could you please tag this as "important" or "Urgent"

you can perform tests on real devices from Samsung remote test lab http://developer.samsung.com/remotetestlab

Thank you for your help

[pdavidc]

@Andro-Samurai You're absolutely right, and we're working on a fix. See #78, which is more general and we think captures the actual underlying cause.

[pdavidc]

@Andro-Samurai, @shazde2025, @Sufaev, @SimoneMike, @Skalaw : Would you please try the latest code in the develop branch, and let us know whether or not the issue is fixed?

[ComBatVision]

It works now Samsung Tab S 8.4 Android 23.

[SimoneMike]

David,

The fix worked beautifully. Thank you for taking care of this issue.

-Mike

On Jan 30, 2017, at 2:11 PM, David Collins notifications@github.com wrote:

@Andro-Samurai, @shazde2025, @Sufaev, @SimoneMike, @Skalaw : Would you please try the latest code in the develop branch, and let us know whether or not the issue is fixed?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.