yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] andrewluecke:
There are 2 ways of looking at this (but I agree with supercurio overall). EXT2 does write less to the HDD, so the effect on write cycles might be lower overall than EXT4. On HDD's where writing is expensive, it may be slower. The Sgs though is believed to use SLC memory internally (at least some of it), so writes shouldn't "cost" much, except maybe if TRIM-like ops don't happen. This might not be true though if you disable a few of the EXT4 features to write less.

On the other side, EXT2 doesn't have journaling, but EXT4 does (journaling has a performance hit). However, EXT2 also happily corrupts files in a power outage/crash. Not sure about you guys, but there is NO way I'd use a phone OS which didn't perform journaling, unless you guys like to reboot your phone from a crash (or simply run out of power), and be stuck in an endless loop because important settings have gotten corrupted? And yes, RFS performs journaling!

The problem with benchmarks, is that most "pros" who test file-systems leave journaling set to the default mode (which is the moderate setting). If they set it to "data=writeback" though, as per http://lwn.net/Articles/203915/ , proper journaling is disabled and the performance assessment is more fair (at the risk of file corruption). You are then comparing the file-systems TRUE performance.

It would be interesting to see how they compare with Journaling turned off. If EXT2 shows that it is performing twice as fast, it is likely to be because the journaling mode has been set to data=journal (the most comprehensive). I'm pretty sure that writes the data to the hard-disk twice.

Seriously, I think we should start a TV show called "Linux users say the Darnedest things", because of some of the stuff I hear. Technically, you can upgrade EXT2 to EXT3 to EXT4 (they are forward compatible), and so I can't even imagine why EXT4 would be slower..
[Galaxy S I9000 Android Development] RyanZA:
Well it isn't that EXT4 is slower, its EXT4+journals. I'm just saying EXT2 instead of EXT4-without-journals cause there really isn't a huge difference when you take the journals out of EXT4.

And yeah - it would be interesting to see how they compare, which is why I want to do it and test it out.

As to HFS+ journaling, it is apparently turned off in the iphone to increase speed. If true, then I guess all those iphone users must be having a terrible, terrible time with data loss.

It's amazing how stubborn some people can be about technicalities, without even testing them out - even to go as far as to want to block others from TESTing them out themselves.

EDIT: And seriously, losing your data in a crash? I've been messing with my phone since I got it, and it has yet to crash even once. So that's a total non-issue for me, personally.
[Galaxy S I9000 Android Development] kindaichi24:
so how should i use tat backup kernel if i wanna disable this lagfix? :confused:
[Galaxy S I9000 Android Development] mikelyon:
I don't really know.

i imagine you have to:

- rename the backup in update.zip

- add the 'disable lagfix' file in the voodoo directory

- reboot to convert in RFS

- reboot again in recovery and apply the update.zip

But i'm not sure, you'd better wait for Supercurio answer

If that work you have to keep the first backup because if you have done several updates with the various versions of the lagfix then you will only have the last backup.
[Galaxy S I9000 Android Development] kindaichi24:
okay thanks. i shall wait for his ans den. :)
[Galaxy S I9000 Android Development] dutchcow:
Small thing curio, the lagfix-only version doesn't seem to log anything in the voodoo folder. It did make 2 backups of my kernel though.
[Galaxy S I9000 Android Development] supercurio:
Hello !

You can use it as Odin package in a .tar or directly with redbend_ua

But that's not very easy and you just gave me the idea to make this simple as a single command :)

Will be present in future versions ;)
[Galaxy S I9000 Android Development] supercurio:
Yes, it only produces logs into Voodoo/logs if a file/dir named "enable debug" is present in Voodoo/

"enable debug" activates the previous behavior too : usb adb is forced on.

Beta4 had a small script error that only saved the logs at each boot ;)

