Database Develop

[MOD] SGS3 TweakAIO init script v1.0.1

Tweak All In One (AIO) init script for Samsung Galaxy S3
Hi guys!
Here is my all in one init script ported to SGS3, what can do every necessary system adjustment for better battery life/peformance.
This script is working with every ROM, ICS, JB, CM9-10!
This script will not made any changes in the system partition, dont delete any of your data, but of course its not fully noob protected.
Dont made any change in the init scipt in the /system/etc/init.d/S99TweakAIO file!
But you can edit the config file free: /data/tweakaio/tweakaio.conf
Installation:
- Just install the attached file from the CWM.
Explanation:
After the first reboot the init script will create a directory structure under the /data/tweakaio folder.
The tweakaio.conf located in this folder too. In the logs directory you will find the script output logs.
The tweakaio.conf explanation (default settings):
Reset Settings=off
If you set this to on, at the next reboot the script will reset the own config file
Script Enabled=on
Enable/Disable script. If this is set to 'off' the script will not run at the init process
Logger Enabled=on
Enable/Disable the system logger.
LMK Tweaks Enabled=on
Low Memory Killer Tweaks main toggle
LMK Mode=aggr
Lowmemory killer modes are: def, std, opt, str, aggr, extr, ult
The def is the most lighter the ultimate is the most harder. If you need a lot of free RAM and you dont want to use heavy multitask you can safely choose the 'extr' setting.
Network Tweaks Enabled=on
TCP/IP networking advanced tweaks. This will increase TCP throughput and save more battery life too.
Memory Management Tweaks Enabled=on
Advanced virtual memory management
KSM Enabled=on
Enable/Disable kernel samepage merging (if its supported)
Cache Drop Interval Time (in hour)=4
Periodically drop unused cache and collect the garbage from the mapped memory area (usually free RAM)
Mount Tweaks Enabled=on
Remount system/data/cache partition with (flash memory) optimized mount flags
SQLite3 Defrag Enabled=off
If its enabled every sqlite database will be defrag after every reboot
Dalvik Cache Cleaner Enabled=off
If its enabled collect unused/garbage dalvik-cache records and eliminate them after every reboot
Move Dalvik-Cache to Cache partition=off
If its enabled this will automatically move present dalvik-cache to the cache partition. This can free up space in the data partition.
Fully automatic, applyed after a full cache/dalvik wipe too. Just set and forget
Every option need to be 'on' or 'off' except the drop cache interval what is need to be a number (calculated in hour) and the LMK mode what is need to be a plain text described above
The config file is a simple text file, you can edit with your favourite file editor, but dont made any changes before the '='
You can follow what has been done in the /data/tweakaio/logs/tweakaio.log file
The dalvik cache mover has a separate log file called /data/tweakaio/logs/dalvik_mover.log
If you have any issue let me know, with the connected tweaklogs part!

Update 2012.09.06.:
- Optimized minfree values
- Added read ahead speed tweak
Update:
- Provided a config editor app, download from the first post attachment

Hy vadanko, thx for your work... I will try tomorrow
Best regards
Craxx
Gesendet von meinem GT-I9300 mit Tapatalk 2

Nice work mister.
After installation the files will added, and not replaced, in default unit.d folder, so we must delete any other unit.d inside as i understand.
Are there any build.prop tweaks (lines) thet we must delete after installation?
Is it compatible with stock kernel too?
Thanks.

eliashadow said:
Nice work mister.
After installation the files will added, and not replaced, in default unit.d folder, so we must delete any other unit.d inside as i understand.
Are there any build.prop tweaks (lines) thet we must delete after installation?
Is it compatible with stock kernel too?
Thanks.
Click to expand...
Click to collapse
If you have any other init script what is adjusting memory management or sysctl values, then you can delete this files, but not necessary.
About the build.prop this script doesn't affect the build.prop, so do not change anything.
If you using memory cleaner/optimizer app like autokiller memory optimizer, or any memory booster app you need to stop all of this app, this script will handle everything.

