yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shaolin95:
ha! That is how it goes...I have been using it for a while and I like it so far :D
[Captivate Android Development] Rhiannon224:
I use the SGS info app from the market.
[Captivate Android Development] johan8:
When the phone hang/freeze, it will reboot itself in a minute,

no need to pull the battery out.

I'm using 1.4.2 128 now.

Don't know what's the different from XT, but it seems a bit unstable in some circumstances.
[Captivate Android Development] aleadam:
From the OP:

Changelog:

- v1.4.2

implemented Tiny RCU

re-enabled Samsung's bootanimation when there's no bootanimation.zip

re-added -noatime optimization script

XT variant: 1280MHz, config optimizations: HZ=500, PREEMPT_VOLUNTARY, UACCESS_WITH_MEMCPY, KSM (possibly unstable, slightly higher performance and battery drain, might be necessary to lower UV)

If you don't want to test an experimental kernel, then don't install the one that specifically says "possibly unstable"...
[Captivate Android Development] ncundari:
bobblx I had the same problem of people hearing an echo on their end but me not hearing any. I had installed the 1280 overclock version of the kernel. I fixed it by installing the JK3 modem provided on the first post.:

setiron_v1.4.2_1280_jk3modem_cwmupdate.zip

If your not using the 1280 kernel maybe try the other JK3 modem update.zip listed.

To install it,

1. copy .zip file to root of sd card

2. reboot to recovery mode (hold vol up + down + power)

3. select .zip from sd card (not the first install update.zip option)

let it do its thing and reboot the phone. Should be crystal clear sound now.
[Captivate Android Development] johan8:
I read that,

but don't know what is HZ, PREEMPT_VOL etc...

And one more problem is the Haptic vibration intensity is too weak !

I've tried flash back to i897(AT&T), the original haptic feedback is very strong even just Mid level of vib intensity.

But with i9000, I can say it is 200% weaker.

Is there any tweak I can make the haptic feedback more strong?
[Captivate Android Development] designgears:
This was tracked back to SuperPower. Disregard.
[Captivate Android Development] bts0uth:
I do want to test an experimental kernel lol. I was just letting SetiroN know that XT version does not work with vignette. It always freezes on initisaling camera. I've tried it on different roms and it never works. Everything else seems to open just fine, but not vignette. 1.4.2 1280 version works perfectly though

Posted from my Captivate running Axura RC1 with SetiroN's SuperOptimized kernel v1.4.2 1280OC
[Captivate Android Development] msm903:
is there anyway to disable OC on startup? i know i can select to limit max voltage to 1ghz each time i reboot, but an automatic way would be nice.
[Captivate Android Development] Yuna:
just disable OC while /system is mounted in RWmode...
[Captivate Android Development] b0bfath3r:
SetiroN, I just got done with flashing 1.4.2 and refreshed the page to see you posted 1.4.3. :P

Thanks for the hard work man. Every update you put out makes my phone that much better.
[Captivate Android Development] SetiroN:
v1.4.3 OUT

- fixed 2e recovery, now completely functional

- added 1350Mhz, 1400MHz and 1450MHz variants, only available as ODIN packages. The latter two have a default voltage of 1350mV. Keep using Xan's Voltage App v1.98b's 1200MHz setting to undervolt, higher frequencies replace the 1200MHz step. Remember to reset said setting before upgrading and please realize how 14xxMHz will only run on few lucky devices

- from now on there won't be a CWM version for 1350MHz+ and XT variants as well as a release integrating the modem, just install it on its own if necessary

XT variants to follow in a few hours
[Captivate Android Development] Demented71:
Holy crap that is fast...can't wait to give this a shot later tomorrow...damn jury duty...awesome work!!!

Sent from anywhere via XDA app
[Captivate Android Development] shaolin95:
Perfect timing...just went to launch so I am going for the big 1450mhz!

Let's see if it can take it :-)

So I assume to upgrade from 1.4.1 I do the following:

