Post Reply

Benefits/disadvantages to developer GPU options?

OP Jason78729

29th May 2014, 07:32 AM   |  #1  
OP Senior Member
Flag Austin
Thanks Meter: 24
 
139 posts
Join Date:Joined: Jan 2011
More
What are the advantages and/or disadvantages of enabling "force GPU rendering" and "disable HW overlays"?

Sent from my Nexus 5 using XDA Free mobile app
Hammer_Of_The_Gods
29th May 2014, 08:16 AM   |  #2  
Guest
Thanks Meter: 0
 
n/a posts
Hi,

You can test easily by yourself and see if you see any advantages and/or disadvantages, right? Just tick/untick and even no need for a reboot... It tends to make some old apps smoother.

If it helps you, here are two quotes that summarize well.

About "force GPU rendering":

Quote:

Enabling this preference in developer options offloads task of rendering window components like buttons, text and complex 2d graphics calculations to GPU. This often results in much faster UI rendering including animations.
On one side you will definitely achieve better frame rate (and hence smooth experience) throughout system, but you may end up using more battery. On certain devices, GPU consumes more power the CPU, hence you may observe 5-15% lower battery life with option enabled.

I would recommend having this option enabled on devices with weaker CPUs e.g. You should seldom need to enable this on dual-core 1.4ghz ARM CPU.

offloading UI rendering to GPU has obvious benefits so that CPU can work on other important tasks like database IO, data manipulation, layout calculations and responding to other user inputs.

About "HW overlays":

Quote:
Originally Posted by molesarecoming

... hardware overlay allows the renderer to take a couple of regions aside and treat them optimized. then theres the cpu and gpu. usually android decides which abstraction is best for each view, taking things like transparency into account and what not. you switch hw overlays off, project butter goes out of the window but cpu and gpu still do the job. you force gpu, the composition will be done by your gfx chip. just don't touch it - its meant for developers picking up debugging output.

I have force GPU rendering enabled since years, it helps about smoothness in XDA app for example, on my side never encountered any side effects, at least for me.
Last edited by Hammer_Of_The_Gods; 29th May 2014 at 08:22 AM.
The Following 4 Users Say Thank You to For This Useful Post: [ View ]
29th May 2014, 07:42 PM   |  #3  
OP Senior Member
Flag Austin
Thanks Meter: 24
 
139 posts
Join Date:Joined: Jan 2011
More
Thanks, that was exactly what I was looking for. I usually keep force GPU rendering on as well but always had mixed results with disable HW overlays. The definitions helped make sense of that.

Sent from my Nexus 5 using XDA Free mobile app
30th May 2014, 11:24 AM   |  #4  
Senior Member
Flag Southport
Thanks Meter: 10
 
226 posts
Join Date:Joined: Mar 2014
More
Hi. I'm rooted with xposed- stock os. I know that I can no longer enable art so i am wondering if this is the same.... Can I enable the GPU HW and rendering without a brick or bootloop

Sent from my Nexus 5 using XDA Premium 4 mobile app
Hammer_Of_The_Gods
30th May 2014, 11:32 AM   |  #5  
Guest
Thanks Meter: 0
 
n/a posts
Quote:
Originally Posted by dec1153

Hi. I'm rooted with xposed- stock os. I know that I can no longer enable art so i am wondering if this is the same.... Can I enable the GPU HW and rendering without a brick or bootloop

Hi,

No, it's not the same thing, about ART: http://forum.xda-developers.com/goog...alvik-t2516646.

And yes you can enable them without any issue, nothing related to Xposed (unless an Xposed module breaks something related to those options but I highly doubt). If you want to be sure then make a Nandoid backup before (in any case the "Disable HW overlays" doesn't persist at boot).
Last edited by Hammer_Of_The_Gods; 30th May 2014 at 11:45 AM.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Nexus 5 Q&A, Help & Troubleshooting by ThreadRank