[GUIDE] Disable CPU rendering

I flashed this moments ago...
Thanks to those who "bumped" it up.
I was thinking with was "included" in the latest MiRaGe ROM update, but re-checked the OP before flashing this.
Flashed in Recovery/successful/Reboot...
Can I get a confirm of matching a system folder(s) library that should basically look like this.
 

Attachments

  • screenshot-20130525-115207am.png
    screenshot-20130525-115207am.png
    32.8 KB · Views: 114
No libGLES_android.so file (the software rendering library) present would indicate the EGL patch is installed.

you can also check egl.cfg, it should only have "0 1 adreno200" in it
(the default state also has "0 0 android" above that)



also... if anyone happens to know... shouldn't just changing egl.cfg disable the software rendering tree?
Shouldn't need to delete libGLES_android.so? Seems to work for me in CM9, changed just egl.cfg and I don't see the software rendering library being loaded at all... maybe something in stock rom liked to load up software rendering even when egl.cfg said not to?



And for anyone that's particularly curious... I spent some time googling and got a picture something like this:

Android has used the GPU for screen composition for a long time now, but individual tiles will be drawn by the CPU if they aren't flagged as being supported for hardware rendering, and will sometimes be drawn with the CPU in an attempt to save memory. This *should* be a helpful scenario - when you fire up say a basic calculator... android is trying to not use ~8MB of RAM on running adreno for a tile when CPU based rendering can render the same tile using less than 2MB...

The theory goes something like ICS is supposed to do a better job of deciding what should be GPU rendered, but still tends to CPU render certain things (besides just apps that aren't marked hardware compatible) - and an increased number of tiles on screen can mean trying to force full GPU rendering takes a hefty overhead in RAM.

At least... that's the picture I seemed to get after 15 minutes of googling the subject - however developers with far more experience than me have opted to put this into most of their roms on this phone (at least in the form of a modified egl.cfg) - so I'd say chances are pretty good that their claims are true, that hardware rendering is much smoother than software rendering on our phones.
 
Hmmmm.. I just tried the egl patch on my ICS rom along with GPU tweaks, they both work nicely together.

1362500614007.png


Sent from my LG-E739 running PenberRom2 using Tapatalk 2
 
Very good thread here, thanks, just flashed the VM670 patch. zip file, i guess it's to early to notice any difference although i didn't even realize it, but my keyboard is much better, yes much snappier!

I'm running MiRaGe, maybe i should ask these questions in that thread, but since i'm here maybe someone could help me out cause i think these questions are sort of related to this thread.

In cyanogenmod settings under performance, what should the vmheap be set at, when i downloaded the rom it was set at 32 so that's where i left it. Also the Compcache ram usage, it's not set on anything, and one more, the scrolling cache, how should this be set? I don't even know what these settings do, if anyone could answer any of this it would be greatly appreciated!

@Leo ...if you feel this doesn't belong in your thread, please feel free to have the moderator delete it, thank you. ;)

NOTE : Found out MiRaGe rom already has the patch built in ,so what i thought was a snappier keyboard had to be placebo effect.

Thanks to tli and Mrg666 for clearing that up. Is it still worth my time to do the build.prop tweak?

Thanks Leo for helping out our phone's performance.
 
Last edited:
screenshot2013060204282.png


I did the build.prop tweak today, let you know if i notice any difference.

Thanks Leo!!!
 
Last edited:
Compcache: effectively trades CPU power for memory - some people swear by it... but compcache can often cause performance to degrade as uptime increases - personally after a day or so with compcache enabled, my phone starts hitting swap walls, not as bad as using an aggressive swap file and really low minfree settings, but still noticeable and irritating imo.


Also... those dexopt-flags... is there a reason you have u=n set instead of u=y ? u is unicore right...?
and the Optimus is single core... doesn't building the dalvik for a multicore system just slow things down on single core hardware?
 
I was just following the op's build.prop tweak on page 5 post #114.;)

@vector 84an...you are correct, on page 5 it says u=n on the first page it has u=y. I'm so glad you caught that mistake!

So it should be u=y correct? Thank you for catching this!

Now i'm totally confused, on page 5 i clicked on the link which took me to the xda thread and that matches my screenshot "u=n"but that is for a galaxy phone. And in the first page of this thread Leo has "u=y"now which one is it supposed to.to be?

Someone please help me out here before i change these files AGAIN

THANKS IN ADVANCE! :p
 
Last edited:
Don't feel so bad. I've flashed most every ROM, recovery, theme, and tweak thats come out for the V since 2011. I couldn't begin to remember how many times I changed things, and that' not including when I was trying to learn how to port ROMs over.
Try the first one you mentioned, do a strees test, then try the other. Stress test app in PlayStore.

Sent from my LG-VM670 using Android Central Forums
 
I recommend u=y for a single core processor phone, such as mine. Thanks for catching on to that, I updated my thread on xda but almost forgot this one. You'll see more tweaks over there, mostly Qualcomm and ICS related.

1362500614007.png


Sent from my LG-E739 running PenberRom2 using Tapatalk 2
 
Hi,

I know this post is old, but is this something that would work on my Samsung Note 4 with KitKat 4.4.4?

Or are there manual changes I can make in my phone's Settings, or in the Build.Prop file?

Thank You! :-)
 
Hi,

I know it's 2017 now, but I was wondering please:

1) Do you think this will work on my Samsung Note 4 running the "came with it", OEM Samsung KitKat 4.4.4?

2) My EGL.Cfg just says "Adreno", not "Adreno200". Is that due to the Phone/OS? Or is that an intentional change by it from one to the other on every phone this is used on?

3) The Permissions, I assume are actually in Columns, so it would actually be:

R R R
W - -
- - -

Correct?

Hopefully someone will see this post and respond. :-)

Thanks!
 

Forum statistics

Threads
955,153
Messages
6,963,926
Members
3,163,210
Latest member
Hollytryx