yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] amtrakcn:
Got linpack a little bit above 17 and Quadrant close to 2400

The performance is amazing, just some concern on OC&UV...
[Captivate Android Development] WickedStyx:
Has anyone tried this with cog 2.3b1 or 2.3b2 yet?
[Captivate Android Development] KaLiBLeeK:
Just flashed it over on a clean install of 2.3b2 (install from SD in Rom Manager); installed the ext4 advanced lagfix, and things seem to be working well. In the process of reinstalling my apps and what not, but I used the kernel/modem combo that tytdfn posted. Haven't hit any lags/stutters yet. Color me impressed. Haha.
[Captivate Android Development] sportedwood:
ya, works great.
[Captivate Android Development] DOAlaboratories:
Has ANYONE had a problem with OC/UV yet? Because I remember on eclair my old Cappy couldn't take it at all.

Sent from my Cappy using mental telepathy, *****ezz.
[Captivate Android Development] CougarBroker:
I have

Works great... so far :cool:
[Captivate Android Development] bts0uth:
Nope. I have both items set to -75 in the voltage control app and I have verified I am overclocked to 1.2ghz and not a single problem. I ran the setcpu stress test for an hour with no errors and played a bunch of games and haven't had anything happen.

Phone is freaking fast
[Captivate Android Development] johnyhoffman:
No problems here. Got this flashed with Raw Steel and this thing is a beast. I've ran pretty much every ROM in this captivate forum and haven't felt power and speed on this thing with 2.2 until this combo. I don't know if it's the rom or the kernel or the combo. Don't care. Love it.

Dropped w/ my Samsung Captivate using TapaTalk Pro
[Captivate Android Development] MikeyMike01:
Which Scheduler is the best? Or at least, what's the difference?
[Captivate Android Development] bts0uth:
Good question. I've been wondering what's better, deadline or cfq?

Posted from my Captivate running Doc's JPO v7.5 rom with SetiroN's i9000 SuperOptimized, ULF, OC/UV, 340Mb, Re-Oriented kernel v1
[Captivate Android Development] Gurgs:
Hey I flashed this kernel and modem over Cog2.3 and everything went great except my service sucks really bad...is there any way to get my old modem back without odin or are their some settings I can change? Any help would be greatly appreciated...
[Captivate Android Development] airbillion:
I had the same problem. I used astro filemanager to copy the modem file from the cogb2.3b2 and then I pasted that over the modem in the cwm kernel with jpp modem download a few pages back and then reflased from clockwork. That kept this kernel and replaced the modem with cogs jj4. Worked pretty well for me.
[Captivate Android Development] Gurgs:
Wow thanks so much. That worked great...I was hoping I could find a way to keep this speed and actually have a phone that works as a phone too lol
[Captivate Android Development] kamots:
in the interest of switching roms, do you have to disable this lag fix the same way as voodoo? or can you just odin back to jf6 and start fresh with no disabling :confused:
[Captivate Android Development] di11igaf:
anytime ive odin'd back to stock, ive never disabled voodoo since odin will convert your file system back to stock rfs. but, some of the lagfixes in this kernel are more aggressive than voodoo with converting more partitions(voodoo only converts data i think) to or whatever you select so it may be safer to disable it. someone who knows more should answer

also, i wonder whats different with the jj4 modem compared to ji6 since right now im using the jj4 modem and its connecting to wcdma 850 and 1900 and everything is fine. with the ji6 modem, the phone would soft reboot every time it connected to 1900 i believe. so far the jj4 modem has been great with this kernel since hsupa doesnt matter to me much.
[Captivate Android Development] kamots:
thank you :) i think ill hold off on this till i read more on it, cause no one wants a borked phone lol
[Captivate Android Development] SetiroN:
I haven't tried flashing back to JF6 yet, but switching back to RFS is not necessary if you repartition (i.e. OneClick).

For those complaining about it, you WILL get a "Configuration has changed" recovery screen at the first reboot after setting lagfix options, it's perfectly normal. If you want to keep your current data, select the first option and wait (a separate backup is recommended).

Suggested and tested configuration (advanced):

ext4

ext4

ext4

ext2

ext2

ext2

no

For those with reception issues, remember that you should manually enable WCDMA 850MHz:

1) Go to phone dial Keypad;

2) Enter *#2263# (if you set to Auto, as noted above, you should see [1] Automatic[*]);

3) Select [4] Combi Bands [];

4) Select [8] WCDMA 850 (FDD V) [];

