yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] LNJ:
So what exactly is the difference between the lag fix methods?

Vodoo vs Universal and so on?

Based on what I can see, they all pretty much change the file format to ext4/ext2 from RFS.

Other than that, are they implemented differently or is one more efficient than the other?
[Captivate Android Development] rajendra82:
Too long to fit all in one thread. Essentially the same idea, replace RFS with something else. Voodoo stays with ext4, and has been the only one I've used so far, and had no issues (thanks supercurio). Universal will allow ext4, ext2, jfs, loops, and other exotic choices. Some say it provides better performance/stability, others say otherwise. A matter of developer choice as to what is optimal, but we all agree, RFS sucks, and anything else is much better.
[Captivate Android Development] LNJ:
So Vodoo only does System and Data?
[Captivate Android Development] mrascon1086:
Will this work on the stock KB1 froyo releases by AT&T and Samsung?

Right now I'm running stock FROYO KB1+ [KERNEL] stock+Voodoo stable 5.x and was wondering if there is more ways to speed up.

or mess with the stock froyo for that matter
[Captivate Android Development] rajendra82:
Voodoo lagfix v4, by default converts system, data, cache, and dbdata to ext4. You can change that and use RFS on some of these partitions, but I am not sure why you would. Ext4 is the only FS it supports.
[Captivate Android Development] rajendra82:
Your question confuses me. What will work?
[Captivate Android Development] existz:
You can use this kernel with kb1, running it with cog4.1 now, you will have to use an i9000 modem though, since this kernel is based off i9000 sources ...I also have a KB1 sourced kernel that is very similar to this one, ..you will have to use a captivate modem with it (kb1)..just look in the development thread for it ..its also an oc/uv kernel
[Captivate Android Development] johan8:
I understand why it is confuse to you.

Basically I would say it is i897 kernel,

no matter what base it is, i9000 source or i897 source code,

it is still for i897.

On the other hand in i9000 dev.section, those kernel are for i9000.

It can run on i897, but as you know due to hardware differences,

your i897 will become no sound and wrong sensor if use i9000 kernels.
[Captivate Android Development] mrascon1086:
Oh ok, thanks guys!
[Captivate Android Development] zodiaxe66:
Nice work,love your boot screen.

I can leve with your option to toggle screen orientation(galaxy tuner apk has a orientation fix).but the previous page button is disabled(right button) why???.now i got 2, back to main screen buttons,please fix. Ps. Voodoo sound disable lagfix and system partition dosn't allways work,i need to enter recovery to disable,enable option works fine.no overclock in js8 1.5 version?. But thanx,nice kernel
[Captivate Android Development] elghouchd:
Does it? Or is it only for headphones?
[Captivate Android Development] rlorange:
Um are you a captivate or i9000 user? I stumbled into this thread thinking it is meant for i9000.... sounds like you did too? :) it's actually only for tjr captivate which has four buttons and and different orientation sensor than the i9000

Edit: ask exitz to share his test beta with you for the i9000... assuming you have an i9000 that is

Stock JPY, SuckerPunch i9000 beta#1 kernel 1.3ghz, all ext4, JVE GB Modem,
[Captivate Android Development] upNsmokeAllDay:
I don't know why but this kernel scores 300 less than speedmod or paragon at default clock speeds in quadrant?

Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood
[Captivate Android Development] LNJ:
At stock clocks without lagfix maybe. Once tweaked, it takes off.

On FF 2.6
[Captivate Android Development] upNsmokeAllDay:
Lagfix is enabled ext4.

Sent from my Amazing Captivate using the XDA Premium App Infused with Tiger Blood
[Captivate Android Development] joeshmoe08:
only headphones
[Captivate Android Development] GGXtreme:
:confused: Do you have ext2 loops enabled?
[Captivate Android Development] ridethelight:
3 months in this flashing game and never once have i bricked my phone, until now....Flashed #59, rebooted and now the phone is stuck at boot logo.....
[Captivate Android Development] existz:
FYI ..there probably wont be any updates for a week or so .. there's a few things I want to do so..next build will be v2.0 :) should be quite a few changes .. there's a few things that need to be changed, and there's some stuff I want to add.. so if im not around, this is why ..
[Captivate Android Development] ridethelight:
3 button combo to recovery isnt working.....**** man. Why after all this time did flashing #59 have to brick me....