Back up

Remove lag fix.

Run the 1.4.2 kernel with Odin since I want 1450Mhz

Pray all is good :-)

If not, do the whole enchilada of steps from zero.

Right?
[Captivate Android Development] SetiroN:
Nope, just set 1200MHz UnderVoltage to 0, reboot in download mode and flash v1.4.3 with Odin. :)
[Captivate Android Development] johan8:
1.4.3 !

Cool !!

Waiting the XT version.
[Captivate Android Development] jhernand1102:
Which slot does the tar file go in Odin? I've never flashed just a kernel using Odin just whole ROM's
[Captivate Android Development] l7777:
Just a report from the 1.4.2 XT variant. No major issues except getting sleeping death after an overnight charge. Requires a battery pull. No other issues. I saw the same thing back on the early 1.3.x variants. Tested with all UV set to 0 as well as active.

ROM: Tayutama for Captivate 1.0.3

Kernel: Setiron 1.4.2 XT

Modem: XXJPP

Lagfix: EXT4 for all, no loops, no binding.

Scheduler: noop

UV (Low to high):150 150 125 100 100 75
[Captivate Android Development] PAulyhoffman:
PDA slot you may need to open the file and extract the TAR
[Captivate Android Development] snieves:
Damn, mine just freezes up a couple of sec after Boot Up with the 14XX kernels :( guess im not part of the lucky few...
[Captivate Android Development] jhernand1102:
Mine too...Going back to the 1280...:)
[Captivate Android Development] shaolin95:
I had a similar issue when I first tried 1280Mhz until I did a complete reinstall so I am not giving up if mine freezes :-)
[Captivate Android Development] PAulyhoffman:
mine froze on both but 1350 works great
[Captivate Android Development] hostilebynature:
Hey guys, im completely new to all this. I'm in canada with a brand new Samsung Galaxy Captivate S.

ive spent some time reading up and decided that i want to run this with the axura rom.

I have no idea where abouts to start...do i load this first and then the rom? or vice versa and can anyone lead me in the right direction to some good reading material to teach me how to properly load this kernel upgrade. Please and thanks
[Captivate Android Development] l7777:
Tried for 1450, thought I was in good shape, booted, ran linpack, then quadrant, froze during the 3d tests. 1400 completed a couple runs in quadrant but started failing the CPU tests. Linpack score also plummeted at that point. 1350 seems to be doing well though, haven't attempted any undervolting yet at that speed. One thing I'm not noticing is any real world performance increase even though we're pushing the processor 20%, 35%, or even 45% higher than it's default settings. That tells me that he clock speed simply isn't the limiting factor for the device.
[Captivate Android Development] shaolin95:
1450Mhz failed and 1400 failed :( I was so pumped. I hope 1350 works :)

Any way to add a bit more juice?
[Captivate Android Development] KaLiBLeeK:
My phone was extremely hot to the touch on 1.4.1 1280mhz. I think I'm gonna stick with 1200mhz regardless just to be safe. Haha.

Sent from my Samsung Captivate (AT&T)
[Captivate Android Development] cappyron:
trying 1400 now

Looks like it won't stay stable at stock voltages... but I don't have enough time before it locks up to change it :)...

SetiroN, can you post an updated init.d script to undervolt so we can flash that and maybe get the crazy overclocks to work? :)

Interesting... Swiftkey and TiBu freaked out when it locked up and I had to pull the battery.. had to reinstall both of those...

Ohwell :)
[Captivate Android Development] shaolin95:
Add me to the no 1400 club but 1350 works fine...I still have hopes lol

I am willing to add more voltage if needed (just a tiny bit) :-)