5) Select Add WCDMA_W850 [];

6) Use Menu and select Back (you should now see WCDMA 850 (FDD V)[*]);

7) Use Menu and select End.
[Captivate Android Development] di11igaf:
i think the problem is that even if it is selected and added under combi, the phone will not switch to either of the 850 bands. so if your in an area with only 850, your phone will have no service. ive tested this with the jpm modem when i had to go on a 4 hour drive and had me and my wifes captivates. mine with jpm, all bands enables(under combi), hers with ji6. her phone had service the whole ride. never lost it. my phone lost service completely for long periods of time while hers had it. YMMV im pretty sure jpp has the same problem. theres a few things that have to be done to enable 850 and it involves flashing back to 2.1-can be found in a thread around here somewhere.
[Captivate Android Development] WickedStyx:
+1

I had no service in 850 area with JPP modem despite adding via *#2263#
[Captivate Android Development] opcow:
The problem is you end up in a loop where every boot brings you back to the changed configuration screen and you can never get out of it.
[Captivate Android Development] shaolin95:
Well, the Playstation emulator can use the extra speed but for overclockers, which I am , it is just a matter of pushing everything we own to the limits needed or not. :D
[Captivate Android Development] joedon3:
exactly.... why? because I CAN! :D
[Captivate Android Development] jhnstn00:
:) nice

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] shaolin95:
My phone seems to like -75 for 1400Mhz but I cant still get it 100% stable as I want so I may drop back down to 1350Mhz. I can run Stability Test for a long time but sometimes something simple makes it freeze..gotta love it.

I am just testing 0 0 0 0 0 0 -75 noop

Since at load it works just fine the issue must be on the big jumps in speed or maybe voltage.
[Captivate Android Development] r.iqbal87:
Is it possible to progressively train your cpu? Im doing 1350 for a week, and then plan on going to 1400, and so on.. is this going to have any effect?
[Captivate Android Development] aleadam:
Coming from 1.4.1 1.2 ghz to 1.4.3 1.28 ghz, I can see a notorious improvement in battery life during standby, to the point that I thought the battery meter was not functioning because I had it over 40 min at 100%.

Obviously, I'm not complaining :) , but I'm curious: Is there any optimization/patch included that could explain this change and is not in the changelog? The only new optimization I see is to 1.4.2 adding back -noatime, but that should have an impact with high access to the sd card, not in stand by, am I right?
[Captivate Android Development] shaolin95:
You know...this is one of those hotly debated topics with CPUs...some people say you can others that you cannot.

I have seen it myself where going for the top right away wont work but going slowly does so if I have to bet, I would go with the "it could help" theory. :)
[Captivate Android Development] thehavock18:
I have not tried the -100 yet but failed to get 1450 to work with -50 and -75. I can boot up and make it through the media scanner but shortly after will just reboot.

1400 -50 -25 both seem to run but after 10 or so minutes of angry birds it locks up.

Either of these roms I have hit the 19's in linpack and 17-1800 quadrant.

Using Axura for these test.

On the 1280 rom however on Geo's Rom I was able to post 20's regularly and with -25 uv I hit 23 on Linpack and 1853 on quadrant.

Can a rom effect how well the kernel performs.
[Captivate Android Development] joedon3:
Lol, kinda like working the gunk out of an old engine! I haven't heard of this making a difference, but it's worth a shot!

I would venture to say that you're not going to train your CPU to go several hundred Mhz past its current break point, but 50 or 100 may be possible...
[Captivate Android Development] l7777:
Define "extended period". With the ability to dynamically raise and lower the clock speed, modern processors are only running at max speed for a fraction of the time. If you want to see how long your processor spends at full speed, look up the file I posted earlier.

Some numbers:

Over the last 20 hours, my CPU has spent 0.4% of the time at 1450, the majority of the time is spent at the 100MHz step, 82.5%. If I throw out the 100Mhz step the 1450 number goes up only slightly to 2.5% of the time with the majority of it spent at 400 MHz, 40%. 200 and 800 take up 24% and 29%. That's still less than 10% of the time spent at 1Ghz or above. I'm not too worried about the extra strain when it is only a fraction of the processor's time.
[Captivate Android Development] shaolin95:
23s on linpack? What ROM is that again? Did you feel an overall faster phone?
[Captivate Android Development] BL4zD:
Is anyone using this kernel with CM 6.1?