Update: Successfully got into Download mode and odin'd back to speedmod. I dont know if i want to attempt flashing #59 again. Anyone else having an issue with it?
[Captivate Android Development] joeshmoe08:
If you had 3 button combo before then it will work with a little tampering. You are not hard bricked so it is solvable. first calm down/relax, you will make mistakes when you are stressed. Then take sim, ext sd card, and battery out of phone. Open odin on your computer and connect the phone to the computer with the usb cable (NOTE the battery should not be in so phone should do nothing) Now hold volume up + down and put in the battery and it should enter download mode. Sometimes it doesn't work immediately, so try multiple times with some time in between. If nothing working then your only option is a jig, which you can make (many guides out there) or buy. I recommend here: http://www.mobiletechvideos.com/blog/?page_id=100
[Captivate Android Development] ridethelight:
Thanks, i used that exact technique. I'm going to try and reflash #59 and see what happens.

Edit: Worked that time. Must flashed 100's of different things and this was my first ever bad flash. :/ Least i didnt brick it
[Captivate Android Development] zodiaxe66:
Your right,i've got the i-9000,tried something like this a long time(captive kernel)same prob. So i should have known better,srry for that and for sure i will ask exitz for beta version.actually it worked quite well with doc's 9.9.5 js8 rom and insanity 6.7 rom,except for the probs. i mentioned.thanx again
[Captivate Android Development] LNJ:
All except the last one in the list. Don't remember what that one is called.
[Captivate Android Development] elghouchd:
Does anybody know how i can raise the volume of the speaker of the phone above max?
[Captivate Android Development] goob1284:
What's the best scheduler? and what are the differences between them?
[Captivate Android Development] geokilla:
About the SuckerPunch 1000Hz. I thought 500Hz was the highest you should go.
[Captivate Android Development] supercurio:
There is extremely little headroom for higher volumes on Speaker.

After that, saturation.
[Captivate Android Development] caanda45:
SuckerPunch-#59-CWM.zip (5.74 MB, 338 views)

SuckerPunch-#59-1000hz-CWM.zip (5.74 MB, 153 views)

What is the difference between these two files? Thanks in advance for the answer!!!
[Captivate Android Development] NightTickler:
I would also like to know.
[Captivate Android Development] xdahgary:
100hz and 1000hz.
[Captivate Android Development] xredjokerx:
there isnt an explanation on the first post but I recall it being something like this

