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?
Related
Hey everyone.
As I spend some time on studying Ext4 for the Galaxy S devices, working on Voodoo lagfix, and based on what I saw in mount logs it's possible that the performances could be increased without altering data integrity nor filesystem integrity in case of crash.
On /data, noauto_da_alloc is not used.
This option activates a sort of Ext3 emulation mode, which force sync on write close without sync.
It also comes with a speed penalty for SQLite writes, and is unneccessary when hardware barriers are enabled.
Barriers allow usage of delayed allocations without risk. Delayed allocations are the key to performance for modern filesystems.
as root:
Code:
mount -o remount,noauto_da_alloc /data /data
You can count on me to cook a kernel with this mount option as default
PS: this option is already used in Voodoo kernels for Galaxy S devices / has been chosen after extensive performance and reliability tests.
Okay, kevin_teslacoil run quadrant:
before:
<kevin_teslacoil> 1676 for the full quadrant bench mark
after:
<kevin_teslacoil> interesting
<kevin_teslacoil> 2422 this time
<GuiPer> :O
<Ibanez33> wtf?
I'm not a fan of quadrant, but used as a tool, it can give some useful infos
Also, note that this dramatic change in benchmark result won't be as incredible in real life usage.
But still, it's a better choice of configuration, using the filesystem driver like it should be given the hardware parameters.
Can this be implemented in Voodoo for SGS?
Reference, from man mount.
auto_da_alloc|noauto_da_alloc
Many broken applications don't use fsync() when noauto_da_alloc replacing existing files
via patterns such as
fd = open("foo.new")/write(fd,..)/close(fd)/ rename("foo.new", "foo")
or worse yet
fd = open("foo", O_TRUNC)/write(fd,..)/close(fd).
If auto_da_alloc is enabled, ext4 will detect the replace-via-rename and replace-via-trun‐
cate patterns and force that any delayed allocation blocks are allocated such that at the
next journal commit, in the default data=ordered mode, the data blocks of the new file are
forced to disk before the rename() operation is commited. This provides roughly the same
level of guarantees as ext3, and avoids the "zero-length" problem that can happen when a
system crashes before the delayed allocation blocks are forced to disk.
Click to expand...
Click to collapse
I'm trying this now.
jaju123 said:
Can this be implemented in Voodoo for SGS?
Click to expand...
Click to collapse
It's already implemented in Voodoo
Okay thanks
Still at it I see?
We lose this whenever we reboot I'm assuming?
Quadrant scores:
Before: 1672
After: 2334
Cook this into some good 1.2GHz OC/UV
We already know the Hummingbird can potentially hit 1.6
Its late, nevermid
Preparing a kernel with this option activated as default.
Anderdroid said:
We lose this whenever we reboot I'm assuming?
Quadrant scores:
Before: 1672
After: 2334
Cook this into some good 1.2GHz OC/UV
We already know the Hummingbird can potentially hit 1.6
Click to expand...
Click to collapse
fstab
10 char
Could you please implement this new mount option in your Vibrant "voodoo" kernels? Much appreciated! Thanks for your hard work, Curio!
zimphishmonger said:
Could you please implement this new mount option in your Vibrant "voodoo" kernels? Much appreciated! Thanks for your hard work, Curio!
Click to expand...
Click to collapse
Already told. This is the default mount option for Voodoo, after extensive analysis for both performance and filesystem+data integrity
I am using the latest of the trasig OC kernel for JPO and tried this options with no changes in quadrant. (1720)
deleted...................
Does this work on the galaxy tab?
futuregerald said:
Does this work on the galaxy tab?
Click to expand...
Click to collapse
no.
go to the galaxy tab section
Lagfix
So does this revert upon a reboot? I tried it on my SGTab and nothing happened, just want to make sure there is nothing i need to "undo" other than just rebooting. Thanks!
cba1986 said:
I am using the latest of the trasig OC kernel for JPO and tried this options with no changes in quadrant. (1720)
Click to expand...
Click to collapse
Doesn't work for me either on Galaxy S with JH3 (stock Telstra ROM other than root). Quadrant score actually dropped (916 to 896).
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.
https://rapidshare.com/files/2417081873/v63.zip
No wipe.
Base- http://wanamlite.com/forums/showthread.php?tid=2480 Thanks to Wanam
Kernel Siyah 1.4
15 toggles,suppressed subsequent overheat warnings, added not charge warning indicator into status bar.
Fixed wrong battery level in not charging condition. Optimized not charge animation. More contrast stock e-mail and status bar. Visible on direct sunlight and in car when using device as navigator.
4-way reboot menu.
All Israel and Russian regions/operators. Default - Cellcom.
All languages.
hosts file with disabled add's.
Memory optimizations (heapsize=96m) some other optimizations in build.prop.
Some init.d tweaks.
ext4 optimizations:
/system & /cache +dir_index,-has_journal
/data +dir_index
sd tweak from Franco kernel v12
Disabled Kies server (has memory leak). If you need KIES - rename /system/bin/kiesexe- to kiesexe and reboot.
Odex, thanks to http://forum.xda-developers.com/showthread.php?t=1799589 . If you prefer deodex - remove odex directory from ROM before flash.
Phone - removed delay after call
Faster auto brightness delay = 250 (Pako)
8 auto brightness levels.
All stock apps inside, updated to last versions. I prefer freesing it, instead of removing.
Beer https://www.paypal.com/cgi-bin/webs...ode=USD&lc=RU&bn=PP-DonationsBF&ch****t=UTF-8
del
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
I am using Carbon kitkat for i9070.
By default zram is enabled in it.
On every boot, I just disable it using swapoff /dev/block/zram0
But the problem I am facing is occasional freeze during which the most resource intensive process is "kswapd0"
So I want to disable zram permanently without using any app or script. Can any dev or geek help me out with the terminal command to disable zram permanently?
@AntaresOne , sorry to disturb you dev, but you are my only hope right now.
@shut_down ?
rajag33 said:
I am using Carbon kitkat for i9070.
By default zram is enabled in it.
On every boot, I just disable it using swapoff /dev/block/zram0
But the problem I am facing is occasional freeze during which the most resource intensive process is "kswapd"
So I want to disable zram permanently without using any app or script. Can any dev or geek help me out with the terminal command to disable zram permanently?
@AntaresOne , sorry to disturb you dev, but you are my only hope right now.
@shut_down ?
Click to expand...
Click to collapse
I am not sure, because I do not use Carbon now (I am on CM 10.1). But it used preload partition for it, probably some custom made zram option from TC. But I do not know how to disable it...
@shut_down Thank you buddy... Let me call some one for help. This zram thingy is really bugging me. kswapd freezes phone even when zram is off and no swap enabled.
Swap and zram are different.
Swap uses preload partition. Using both swap and zram at the same time will make your phone lag.
To disable zram on boot, make an init.d script and put it in /system/etc/init.d folder.
Sent from my GT-I9070
anantttt said:
Swap and zram are different.
Swap uses preload partition. Using both swap and zram at the same time will make your phone lag.
To disable zram on boot, make an init.d script and put it in /system/etc/init.d folder.
Sent from my GT-I9070
Click to expand...
Click to collapse
@anantttt Buddy, I know everything about zram and swap as I am a debian Linux user for years. There is no swap enabled in my phone. Disabling zram in ubuntu Linux is an easy process. But in case of android, I don't know the exact commands to deliver in terminal. Basically, I think it can be disabled without using scripts. Anyway, thank you for answering. Do you know how to create a init.d script to disable zram at boot?
I think the better way is to disable the kernel module corresponds with swap and zram...... Hope, I will soon find a workaround.....
rajag33 said:
@anantttt Buddy, I know everything about zram and swap as I am a Linux user for years. There is no swap enabled in my phone. Disabling zram in Linux is an easy process. But in case of android, I don't know the exact commands to deliver in terminal. Basically, I think it can be disabled without using scripts. Anyway, thank you for answering. Do you know how to create a init.d script to disable zram at boot?
I think the better way is to disable the kernel module corresponds with swap and zram...... Hope, I will soon find a workaround.....
Click to expand...
Click to collapse
Modifying kernel is a tedious work and my knowledge is limited.
For making init.d script See if this helps
http://forum.xda-developers.com/showthread.php?t=2503884
Sent from my GT-I9070