I can't seem to get the 1200 to boot. I tried with /data and /dbdata set to ext4 and /cache rfs. /system is ext4 so I don't know if that has anything to do with my issue.

I am using glitterball's kernel in the meantime with no issues.

http://xdaforums.com/showthread.php?t=842488
[Captivate Android Development] MikeyMike01:
Doesn't CM 6.1 need a special kernel?
[Captivate Android Development] thehavock18:
GEOMOD 2.2.1 and yes its been the fastes phone I have flashed however Bluetooth did not work.
[Captivate Android Development] Cezar`:
It seems that there are some problems with recovery on 1.4.3 , at least on 1.35 and 1.4 GHz versions. In Lagfix options i got stuck 2 times after choosing the lagfix type and hitting back.
[Captivate Android Development] joedon3:
Yes. I'm not sure why, but CM needs its own kernel.

When I was running CM, my quadrant CPU score was HUGE, way past the N1. On the Samsung based ROMs, it is much lower.

That's one reason why true vanilla Android is so wanted....

Edit: BTW, I have quadrant advanced where it breaks out each section of the score.
[Captivate Android Development] aleadam:
I had that in the 1.35 version. It said "back button blocked" or something like that (sorry I don't remember exactly). I thought it was because I was doing an adb push of the 1.28 version to /sdcard/ at the same time so I did not think again about it. Solved it with an adb reboot recovery.
[Captivate Android Development] BL4zD:
Bummer, I thought that was due to the partitions so I gave this one a try.
[Captivate Android Development] existz:
Any plans on putting hardcores new battery tweaks and ext2/3/4 lagfixes? Would love to have a 1280 300hz or 500hz with these
[Captivate Android Development] slayp00n:
I do to on my desktop, but there i just have to flash bios, and if i cant reboot clear some jumpers... But on my phone having to flash a new kernal every time... I am lazy as **** man lol.
[Captivate Android Development] shaolin95:
I love flashing my phone cause it makes me think of something else when at work
[Captivate Android Development] DAGr8:
for me phone freeze when I go into gallery other then that it runs perfect

20.22 linpack is the best I coudl achieve tho

but my quadrant was way up there see this :

http://img253.imageshack.us/i/snap20101130232142.png/
[Captivate Android Development] JPxM0Dz:
At what speed was it freezing and what are you running now?

Sent from Axura RC1 Captivate Edition
[Captivate Android Development] DAGr8:
Im back on 1280 , no offense to seti but that kernel is not stable yet ...

I was running 1450 pretty stable doin bunch of stuff .
[Captivate Android Development] JPxM0Dz:
Yeah I'm back to 1350, 1400 and 1450 I had random freezing. I should retest as I have found my phone does not like UV, so I'm 0's across the board.

Sent from Axura RC1 Captivate Edition
[Captivate Android Development] MarlowXim:
Possibility of Adding BFS Sched

Hey Setiron Was reading about the different schedulers available and it may interest you. Seems very close to deadline scheduler though.

Souce patches are located are as well as faq

http://ck.kolivas.org/patches/bfs/

Quick question on 1450 kernels did you modify the gpu clocks on this frequency. After testing it for while it would lock up on gpu tests only. Cpu stability tests were fine had it going for 10minutes+ and no errors. Looked at the raspdeep source he had available on github couldn't make sense, if gpu clock was modified. However he only scaled voltage to 1300mV in his newest release uv300 mentioned a bug, perhaps it may be related to mV.
[Captivate Android Development] DAGr8:
EXACTLY (caps lock !!!! )

stess test cpu quadrant 3 times in a row works great but open the gallery, swipe left and rigth for like 20 seconds phone would freeze everytime eventho all images were loaded without a hitch .. same for going into settings phone would freeze for no reaso ..
[Captivate Android Development] Cezar`:
[REQ]

Is there any way to have all frequencies in one kernel?

Like 1200-1280-1300-1350-1400-1450 and to be able to switch between them in Voltage manager?
[Captivate Android Development] crazililazn:
Seems stable at 125 125 100 100 100 50 for me with the 1350 kernel.

for the 1400 kernel, even with no undervolt, i couldnt get it stable :/
[Captivate Android Development] johnny13oi:
Hey setiron, is there any chance you would be able to add into the kernel whatever it is to make Wifi Calling app for T-mobile work? I know it has been done on the Vibrant kernel but not the Captivate kernel.
[Captivate Android Development] MarlowXim:
Try undervolting to 100 or 75. I've noticed the chip is having problems overvolting at 1275+. (Or 1350 mv) Have mine running with 1400 xt stable at -100mV
[Captivate Android Development] crazililazn:
Hmm, will do. I think i did try 75 and it crashed during a quadrant 3d test.
[Captivate Android Development] MikeyMike01:
Haha, that's why my desktop is 3.8 GHz.