− no biggie for a beta version −
[Galaxy S I9000 Android Development] kindaichi24:
erm so i need to convert the .img to .tar or rename it to .tar to flash in odin pda without using any pit files and ticking anything am i right? sorry noob here still learning. i just curious how to disable it completely. :D
[Galaxy S I9000 Android Development] miketwn:
@Supercurio I dont know why so much fuss about color fix, its works pretty smooth. With Froyo update coming soon, to disable lagfix you need to create file/folder in Voodoo file in /sdcard called "disable lagfix" or is it "disable*lagfix*" (when you replied to a poster here http://xdaforums.com/showpost.php?p=8127966&postcount=576) Just want to make sure? cheers bro....
[Galaxy S I9000 Android Development] raspdeep:
u can use adb or terminal to do this:

mv bml7-zImage-kernel-backup.img zImage

tar -cf kernel.tar zImage

then pull the kernel.tar file to your computer as backup for odin to flash

if you want to flash the kernel directly from your phone:

$ su

# redbend_ua restore bml7-zImage-kernel-backup.img /dev/block/bml7
[Galaxy S I9000 Android Development] cdmackay:
The '*' chars in "disable*lagfix*" are special chars, used in shell filename expansion (aka "globbing"), which mean "any number (incl zero) of any character". So, as long as the file or folder's name contains "disable", and then after it also contains "lagfix", that's enough, regardless of extra chars that may or may not be there. And case-insensitive, too.
[Galaxy S I9000 Android Development] kindaichi24:
erm i tried and it said no such file or directory. wad command should i use before the "mv bml7-zImage-kernel-backup.img zImage" ?
[Galaxy S I9000 Android Development] raspdeep:
u must cd to the directory where u found bml7-zImage-kernel-backup.img?
[Galaxy S I9000 Android Development] kindaichi24:
sorry but how to cd to the directory where i found it? its inside my sdcard where the update.zip is. can teach me the command. :o
[Galaxy S I9000 Android Development] miketwn:
@cdmackay thanks for the spot-on explanation....
[Galaxy S I9000 Android Development] raspdeep:
cd /sdcard
[Galaxy S I9000 Android Development] kindaichi24:
ok thanks! it works. u are a genius man!
[Galaxy S I9000 Android Development] spline1:
I have a system monitor with Beta4 now on the top right.

What is it?

How it goes away?
[Galaxy S I9000 Android Development] iammichel:
8 hours unplugged and battery still 100%... 1775 score with XWJG5... Runs like a charm!

I am wondering... Is it possible to disable the color fix in any way. Since you are now offering the lag fix separately I can imagine some people who have the color fix would like to get rid of it and guy with the lag fix only...
[Galaxy S I9000 Android Development] JuWa:
Have you reboot your phone after lag fix?

Maybe you have the same problem, than I had. It got stucked in 100% and after reboot it was correct...60%... lol :D :rolleyes:
[Galaxy S I9000 Android Development] gnoelnahc:
haha i just tried removing 3.0 because i wanted to try beta4, and it wiped all my apps... this is so weird. it removed the lagfix but did not remove the colourfix too.. HM.

not that i mind losing all my apps, because my data is all still there, but this is a slight hassle.

another two things i noticed: I used the 3.0 on one phone, and according to the changelog it only removes the bluish tint at 100% brightness. worked perfect, exactly what the site said, it even removed the bluish tint when displaying the camera viewfinder.

next, i tried beta4 on a second and separate galaxy s. the colourfix is definitely in for 100% brightness, but the bluish tint is present on the camera viewfinder now. is this strange?
[Galaxy S I9000 Android Development] lemmy_0:
you're a lifesaver!

i did think i needed to restart Launcher Pro.

i thought switching the homescreen to touchwiz would reset launcher pro. guess not.

went fine after restarting launcher pro from the preferences (darn! how could i have missed that option)

thanks mate
[Galaxy S I9000 Android Development] etking:
Great work so far! Will there ever be a color fix allowing to leave autobrightness and minimum brightness levels untouched? I think they both work quite perfectly for me on stock firmware and I want to keep them. A too low brightness setting just does not look nice anymore.
[Galaxy S I9000 Android Development] kindaichi24:
can create a brightness level until 10 instead of zero?i think that will be more suitable for anytime usage =D
[Galaxy S I9000 Android Development] ludow:
I hope you guys don't use stock battery status meter to measure battery drain by Voodoo lagfix (only). It will stay at 100% few hours indeed. :P It is fixed to 100 - 80 - 60 - 40 - 20 %.

Better use some 3rd party battery meter.
[Galaxy S I9000 Android Development] cantIntoCode:
Updated to FroYo and totally miss Voodoo :( Just need to wait until its implemented to 2.2. And when Samsung release there source.
[Galaxy S I9000 Android Development] ufuuu:
Since ClockWorkMod doesn't work with voodoo kernel, could you suggest another recovery mod/or another way to wipe battery stats? I don't wanna use ADB commands because you need to plug in phone via usb, which charges the phone and affects the battery meter. I need to charge it completely and enter a recovery mod to wipe batt stats, without power the phone up.

So, any suggestions?

Btw, that lagfix-only version says beta3. So, is CPU locked at 1GHz in that lagfix-only version too?

Aaaand, big big appreciations to curio. I have JM8+voodoo b4 and no more lags with my phone :) The simplest example is, no more lag when I try to shut down the phone and it ask me are you sure. That window was really laggy before the voodoo fix.

So, thanks again curio :)
[Galaxy S I9000 Android Development] mintomax111:
Hi,