Very nice work.especially like sqlite and dalvik cleaner/mover option.
Thanx m8

Well, the Apk on DHL8 just FC
Sent from my GT-I9300 using xda app-developers app

Hy vadonka,
Can't test until now because I have no init.d support with kernel phenomenal or perseus...
Hope it will be solved today and then i test...
Gesendet von meinem GT-I9300 mit Tapatalk 2

The sgs3 TweakAIO apk f/c when i tried to open it.
Im on LH9.
And also there in no sgs3Tweak config in my data (that's why the app f/c???).
Thanks.

Hi Vadonka, How can this script can save more battery because i already using undervolt kernel GalaXsih 4.0 kernel..Isit will work in this kernel or will have some conflict or either suitable for stock kernel

vadonka said:
Update:
- Provided a config editor app, download from the first post attachment
Click to expand...
Click to collapse
Tried it "old fashion" (editing tweakaio.conf by hand), worked pretty fine that way. Now there's an app ! Sweet ! It works fine on LH1 base (CodecROM 7.7), and the app confirm changes applied by hand to tweakaio.conf are working.
Thanks !

eliashadow said:
The sgs3 TweakAIO apk f/c when i tried to open it.
Im on LH9.
And also there in no sgs3Tweak config in my data (that's why the app f/c???).
Thanks.
Click to expand...
Click to collapse
I had the same issue, but I solved it by creating a folder in /system/etc named init.d, then I flashed the script in cwm again, and voila'! It worked.
Sent from Hell with help from XDA

if the /data/tweakaio/tweakaio.conf file is not exsist or have 0 byte size or the permission is not 0777 then the app will FC. in some ROM also FC if this file is exsist but i dont know why yet this is not my app one of my friend wroted for my O2X init script. im just redesigned a little. im trying to figure out why FC on some ROM.
if the tweakaio.conf file is not exsist the init script will create at the next reboot automatically. at least it should be create

jothi2lingam said:
Hi Vadonka, How can this script can save more battery because i already using undervolt kernel GalaXsih 4.0 kernel..Isit will work in this kernel or will have some conflict or either suitable for stock kernel
Click to expand...
Click to collapse
well not only the undervolt can save battery
for example this parameters...:
dirty expire centisecs
dirty writeback centisecs
dirty ratio
dirty background ratio
plus the VM related parameters, timeouts, etc...
all of them together affected the battery life.

Huppen said:
I had the same issue, but I solved it by creating a folder in /system/etc named init.d, then I flashed the script in cwm again, and voila'! It worked.
Sent from Hell with help from XDA
Click to expand...
Click to collapse
vadonka said:
if the /data/tweakaio/tweakaio.conf file is not exsist or have 0 byte size or the permission is not 0777 then the app will FC. in some ROM also FC if this file is exsist but i dont know why yet this is not my app one of my friend wroted for my O2X init script. im just redesigned a little. im trying to figure out why FC on some ROM.
if the tweakaio.conf file is not exsist the init script will create at the next reboot automatically. at least it should be create
Click to expand...
Click to collapse
The file in init.d is ok.The problem for me is that i havent the config which i can manage the TweakAIO in /data.
So thats the reason that the app f.c, as i thought...
I hope to find the solution mister vadonka...
Revolution rom based on LH9.
edit: Im using wannam repack stock kernel.There is a script in init.d that it cant deleted (it recreated in every boot).
The script is:
Code:
#!/system/bin/sh
# WanamLite tweaks
sysctl -p
/system/bin/setprop pm.sleep_mode 1
/system/bin/setprop ro.ril.disable.power.collapse 0
if [ -e /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold ]; then
echo "80" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold
fi
if [ -e /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate ]; then
echo "60000" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate
fi
if [ -e /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor ]; then
echo "2" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor
fi
if [ -e /sys/devices/system/cpu/cpufreq/pegasusq/down_differential ]; then
echo "10" > /sys/devices/system/cpu/cpufreq/pegasusq/down_differential
fi
Its ok to have this and yours both???

@eliashadow
The only way i could delete s script in wanamlite roms was using rom toolbox.
But first i had to run from scripter a script to mount system as R/W.
I know it should had been mounted automatically but try it this way
Sent from my GT-I9300 using xda premium

eliashadow said:
The file in init.d is ok.The problem for me is that i havent the config which i can manage the TweakAIO in /data.
So thats the reason that the app f.c, as i thought...
I hope to find the solution mister vadonka...
Revolution rom based on LH9.
edit: Im using wannam repack stock kernel.There is a script in init.d that it cant deleted (it recreated in every boot).
The script is:
Code:
#!/system/bin/sh
# WanamLite tweaks
sysctl -p
/system/bin/setprop pm.sleep_mode 1
/system/bin/setprop ro.ril.disable.power.collapse 0
if [ -e /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold ]; then
echo "80" > /sys/devices/system/cpu/cpufreq/pegasusq/up_threshold
fi
if [ -e /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate ]; then
echo "60000" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_rate
fi
if [ -e /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor ]; then
echo "2" > /sys/devices/system/cpu/cpufreq/pegasusq/sampling_down_factor
fi
if [ -e /sys/devices/system/cpu/cpufreq/pegasusq/down_differential ]; then
echo "10" > /sys/devices/system/cpu/cpufreq/pegasusq/down_differential
fi
Its ok to have this and yours both???
Click to expand...
Click to collapse
this script is manage the cpu governor. you can leave this for sure. it doesnt interfered with my script.
Sent from my GT-I9300 using Tapatalk 2

mariosraptor said:
@eliashadow
The only way i could delete s script in wanamlite roms was using rom toolbox.
But first i had to run from scripter a script to mount system as R/W.
I know it should had been mounted automatically but try it this way
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
Thanks but it didn't work for me too.The script recreated again after rebooting.
Edit:thanks mr vadonka.Now I'm ok.
Sent from my GT-I9300 using Tapatalk 2

eliashadow said:
Thanks but it didn't work for me too.The script recreated again after rebooting.
Edit:thanks mr vadonka.Now I'm ok.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Really weird
But as long as the script does not run, if there was a chance of conflict between the two scripts now is eliminated by renaming it.
Edit: if you rename it and reboot, do you then have 2 files ( the renamed one and the correct).
I flashed wanam's kernel but cannot recreate. It gets deleted correctly.
Sent from my GT-I9300 using xda premium

mariosraptor said:
Really weird
But as long as the script does not run, if there was a chance of conflict between the two scripts now is eliminated by renaming it.
Edit: if you rename it and reboot, do you then have 2 files ( the renamed one and the correct).
I flashed wanam's kernel but cannot recreate. It gets deleted correctly.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I edited it inside and changed the lines, not the name of the script.
But if the dev here said that is ok, everything is ok
Sent from my GT-I9300 using Tapatalk 2

[Q] Change I/O scheduler

Hi,
I'm running stock 2.3.6 (rooted). By default phones uses "deadline" I/O, but have also "noop". How can I choose "noop" using the terminal? I've tested cpu frill but i'm getting a error.
In few words.
What are the commands to uses "noop" and the one to "deadline", if I wish to go back.
BR.

commands are different
you can try nstools app
it will do the work

dheeraj (dhlalit11) said:
commands are different
you can try nstools app
it will do the work
Click to expand...
Click to collapse
Tested nstools. It keeps reverting to deadline after reboot. Don't know why, but from all the scripts that I've inside /init.d (with the right permissions) the only that works is the Link2SD.

stock roms don't have init.d support by default
so just untick the use init.d option available in setting tab of nstools
and your settings would be sticked to what you choose even after a reboot

What you can do is wipe cache/dalvik cache from custom recovery and then trying nofrills again

[Q&A] [Kernel][CPU OC][GPU OC][F2FS] CroPol kernel

Q&A for [Kernel][CPU OC][GPU OC][F2FS] CroPol kernel
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

doesn't work
I've got an error on boot, something like 0x0000d0d2. I got it with all versions. I use the latest cm10.2 by novaFusion with PurePerformanceX installed.

vietnam131 said:
I've got an error on boot, something like 0x0000d0d2. I got it with all versions. I use the latest cm10.2 by novaFusion with PurePerformanceX installed.
Click to expand...
Click to collapse
Afaik it doesn't support 4.3.x ROMs. Try any 4.4.x ROM.

Ok, I will try. But if you can make this kernel for previous versions of Android, it would be nice.

i cant get 1150/2000 mhz
what cpu governor and i/0 scheduler are you guys running to get 1150/2000 mhz? i have the normal s3 mini, not the nfc version and im running cyanogenmod.

snakeboy1011 said:
what cpu governor and i/0 scheduler are you guys running to get 1150/2000 mhz? i have the normal s3 mini, not the nfc version and im running cyanogenmod.
Click to expand...
Click to collapse
Try pegasusqplus+sioplus.

mauam said:
Try pegasusqplus+sioplus.
Click to expand...
Click to collapse
what should i put as the min frequency?

snakeboy1011 said:
what should i put as the min frequency?
Click to expand...
Click to collapse
100 or 200. You need to try by yourself

what ROM do you use as I don't think CyanogenMod supports 1150/2000mhz?
mauam said:
100 or 200. You need to try by yourself
Click to expand...
Click to collapse
Sorry for your time

deep sleep bug? reboot bug? voltage limits? persistent config by userinit.sh?
Hello!
I got several questions regarding the usage of this kernel's voltage and clocking/voltage options:
1. Everytime my mobile goes to deep sleep, it sets maximum clock to 400MHz and minimum clock to 100MHz. It stays so after enabling and while using the phone. It's horrible slow. So I got to increase maximum clock by hand everytime the phone was in deep sleep before.
What's the problem there?
2. After rebooting the maximum clock is always reset to 1000MHz, although i had set it to 1150/1200MHz before.
Why?
3. I noticed 1200MHz not being completely stable on my device. So I wanted to increase the voltage for step9.
In /sys/kernel/liveopp/arm_slot09 i saw the default hex value for VARM was 0x3f. So I tried increasing this to 0x40 and 0x41, but the voltage shown in this file didn't increase anymore.
3a) So is the voltage capped at 1362,5000mV or is it just not displayed correctly?
3b) Will increasing Varm to more than 0x3f do anything at all?
Also I've seen the voltage called Vbbx (default value for step9: 0xff)
3c) What exactly is this voltage, and how does it go together with Varm?
3d) Is there a way for increasing voltage any further than 0x3f for Varm and 0xff for Vbbx?
4. For persistence I tried automatically setting changed voltage parameters on boot, using userinit.sh.
The file didn't exist before, so i created it as /sys/local/user/userinit.sh, set the perissions to 755, and added the following content:
Code:
#!/system/bin/sh
echo set_volt= 1 > /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x41 > /sys/kernel/liveopp/arm_slot09
But the script doesn't work. After rebooting varm for step09 is always at default value (0x3f).
4a) Why doesn't this work?
4b) I think it maybe is not working because the above command needs to be run as root, but how could i do this in userinit.sh without sudo?
Many thanks for patience and help!

