yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] IStern:
interesting, I was getting ~15.6 on linpack with build 26, 1.12ghz OC 100Hz. After upgrading to build 30 at 1.2ghz, dropped to around 14.3. Any ideas?
[Captivate Android Development] existz:
Are you sure you enabled it in "states" , just setting the max clock will not work, it will still stay at stock speeds, you have to make the frequency active first, use VC
[Captivate Android Development] IStern:
I'm an idiot, thanks!
[Captivate Android Development] froli13:
Downloading now. What are the best/suggested UV settings (and scheduler) for this kernel?

I know it depends of each Captivate, but I just want some of your best settings so I could start from there.
[Captivate Android Development] existz:
Read Shaolin95's Mini Overclocking Guide, posted a few post up and in the OP, as for scheduler, use CFQ, as Hardcore has actually tweaked it for that specific scheduler, make sure to turn the tweaks on in CWM.
[Captivate Android Development] mkr14:
The mic is not working with HPcall support.

Hardcore stated that he needed to modify the driver to get the mic working with his Speedmod kernel
[Captivate Android Development] WickedNite:
So the SuckerPunch #30 is 1.4ghz by default? No more 1.12ghz version?

EDIT: Nvm, I got it now. :D
[Captivate Android Development] froli13:
Thanks for the info!

Also, does flashing a new kernel affects battery stats? Is it suggested to charge my phone to 100% before flashing or it only apply when flashing ROMs?

/noob
[Captivate Android Development] existz:
No its 1ghz by default, you can use VC to enable which frequency you want under "states" (I.e you would enable 1120) then set max clock to 1120. With this 1120, 1200, 1280,1360 and 1400 are all in one kernel, just set which you want. The reason for setting "states" is if you oc to 1280, you can choose if you want the 1120 or 1200 step in there as well, or you can choose not to
[Captivate Android Development] AJerman:
Ouch, went to sleep and never woke up the very first time I plugged it in. Looks like this kernel won't work out for me.
[Captivate Android Development] existz:
This is not using the same code hardcore first used, have you verified hpcall does not work? Or just going by hardcores? Cause if it does not work ill fix it
[Captivate Android Development] mkr14:
HPcall works, however, the mic does not work while using it. I had Speedmod running yesterday and it was working fine. Flashed Suckerpunch #30 and it is no longer working. Verified through testing.

In his K12S-T3 release post Hardcore mentions that he had to modify the driver to get it to work.

http://xdaforums.com/showpost.php?p=10938303&postcount=1470
[Captivate Android Development] existz:
K thanks, ill get it fixed in next release
[Captivate Android Development] c0ldburn3r:
Read the OP.
[Captivate Android Development] WickedNite:
Nice. Thanks, that makes me understand better. :)
[Captivate Android Development] shaolin95:
Oh by all means...actually I am honored! :)

Feel free to edit it as you like if you find out better ways of doing it as it is just a basic guide from my experiences but I am sure others may have useful stuff to add to it.
[Captivate Android Development] existz:
Just to verify, so when using headphones and a call comes in, the other side cannot hear you through the phone mic?
[Captivate Android Development] mkr14:
Correct

10char
[Captivate Android Development] existz:
Ok, fixed and tested, uploading now.. Build #31
[Captivate Android Development] cumanzor:
For some reason I cannot get past 10 with release #30, even at stock settings. Back to previous settings.
[Captivate Android Development] existz:
**UPDATE**

Build #31 (01/30/11)

Fixed hpcall support (mic now works) - Thanks Hardcore/Xcaliburinhand

Updated initramfs to Hardcores K12S
[Captivate Android Development] sjavvaji:
does updating the initramfs give us all the new features of Speedmod?
[Captivate Android Development] existz:
No, not necessarily, which features are you referring to? As ive added in most of what Hardcore has done and includes everything up to K12P, except his sound tweaks, those are stock voodoo sound 3 settings, and my version does not include Hardcores gamma settings that are in K12S, plus a few other things as well, everything is in the OP in the changelog
[Captivate Android Development] ThisWasATriumph:
Converting /system to EXT4 just hangs on the Suckerpunch logo. What do I do at this point? Dont really want to yank it.

Never mind, I fixed it.
[Captivate Android Development] cumanzor:
Well I noticed something that is probably completely unrelated. I'm unable to see the logcat

Unable to open log device '/dev/log/main': No such file or directory

