yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Correct, Speedmod has a 250 and a 500 version... My kernel uses kernel hz at 100hz which is the same as user hz, so its said to cut out the kernel--user hz conversion, providing better battery life without hurting performance, i havent tested it that much to give a 100% answer, but HOWEVER, it does seem to be as smooth, if not smoother... i am testing different combos of kernel hz and user hz, if I find a better combo than what its using I will change it...

As for battery, there is no difference between 250 and 500...as for 100 vs 250/500, like I said i havent tested it that much to give a confident answer just yet..still testing

In Glitterballs thread it shows the same settings (its where I got it from) he may be better to ask than me since hes been using this combo longer than me

EDIT

Also, if you guys want to score higher in Quadrant, go into CWM under Speedmod Features / Lagfix Options / Ext4 mount options ...and change to "Use Faster mount opts"...however its recommended to use SAFER, with the Faster setting it is more likely to have file corruption
[Captivate Android Development] ccdoggy:
I just flashed it and its looking great for the 10min i have had to use it.

Though when i bring up the voltage control app (the one in the 3rd post) I get a limited number of speeds to control the voltage.

Here is my list:

1120

1000

800

400 <- was not there the first time i started the app

Make any sense at all?
[Captivate Android Development] doreyu:
That happened to me, but exiting the app and running it again seemed to fix it, I reduced my UV a bit to see if that is why that happened.
[Captivate Android Development] dmutpp:
Gonna give this a try!
[Captivate Android Development] ccdoggy:
Gave it some time and it cleared up and now shows all of them. No problems at all yet, recharging overnight and tomorrow the battery test.
[Captivate Android Development] ryude:
Does using 1120 lower your GPU clock like setiron's did with anything other than 1200/1400/etc.
[Captivate Android Development] airbillion:
Awesome rom, but could you include a 1200 oc version please?
[Captivate Android Development] existz:
**UPDATE**

1280mhz version is posted!!

NOTE:

This kernel might score lower than other OCed kernels, (1st you really shouldnt go by benchmarks anyways) but this is because this kernel is geared towards the best possible battery life, speed comes 2nd.
[Captivate Android Development] Majortom420:
This is excellent, and a great replacement for speed mod. Just hoping you will be up to date with hard cores frequent patch updates and test versions.
[Captivate Android Development] ryude:
Well that sucks, can you leave the 1120 version up? My phone has never been able to run 1280 OC kernels, only 1200 and under.
[Captivate Android Development] existz:
Yea im def leaving the 1120mhz, and to be honest its the version I run, as I wanted something as close to stock as possible but with oc/uv ... I just made the 1280 due to request ..so no worries about that
[Captivate Android Development] ryude:
Thank you! I will report with my impressions once it's flashed.
[Captivate Android Development] rootnik:
I'm pretty excited just to add under volting to what hardcore has already done to save battery life. Thank you existz.
[Captivate Android Development] slaman:
Looking forward to trying this out!!!

A suggestion: perhaps you can endeavour to update with each of hardcore's "stable" releases to avoid having to do too many updates?

Really appreciate the effort - thanks!
[Captivate Android Development] existz:
Yea ill keep up to date on everything new, not just hardcores, also I will add in a few of my own tweaks here and there... As we all know Hardcore is super human and puts out alot of updates, which is a great thing, I will do my best to keep up.. As I stated earlier, I dont want this kernel becoming a copy cat of Hardcores, Im not out to copy all of his work and set back calling it mine with OC/UV, if he makes something open sourced then yea, ill def add it if its something we can benefit from.. As with any other dev, if something is put out for us, and we can make use from it, ill add it...But also if theres something that I have a different opinion on than the original dev, ill add my tweaks to it... Im pretty new to the dev world, I really dont want my first project being named a rip off.. Im slowly learning, but making progress, only about a week and half ago I didnt know the first thing about making a kernel, if it wasnt for these great devs, I wouldnt have learned ****..so I really dont want to step on any toes

But to give you a short answer, yes, I will do everything I can to make this a "similar" alternative to Hardcores, not exact, but similar
[Captivate Android Development] ryude:
So far so good, stable @ 125/125/100/100/75/50 on the 1120 kernel. Have not enabled any tweaks yet, so I'm going to do that now.

