• Locked Locked
  • Replies 4 replies
  • Subscribers 136 subscribers
  • Views 6513 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Samsung Galaxy Note 2 Mali GPU Problem with Opengl es2.0 in Android

Harikrishnan v
Note: This was originally posted on 20th June 2013 at http://forums.arm.com

Hi Everyone,

I have created an android app for drawing of lines,circles.. by using GLSurfaceView in OpenGLES 2.0 like an Auto cad app.

The app works well with Google Nexus 7, in the sense that if we draw a line & then a circle the line doesn't get erased in surface view. But with Samsung Galaxy Note II, it is entirely different.

The line previously drawn before a circle being drawn, gets erased. i.e., each time if we draw a new line or circle, the previous one gets erased.I can draw only one image at a time. What I need is the same output which I get in Google Nexus 7 in Samsung Galaxy Note II.i.e.I want to draw more than one image in the GLSurfaceView at a time.

Note : Both the Android OS in Google Nexus 7 and Samsung Galaxy Note II are Jelly Bean 4.2. But both devices are different GPU. Google Nexus 7 GPU is ULP GeForce & Samsung Galaxy Note II is Mali400MP.

Would this be an issue in the rendering of output of the Surfaceview ?

Should we take into account of GPU while Coding ?

Can anyone tell me why this problem of different output in different devices ?

I  Posted this Problem in stackoverflow also. i got one reply. but, i cant solve out my issue..
this link having some sample code also for understanding..
http://stackoverflow.com/questions/17187032/why-my-opengl-output-differs-for-various-devices

Thanks Advance
Parents
  • Note: This was originally posted on 15th July 2013 at http://forums.arm.com

    Note that color buffer preservation is not "free" as far as the GPU will generally need to read back the previous frame as the output window surface for the next frame is usually different due the pipeline behavior (i.e. they are N-buffered).

    If you only actually need to preserve a small area of the screen then it can be more efficient just to explicitly redraw using draw operations in the application.


    HTH,
    Iso
Reply
  • Note: This was originally posted on 15th July 2013 at http://forums.arm.com

    Note that color buffer preservation is not "free" as far as the GPU will generally need to read back the previous frame as the output window surface for the next frame is usually different due the pipeline behavior (i.e. they are N-buffered).

    If you only actually need to preserve a small area of the screen then it can be more efficient just to explicitly redraw using draw operations in the application.


    HTH,
    Iso
Children
No data