Does anybody know if the GPU settings under development settings are essentially the same as some build.prop edits? For example:
In Developer Settings "Force GPU Rendering" forces GPU for 2d drawing. Is that essentially the same as adding ""debug.egl.hw=1 or debug.sf.hw=1" to your build.prop? Also if anybody can give me a technical explanation for the following development settings and build.prop edits (if they are even coded in KitKat) I'd greatly appreciate it.
Developer Settings: ""Force GPU Rendering", "Force 4x MSAA", and "Disable HW Overlays"
build.prop mods that may be similar or complete non sense at this point: "debug.composition.type=gpu", "debug.performance.tuning=1", "debug.egl.hw=1", "debug.sf.hw=1", "video.accelerate.hw=1"
Any solid advice would be appreciated.
Related
In my never ending quest to tweak my HOS to the max I stumbled upon this thread. It appears they have an adreno_config file to adjust the settings of their GPU. I was wondering if anyone knew if there is such a file buried in our device somewhere, or other ways to configure the defaults.
Thanks in advance
With the bricked kernel and kernel tuner you can OC the GPU (3D) to 520Mhz.
Hi Everyone,
Currently, our /system/build.prop file has the debug.composition.type value set to dyn. I've changed this to gpu and it seems to have increased UI performance, particularly for the transition animations.
Sources online indicate that this may be equivalent to checking "Disable hardware overlays" in Developer options -- the setting in Developer options does not persist after a reboot, whereas a build.prop edit does.
Please test if you have a chance and post back with results if you do.
Thanks.
The option still remains in dev options, and I always check it. But Idk if it's even necessary anymore.
Sent from Tapatalk on my Verizon HTC One M8.
ROM: ViperOne 2.4.0
Kernel: Lunar Kernel 4.4.3
Clock Speed: Overclocked to 2457MHz
Voltage: Undervolted
Governor: Wheatley
bump
Sent from Tapatalk on my Verizon HTC One M8.
ROM: ViperOne 2.4.0
Kernel: Lunar Kernel 4.4.3
Clock Speed: Overclocked to 2457MHz
Voltage: Undervolted
Governor: Wheatley
When GPU rendering was first added, it was very unreliable. Sometimes it would be slower than software rendering, and there were some kinds of GUIs that it just couldn't work with. For this reason, it was up to the app developer to test their app with GPU rendering, and set an option in the app's manifest (the same place that it declares its permissions) to enable GPU rendering for that app. The option was mainly to make it easier for developers to test the effect of GPU rendering on their app. This makes sense because:
most users don't know or care about what GPU rendering is, and don't know whether it should be on or off for any given app; and
the setting really needs to be per-app, not device-wide, because some apps just wouldn't work with GPU rendering turned on.
After further development, when 4.0 came along, GPU rendering got more reliable, so it became the default for all apps: it's now up to the developer to explicitly disable GPU rendering if it causes a problem in their app. (That's very rare now.) The "Force GPU rendering" option is vestigial and rarely used even by developers now, because it's already the default.
Source: http://android.stackexchange.com/qu...ndering-disabled-by-default-developer-options
Hope this helps, I was wondering this too.
As I don't have any idea about which option to select ( and their is no option to leave it), if someone knows which Gpu optimisation option to apply or has any idea of it, it would be helpful.
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
BEFORE WE START...
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
De-bloat your ROM using this method
This will free +700mb of storage and there will be more RAM available for other apps to use, also I've noticed this helps a bit with the memory management
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
DEVELOPER SETTINGS
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
Enable developer settings, go to developer settings and enter the system performance tab
Disable trace debuggable applications, click on categories and disable every single one
This will disable (some) logging and it will improve battery life a bit as well as free up some ram
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
KERNEL ADIUTOR SETTINGS
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
CPU:
tbh if you have a stock kernel I wouldn't bother changing CPU settings, I haven't found the voltages for each frequency for the sd630. When I find them I will improve this part
GPU:
same thing as the CPU part
Low Memory Killer:
if you are an average user set this to agressive, otherwise set it to very aggressive
Virtual Memory
if you are an average user set the "swappiness" to "65", if you are an hardcore user set it to "70" or "75"
*experimental* set the "vfs_cache_pressure" to "95" if you set the "swappiness" to "75"
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
OTHER SETTINGS
●▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬●
Go to Magisk settings and touch on the "Systemless Hosts" button, reboot and then check is the "Systemless Hosts" module properly installed
After that download AdAway and install the latest ad blocking hosts file
And if you reallyyy want a snappy phone go to developers settings and set all the animations to 0.5x
That's it, this post will be updated over time so keep an eye on it
PS: I may need some testers so reach out to me if you are intrested
Changelog
28.11.2019 - updated virtual memory values, simplified memory killer settings, added a way to disable logging