As an experiences PC overclocker I found it odd that everyone is failing at 1400 but 1350 works just fine..I feel something else is going on here that is not related to our CPUs not being able to handle it...
[Captivate Android Development] Jjparknyc:
Damn you guy are crazy with the oc. I'm going the opposite way. Set the limit to 800mhz with- 75 -100uv all and get 1700+ quadrant and great battery life.
[Captivate Android Development] bts0uth:
1400 and 1450 not working for me but 1350 seems stable. linpack got a 18.9 score and quadrant got 1921 on the first runs.

Hells yeah! Thank you SetiroN!! Your kernel is amazing
[Captivate Android Development] l7777:
You could use ADB while in CWM to change the script manually if you really want to push the voltage envelope. I'm finding that mine is happy at 1250mv @1350 but didn't like either 1400 variants.
[Captivate Android Development] cappyron:
I'm just trying to make that "hand warmer" app more efficient! :)

...Looks like 1350 is as stable as 1280...

And in theory, it shouldn't hurt battery life, the phone should be getting done with things faster and should use overall less energy.. maybe.. :)
[Captivate Android Development] joedon3:
Well, so far mine booted and completed media scanning on 1450! no UV yet, I'm going to run some Neocore loops to make sure it's stable!
[Captivate Android Development] joedon3:
I thought this kernel added steps up to 1450, it just jumps from 1000. oh well, it's nice to have the Linpack scores if she can handle it!

Without stress tests, my Linpack score at 1450 was 19.92 MFLOPS!!!! Excited!!!!

Edit: Damn, it locked up on first run of NeoCore. time to try 1400. :-(
[Captivate Android Development] shaolin95:
Lucky!

Did you do something to voltages?
[Captivate Android Development] gtg465x:
For those who aren't stable @ 14xx, try lowering your voltage a notch and see if that gets you stable.
[Captivate Android Development] shaolin95:
Must are not able to finish the scanning I think. Unless we can lower it say with 1350 then flash 1400
[Captivate Android Development] gtg465x:
Yep lower it before you flash 14xx. Make sure your settings are sticking after reboot too.
[Captivate Android Development] cappyron:
Yeah you'd have to change your init.d script to have it start at -50 and change the frequency.. I might try that in a little bit.. I gotta get some real work done for now though :)
[Captivate Android Development] joedon3:
Nothing yet. I'm going to try to UV a little to get it working. I'll report back.
[Captivate Android Development] slider2828:
ROM First ask questions later hahaha....

ROM then Rom Manager (Clockword Mod (CWM)) then get a Setiron CWM update package and apply zip.

If you dunno how to load a ROM, then you gotta go to the ROM threads and read the FAQs....
[Captivate Android Development] l7777:
Nice thought. I forgot that he raised the voltage for those two.
[Captivate Android Development] MarlowXim:
1450 Stable

Got 1450 mhz at -75 mV undervolt to run without issues so far. Tested linpack and quadrant.

Linpack is around ~20 on average

Quadrant is around ~2150 on average

If your into benchmarks.

If your having trouble try setting the 1 ghz stepping to no undervolt. (0 mV)

The cpu does not like to jump to drastic voltage jumps. I hope later on the frequency steppings can be customized. Since the most ones used in fast scaling are 400 mhz, 800, mhz, 1000 mhz, and last stepping. I'd rather do away with 1000 mhz and place 1200 mhz instead since they consume about the same voltage. (raspdeep is apparently working on this)

Thanks again to Setiron for releasing these customized steppings
[Captivate Android Development] joedon3:
I'll give -75 a try before I go to 1400. thanks!

Edit: I'm getting freezes and reboots at -50 and -75. :-(
[Captivate Android Development] joedon3:
So far 1400 is stable at full voltage. linpack score 19.2. not shabby....
[Captivate Android Development] joedon3:
How about adding steps? Unhelpful was able to add several steps to his Captivate kernel a couple months ago.
[Captivate Android Development] shaolin95:
***TO MAKE UV SETTINGS STICK, NAVIGATE TO /system/etc/init.d/ WITH ROOT EXPLORER AND MOUNT R/W.

I am doing the above then setting the changes to bios but nothing gets added to that folder...what am I missing?

NVM it worked now...testing OCes again.
[Captivate Android Development] MarlowXim:
Look at raspdeep's code

Yes, but this kernel's frequency stepping is based on raspdeep's code look in the i9000 forums to get an idea how this steps up or the source code itself.

Why add more steps that your unlikely to use? Unless if you want to do managed profiles in setcpu, but the two don't play well together as previously mentioned.
[Captivate Android Development] joedon3:
That makes sense. When I use my higher clock speeds, I'm typically going to max the CPU anyway....
[Captivate Android Development] shaolin95:
So I did the above and see the file created in that folder but the boot came back to 0s again....what am I missing?
[Captivate Android Development] gtg465x:
Rename S_volt_scheduler to S_98_volt.sh.
[Captivate Android Development] joedon3:
thanks! I'm stable on 1.4Ghz @ -50.
[Captivate Android Development] l7777:
1450 with a -50 UV seems to be working. It appears to be the limit though as any more and the system becomes unstable even if raising the 1000 voltage. Quadrant and Linpack in line with what MarlowXim found.
[Captivate Android Development] shaolin95:
Doing that -50 and 1400 now works for me...trying 1450...sweet guys thanks!
[Captivate Android Development] Bowsa2511:
holy ****, almost 1.5 ghz!!!!
[Captivate Android Development] slider2828:
Mine freezes before I can get into Voltage Control.... How can I make changes without it?
[Captivate Android Development] shaolin95:
Use a kernel that wont freeze like 1350mhz and make changes there then make sure they stick when you reboot then you can flash 1400
[Captivate Android Development] shaolin95:
I had an issue with the computer freezing and it corrupted my install as it happened while flashing....I still have a back up with Cloworkmod for 1280mhz...do you guys think I can just restore that and move on from there or better to start over?
[Captivate Android Development] slider2828:
Awesome! hahaha I guess it goes against warning of resetting.... trying it now...

-50 at 1400.... Hopefully it will work....
[Captivate Android Development] joedon3:
In any case, I'd start with a Nandroid restore. If it doesn't work, you can always one-click...
[Captivate Android Development] shaolin95:
Very true :-)
[Captivate Android Development] timur525:
Can anyone make a 1350mhz CWM .zip real quick? Kinda away from computer... thanks by the way SetiroN
[Captivate Android Development] JPxM0Dz:
Thanks SetiroN!