Elmarigo said:
1. Everytime my mobile goes to deep sleep, it sets maximum clock to 400MHz and minimum clock to 100MHz. It stays so after enabling and while using the phone. It's horrible slow. So I got to increase maximum clock by hand everytime the phone was in deep sleep before.
What's the problem there?
Click to expand...
Click to collapse
First of all, notice that deep sleep is a power state in which the CPU has a very low voltage consumption.. Therefor its not even clocked at 100 Mhz. With this Kernel, when screen is off, the clock is set 100-400 MHz if its needed (by wake locks).
Now, I see that the problem here is that it stays when you wake the phone. What ROM are you using? You could try flashing the Kernel again.
Elmarigo said:
2. After rebooting the maximum clock is always reset to 1000MHz, although i had set it to 1150/1200MHz before.
Why?
Click to expand...
Click to collapse
Unless this values are set compiled in kernel, you will have to manually set everytime you boot. But a quick solution is to enable the "apply settings on boot" on the app that you are using to OC. (You can use ROM Toolbox if your ROM doesn't have built in this options)
Elmarigo said:
4. For persistence I tried automatically setting changed voltage parameters on boot, using userinit.sh.
The file didn't exist before, so i created it as /sys/local/user/userinit.sh, set the perissions to 755, and added the following content:
Code:
#!/system/bin/sh
echo set_volt= 1 > /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x41 > /sys/kernel/liveopp/arm_slot09
But the script doesn't work. After rebooting varm for step09 is always at default value (0x3f).
4a) Why doesn't this work?
4b) I think it maybe is not working because the above command needs to be run as root, but how could i do this in userinit.sh without sudo?
Click to expand...
Click to collapse
Try deleting the space between "1" and ">" like this:
Code:
#!/system/bin/sh
echo set_volt= [B]1>[/B] /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x4[B]1>[/B] /sys/kernel/liveopp/arm_slot09

