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
Related
So i have installed Darky's 9.2 ROM and i chose the Speedmod kernel...
and i have some questions about this mode...
when i go into recovery and choose the speedmod
i see this:
Lagfix Options:
Disable lagfix: convert DATA to RFS
Enable lagfix Convert data to ext4
Convert System to Ext4/RFS
Tweak Options:
IO scheduler + Remout noatime
Kernel VM management
Kernel scheduler
Misc battery tweaks
Enable CIFS support
Enable TUN support
Enable IPv6 privacy
Enable Android logger
BLN Options:
Turn BLN on
Turn BLN off
So after i have flashed the ROM i have enabled the Lagfix and i have converted the system to ext4...then i have entered the Tweak options and enabled the Misc battery tweaks..
But my question is what are the other tweaks? and how does it help?
and does the BLN saves battery? because it lights up only the Backlight keys and not the whole screen...
Anyone? >.<
Hi, please check out this thread: http://forum.xda-developers.com/showthread.php?t=813309
well... i have read it already... but it is to complicated for me to understand >.<"
can't you just in a few words what each tweak does? ^^
It's vague. I would like to learn more about it.
I get into recovery mode, and i see those options, but i dont even know what they do or if i'm abling or disabling them?
Before I start, let me clarify that I am using S.U.R.F.A.C.E rom and Galaxian kernel.
1. I always get a force close when I access : Settings > Wireless and Network > Synchronise.
and Setting Lockscreen Wallpaper > Gallery.
This two problem has been with me for the longest time ever. I'm not too bothered by this. But still, I found it odd.
2. Oc/Uv profile always resets itself even after 'apply at boot' has been checked.
3. Per app-config in Chainfire does not work regardless of app. Settings can be checked, but does not actually apply any of them (Defaults works)
4. My phone seems to be running slower in EXT 4 then RFS for seemingly no reason whatsoever. ( Unable to 'confirm' this, but the occasional lag and freeze occurs) Would like to know of a way to check if EXT4 is really enabled. I might just be me, but Galaxian kernel simply runs and tells me ext4 is applied, which is new to me since all the ext4 I ever applied in other kernels always does the restore and backup, and is seemingly absent here.
Sorry if such issues has been asked before, but I could not pinpoint someone with the exact same situation as me however hard I searched.
Thank you for reading this extremely lengthy post. And help is greatly appreciated.
Use setcpu to set oc/uv and they should remain after boot. Run adb or terminal emulator and type
mount |grep ext4
and this will show any file systems using ext4 . Galaxian recognises ext4 file systems so will keep previous
Enter recovery, wipe cache, dalvik , fix permissions and reboot (maybe twice)
Sent using geek power
Pls have someone of you tried the supercharger v6 script? What was the result? Was it easy to install?
Sent from my LG-P990 using Tapatalk
its great. i installed it when still in stock and still using it with neoblaze kernel.
its already fast even without the oc kernel. you wont see higher number on benchmark apps. but you will feel the difference.
this is from the supercharger thread
http://forum.xda-developers.com/showthread.php?t=991276
Requirements:
1. Rooted Phone....
2. Script Manager or Terminal Emulator to run the script. Stock ROMs can also use SM to load up boot scripts!
3. Busybox 1.18.2 OR LOWER - 1.18.3 or newer are VERY much a hassle with errors that should NOT be errors!
4. AutoStart Script by me - Enables Stock ROMS (Milestone) to utilize etc/init.d for boot scripts.
Installing/Using:
1. Download the attached V6_SuperCharger_for_Android*.txt script and save to your sdcard.
... Do NOT run the V6 SuperCharger install script at boot!
2. Load the script (V6_SuperCharger_for_Android*.txt) into Script Manager and select "Run as Root."
3. Touch the screen for the soft keyboard or slide out the keyboard and get SuperCharged! Just pick an option!
4. READ the script's output!
5. Afterwards, READ the html HELP FILE in the root of your SD Card!
6. Disable "Lock Home in Memory" if your ROM has this option.
7. Optional: For a quick status check, you can put a Script Manager widget for V6 SuperCharger on you desktop
for me, i use the 11th option (oom grouping fixes + hard to kill launcher) then reboot.
cyanogen doesent need the autostarter script ore does it?
Ok,thanks. I am running it now too and it feels really faster
Sent from my LG-P990 using Tapatalk
Hi, may i know which option did you choose? I chose the 8th one(the MAX one) but i don't feel such many differences...
If my memory is correct, i used the option 7, max RAM 512 and hard to kill launcher
It is also for CyanogenMod 7?
Hi, I tried to apply ext4 lagfix via CF ext4 Manager (CF-Root-ext4-v1.3-Addon.apk) , data was converted successfuly, system was not converted due not enough free space, which is normal as Chainfire said.
Please note that when first using the tool to convert, you will probably notice /system is not converted. If this happens, it is because /system does not have enough free space for the extra space overhead of ext4. You will need to free up some space on /system before the conversion will succeed.
Click to expand...
Click to collapse
Running 2.3.4 JVQ stock firmware with CF root.
But after reboot ext4 app have all choices grayed, so I cannot convert system or any other partion to ext4 or back.
It show "No rfs/ext4 partions found" and "unknow ,0.0MB, 0.0MB total"
Any tips appreciated. Thanks in advance
Roman
Which kernel are you running? Try changing kernel eg: Semaphore or galaxian. Then do a wipe cache and dalvik cache
Runnig CF-Root-XX_UNK_JVQ-v3.7-CWM3RFS on stock JVQ without other changes.
Thanks for advice
Problem is, that many kernels have logging disabled, I need logcat, ddms for developing
EDIT: Flashed semaphore, there is greenscreen while lock/unlock screen(minor issue),but other things seems fine, thanks!
semaphore has logging enable script
Quote :
"In order to control voodoo sound and BLN you have to download Voodoo Control and BLN control applications respectively from android market.
The max CPU frequency is by default 1Ghz.
You may use applications like Voltage Control or Pimp my CPU to control OC/UV.
In order to load various modules of the kernel copy the respective script from /res/scripts to /system/etc/init.d directory and give the script executable permissions. This is optional. It is needed only if you want to use this functionality. The scripts:
- enable_conservative (load conservative governor module)
- enable_cifs (load cifs module)
- enable_netfilter (load netfilter modules for firewall or WiFi, USB tethering)
- enable_tun (load tun module)
- enable_deadline (load the deadline I/O scheduler module)
- enable_binfmt_misc
- S05_enable_oc replaces enable_ocuv since 1.6.0 (enable overclocking)
Other scripts:
- enable_sm_cold script for SpeedMod cold preset
- enable_sm_warm script for SpeedMod warm preset
- enable_sm_neutral script for SpeedMod neutral preset (please note that this is enabled by default)
To enable logcat run the enable_logger script in res/scritps and reboot your phone."
Here is the link
Hope this helps.
Hello, I'm using speedmod kernel k3-3, ondemand governor and wanted to change up-threshold and sampling rate, but after i reboot phone it goes to default. Is it possible to change it permanently? thnx
EdgaBimbam said:
Hello, I'm using speedmod kernel k3-3, ondemand governor and wanted to change up-threshold and sampling rate, but after i reboot phone it goes to default. Is it possible to change it permanently? thnx
Click to expand...
Click to collapse
Set CPU, apply on boot ?
Boy124 said:
Set CPU, apply on boot ?
Click to expand...
Click to collapse
system tuner, rom manager, setcpu, antutu cpu... none of them works after reboot settings goes to default.
Extract attached file and copy 99cpu to init.d folder and grant it all the permissions.
I have set Up Threshold to 95% and Sampling Rate to 45000.
You can change the values, just edit 99cpu.
Reboot and check if values stick. If it does not, download Script Manager from the play store. In Script Manager, browse to init.d > select 99cpu > tap Su and Boot > tap save.
Exit and reboot.
PS
---
I think that values won't stick. I always had problems with init.d scripts on SpeedMod kernel. Please reply if values stick.
Boy124 said:
Extract attached file and copy 99cpu to init.d folder and grant it all the permissions.
I have set Up Threshold to 95% and Sampling Rate to 45000.
You can change the values, just edit 99cpu.
Reboot and check if values stick. If it does not, download Script Manager from the play store. In Script Manager, browse to init.d > select 99cpu > tap Su and Boot > tap save.
Exit and reboot.
PS
---
I think that values won't stick. I always had problems with init.d scripts on SpeedMod kernel. Please reply if values stick.
Click to expand...
Click to collapse
ok thank you vm, going to try
edit: values didnt change. seems that this kernel not supporting init.d scripts or what?
edit2: it changed after i ran script via script manager, will try again to reboot
edit3: seems that after reboot need manually boot script. Btw init.d folder what permissions should have?
EdgaBimbam said:
ok thank you vm, going to try
edit: values didnt change. seems that this kernel not supporting init.d scripts or what?
edit2: it changed after i ran script via script manager, will try again to reboot
edit3: seems that after reboot need manually boot script. Btw init.d folder what permissions should have?
Click to expand...
Click to collapse
Anything you want to run on boot in the init.d should have the rwx-rwx-rwx permissions
carbonassassin said:
Anything you want to run on boot in the init.d should have the rwx-rwx-rwx permissions
Click to expand...
Click to collapse
yeh thanks btw i have put this script at init.d
#!/system/bin/sh
# Up Threshold and Sampling Rate - Boy124
echo "70" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo "45000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
have set permissions to rwx-rwx-rwx and after reboot it doesnt work, even with script manager su and boot enabled, after reboot it doesnt work. Works only after running script manually, wtf is that
maybe my tweaks are atm useless, maybe it doesnt starts at boot
On CF-Root 5.6, it changes up threshold but sampling rate remains default.
See this http://forum.xda-developers.com/showpost.php?p=26582847&postcount=72
---------- Post added at 12:12 AM ---------- Previous post was at 12:06 AM ----------
carbonassassin said:
Anything you want to run on boot in the init.d should have the rwx-rwx-rwx permissions
Click to expand...
Click to collapse
Thanks. I never bothered to learn about permissions.
Whenever I am confused, I grant all the permissions. And it works most of the time.
Boy124 said:
On CF-Root 5.6, it changes up threshold but sampling rate remains default.
See this http://forum.xda-developers.com/showpost.php?p=26582847&postcount=72
---------- Post added at 12:12 AM ---------- Previous post was at 12:06 AM ----------
Thanks. I never bothered to learn about permissions.
Whenever I am confused, I grant all the permissions. And it works most of the time.
Click to expand...
Click to collapse
hmmm so to sum up, speedmod kernel doesnt support init.d? maybe tomorrow will try franco kernel.