yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] matty___:
Well duh. Its 2.1 kernel.
[Galaxy S I9000 Android Development] :
Sry guys my fault. But how to undo the voodoo lagfix if applied?
[Galaxy S I9000 Android Development] m4ssnet:
will be avaiable all original kernels (zimage) for all rom for "uninstall" this fix ?!!
[Galaxy S I9000 Android Development] RyanZA:
Did you read your link?

DroidX has a much better CPU then the N1, and has JIT enabled, but only shows 15s...

It is the FPU... ;)
[Galaxy S I9000 Android Development] zimphishmonger:
Huh? If yiou are asking if they will provide a stock kernel for every rom & phone varient, its not happening. You should have found the "stock" kernel prior to flashing a BETA kernel.
[Galaxy S I9000 Android Development] katsuru:
Easy, create a file on sdcard. Dir: /sdcard/disable-lagfix

Next reboot will restore your Filesystem back to stock, if you remove that file and reboot, your filesystem will be set to ext4 as your voodoo kernel is still there.

WARNING.

Before flashing a new firmware YOU MUST disable the Ext4 Filesystem!

Do not flash a Stock kernel ever with Ext4 running, because the kernel wont convert the Ext4 filesystem to RFS, and either will the stock kernel be able to boot the phone as it can't access the Ext4 filesystem.
[Galaxy S I9000 Android Development] ed10000:
So all 1GHz Snapdragon phones (and not just the N1/Desire) come equipped with the FPU as well? I was under the impression that only the Snapdragons reach those scores because Google optimized the JIT compiler specifically for the Google Phone (a Snapdragon one). So if it does have a dedicated FPU, what performance does this boost exactly? Or in other words, what kind of applications extensively use floating point operations (like, games? open/close speed of apps? or what?)?

P.S. - It would be great if you could have links to all your stuff in your siggy :) I'm looking forward for your benchmarking app, but don't really visit the Themes/Apps section and don't want to miss it just because of that :D
[Galaxy S I9000 Android Development] madmack:
I'm wondering whether that is totally necessary. Doesn't ticking the option "repartition" in Odin repartitions these filesystems back to RFS ?
[Galaxy S I9000 Android Development] katsuru:
If you try that, here is what happens:

Your kernel boots, you will see the shiny S logo and then nothing else happens, android UI never starts. Access through adb is still possible at this state.

Odin3 will not touch the filesystem while creating partitions.

As far as i know that is how it goes. I will check with curio about it.
[Galaxy S I9000 Android Development] ed10000:
I remember reading a post previously posted by Supercurio that flashing a new firmware automatically formats it back to RFS, regardless of whether it is with or without re-partition checked. Also, flashing ONLY a kernel that doesn't support EXT4 will make your phone un-bootable, but reflashing an EXT4 compatible kernel should get things running again, without any data loss.
[Galaxy S I9000 Android Development] Zilch25:
I've flashed to a completely different firmware using repartition after applying the fix without any issues
[Galaxy S I9000 Android Development] katsuru:
Than seems like Odin3 re-partition takes care of it.

How did you do it? .512pit flash at first, and then the firmware? or all at once?
[Galaxy S I9000 Android Development] ed10000:
Here is the link to supercurio's post - http://xdaforums.com/showpost.php?p=7838991&postcount=115

I'm going to try this as soon as the public release is made. Can't wait :)
[Galaxy S I9000 Android Development] katsuru:
If u flash a new firmware without removing the lagfix 1st, when u apply the lagfix on the new firmware, it will kill ur system, as the lagfix restores the older lagfix.

I knew i was right! xD
[Galaxy S I9000 Android Development] dopeee:
wow this is looking really promising!

I'll put $10 for a complete fix! Keep it up!
[Galaxy S I9000 Android Development] dckiwi:
Yeah chuck me down for a tenner too (complete fix).
[Galaxy S I9000 Android Development] kenkiller:
That doesn't seem like what he says here

Even if you flash back to an older kernel, it doesn't "kill" the phone. You just need to flash back to a ext4 supported kernel
[Galaxy S I9000 Android Development] katsuru:
it is a bug. will be reviewed on the 2nd beta.

