Database Develop

[REF] Ext4 speed improvement with a safe mount option on /data

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).

gingerbread compcache

How can i add compcache to gingerbread rom.
I need a push in the right direction.

Same as in CM 6.x
But in addition you need
- a fix for loading the ramzswap module
- install rzscontrol
If you need further help, this evening I can provide you with a update.zip

AndDiSa said:
Same as in CM 6.x
But in addition you need
- a fix for loading the ramzswap module
- install rzscontrol
If you need further help, this evening I can provide you with a update.zip
Click to expand...
Click to collapse
Ya if you could possible set me up with and update.zip that would be great.
Lol school and work takes up all my time nowadays.

An update.zip, which enables compcache on gingerbread, too, is available here. Goog luck!

LagFix

Another toy for us to play with . :silly:http://forum.xda-developers.com/showthread.php?t=2104326
App at Play Store https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix

It's not working on our device

DooMijasz said:
It's not working on our device
Click to expand...
Click to collapse
works on mine though I've actually not had time to read the thread yet .I've been a bit busy since I saw it .
But the one thing I recall reading is that you will see errors running it if it isn't compatable with your device.
Seeing zeros or numbers is fine.
I'm seeing no errors and saw numbers when I ran it .
What have I missed ?
Anyone else tried it ? I've seen it's had a few looks but no responses.
einstein.frat does your ROM mounts /data with -discard ?
Though I did see a few posts down one guy got rid of the mount /data with -discard script on his phone and switched to using this app as it worked better for him .

On my HTC Desire C i get error
fstrim -v /data(or cache it depends on what You will use this APP)
fstrim: FSTRIM: Operation not supported on transport endpoint
wich means our device is not suported and Lagfix does nothing for us. Check thread Page 9, same error for LG L5-610. OP explained that this error appear when device is not supported.

DooMijasz said:
On my HTC Desire C i get error
fstrim -v /data(or cache it depends on what You will use this APP)
fstrim: FSTRIM: Operation not supported on transport endpoint
wich means our device is not suported and Lagfix does nothing for us. Check thread Page 9, same error for LG L5-610. OP explained that this error appear when device is not supported.
Click to expand...
Click to collapse
Thats seems odd.I installed this app and works well(I dont get any error anways)
Try installing busybox from playstore and retry.Errors might be due to this busy box issues.

nikhil16242 said:
Thats seems odd.I installed this app and works well(I dont get any error anways)
Try installing busybox from playstore and retry.Errors might be due to this busy box issues.
Click to expand...
Click to collapse
Still the same error after installing new busybox from playstore.
I wonder if this problem is related to that, that 90% of your customizer scripts are not working on my device oO Just a lot of "No such file or directory" or "command not found" errors

Did you open the busybox and installed it from within (just verifying).
Sent from my HTC Desire C using xda app-developers app

Just check your busybox location . I've come across the odd recomendation to try system/xbin rather than system /bin . Also I always install it as a smart install (replace all(symlinks all)) and clean mode .(just in case this is the difference)

DooMijasz said:
Still the same error after installing new busybox from playstore.
I wonder if this problem is related to that, that 90% of your customizer scripts are not working on my device oO Just a lot of "No such file or directory" or "command not found" errors
Click to expand...
Click to collapse
Just noticed what you wrote . I'd guess you have an issue with your phone somewhere. Either Busybox or some other issue. What it is I have no clue . It's worth starting a new thread I think to see if one of the Gurus has an idea what is wrong .

nikhil16242 said:
Did you open the busybox and installed it from within (just verifying).
Sent from my HTC Desire C using xda app-developers app
Click to expand...
Click to collapse
Busybox installed from within with SMART INSTALL option. Idk whats wrong. I have exploss!on 2.1.1 rom installed.

DooMijasz said:
Busybox installed from within with SMART INSTALL option. Idk whats wrong. I have exploss!on 2.1.1 rom installed.
Click to expand...
Click to collapse
we are running Nameless . It could very well be your Rom . I've seen a few issues cropping up with Explosion lately unfortunately .