xhhb said:
First of all, notice that deep sleep is a power state in which the CPU has a very low voltage consumption.. Therefor its not even clocked at 100 Mhz. With this Kernel, when screen is off, the clock is set 100-400 MHz if its needed (by wake locks).
Now, I see that the problem here is that it stays when you wake the phone. What ROM are you using? You could try flashing the Kernel again.
Click to expand...
Click to collapse
Hello!
I'm using Carbon Rom by novafusion. There's an update from 27.10. now, and I'll see later if this helped against this particular problem!
xhhb said:
Unless this values are set compiled in kernel, you will have to manually set everytime you boot. But a quick solution is to enable the "apply settings on boot" on the app that you are using to OC. (You can use ROM Toolbox if your ROM doesn't have built in this options)
Click to expand...
Click to collapse
In Carbon there's an option for applying saved values on boot. I used these and I also tried CoCoreManager, but both didn't apply my saved config although I had enabled this setting.
xhhb said:
Try deleting the space between "1" and ">" like this:
Code:
#!/system/bin/sh
echo set_volt= [B]1>[/B] /sys/kernel/liveopp/arm_slot09
echo set_varm = 0x4[B]1>[/B] /sys/kernel/liveopp/arm_slot09
Click to expand...
Click to collapse
Ok, I will try this. Is userinit.sh being executed as root by automatic?
Thank you!

Ok, i found multiple bugs in my script and corrected these.
The script currently is like:
Code:
#!/system/bin/sh
echo set_volt=1 > /sys/kernel/liveopp/arm_step09
echo varm=0x41> /sys/kernel/liveopp/arm_step09
The commands are working from terminal/SSH, but playing them in /data/local/userinit.sh doesn't change anything after reboot. (file is marked as executable!)
So can anyone help please how to make this working?
I still believe it's maybe because of the script not being executed with root permissions, but I'm not sure about that and I don't know how to work around this without a sudo command.
Also I still could use help with my remaining questions from my older post: http://forum.xda-developers.com/showpost.php?p=56343298&postcount=10
Thank you!
PS: this 10message restriction for 'new users' doesn't seem like a working way for keeping the forum's content at good quality.
I'm forced to writing in Q&A-Thread, while the creator and the other most experienced users of original thread don't even seem to look here.
Aswhile, the 'more experienced' users, having more then 10messages, in original thread are keeping the most experienced users busy, asking questions that are even way more basic than mine, but regarding the same topic (persistent undervolting). So I can't help these users and no one from that other thread can help me

Not working on miui
I flashed it on miui v5 http://forum.xda-developers.com/showthread.php?t=2647472 and it won't boot!!! Need help!!!!

chaudhary1122 said:
I flashed it on miui v5 http://forum.xda-developers.com/showthread.php?t=2647472 and it won't boot!!! Need help!!!!
Click to expand...
Click to collapse
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.

Elmarigo said:
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Click to expand...
Click to collapse
Nope, I guess not. So I'll give it a try now!!! Thanx!!!!

Elmarigo said:
Did you delete your Cache and reboot twice?
If you already did, then flash your full ROM again.
Click to expand...
Click to collapse
Did it but still not working!!! Not booting first the Samsung startup screen with the name and model is replaced with a white screen and then comes a black screen with red text at the top left corner I don't actually remember what it says!!!! Need help!!!

wifi and bt not work
I have a problem with this kernel , no wifi or bluetooth install on virginity v14 rom with option 2 for stock based rom otherwise I will work perfect kernel 1.1 ghz wifi but I need someone a suggestion? Do not attempt to try to option 1 cm based on that I guess should be different thanks

chaudhary1122 said:
Did it but still not working!!! Not booting first the Samsung startup screen with the name and model is replaced with a white screen and then comes a black screen with red text at the top left corner I don't actually remember what it says!!!! Need help!!!
Click to expand...
Click to collapse
I think for saving your phone you should flash your previous ROM (the one you had on that phone before) using Odin from a PC. If this doesn't help either you should try Full Wipe and flash stock ROM.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2159660
LaInfluenza said:
I have a problem with this kernel , no wifi or bluetooth install on virginity v14 rom with option 2 for stock based rom otherwise I will work perfect kernel 1.1 ghz wifi but I need someone a suggestion? Do not attempt to try to option 1 cm based on that I guess should be different thanks
Click to expand...
Click to collapse
I didn't see anyone else trying the kernel on stock-ROM, yet. You should write a PM to ChronoMonochrome about this, so he can tell the developer.

Elmarigo said:
I think for saving your phone you should flash your previous ROM (the one you had on that phone before) using Odin from a PC. If this doesn't help either you should try Full Wipe and flash stock ROM.
Follow these instructions: http://forum.xda-developers.com/showthread.php?t=2159660
I didn't see anyone else trying the kernel on stock-ROM, yet. You should write a PM to ChronoMonochrome about this, so he can tell the developer.
Click to expand...
Click to collapse
The fact that the kernel is pretty good, I loved it but I need the wifi I use it all day and does not serve me well beyond virginity v14 rom that I really like, I tried it on the newest cm11 but I do not really like this rom I hope for the next update will fix this kernel as serious buenisimo roms have oc in stock or stock -based.

[FIX] SCRFIX, a fix for DT2W/Sw2W lock screen freeze

The included file is a binary that runs a daemon that fixes the lockscreen freeze that happens with dt2w/sw2w kernels. It requires busybox to be installed on your device. If your screen is still unresponsive the first time you attempt to wake your device; shut your screen off, wait a couple seconds, and try again and it will usually work.
The executable will do nothing on its own, so you must either have it start on boot with an init.d script or manually in terminal. It has to be ran as root.
To install the zip boot into recovery and install it using your recovery's standard install method, like installing a kernel or ROM.
To install the binary simply put the file in /system/bin and give it executable permissions
Recovery installer zip:
https://docs.google.com/file/d/0B_hgNZE_j5sVd0Itb1V4RGhhOGc/edit?usp=docslist_api
Binary:
https://docs.google.com/file/d/0B_hgNZE_j5sVLU9wdDEzamFUV0U/edit?usp=docslist_api
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.

What this app does? How did you find it?

and after put in system/bin what to do next? how to run it?

Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.

I use SManager , give to scrfix su and boot privs it will work?

I haven't used that app personally, but it sounds like it should. Its normal for the program to seem like it exits because it spawns a child process that runs in the background that is owned by init (PID 1)
Or if you want to launch it manually, you can launch it in Terminal Emulator, but it will need started again on each reboot.

There is now a link to an installer zip for installation from recovery mode that comes with an init.d script included, for anyone using this method, please let me know if you encounter any issues with it. You may need to enable "trust system user" in your su application for it to work. The recovery installer was made with the ZipMe application.

Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk

imranaryan said:
Will this enable DT2W in cm12
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
If you will read the title, you would realize that this mod is a fix for a very common problem faced by dt2w users. If you want dt2w, flash a custom kernel like optimus.

I just tried this on my Moto E 2015 and I ended up flashing a zip I modified when I tried it on my Moto G some time ago. I've found that it does not work when applying dt2w with an app such as Kernel Adiutor. It does work if you apply dt2w with an init.d script, and make it so the scrfix script is ran before the dt2w script. You just have to change the numbers in the beginning of the script name to something like 01 and 02 with the scrfix script having the smaller number.

Thanks for the info, I may upload an updated zip that has the name change to make sure it runs first. Some times too (on my phone atleast) when the screen isn't responsive I'll turn the screen off for 3-5 seconds and try again and it'll usually respond.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!

elrod16 said:
Run it from the terminal command line, and it will continue to run in the background.
Its a quick and dirty fix that resets the touch screen driver when the screen is off.
If you copied the file to system bin you should be able to just type "scrfix" in your terminal and it will run in the background until your next reboot.
Alternatively you can just call it in an init.d script to have it start automatically on every boot.
Click to expand...
Click to collapse
i know this is an old forum but I just found it. How can I call it in an init.d script?

Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!

elrod16 said:
Just adding the line
scrfix
to a script.
---------------------------------------------------
Please thank if my software has helped you and please leave logs and descriptions of problems if my software did not work for you.
Please donate at:
http://www.PayPal.me/elrod16
Every bit helps, thanks!
Click to expand...
Click to collapse
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs

V-Droid said:
Would this be correct?
#!/system/bin/sh
/system/bin/scrfix
exit 0
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------

amarc78 said:
Yes, you'll also need another script with this:
#!/system/bin/sh
echo "2" > /sys/android_touch/doubletap2wake
This one needs to run after the previous script so you'll have to name them 98scrfix and 99dt2w. Also make sure their permissions are 0755.
---------- Post added at 08:46 PM ---------- Previous post was at 08:35 PM ----------
Click to expand...
Click to collapse
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs

V-Droid said:
Im not able to change the script permissions, tried root browser but gave me an error. How can I change the permissions?
By the way sorry for the constant questions
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
Try Root Explorer or ES File manager. As long as your rooted it should work.

amarc78 said:
Try Root Explorer or ES File manager. As long as your rooted it should work.
Click to expand...
Click to collapse
Still no luck, I tried root browser, root explorer and es file explorer all of them gave me the same error.
I also tried moving the file from the external SD card into the internal memory.
By the way, the way I create the scripts is in a .txt file, is this correct?
Sent from my Moto E 2015 using XDA Labs

V-Droid said:
Still no luck, I tried root browser, root explorer and es file explorer
Sent from my Moto E 2015 using XDA Labs
Click to expand...
Click to collapse
You need to put them in /system/etc/initd not on your sdcard.

amarc78 said:
You need to put them in /system/etc/initd not on your sdcard.
Click to expand...
Click to collapse
Thank you very much for all of your help, finally managed to change the permissions :laugh:
Sent from my Moto E 2015 using XDA Labs

[TWEAKS][MOD] L SPEED Mod for Asus x86 devices - OG thread is compatible now

**I did not write these scripts, just updated the flashable zip for our x86 Asus phones**
**All work done by @Paget96**
ORIGINAL Mod Thread here : http://forum.xda-developers.com/android/software-hacking/tweak-l-speed-v1-0-02-02-2015-t3020138
@Paget96 has added an x86 version to the original thread with the (more appropriate) fixes!! Go discuss there!
Big thanks to him. Use the v2.4 Test3 or greater "x86" file
Reqs:
1) Need root
2) Need Custom recovery (TWRP)
3) Need kernel with init.d support (like @TheSSJ 's here: http://forum.xda-developers.com/zenfone2/development/project-t-custom-kernel-zenfone-2-t3150822)
** Use v44 or greater for proper init.d support
Download zip from the original thread
and flash in recovery.
Then look at the original thread for config options while you're in there
Added the Emergency Uninstaller zip as well. (i think you still need to use this version, until an x86 version is up there too)

Ch-Ch-Ch-Ch-Changes
Jul 23 2015: OG thread updated by dev. Updated flashing instructions in OP (mods can probably lock this thread)
Jul 15 2015: Fixed script to properly set perms on /system/bin/LS; Added Emergency Uninstaller zip
Jul 14 2015: Initial upload. Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms

I would have expected that some parts of my kernel would fight against this tweak, nice to see that it seems to work

Yean I don't know that some of the governor stuff is working 100%, still messing around with it .

Thanks man Been using TheSSJ kernel with this pack of tweak. Its awesome Thanks to both of you

Added in index, thanks for updating the mod!

taylor.fowler said:
@aziz07 Here you go.
Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms
Click to expand...
Click to collapse
Thanks! Working A++
Edit: I tried running the script from terminal with no luck. I have to cleanup the alpha version first with the provided uninstaller by Paget96. Its a great idea to have the uninstaller zip working with x86.
++Uninstaller patched, permssions fixed, kudos @taylor.fowler

Need help can't get to run in terminal
Sent from my ASUS_Z00AD using Tapatalk

taylor.fowler said:
@aziz07 Here you go.
Needed to use the update-binary from Asus to work with our x86 architecture and replace all the set_perms with set_metadata's. Apparently the update-binaries from Asus don't include set_perms
Click to expand...
Click to collapse
how can i do that because not work for me

Have u guys tried with Kernel Adiutor?

su
LS > permission denied
selinux already permissive

chobztopz said:
su
LS > permission denied
selinux already permissive
Click to expand...
Click to collapse
I've got it too

The permission for LS file in system/bin is wrong. It should be 0755 (rwx rx rx) then it will done on terminal emulator

lordpipa said:
Have u guys tried with Kernel Adiutor?
Click to expand...
Click to collapse
I am using that.. But y u asked?
And guys only cleaner works it seems, he added logs for all option thankfully and only cleaner having log, others are blank, I can't run the options of LS..
mustatir said:
The permission for LS file in system/bin is wrong. It should be 0755 (rwx rx rx) then it will done on terminal emulator
Click to expand...
Click to collapse
Yep thanks, OP can you edit the updater script please...
After that script enable also same result, no log entered in those files..
Kernel samepage merging didn't came, no swap.. kernel auditor can enable kernel samepage merging even without this script. .. .

ansebovi said:
I am using that.. But y u asked?
And guys only cleaner works it seems, he added logs for all option thankfully and only cleaner having log, others are blank, I can't run the options of LS..
Yep thanks, OP can you edit the updater script please...
After that script enable also same result, no log entered in those files..
Kernel samepage merging didn't came, no swap.. kernel auditor can enable kernel samepage merging even without this script. .. .
Click to expand...
Click to collapse
Hrmph. I must have Ul'd the wrong version. I had the same issue. Will re-up in a couple hours.

@ansebovi cause u can use it for some of the init scripts.

Hmm, mine does all have logs. Yep, I had to set LS permissions to all in /system/bin folder. I think it might be because I still have the old alpha version files and I can't flash the uninstaller as it needs the x86 code.
Edit: ++Uninstaller patched, permssions fixed, kudos @taylor.fowler

Checked the updater-script. All functions are already available in TWRP itself, so normally you don't even need the updater-binary in the zip file, maybe this makes also the uninstaller work if you just delete the updater-binary from the zip file

TheSSJ said:
Checked the updater-script. All functions are already available in TWRP itself, so normally you don't even need the updater-binary in the zip file, maybe this makes also the uninstaller work if you just delete the updater-binary from the zip file
Click to expand...
Click to collapse
OK, so I fixed the updater-script (and found another error with setting the permissions on init.d). Apparently I had changed them to 0775 instead of 0755 :silly:
Also added the emergency uninstaller script too.
@TheSSJ I dont think that's how flashable zips work, but i tried anyhow. No dice...

taylor.fowler said:
@TheSSJ I dont think that's how flashable zips work, but i tried anyhow. No dice...
Click to expand...
Click to collapse
Bummer...was convinced this would work...twrp code at least shows that it executes updater-binary if present,otherwise it interprets the script itself...
Sorry!