Edit: What benefit, if any, does converting the /system/ to ext4 have? Surely it wouldn't have it's own setting in the recovery menu if it wasn't special in some way.
[Captivate Android Development] existz:
If you have tons of apps installed, converting system to ext4 helps out alot over RFS with lag, also for people like me, who wants to stear clear of RFS all together (Samsung must of had a reason to ditch it and go with ext4 on the Nexus S) I prefer it because I come from Linux and ext4 is the chosen file system, just something im use to..
[Captivate Android Development] ryude:
Ok, thanks!

Also I made a ROM designed for battery life and speed, it's 86MB and scores quadrant of around 1300 with no lagfix or any OC. I've been using it for about a week now and it's given me outstanding battery life. If anyone wants to try it just let me know and I'll post it. The ROM is based on Doc's XWJS3, has JK4 modem, and uses Suckerpunch 1.12 kernel.
[Captivate Android Development] Nickel Dime Bay:
If im on GB's kernel do i have to disable voodoo lagfix before flashing this with neldars app? or can i just flash it over it?
[Captivate Android Development] sfernandez:
No luck here either, I added to the Phonienix 4.1 rom base and tried to flash from scratch with #32,#30,#26(you get the picture)as default kernel but all I got it to was the splashscreen then FC and stayed that way.It was able to Flash with SM12-S as default kernel fine then I just flashed #32 over, so not sure if something in the script is not allowing it?
[Captivate Android Development] existz:
There's something else wrong with Phoenix, try asking adamholden what he did or didn't do, I actually just sent him #30 or #31, can't remember which one, yesterday morning and he hadn't had any issues
[Captivate Android Development] ccdoggy:
I had a problem like this yesterday, I tried to flash phoenix 4.1, green mod, and Sucker kernel at the same time and it hated me. FC on phoenix loading screen.

To get it to work I went back to stock odin, then flash phoenix, then let it boot all the way and use it a little bit. then flash Sucker, let it boot and use it a little bit. then enable lag-fixes and what not in CWM. let it boot and use a little bit, then i flashed the green theme mod and now its working great.

seems a little picky to get working totally right if you rush it.
[Captivate Android Development] Chargerdude70:
He mentioned in his thread about working with you. I'm wondering if he is going to use your kernel in his latest PHX 4.5 or in his new Supernova?
[Captivate Android Development] existz:
Well, whats the odds..just heard from adam again, seems after about a hour of use he started having issues, hopefully me and adam can work to figure this out
[Captivate Android Development] ryude:
Anyone else having problems getting phone to boot when flashing #32?
[Captivate Android Development] crazililazn:
Nope. Flashed on Serendipity 4.3 and it worked fine.

Anyone having problems mounting their USB storage in Recovery with this kernel? Whenever I try to mount it, nothing happens :/ Mounting works fine when I'm in the OS tho.
[Captivate Android Development] cumanzor:
Well, I tried over and over again but I just cannot get #32 to work stable. Even with everything on stock, 1GHz, no UV at all, it cannot handle Stability Test for some reason. It's weird becasue #27 works perfectly fine, but it doesn't have Voodoo Sound 4.
[Captivate Android Development] silverslotcar:
Well how is it in real world performance?? Who cares about the stability test.
[Captivate Android Development] RonH54:
I am running #26 1120/100 with UV settings of:Noop,50,50,75,75,100,125 on Darky 9.1. Last night I had my 1st "semi" problem it may not even be the Kernel but I wanted to ask here to get opinions. I have been running this Kernel for 3-4 days and have Rebooted several times for different reasons but last night I decided to completely Power the phone OFF. When I restarted phone I got though Splash Screens and to my Home Dock(I am using LauncherPro Plus) and things started to load but then the Phone Froze for a few seconds and then Rebooted itself. It rebooted back completely and Phone completely loaded this time and is running fine. What could be possible causes of this Reboot thing?

Thanks
[Captivate Android Development] RonH54:
I just flashed 1280/500 over my Previous 1120/100. The Flash went smooth but when I try to open Voltage App I get "process com.darekxan.voltage control has stopped" and I have to Force Close. I went to Settings and Applications and Cleared data and it still occurred. I then uninstalled and re installed and it still happening. What should I try next so I can access Voltage app?

Thanks.
[Captivate Android Development] x3nhydr4lutr1sx:
you need to go to /system/etc/init.d and delete the s99_voltage file.
[Captivate Android Development] lrs421:
What he said^^
[Captivate Android Development] LimaI896:
Lol that stability test is full of ****.

