Under settings > Developer Options (User Interface) there's a checkbox that's unchecked "Forec GPU rendering". Has anyone tried this?
Anyone tried "force GPU rendering"?
- Thread starter 6tr6tr
- Start date
I was going to try the Force GPU Rendering, but I wasn't sure what it did or if there was any benefit.
Does anybody know what this "Don't keep activities" option under Developer options menu is? The description says "Destroy every activity as soon as the user leaves it," so I wasn't sure if it was basically like a built in task killer or something else that I probably shouldn't mess with, lol.
Does anybody know what this "Don't keep activities" option under Developer options menu is? The description says "Destroy every activity as soon as the user leaves it," so I wasn't sure if it was basically like a built in task killer or something else that I probably shouldn't mess with, lol.
chud
Well-known member
- Jun 16, 2011
- 983
- 48
- 0
The only thing you guys really want to have checked in that Dev menu is USB Debugging and even thats optional. Otherwise everything else in there ( I guess except for Stay Awake) is just like it says.....for Developers(ment).
Window Animation Scale and Transition Animation Scale.....if you turn those off you should see a tiny battery life improvement but you'll also lose the menu transition effects and the locking TV screen animation.
Window Animation Scale and Transition Animation Scale.....if you turn those off you should see a tiny battery life improvement but you'll also lose the menu transition effects and the locking TV screen animation.
Yea no need for it really. There is a small difference with certain apps. It makes then run a little smoother but I think it might create more problems then it solves. As far as the question reguarding the "don't keep activities" that makes it so that no app will stay in cache for multitasking. I wouldn't suggest having that on either.
Sent from my Nexus S 4G
Sent from my Nexus S 4G
- Nov 25, 2010
- 15,958
- 2,752
- 0
I've been running ICS custom ROMs since they first hit back before ICS was even officially released... The force GPU rendering I leave off, it has some benefit in certain apps but not anything that is gonna blow your socks off..
Many of the other settings under Developer Options are simply that, dev options for devs to trouble shoot things and see what is happening during testing..
Many of the other settings under Developer Options are simply that, dev options for devs to trouble shoot things and see what is happening during testing..
With it on, I find apps quit much faster, the homescreen whips into view and folders close faster and animations on the homescreen/app drawer seem musch snappier.
If you are like me and don't have any issues enabling gpu rendering, then here is a way you can force the phone to always use it.
Checking the setting under developer tools only tells the phone to hardware accelerate OpenGL when there is a flag set to do so within the SurfaceView or Canvas class.
Making the following changes will force the phone to always use gpu rendering regardless of this.
MAKE A NANDROID BACKUP FIRST PLEASE. THERE IS A CHANCE THAT IF YOU DO SOMETHING NOT IN THIS GUIDE YOU COULD MAKE YOUR PHONE UNUSABLE.
What we are going to do is rename or delete the software rendering library file and comment out or delete one line in a text file that references the Android OS as a rendering engine. Oh, and did I mention to make a NANDROID first? ^_^
Ok....
Precautionary Step (optional) : Using Root Explorer or equivalent, navigate to /system/lib/egl and mount system as read write. If you plan on not preserving the original files within this directory, then copy both the libGLES_android.so and efg.cfg files to your sdcard in case you want to manually reverse the changes if you need to for some reason (as time goes on less and less apps should have any compatibility issues and I have none with the 176 apps I have installed). Since you made a NANDROID as well you could always restore from there as well if needed lol.
1. First, Rename the libGLES_android.so file to libGLES_android.so.bak, or simply delete it if you did the precautionary steps to preserve the original.
2. Next, open the egl.cfg file in a text editor. There should be three lines (the last being just a blank line...IT IS IMORTANT to make sure there is at least one blank line at the end of the file... Just as if you were editing build properties or other configuration files). This is what it should contain:
0 0 android
0 1 POWERVR_SGX540_120
<representation of blank line>
What we want to do is stop Android from processing the first line. You could either comment it out such as:
#0 0 android
0 1 POWERVR_SGX540_120
<representation of blank line>
OR again, if you preserved the original files, then you can simply delete that first line that has "0 0 android" in it.
Save your changes and close out if your file explorer and now reboot your phone.
After rebooting your phone again, it will have no choice but to use GPU rendering as we've removed the Android OS from accelerating anything.
And yes, I there is also a build prop edit, and but it only does the same thing as checking the setting under developer tools so I won't go there as it's simply redundant. I also could have simplified this quite a bit but wanted to make sure you are aware of the two methods of restoring this back to stock if desired (restoring your NANDROID or copying the backup files you made if you made them back from your sdcard and back into the /system/lib/egl directory)... AND wanted to point out that if you make changes to or create any configuration file and do not leave at least one blank line at the end then the previous line will not be processed, meaning in this case it would be the same as removing both the first two visible lines. This would leave Android with no references to OpenGL rendering as far as I know so could probably have nasty consequences (or maybe none.. I haven't tested it, but you get the idea).
Post your results back here...as I'm curious to see if anybody else can tell the difference afterwards. If you have an app incompatibility name the app (or if a LOT don't worry lol). I know Quickpic and Picsay Pro both mention NOT forcing GPU rendering but I haven't ran into any issues with either. I also haven't had a game I couldn't play either, but then again I normally only play games and install apps from quality developers so might not have installed the apps you guys are using to cause issues. That's why I'd like to know of a few so I could test them out using this method.
Checking the setting under developer tools only tells the phone to hardware accelerate OpenGL when there is a flag set to do so within the SurfaceView or Canvas class.
Making the following changes will force the phone to always use gpu rendering regardless of this.
MAKE A NANDROID BACKUP FIRST PLEASE. THERE IS A CHANCE THAT IF YOU DO SOMETHING NOT IN THIS GUIDE YOU COULD MAKE YOUR PHONE UNUSABLE.
What we are going to do is rename or delete the software rendering library file and comment out or delete one line in a text file that references the Android OS as a rendering engine. Oh, and did I mention to make a NANDROID first? ^_^
Ok....
Precautionary Step (optional) : Using Root Explorer or equivalent, navigate to /system/lib/egl and mount system as read write. If you plan on not preserving the original files within this directory, then copy both the libGLES_android.so and efg.cfg files to your sdcard in case you want to manually reverse the changes if you need to for some reason (as time goes on less and less apps should have any compatibility issues and I have none with the 176 apps I have installed). Since you made a NANDROID as well you could always restore from there as well if needed lol.
1. First, Rename the libGLES_android.so file to libGLES_android.so.bak, or simply delete it if you did the precautionary steps to preserve the original.
2. Next, open the egl.cfg file in a text editor. There should be three lines (the last being just a blank line...IT IS IMORTANT to make sure there is at least one blank line at the end of the file... Just as if you were editing build properties or other configuration files). This is what it should contain:
0 0 android
0 1 POWERVR_SGX540_120
<representation of blank line>
What we want to do is stop Android from processing the first line. You could either comment it out such as:
#0 0 android
0 1 POWERVR_SGX540_120
<representation of blank line>
OR again, if you preserved the original files, then you can simply delete that first line that has "0 0 android" in it.
Save your changes and close out if your file explorer and now reboot your phone.
After rebooting your phone again, it will have no choice but to use GPU rendering as we've removed the Android OS from accelerating anything.
And yes, I there is also a build prop edit, and but it only does the same thing as checking the setting under developer tools so I won't go there as it's simply redundant. I also could have simplified this quite a bit but wanted to make sure you are aware of the two methods of restoring this back to stock if desired (restoring your NANDROID or copying the backup files you made if you made them back from your sdcard and back into the /system/lib/egl directory)... AND wanted to point out that if you make changes to or create any configuration file and do not leave at least one blank line at the end then the previous line will not be processed, meaning in this case it would be the same as removing both the first two visible lines. This would leave Android with no references to OpenGL rendering as far as I know so could probably have nasty consequences (or maybe none.. I haven't tested it, but you get the idea).
Post your results back here...as I'm curious to see if anybody else can tell the difference afterwards. If you have an app incompatibility name the app (or if a LOT don't worry lol). I know Quickpic and Picsay Pro both mention NOT forcing GPU rendering but I haven't ran into any issues with either. I also haven't had a game I couldn't play either, but then again I normally only play games and install apps from quality developers so might not have installed the apps you guys are using to cause issues. That's why I'd like to know of a few so I could test them out using this method.
Similar threads
Trending Posts
-
-
Question Easy way to tell if bootloader can be unlocked?
- Started by littlebigman
- Replies: 0
-
-
There should be an affordable folding phone with mid range chipset/camera/screen
- Started by onetimeuserpost
- Replies: 0
-
Facebook
Twitter
Instagram