I've tried all other approaches for the lagfix before. All of them have been fast in the beginning, and slowing down rapidely with growing number of apps installed.

I also had sleep mode lag and sometimes it didn't do something for some seconds aswell, even with only a few apps on it... so they all failed my needs ;)

Voodoo is a new method, and altho I just had flashed Froyo and installed the Oneclick Fix, I decided to go back to 2.1 JM8, which is offered here aswell.

Installed Voodoolagfix, and after the first reboot (restored my data and a few system settings aswell) it came up with FC's on process.acore and android.sep.twlauncher, even after wiping both, cache and phone memory.

Oh, I forgot to mention, that the voice, that comes up when you first time execute startup after updating to voodoo, was until "step 1" okay, but then it lagged like hell and it was slowed down.

Still, it booted up without problems and as mentioned, after the restore it was somehow broken.

Reflashing, Rebooting, wiped, installed voodoo with "update.zip" and restored apps+data without system settings worked.

And it's so running, like never before. Thanks for that!

m2m
[Galaxy S I9000 Android Development] TheTodFather:
thats not his kernel thats the i9000 rom. Possibly can be fixed by the orientation fix in the captivate board, not sure haven't tried.
[Galaxy S I9000 Android Development] iammichel:
Yup, rebooted and all working well and decent battery app running. 8 Hours before phone drops to 99% :)
[Galaxy S I9000 Android Development] danamoult:
Don't know about losing apps, but yes beta4 still includes the colour fix in it. The Lagfix 3.0 is ONLY the lagfix, without the colour fix.

It doesn't say 'beta 3', it says version 3.0. So no, the CPU isn't locked at 1GHz. It's basically beta 4 without the colour fix.
[Galaxy S I9000 Android Development] ufuuu:
Ok, thanks :)
[Galaxy S I9000 Android Development] adrianmak:
Seems locked at 1G bug fixed on beta 4 is not as smooth as beta 3
[Galaxy S I9000 Android Development] MasK:
Not sure if its Voodoo, but i feel my headphone levels are higher now. Also, no music pauses during heavy data transfer. I like!!
[Galaxy S I9000 Android Development] Bhonka:
Anyone have issues with 3g/hspa not working after applying the kernel?
[Galaxy S I9000 Android Development] MomijiTMO:
+1

Is the color fix also disabled when you go about reverting back to RFS?

EDIT: Well I'm going to give it a go and see what happens :p

EDIT V2: Yup no problems.
[Galaxy S I9000 Android Development] desman:
Beta 4 consumes much more battery than beta 3 in my i9k. Will revert to beta 3 for the time being.
[Galaxy S I9000 Android Development] danamoult:
Having the CPU locked at 1Ghz makes the phone 'slightly' faster, but causes a huge battery drain.

This happened to me the other day after repeated applying/removing the kernel. I'm not sure if it was caused by Voodoo, but I fixed my problem by going to Settings -> Wireless and network -> Mobile networks -> Access Point Names, and making sure that the details are 100% correct there for your mobile internet provider. Mine had somehow changed and by reverting to default everything started working again.

Applying the Lagfix-only update.zip directly over beta3/4 will automatically remove the colour fix while keeping the lagfix.

This is extremely strange, are you sure? I'd test beta4 for a couple days before immediately reverting, as almost everyone else has experienced much better battery consumption with beta4.
[Galaxy S I9000 Android Development] desman:
There are some other discussions in a Taiwan Forum regarding the high battery drain in beta 4.

I have monitored the CPU usage with beta 4, the cpu usage keeps from 1x% to 3x% when idle. With beta 3, the cpu usage keeps below 10% (most of the time 5%) when idle.
[Galaxy S I9000 Android Development] mikelyon:
Like others I have a lot of battery drain with Voodoo lagfix 3.0 (same as beta4 without color fix) !!! I had my phone fully charged yesterday at 7pm and now my phone is only 38% charged.

