Database Info

[DEV] Script for tweaks (version 1.02) 18-12-2010

Here is a script i've made (had nothing to do, so...).
Phone must be rooted and have busybox installed.
What first menu looks like:
1 - enable/disable hardware acceleration
2 - enable/disable jit
3 - enable/disable stagefright player
4 - change heapsize
s - show status
r - revert to original configuration
q - quit (don't forget to reboot your phone!)
==================
enter your option:
Click to expand...
Click to collapse
Download:
http://www.4shared.com/file/gApTB6EG/tweaks.html
md5 b0865d9de67a82215913512cb644211d
Just copy the file to your sdcard. Then in a terminal emulator run:
su
cat /sdcard/tweaks > /data/tweaks
rm /sdcard/tweaks
cd /data/
./tweaks
If it doesn't run, type first:
chmod 755 /data/tweaks
Additional notes:
Script does not work if run from sdcard, must be in /data/ or /system/ (this one goes to allsalvati for testing)
---
If anything is wrong i will fix it, but only if you give me feedback
If you know any good tweaks, say it and i'll add them.
---
Changelog:
version 1.02:
backup/restore added
version 1.01d:
working again. sorry for the mess...
version 1.01c:
nothing new. just rearranging code
version 1.01b:
messages were not staying in output. fixed
version 1.01a:
small fix. v1.01 was not working
version 1.01:
added status menu

ruigui said:
Here is a script i've made (had nothing to do, so...). Phone must have busybox.
Download:
http://www.4shared.com/file/gApTB6EG/tweaks.html
md5 ea568c399c67ecd87db0dd790cdf0e93
Just copy the file to your sdcard. Then in a terminal emulator run:
cd /sdcard/
./tweaks
If it doesn't run, type first:
chmod 777 /sdcard/tweaks
Please give me some feedback. I don't own the phone so i can't test.
Click to expand...
Click to collapse
what the script does?

So script should be able to do:
enable/disable hw acceleration
enable/disable jit
enable/disable stagefright player
change heapsize

Yes. For now it's what it does.
The ideia is to be able to enable/disable a certain tweak, without reflashing zips, and rewriting files in phone.
But i need some feedback to know if it is working. I can't test it.
It will only change values in /data/local.prop, nothing else.

It seems that it is well written, so I will try that and let you know what's happened.

Thanks for testing. I'm still waiting to have some money so i can buy this phone...
Meanwhile, i'm "playing" with ROMs and files. I'm not good at scripting, but i'm trying to learn while doing something useful.

How much did you increase the heap size?

domenic_s said:
How much did you increase the heap size?
Click to expand...
Click to collapse
I didn't increase it. Script shows this message:
"default=24, recommended=32"
"enter new heapsize value (1-64): "
You can enter any value between 1 and 64.
If you enter any other value, or a string, character, symbol... script will show this message:
"wrong value"
"please input a value between 1 and 64"

For those who don't feel like editing this themselves this is great. Thanks for releasing it for people to try out more tweaks on stock ROMs.

i'm trying to run this script and gives me the following message: ./tweaks: permission denied
Before anything i typed su, then chmod 777 and it gave me error.

It should work be working...
Anyone else confirms this issue? Is this script running or not?
If it is working and there are more tweaks, i can easilly add them to the script.
If this is an isolated case, i really can't help. I don't own an android phone (yet), so i can't test....
allsalvati do you have busybox installed?

No, i don't.
Sent from my LG-P500h using XDA App

That may be your issue.
You must mount /system/ as read-write, then copy busybox binary to /system/xbin/, then run these commands in terminal emulator:
su
cd /system/xbin
/system/bin/chmod 755 busybox
./busybox --install -s /system/xbin
After that you can mount /system/ as read only again, and reboot your phone.
I don't know if there is another way to install it that is easier.

I downladed busybox installer from market and the app says that was installed. The. /tweaks gives me the same message.
How do i test if busybox was installed right?
Sent from my LG-P500h using XDA App

I found this:
That is a problem, you cannot chmod a script to executable on the SD card. (well some things can, but 99% no) the system is designed to prevent u executing scripts from an SD card
cp it to /system/xbin or /system/bin.
Or if u hate to see it in system', use /data/
THEN chmod it. should be fine to run
Click to expand...
Click to collapse
Try to copy the file to /data/ (so you don't mess with /system/), and then try to run it with:
cd /data/
chmod 777 tweaks
./tweaks
It should not need to be run as root

Moved to /data and worked.
I changed heap size to 32 and disabled hardware accelaration just to test.
With hw acc - 981 on Quadrant
Without - 820
So i think this is working.
Perhaps you should print the values so the user can see what is enabled or not before apply.
Thanks for your help
Sent from my LG-P500h using XDA App

Can you test something for me?
Make sure you have hardware acceleration disabled, and reboot you phone.
Then open terminal and run:
getprop | grep hw (see what it outputs)
then run the script, enable hardware acceleration on it, but DON'T reboot your phone yet.
Then exit script, and run again:
getprop | grep hw
Has the value changed, or is it the same?
I need to know if the system assumes immediately any changes (although they may not be functional until reboot).
This is needed to work on your request.
allsalvati said:
Perhaps you should print the values so the user can see what is enabled or not before apply.
Click to expand...
Click to collapse
I'll work on that and post an update after someone tries what i asked above.
Thanks for testing
EDIT: to test benchmarks, enable/disable jit. It gives greater differences in values

I tried what you say and both outputs are the same:
$getprop | grep hw
[debug.sf.hw]: [0]
[hw.keyboards.65537.devname]: [7k_handset]
[hw.keyboards.65540.devname]: [thunder_keypad]
[hw.keyboards.65541.devname]: [touch_mcs6000]
[hw.keyboards.65542.devname]: [atcmd_virtual_kbd]
Edit: Tested disabling JIT and it worked. Linpack Before 7.35 - After 4.3

So i can't rely on getprop to check current values...
If anything is changed, getprop won't give the right output till reboot.
Damn... Script was almost updated. Now i must find a new way and redo this section.
Thanks for testing again
EDIT:
New version for download at first post. status menu added.
I think it's all ok.

It seems work fine on my phone. But I can't see the status. When I choose to see current status or status after reboot, the screen of my emulator returns too fast to the selection menu (show curent status or after reboot) and I can't see anything !

[SCRIPT]AndroidManager v0.1

AndroidManager v0.1​
by ScumpinatoS​
Screen​There are no screen, the script operates on a command line
What is it?​This script allows you to do anything on your android device even if you don't know anything about adb and/or about scripting
With this script you can:
1. Reboot
2. Go To Recovery Mode
3. Install an APP in /data/app
4. Install an APP in /system/app
5. Pull your framework folder
6. Stop your device (ROOT)
7. Start your device (ROOT)
8. Mount partitions Read-Write (ROOT)
9. Mount partitions Read-Only (ROOT)
10. Backup your /data/app folder (ROOT)
11. Restore your /data/app folder (ROOT and REBOOT)
12. Backup your SMS (ROOT)
13. Restore your SMS (ROOT and REBOOT)
14. Send a file to your SDCARD
15. Pull the build.prop
16. Push the build.prop
17. ADB Shell
18. Exit
Requirements​
- Windows 98 or above
- An Android Device
- Admin rights (Vista/7)
- ROOT where needed
- USB DEBUG ON
How to use?​
1. Download the Link at the end of the post
2. Double click on AndroidManager
3. Now the script is running
4. Choose the option that you want, then choose what do you want to do and the script will do everything
In the guided mode the script guides you trough the script telling you something about the command and how to use them It's good if you want to know how the script work or if you want to learn something about adb scripting
Now the download link:
AndroidManager v0.1
Changelog:
v0.1: Initial release
Enjoy and leave a feedback
Who wants the source code, ask to me in PM
IF YOU LIKE MY WORK, PLEASE THANK ME AND CONSIDER DONATE TO ME, EVEN 1$ IS GOOD, I'M JUST A STUDENT

Very usefull(you are a genius)

Thank you really much =)
I'm not a genius, I'm just a guy who loves making his life easier XD XD

I found a little bug (not very important to fix).
I have tried to shutdown(6) and works but 1 min ago when i tried it the screen just freeze, i have tried to shutdown again and nothing but when i tried poweron(7) the phone powered one whitout problem(theat freeze was funny whit the phone poweredoff but whit screen on ).

That isn't a bug. They are the adb shell stop and the adb shell start command. You need them when you want to modify the /system partition without having problems

Is this scrit useful to You?
What do you think of this script?

there're no option to install font?
Btw thank.

ScumpinatoS said:
Is this scrit useful to You?
What do you think of this script?
Click to expand...
Click to collapse
Very good for persones like me (i have a short cable and was hard to use the phone when was at pc) thease is what every android owner must have.

afifth said:
there're no option to install font?
Btw thank.
Click to expand...
Click to collapse
Based on the number of download and the number of donations [0 so far] I will decide if update this script or leave it as it is.
I have so more ideas in my mind, but I'm waiting to see the appeal of the script
IF there will be a 0.2 version, that option will be available

*bump*
Do you use/like this script? What do you think of it?

I started to use your script it's very usefull, thanks

You're welcome
If the script can reach 500 download by the end of the week will be upgraded to the v0.2

*up*
So? Any feedback?

I will stop developing this script because I found that http://forum.xda-developers.com/showthread.php?t=825934&highlight=androidmanager
I think that it isn't fair from me to steal the name, and btw that script is much much better than mine

[HOW-TO] Some tweaks to sweeten your life with the Infinity a little

Hi everybody, I would like to share my experiences with the Infinity and ask you guys to share your opinions, thoughts and ideas on tweaking it. Hopefully we can sort something out together.
Please remember that you can brick your tablet with any of these methods and lose your warranty too and be the one solely responsible for it. I have not bricked mine, so I am writting all of this with best intentions . Proceed with caution and only if you are sure that your Infinity not booting will not lead you to jumping off a high building! Seriously.
Ok, here it goes.
Hit [THANKS] if it helps.
Seems this thread somehow got to the News, so special thanks go to Joe and those of you who have reported it newsworthy. I'm glad I could've helped you with this!
Remember 1) you'll have to do most of these each time you update firmware / change ROM and 2) go back to stock /system files every time before you apply an OTA update, as it does various checks on /system integrity now.
1. ROOT
Don't use ASUS Device Tracker! (see point 6. below)
Install SuperSU and follow these steps before updating to the Jelly Bean to preserve root (thanks to nooktablet for posting this). Others said that Superuser app combined with RootKeeper sufficed, so do as you wish.
DroidEris1981 has reported that in his case on the .30 firmware he was only able to root his Infinity using an older version of Debugfs and only when pausing it at each reboot, waiting for the device to fully boot up before the next step.
So far the only rooting method that works is the Debugfs method by sparkym3. By rooting you can boost your Infinity's performance a bit, including its poor I/O results, and much, much more (see threads on reasons for rooting and apps).
Once again: ROOT BEFORE UPDATING TO THE JB!
If you've failed to do this, however, there is still a way to work things out - see the first few posts in this thread if you're under unrooted JB now.
In case you experience problems using this method, you may try one of the solutions described in this thread, but as there is a new 2.2 version now, you should be good just using it.
Some need to RUN the Superuser app first before it starts working. And remember about BusyBox, it comes handy in many situations, especially if you are going to use the shell. And you can use SuperSU instead of the "default" Superuser app.
RootKeeper might come in handy when updating firmware on a rooted Infinity.
1.1. We have the unlocking tool now, and a few custom ROMs in the development section.
2. I/O scheduler [only after rooting your device] OBSOLETE
Since the .26 update and under the JB as well cfq is the default scheduler and better than non-stock sio, so no reason to change the scheduler at this point already on >= 9.4.5.26 firmware!
After a day of using JB I can say that (stock) noop is slightly faster than cfq for most uses.
[REMOVED]
3. build.prop tweaks ("/system/build.prop" file)
These are for the ICS. We'll all have to see how these perform under the JB. So far changing the DPI via build.prop has been confirmed to be obsolete.
EDIT 22.12.2013 Deleted several obsolete entries, see LaraCroft304's post for reference.
I have used various suggestions as a reference, incl. demandarin's tweaks for the Prime (just search "build.prop tweaks" on xda and read about what these tweaks do). I am still unsure of some of them, e.g. the proper heap size instead of the default 256m (or maybe we should leave it be?). The tweaks I'm using are the following.
Edit: I'm leaving the default heap size, I think it's better for the games.
Lines to EDIT:
#an old proposal, which seems to be of no use
#dalvik.vm.dexopt-flags=m=v,o=y
dalvik.vm.dexopt-flags=v=n,o=a,u=y
#In case you experience problems with some apps after this, try (unhash) this instead:
#dalvik.vm.dexopt-flags=v=a,o=v,u=y,m=y
#(you can also see, for example, this thread for instructions)
# optional: CHANGE SCREEN RESOLUTION / PIXEL DENSITY (so that your screen can become more capacious)
# ro.sf.lcd_density = 160
Lines to ADD:
# BATTERY SAVING
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
# UI & GENERAL PERFORMANCE
ro.kernel.android.checkjni=0
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
dalvik.vm.execution-mode=int:jit
com.ti.omap_enhancement=true
# MEDIA QUALITY & PERFORMANCE
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.media.enc.jpeg.quality=90
ro.media.enc.hprof.vid.bps=8000000
persist.sys.use_dithering=1
# NETWORK PERFORMANCE
# there are different types of advice here, you can try what work's best for you out of the latter two (just delete all the spaces which xda keeps adding!):
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
#net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=262144,524288,1048576,262144,524288,1048576
# SWITCHING SOME NOTIFICATIONS OFF
# disable sending usage data
# disable adb notifications
persist.adb.notify=0
# FAST REBOOT
persist.sys.purgeable_assets=1
# you can also unhash this and disable boot animation for faster boot:
# debug.sf.nobootanimation=1
# This is for current, Wi-Fi only version of Infinity of course:
ro.carrier=wifi-only
# Just for those who need it - unhash the following line to make your device run all ADB shell and terminal emulator commands as ROOT by default (use with caution)
# ro.secure=0
3.1. You can edit the build.prop file manually, you can use one of a few apps out there to manage it, but I have found manually mounting the system r/w (and r/o again after changing the file) and editing it through a PC (you can use Dropbox) or the Infinity with the dock most helpful - you can just cp the new file to (remember to make a backup copy of the old file just in case!).
If you like using the term, you can just 'su' and write these commands:
a) R/W before edit:
mount -o rw,remount /system
b) R/O after edit (remember to run 'chmod 644 /system/build.prop' as root before remounting /system R/O):
mount -o ro,remount /system
3.2. Remember to reboot your device after changing the file. Clearing dalvik-cache won't hurt either.
Edit: Actually I highly recommend wiping dalvik cache to avoid bootloops (as root: rm /data/dalvik-cache/*) <- and then.reboot
4. Minfree tweaks:
You can either change the values in /sys/module/lowmemorykiller/parameters/minfree (remember these are pages, so 1024 means 4MB!) or use any of the apps from the Playstore meant for that. I'm using System Tuner for things like that (look for Tweaks / Auto-Kill in the app). You might set anything you like, possibly 8,16,200,220,240,275 MB proposed by the author of the (messy) SuperCharge script for the 1GB RAM devices (based on a minfree calculator by another XDA member). I have it currently set on 8,16,32,128,192,192 MB, which seems aggressive enough.
You can read more about it and what these values mean here.
You can also have a look at my thread on battery life.
5. Disable "smart dimmer", which is the reason you can see some screen flickering when changing between light and dark backgrounds that many find annoying (described by some as "dynamic contrast", which it resembles):
Can be done through SYSTEM SETTINGS under the JB, so no need to do this manually anymore.
To disable:
echo 0 > /sys/devices/tegradc.0/smartdimmer/enable
To re-enable echo 1 to the this file or simply reboot.
Be sure to include this in a script so that rebooting won't change it (just make an .sh script with the above line in it, you can use either SManager or system .sh scripts (you can use my simple solution posted here if you don't like editing files yourself). See also jtrosky's hints on changing the brightness settings.
Please note that it may negatively affect your battery life, although with brightness set low it shouldn't be much worse.
All credit goes to those who have found out about it - see this post for details.
6. Disable remote management that allows ASUS (or anybody in charge of their servers) to track, lock or wipe your device over-the-air or steal your data, which has been confirmed ASUS is doing: read the whole story about warranty voided because of rooting here.
7. Install Volume+ or a similar app to boost your device's sound level (you can register here to get the full version for free, but if it helps, support the developer). And remember to change the audio device in the system audio settings to Volume+!
8. Other tweaks, init.d, scripts etc.
See the development section for custom ROMs which include various tweaks and for custom recoveries.
9. Some keyboard solutions:
Re-map the browser keyhttp://forum.xda-developers.com/showthread.php?t=1497624 in the dock in order to be able to use your favourite browser or do some custom re-mappings.
In case of problems with diacritics when docked, be sure to use KLSwitcher for setting your locale.
Finally, not really a tweak, but something that a lot of users find helpful: KEYBOARD SHORTCUTS.
10. Remove bloatware (see the first few posts with further links here).
11. Set background processes to max. 4 in the dev. settings for better stability (that's true for the ICS at least).
<----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
And remember, at the end of the day, when you're done tweaking, you should disable USB debugging if you don't want to get hacked.​
Hit [THANKS] if it helps.

Thank you for this! I'll have to try some of these out when I pick up my tablet.

i remember reading about some 300 users using, browser2ram (i think that's what its called) for a better internet browsing experience.

denniegst said:
i remember reading about some 300 users using, browser2ram (i think that's what its called) for a better internet browsing experience.
Click to expand...
Click to collapse
Can you give us a link? Google is not helpful with this name you mentioned (browser2ram).

http://forum.xda-developers.com/showpost.php?p=25286407&postcount=61
i think it only works on stock browser, but i could be wrong. and since everything is sent to the ram, once the tablet resets everything will be lost: browser history settings etc

denniegst said:
http://forum.xda-developers.com/showpost.php?p=25286407&postcount=61
i think it only works on stock browser, but i could be wrong. and since everything is sent to the ram, once the tablet resets everything will be lost: browser history settings etc
Click to expand...
Click to collapse
Thanks, that sounds interesting, but I am not sure there is a need for it on the Infinity. Dolphin HD performs exceptionally well (thanks for the info, ray3andrei: http://forum.xda-developers.com/showthread.php?t=1752809&page=2).
Edit: Can't recommend Dolphin anymore due to serious privacy issues.

Hi
Correct me if i'm wrong:
1. install the drivers if they are not installed allready
2. tick usb debugging
3. tick unknown sources
4. unzip DebugfsRoot_v1.8
5. connect tab to pc
6. run RootDebugfs.bat
7. select option 1 -Root
8. since haven't go further this step, i don't know what's next till rebooting
that's it? device rooted?
i have a little experience in rooting cause i have rooted my galaxy s a few times, but that phone is almost unbrickable
i just want to be sure i'm doing it right
thanks

dobranszky said:
Hi
Correct me if i'm wrong:
1. install the drivers if they are not installed allready
2. tick usb debugging
3. tick unknown sources
4. unzip DebugfsRoot_v1.8
5. connect tab to pc
6. run RootDebugfs.bat
7. select option 1 -Root
8. since haven't go further this step, i don't know what's next till rebooting
that's it? device rooted?
i have a little experience in rooting cause i have rooted my galaxy s a few times, but that phone is almost unbrickable
i just want to be sure i'm doing it right
thanks
Click to expand...
Click to collapse
Yep, that's basically it
Then it reboots a few times while pushing some files through adb, you get the Superuser program installed etc. After a few minutes you should have a rooted Infinity.
However, it will be much more fun after installing BusyBox from the Market/Play. It gives you a bunch of commandline tools to play with.
Just remember to charge your device and not to connect any other Android device while rooting.

I don't understand why you are using the 1.8 version when the 1.9 is there. I used 1.9 to root without any problems.

Alkzn said:
I don't understand why you are using the 1.8 version when the 1.9 is there. I used 1.9 to root without any problems.
Click to expand...
Click to collapse
There are links to both in the thread I was referring too. Actually I don't see any harm in using 1.8, as 1.9 is just updated Superuser app, which will update itself from Google Play anyway (they had some problems uploading the file to xda btw)

Hi fellow Infinity-Users!
I tried both versions (1.8/1.9), and both equally worked/failed with my (european) TF700.
The issue that actually broke the batch-script was adb wait-for-device, which just seemed to catch a timeout after waiting for the tablet to reboot.
As there is little magic in that script, you can safely execute all it does by hand (basically all the lines involving adb). That's the way I just rooted my TF700 and it worked like a charm.
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
Then you will have to hit enter (or some other key) each time once the tablet has rebooted.
What is actually needed for rooting:
Wait for your tablet to be fully booted up.
In a terminal execute the following commands in the folder you unpacked the rooting stuff to:
Code:
adb kill-server
REM as we are not rebooting and we don't hit a timeout, the first wait works
adb wait-for-device
adb push debugfs /data/local/
adb push su /data/local/
adb push debugfsinput /data/local/
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /dev/block/mmcblk0p1 /data/local/tmp
adb reboot
REM Wait for the tablet to reboot
pause
adb shell chmod 777 /data/local/debugfs
adb shell "/data/local/debugfs -w /dev/block/mmcblk0p1 < /data/local/debugfsinput"
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb shell rm /data/local/su
adb shell rm /data/local/debugfs
adb shell rm /data/local/debugfsinput
adb reboot
pause
REM Wait for the tablet to reboot
Now check the if you've got a rootshell - thus the given uid and gid of the are indeed root (0). make sure to remove the REM from the first or second part, if needed
You do this eg. by executing:
Code:
adb shell "/system/xbin/su -c id"
If you are root, install the Superuser Management Toolpack:
Code:
adb install Superuser.apk
adb reboot
Else cleanup:
Code:
adb shell /data/local/nachoroot.bin --undo > nul
adb reboot
Hope this cleared things up a little!
(all commands are taken from the script. If someone feels this is undesirable to post here, please let me know, I'll remove that immediately. Thanks to sparkym3, miloj and viperboy for giving me root-power !)

Thanks, that's interesting, I have the "European" version, as you called it, or rather WW firmware, and the script worked perfectly for me.

d14b0ll0s said:
Thanks, that's interesting, I have the "European" version, as you called it, or rather WW firmware, and the script worked perfectly for me.
Click to expand...
Click to collapse
True, I'm running WW_epad-9.4.5.21-20120601. From what I've seen so far, the issue seems not to be related to the tablet, but seems to be some issue with the OS adb is run on. In my case this is win7x64. What OS are you running? Would be interesting to track this down for others who may run into this issue in the future .

burningcf said:
True, I'm running WW_epad-9.4.5.21-20120601. From what I've seen so far, the issue seems not to be related to the tablet, but seems to be some issue with the OS adb is run on. In my case this is win7x64. What OS are you running? Would be interesting to track this down for others who may run into this issue in the future .
Click to expand...
Click to collapse
Good point. Unfortunately, the OS version trace seems to lead to nowhere, as I'm on Win 7 x64 too... perhaps something else then?

Run on balanced no matter what, everything runs better, and the tablet seems to not get stuck anymore or lag while downloading... so for the love of your infinity run on balanced instead of performance
Sent from my Jelly Beaned GNexus

ray3andrei said:
Run on balanced no matter what, everything runs better, and the tablet seems to not get stuck anymore or lag while downloading... so for the love of your infinity run on balanced instead of performance
Click to expand...
Click to collapse
I had good experience with "balanced" too, but if you compare it to benchmarks you can see that actually some operations are faster in "performance": mostly GPU, but not only that - RL Benchmark (SQLite Performance) is 110 in balanced instead of <90, reading & writing speeds are often faster in "performance" etc. But I agree it is the best mode to be running in everyday use, mostly because of power/battery *balance* and governing the CPU.

d14b0ll0s said:
I had good experience with "balanced" too, but if you compare it to benchmarks you can see that actually some operations are faster in "performance": mostly GPU, but not only that - RL Benchmark (SQLite Performance) is 110 in balanced instead of <90, reading & writing speeds are often faster in "performance" etc. But I agree it is the best mode to be running in everyday use, mostly because of power/battery *balance* and governing the CPU.
Click to expand...
Click to collapse
i really cant seem to get better gpu performance,,, quite the contrary i get better o balanced
Sent from my Asus Transformer Pad Infinity

I used sparky root on my prime and my tf300. Question. Can I use sparky root on my tf700 or will I need to do the debugfs method? If I have to use the debugfs method is there a step by step link?

leroybrute said:
I used sparky root on my prime and my tf300. Question. Can I use sparky root on my tf700 or will I need to do the debugfs method? If I have to use the debugfs method is there a step by step link?
Click to expand...
Click to collapse
So far only Debugfs has been confirmed to be working.
You might find either of these useful:
http://forum.xda-developers.com/showthread.php?t=1706588
http://forum.xda-developers.com/showpost.php?p=28490040&postcount=8

Thank you

[TOOL] DEXO – universal odex tool | HOW-TO move lib to /system/lib without reflash

DISCLAIMER: I am not the author of this tool!
All credits goes to tommytomatoe and you can press thanks in this thread because there is no dedicated thread for DEXO @xda (at least I found none)​
theking_13 said:
thiagomme said:
Why does it give better battery life? Thank you.
Click to expand...
Click to collapse
Because it splits the .apk (app package) into two parts, the .apk and a .odex file. Usually, for the phone to use an app, it has to decompile the .apk and get the parts it needs to run the app. With the odex files, which stands for "Optimized Dex" the startup time is much faster since the phone doesn't have to perform any optimizing at startup/runtime, and because of that, it also uses less CPU power, and thus makes it faster, smoother, and battery life is increased.
Click to expand...
Click to collapse
OK. So what is this tool?
This tool doesn’t deal with partially odexed ROMs. This tool is for odexing a ROM that is completely DEODEX.
The benefits? Faster boot, smaller imprint on /data/ partition, overall faster feeling
The myths? I can’t theme ODEX! WRONG! You can theme odex just fine! Just use baksmali and smali.
Click to expand...
Click to collapse
Requirements:Of the author:
adb
Linux, Mac OS X, Windows
Android device with busybox
Four minutes of your day
Added by me:
You have finally settled on a ROM that you want to use for some time without an intention to modify it further
You will need about 100 MB free space on system (my free space decreased from 160 MB to 96 MB after the completion of the process) To free some you can delete some apps from /system/app or move them to /data/app with a root file explorer (do not forget to set the correct permissions afterwards) or even better: to move your /system/lib folder to the lib partition without reflashing the ROM (see below for details)
Tested on Fallout 5.0 and Virtuous Infinity 1.35 with my Tweaked3 8.6 kernel. If you are using this it is at your own will and risk
NOT WORKING on CoolDroid and Sabsa Prime 6.5, probably because they have mixed framework from different Sense versions! Do not do on other similar ROMs only on ones with an original (even modded) framework!
Procedure:Go here and read carefully. It is basically some adb commands.
Out of respect to the author I will not mirror his link nor the instructions​----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------How to free about 120 MB space on /system by moving the lib folder to its dedicated partition without reflashing the ROM
This is only for ICS Sense ROMs. AOSP ROMs have enough free space to run the script without issues. I am not sure about the GB Sense ROMs, but if I remember correct they have enough free space on /system too. (if I am wrong please PM me to add GB Sense boot.img)
Requirements:
Bootloader with /system/lib support: 2.xx or 7.xx
150 MB free space on your SDcard
adb drivers installed (link in my signature)
4EXT Recovery (or any other recovery that has a menu entry for mounting /system/lib partition)
good attention while copy/paste the commands from here. One typo will lead to a bootloop
Download Tweaked3: XI_lib_bootimg.zip
md5sum: 1bc1d645b8212cdb2e4e949c6b7b3312
Download Patched: 3089_lib_bootimg.zip
md5sum: f1ae0228eb4057b4e4c4934a1e8a0515​The zips contain boot images of my Tweaked3 and Patched kernels with /system/lib support (I am not advertising them but this are the files I have ready, you can use a Stock kernel as well). There are 4 of them:
Sense4_lib_boot.img - for ALL Sense 4 ROMs (except VIrtuous Infinity)
Sense36_exp_lib_boot.img - for custom Sense 3.6 ROMs with experimental WiFi driver (Experimental kernel)
Sense36_lib_boot.img - for custom Sense 3.6 ROMs with stock WiFi driver (Stable kernel)
Virtuous_lib_boot.img - the name speaks for itself
Extract the archive in the folder where your fastboot executable is. This is not a flashable zip!​orDownload 2: b2b_lib_bootimg.zip
md5sum: 4bb4d44506eae5f247b69f9c5663e3a8​The zip contains boot images of my B2B kernel with /system/lib support (I am not advertising it but this are the files I have ready, you can use a Stock kernel as well). There are 2 of them:
Sense4_lib_boot.img - for ALL Sense 4 ROMs (except VIrtuous Infinity)
Sense36_lib_boot.img - for custom Sense 3.6 ROMs
Extract the archive in the folder where your fastboot executable is. This is not a flashable zip!​NOTE: your ROM has to be on the same version of the kernel before the procedure, otherwise your WiFi will stop working. Or you will need to download the zip from the kernel thread and copy the modules to /system/lib/modules manually giving them right permissions (644 or -rw-r--r--)​Procedure:# Connect the device to PC, open Command Prompt (cmd) and browse to the folder where are your adb and fastboot executables are (example: cd C:\android-tools)
# Reboot to Recovery (4EXT recommended)
Code:
adb reboot recovery
# Make a Nandroid backup
# Mount manually /system and /sdcard from the "mounts | storage" menu of the Recovery
# Copy the content of /system/lib to the SDcard
Code:
adb shell
mkdir /sdcard/system
cp -r /system/lib /sdcard/system
# Clean /system/lib
Code:
rm -r /system/lib
# Recreate empty /system/lib and set permissions
Code:
mkdir /system/lib
chmod 755 /system/lib
# Unmount manually /system from the "mounts | storage" menu of the Recovery
# Mount manually /system_lib from the "mounts | storage" menu of the Recovery
# Copy the lib contents to /system/lib
Code:
cp -r /sdcard/system/lib/* /system_lib
# Set permissions to /system/lib
Code:
cd /system_lib
find . -type d -exec chmod 755 {} \;
find . -type f -exec chmod 644 {} \;
[I]# Creating symlinks [COLOR=Red]Only for Virtuous Infinity![/COLOR][/I]
ln -s libhtc_ril.so librilswitch.so
cd hw
ln -s copybit.msm8660.so copybit.msm7x30.so
ln -s gralloc.msm8660.so gralloc.msm7x30.so
ln -s lights.msm8660.so lights.msm7x30.so
# Remove the SDcard /system/lib folder
Code:
rm -r /sdcard/system
exit
# Unmount manually /system_lib and /sdcard from the "mounts | storage" menu of the Recovery
# Reboot to bootloader
Code:
adb reboot bootloader
# Flash the boot.img and reboot
Code:
fastboot erase boot
fastboot flash boot XXX_lib_boot.img
fastboot reboot
Now you can use the tool above without concerns about free space
Enjoy!

amidabuddha, thanks for sharing. Have you tried this?

old.splatterhand said:
amidabuddha, thanks for sharing. Have you tried this?
Click to expand...
Click to collapse
Yes of course. Read the Requirements part
Sent from my HTC Desire S

Ok, i need help, cause i don't do this things often:
Fifth step, run it!
Click to expand...
Click to collapse
What and how?

old.splatterhand said:
Ok, i need help, cause i don't do this things often:
What and how?
Click to expand...
Click to collapse
Read further in the instructions, Theres a complete usage example with all the commands
Sent from my Desire S using xda app-developers app

Gonna try it today on CM10.
Tapatalked from Desire S running Andromadus

teadrinker said:
Read further in the instructions, Theres a complete usage example with all the commands
Click to expand...
Click to collapse
Sorry, my fault! I thought this come after the 5 steps.

if a rom is zipaligned, doesn't this mean that there's no need being odexed - kind of same thing? (same performance, battery life...)
i've read that, but i'm no expert...

toxic-hero said:
if a rom is zipaligned, doesn't this mean that there's no need being odexed - kind of same thing? (same performance, battery life...)
Click to expand...
Click to collapse
Zipaligning is about better RAM utilization. Odexing is about reducing the Dalvik VM which in theory should reduce CPU use and make the system run smoothly. You can watch the video, it is made by one of the Elite Recognized Developers of XDA so this guy probably knows what he is talking about. Moreover ALL Stock ROMs are odexed and I am sure that the companies developers are not just too lame to use it for nothing

tried the above...pasted something wrong and now phone stuck on htc screen and can't get into recovery

mackhenri said:
tried the above...pasted something wrong and now phone stuck on htc screen and can't get into recovery
Click to expand...
Click to collapse
Have you provided enough free space on your system partition? Try with a factory reset.
And once again:
If you are using this it is at your own will and risk
Click to expand...
Click to collapse

i think it was due to less space but still will try it once again after making space

Was a hard task to get enough space free.
Let's see how it works now.

old.splatterhand said:
Was a hard task to get enough space free.
Let's see how it works now.
Click to expand...
Click to collapse
Yes this may be an issue with the bigger ROMs. The easiest way is to move some app that you use rarely to /data/apps
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Sent from my HTC Desire S

amidabuddha said:
Yes this may be an issue with the bigger ROMs. The easiest way is to move some app that you use rarely to /data/apps
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Sent from my HTC Desire S
Click to expand...
Click to collapse
Get it on buddy.....I am ready to try whatever u make as you seem to give life to my phone once again and all the devs here and I am become a flashaholic...
Sent from my HTC Desire S using xda premium

amidabuddha said:
The other way is to use the lib partition but this needs ramdisk modification and a hboot that supports it. It is not hard I may add a small how-to if more users want to use this tool
Click to expand...
Click to collapse
This would b great, I did it once for Fallout with one of your kernel ramdisks, but it was not so trivial and a pain in the a** doing this all by hand. Though it worked perfectly, I don't remember every step I did, and mayb I didn't do it the elegant way, as I'm not very experienced.
As far as I remember the complicated part was unpacking kernel+ramdisk, modifing ramdisk, repacking everything and signing it. But this has to be done only once (by one idividual) for every kernel (+ramdisk). The rest ist more or less flashing and copying from /system to /system/lib partition (can be done in recovery easily). The latter mayb realised with one single script installer for every kernel (and rom) I guess. But here I also lack the experince with script installers, elsewise I would have shared the info.
I did it on Windows with bootimg-tools via Cygwin (unpacking, repacking), with SignApk on cmd (signing), in recovery (flashing, copying). For flashing I guess fastboot is more elegant (reflashed whole rom with mod boot.img). For the rest I didn't found something more convinient, but maybe soemone can enlighten me.

HOW-TO move your /system/lib folder to the dedicated partition added to the first post. Tested and verified working. Just copy the commands carefully
Enjoy!

Thx, the new guide worked like a charm for me on Fallout v5.0.0 with your kernel v8.5. I think it is more or less what I did, when it worked for me before. Also the odexing stuff worked well. What I am just wondering about, as this is odexing Rosie, will this affect the Fallout Tweaks for Rosie? And I tended to use Titanium Backup to merge updated system apps (like Facebook) into rom (essentially moving to system I guess), are there any drawbacks doing it with odexed apps?

kwisatz79 said:
Thx, the new guide worked like a charm for me on Fallout v5.0.0 with your kernel v8.5. I think it is more or less what I did, when it worked for me before. Also the odexing stuff worked well. What I am just wondering about, as this is odexing Rosie, will this affect the Fallout Tweaks for Rosie? And I tended to use Titanium Backup to merge updated system apps (like Facebook) into rom (essentially moving to system I guess), are there any drawbacks doing it with odexed apps?
Click to expand...
Click to collapse
All apps will work the same way after odexing. I can confirm all Rosie tweaks in Fallout working.
As per the Titanium stuff I have no idea try it and let us know
Sent from my HTC Desire S

when I am trying to copy /sdcard/system/lib to /system_lib it is showing not enough space....
Also in 4extrecovery - two system_lib are showing...
Any ideas?
BTW I am on Fallout 5.0...

4/18/2017 [] 7.1.1 UPDATE [] LG V20 (msm 8996) [] CPU, VM, RAM, IO "Tune"

ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the LG V20, please see below, and post questions or comments in the original thread above. Please state you are a V20 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the LG V20 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the V20 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to V20 users, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD

warBeard_actual said:
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the LG V20, please see below, and post questions or comments in the original thread above. Please state you are a V20 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the LG V20 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the V20 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Using Linux terminal (from your phone, for example):
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to V20 users, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
su
cd /
mount -o remount,rw /system
cd /system/etc
rm init.qcom.post_boot.sh
cd /sdcard
mount -o remount,rw /system
rm init.qcom.post_boot.sh
cd /system/etc
cd /sdcard
mv init.qcom.post_boot.sh /system/etc
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD
Click to expand...
Click to collapse
So to see any changes I need to change governor to interactive correct?

storm68 said:
So to see any changes I need to change governor to interactive correct?
Click to expand...
Click to collapse
Why wouldn't you be using interactive anyways?
If you are using a cpu set app, disable it if you decide to use this. The script will automatically set the governors to interactive

warBeard_actual said:
Why wouldn't you be using interactive anyways?
If you are using a cpu set app, disable it if you decide to use this. The script will automatically set the governors to interactive
Click to expand...
Click to collapse
Well cause v20 here has a kernel that uses conservativex that rocks on battery life. Your script is in. Gonna see the outcome... Thanks

storm68 said:
Well cause v20 here has a kernel that uses conservativex that rocks on battery life. Your script is in. Gonna see the outcome... Thanks
Click to expand...
Click to collapse
The conservative governor does good on battery life because it favors lower frequencies, or places bias to keep frequencies down. This is done at the cost of performance.
A tuned interactive governor can give you both.
Thanks for trying it out, let me know what your experience is with this mod.

Thanks for sharing this.. 1 quick question. I throttle my phone down to save battery with kernel auditor. Should I just leave all that at default for your mod?
I pushed this mod this morning, I'll let you know how things go. ?
Sent from my VS995 using Tapatalk

They phone sleeps deep

warBeard_actual said:
The conservative governor does good on battery life because it favors lower frequencies, or places bias to keep frequencies down. This is done at the cost of performance.
A tuned interactive governor can give you both.
Thanks for trying it out, let me know what your experience is with this mod.
Click to expand...
Click to collapse
Ok... So far battery is about the same. Performance is a bit better but not like it's a huge difference. I have NSS 6.5 kernel and when using conservativeX it was a bit better on battery and performance was never an issue. So honestly for me? Could be different for others due to personal setup. I'll keep the mod on but switch back the governor... Thanks for sharing this. I like to tinker. ?

It is very snappy now. Thank you

storm68 said:
Ok... So far battery is about the same. Performance is a bit better but not like it's a huge difference. I have NSS 6.5 kernel and when using conservativeX it was a bit better on battery and performance was never an issue. So honestly for me? Could be different for others due to personal setup. I'll keep the mod on but switch back the governor... Thanks for sharing this. I like to tinker.
Click to expand...
Click to collapse
Battery is about the same, performance is better, as stated it would be.

I can't get permission to change . I'm using romtoolbox pro...I've followed directions
Sent from my LG-H918 using Tapatalk

warBeard_actual said:
Battery is about the same, performance is better, as stated it would be.
Click to expand...
Click to collapse
Gotcha.. Your right... Gonna keep on phone. Thanks for your time and effort. Greatly appreciated.
---------- Post added at 04:25 AM ---------- Previous post was at 04:22 AM ----------
kenbrownstone said:
I can't get permission to change . I'm using romtoolbox pro...I've followed directions
Click to expand...
Click to collapse
I use FX file manager. May help you a little better. Just a thought

Yea it's noticible faster especially loading apps and loading on Facebook

warBeard_actual said:
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the LG V20, please see below, and post questions or comments in the original thread above. Please state you are a V20 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the LG V20 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the V20 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to V20 users, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD
Click to expand...
Click to collapse
@Warbeard... I've been running for over a week. I absolutely love it. Thank you for sharing. My phone is so smooth and lag free it feels like my wife's s8.
Amazing work with no sacrifice on battery life!
Cannot thank you enough.
Sent from my VS995 using Tapatalk

Hey @Warbeard....
Does this mod need to be reapplied if
Cache, dalvik- are wiped and a new kernel flashed?
warBeard_actual said:
ORIGINAL THREAD HERE: https://forum.xda-developers.com/axon-7/development/2-15-2017-axon-7-msm-8996-cpu-vm-ram-t3557392
This mod was originally created for the Axon 7, but due to several requests, I've modified a version for the LG V20, please see below, and post questions or comments in the original thread above. Please state you are a V20 user if you have feedback in that thread, to consolidate user feedback and speed up response time.
Custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the LG V20 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled. If the V20 requires write protection to be disabled, see the code and instruction below:
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio, dirty_background_ratio, swappiness, and other parameters of the virtual machine.)
- disabled zRAM for 6 GB variants (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power) this will not apply to V20 users, you will still have zRAM enabled.
- remapped minfree parameters for LMK (low memory killer) again only for 6 GB variants
- Tuned CFQ scheduler for flash storage devices
- Tuned "core_ctl" module (needs kernel support, I recommend freeza's latest version of BeastMode. For those wondering, yes, you can still use this mod with the stock kernel. It won't break anything.) again this will only apply to devices that support core_ctl at the kernel.
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
DOWNLOAD
Click to expand...
Click to collapse
Sent from my VS995 using Tapatalk

Guys, please don't quote the entire OP. It's not proper forum etiquette... :silly:

AthieN said:
Guys, please don't quote the entire OP. It's not proper forum etiquette... :silly:
Click to expand...
Click to collapse
My bad. I thought I deleted all but the 1st paragraph, then the post kept getting hung up. So I exited the app, then came back and it was there. I hate this app sometimes.
Sent from my VS995 using Tapatalk

Cant download your file

Just downloaded and I'm about to try this. Will report back in a bit. One question tho, I use atk app to tune my phone. Will that conflict with this?
Edit: I disabled atk app and after a couple of minutes of using this zip it does seem to make my phone a bit snappier just like applying a performance profiles from atk. I'll put my phone through hell today and report back

Thanks! There is a noticeably difference with this + no throttle fix!