Stress test via setCPU, Neocore, Quadrant scores, and Linpack are all good ways to test.

But of course real time every day use is your best test you can do. I passed many tests but still have stability issues clearly as Id freeze up at times. Now

I'm stable.
[Captivate Android Development] sjavvaji:
noop helps in getting higher overclocks but since this is so optimized for cfq...i use cfq...luckily...my phone can still handle 1.4ghz on cfq without charge death or instability
[Captivate Android Development] RonH54:
That file not Present only these:

S01sysctl

S70zipalign

S99complete

S-volt_scheduler
[Captivate Android Development] lrs421:
Try reflashing the kernel. That worked for me.
[Captivate Android Development] existz:
Delete s_volt_scheduler
[Captivate Android Development] IStern:
Running phoenix 4.0.3 + build 32 1.2ghz/100hz. After tinkering with the UV settings to fix my charge death problems, my phone has never run better! UI is super responsive and 3D games are smooth as silk.
[Captivate Android Development] sixstringsg:
What UV are you using?
[Captivate Android Development] RonH54:
That got it
[Captivate Android Development] IStern:
1200mhz: -50

1000mhz: -75

800mhz: -75

400mhz: -75

200mhz: -50

100mhz: -50

These are 100% safe for my phone, I might increase the UV values for the mid-range speeds and see what happens.
[Captivate Android Development] MexicanAmerican:
Update: My work day is coming to an end, and I've been unplugged for approximately ten hours.

I've been on EDGE most of the day, only enabling HSUPA just to check download/upload speed while at the office (not great, but I get horrible 3G service out here).

While on 3G, I ran about five Internet Speed Tests using Speedtest.net app, and checked my GPS reception a couple of times in different parts of the building (again, not great, but I'm indoors), and surfed the interweb net for about twenty minutes during the day.

Ran LinPack about five times (just love seeing that ~16.5 and above MFLOP score), sent about twenty text messages, voice call for about ten minutes....

And listened to WinAmp beta for nine hours of the ten. The other hour was spent watching Futurama during my lunch break....all on my Captivate.

I can't show screen shots as they wouldn't be accurate. My phone froze once, but that's because I haven't tweaked my voltage settings yet (have them set at -100 across the board), but my display has been on approximately 2 hours.

I don't do social media, nor background syncing, and I don't use widgets. Really bare bones.

I'm at 40% battery left.

This is my first all out test of Captivate's battery life, as I usually stick to my iPhone (now iPod touch) 3GS for music and video.

So, with the usage described, how's my battery life? Average? Good? Great? Pure f'n awesomeness?
[Captivate Android Development] LimaI896:
I would say great as I'm a heavy user and barely get 7-8 hours :)
[Captivate Android Development] iNFRiNGE:
lol no app on the market or the planet for that matter can match real time use, they are a decent OK but for a real test "Use It" that's it. I failed bench tests and drove myself nuts trying to pass it then I said fook this and just starting using my phone and ran like a hot knife through butter ever since. Try not to get head strung on "numbers" get sprung on how it actually performs for you.

+1 never even tried noop and never had COD or other problems that others have but are mainly due to not reading or following the directions in the first place.

It's that highlighted one I know you already found but in case anyone else reads this. ;)

Noooooooo! find that file and delete it.

Yeeees just like he says. Again you already know this but for GP.
[Captivate Android Development] lrs421:
Voodoo sound 5 is out, geesh. That dude doesn't mess around.
[Captivate Android Development] ThisWasATriumph:
Where are you seeing that?
[Captivate Android Development] lrs421:
In the market it asked me to download v5.5

Seems like a small update.
[Captivate Android Development] lrs421:
Actually I'm not sure if it requires a new kernel driver or not.
[Captivate Android Development] joeshmoe08:
No voodoo sound v5 just yet:)

http://xdaforums.com/showthread.php?t=806195

or

https://github.com/project-voodoo/sound_kernel_patches
[Captivate Android Development] Mortify1:
So if the kernel is based on i9000 and you need a i9000 modem.. Can't I flash this if I actually have an i9000?
[Captivate Android Development] existz:
No, even though its based off i9000, its made to work on the captivate, if you flash it on an i9000 your screen rotation and everything will be messed up