Guess that means it's time to reflash the ROM. :D
[Captivate Android Development] existz:
Logcat is disabled by default, enable it in recovery, speedmod features/tweaks

That was my fault, must have deleted it from the OP by accident when cleaning it up, ill add it back
[Captivate Android Development] sjavvaji:
so what does updating the initramfs do?
[Captivate Android Development] existz:
The initramfs is a root filesystem which is embedded into the kernel and loaded at an early stage of the boot process. It provides early userspace which lets you do things that the kernel can't easily do by itself during the boot process. , its what controls the lagfix, the tweaks options..etc, etc,
[Captivate Android Development] Nuskul:
Just wanted to say I've been using #26 for a couple of days now. Great battery life and speed. Will be updating to 31 shortly. Great job and thanks.
[Captivate Android Development] existz:
Next release should be a good one in terms of battery life, more than likely going to ditch the 1360/1400 steps and add 600/900 . It will be something everyone will benefit from instead of just a few lucky ones. Plus should give use some better battery life as well with extra lower steps
[Captivate Android Development] WickedNite:
Hmm. Sounds great but I can't understand it. Any simpler terms? Lol.
[Captivate Android Development] RonH54:
Thanks for the GREAT work on this Kernel. I presently on #26 on 1120,Noop,50,50,75,75,100,125 and Super Stable and Smooth. I was getting ready to try 31(just to have the Newest) but I guess I'll wait for the next Version because I don't need 1360/1400.
[Captivate Android Development] cumanzor:
Cool. Why is it "Not Recommended" though?
[Captivate Android Development] existz:
Build #32 will be coming in a few minutes...only added Voodoo Sound 4
[Captivate Android Development] WickedNite:
That includes the improvement in battery life you posted earlier right?
[Captivate Android Development] existz:
No not yet, I only added Voodoo Sound v4 in this build, I still have to work on adding in 600/900 steps, I originally wasnt planning on another release for a day or so, but Voodoo Sound v4 just dropped ..so..figured id go ahead and add it real quick
[Captivate Android Development] sjavvaji:
did anyone get massive fc's the second reboot after clearing cache and dalvik cache...i have had this happen to me twice and it is pissing me off -___-...im on Doc's 9.1.2...can anyone reproduce this? This is the second time this happened on this kernel.
[Captivate Android Development] WickedNite:
Okay. I guess I'll wait for the one with battery life improvement instead. C'mon! Do it already! Jk. :D
[Captivate Android Development] TRusselo:
Im getting NO GPS at all since flashing.. tried clearing and re-locking. no signal.

0 satilite lockons after 2 minutes. also tried sgs fix. nothing

is that a modem issue or kernel? still getting this stuff straight...

build #30
[Captivate Android Development] zerkai:
Should be modem
[Captivate Android Development] mkr14:
The mic is not working for me while using hpcall. Seems it is routing to the headphones now.
[Captivate Android Development] TRusselo:
so that would be part of needing the i9000 modem? didnt think i needed cus i dont bluetooth my calls.

but build #29 was fine. build #30 NO GPS..
[Captivate Android Development] existz:
wtf...I just tested it and everything works like it should, sound comes through headphones and other person can hear me via phone mic, its the same code Hardcore has..can anyone else confirm this?
[Captivate Android Development] existz:
You HAVE to use an i9000 modem, its in the OP, its not just bluetooth, but all connectivity is effected ( static during calls, gps issues..etc.etc) its mandatory
[Captivate Android Development] sjavvaji:
i have ext2 loopback so i should try not to do this in the future...my retarded fault...
[Captivate Android Development] TRusselo:
are you still on build #30 from this morning #31 supposedly fixed that issue..
[Captivate Android Development] sjavvaji:
lol...stop scaring the **** out of existz
[Captivate Android Development] existz:
UPDATE

Build #32 (01/30/11)

Updated Voodoo Sound v4
[Captivate Android Development] mkr14:
On #31. Not working for me. Went back to Speedmod and it works.
[Captivate Android Development] existz:
Just tested again with #31 and #32, even used a normal 3pole headphones from a blackberry w/ no mic and it works .. can anyone else confirm or deny?

EDIT

On the phone right now, every thing works 100% <--- w/ Blackberry headphones w/o a mic.... So I know the phone mic works..and of course the caller comes through headphones

Make sure to check which kernel version it says on the phone, (Settings/About Phone) #31 and #32 has the new fix
[Captivate Android Development] Barbarian:
Really liking this kernel. Thanks for adding the new Voodoo sound updates swiftly.