there are two hz values (i forgot what they're called. I think user and system hz values?)

for the 100hz version--your default hz value is 100 and the system hz value is 100 so your system doesnt have to convert from 100hz to another hz. It should "save battery."

for the 1000hz version--your hz value has to convert to the system hz value. but a 1000hz system will "be smoother"

its up to yourself to test. I personally use the 100hz version
[Captivate Android Development] Kizzmiazz:
I have not uv'ed at all and I got charging death last night to, so its not the uv settings. This has not happened since an old version of setirons kernel.

Sent from my SuperDuper!Captivate | PHOENIX RISING 4.1 | SuckerPunch Build 27 @ 1.28Ghz - 500Hz | Member of Team Phoenix
[Captivate Android Development] bts0uth:
Two nights in a row I've woke up to my phone being off. I'm using noop but I don't think that is causing it

Edit: hopefully GB will help you fix it. He spent a lot time finding a fix for charge death
[Captivate Android Development] LimaI896:
Hopfully this issue is an easy fix.
[Captivate Android Development] cumanzor:
Perhaps GB can give some input as his kernels don't have this problem anymore.

I haven't noticed any particular difference with the 500hz kernel so I'll go back to 100.

Does anyone know what changed in Voodoo Sound v3?
[Captivate Android Development] WickedNite:
I don't know what's the problem but here it is. I usually charge my phone overnight while it's turned off. So this morning I unplugged the phone and while I'm trying to turn it on, it doesn't turn on. It took me like 2 mins before it turned on, I was about to pull out the battery and surprisingly it turned on and I'm not holding down the power button. Any ideas on what happened? Haven't experienced this on SpeedMod.

Sent from my Muscles using Brain Cells
[Captivate Android Development] LimaI896:
Happened to me too after my charge death. Did a battery pull. In on answer to this as well lol.
[Captivate Android Development] delugeofspam:
Subscribed.

Long-time fan of speedmod, may flash this in the future... certainly want to pay attention to where you go with it :D
[Captivate Android Development] KonaZXIII:
Two thing I noticed-

1. No sounds when installed (it has Voodoo sounds, no?) - is this a prob?

2. I don't see a selectable option for "ext4 lagfix and all tweaks with [R] are recommended", I just see a bunch of different options and none as clear as the description you gave here in bold. Maybe I'm spoiled with Voodoo's user friendly menu (i.e. Enable or Disable)?
[Captivate Android Development] LimaI896:
Really? I have all those options. Are you sure you went into the right menu?
[Captivate Android Development] iNFRiNGE:
OK I went ahead and created your situation and then flashed using the SGS Kernal flasher and can confirm it does indeed work. Just make sure you install the Voltage.apk before you flash it.
[Captivate Android Development] jjtitus098:
Im sorry if this has been asked, but how do I get the voltages to save on boot? I don't see the file where it is supposed to be.

Sent from my Captivate running Cezar's Continuum v.2.0 with SuckerPunch 1280mhz kernel.
[Captivate Android Development] silverslotcar:
system/etc/init.d and the file name is S_Volt_Scheduler
[Captivate Android Development] jjtitus098:
I've checked there and there is no file there.

Sent from my Captivate running Cezar's Continuum v.2.0 with SuckerPunch 1280mhz kernel.
[Captivate Android Development] ryude:
System has to be r/w in order for it to write there, probably why it isn't saving.
[Captivate Android Development] KonaZXIII:
There's more than one? I'm talking about the recovery menu(s). Nowhere in them is this exact term - "ext4 lagfix and all tweaks with [R]"

"Tweaks" and "Lagfix" are in two totally different places. Neither says "install all tweaks".
[Captivate Android Development] silverslotcar:
You can click on tweaks and click on the ones with (R)s next to them for recommended. There should be 4 recommended tweaks. Then under lagfix it should show on option to convert the partitions to ext4.
[Captivate Android Development] KonaZXIII:
Sooo, if they're ALL recommended why is not automatically installed with options to disable them individually for the advanced users? ;) lol

Another nugget I just found. I installed this kernel with a full battery. After it fully rebooted and I selected some tweaks and it did it's thing, it finished with 95% battery capacity- I am now struggling hard to get the batter to charge

fully

. I used CWM to clear the stats and I've been doing the charge full/power off charge full/power on charge full/etc., and it has yet to get past 97%.
[Captivate Android Development] silverslotcar:
They aren't ALL recommended. Obviously you haven't even entered recovery and seen the options for yourself. Its EXTREMELY simple if you ask me. If your flashing kernels then you probably have a custom rom, and if you have a custom rom, then you most likely have an extended power menu!!! Just hit recovery on that menu and go to advanced speedmod options then tweak options.
[Captivate Android Development] KonaZXIII:
Tip for the Dev/OP- Maybe you should title this kernel as "for the advanced users",

or

provide clearer install instructions?
[Captivate Android Development] silverslotcar:
LOL flashing kernels is advanced!!! You flash kernels, but you don't know how to navigate in recovery???!
[Captivate Android Development] Soccer_Dad:
An update on the "mini-thread" I started a while back, about converting /system to EXT4:

In a nutshell, it didn't work. I didn't notice any change at all. Actually, my animations were pretty choppy at first, until I re-overclocked. ...But I didn't notice any difference in feel, and the benchmarks were about the same as prior to the system lagfix. I converted back and forth a couple times. Pretty much no difference.

Well, except for screwing up stuff. I lost root. I was trying to check my Galaxy Tuner sound settings, and the program would hang up with a few of the items. I was going to reinstall through TIBU, but it was obvious what the problem was, when I went into TIBU and it couldn't get root.

And that probably explained my (previously) inexplicable loss of GPS lock, in some fashion. I was fine yesterday, but today I would get an instant lock, and then none of my mapping programs could find me again. I could exit out, come back in, lock in my position for a moment, and then it was gone. Anyway, I was able to restore root through CWM recovery, and I went back to last night's nandroid backup anyway, and everything came back the way it was supposed to. But I'm not reapplying the lagfix to /system.

Obviously, not everyone has this issue, or the option to convert /system wouldn't be there. But in case you find yourself in the same boat, this is what is going on.
[Captivate Android Development] mcmac7:
When I flash this kernel. My back button no longer functions properly (i9000T). It just takes me to the home screen and always and doesn't actually go back. It also doesn't vibrate when the button is touched like it should (although menu button still vibrates). Also there's no selection 'audible selection' tones being played either. Don't have these issues with other kernels. Pls fix.
[Captivate Android Development] rajendra82:
Thete is a much easier way to check if the conversion worked. Just type mount in Terminal Emulator and look at the output. It will tell you what /system is mounted as. If it says ext4 it worked, if it says rfs, it didn't. Simple as that. I notice a huge reduction in lag with ext4 versus rfs, which is why I voodoo.
[Captivate Android Development] froli13:
It's what happens when you use a Captivate kernel on a non-Captivate device.
[Captivate Android Development] aalh:
he should try an HTC Aria kernel, I hear they are FAAASSSTTT on an i9000T:p

>>>>J O K E<<<<<<<<
[Captivate Android Development] disellusional:
are there improvements in this over the paragon kernel?
[Captivate Android Development] froli13:
Read the OP/Changelog and/or try it yourself. It's the best way to get answers to your question.
[Captivate Android Development] RichMD:
Deleting voltage control boot settings is no longer required?

Hi Existz,

I tried searching and I didn't see anyone ask this question. In the installation instructions for previous versions, it said to delete the voltage control boot settings prior to flashing the new version. It doesn't mention that anymore and your update script doesn't delete it. Have you somehow resolved any issues it would cause with an existing file during a flash?
[Captivate Android Development] existz:
Theres just certain builds that need the voltage control settings deleted..for example, if I put in a new default scheduler, since VC writes the scheduler to the boot settings, it would need to be removed so that the new scheduler is default, instead of whatever the VC boot settings tell it.. also, for example, if I add/remove a frequency, then the boot settings need removed, ..etc..etc.. But it does not need to be removed when, for example, I update voodoo sound or something like that, since its nothing that effects the VC boot settings... So in short, there will be versions where it needs deleted, then versions where it doesnt...But if it does need to be deleted, Ill have it in the update-script to automatically do it..
[Captivate Android Development] disellusional:
exist is your lagfix settings all ext4 includilng the loops and the last one?
[Captivate Android Development] existz:
No its system, data, dbdata, cache , I dont use loops
[Captivate Android Development] aalh:
the loops are disabled by default in SP (iirc)

they are "fake" filesystems that give boosts to benchmarks, some improvement to some tasks, and zero benefit to stability or security

I have never used the loops

the default SP settings on lagfix are best for a phone to use

if all you want to do is run benchmarks, loop away;)
[Captivate Android Development] disellusional:
thanks for the info guys. i think my settings are currently ext2 so i'll change and see whats the diff
[Captivate Android Development] existz:
v2.0.1 changes so far-

