Android: CREATESCREEN fails on some devices (like NEXUS 7).

[spacefractal]

http://www.glbasic.com/forum/index.php?topic=8677.msg73706#msg73706

The issue with Nexus 7 is that when using CREATESCREEN/USESCREEN you will get similar errors to:

         I/glbasic ( 8665): glBindRenderbufferExt failed 8cd6

which is: 

         GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT

I believe this is an issue within GLB whereby it's not defining the correct z buffer component (16bits vs 32bits).

If you do NOT use createscreen/usescreen in your app/game, then it will run perfectly fine on the Nexus 7.

Note: The same also applies to the Asus Transformer.

I thinks he can been right you might use wrong settings. If its cant been fixed, its would been nice to return a gracefull error rather than a crash.

[Beginner]

I guess the problem are Nvidia processors.

We recognized the same problem on Medion Lifetab and Acer Iconia A210. Both devices also have nvidia chips inside.   

[spacefractal]

Its might not support the texture format used, but might work with different settings. But it's should not crash, better so nothing so we can catch the issue.

[msx]

I think it also occurs in Samsung Galaxy S. At least my application does not work and I had to remove it from the market.

All with GLB11

[msx]

Correction to previous post: The problem occurs on a HTC Desire HD with GPU Adreno 205

[spacefractal]

strange....

CREATESCREEN works pretty nice on extracly that device here (HTC Desire HD with Android 2.3.5), also with v11 Beta. Its mightbeen different models of same phone? Howover Greedy Mouse did run too slow (but its was just a quick offbuffer test, so speed was not about it). Its use Android 2.3.5 as version number here.

I gonna thinks do you using a fixed sprite number or GENSPRITE()? I did that with GENSPRÍTE(). Mightbeen CREATESCREEN have trouble with fixed sprite number?

_____

I also tested with bigger resoulution than the screen (double resolution) and its still works nice (dispite alpha issues due wrong blendmode, not to been debated here). I so property, its a "out of memory" issue?

[msx]

I do not use gensprite (), but the same application works well on a ZTE Blade.

I do not have HTC Desire HD for more testing.

[fivesprites]

I've not experienced any problems on the Galaxy S, S2 or even the Galaxy S3. 

Confirmed as also non-working on the Motorola Atrix (Nvidia gpu).  Unconfirmed report of it failing on Samsung Galaxy Tab too, although this uses PowerVR graphics so is a curiosity.

[Kitty Hello]

Also in V11? I think this was fixed, already.

[spacefractal]

its works here, but I do not have the NEXUS 7.  Mightbeen its have been fixed after the v11 beta release? So its might need retest here.

[fivesprites]

No, not fixed. Definitely still an issue with the latest V11 beta I'm afraid.

[caffeinekid]

This is the same problem that has been haunting people for a year plus? It would be great if a fix is possible. Then I don't have to learn java to get my game working on these devices. lol

[Kitty Hello]

I found it. The depth buffer attachment was wrong, but gave no error. I'll try to create with 24,32,16 bit depth buffer and if all fails, I go without one. For 2D graphics on that off-screen that would still do better than a crash.

[caffeinekid]

That's great news. Can you let us know when it's added to the beta so I can try compile my game and get someone with a Nexus to try it for me.