Sent from my Captivate running FireFly 2.0.5
[Captivate Android Development] joeshmoe08:
Whats different in voodoo sound 4? Any drastic changes or minor sound tweaks?
[Captivate Android Development] existz:
Changelog

In the driver:

- improved volume management (no more loud notifications)

- no more light tick on audio start-up

- better mono implementation, work also on FM radio

- FM radio high frequency preservation and volume harmonization

- added 128x oversampling on record & FM radio

- removed SNR booster: didn't pass quality tests
[Captivate Android Development] mkr14:
On #32 now. Not working for me. Cleared cache etc. It is working for you so something weird is going on. What could it be if Speedmod works and Suckerpunch does not?
[Captivate Android Development] existz:
damn, to be honest, I dont know... cause like i said, the headphones im using do not have a mic, so I know the phone mic is working. We need someone else to verify, trying to determine between 2 people isnt going to tell us anything lol... so if anyone else can test this let me know...but like I said, I know its working, if it wasnt working in general then there would be no way it would work for me..

Edit

Just went back and tested #30, #31 and #32, of course #30 didn't work, but it works with #31 and #32, so the new code fixed it. But I think its something other than the code, there's another variable coming in to play somewhere

EDIT #2

The ONLY thing I can think of is where I don't use Hardcores sound tweaks, just stock voodoo sound v4, unless he has wrote some code in his sound tweaks for other headphones, which I don't know what your using so its just a guess, but im using the hpcall patch with hardcores changes to that code
[Captivate Android Development] mkr14:
Using Klipsch Image S4 earbuds. Standard headphones.
[Captivate Android Development] LimaI896:
Hey Existz tested out 3 headphones

2 with mics there were no problems, but the one with out a mic the phone mic would not pick up my voice.
[Captivate Android Development] existz:
Ok, good..got another input on this, ill go back over everything again, im left clueless as to why it works with mine with no mic... ill msg hardcore and let him think about it..give me a little bit and ill get it fixed...im dumbfounded to why mine works
[Captivate Android Development] c0ldburn3r:
Still don't see a reason not just use a bt headset. Anyways, confirmed not working.

Sent from < clever remark here >
[Captivate Android Development] LimaI896:
Existz I swear your captivate does what you want, no CD, no mic problems even though we have them. lol
[Captivate Android Development] mkr14:
It is convenient when listening to music.
[Captivate Android Development] LimaI896:
Very convenient, would be annoying to rip out the headphones every time you receive a call.
[Captivate Android Development] existz:
I promise ill get it fixed soon, wont be hard tracking down what I missed
[Captivate Android Development] LimaI896:
No rush lol, you been doing great!
[Captivate Android Development] lrs421:
This last version appears to have insane battery life...don't break that :)

You've really stay on top of this kernel. Well done!
[Captivate Android Development] joeshmoe08:
existz, You might want to check up on hardcore for your hp call problems. He might have done some extra tweaking that you might not know about. Hope it gets resolved.
[Captivate Android Development] pizz0wn3d:
Existz,

I love this kernel so much, thanks for putting out updates so regularly. I wish I wasn't such a broke college student so I could donate mega $ to you. Keep up the amazing work.

I'll test out my headphones and see what happens. Give me a few minutes.

Herp derp Captivate XDA App
[Captivate Android Development] nickm50:
Phone mic not working here either!
[Captivate Android Development] existz:
Ive got a test version going now to fix hpcall, dont know why it worked on mine, so i have a few others testing also to verify, should get it up soon
[Captivate Android Development] lrs421:
When do you sleep?
[Captivate Android Development] pizz0wn3d:
Just tested my mic with a pair of headphones that have a mic on them. Worked perfectly lol.

If it's any help, I'm running Cognition v3.02 and the JK4 modem.
[Captivate Android Development] LimaI896:
The issue is mainly headphones with out a mic. The phone mic should still work.
[Captivate Android Development] pizz0wn3d:
Oops my bad. I actually didn't even realize the pause/play button on the wire had a mic on it until I went to go post. I'll try to dig up a pair without a mic then.

EDIT: tested on a pair without a mic. Didn't work = /

Not a big deal for me though as I never use these headphones, or even usually talk with my normal pair in anyways. Hopefully this gets fixed for the sake of those that rely on they feature though.