Looking at the stats Android system is first (the first time ever) with 39% of use ..........

I thing i'm going to go back to Beta 2 or 3..... waiting for little improvment on that side
[Galaxy S I9000 Android Development] pilotbrille:
has anyone problems with the LOW-lightning levels on the brightness settings?? cause when i'm in a dark room, or lying in the bed, with beta 4 the brithness jumps every 10 sec or so, from very low to the next level. i loved the new color fix cause of the new LOWEST brithness setting in auto-mode cause the lowest on the original one was way to bright for me!

i upgraded from beta2 to beta4, on beta2 it worked perfect!! now im using the lagfix only cause the brightness jumping is realy annoying... anyone having the same problem as me?

but still, nice nice work curio
[Galaxy S I9000 Android Development] igniztion:
I also had problems with brightness jumping all over the place. Some apps have their own brightness settings and it just is too huge a difference between the levels.

Autobrightness in a dark room is unusable as it seems to have trouble keeping fixed at the low level, even when using a single app it keeps jumping from low level to high level brightness and back. Happened several times during a 10 minute Angry Birds Lite game.
[Galaxy S I9000 Android Development] MasK:
Well.. I guess those who have issues with brightness settings:

Curio has released a lagfix-only kernel.. so just use that instead. It simply doesn't work for everyone.
[Galaxy S I9000 Android Development] bub181:
After reading this post I decided to monitor CPU usage too. I was running beta4 with lagfix only and the system CPU usage hovered around 10-15% all the time, but after reflashing beta2 the system CPU usage is now around half that at 3-6%. I wonder what changes were made between beta2 and beta4. I'm running XWJM8 by the way if that helps.

I'm using an app called Usage Timelines which is free and seems to be quite good:

http://www.androidzoom.com/android_applications/tools/usage-timelines_irxk.html
[Galaxy S I9000 Android Development] MasK:
Whoa.. second person reporting that.

Not sure if I wanna be reporting this..

88% -> 70% -> 40% -> 28% -> 12%

*estimated* 30mins in between the readouts above.. Phone was getting warmer as well and before I knew it, it shut down.. LOL

I also noticed constant data transfers.. so It's prolly not the Voodoo.

Now charging and monitoring. Using Lagfix-only 3.0 btw.
[Galaxy S I9000 Android Development] Narcissus85:
flashing the original kernel back is the same as disabling the lag fix with the "disable lagfix" file in the voodoo folder?

are there some differences?

i noticed that after disabling the lag fix if i make a wipe of data at the reboot it's automatically reistalled again .......
[Galaxy S I9000 Android Development] ashwinds:
If on JM7/JM8 - check wifi

JM8/Jm7 people - please check if your wifi is going to sleep. Howto is here:

http://xdaforums.com/showpost.php?p=7997190&postcount=451

Workaround is here:

http://xdaforums.com/showpost.php?p=7998188&postcount=458

Had major battery drain and this kind of alleviated it.
[Galaxy S I9000 Android Development] stratmetal:
Today I went from fully charged to 10% in about 7 hours which is huge compared to what I'm used to. Beta 3 didn't have this issue for me. Might be beta 4 causing it?
[Galaxy S I9000 Android Development] supercurio:
Now you can access to CWM in RFS mode.

This access will even be simplified in future version with "Rom manager recovery commands" auto-detection.

BTW you don't have to wipe your battery stats, i already do this in the code since beta2 at each conversion. ;)
[Galaxy S I9000 Android Development] supercurio:
Sorry but it's something else ;)
[Galaxy S I9000 Android Development] supercurio:
I hope Samsung will give us sources very soon like.. yesterday already

We have Firmware leaks, we should have Source leaks too !
[Galaxy S I9000 Android Development] leoon:
I didnt really like the color fix etc, and the bluish tint isnt that bad (at least for me..)

About the lag fix, I dont feel that its different from the others? its fast but its just like the others no?

Though thumbs up for the work and the dedication to this device
[Galaxy S I9000 Android Development] tszsiutong:
Hello

I have installed the beta4 lagfix 3.0 and voodoo-color version.

But I only want the lagfix function.

I know there is only lagfix update.