The 7.5 CPU Score was dragging my Windows Experience Index down by 0.1... I had to do it!
[Captivate Android Development] bp2826:
From a fresh install with nothing loaded i don't see anywhere close to 348mb of available ram usually sits around 200, am i doing something wrong??
[Captivate Android Development] chrism0483:
I see you sent this using Axura RC1. I really want to flash this Kernel and i currently am running the Axura RC1 rom. Is this something you reccomend or have already done. And If you have, did it flash easliy without having to use one of the listed methods if it didnt boot correctly. Sorry if this seems to be a lame or newb question. But i wanted to be safe then sorry. So please let me know if this is something you hgave done or know what version i should use and how i should do it

Thanks ahead of time if you can be of any help :)
[Captivate Android Development] MS3Zoom24:
ok new territory for me,

if I wanted to change the kernel in a ROM would i jsut need to swap out the lights.s5pc110.so file with what ever kernel I wanted (v1.4.3) and inversely replace it

Thanks never done this before, just themeing and installing apk apps
[Captivate Android Development] MikeyMike01:
The lights.s5pc110.so and the zImage.
[Captivate Android Development] glitterballs:
What? No...just no. Stop right now before you need to make a post about bricking your phone.

Sent from my brain using thumbs 2.0.
[Captivate Android Development] timur525:
With the 1400s most people seem to have problems with the media scanner, so if you just sat 1ghz as Max everytime you turn your phone off(using Xan's voltage app) you would do media scanner in 1ghz and then uncheck it again and you'd have your 1400/1450 step back! Yeey!
[Captivate Android Development] shaolin95:
Media scanner was a problem for me before changing the UV to -50 or -75 for 1400Mhz...the problem I have is what someone mentioned earlier, it seems to run CPU stability tests just fine but doing simple things like scrolling thru app icons in launcher pro so it might be video card related maybe...or we just hit that cpu wall some CPUs have like my i7 920 which got to 4.1Ghz and after that anything else becomes unstable.
[Captivate Android Development] joedon3:
I wouldn't think the GPU clock is affected, I'm still getting the same framerate cap durring Neocore and Quadrant. If he used a BUS OC instead of a multiplier OC, then framerate would increase as well.

But a GPU OC would explain why lockups are occuring during graphic intensive apps.
[Captivate Android Development] shaolin95:
Well the thing is we are still locked at 56 fps arent we so we might not notice the effect of a faster gpu perhaps. I just feel something else is preventing most of us from stable 1400mhz :-)
[Captivate Android Development] joedon3:
I asked a few weeks ago about a fps cap on our device and never got a straight answer, but I think the consensus was that we didn't have a cap. I dunno though...
[Captivate Android Development] DAGr8:
+1 .. kernel problem obviously the cpu can take it , I am pretty sure MOST hummingbird 1ghz processor can be overclocked to 1600 mhz we just need the proper kernel .
[Captivate Android Development] TheYar:
I did this as an experiment:

> adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# cd /system/etc/init.d
# touch S_volt_scheduler
# chmod 777 S_volt_scheduler

Which leaves the rest of the startup script folder permissions intact but enables writing the voltage script from the app. Tested it and it worked fine; held voltage settings after reboot. FYI for anyone who wants to pretend that they are security-minded.

EDIT: Actually, this setup won't allow you to clear boot settings without going into shell again, so I wouldn't recommend it unless you're happy with your UV settings.
[Captivate Android Development] MS3Zoom24:
OK then what do i need to do if i upload the 1.4.3 cwmupdate and it doesnt work so then im suppose to revert back to the 1.3.5 kernel?
[Captivate Android Development] peachpuff:
Yes, just flash the old kernel in recovery. Unrelated tip, always have usb debugging on.
[Captivate Android Development] drancid:
lol that way's kinda dangerous cause when if u forget to set it as 1 ghz limit just 1 time then ur phone will be stuck in the media sanning process..

Which means u need to flash ur kernel again..

if i were u i am just gonna use a stable kernel instead of doing that..

Just my oppinion..;)

Sent from ATT Captivate operated by Perception build 5
[Captivate Android Development] xfernand:
Does anyone has the instructions on how to perform a restore via Clockmod Recovery of a ROM using SetiroN?