-new name and boot logo :)

-now non-oc and oc versions

-added more frequencies (up to 1.6ghz)

-new sysfs file to change cpu threshold

---boot script for performance and battery saver (working on adding to cwm *MAYBE*)

-still working on alot more

I wont be going by the build #s anymore, so disregard those...will be v2.0.1 ..v2.0.2..etc..
[Captivate Android Development] doreyu:
Ohhhhh cool, can't wait!
[Captivate Android Development] LNJ:
Good news.

ETA so I don't keep checking back like a kid excited over candy?
[Captivate Android Development] existz:
Probably Tuesday-Wednesday-Thursday...some where around then
[Captivate Android Development] disellusional:
what's boot script for battery saver? that caught my eye
[Captivate Android Development] LNJ:
You're killing me :)
[Captivate Android Development] existz:
It will be a boot script that adjusts the cpu threshold values for best battery life, then there will be a script for performance.. I added a sysfs file that controls the threshold values, so with the scripts you can adjust it to your needs (better battery or better performance)
[Captivate Android Development] existz:
lol..i would give a more exact etc, but theres alot of things I want to clean up/add/fix..etc.. so im not exactly sure how long its going to take..depends if I run into any issues or not, if it all goes smoothly then should have it up in a day or two, but..the way things go anymore, it will probably be more towards wednesday-thursday..
[Captivate Android Development] LNJ:
No worries... I'm sure it's worth the wait!
[Captivate Android Development] 13_:
OoOoooOoOOo....

Enthusiastically waiting.... :D

Sent from a Captivate on Bluedipity 6.2, SP#59, JQ1 with Xda App
[Captivate Android Development] Rodman101:
Ok so I've been running serendipity 6.2 and suckerpunch 59 for a while and I love it but for the past day or so my accelerometer won't work at all. Could someone please help