Trust me, if you don't then join IRC @ freenode - #project-voodoo
[Galaxy S I9000 Android Development] Zilch25:
Yeah it's correct, even if you reflash if you try to reapply the fix it will botch things up. You HAVE to use the disable-lagfix trick to remove it or reapplication will cause a ton of FCs. Even if you've reflashed though you can use disable-lagfix and it will turn off the fix- it'll completely screw up your current flash though, so before flashing back MAKE SURE you run disable-lagfix =P
[Galaxy S I9000 Android Development] bucklino:
Sorry, but....... how do I exactly to "run disable-lagfix", if i created an empty file "sdcard/disable-lagfix"?

Thanks....
[Galaxy S I9000 Android Development] odyssey61:
Create a blank file with no extension and with the name disable-lagfix in /sdcard and reboot.
[Galaxy S I9000 Android Development] JaGuR:
Anybody else experience WIFI not going to sleep with this lag fix, when screen is off ?

Or am I the only one ?

I am using Austrlia DTJG4 Optus firmware, and just not sure if it is something I have installed, and if a factory reset will work :/
[Galaxy S I9000 Android Development] distortedloop:
You just create the empty file. The startup script checks for it, if it's not there, it just continues booting, if it's there, it reverses the process. Brilliant.
[Galaxy S I9000 Android Development] Ferdimage:
yeah it stays on but what the hell it works well, i left my phone on standby for 7 hours when i wen to to sleep with wifi still on and from 77% to 75% when i woke up!

AMAZING!!
[Galaxy S I9000 Android Development] dckiwi:
Nice... what firmware you on? That's a slow draw.
[Galaxy S I9000 Android Development] titovic:
Reflash same firmware w/out disabling Voodoo lagfix

I was already on XWJM7 with Voodoo installed but saw an error message (not lagfix-related) due to the CSC I used. Without disabling this lagfix, I re-flashed the same firmware (512 PIT, re-partitioned) and ended up having to do a wipe cache/factory reset under Recovery before i finally got past the S logo and into the system. Without doing the factory reset, my screen stays off and pushing the power button just lights up the 2 LEDs (Menu, Back).

I haven't re-flashed/re-applied the Voodoo kernel yet and I believe it can be done safely as the quote above says but I am now concerned after reading your post. Any idea as to the worst that can happen? :confused: TIA
[Galaxy S I9000 Android Development] Zilch25:
Nah the worst case scenario in my post is if you try to flash the voodoo kernel without having done the disable-lagfix step you *will not* be able to reflash and use the voodoo kernel again (When you do you'll get a storm of force closes until you reflash your stock kernel)

To fix it you can reflash, create the disable-lagfix file and put it in the root of /sdcard, flash in the voodoo kernel and let it reboot... it'll take a while, and when the phone comes up itll be Force close city. Reflash the phone again and you'll be ready to use the voodoo kernel again with the force close problem. (Make sure you remove the disable-lagfix file before you reflash the voodoo kernel again)

The best thing to do is make sure you just use the disable-lagfix method before reflashing to a new firmware to avoid the issue

(To clarify, this is a bug that I'm certain won't exist once supercurio actually OFFICIALLY releases this :)
[Galaxy S I9000 Android Development] supercurio:
Hey hey !

It's been not a long time but so many messages of yours since I wrote here :D

I've read every message, and the complete IRC logs and missed nothing.

Sorry I can't answer to everybody, but be sure you're not ignored.

Beta Feedback

I'm very happy by the very convincing feedback on IRC and here, and by the bug report too.

You found a path that i got wrong: Flashing directly another firmware on top of a Voodoo lagfix configuration. I assumed that Odin flashing part "wipes" data but... of course it don't touch the SD card!

Because so far the only people stuck (+ 1 guy with a previous lagfix unable to uninstall itself) were because of this after reinstalling Voodo Lagfix, this will be the first bug addressed in code.

I'll also improve the communication with users for easier rare interactions.

If you had a problem with the private beta, in theory you should already be on IRC but the the diffusion was wider. Please let me know, don't stay silent about that, i need feedback about broken things.

What's next

Beta2 will come once a minimal website will be up and ready to. Sometimes forums are not the most efficient way to find information.

A reference website is indeed required ;)

USA !

It's rumored that... some of you own Vibrants and Captivates :D (i heard somebody say Epic 4G.... and Galaxy Tab?)

I have good news for you too !

We already agree with JAC who will build the Vibrant kernel, I'll have the answer from Unhelpful soon for the Captivate.

I'm pretty confident that every Galaxy S guru will soon build Voodoo lagfix enabled kernel for each model.

Communication

Feedback can be quite overwhelming, especially when it's good ;) In a vain hope not getting addicted to it, I will stay almost quiet in order to focus again on the code an improve it until beta 2 release.