I tried these steps but didn't work:

Reverse whatever lagfix there is

Wipe data

Wipe cahe

Execute CM restore

I tried to comeback from Cognition or Docs to Axura by restoring the Axura backup but had no luck.... Odd behavior after booting and/or FCs.

Thanks...
[Captivate Android Development] peachpuff:
I dont think cwm backup/restore actually backups up the kernel/modem, thus giving you issues when restoring roms with different kernel's.
[Captivate Android Development] crazililazn:
Just noticed something today. Using the 1350 kernel, my phone is stable with everything, OTHER than the stock samsung music player. Everytime I open it, it just closes a bit after.

Also, has anyone had trouble using voltage control 2.0 rc2 with the 1350+ kernels? It just force closes for me, and i have to resort to using 1.98 beta :[

EDIT: ends up my phone needed more voltage. Lowered my UV to 125 125 100 100 100 25 and all is well. Damn, but phone sucks at Ocing ><

I really hope its the kernel and not my phone :O
[Captivate Android Development] shaolin95:
Well my phone does 100 100 100 75 50 50 stable so I only do better at the highest as you have lower voltages in the others. :-)

I too use 1,98 as 2.0 wont work for me
[Captivate Android Development] shaolin95:
OK so this is for sure not the CPU itself having issues at 1400 etc.

I tested with neocore and at -50 where my CPU passes all cpu tests just fine, neo core wont start or freeze. At -75 it almost starts and at -100 it runs perfectly BUT at -100 my CPU runs out of juice and restarts when pushed too hard so there is a relation here between video and cpu with this kernel OC
[Captivate Android Development] zielins1:
Apologies for this if it's the wrong location to post this or if it's already been found. It's a wired headset thing, and I posted it here because this kernel seems to be the most ubiquitous at the moment.

I know my iPhone headphones work for my Captivate, and I found online (whether or not it's true) that on those phones (and therefore, likely, ours):

P1: L

P2: R

P3: Ground

P4: Mic

Whereas a listing shows the I-9000 at:

P1: L

P2: R

P3: Mic

P4: Ground

Makes sense for it not working. Is there any way to specify this somewhere in the kernel, perhaps in the code that watches for the interrupt in the Mic line and interprets it?

Again, hope I didn't repost anything already known.
[Captivate Android Development] fatttire:
Yeah, thankfully we don't have i9000 hardware cause iphone headphones don't have a mic with them.

Xcaliberhand is aware of that... it is more complicated than switching I/o's...trust me hes pretty knowledgable

Prob wont get a fix until froyo cappy source is out (official release) but who knows
[Captivate Android Development] Pirateghost:
wait....you mean that mic i was talking into all those years wasnt a mic at all?? holy crap!
[Captivate Android Development] MikeyMike01:
I believe that his poor grammar was trying to convey that the iPhone headphones microphone didn't work with the i9000, not that it wasn't their.
[Captivate Android Development] Pirateghost:
;)

i figured that....just messin around
[Captivate Android Development] MarlowXim:
RFC v4+ and memconfig tweak

Found some more interesting tweaks that might be beneficial to the kernel Setiron, in addition to BFS.

automated per session task groups

Description and video, however it was designed for desktops not sure how it scales on mobile devices.

http://www.phoronix.com/scan.php?page=article&item=linux_2637_video&num=1

I included this source patch.

View attachment rfcv4p+.zip

As well as author's post.

https://lkml.org/lkml/2010/11/30/121

memconfig

Not sure what parameter you set this as, but I believe this is the lowest it can go.

CONFIG_VIDEO_SAMSUNG_MEMSIZE_TEXSTREAM=2048

Should cause 3G Video call to fail completely while in phone call. Could squeeze in to free more memory.
[Captivate Android Development] 10tonhammr:
I tried out the 1350 kernel last night by just flashing it over Perception 5. It seemed stable at first, but today my phone was a complete disaster. I bit the bullet and flashed back to stock, master cleared, reflashed Perception 5, reflashed the 1.4.3 1350 kernel, and tweaked my UV settings to 125, 100, 100, 75, 75, 25 and all seems to be well. Its handling the stress testing from Neocore perfectly, and no freezes or FC's. Gotta spend the next two days battery testing, but this looks promising... and smoking fast!! Kinda wished I started with 1450 though, just to see how it would perform, but I guess that's what nandroid is for. :)