hey guys, what's your experience, does it worth to install?

neoyoli said:
hey guys, what's your experience, does it worth to install?
Click to expand...
Click to collapse
It's hard to say but that is entirely mine (our) own faults.
From my understanding (and I could be wrong) this is an implimentation of the Trim function they took so long to get on and working for ssds. This is ovbiously a good thing if I'm right.
Where it's hard to tell is because I/we are constantly flashing our phones. Most of the time I do a full wipe which does exactly the same action as ftrim . So atm I don't believe I've actually run the phone long enough to need to use it or should I say take proper advantage of it .
It's only meant to be run once a week so I'm keeping with it for the quiet times when I won't be flashing . I'll get to actually see how it works then .(maybe I'll try and do the next few updates as dirty flashes)
hope that helps

doea lagfree realy work ?
does it really work ?

PowerHAL: Error with boostpulse: Folder missing

Hi everyone!
Necessary Infos first: I am on a C6603, Stock .244 unlocked, rooted and relocked. I have been running DooMKernel before but .244 is a clean install. I also have reflashed the .244 stock kernel to see if that solves the issue. It doesn't.
I have been playing around with Logcat Extreme and i found that everytime I touch the screen, I get about 45 instances of
PowerHAL: Error opening /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such file or directory
even if I'm not using the interactive governor. When I am using the interactive governor, I get Permission denied instead of No such file or directory. I checked the path with my file explorer, and the cpufreq folder only contains a ondemand folder but */interactive/boostpulse is missing.
I have also tried chown system.system /sys/devices/system/cpu/cpufreq/interactive/boostpulse as suggested by DooMLoRD here
Could anyone who is interested check if he experiences the same behavior, and if not, post me the missing folder?
Thank you very much!

exact same problem here
Coirpre said:
Hi everyone!
Necessary Infos first: I am on a C6603, Stock .244 unlocked, rooted and relocked. I have been running DooMKernel before but .244 is a clean install. I also have reflashed the .244 stock kernel to see if that solves the issue. It doesn't.
I have been playing around with Logcat Extreme and i found that everytime I touch the screen, I get about 45 instances of
PowerHAL: Error opening /sys/devices/system/cpu/cpufreq/interactive/boostpulse: No such file or directory
even if I'm not using the interactive governor. When I am using the interactive governor, I get Permission denied instead of No such file or directory. I checked the path with my file explorer, and the cpufreq folder only contains a ondemand folder but */interactive/boostpulse is missing.
I have also tried chown system.system /sys/devices/system/cpu/cpufreq/interactive/boostpulse as suggested by DooMLoRD here
Could anyone who is interested check if he experiences the same behavior, and if not, post me the missing folder?
Thank you very much!
Click to expand...
Click to collapse
I don't understand why this folder is missing I'm on ROMAUR v8.0
I have exactly your same problem and I don't have a clue how to fix it, stock rom or mod rom same problem.

What is this error code doing to our device? Cuz I'm running ROMAUR 8.0 as well

sebastianlow said:
What is this error code doing to our device? Cuz I'm running ROMAUR 8.0 as well
Click to expand...
Click to collapse
probably not much except preventing touch boostpulse

Coirpre said:
probably not much except preventing touch boostpulse
Click to expand...
Click to collapse
I have the Same Problem, Samsung Galaxy 2 7.0 with stockrom. Kernel blackjack 2.1.2 and Android Tuner.

I think when "project butter" was introduced they were using interactive governor and boostpulse to ramp up the processor momentarily when the screen was touched to make the UI more responsive.
I don't think the code has been fully integrated properly into JB, I think by default boostpulse is set to -1 if its there at all.
rather than chown it try chmod it to 644
chmod 0664 /sys/devices/system/cpu/cpufreq/interactive/boostpulse
although it should be set like that in the init.rc files. Maybe worth cat those to check

[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.