It uses xcaliburinhands reoriented code so us captivate users can use i9000 roms and modems. But its not that hard to make it for the i9000, I don't have the time to maintain 2 kernels, but once I get all the bugs out I might
[Captivate Android Development] existz:
Delete double post
[Captivate Android Development] psufan5:
Having major performance issues with 32... trying to narrow it down.
[Captivate Android Development] lrs421:
What's happening?
[Captivate Android Development] psufan5:
Mostly notable in quadrant - earlier versions would get far far far higher frame rates. Currently im seeing a lot of pausing, slow down, and much lower frames. Tried rebooting, erasing dalvik, permissions etc.. still doing it. Going to reflash after I disable the lagfix etc.
[Captivate Android Development] lrs421:
Hmmm. That's weird, 32 has been great for me. Did you try enabling faster mounts in lagfix? That helps w/quad
[Captivate Android Development] psufan5:
Yikes... linpack got an 11... quadrant 1100... Really really low. Not sure why.

Glitterballs got me 18 on linpack, and 1890 on quadrant. Not sure whats going on here.
[Captivate Android Development] LimaI896:
Really that is really low, at 1.2Ghz I'm averaging 17+ linpack and 1800 quadrant.
[Captivate Android Development] psufan5:
Maybe it doesnt like kernel flasher... ill try clockwork.
[Captivate Android Development] LimaI896:
I always and will only use clockwork, never have an issue. Plus it is so easy.
[Captivate Android Development] silverslotcar:
Clockwork is always the safer bet. Sometimes Neldar's app wouldn't work for me. And one time I used it to try and flash the Paragon kernel zImage and it was a complete fail. On the other, there are times it has worked like a charm. Still a great app though nonetheless.
[Captivate Android Development] psufan5:
The helix and the orange one are giving me issues.. if that helps narrow the issue down. I normally get around 22-23 on the orange, right now around 12. Helix normally 50ish, now around 30. Something is def wrong.
[Captivate Android Development] existz:
I dont think its the kernel, if it was everyone would be having issues, sounds like something is running in the background taking up cpu, try killing all processes
[Captivate Android Development] opcow:
Did you enable states above 1000 in voltage control (preferably just one).
[Captivate Android Development] doreyu:
I just wanted to point out and ask about SpeedMod and this kernel.

hardcore has listed that BFQ is the default scheduler on SpeedMod, whereas this one is CFQ, and I remember reading to use the one that hardcore optimized, which would be BFQ.
[Captivate Android Development] Auridran:
Even if he didn't, those scores are far worse than stock. ~14 is 1000MHz in Linpack.

doreyu, I personally find noop to be the best. It has given me better battery life than CFQ with no degradation of performance.
[Captivate Android Development] psufan5:
Im actually just going to reflash the ROM and then install this kernel again.... **** I do it nearly every day so no biggie lol...
[Captivate Android Development] existz:
No, hardcore uses CFQ by default, he switched awhile back but never changed it in his OP, he got way smoother results with cfq over bfq, you can flash his and see cfq is default.
[Captivate Android Development] sjavvaji:
i loose some smothness w/ noop even at 1.4ghz...i prefer cfq because it feels screaming fast like speedmod and then some
[Captivate Android Development] Auridran:
Interesting. I haven't noticed any degradation at all, whether it be in feel, or benchmark performance.
[Captivate Android Development] airbillion:
Same issue here with the same kernel. I wonder what the issue is?
[Captivate Android Development] pizz0wn3d:
I'm getting ~14 MFLOPS at 1280 (conservative scaling). Should I change the scaling options or something under the advanced tab? Because I'm getting around 17 when it's on performance. I have only 1280 enabled for the frequency states in voltage control.

Herp derp Captivate XDA App
[Captivate Android Development] existz:
Doesn't sound like 1280 is active, 14 is the score for stock, somethings not sticking ...even if you was getting "bad" scores, you would be getting more than that
[Captivate Android Development] cumanzor:
I get around 18 with 1400 and CFQ. Does that sound normal?
[Captivate Android Development] psufan5:
just reflashed my ROM and now flashed the kernel... going to test it again on a fresh install.
[Captivate Android Development] doreyu:
ahhh, got it!
[Captivate Android Development] pizz0wn3d:
That's what I was thinking. I disabled the 1400 and put setcpu at 1280 max.

Here's a couple of screenies, maybe I'm changing the wrong settings.

Edit: Advanced tab

Could it have something to do with the thresholds or increments? It does go up to 1280, but it looks like it's just not scaling all of the way up during the benchmarks.