Don't freak out if I don't answer, it's allright !

I will create a topic for the Voodoo lagfix as soon as necessary.

Donation : feel free to contribute, my Paypal is curio@free.fr, don't hesitate to show it on this topic, it name is BOUNTY after all ;)
[Galaxy S I9000 Android Development] Ferdimage:
M7 + root & Voodoo Beta1 ...

definitely better than my previous combo M5 + samset 1.9f & One Click Lagfix EXT2..
[Galaxy S I9000 Android Development] m4ssnet:
only 2 question,

1) if I've installed the voodoo lagfix beta1, and after I reinstall one stock rom (for example JM7) with ticking repartition, the lagfix will "force unistalled" right ?? (because overwrited by the stock inside rom kernel) OR NOT ??!!!

2) How can completly unistall this lagfix ?! I undestand that i have to create an empty file in sd-card with that name, but, after that it will reboot and ??? Force close ? repartition in normal mode and not EXT4 ?? I have to repartition ?? (how, on the fly ??!!) I haven't understand this points

Thanks to all community, you're truly awesome people ;)
[Galaxy S I9000 Android Development] CazeW:
1) No.

2) You create the empty file. Reboot and let the phone do its thing. When it's done you can flash a new firmware like you do normally (remember to tick Re-Partition in Odin when you do it).
[Galaxy S I9000 Android Development] captive:
Flashed about 1 hour ago, so far so good.

@supercurio: what has really changed is just ramdisk (and init scripts), or kernel had to be recompiled too?
[Galaxy S I9000 Android Development] -NRG-:
I will donate 20 dollar when there is a complete fix, that also works on froyo.
[Galaxy S I9000 Android Development] networkdood:
This seems like a great fix - I have the i897 and like i9000 ROMs better - when I applied the voodoo file and rebooted using ODIN I was stuck at the SAMSUG i-9000 screen. The voodoo file for use in the PDA section contains a zimage - I do not need to extract the zimage first and just need the actuall file that starts with voodoo....? Correct? If I want to use this with a SAMSET ROM does anyone know if it will work because after applying the file PDA and then applying an update file of SAMSET, for example, it gets stuck at the multi-CSC part in recovery....for the 7th time, I brought my phone from the dead...lots of fun...lol
[Galaxy S I9000 Android Development] moreira86:
hi there, im using JM5 with the very first lagfix that came out (http://xdaforums.com/showthread.php?t=748596&page=17), i would like to flash a new firmware and apply voodoo fix, should i select re-partition in odin while flashing to remove the previous lagfix and start things from ground level again? thanks
[Galaxy S I9000 Android Development] mikelyon:
Why need to tick re-partition if the boot with the file already restore RFS ?

Samsung support has said it's better not to use this parameter....
[Galaxy S I9000 Android Development] davydt:
It is not very first lagfix. First was mimocans kernel with ext4 partition on external SD card. And that lagfix shows almost the same speed as this one.
[Galaxy S I9000 Android Development] moreira86:
well, it was the first lagfix without the need of an external sd card, anyway, thats not the problem, you didnt help me with my question, just felt the need to correct me right?:) so if i select re-partition the fix i applied will be erased?
[Galaxy S I9000 Android Development] praveen6585:
even i am using that manual lagfix with JM2.. AFAIK a normal reflash with ODIN will reset the lagfix.. but you can take a confirmation from any expert here..
[Galaxy S I9000 Android Development] CazeW:
Don't know if it's necessary. I just guessed that it could be good to tick it. :)
[Galaxy S I9000 Android Development] Finguz:
Just installed beta 1 and wow!! Supercurio should be getting paid by Samsung to fix their products :rolleyes::D

Thankyou, donation is on it's way ;)
[Galaxy S I9000 Android Development] trenje:
Will we be able to flash beta 2 (when it comes out) over beta 1 without reflashing firmware?
[Galaxy S I9000 Android Development] bucklino:
Just it? So easy....

And should i create this file before or after run the voodoo lagfix?

Thanks a lot.
[Galaxy S I9000 Android Development] Guiper:
Well after using the lagfix for 2 days, im posting my feedback.

For me the I/O problem is 95% fixed. Market is fast, applications that lagged before don't lag anymore, and the device interactivity is way much smoother (using Launcher pro), although may be some small improvements that can be done.