EDIT 2: Is there a topic for voodoo sound that shows the changelog? My inferior searching capabilities didn't reveal anything =\

Herp derp Captivate XDA App
[Captivate Android Development] existz:
Voodoo Sound v4

Changelog

In the driver:

- improved volume management (no more loud notifications)

- no more light tick on audio start-up

- better mono implementation, work also on FM radio

- FM radio high frequency preservation and volume harmonization

- added 128x oversampling on record & FM radio

- removed SNR booster: didn't pass quality tests
[Captivate Android Development] nickm50:
http://xdaforums.com/showthread.php?t=806195
[Captivate Android Development] pizz0wn3d:
Haha derp. It's in the OP haha. Thanks, I found the thread for the original voodoo kernel too >.<

Herp derp Captivate XDA App
[Captivate Android Development] hype8912:
This kernel is screaming fast. I had an issue initially with having all the speed steps set and it was like eclair slow. I unchecked 1120, 1280, and 1360 thinking either one of the steps was incompatible or it was just too many steps to check and it worked. Everything is screaming fast now. Extremely shocked at how stable it is too.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] cumanzor:
Question,

does it makes sense that, the latest release is unstable even with the exact same settings from an older release (speed limit at 1152, uncheked further states, same UV settings) ??
[Captivate Android Development] LimaI896:
It could of been unstable before but you actually found out now.
[Captivate Android Development] cumanzor:
Nah I actually did a few tests with StabilityTest, that are failing now for some reason...
[Captivate Android Development] sjavvaji:
check ur cpu/battery temperature...i can do like 80 loops but when my phone passes that 43C mark...it downclocks intermittently causing failed stability tests but is still actually stable for any other use
[Captivate Android Development] Auridran:
I find stability test isn't a very good indicator of stability. I'd much rather run Neocore for half on hour.
[Captivate Android Development] nappent:
What differences are you guys seeing with this Kernel vs GB's latest? Battery life?

I'm still on GB's kernel with 17.55-17.78 linpack and a 1798-1820 Quadrant. For this being a 1.4ghz kernel it doesn't seem that fast. I'm not trying to starting anything I'm just honestly wondering. If any one has experiance with the two please let me know. Thanks!
[Captivate Android Development] iXNyNe:
So just to be clear. Setting limit clock to 1400 and then only enabling lets say 1200 and under in states (7 total) should let my phone run in 1200, 1120, and all the standard states right? Or should I also be setting limit clock down to 1200?

Quadrant scores seem kinda low for an overclocked kernel (1500 @ 1.2ghz)
[Captivate Android Development] Auridran:
19.41 is my best in Linpack at 1.4GHz. 1555/3324 is my best Smartbench result.

EDIT: Even though it's an awful benchmark, I installed Quadrant. 2112 is my highest.
[Captivate Android Development] pizz0wn3d:
Yeah that seems to be my average as well when I get ballsy enough to ramp it up to 1.4

Herp derp Captivate XDA App
[Captivate Android Development] XGX5309:
Another way to keep on top of Voodoo Sound's changelog is to look at the changelog in the Market for Voodoo Control App. :)
[Captivate Android Development] nuwayman:
Same here at 1.4. had almost a 61fps on neocore. But then froze running nenemark. Went down to 1360 and everything runs fine without changing any uv settings. I then just only uv the 1.4 setting with -50. Touched nothing else. Nenemark ran complete without any freezes. Still testing more.
[Captivate Android Development] MexicanAmerican:
Great kernel. Still haven't tested battery life, and running at 1.2 Ghz. First full real world test is tomorrow, when I head out to work.

I haven't tinkered with undervolting too much. Went to Shaolin's mini oc/uv tutorial, set all frequencies to -100mv and ran SetCPU stress test for 15 minutes, with no freezing. Then ran Neocore for the same amount of time, no freezing.

Really looking forward to seeing what kind of battery life I get out of this kernel.
[Captivate Android Development] Auridran:
I know I get insane battery life running stock undervolted. I'm going to test out my 1.4GHz overclock tomorrow and see if it's worth running 1.4GHz 24/7.
[Captivate Android Development] existz:
I think ive decided to update to K12S patch, adding in everything thats in Hardcores K12S, was just cherry picking pieces I wanted, but I dont think its going to work out, im going to do a few test and if its the same/better as #32 ill release it tomorrow, if its not, then ill just stay with k12p
[Captivate Android Development] pizz0wn3d:
I noticed that earlier today too when I updated the app, haha. I'm so detail oriented I often miss the obvious >.>