Actually, it could be the sampling rate. Should I lower it?

Herp derp Captivate XDA App
[Captivate Android Development] Auridran:
And I quoth from the OP:

"DO NOT USE SETCPU"
[Captivate Android Development] pizz0wn3d:
Derp. I've read the OP 2-3 times, yet Somehow I missed that, it's probably from checking so many different topics throughout the day. Just being curious, is it because the apps conflict? I'm going to miss the performance scaling option :(

Edit: Uninstalled setcpu and rebooted. Linpack results went up to ~17. So I guess that's problem solved. Thanks for allowing me to waste your time.

Herp derp Captivate XDA App
[Captivate Android Development] biochemgod:
OK, given some of the comments here regarding the different speeds, I decided to give this another shot. Coming from Speedmod K12S, all partitions ext4.

I set the Voltage Control settings to the following:

In the states menu, I selected only 100, 200, 400, 800, 1120 and 1400.

My UV settings are -100, -100, -75, -75, -25, -25.

Scheduler is CFQ.

Now it flies!! Perfectly stable at max 1400Mhz. Quadrant of 1700-ish.

Based on my previous experience, it is possible that the 1200/1280 settings have an issue.
[Captivate Android Development] psufan5:
Whatever it was... fresh rom fixed it.
[Captivate Android Development] psufan5:
Enabled 1400.. i just got a 1942 on Quadrant LOL... almost a 19 on linpack.

SICK

Second run: 2095 Quadrant!!!! HOLY CRAP
[Captivate Android Development] psufan5:
2095! screenshot incoming lol! crazy scores!
[Captivate Android Development] laz0r:
I am sad... my phone almost instantly freezes on 1360 or 1400 with no UV... curse my cpu!
[Captivate Android Development] iNFRiNGE:
I've become accustomed to trying not to use an app to do anything that has to be done that affects the main system I started this habit on pc and just follow suit, not that apps are bad but it just makes more sense to do it myself then have a program do it for me. Believe me I'm lazy as they come but not that lazy. After I factored how much time I spent fixing issues from using apps compared to time they saved me to just carry out the action it was a no brainer.

Not to mention you have to back in manually anyway and do all your tweaks and lagfixes don't you?

Don't get me wrong it is a great tool I'm just making a general statement about that sort of thing.

+1 see above

I missed that too one time, it's too bad there's not a section or a box of important things to look out for in the changes. The change log obviously doesn't do justice. I try and hunt through everyone's OP for changes but simne things never change. foir instance this one still says This is my first attempt at a rom yada yada yada and there been countless updates first time I came in here I thought I was getting the first beta edition to try out. Anyway it's something to deal with. another thing is this newest release has all the options rolled into one which Is great but that changes everything is you are used to just dl a certain 500 version. No biggie I accept it and move on. ;)

Partially answered above congrats.

Whoo Hoo! :D
[Captivate Android Development] pizz0wn3d:
Haha yeh. it's just one of those moments where you /facepalm and fix your mistake.

I actually remember reading it before, but I thought I had read it on a thread for a different kernel because I've kinda skipped over that section after I read it the first few times.

Herp derp Captivate XDA App
[Captivate Android Development] existz:
Finally have hpcall fixed, will upload an update tomorrow. Also working on a new base, using laststufo's super optimized sources. Frequencys up to 1600mhz, with extra 600/900 steps...also includes his VSF display, all I have to say is wow...once you configure it, it is awesome. My version is still in very early testing, im not sure if I will replace this build with it or release a whole new kernel, either way I will continue development on this kernel in the mean time till I decide...but anyways, look for an update tomorrow some time with fully working hpcall, actually works this time :P
[Captivate Android Development] airbillion:
Sounds great. Just checked out the kernel on the i9000 forums and it looks awsome. I can't wait!
[Captivate Android Development] pizz0wn3d:
Woop woop. 1600 is effin nuts. Can't wait to burn out my CPU. Or was that 1600KHz?

:P

Herp derp Captivate XDA App
[Captivate Android Development] Auridran:
I'm not sure I understand the whole VSF thing. It seems like if you're actually using the phone it wouldn't clock down to 25Hz, and if you're not using the phone, the screen would be off and using no power anyway.
[Captivate Android Development] psufan5:
Cant do 1400 stable, but 1360 is perfect. Loving this kernel!