If I just install the only lagfix version again, can I remove the voodoo-color at the same time?
[Galaxy S I9000 Android Development] achio1115:
Yes it will remove the color fix…
[Galaxy S I9000 Android Development] bilboa1:
brightness sometimes changes for no reason otherwise i like the color fix, id like if all brightness levels were fixed ;)
[Galaxy S I9000 Android Development] Stefanauss:
Absolutely not, you MUST disable the lagfix first, do a complete reboot and only then reflash the original kernel back. Original kernel can't boot an ext4 partition, this is why you need to disable first.
[Galaxy S I9000 Android Development] Stefanauss:
Do you just reflash beta2 over beta4? does it work, no problems?
[Galaxy S I9000 Android Development] bub181:
Yes, I just flashed beta 2 over beta 4. I think I'm definitely noticing improved battery life, and the system CPU usage is much less.
[Galaxy S I9000 Android Development] danamoult:
You can simply flash different versions of Voodoo over each other without disabling anything. Even flashing the Lagfix-only version over beta3/beta4 can be done immediately and it will automatically remove the colour-fix for you.

On the other hand, I believe you have to create the 'disable lagfix' file in the Voodoo directory if you should wish to restore your original kernel.
[Galaxy S I9000 Android Development] egress:
Stupidly flashed JM8 or JM7 firmwares with voodoo still active. followed instructions on voodoo homepage and reflashed Voodoo-beta3-GT-I9000-odin-pda.tar using Odin and now phone keeps rebooting and states data partition wipe detected converting data partition to optimised extension form. Is this how it should work. I have also wiped data and cache.
[Galaxy S I9000 Android Development] tameracingdriver:
Got this on mine now (beta 4).

Best lag fix I've used - phone seems as fast as ever. Quadrant 1700, compared with 2300 of other "fixes", but in the real world this is better - I'm now running without autokiller and for the first time, I don't seem to get any major slowdowns.

I quite like what has been done with the colours / screen / brightness, FWIW. Especially the new much lower brightness level which is far better at bed time.

Good work :)

ETA: I've just read about others having problem with brightness - I DONT use auto brightness as I've always preferred to set my own - I like the extra settings on that.
[Galaxy S I9000 Android Development] nickporwal:
Guys does this lagfix also slows down like other lagfixes after usage of sometime.

Other lagfixes remains fast just after the reboot but becomes slow after 4-5 hrs of usage.

I really appreciate the curio's work for making the sgs better. Keep up the good work mate.
[Galaxy S I9000 Android Development] cryolithic:
Also running into the auto brightness issues. I really like the colour fix, but would like to have autobright too. Hoping for a fix in beta5
[Galaxy S I9000 Android Development] oskariunit:
lol that's a neat trick, thanks :)
[Galaxy S I9000 Android Development] Stefanauss:
@Supercurio

I read somewhere that since beta2 you started wiping battery stats in your code.

Could you tell me exactly in which occasions batterystats.bin gets erased? After enabling/disabling lagfix? Everytime at boot? Something else?
[Galaxy S I9000 Android Development] etking:
Autobrightness means that I do not even have to think about brightness settings and can concentrate on other things. I do not care how easy it is to change brightness manually, I just need autobrightness working reliably and it should not be any darker than stock autobrightness. I will not use this lagfix until autobrightness is working correctly with color installed. But as the current work looks very promising, I am looking forward to use it!
[Galaxy S I9000 Android Development] ed10000:
Used it for about a week (starting from beta 1). Very zippy and doesn't slow down with time. Apart from the half second lags once every hour, there's hardly anything wrong with this fix.

Also, I especially liked the lowest minimum brightness setting. Finally I was able to use it in bed without having to strain my eyes too much. The 100% settings seemed to be a bit on the warmer side though.

Used this until earlier today with JM7. Upgraded to JM8 now and decided not to use any lagfixes for a few days to see if anything has improved on stock. I really miss the min brightness though.

Thanks curio, great work! I'll donate a bit as soon as I'm able to get some cash on Papal. Keep up the good work!
[Galaxy S I9000 Android Development] butro:
I performed a battery test and have found voodoo beta 4 gives me normal battery life. After 26.5 hours unplugged I am at 10% battery left with the android system using only 2% of the battery (14 minutes of CPU usage). This battery test included 25 minutes of voice calls, texting and chatting continuously, internet browsing, email reading and replying, and some fair amount of application usage. I did not test it using any wi-fi. I do not normally use wi-fi so to me this test was pretty conclusive that battery life is not affected significantly by voodoo beta 4.

I will say again, great work curio! Can't wait til final release.
[Galaxy S I9000 Android Development] mbriody:
Sorry dupe