1350 seems to be the most stable for me, flashed and benched both 1400 and 1450, but had random freezing, sometimes during a bench, sometimes just scrolling through launcher

Random settings in VC sometimes helped, but eventually it would freeze

Happy with a 1350 for now ;)
[Captivate Android Development] kr3w1337:
Running 1450 right now with no problems, had to do -50 UV because nothing else would run stable. Battery is getting owned though.
[Captivate Android Development] Shammyh:
Running 1.4 GHz without problem so far w/ stock voltages.

Been doing a bunch of benchmarks and other stress tests. Haven't had a single FC or bug-out yet, but oddly enough, Quadrant Pro CPU benchmark refuses to run, yet everything else is running perfectly. Weird.
[Captivate Android Development] gocats7:
If I UV to assist with more battery life, OC would then negate that to a degree right? If thats the case, if I disable OC via voltage app then the UV should give me greater batter life right?

Im running 1.3.5 right now but thinking of hitting up 1.4.3... not sure its worth it or not, this thing runs pretty good as it is. Will I really notice anything upgrading? I am on Perception 4, never could get 5 to work.
[Captivate Android Development] netnerd:
i'm back to 1.28Gzh :(

tried 1.45G, 1.4G, and 1.35G; all freezing or phone just shut down
[Captivate Android Development] SetiroN:
v1.4.3 XT OUT

Sorry for the delay.
[Captivate Android Development] Cezar`:
Damn, 2724 in Quadrant, 19.8 in Linpack, this thing is crazy.

It is stable only with undervolting, interesting.
[Captivate Android Development] Cezar`:
What is the difference between XT and normal kernel?

