Related
Ok I’m sure by now most have read the previous Op about losing half my Teeth, all in the back thank the Gods but still can’t wait until I get the fakes bolted in. Sure that will also be an awesome experience, forgot to add that I can’t take pain killers either. Anyhow I originally started working on this Mod for personal use and a means of keeping sanity. Because it ended up working out much better than anticipated I decided to share the script. Since then I have made some changes as I first have learned a little bit more and second because it has expanded beyond its original intention of being made specifically for CM7 and optimized in some areas around my own personal device configuration. Because of this I just decided to kind of give things a Reboot.
What does this Mod do you may ask? In short it just makes everything a little better and snappier! How does it go about doing these things you may ask?
In Short,
IPV4 Internet speed Tweaks,
Chainfire Touchscreen Tweaks,
Increased Cache Sizes,
Defrag Database Files On Boot,
Remove Logger,
Running fewer background Processes,
Set’s Higher Priority for App's like Phone, Launcher, Contacts, SMS, SystemUI & Camera, (Loopy Smoothness)
Two Sweet Edition Changes (04.28.2012)
Linux Laptop Tweaks for Battery Life
Ondemand, Interactive & SmartassV2 Govenor Tweaks
APK Zipalign (Already performed by most Roms but included for the few that do not)
Many more along the same lines.
Again just so it’s clear, I did not develop any of these Tweaks on my own. If any credit should go my way it would be for looking around various websites and inside ROMs for other devices, finding things that look interesting, testing on the Triumph for effectiveness, making minor adjustments if needed and then collecting them into a method that is easy to apply. This should work with just about any Rom with Init.d Support. The easiest way of determining if your Rom has Init.d support would probably be to look at the below directions. If you find an Init.d folder in the spot they say you should then your Rom supports Init.d. It would still be recommended to keep a backup handy as I am not responsible for any damage caused to anything you own.
.
Instructions (Busybox must be installed, if not, download from the Market)
1, Download 108 Triumph Script.
108 Triumph Script (04.22.2012)
http://www.mediafire.com/file/l8x4pyt1u3wfjck/108TriumphScript
108 Triumph Script Two Sweet Edition (04.28.2012)
http://www.mediafire.com/file/77cd8dzdgzmsar1/108TriumphScript2sweet
If for some reason and I noticed this with Dolphin, .txt has been added to the end of the file name after downloading .text will need to be removed or the Tweaks will not be applied. So far I have only seen this happen with Dolphin but no dots should appear in the file name and should be removed.
2, Place file on your SD-card. (USB Dropbox, doesn't matter how)
3, Use Root Explorer or Root Browser Free and move the file into system/etc/init.d folder. (Remember to hit the tab that makes the folder Read/Write as Read Only is the default setting for most File Explorers.)
Root Browser Free if you need a free File Explorer.
http://dl.dropbox.com/u/29969403/rootbrowser.apk
4, Give the file full Permissions.
5, Reboot! (Will take a bit longer to boot and will appear to be held up on the Motorola Logo for a bit. This is nothing to worry about, the script is running and the Tweaks are being applied.)
Clear both Caches in recovery if you have any issues. Should not be needed but have noticed that sometimes Root System Apps like SD-Booster or Auto-Killer when installed before applying the script will restore pre-script values when the restore default settings option in the App is used.
To remove these Tweaks simply delete the file and reboot. To update the file use the file explorer to delete the old version after placing the new version in the init.d folder.
Going forwarded at least for the time being the Build.prop Tweaks can be applied by using the optional Hollyname Script. This was done because to apply these Tweaks correctly as part of the 108 Script with my current knowledge would do either one of two things, permanently add these Tweaks to the Build.prop or make the script Rom specific. Because I’m trying to stay away from having the Mod make any permanent adjustment or have the willingness or time for keeping up with every version of every Rom until I figure a way around the issue they can still be easily applied without making any changes to the Build.prop by following the following.
Additional Build.Prop Tweaks (Recommended)
1, Download Hollyname Build.Prop Tweaks Script and place on SD-Card.
Hollyname Build.prop Tweaks (04.22.2012)
http://www.mediafire.com/file/9f843s9j47czw4z/HollynameBPTweaks
Hollyname Build.prop Tweaks Two Sweet Edition (04.28.2012)
http://www.mediafire.com/file/gzg44q7hho1q8qx/HollynameBPTweaks2sweet
2, Install Script Manager Free from the market.
3, Open Script manager and select the script.
4, Select SU, Boot and then save.
5, Reboot! (All Build.prop Tweaks will now be applied during each boot unless un-selecting the option in script manager or deleting the script from the SD-Card. This will not make any actual changes to your Build.prop. Nor will it effect any properties associated with Market Access.
You Can run "getprop" in either ADB or a Terminal to confirm all current property values if not sure everything was done correctly. If so you should now see the following included among the listed properties,
debug.sf.hw 1
dalvik.vm.heapsize 48
persist.sys.ui.hw 1
ro.max.fling_velocity 12000
ro.min.fling_velocity 8000
ro.ril.disable.power.collapse 1
pm.sleep_mode 1
windowsmgr.max_events_per_sec 150
ro.media.enc.jpeg.quality 100
ro.media.dec.jpeg.memcap 8000000
ro.media.enc.hprof.vid.bps 8000000
media.stagefright.enable-player true
media.stagefright.enable-meta true
media.stagefright.enable-scan true
media.stagefright.enable-http true
net.tcp.buffersize.default 6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.wifi 524288,1048576,2097152,524288,1048576,2097152
net.tcp.buffersize.umts 6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.gprs 6144,87380,1048576,6144,87380,524288
net.tcp.buffersize.edge 6144,87380,524288,6144,16384,262144
net.tcp.buffersize.evdo_b 4096,87380,256960,4096,16384,256960
ro.kernel.android.checkjni 0
ro.kernel.checkjni 0
debug.performance.tuning 1
video.accelerate.hw 1
dalvik.vm.dexopt-flags v=n,o=v
persist.adb.notify 0
wifi.supplicant_scan_interval 180
ro.config.disable_hw_accel false
ring.delay 0
All Tweaks And Mods Are Not Devloped By Me So The Creadit Goes To The Devlopers....
Warning:-All These Tweaks And Mods Are Tested But Try On Your Own Risk....
Make A Backup Of Your Rom Before Trying Anything...
(•1) Get more RAM and faster responses by disabling verify-bytecode!
AS WITH ANY MODDING PROCEDURE FOR YOUR PHONE, THIS GUIDE ALSO COMES WITH NO WARRANTY. I HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF FOLLOWING THIS GUIDE. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING.
This is not useful in odexed ROMs & devices with 1GB or more RAM. However, this will give a performance boost in deodexed ROMs as much as odexing system & data apps. This is an alternative for odexing. It's not that you can't apply this tweak on an odexed ROM but rather, it's useless to do so.
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=v
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
2) Add these to the /data/local.prop or build.prop.
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=v
(Copy local.prop or build.prop to SD and edit them. Copy back afterwards. If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already, please modify them as above. Also type following in adb shell or terminal emulator.
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
Advantages:More free RAM.
Faster launch for system & user apps during the second launch.
Gives as much as of a performance boost as ODEX without odexing. Themer friendly.
Smoother app switching.
Disadvantages:Might break some apps.
(•2) Seeder 2.0.0 entropy generator to provide significant lag reduction
Use Seeder For Lag Reduction
Here:- http://forum.xda-developers.com/showthread.php?t=1987032
(•3) One click ODEXing a ROM for more RAM and better speed
Here's an alternative way to gain more RAM and performance without odexing.
Get more RAM and faster responses by disabling verify-bytecode!
This process will usually give just as much as performance boost as odexing SYSTEM and USER app.
AS WITH ANY MODDING PROCEDURE/SCRIPTS FOR YOUR PHONE, THIS SCIPT ALSO COMES WITH NO WARRANTY. AUTHOR HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF RUNNING THIS SCRIPT. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING. MAKE SURE YOU HAVE AT LEAST 15% FREE ON /SYSTEM, THIS IS IMPORTANT BECAUSE IF YOU RUN OUT OF SPACE THINGS WILL GO BADLY WRONG..
Requires busybox.
If your system partition is almost full, have a look at http://forum.xda-developers.com/showthread.php?t=734236.
This script will *attempt* to odex all apks found at /system/app. Theming would be impossible once the ROM is odexed. Themes applied at the time of odexing will be preserved. If you plan on applying a theme, apply it before odexing. If you want to theme after odexing, you must deodex the ROM before theming. If you change themes often, odexing is not for you.
Quick Instructions for Windows:
Connect the phone with USB cable and enable USB debugging. (No wireless or Android Terminal shell)
Put the phone in airplane mode.
Download and extract the attached file and run odex.bat
Instructions for advanced users:
This attachment contains a folder called odex. Push that folder to data and set the permission of odex.sh to 4755. Mount system as r/w(could be done via adb remount system). Next, execute odex.sh. All of this should be done via USB using ADB shell. Do not use wireless adb or Android Terminal.
Advantages:
More free space in system partition.
Faster booting.
More free RAM(I was able to gain 20-30MB.)
Faster access to system apps.
Disadvantages:
Cannot be themed after odexing.
APK tweaks cannot be applied.
Might break some of the non-AOSP system apps such as Root Explorer if they are installed as system app.
Acknowledgments:
Only the odex.bat was created by me. Similar projects were done in past but most of the downloads are broken. So, I collected together different stuff from different places to put together this package.
adb.exe is from the RATC batch ROOT.
adb dlls are from Android SDK
odex.sh is from Paul O Brian from MoDaCo (pastebin.com/EZLWUdea)
zip, zipalign and dexopt-wrapper are from XDA (http://forum.xda-developers.com/showthread.php?t=734236)
(•4) V6 SuperCharger +DIE-HARD Launcher
This One Is The Beat And I Think Nothing Can Beat It Takes Your Phone Flying....
What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind
NO LAUNCHER REDRAWS, faster than ever, multitasking is better... why?
Because it works with the lowmemorykiller and letting it work the way it's meant to work.
Also, because of the rearrangement, it works the same on all roms!
Here Is The Link:- http://forum.xda-developers.com/showthread.php?t=991276
(•5) Entropy Lag Reduce/DNS Speedup/Tether boost/Clean Adblock {CROSSBREESER}
What CrossBreeder Does....
1. It's a big new feature, removal of DNS lag . A lot of the lag in a lot of apps, apart from the GUI lag, is due to slow DNS querying, specially on the mobile network.
CrossBreeder now runs a caching, parallelising DNS client on the device. So now most of your DNS queries will be served from the cache and if not found, the query will be sent in in round robin fashion to multiple DNS servers including Google DNS, OpenDNS and your home router and the reply will be served to you, hot.
This speeds up network access and networked apps, like Browsers of course, and Tapatalk, Gmail and thousands of others drastically. And removes a lot of the lag where it was due to DNS querying. This will not increase your network or download speed but pages will load much faster.
This will future proof your devices as more and more apps start using HTML5 and/or reside completely as web pages or the like.
CrossBreeder now boosts your tethering connection. Client devices to your device will take advantage of the new DNS. Hence their usage is also improved! In many cases this update might even fix a broken tethering feature on your phone. So if your ROM doesn't have a working tethering support, you an try and install this update. It might magically start working!
Here Is The Link With Description:- http://forum.xda-developers.com/showthread.php?t=2113150
(•6)Apps For Tweaks And All
Pimp My ROM - The only app that implements tweaks I can't do on my own and applies them well if you take the time to apply the right tweaks. You'll learn about PMR tweaks later.
Quadrant/Nenamark2 - Standard benchmarking and stress testing.
Android Tuner Pro - I don't apply any tweaks through AT, in fact I have most of ATs features disabled or hidden (my favourite aspect of AT is its customizability). However, this is the app I use most frequently throughout the tweaking and testing process. AT has incredible system monitoring features. AT allows me to actually collect data so I can objectively measure a tweaks impact on performance. It also has a great root terminal shell and script manager.
AntTek Explorer- Root file manager that is great for managing scripts. Has a built in text editor, great customizable UI, low footprint, and makes the process of enabling init.d scripts easier than other file managers. It also reminds me of nautilus and other linux file managers, which is a wonderful thing.
SDMaid Pro- Great for system cleaning and app management. During testing, whether deliberately or unintentionally, I crash my system a lot (my cpu hates me). SDMaid allows me to clean up junk system files after crashes. On average a system crash generates a couple mb of junk files (logs, etc) that I have no use for. SDMaid also clears app caches without clearing any settings or other data. I know your not supposed clear caches all the time but after all the crashes I put my system through during testing it is useful every once in a while.
LagFix Premium - Another app thats great for maintaining sdcard performance if your constantly wiping, restoring, and flashing.
And If You Are Newbie Try To Understand It.
I Will Be Updating This Topics For Future.....
If You Like It Hit The Thanks Button
Any Ideas And Request Would Be Great....
And Pls Reply Don't Quote....
Re: [Guide] (How To Make Most Of Your Phone Ram And Cpu)
Pls Post Suggestions And Ideas To Keep This Thread Updated....
Sent from my LG-E400 using xda premium
Re: [Guide] (How To Make Most Of Your Phone Ram And Cpu)
You should add the Crossbreeder script here
Sent from my A9 using Tapatalk 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The best for your device
Description:
Hello guys, this is my newest work for all android devices, is a simple engine focused on a good performance and battery saving, I know, it does a great job, but I did my best and I guarantee you will enjoy, you will not even see a LAG on your device.
Unlike many engines out there, the MaliveBooster is not based on AdrenalineEngine, or anywhere else, I created it from scratch to make the best of my device, she had several contributions of many of my friends who encouraged me to create it.
Features:
✔ Increase touchscreen sensitivity
✔ Less battery consumption
✔ Small and simple SD-Card read ahead script, configured to work with "4096 KB"
✔ Wireless Speed Tweaks
✔ Custom Sysctl (made by myself)
✔ Optimized overall performance
✔ Photo and video recording quality considerably increased
✔ New script to compress 3G/WiFi data, resulting in better network performance
✔ CWM/TWRP/PhilZ Touch Flashable
✔ Custom Hosts
✔ Easy to uninstall
✔ Turns your mobile phone into an incredible Galaxy S5. (joke , haha)
**Do a backup before your try anything as usual !!!
Installation:
1.Delete all others ram scripts you have installed in "/system/etc/init.d"
2. Copy 'MaliveBooster' to your phone SD card
3. Reboot your phone to recovery mode
4. Mount /system
5. Flash MaliveBooster
6. Reboot your phone when finished installation
7. Done
==================================================
Downloads
MaliveBooster alpha 4.1
12115 Downloads and counting(thanks everybody who like and download my project)
V3 NEED NEW UNISTALLER, PLEASE, DOWNLOAD THE NEW ONE(DONT USE ON V4)
Unistaller
==================================================
Please, if you found a bug, tell me in the comments that I will fix, and please press THANKS instead of saying thank you, keep this topic clean.
Tested Device's:
Samsung Galaxy Note® 3
Xperia Z1
Galaxy Note
Oppo Find 5
HTC One X
Alcatel OneTouch S'Pop
iOcean X7S Elite
Aquaris 5 HD
Samsung Galaxy Note® II
Galaxy Tab Pro 8.4
Optimus L9
Blü Life Pure Mini
Moto G
Moto X
Galaxy S3 Mini i8190/L
Galaxy S3 i9300
Galaxy S4 i9505
Galaxt Tab 2 7
Galaxy Tab 3 7
Galaxy Ace 2 (I8160P)
Galaxy Pocket s5300
Galaxy Pocket Plus s5301
Galaxy Pocket Neo s5310
LG G2
LG Optimus L5
LG Optimus L3
Motorola Razr i (x86 hardware)
Xperia Mini Pro sk17a
Xperia Mini X10
Nexus 5
Nexus S
Changelog20140504 - Initial Release
20140601 - Release two
Add a cache cleaner
Fixed repeated commands
Added tweaks for DalvikVM
Added libncurses.so
Optimization of memory blocks
Script to set correct permissions to init.d folder
20140728 - Version tree
All tweaks malive.prop file will be installed directly into your build.prop, but before the installer will make a backup of build.prop for when you uninstall not leave any trace of the engine on your device
Script updated, new sysctl.conf, better compatibility with multiple devices
Engine divided into multiple files (I'm thinking that is not loading all scripts properly then it will be a test)
New file that compresses 3G/WiFi data, resulting in better network performance
Some minor changes
Init.d support patched on zip
20141128 - New version four with Open Source Project
Redone all engine from scratch, removed a lot of scripts
Fstrim script to "TRIM" all partitions(EXT4 only)
Script to remove caches from internal memory
Updated hosts
Updated script to install tweaks on build.prop
New Sysctl.conf totally redone for better performance, all init.d scripts is executed by sysctl now
Included my engine on Open Source project based on GPL 3, now you are free to use all parts from there
Warning
On sysctl.conf you will find some "test tweaks" , use by your own risk(for me, only placebo on tests)
Credits:
ImbaWind for BASE idea from Adrenaline Engine
Marilia de Oliveira <3 for motivation and ideas :victory:
Elerson Carvalho for continues help
Recommended mods that work seamlessly with MaliveBooster
(MoaAB) Mother of All AD-BLOCKING
[MOD] CrossBreeder - Lag-/Entropy+/DNS+/Tether+/Ads-/Censors-/.bit support!!
FAQs
what is the minimum version of android to use MaliveBooster?
A: Any version of android is 2.1 until 5.0, so you have working init.d to load part of the engine.
It works on Custom ROM? CyanogenMod, AOSP, AOKP, Omni, or stock ROM?
A: yes, it works on all ROM's.
I can put your script in my ROM?
A: If you want to publish the ROM, NOT, put a link to my tread, do not add my script in your rom, we plan to improvise this engine issue several updates and would be boring all the time you have to update your ROM because of some scripts then let separately as an add-on
What my engine is so good about? read these explanations and see how it works.
Ok, so what exactly is sysctl.conf?
The sysctl.conf is a configuration file for "sysctl" which is an interface for dynamically changing kernel parameters in the Linux OS. The configuration file contains the following elements, vm.min_free_kbytes, vm.dirty_ratio, vm.dirty_backgroud_ratio, vm.vfs_cache_pressure, vm.oom_kill_allocating_task. There are many other elements within the file, but we will be primarily focusing on these specifically (the vm prefix stands for virtual memory). The sysctl.conf file should be located in /etc (/system/etc) by default. To enable it you need your ROM to execute "sysctl -p" somewhere during the boot process (or shortly afterward). We will also be discussing how to enable it if it is not already done so. You can also run sysctl -p manually to enable it any time after the OS is started.
Now, let’s get down to what sysctl.conf does and how it works.
min free kbytes (vm.min_free_kbytes)
This is used to force the Linux VM to keep a minimum number of kilobytes free. The VM uses this number to compute a pages_min value for each lowmem zone in the system. Each lowmem zone gets a number of reserved free pages based proportionally on its size. Default is 2048kb.
dirty ratio (vm.dirty_ratio) and dirty background ratio (vm.dirty_background_ratio)
This controls how often the kernel writes data to "disk" (in our case the internal microSD system card, not the removable microSD card). When your apps write data to disk, Linux actually doesn't write the data out to the disk right away, it actually writes the stuff to system memory and the kernel handles when and how the data is actually going to be flushed to the disk. These values represent a percentage, the higher the percentage, the longer it waits to flush, the lower the percentage, the more often flushes will occur. Now remember, we are dealing with solid state storage, not the traditional disk platter and spindle. So we are actually able to delay flushes a little longer with solid state versus a traditional hard drive disk.
VFS Cache Pressure (vm.vfs_cache_pressure)
Now here is where it gets interesting! File system cache (dentry/inode) is really more important than the block cache above in dirty ratio and dirty background ratio, so we really want the kernel to use up much more of the RAM for file system cache, this will increas the performance of the system without sacrificing performance at the application level. The default value is 100, as a percentage, and what you want to do is lower the value to tell the kernel to favor the file system cache and not drop them aggressively.
oom allocating task (vm.oom_kill_allocating_task)(enable or disable, generally in Linux this value is either a "1" or a "0," representing as on or off.)
This enables or disables killing the OOM-triggering task in out-of-memory (oom) situations. If this is set to zero, or disabled, the OOM killer will scan through the entire task list and select a task based on heuristics to kill. This normally selects a rogue memory-hogging task that frees up a large amount of memory when killed. If this is set to non-zero, or enabled, the OOM killer simply kills the task that triggered the out-of-memory condition. This avoids the expensive task list scan, which can take mass amounts of time and "hang" or freeze the system.
block_dump (vm.block_dump)
This enables block I/O debugging when set to a nonzero value. If you want to find out which process caused the disk to spin up (see /proc/sys/vm/laptop_mode), you can gather information by setting the flag.
When this flag is set, Linux reports all disk read and write operations that take place, and all block dirtyings done to files. This makes it possible to debug why a disk needs to spin up, and to increase battery life even more. The output of block_dump is written to the kernel output, and it can be retrieved using "dmesg". When you use block_dump and your kernel logging level also includes kernel debugging messages, you probably want to turn off klogd, otherwise the output of block_dump will be logged, causing disk activity that is not normally there.
overcommit_memory (vm.overcommit_memory)
This controls overcommit of system memory, possibly allowing processes to allocate (but not use) more memory than is actually available.
0 - Heuristic overcommit handling. Obvious overcommits of address space are refused. Used for a typical system. It ensures a seriously wild allocation fails while allowing overcommit to reduce swap usage. root is allowed to allocate slighly more memory in this mode. This is the default.
1 - Always overcommit. Appropriate for some scientific applications.
2 - Don't overcommit. The total address space commit for the system is not permitted to exceed swap plus a configurable percentage (default is 50) of physical RAM. Depending on the percentage you use, in most situations this means a process will not be killed while attempting to use already-allocated memory but will receive errors on memory allocation as appropriate.
page-cluster (vm.page-cluster)
This controls the number of pages which are written to swap in a single attempt. The swap I/O size.
It is a logarithmic value - setting it to zero means "1 page", setting it to 1 means "2 pages", setting it to 2 means "4 pages", etc.
The default value is three (eight pages at a time). There may be some small benefits in tuning this to a different value if your workload is swap-intensive.
panic_on_oom (vm.panic_on_oom)
This enables or disables panic on out-of-memory feature. If this is set to 1, the kernel panics when out-of-memory happens. If this is set to 0, the kernel will kill some rogue process, by calling oom_kill().
Usually, oom_killer can kill rogue processes and system will survive. If you want to panic the system rather than killing rogue processes, set this to 1.
The default value is 0.
Panic is a system error that is detected by the kernel.
dirty_expire_centisecs (vm.dirty_expire_centisecs)
How old "dirty" data should be before the kernel considers it old enough to be written to disk. It is expressed in 100ths of a second.
dirty_writeback_centisecs (vm.dirty_writeback_centisecs)
This is the interval of when the writeback daemons periodically wake up and write "old" data out to disk. It is expressed in 100ths of a second.
APK Zipalign
zipalign is an archive alignment tool that provides important optimization to Android application (.apk) files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Specifically, it causes all uncompressed data within the .apk, such as images or raw files, to be aligned on 4-byte boundaries. This allows all portions to be accessed directly with mmap() even if they contain binary data with alignment restrictions. The benefit is a reduction in the amount of RAM consumed when running the application.
FPS Stabilizer
Lenarox clearly says it unlocks the normal FPs limit, so its doing NOTHING, on multiple devices I tested these commands remained stable without the FPS slown downs and loss of performance in the game
Sqlite optimizer
Faster access to contacts, messages, etc by removing blank pages from databases(.DB)
Ext4 File-Systems optimization & instant-mount
he name says it all, it optimizes the ext4 partition to mount faster, improved data access, etc...
SD Card Head Ahead cache
You might have heard about the term “readahead”. This is a command that sets the cache of the sdcard in kb/s.
The default value on android devices is “128″, so that’s a cache of 128kb, which is very small, then my script optimize reading speed sd card for 4096
Touchscreen sensitivity
I do not have much information on this, but it increases the sensibility of the screen
Battery save tweak
increased wifi scanning time for battery saving, handles battery better after disconnections, allows fast dormancy for better battery, deep sleep, and other little things
and other's random tweaks
Cool
Very good, keep your job! :good:
Let's see..
Sent from my SCH-I535 using Tapatalk
How to know if work?? And how to uninstall
Sent from my GT-I9100G using XDA Premium 4 mobile app
Is this compatible with KK?
Interesting but cant see uninstaller and instructions to check if it is properly installed, and can you explain a bit more every feature announced. Thanks and keep the good work.
Enviado desde mi bq Aquaris 5 HD
acuicultor said:
Interesting but cant see uninstaller and instructions to check if it is properly installed, and can you explain a bit more every feature announced. Thanks and keep the good work.
Enviado desde mi bq Aquaris 5 HD
Click to expand...
Click to collapse
I will make a unistaller soon, and explain more about my engine
tamingsarix said:
How to know if work?? And how to uninstall
Sent from my GT-I9100G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I will make a unistaller and show if worked
Babyhustle said:
Is this compatible with KK?
Click to expand...
Click to collapse
Its compatible with any Android version, i using on KK right now
Please put DNS on next version...now days DNS not work on 4.3 and 4.4..maybe u can do magic....
Sent from my GT-I9100G using XDA Premium 4 mobile app
Simple and effective mod. Thank you
Sent from my SGH-I317 using Tapatalk
Looks great I give it a try. BTW I think you need libncurses.so in lib folder for the touchscreen tweaks to work if I'm not wrong.
https://mega.co.nz/#!n14h3YRA!Gp37uP4NHej8d--jcJ2HVYGG-HgK0-OA6qsY-bwzDx0
Verstuurd van mijn GT-I9300
Is work with any cyanogenmod??
after installation and restart proved to the point of contact and responds only using two fingers. I do not know how to put it away. I have a samsung galaxy s i9000 rom 4.1.2 and Mackay
mgg said:
after installation and restart proved to the point of contact and responds only using two fingers. I do not know how to put it away. I have a samsung galaxy s i9000 rom 4.1.2 and Mackay
Click to expand...
Click to collapse
Same results with different mods, sounds like you are doing something wrong.
Enviado desde mi bq Aquaris 5 HD
I think so. installation is performed on my wife's phone and there is no problem.
Still waiting uninstaller script
Sent from my GT-I9100G using XDA Premium 4 mobile app
Reinstalling rom u helped me, but I think this rom can not install scripts. I tried vice performanses scripts and nothing. The same problem. Brother has installed the samsung s2 and everything ok.
mgg said:
Reinstalling rom u helped me, but I think this rom can not install scripts. I tried vice performanses scripts and nothing. The same problem. Brother has installed the samsung s2 and everything ok.
Click to expand...
Click to collapse
Sorry but i cant understand what you are trying to say. May your kernel dont have init.d support.
Enviado desde mi bq Aquaris 5 HD
se.nainstaloval I apologize again and I managed to finally get to the settings. and set trackpad. I do not know how to deactivate
sorry for the sudden disappearance, I'm already working on changes and improvisations on the engine, I will soon update the post and everything, for better understanding of what my engine will cause on your device :good:
Remember to have the screen turned ON while you apply the script!!!
Hi guys!
Today i want to share with you a script i specifically tailored for our 4C, to decrease high battery drain just by tuning parameters of the interactive governor.
As many of you know, on the Nexus 5X forum there is a huge post about different profiles created to achieve the same purpose, and almost all of them works with our device (personally tested)
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
I raccomed to read it!
One of them in particular was extremely good battery wise but i felt some lagginess here and there (talkin about HawkTail 1.2)
So i decided to make a script myself and share it with you, the idea behind it is to force the CPU to scale better with loads and making the Big cores in use more frequently by tuning some of the kernel parameters.
Plus we will have the GPU idling @ 180MhZ instead of 300MhZ (like in the Nexus 5x) and a switch to noop scheduler.
Performance wise and taking in example the latest stable ROM from Xiaomi.eu (8.0.5) we will have a decrease of about 5k point in Antutu (I'll attach two screenshots, the 71K was the result without tweaking, plus just by switching back to CFQ scheduler you'll get 2K points back but NOOP is more battery friendly)
So here you go, this is my script TAO.
Using it is pretty simple and you have a couple of options: [ROOT IS NEEDED]
Since it's a script, if your rom have INIT.D folder support, you can just move the file under /etc/Init.d and reboot the device. The script will make a log file under /sdcard/TAO.log that you can check if anything went wrong.
The second option, if your rom doesn't have Init.d folder support, just use Kernel Auditor and a text editor.
Open the downloaded file in a text editor, select all and copy the text.
Then open Kernel Auditor, and in the menu look for init.d, enable the "Emulate Init.d" and then click the "+" symbol. It will ask to add a name (let's set it to TAO for coherence), then OK. It will open a new window where we have to paste all the text previously copied, save it by pressing the icon on the top right. Now we can just reboot the device or click the newly created item and select execute.
Third option is to run it manually from terminal.
Plus, i'll add my Thermal-engine-8992.conf that you guys can use to change the thermal throttling values. Download it and replace it in /system/etc/ , set it with permission 644 and reboot.
This modded thermal will move up the limits, long story short, your device will continue to perform even if it gets hot.
Enjoy! & report back for feedback
Remember to have the screen turned ON while you apply the script!!!
P.S.
Files are zipped, extract them!!!
UPDATE
Minor update - use_sched_load set to 0 for both cores
Correction made for the log file
UPDATE 0.7
Since @solis_f is having some problem with the big cores, and this could be a common problem to many others too i've decided to add something in the script that will force the big core online so you should not have any more problem executing the script. Let me know
UPDATE 0.8 - Experimental
Updated Target_loads for both Little and Big cores.
Little core min freq. to 384 MhZ.
Input boost @ 787 MhZ instead of 600 MhZ.
hispeed_load disabled for both cores.
Updated values for UpMigrate.
Enabled core_ctl for big cluster:
With this update, you'll have your big cores Offline most of the time, but they will comes online when needed.
Yours perfd (/data/system/perfd/default_values) with this version have to look like this:
Code:
ihf;787200
iahd;38000
ighl;200
itl;39 460800:5 600000:62 672000:10 787200:81 864000:90 960000:99
gpu_default_pwrlvl;5
sst;33
smil;20
sminr;3
sitl;65
sum;66
sdm;54
cbmf;1525
cbhdr;90
cbhip;16
ihf0;787200
iahd0;38000
itl0;39 460800:5 600000:62 672000:10 787200:81 864000:90 960000:99
imst0;0
ighl0;200
imf0;0
itr0;30000
its0;-1
iiib0;1
intb0;0
ibd0;0
ihf4;1248000
iahd4;38000
itl4;53 768000:64 864000:72 960000:79 1248000:99
imst4;0
ighl4;200
imf4;20000
itr4;30000
its4;-1
iiib4;1
intb4;0
ibd4;0
P.P.S.
Over two hundred downloads, but not even half of you gives me feedback...
UPDATE 0.9
Sorry for the delay, many things to do IRL.
This version is what i'm using now, should be smoother then v0.8, hope you like it.
nice one, will try this
Did you try to run Antutu several times in a row, so we can see is the result of 66k almost constant. Since as we all know, results can degrade towards 44k because of overheating..
predragiPredrag said:
Did you try to run Antutu several times in a row, so we can see is the result of 66k almost constant. Since as we all know, results can degrade towards 44k because of overheating..
Click to expand...
Click to collapse
I did not, but degradation of score is dictated by the thermal config. That's why i modded that too, and pushed the standard limits...
Let me show you with an example:
Code:
[SS-SKIN-XO-THERM-PERF]
algo_type ss
sampling 250
sensor xo_therm_buf
device cluster1
set_point 43000
set_point_clr 37000
time_constant 0
device_max_limit 800000
This is taken from the original file, and it covers the big cluster... when it reach 43° celsius, the thermal throttling will limit the max frequency of the cluster to 800MhZ
Code:
[SS-SKIN-XO-THERM-PERF]
algo_type monitor
sampling 5000
sensor quiet_therm
thresholds 46000 48000 50000
thresholds_clr 44000 46000 48000
actions cluster1 cluster1 cluster1
action_info 1632000 1248000 960000
This is the same part but modified by me, i've added more step... as you can see thermal throttling for big cluster will work once the big cluster reach 46° and it will cut the max frequency to 1632MhZ, then at 48° 1248MhZ and at 50° at 960MhZ
The hot-plug, that put the cores offline, on the original file for the big cluster is marked at 42° for core 4 and 45° for core 5.
On my config file both cores will be hot-plugged once they reach 52°.
TL;DR if you use my thermal-engine conf file, you will get more consistent score on several runs.
Nice to hear that will try this when I have more time to play with my phone and report back.
Great work and thanks for sharing this
GoldGanja said:
Hi guys!
Today i want to share with you a script i specifically tailored for our 4C, to decrease high battery drain just by tuning parameters of the interactive governor.
As many of you know, on the Nexus 5X forum there is a huge post about different profiles created to achieve the same purpose, and almost all of them works with our device (personally tested)
[GUIDE] Advanced Interactive Governor Tweaks; Buttery smooth and insane battery life!
I raccomed to read it!
(...)
Enjoy! & report back for feedback
P.S.
Files are zipped, extract them!!!
Click to expand...
Click to collapse
Hi,
I can not apply root because of he problem between pokemon go and root, (I am playing pokemon go with my 8 years old son a father-son activity and he loves it)
I am using a dev miui rom and i did tune my thermal-engine and remove the input boost using the TWRP file manager to apply the files.
This rom does not have init.d folder could i call your script from init.qcom.post_boot.sh? if so, do you know how to?
best regards,
John
You should look for some sort of systemless root, and magisk to masquerade root and be able to play Po Go on a rooted phone. I don't think you can chain load the script within post_boot.sh and by the way to modify it you should have super user permissions. Anyway keep up the father and son activity, is way more important!
Sent from my Mi-4c using Tapatalk
GoldGanja said:
You should look for some sort of systemless root, and magisk to masquerade root and be able to play Po Go on a rooted phone. I don't think you can chain load the script within post_boot.sh and by the way to modify it you should have super user permissions. Anyway keep up the father and son activity, is way more important!
Sent from my Mi-4c using Tapatalk
Click to expand...
Click to collapse
thanx, my son does not talk about anything else...
About the chain load the TS rom does that with ts_power.sh file.
Code:
# ts power scripts permissions
chown -h system /system/etc/ts_power.sh
chown -h system /data/ts_power.sh
Code:
# Call ts_power.sh, if found
if [ -f /data/ts_power.sh ]; then
logi "Call /data/ts_power.sh set_profile $profile"
sh /data/ts_power.sh set_profile $profile
elif [ -f /system/etc/ts_power.sh ]; then
logi "Call /system/etc/ts_power.sh set_profile $profile"
sh /system/etc/ts_power.sh set_profile $profile
fi
I will try to see if it works using your script.
About systemless root, i don't want to be in the middle of the cat and mouse thing. Today google update and tomorrow there is another hide root.
I did replace the thermal engine using the twrp file manager. It works.
Nice share bro. Thermal engine + init.d script is good battery backup for mi4c.
Hello,
could you make patched files available and the place where they should be placed ?
I don't want to root my phone but I want to give your optimisation a try. It is possible with TWRP to replace the files in the file manager. More work but it can be done without root. Therefore however I will need the allready patched files....
A little more "complicated" even... might it not be possible using TWRP to flash these files ? I have no idea how that would work exactly but I can imagine it would be possible to create a flashable zip that replaces these files... It currently goes beyound my abbilities though unfortunatly but maybe someone can help with that.
Thanks for your share @GoldGanja , looks interesting.
But i think the thermal-engine.conf would cause more overheating as it is already (for me reduce overheating is the most important), but i like the way to reduce the clockspeed step by step. Maybe i will try it with lower values.
The modified governer looks great. I think this will help with heating too. But on this there aren´t laggings ?
Thank you! i hope this fix my battery drain and the heat, i'll report if i see changes
@nachtwacht
Even if i make a zip file to use with twrp, this will only be useful for the thermal-engine conf file...because the other one is a script i've created and so there is no other file to replace. As stated ROOT is needed, i'm sorry.
@Danny94
thermal-engine.conf per se will not increase or decrease over-heating, of course one could make a conf file to be more restrictive on the temps and brutally decrease the performance but i don't see the need of this because i don't have any over-heat problem within my device with the script i've made. A major cause of over-heating is the input-boost frequency that by default is set to 1248MhZ, while if you run my script it will be 600 MhZ. Farther i have no lags at all...give it a try and report back. More feedback I have about it, the better I can adjust some parameters.
@HYBRIDEMON
Thanks!
@GoldGanja
Yeah i will try tomorrow if i get some free time.
Wich Rom do you use ? I have at almost all roms overheating problems. After 10 min+ of 3d gaming i have ~55°c + (On my old phone Thl 5k i could play the same game hours, don´t get over 45 °c and no lagging or something - and yeah its not the best phone).
With your thermal config the device throttles later. So it will heat higher, until it shut down big core etc. As hotter it becomes as more difficult its to cooldown. Sure if you won´t reach 52°c would be perfect one. But maybe i will replace the values with lower, else it looks very good.
I can't find tao.log at sdcard.
Script is applied or not?
I copied to etc/init.d and set 755 permissions.
Edit:
Finally I applied manually and I have 2 errors with big cluster settings.
Enviado desde mi Mi-4c mediante Tapatalk
@dany94
I'm using last stable from xiaomi.eu (8.0.5). Anyway, if you get to know how the gears of the thermal engine works, do what is best for your usage. Feel free to change the numbers on my file if needed
siba01 said:
I can't find tao.log at sdcard.
Script is applied or not?
I copied to etc/init.d and set 755 permissions.
Edit:
Finally I applied manually and I have 2 errors with big cluster settings.
Enviado desde mi Mi-4c mediante Tapatalk
Click to expand...
Click to collapse
I think you are using a CM TS rom, right? well, for that you have to do two things.
First, set the battery mode to QUICK, because on BALANCE there is the hotplug of the BIG cores. Then re-run my script.
If that's not the case, maybe the device was just a bit hot, and the hotplug kicked in by the thermal-engine...let it cool down first or use my thermal-engine conf.
Second, rename my file to userinit.sh and place it under /data/local if you want the settings to be applied at each boot.
GoldGanja said:
Even if i make a zip file to use with twrp, this will only be useful for the thermal-engine conf file...because the other one is a script i've created and so there is no other file to replace. As stated ROOT is needed, i'm sorry.
Click to expand...
Click to collapse
Maybe I was not clear or, more likely I do not completely understand which is a fact for sure
Let me clear up the first part, then hopefully in the end I will also better understand
Your script chances several files if I understand correctly ? scaling_min_freq for example is the first one you change in the script ?
Could we not update all the files that you change using TWRP ?
My guess is, (that's just me trying to understand better.....) that I think that using TWRP it is possible to change these files without root, but in reality it is not because the phone is not rooted ? Maybe because only the complete system can be changed and not single files ? (without root)
I do know that in the end, for me it is possible to root my phone, apply the settings, and then unroot it again.... which hopefully have my phone working like it never was rooted... it's just a risk I would like to avoid if in any way possible, therefore I am investigating and trying to get it all clear for me, sorry for that
GoldGanja said:
@dany94
I'm using last stable from xiaomi.eu (8.0.5). Anyway, if you get to know how the gears of the thermal engine works, do what is best for your usage. Feel free to change the numbers on my file if needed
I think you are using a CM TS rom, right? well, for that you have to do two things.
First, set the battery mode to QUICK, because on BALANCE there is the hotplug of the BIG cores. Then re-run my script.
If that's not the case, maybe the device was just a bit hot, and the hotplug kicked in by the thermal-engine...let it cool down first or use my thermal-engine conf.
Second, rename my file to userinit.sh and place it under /data/local if you want the settings to be applied at each boot.
Click to expand...
Click to collapse
I'm using Resurrecction Remix.
Thanks for your answer.
Enviado desde mi Mi-4c mediante Tapatalk
I was pretty sure you will do such a good job for Mi4c! Well done!
Edit: btw big cluster values are not getting applied
solis_f said:
I was pretty sure you will do such a good job for Mi4c! Well done!
Edit: btw big cluster values are not getting applied
Click to expand...
Click to collapse
What ROM are you using?
Sent from my Mi-4c using Tapatalk
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
Thermal throttling solution
Block max/min auto frequency: Samsung Custom Frequency Manager, i call it "The Slippery" (gekkehenkie11 explanation here) is "samsungs personal assistant" when it comes to cpu frequency, changing it according to samsung preferences. We don't have sourcecode of it, so we cant modify it. But we can override it so it doesn't modify our settings (we do it with permissions this way) so then you can choose the range of frequencies you prefer with any cpu manager like kernel adiutor (kernel's thermal throttling will still continue working) re-activated in v8 (see changelog for more info)
"Disable" throttling (push it further) = snappier device specially during heavy tasks (tested very heavily and couldnt pass 82C (180F) battery never reached 42C (108F)) you may have different temps due to Sillicon lottery or heavy gaming modified in v8 (see changelog for more info)
We have 3 options to manage temperature: Core Control (turns off cores), VDD Restriction (increases voltage when cpu is really cold) explanation HERE and HERE and Throttling (decreases cpu max freq)
How to check
A log file with the name "90Thermal_solution.log" will be created at /data
Click to expand...
Click to collapse
CPU Solution
If you take a look you will realise big cpu utilization percent is always high, and that leads to higher frequencies used and sustained for more time = higher battery consumption and cpu temps
I've tried to mitigate that by changing interactive cpu governor tunables and after setting tunables i got to a point where big cpu doesn't ramp up so often when nothing is being done (there is always something going on in background but that cpu usage and frequencies when doing "nothing" can't be justified in my opinion (i blame eng kernel for this)
Change gpu governor to cpufreq (i didnt notice any increment in battery consumption whereas the smoothness has increased for good) and set freqs to 214-624mhz (133 caused scrolling lags sometimes. You can change it if you want -> kernel adiutor)
Useful sites:
Advanced Interactive Governor Tweaks by SoniCron - Angler thread
[Guide] Advanced Interactive Governor Tweaks
GoogleSource documentation about governors
Interactive – why is this the best governor? [INFO]
[*] [URL="https://source.android.com/devices/tech/perf/boot-times"]Optimizing Boot Times | Andorid Open Source Project[/URL]
How to check
A log file with the name "91Cpu_solution.log" will be created at /data
Click to expand...
Click to collapse
DAC Solution
Enable class AB config for hph (good explanation of what it does HERE), In simply words:
Prioritize quality over battery consumption (especially when not at max volume)
High performance only works with headphones (or anything you connect using 3,5mm jack)
How to check
A log file with the name "92Dac_solution.log" will be created at /data
Click to expand...
Click to collapse
More Solutions
First of all, the links:
How GPU governor impacts user experience
GPU causing jitter in essential phone
GPU causing jitter in essential phone 2
Sysctl documentation
Extra free kbytes explanation
Extra free kbytes explanation 2
Difference between vm.dirty_ratio and vm.dirty_background_ratio
VM tunning
More VM explanations
Entropy explanation by zeppelinrox
Overcommit ratio is a myth
How overcommit works
good scheduler explanation by kgs1992
cfq, noop, deadline comparison
Improving the Real-Time Properties
What this does:
Adjust some VM things
We will allow dirty data to stay on ram for a while (i cant belive why this was "off" originally -> eng kernel (maybe))
We will ajdust min and extra freekbytes to stock user-kernel value
Adjust lmk values
Increase read ahead and disable io stats (technically this should free some cpu) + change scheduler to deadline
Disable some logs (less 'disk' use) and other useless things
Modify entropy rngd tunables and link random to urandom
How to check
A log file with the name "94More_Solutions.log" will be created at /data
Click to expand...
Click to collapse
Installation
All has been tested in S7 Edge 935V with CRG2 Stock_Oreo_Hybrid by Jrkruse Rooted with Root For S7/S7Edge Oreo And Nougat by Jrkrusewith interactive governor option without issues (no bootloop)
0 ) You must be rooted
1 ) Make sure you have lastest busybox installed Google Play link
2 ) Download the Files (attached)
3 ) Extract .zip or .rar (they have the same files)
4 ) Copy tweak files (.sh ones) you want to apply to
Code:
/system/su.d
or
Code:
/system/etc/init.d
or use any init.d emulator (i dont guarantee it wil work) [MOD][APK+SCRIPT+ZIP] Enable Init.d for Any Phones w/o Need of Custom Kernels!!!
5 ) Set 777 permission (rwx-rwx-rwx)
6 ) Reboot
Click to expand...
Click to collapse
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
Solution Installer
This is just 2 .bat installer, which will install
EngSolution.bat
Thermal Throtlling Solution
Cpu Solution
Dac Solution
More Solutions
Rendering Solution
A modified sysconfig to allow google play services and playstore be optimized by doze
AppSolution.bat
Will delete lots of apps i consider bloat
This is done using a pc
1 ) Unzip/decompress
2 ) Run .bat you want
3 ) Device will reboot once completed
Click to expand...
Click to collapse
If you want to Uninstall
1 ) Delete the files you copied and reboot
2 ) If you used dalvik solution, restore build.prop backup and wipe dalvik cache (delete the files inside /data/dalvik-cache/) --> Next boot will take more time after this (only the next one after deleting)
3 ) If you used Rendering solution, restore stock name and set permission to 777
4 ) If you used Apps solution, defrost all the apps you froze
Click to expand...
Click to collapse
Changelog
V2
V3
V4
V5
V6
V7
V8
V9
Click to expand...
Click to collapse
Has anyone tried this and noticed any improvement? What about heat issues?
Archangel said:
Has anyone tried this and noticed any improvement? What about heat issues?
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
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
Reorganized post, added dalvik tweaks, redone all the scripts.
I suggest anyone who is using this uninstall and install new versions
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 !
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 !
Click to expand...
Click to collapse
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?
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?
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
Have you had anymore development on these? Running these along with my flashing stock BL tweak has been very helpful
gwilly3301 said:
Have you had anymore development on these? Running these along with my flashing stock BL tweak has been very helpful
Click to expand...
Click to collapse
Yes, im currently testing 2 configs to decide which is better. Then i'll finish with cpu governor tunables and update op
Maxissc said:
Yes, im currently testing 2 configs to decide which is better. Then i'll finish with cpu governor tunables and update op
Click to expand...
Click to collapse
Awesome, thanks for the update! Don't mean to nag
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)
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)
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
Does Dalvik Solution.txt go into /su.d as well?
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?
Click to expand...
Click to collapse
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)
UPDATE V3
Reupdated V2 with scripts working correctly now
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)
Click to expand...
Click to collapse
No, no logs. Does that mean scripts aren't running then?
gwilly3301 said:
No, no logs. Does that mean scripts aren't running then?
Click to expand...
Click to collapse
yes. please try with v3 i just uploaded. im sure they are working fine now
Maxissc said:
UPDATE V3
Reupdated V2 with scripts working correctly now
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
Do I need to clear dalvik again?
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?
Click to expand...
Click to collapse
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)