Looks like Samsung applications are still lagging little bit, mail for example. Are they running from /system which is still RFS? (I'm not an android export). It's not possible to migrate it to ext4 also?

The same for /dbdata. It's not possible to migrate it also? Some basic tests showed me that the slow NAND (internal SD) using ext4 after the fix is 50% faster than the fast flash memory using RFS (/dev/block/stl10). Just use a simply DD command on both partitions to create 20MB file.

Just paid my 10$ bounty, curio for sure deserves it, after the hard work. Please keep it up.

Somebody wants to open a bounty for a RAM fix? My phone is almost perfect, just lagging when sweeping memory, when no more memory is available (around 40MB free on JM6). Why we just have 320MB free RAM? Why is part of the 512 (is it really 512MB??) it on an apparently not used tmpfs? I don't believe that the radio needs 192MB for working. If somebody has free time, and the right knowledge count with some beers from my side.

Curio, keep up the good work and congratulations!
[Galaxy S I9000 Android Development] distortedloop:
Nah, you're both wrong, I believe.

The FIRST lag fix I know about was by Paul at MoDaCo. It's described here, and he announced it on June 29.

Paul moved /data/data to the nand's /dbdata partition via the symlink method, which really improved things, but it limited your apps to 130mb.

Seems like Mimocan built upon Paul's idea by basically using apps2sd idea of moving the apps stuff to the ext partition of an sdcard, but not for needed space, more for needed speed. Mimocan posted this on MoDaCo on July 12, here.

One major difference between the two is that mimocan requires a custom kernel to support ext4, Paul's did not. All these other methods require a custom kernel because of that.

The big advantage to supercurio's method is that it uses the internal space (and why not, there's 2gb of it!) and uses faster memory than an external card will provide. The best of both worlds.

Keep an eye on supercurio in other threads. He's come up with some great stuff in a short time: this fix, the headphone fix, the redbend method to flash a kernel with update.zip. Exciting stuff for our SGS community.
[Galaxy S I9000 Android Development] distortedloop:
ONLY create that file when you need to UNDO the voodoo lagfix. IF you create it after you've done the fix, it will automatically undo the fix, and you might freak out when your phone takes a really long time to boot the next time you boot it! ;)
[Galaxy S I9000 Android Development] ginkage:
Hm... /dbdata size is suspiciously similar to the difference between RAM size seen by 2.2 device on SGS Froyo (304 Mb) and on Samsung Galaxy Tab Froyo (435 Mb). The speed of /dbdata also makes me think... Could it be that /dbdata is in fact mapped to RAM and is periodically synchronised to some file in flash memory?
[Galaxy S I9000 Android Development] mikelyon:
We have "only" 320 Mb free because the system uses the rest.

My feedback after a day of test is that like everyone the phone is fast in loading apps, downloading market and opening the application list.