EDIT: never mind, found it ;) damn ignorance
[Captivate Android Development] joedon3:
Damn this is FAST!!!
[Captivate Android Development] Cezar`:
Im on 1.45G with UV set like this (from 100 to 1.45) -75, -75, -75, -75, -50, -50

using bfq

Im stress testing now, ran Quadrant 15 times, no problems.

Battery increasing temp with 1 degree per 1.5 minutes.

I started 6 mins ago and I have +4 degrees (C) in StabilityTest v1.2 (was 38 degrees originally, now 42)

EDIT: Keeps 42 degrees for the last 4mins.
[Captivate Android Development] gocats7:
What app did you use to limit it?
[Captivate Android Development] shaolin95:
I am fighting it but I dont think I will be able to make it fully stable at 1400Mhz so I will probably drop to 1350Mhz and call it a day :-)

Well at least I was able to run 1450Mhz and got a few 20s linpack scores to feel proud lol
[Captivate Android Development] slayp00n:
I am running 1280, is there any reason I need 1350, I mean it sounds sexy and all but wtf my phone has NO LAG ANYWHERE... And I am lazy to flash and have stability issues, are all phones running mint at 1350? higher is the beginning of problems?
[Captivate Android Development] l7777:
Not really so interesting, setrion said he bumped the voltage to 1350 mV on the 14xx kernels, if stock max voltage is 1275 mV we're probably stressing the voltage regulators in addition to the frequency of the CPU. By bringing the voltage back down we're getting closer to stock and making the voltage regulators happy.

The 12xx OC won't have much effect on battery life as it can usually be undervolted to bring it's voltage very close to the 1ghz step. In addition, most of the time the CPU is at those voltages, the screen will also be on and that will suck up the most power. UVing the lower voltages will give you a good boost in standby life since that is where the CPU will spend much of its time. If you want to see how long your CPU has been in each state, read the contents of the file in /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state

Setiron left those out on purpose, hopefully no one adds them.
[Captivate Android Development] gocats7:
Fantastic, thanks
[Captivate Android Development] aleadam:
Which Odin3 version?

What version of Odin3 are you guys using? Still 1.0? To be honest, I never needed to use Odin before (except for the one-click version), so I was looking what was there. I found also versions 1.3, 1.52 and the latest afaik, 1.7 (http://xdaforums.com/showthread.php?t=821625).

Which one do you suggest to use? Is any more stable than the others? I read a few threads commenting some nasty bugs in 1.0...
[Captivate Android Development] shaolin95:
I used 1.0....maybe thats why it froze on me today and had to reinstall...I want to see the replies to this question for sure. :)
[Captivate Android Development] slayp00n:
why is that?
[Captivate Android Development] timur525:
But I have Odin and all, I'm just on a skiing trip. Pretty pl0X?
[Captivate Android Development] geokhentix:
I'm currently sitting with the 1450mhz kernel, undervolted to -100 across the board, haven't had a single crash or FC of any kind.

Highest Quadrant score was 2900, Linpack was 24.56. My chip seems to react really well to the overclock. :D I hope all of you are having good luck. And, thank you SetiroN, and the rest of the dev's, for the bangin' kernel.

Edit: I know this sounds ridiculous, I almost can't even believe it, but i'm @ -200 all around right now, and it is..fine. I'm at 30% Battery, just gonna stress test it all the way down. We'll see what happens!
[Captivate Android Development] damnitdave:
which slot do i put the tar file in odin
[Captivate Android Development] slayp00n:
go buy lottery
[Captivate Android Development] drancid:
pda

10 char

i tried 1450, 1400, 1450 xt, 1400 xt... not stable for me...

1350's pretty fast anyways!!

thank you Setiron!!!
[Captivate Android Development] Haloruler64:
I lol'd. Really.

Downloaded all 3 new OC kernels, will try from highest to smallest!
[Captivate Android Development] slayp00n:
Does anyone know if were getting in the frequency range of shortening the chip or mem controllers life...?
[Captivate Android Development] aleadam:
Nobody else replied, so I ended up using the 1.7. It works just fine. I tried both 1.45 and 1.35 versions. Usable, but lots of f/c without uv, and somewhat more stable with mild uv. I tested quadrant standard, linpack, speedtest.net, gallery and angry birds. Calendar storage (?) was giving me a hard time with multiple f/c.

But I don't have the time to figure out the right uv settings, so I defaulted to the 1.28. Testing same uv settings as with the 1.4.1 1.2. Will see...

Having seen the light with the 1.45 ghz, now I feel the urge to give it a second chance. Perhaps by the end of next week I'll have more time.
[Captivate Android Development] ncundari:
Bluetooth Headset Audio Problems - Help

I am running setirons 1280 kernel and the 2.2 ATT Captivate ROM. I updated my modem to JK3 and I thought it had fixed all previous call audio problems.

However now when I use a bluetooth headset the person Im calling can hear me 100% clear, but on my end some static/garbage is coming through my speakers overtop of their voices. I have tried these modems so far and none work: JPM,JPP,JPK,JP6,JPA, and JK3 (However JK3 gives me the best signal). Is there anyway to fix this problem? Either does anyone know a good modem to use or is there a way to block this feedback sound that is somehow coming back to my end of the call but not the person on the other end? I have tried playing around with the Audio settings in Service Mode with no luck. I am also considering trying a 2.2 ATT Captivate modem but I am afraid of what might happen while running i9000 kernel.

Any ideas greatly apreciated.

Thnx.
[Captivate Android Development] eliwu26:
Crash

Nah, everytime i use >1350 kernels, it'll run for 20 seconds or so, then freeze.
[Captivate Android Development] l7777:
BLN doesn't appear to be working for me. Anyone else?

He had his reasons, seems like it would be rude for someone else to make them up and post them since he purposely left them off. Best guess is so newbies don't apply the 1450 kernel and then whine that they can't revert because they can't boot the OS, get into download mode, or any other number of problems that a new person could run into.
[Captivate Android Development] joedon3:
I'm using 1.0. never had a problem.
[Captivate Android Development] slayp00n:
again I ask, anyone know if running the 1450 for extended periods of time is safe for the hardware? I have shortened many amd chips lifes with less then 45% overlcocks.
[Captivate Android Development] joedon3:
If you're asking that question, you don't need to OC. Of course it's going to strain the hardware more than a 1Ghz clocking would. It may take the life from 7 years to 5 or 3 years. Or maybe you'll blow it up on the first boot, who knows..... That's why it didn't come at 1.45Ghz stock.

If you shorten the life to 3 years, are you going to have that phone in 3 years?

Edit: it's also a per unit answer. I can't run mine at 1.45 for more than 2 minutes without locking it up. That'll cause more damage than if it keeps going with no issues.....
[Captivate Android Development] warri:
I'm unlucky, seems like my processor doesnt even like 1.35G shuts down every so often (lowered voltage using XAN's App)

oh well, each processor is differnt i'll just run 1280.. can we get an XT version of 1280 again?
[Captivate Android Development] joedon3:
I wonder if it's a batch thing.... I bought my Cappy on release day, you think they made some manufacturing sacrifices to keep up with demand?
[Captivate Android Development] slayp00n:
No I am happily running at 1.28, and I do need to OC, I just don't think I need 1.45 ghz for anything yet.
[Captivate Android Development] bts0uth:
Mines 1006 and handles the 1350 oc well just not the 1400's.

Posted from my Captivate running Axura RC1 with SetiroN's SuperOptimized kernel v1.4.3 O/C'd to 1350
[Captivate Android Development] joedon3:
Lol, I don't think anyone really needs it yet. I just like to push everything to the limit! :-P