[Tweaks][su.d][build.prop] Thermal Throttling solution and more

Maxissc · Aug 14, 2018

Hi Snapdragon S7 users!

As we know we have a locked bootloader, and rooting includes heavy thermal throttling and strange frequency managment done by the system automatically (try to change max/min freq and you will se how it resists). Also to suffer a slower system (apps take longer to open/multitask), And a higher battery consumption (kernel organises processes strangely and big cpu is always under moderate-high load)
i have been searching all over xda (and many other forums) to get to the solution. And this is how far i could get:

Warning
Use this at your own risk!
su.d scripts will break safety net

Thanks to:
@xFirefly93 and his [MOD] Pixel (XL) Unified Kernel(s) Tuning Script (v1.3)
@Zola III
@TheDevelopper
@Craz Basics
Xperia XZ forum
OnePlus 3/3T forums
Pixel XL forum

su.d/init.d

build.prop

Dalvik solution

I'll keep this simple

Most important pages:

Configuring ART

Optimize android rutime

GoogleSource: Configuring ART

Eng builds different things

More eng builds different things, and stock values

Google Pixel default values

[MODULE][SYSTEM/LESS] ART Optimization v2.0 [DISCONTINUED]

Conclusions:

Our eng kernel has different values for certain dalvik things which ruins the "smooth android experience" (eng kernels are not meant for normal use). Hopefully most of them can be changed (fixed) into normal/stock values

The whole dalvik cache creation is really complex (and i barely know chunks of it), but to summarise It uses profiles which are a versus of "space utilization vs performance" more speed = less space available and vice versa (there are exceptions of course)

After testing with an exynos s7 besides my snapdragon i saw that exynos dalvik-cache folder was like 1gb big in stock conditions (and the phone was basically factory resetted), whereas snapdragon's folder was 300mb or so (with more than 100 aps installed). After applying the tweaks to exynos variant, dalvik folder went to like 1,2gb. After restoring ~100 apps on exynos dalvik is 1,8gb

Applying this tweaks could lead to (after dalvik-cache gets completely rebuilt):

Apps opening faster (they have more "parts" optimized)

Less cpu cycles used (apps have more "parts" optimized, so no need to waste cpu on doing that every cold launch)

Less battery consumption (above reasons)

Less internal space available (Dalvik cache will get bigger)

Longer first boot (A LOT LONGER) only first after deleting dalvik. Then it will be almost like before applying patch until dalvik gets completely rebuilt.

Some battery consumption increase until dalvik gets completely rebuilt (it's built while phone is booting, idle or charging)

After applying this tweak and deleting dalvik cache next boot will take A LOT LONGER. It's not a bootloop, i can ensure you, just wait. (like 20min)

How to install

Since values were not applying using setprop, i think it's better to add the values inside the build.prop (if someone has a better idea please tell me)

Make build.prop backup

Add values to build.prop

Leave one blank line at the end, like this:

battery.capcacity=3600
improve.performance=true
Last.buildprop.line=1
'empty space'

Click to expand...

Click to collapse

Delete dalvik-cache

Delete what is inside /data/dalvik-cache/
or

wipe dalvik-cache through Flashfire

Reboot (and go make a sandwich as it will take some time)

Click to expand...

Click to collapse

Dalvik takes time to rebuild, so wait some time (a couple of hours of device idle, charging if possible). I suggest you to do this at night some time before going to sleep: follow installation steps, check dalvik folder size and go to sleep (you can take screenshots to keep trace). at the next day check again if it has gain some size, reboot the phone, and use it normally. That night check again dalvik size. As soon as you see it stopped growing you can "document" your feelings with the configuration

Values

pm.dexopt.boot=verify
pm.dexopt.first-boot=quicken
pm.dexopt.bg-dexopt=speed
dalvik.vm.image-dex2oat-filter=speed
dalvik.vm.dex2oat-filter=speed
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.dex2oat-flags=--compiler-filter=speed
dalvik.vm.dex2oat-flags=--compiler-backend=optimizing

Click to expand...

Click to collapse

Click to expand...

Click to collapse

Extra build.prop tweaks

Here are some more build.prop values i found and im using right now. You can add them under dalvik solution ones if you like

boot.fps=30
shutdown.fps=30
ro.secure=1
ro.debuggable=0
persist.sys.scrollingcache=4
sys.config.samp_spcm_enable=false
sys.config.samp_enable=false
ro.config.fha_enable=true
ro.sys.fw.use_trim_settings=false

Click to expand...

Click to collapse

Click to expand...

Click to collapse

Extra

Rendering Solution

We know gpu is better than cpu at graphic rendering

In the old times a file named egl.cfg existed at lib/gles | lib/egl. That file contained the name of the libraries which would be used to render the screen (Phone and external). Some users modified the file in order to force gpu rendering always. This basically made phones smoother (info HERE)

Many people claimed that using gpu rendering only would increase battery consumption, whereas others said the opposite

We dont have egl.cfg, so i investigated and it results that since oreo the EGL loader doesn't need a config file to "know" which libraries to load, it detects the libraries and loads them automatically. So deleting (or renaming) libGLES_android.so makes the EGL loader unable to detect software rendering libraries and stick with only hardware ones, thus disabling cpu rendering List of commits

As far as i've tested, disabling cpu rendering made the device perform smoother (easily noticeable, specially just after a reboot). I didn't notice any big difference with battery (it may be lasting a little longer though)

How to

Rename (or delete) "libGLES_android.so" to "libGLES_android.bak" and set 444 permissions. . The file is at /system/lib/egl and /system/lib64/egl

Reboot

Click to expand...

Click to collapse

Apps Solution

Unlike the rest of solutions, this is not a script. Here i will tell you two group of apps i disabled, and made a LOT of difference in terms of snappiness
Short tuto:

1 ) in titanium backup search for 'qualcomm' with system/defrosted filter
2 ) freeze all
3 ) do the same but searching 'knox'
4 ) delete frozen apps data
5 ) reboot