It is not awasome compare to before (i'm on JM2) but i can feel more responsiveness in standard use.

Still have sometimes some lag but imo it is the due to RAM ressources
[Galaxy S I9000 Android Development] DReaMoR:
Would be nice if it could, but is not a real problem, coz there is a way to uninstall beta 1, an then install a new beta(when it comes available).
[Galaxy S I9000 Android Development] ufuuu:
I stuck on Odin while trying to do voodoo lag fix. I wait about 30 minutes but no change... And my phone's screen is black all the time...
[Galaxy S I9000 Android Development] Zilch25:
Yank the battery, disconnect USB, close Odin

Reopen Odin, plop the kernel into the PDA box again, reinsert your battery.

Hold vol down + home + power, your phone should pop into download mode and you can try again.

Make sure you aren't in Kies when you try to flash this

Edited: Didn't have my I9000 key combo facts straight
[Galaxy S I9000 Android Development] trenje:
Of course, it's not a problem. :)

It's a stupid question, but have you put your phone into download mode? Make sure you don't have Kies opened.
[Galaxy S I9000 Android Development] ufuuu:
I did them both. Reflashing know... Then gonna try the Zilch25 way.
[Galaxy S I9000 Android Development] ufuuu:
that not worked, did not pop into download mode...
[Galaxy S I9000 Android Development] Zilch25:
Hmm, I'm a Captivate user so your download mode combinations might be different. Try your standard download mode key combination (without power button) and plug it into USB (while holding the combination) and it *should* toss you into download mode.

Make sure you restarted Odin before plugging the phone in though!

Alternatively get it into download mode *before* you hook it up to USB or start Odin- Odin is really *****y about when you plug your phone into it sometimes.
[Galaxy S I9000 Android Development] ufuuu:
thanks for your kind interest. i'm trying chain fire fix :)
[Galaxy S I9000 Android Development] kgk888:
C'mon man, it's not even the same device. This right here is the reason there are separate forums for the carrier devices like the Captivate and Vibrant.

Galaxy S download mode -> volume down, home button, power

And Odin should always, ALWAYS be started before you plug the phone into the computer during download mode. That's flashing 101 for this phone and has been repeated in countless guides. If you plug the phone in and then fire up ODIN it more often than not fails to detect the phone or detects multiple devices.
[Galaxy S I9000 Android Development] Zilch25:
I apologize for trying to help =P How could I have been so rude to overstep my boundaries? Maybe I should go back to the Captivate concentration camp so that you pure, chosen I9000 folks can be alone :o

My justification- my Captivate running I9000 + I9000 kernel can enter download mode by holding down (no physical home button here) and plugging in USB. Whereas my stock kernel/firmware requires both volume buttons. Peculiar wouldn't you say?
[Galaxy S I9000 Android Development] kgk888:
There are sub forums for a reason. To prevent bricking from using the wrong firmware and confusion when explaining things. If you view them as "concentration camps" that's a vision entirely of your own making. You can blame U.S. carriers for each insisting they have their own special version of the device.

So instead of him simply following established guidelines on flashing the Galaxy S, you think it's best to complicate the issue by using your half n' half device as a guideline?

Plugging in a Galaxy S while holding down the volume button does nothing but bring up the battery charging symbol. This is why there are [How-To]'s and [Guides]'s.
[Galaxy S I9000 Android Development] Zilch25:
No sir I don't, but I fail to see how my instructions would have put his phone in any jeopardy of bricking if it didn't even get him into download mode. Oh the horror! I've hardly advocated doing anything that would be in any way detrimental to him, his device, loved ones, or pets. So I'm not exactly sure how this struck such a nerve with you.

A lot of good comes from the community being more united and less segregated, more minds, more ideas. Perhaps we can both agree that maybe if you can't figure out how to use download mode perhaps using a version 1 beta of a kernel based lag-fix might not be the best idea and perhaps using Chainfire's method was the right decision?
[Galaxy S I9000 Android Development] HaTeNL:
I've installed JM7 and this lagfix. Quadrant score aprox. 1700. I don't feel any difference! When installing an app I still have huge lags.. Not anything near speed in the youtube video :(
[Galaxy S I9000 Android Development] kgk888:
I've offered nothing but a calm, rational response. I also never said you endangered his device. You seem to be the only individual who's had a nerve struck with your "concentration camp" responses and other dramatic flair.

I also never stated you shouldn't offer advice. But if you are not familiar with a device or do not own it, simply refer or copy/paste the flashing instructions. Otherwise it just breeds more confusion rather than helpful community. When people find that post when searching for the same problem and sit in front of their computer wondering why "volume down + usb connection" garners them nothing but a battery symbol, it doesn't help.

Have a nice day.
[Galaxy S I9000 Android Development] Zilch25:
Eh sorry, I can be a bit of a sarcastic goon sometimes. I'm vehemently against the concept that our devices should be completely segregated and treated as 100% different devices, so I overreacted a bit, I do apologize. Sometimes you can read a bit too much subtext into things you read on the internet. I've also made a mental note of what your download mode procedures are and will be sure that when dispensing advice I follow them. My honest goal around here is to help, and to learn at the same time- I've no desire to see anyone led astray.

Hopefully there's no hard feelings on either side, but I do honestly want to stop crapping up this fine thread with our off-topic silliness. Truce? :D
[Galaxy S I9000 Android Development] bucklino:
Ok man.....Thanks again. :)
[Galaxy S I9000 Android Development] kgk888:
Agreed.

Of course there's no hard feelings :o

I really think they need to combine the App/Theme, and Accessory sub forums though as those are really pointless to keep separate. The dev forums most certainly need to remain separate though, as we've seen how easy it is for a US device to be bricked with European firmware and vice versa.

I really, for the life of me, don't understand why they had such a large product differentiation for the U.S. markets though. I actually prefer the Vibrant in terms of the four button touch layout, but they don't have the front facing cam.

If it was my choice, the Vibrant (with a front facing cam) would have been the only model and CDMA specific versions could then be made for Verizon and Sprint. The Epic I can see a reason for though since it has the slide out keyboard.