Cool beans. Looking forward to the results.

Herp derp Captivate XDA App
[Captivate Android Development] WickedNite:
And I'm still waiting for the version that improves the battery life even more. Or you already forgot it? :D

Sent from my Muscles using Brain Cells
[Captivate Android Development] existz:
Thats going to take some research to get that one done, hopefully i will have it finished within a few days, right now im just trying to get everything up to date
[Captivate Android Development] WickedNite:
No worries. I can wait. :)

Sent from my Muscles using Brain Cells
[Captivate Android Development] iNFRiNGE:
I'm lovin every thing about this seriously. I'm pimpin it out to people that don't even know what a ROM or Kernel is. :D
[Captivate Android Development] opcow:
Changing your mount options from safe to fast will improve quadrant scores. I think GB mounts with the equivalent of the fast option. Also, I'm running 1280 and I disabled all other speeds above 1000 which seemed to improve my linpack score a bit.
[Captivate Android Development] shaolin95:
61? Do you have a screenshot of that mate?
[Captivate Android Development] TheYar:
Yeah, it's best to have only one OC freq enabled. How "unsafe" are the fast mounts?
[Captivate Android Development] opcow:
According to supercurio "...this option is already used in Voodoo kernels for Galaxy S devices / has been chosen after extensive performance and reliability tests."

Link.
[Captivate Android Development] lrs421:
Not sure if its related but last night I switched to a faster mount and subsequently had issues getting my external SD card to read properly. I'm going the safer/recommended way.
[Captivate Android Development] LimaI896:
Got 17.08 on linpack and 55.7fps on neocore. Oc to 1280, been stable with my uv settings as -75,-75,-75,-100,-100,-100,-125,-125

Great battery life too :)
[Captivate Android Development] biochemgod:
I installed this kernel over the latest Speedmod and had some strange issues with speed. It was extremely slow and laggy at times, despite running at 1280 (my phone is happy up to 1500). I didn't have the chance to dig into it very much, but perhaps one of the speed steps is the culprit.

I'm back on Speedmod for now, but I would love the option to OC/UV.
[Captivate Android Development] opcow:
The safer/fast mount option only affects ext4 mounts.
[Captivate Android Development] lrs421:
Well then I have my answer. Unrelated. Thanks.
[Captivate Android Development] Auridran:
1500? Jeeze, that's pretty good. 1.4GHz is probably the highest I can hit, as I can't UV at all at 1.4GHz without instability.
[Captivate Android Development] RonH54:
I am running #26 1120/100 with UV settings of:Noop,50,50,75,75,100,125. I am think about trying #26 1120/500 or maybe #27 1280/500 and I was wondering will all my UV setting stay the same after a new Flash or do I need to to go in Before or after and re set things up?

Thanks
[Captivate Android Development] shaolin95:
So are you guys using the CFQ option? My phone does not seem to like that one.
[Captivate Android Development] Chargerdude70:
No luck

Has anyone had trouble flashing this kernel that has Phoenix as their rom? Running PHX 4.1 and I have had 2 unsuccessful attemps. Both have ended in freezes to the point I have had to go back to my previous kernel. The first attemp, I used the kernel flashing app then read that flashing with it may cause issuses. So I tried to flash the latest version of suckerpunch with CWM. First I disabled the lagfix in my current kernel(SM K12-s)then flashed. As soon as the phone booted up it went to panic screen. I rebooted it, then phone booted to home screen then froze. Tried to reflash SM K12-s and then phone went into boot loop...So I just wound up flashing whole system over. Anyone have any suggestions?
[Captivate Android Development] tietherope:
When i was on this kernel noop would run great, anytime I used CFQ I would get sleep/charge death. Maybe CFQ just needs a lower undervolt.
[Captivate Android Development] lrs421:
I am. I see no difference in performance.
[Captivate Android Development] sixstringsg:
I still got charge death with the latest kernel.
[Captivate Android Development] LimaI896:
Did you do the wifi temp fix? existz.is still working on it.
[Captivate Android Development] TRusselo:
running fine for me.

by panic screen do you mean blue letters that overlap eachother? cuz thats normal dont reboot. did you have any issues when you flashed with SGS? or you just read that there might be issues, so you decieded to make things worse?
[Captivate Android Development] LimaI896:
Saves battery life