Long tuto:

1 ) Download Titanium backup
2 ) open and go to 'backup/restore' tab
3 ) 'click to edit filters' and select type 'system', temperature 'defrosted'. the rest in 'all'
4 ) apply filter
5 ) click the magnifying glass and type 'qualcomm'
6 ) tap the paper with a tick
7 ) go to 'freeze/defrost' and tap 'run' in the first option "freeze all user & system...."
8 ) select all and tap the tick
9 ) repeat from step 5 but instead of qualcomm type 'knox'
10 ) go to 'backup/restore' tab
11 ) 'click to edit filters' and select type 'system', temperature 'frozen'. the rest in 'all'
12 ) tap the paper with a tick
13 ) go to 'manipulate data' and tap 'run' in the second option "wipe data for user & system apps"
14 ) select all and tap the tick
15 ) reboot

I will leave you also attached some screenshots of the apps i have frozen, so you can be sure they don't cause bootloops in case you wonder that. If you froze/disable something and suddenly something stops working (for example: bluetooth doesnt turn on) just defrost/enable it again and you should be fine

Click to expand...

Click to collapse

Solution Installer

If you want to Uninstall

Changelog

Archangel · Aug 19, 2018

Has anyone tried this and noticed any improvement? What about heat issues?

C64assembly · Aug 21, 2018

Archangel said:
Has anyone tried this and noticed any improvement? What about heat issues?

I have! I have noticed my device is much more snappy and I do notice an improvement in audio. I have a s7 edge and it is running cool.

Archangel · Aug 21, 2018

I ran it for a day or so and it seemed to make mine run hotter,,,I will try it again and see

C64assembly said:
I have! I have noticed my device is much more snappy and I do notice an improvement in audio. I have a s7 edge and it is running cool.

Maxissc · Aug 22, 2018

Archangel said:
I ran it for a day or so and it seemed to make mine run hotter,,,I will try it again and see

It will run hotter. Anyways i couldn't make cpu surpass 82C/180F, and i think it's really worth the benefit. I think samsung's eng kernel throttling wasn't totally polished, because some degrees ahead device stops getting hotter (unless during a heavy task), apps opening/switching becomes noticeably faster and scrolling lag decreases

I need to do some more research about how thermal throttling kicks in (eng kernel is weird) because i have plans and new ideas for an update but im not having my phone in hands until next week. Im thinking of wether release all at once or make it in 2 or 3 simpler updates

Maxissc · Aug 23, 2018

Reorganized post, added dalvik tweaks, redone all the scripts.
I suggest anyone who is using this uninstall and install new versions

gwilly3301 · Aug 24, 2018

I do not know if you're aware but Im pretty sure installing these and rebooting breaks safetynet! I had signed out of snapchat a day after installing these and tried to sign back in and i got the dialog you get if you are rooted and snap detects safetynet is broken, I then went an uninstalled the files from the su.d, rebooted and i was able to log in again, might want to add to OP

!

Maxissc · Aug 24, 2018

gwilly3301 said:
I do not know if you're aware but Im pretty sure installing these and rebooting breaks safetynet! I had signed out of snapchat a day after installing these and tried to sign back in and i got the dialog you get if you are rooted and snap detects safetynet is broken, I then went an uninstalled the files from the su.d, rebooted and i was able to log in again, might want to add to OP !

oh, thank you. Since don't use snapchat, and none app has given me problems, i didn't realise it. added to op :good:
Are build.prop lines working for you without breaking safety net?

gwilly3301 · Aug 24, 2018

Maxissc said:
oh, thank you. Since don't use snapchat, and none app has given me problems, i didn't realise it. added to op :good:
Are build.prop lines working for you without breaking safety net?