I'm feeling serendipitous...

I'm feeling serendipitous...
[Captivate Android Development] froli13:
Try wiping cache and dalvik
[Captivate Android Development] Rodman101:
I tried wiping dalvik and nothing but I can't find normal cache

I'm feeling serendipitous...
[Captivate Android Development] bryman27:
I think it's the fourth option on the main recovery menu.
[Captivate Android Development] Rodman101:
Nothing I trough it twice and the circumstances under which it stopped were interesting: I was playing a game using the accelerometer and it suddenly stopped working and I've tried reboots and now this but still nothing.

I'm feeling serendipitous...
[Captivate Android Development] froli13:
Maybe hardware problem?
[Captivate Android Development] Rodman101:
Even if it is I can't claim warranty on it because it's a refurb

I'm feeling serendipitous...
[Captivate Android Development] existz:
if all else fails, redownload and reflash via cwm (NO kernel flasher app)
[Captivate Android Development] brendanmurphy:
Im on #59 now and getting lower gpu benchmarks then #52. Getting only 49fps on neo
[Captivate Android Development] Rodman101:
Do you think it's a kernel thing? Or should I just hard reset the phone?

I'm feeling serendipitous...

Edit: I tried flashing it again with cwm but still nothing
[Captivate Android Development] existz:
Lock your screen then unlock it for it to take effect ..
[Captivate Android Development] existz:
Shouldn't be the kernel, if it was.. everyone else would be having same issue, but try flashing a different kernel and see. ..
[Captivate Android Development] LNJ:
Try #58 maybe?
[Captivate Android Development] xreflection:
I flashed 59 from 56 and it didnt default to Simple I/O. Still has my previous settings from cfq. Voodoo sound 5 is working though.
[Captivate Android Development] froli13:
You had to remove S_volt_scheduller before flashing.
[Captivate Android Development] doreyu:
you didnt delete your previous voltage settings... i think he took out the script that removes it at flash because #58-59 was just a bug fix.
[Captivate Android Development] xreflection:
Oh, okay. So if I were to just set my settings to simple I/O in voltage control and save it, it should be the same thing as if I had deleted it and it got defaulted?
[Captivate Android Development] Rodman101:
Ok so I flashed two other kernels and nothing worked so I'm gonna back everything up and hard reset because I've read that might be a fix.

I'm feeling serendipitous...
[Captivate Android Development] froli13:
Should be fine.
[Captivate Android Development] Rodman101:
Ok I fixed it! I don't know what it might have been but I followed the suggestion of an i9000 thread that said factory restore phone and as soon as it booted back up accelerometer worked fine! Thanks to everyone for their help! I feel loved here at Xda developers :D
[Captivate Android Development] fractaline:
stability test

so , i'm just trying out the process in the mini oc/uv guide.

i'm assuming i should use 30+ successful core runs not ram runs??

i used the config displayed in the op. and i loved what it did for performance but not for the battery life. looking for a middle ground.

also how hot is too hot for the battery?
[Captivate Android Development] rajendra82:
You have to shoot for 30-50 core runs, and ignore the quicker RAM runs. I've heard people say that less than 45 C is fine for the battery.
[Captivate Android Development] fractaline:
mines at 49 degrees currently running stability test ............. or does it mean core temp.....? is there some sort of cut off at danger zone???

just being paranoid.......not you johnny.

1120 mhz all uv -100, went thru 30+ runs and 15-20min neocore.....how much lower to go?

seems there is no real answer just alot of testing......... good for addicts
[Captivate Android Development] Johnny Paranoid:
existz, not sure if you're aware of this but if you dl SP #59 thru SGS Tools you actually get #56.
[Captivate Android Development] NightTickler:
Hey just curious, I flashed sp #59 via the sgs kernel app from sp #9 voodoo kernel is that a bad idea (i.e. Using the app vs cwm). Also, after I flashed I applied the SpeedMod ULK lagfix found in CWM, was that wrong? As I heard you can use it as sp is based off the SpeedMod kernel.
[Captivate Android Development] johan8:
i897 audience chip

Hi existz,

Is it possible to add i897 audience chip capability into SP ?

and is it also straightly require use with i897 new modem.
[Captivate Android Development] sixstringsg:
Usually kernel flasher works, once in a blue moon it causes errors so you should be fine. As for the lagfix, that's correct, it actually would be enabled already coming from the voodoo one.

Sent from my CM7 powered captivate