Build.prop lines should be fine, they won't break safetynet. As that's what apps like L-Speed modify are lines in the build.prop and it doesn't cause any problems

gwilly3301 · Sep 3, 2018

Maxissc said:
Hi S7 users!

As we know we have a locked bootloader, and rooting includes heavy thermal throttling and strange frequency managment done by the system automatically (try to change max/min freq and you will se how it resists). Also to suffer a slower system (apps take longer to open/multitask), And a higher battery consumption (kernel organises processes strangely and big cpu is always under moderate-high load)
i have been searching all over xda (and many other forums) to get to the solution. And this is how far i could get:

Warning
Use this at your own risk!
su.d scripts will break safety net

Thermal throttling solution

~~CPU Solution~~ Not finished, only touchboost tweaks for now

DAC's high performance mode

Installation

Dalvik solution

If you want to Uninstall

Have you had anymore development on these? Running these along with my flashing stock BL tweak has been very helpful

Maxissc · Sep 3, 2018

gwilly3301 said:
Have you had anymore development on these? Running these along with my flashing stock BL tweak has been very helpful

Yes, im currently testing 2 configs to decide which is better. Then i'll finish with cpu governor tunables and update op

gwilly3301 · Sep 3, 2018

Maxissc said:
Yes, im currently testing 2 configs to decide which is better. Then i'll finish with cpu governor tunables and update op

Awesome, thanks for the update! Don't mean to nag

Maxissc · Sep 5, 2018

UPDATE V2

Reworked Thermal solution
Added cpu tunables tweaks (at Cpu Solution)
Deleted some build.prop lines (also there aren't test values any more)

gwilly3301 · Sep 6, 2018

Maxissc said:
UPDATE V2

Reworked Thermal solution

Added cpu tunables tweaks (at Cpu Solution)

Deleted some build.prop lines (also there aren't test values any more)

Awesome, trying now! Will let you know how it runs!

---------- Post added at 11:39 PM ---------- Previous post was at 11:15 PM ----------

Maxissc said:
Hi S7 users!

As we know we have a locked bootloader, and rooting includes heavy thermal throttling and strange frequency managment done by the system automatically (try to change max/min freq and you will se how it resists). Also to suffer a slower system (apps take longer to open/multitask), And a higher battery consumption (kernel organises processes strangely and big cpu is always under moderate-high load)
i have been searching all over xda (and many other forums) to get to the solution. And this is how far i could get:

Warning
Use this at your own risk!
su.d scripts will break safety net

Thermal throttling solution

CPU Solution

DAC's high performance mode

Installation

Dalvik solution

If you want to Uninstall

Does Dalvik Solution.txt go into /su.d as well?

Maxissc · Sep 6, 2018

gwilly3301 said:
Awesome, trying now! Will let you know how it runs!

---------- Post added at 11:39 PM ---------- Previous post was at 11:15 PM ----------

Does Dalvik Solution.txt go into /su.d as well?

no, i'ts just a txt you can use to copy build.prop tweaks more easily.
about the .sh tell me if you have the logs at /data because i wasn't having them (neither the scripts running) until i deleted and pressed enter at every line of the files (i dont understand why that fixed the issue)

Maxissc · Sep 6, 2018

UPDATE V3

Reupdated V2 with scripts working correctly now

gwilly3301 · Sep 6, 2018

Maxissc said:
no, i'ts just a txt you can use to copy build.prop tweaks more easily.
about the .sh tell me if you have the logs at /data because i wasn't having them (neither the scripts running) until i deleted and pressed enter at every line of the files (i dont understand why that fixed the issue)

No, no logs. Does that mean scripts aren't running then?

Maxissc · Sep 6, 2018

gwilly3301 said:
No, no logs. Does that mean scripts aren't running then?

yes. please try with v3 i just uploaded. im sure they are working fine now

gwilly3301 · Sep 6, 2018

Maxissc said:
UPDATE V3

Reupdated V2 with scripts working correctly now

Should I re-download? Also with the, .txt file, I need to copy what's in there to my build.prop or do the scripts already do that?

---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------

Maxissc said:
yes. please try with v3 i just uploaded. im sure they are working fine now

Do I need to clear dalvik again?

Maxissc · Sep 6, 2018

gwilly3301 said:
Should I re-download? Also with the, .txt file, I need to copy what's in there to my build.prop or do the scripts already do that?

---------- Post added at 11:55 PM ---------- Previous post was at 11:54 PM ----------

Do I need to clear dalvik again?

redownload, delete previous files (from v2) at su.d, and copy new ones and give them 777 permission (all rwx). add .txt lines at the end of build.prop (remember to leave a blank line at the end), delete dalvik cache and reboot. it will take a while to boot after deleting dalvik (5-10min or so)

[Tweaks][su.d][build.prop] Thermal Throttling solution and more

Senior Member

Attachments

Inactive Recognized Themer

Senior Member

Inactive Recognized Themer

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts