yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] bballer182:
try wiping the voltage settings in CWR to get it stable again and the program you are thinking of is named "stability test"
[Captivate Android Development] grkmaster:
Thanks.. I guess I was stable for a certain amount of time before it just couldnt give no more. Im gonna re adjust some of the UV settings now
[Captivate Android Development] geokhentix:
Absolutely awesome kernel existz, you are kind of the man. I'm sitting pretty right now @ 1.6GHz stable! At least it was stable for 100 passes in StabilityTest. :o

OC/UV Settings[with CPU tweak ON, using SIO]:

1600 = -25

1400 = -25

1200 = -50

1000 = -75

800 = -75

600 = -100

400 = -125

200 = -125

100 = -150

I've yet to have any problems related to the OC and it's been about 24 hours. My battery seems to be standing up to it rather well too, and I'm really enjoying the blue recovery, it's the small things that matter yo.

EDIT: I knew I shouldn't have posted. 5 Minutes after making this response, my screen turned light and grainy and started to fade out. Nothing responded, the screen looked like a bunch of pastels. THATS A FIRST!
[Captivate Android Development] grkmaster:
LOL as soon as I had written my post before saying i was stable, it started screwing up alot .. The gods are pretty strong here when using the word Stable too soon lol
[Captivate Android Development] geokhentix:
Stable again @ 1.6GHz, CPU tweak disabled.

New voltages;

1600 = -25

1400 = -25

1120 = -50

1000 = -75

800 = -75

600 = -25 (if this is set any lower, bad things happen...)

200 = -100

100 = -125

Survived 56 passes of StabilityTest and 16 NeoCore loops. I am in love. 1.6 won't take with the CPU tweak, it's all fine and good until I open the market, then it dieses. :(

Seems like the 600mhz step UV is the key, as if i even make it -50, the phone dies immediately on Apply for Now.
[Captivate Android Development] indomikey:
Reporting

Strangeness, on Continuum rom with Onix, and I had a charge death without having any UV last night. OC to 1300, first 4 tweaks on except CPU one. This is the first time I have had that happen without any UV. The night before it was the same with UV at 25 from 1300 down to 600.

i'll be trying again tonight, no UV with Firefly ROM same OC. Flashed back to stock before flashing.

Edit: What I'm getting is not quite charge death. I don't wake up to a blank screen, I wake up to a bright kernel panic screen.
[Captivate Android Development] KonaZXIII:
I'm restoring as I type this- I appreciate you all. Thank you.
[Captivate Android Development] arcardinal:
@KonaZXIII

Here is a link to a post by hardcore, the guy that originally came up with the Speedmod Kernel

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

You might want to check the original Speedmod thread as well, as this kernel is based off of that. Check the OP in that thread and you can find more links to information on the features of the kernel. It doesn't hurt to do a little reading and research on your own.

@existz

Loving the kernel. Currently running #26, and was previously running #24. No sleep death on either, and I am aggresively uv'ing. I used to get the sleep death on Setiron's older kernel version, but have not experienced it quite a while. This was with and without UV or OC, and less aggressive settings than what I'm running on your kernel.
[Captivate Android Development] rootnik:
I sent a request to a mod to clean the past couple of pages up. Sorry existz, for being a part of the clutter.

Going to try to make my phone charge death under different conditions to see if I can help figure this out... I personally haven't had any problems with it so far.
[Captivate Android Development] ryude:
This kernel also has a "slim" chance to cause your home button to stop working. I've already posted 2 fixes for it though.
[Captivate Android Development] opcow:
Almost any fool can explore the menus in recovery and find the lagfix options. Once found almost any fool can see that some of them have the [R] label and if said fool clicks them he or she can see the changes reflected in the lower part of the screen. If still confused, just type out what you see on screen and ask what it means. I really see very little difference between the setup of this kernel and any other.

Finally something we can agree on.
[Captivate Android Development] jjtitus098:
I don't understand how the instructions for this kernel are vague. It's not that hard to figure out what to do. Doesn't take a genius... I think you need to learn some more about flashing before you start flashing different kernels.
[Captivate Android Development] existz:
I must have missed this, my bad, ill look into this as well, thanks for the fixes..:)
[Captivate Android Development] opcow:
Why did you clear your battery stats? That sounds like the cause of the problem not the kernel flash.
[Captivate Android Development] existz:
This might be related to your problem, but in the original speedmod kernel, it cuts charging off at around 97%, Hardcore says this is something Samsung implemented in 2.2.1 to save the life of the battery, as keeping the charger on when its a 100% could degrade it. Even though your rom might not be 2.2.1, the kernel is, so... there's a few ways around this, you can keep unplugging your charger and plugging it back it, after doing that a few times it will go to 100, or if you charge with the phone off, it will also fully charge. Some roms remove the 100% full notification, im not 100% sure, but if yours does then it might just cut off at 97% and that be it, as with others it will get to 97% then automatically jump to 100% full, then when you take it off the charger it goes back to 97% instantly
[Captivate Android Development] IStern:
Ah sad...everything was perfect with this kernel until I woke up this morning and had to pull the battery.
[Captivate Android Development] xbeamelite:
I tried this ROm out yesterday and was very impressed by the speed and wanted to test it out for a few days. After trying to UV a few times, the phone freezes as soon as I entered Voltage Control, resulting in battery pull. The phone then continues to freeze as soon as the media scanner is basically done. UV settings were set at the minimum -50, -50, -75, -75, -100, -100. Coming from Firebird Kernal. Had to revert back to firebird but would def like to try this kernal again maybe on the next release. I flashed via CWM. Running Phoenix 4.1. Any thoughts?

I also went into root exp and toggled the r/o r/w option i read in the OP to no avail. Thanks for any help.
[Captivate Android Development] cumanzor:
Not sure if it is related, when using the 100Hz kernel, Xan's Voltage Control apply doesn't detect the correct speed steps... anyone else noticed this?
[Captivate Android Development] rootnik:
Those settings may just not work for you. Try starting at 25 for each.
[Captivate Android Development] xbeamelite:
I did, I actually started out at -25, -25, -50, -75, -100, -100. Also it started to do it after the start up, before i could even go into VC to change the voltage. Once I entered VC the phone would be frozen in VC (with no UV done). dont know why, it did work for about 20 minutes and it was super fast. Will try a fresh flash next time to see if it helps.
[Captivate Android Development] Kizzmiazz:
Agreed, I love the kernel and will definitely use as my kernel of choice if you can fix the charging death. awesome work.

Sent from my SuperDuper!Captivate | PHOENIX RISING 3.5 KizzEdition | Firebird 2 v0.5 | VA Green v10 Theme | Member of Team Phoenix
[Captivate Android Development] rootnik:
I know I have been guilty of trying to set my 100mhz to high. Try going no higher than 75 to start out.

My phone won't under volt 1200mhz+ at all (no matter what kernel I use), not even 25. Try setting your higher mhz to 0 to see if it makes it stable.

I just takes allot of trouble shooting to find the right settings for your phone. Good luck!

edit: Didn't notice it if you posted it previously, but are you using noop scheduler?
[Captivate Android Development] iNFRiNGE:
+100 if I could lol But for the record +1

It's not that hard if you actually take the time to do the procedure rather than ***** about it.

Here's the path to use so you have no further issues even though there isn't any..:confused:

Just follow the path I lay out for you.

Reboot into Recovery>>>advanced SpeedMod ULK features>>>TWEAK options>>>EVERYTHING with the (R) next to it is "RECOMMENDED" everything with the (O) next to it is OPTIONAL and what says (NOT RECOMMENDED) is uh...actually NOT RECOMMENDED believe it or not.:eek: after you have enabled what you want back out and reboot or go into the LAGFIX options and set up your EXT4 in there back out and reboot.

Pretty simple don't ya think? ;)
[Captivate Android Development] c0ldburn3r:
Are you using at least Voltage Control 3.0a? The final release for 3.0 is out now too. As far as I know the old versions will not work with this kernel.
[Captivate Android Development] ProBoner:
My phone and MANY MANY others can't go over 1200mhz fully stable. If anything I would probably need +25 or +50 to make 1280+ work (can't that be done?).

I recommend you try the 1.12ghz kernel and start with either 0 or -25 at full speed then go -50 -75 -75 -100 -100

I think that's what I'm using but it might be -25 -50 -50 -100 -100

I can't remember and I'm running my x10 ATM so I can't check until later.
[Captivate Android Development] xbeamelite:
I am using the 1120 kernel. sorry if I didnt mention that before. I tried to change it to noop afterwards but it freezes before I could even change anything. ill try again later when I get a chance.
[Captivate Android Development] grkmaster:
I decided to go back to 1200 mhz to keep me stable for a bit and I just adjusted 600mhz from from -150(was stable with this) to -75(to test it out) and my quadrant score when up like 60 points..

Then again I UV that freq to -50 and it went up but just very little
[Captivate Android Development] existz:
Try to reflash with CWM, no kernel flasher app, then clear cache and dalvik cache (first boot takes awhile)...and try it at stock voltages/frequencies ... that way you can rule everything out.. cause if it doesn't do it at stock voltages/frequencies, then something else is causing it.
[Captivate Android Development] AReynante:
Running very smooth on 1400 now :) first time with any kernel that I can go above 1200. Amazing work :)
[Captivate Android Development] grkmaster:
No rushing or anything, but any timetable for 2.0.2? sorry for asking
[Captivate Android Development] existz:
Actually finishing up a few things, should have it up soon.. its not a major release, just added boot image (still not set 100% sure on it, so might change later on)..and added audio dock support
[Captivate Android Development] jon.groves:
What are you OC/UV settings?
[Captivate Android Development] grkmaster:
Very nice. to me this is a big update lol cause of the audio dock support :)
[Captivate Android Development] existz:
Since I dont have a dock I cant confirm it works 100%, but it should lol..so let me know if does or if it doesnt...compiling it now, should have it up in 15-20min
[Captivate Android Development] existz:
*UPDATE*

Onix v2.0.2

-Add new boot image

-Add audio car/home dock support

--Audio uses dock when available (use this app)

--Call audio uses dock when available
[Captivate Android Development] jon.groves:
Just flashed it. Love the boot image! Will let you know what I think
[Captivate Android Development] gorgy76:
I just flashed v2.0.1 and set the max clock to 1500mhz. just want to ask because with heavy testing it only runs at 1120mhz as seen on my cpu v2 widget and seems I'm getting low bechmarks score although it's not that entirely reliable. Is there some process/steps I missed? I clear dalvik cache before and followed the steps seen in OP. thnx
[Captivate Android Development] halfsoul:
Did you enable states and reboot?
[Captivate Android Development] grkmaster:
Kk.. I will be testing it in about 20 minutes when I get out of works. Thanks
[Captivate Android Development] existz:
You have to also enable which states you want to use, then set max clock, also save your settings twice because sometimes VC doesnt stick
[Captivate Android Development] aalh:
bootscreen idea

Tux about to eat a donut ...the first letter in Onix of course
[Captivate Android Development] goodolsen:
Just flashed 2.0.2, like the boot screen as well, great work.
[Captivate Android Development] gorgy76:
what do you mean by states? is it in the votage control app? in the vc settings I set clock limit to 1500 and I'm also undervolting here are my settings:

Ican see

1600

1500-0

1400-0

1300-0

1200-0

1120-0

1000-50

900-50

800-75

600-100

400-100

200-100

100-100

by the way I'm using my previous vc app anyway I'll just try to install the new vc app posted in the OP.
[Captivate Android Development] existz:
When you open VC theres a tab at the bottom that says "states" select it and a menu will slide up, you have to enable which states you want active before they work...for example if you just set max clock to 1500, the 1500 step is not active until you enable it in the states menu
[Captivate Android Development] gorgy76:
ok I see... I didn't see states in my vc app because its the old one I only see scheduler. thnx. will install the vc app from op now. is it cmw flashable or just install it as normal apk's?
[Captivate Android Development] goodolsen:
Make sure you are on the latest VC, earlier versions didn't have the states tab.
[Captivate Android Development] existz:
Remove the old one first then reboot and then install the new one like any other apk..there's something that causes the new one to not install if don't reboot or clear all its data out before installing ...
[Captivate Android Development] ridethelight:
1000hz version with cputhreshold on gave me the most terrible battery life, even with -100 everything UV. Going back to 100 and turning threshold off, did notice the phone was a bit snappier setup like that though.
[Captivate Android Development] gorgy76:
ok thnx thats what I thought also I'm running it now gonna just test my sweet spot.
[Captivate Android Development] grkmaster:
Problem - I flashed 2.0.2 with CWM and now my phone wont go past the ATT screen. Going to try to get into download mode and see if I can flash the kernel through there

EDIT: Got it working through Odin and going to flash the 1000... i had originally dled the wrong one as well.. stupid me
[Captivate Android Development] xreflection:
Just flashed, love the new boot image. Everything seems to be booted up fine and dandy. Will do the usual checks of camera etc...
[Captivate Android Development] djinferno806:
Im having problems going from K13D to this kernel. Everything runs smooth and fine until i put the phone to sleep and then press power to awaken it again. The phone runs choppy for the first 3-5 seconds then it goes smooth again. It wont get choppy until I turn the screen off then on again.

I dont UV or OC at all and i cleared the cache and dalvikcache after flashing this kernel.

any ideas? thanks.
[Captivate Android Development] existz:
Its probably because I use more battery conservative settings, such as the cpu threshold, it effects how the cpu scales, so for example when its asleep and you wake it, (and if there's alot of apps in the background running) the cpu doesn't scale up as quickly as some other kernels .. try enabling the cpu performance threshold tweak in recovery .. it sets more performance settings for the threshold .. meaning the cpu will scale higher quicker, giving smoother results .. read the 2nd post and it will explain it a little more .. but try that and see if it helps ..most likely its because either there's alot of stuff running in the background or theres 1 app hogging the cpu, and the default threshold is not as quick as you need it to be..I usually do a level 2 clear after boot to end alot of processes I don't use ..but don't do it very often as it can actually use more battery, cause once you end those processes, the ones being used start right back up ..but try that and let me know if it helps ..

But remember, the default setting will give better battery life ..
[Captivate Android Development] H3llstorm:
That's why I use Autostarts. :cool:
[Captivate Android Development] grkmaster:
existz, the car dock works... thanks again!
[Captivate Android Development] existz:
Awesome..appreciate you checking for me ..kinda hard to confirm without a dock :P
[Captivate Android Development] H3llstorm:
What does "Fix Permissions" do in CWM > Advanced Features?

Is there some way to incorporate the improved GPS performance from the Skullcap-Voodoo #7 kernel (based on the GT-i9010 JL1 Armani source) without making my phone write-protected so that I can't transfer files to it from my PC?

Edit: I probably should have posted this in the SuckerPunch-Voodoo #11 thread. :confused:
[Captivate Android Development] steadilyshine:
I have cognition 4.2.2 with the new onyx 2.0.2 1000hz kernal with jq1 modem...I reflashed a few times ...but my CPU stays maxed out and stuck at whatever clock limit I set it at...what am I doin wrong??
[Captivate Android Development] existz:
Im using the same setup.. if your using setcpu, DO NOT USE IT, make sure you are using the conservative governor (if you changed it) .. if your using VC then make sure the correct states are enabled ...also how are seeing if its maxed out?
[Captivate Android Development] steadilyshine:
I'm using VC never used (set CPU).......but perfect system monitor ...and temp CPU v2....I was using suckerpunch#59...then wanted to switch up....now it just maxed out and drawing my battery....
[Captivate Android Development] existz:
Not sure...make sure you don't have a run-away app/process.. sounds like something is running in the background and wont quit..either that or some old voltage settings from 59 are sticking, since the frequencies and the number of frequencies changed it could be setting the wrong enabled states..

im using the exact same rom/modem and have never had that happen...

But try the basic troubleshooting..

Reflash with cwm (no kernel flasher app)

Clear cache/dalvik cache

Clear voltage settings in cwm
[Captivate Android Development] abee_13:
Had the best battery life 16 hours with 3 hours and 56 minutes on screen time. Going to try to get the same results tommorow and take a screenshot.

Thanks existz for this great kernel!!
[Captivate Android Development] Beny The Kid:
Existz, you are a star my friend. 2.0.2 with Firefly 2.7 running like a dream. Really like the boot screen too.
[Captivate Android Development] bballer182:
Hey Existz, when using antutu benchmark I have noticed that the database IO scores are pretty low compared to some other phone models. We, as in, captivates are scoring a consistant 30 maybe 40 when everyone else is in the hundreds. Is this problem anything that can be fixed within a kernel or is it just the way our phones are?

Sent from my OC'd Samsung Captivate
[Captivate Android Development] Johnny Paranoid:
Well, I got Onix running again on my phone. Stability Test ran 50 CPU core runs with no problems. Looped Neocore 10 times, no problem. Rebooted 5 times in a row, no problems. Not sure what happened last time. One thing I've found is that my phone does not like to be overclocked past 1.2Ghz. But that's fine. I don't really need to anyhow. Interestingly, though, OC to 1.2Ghz on Onix gives me ~100 points less on Quadrant vs. SuckerPunch-Voodoo. And that's with all the tweaks enabled. Is Voodoo natively faster? Doesn't really matter much to me. I could care less about benchmarks. As long as I get good battery life, my phone is stable and it runs all my apps smoothly I'm good.
[Captivate Android Development] existz:
Enable the faster mount option in recovery..under lagfix, should boost scores a little...its the same option voodoo uses
[Captivate Android Development] fractaline:
@johnny, are you getting better battery life with onix oc/uv 1.2 than with k13? I am. But I started using juice defender somewhere in there and I'm not sure.

Also, do you find that you can uv more (less) with the cpu threshold tweak?

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] Johnny Paranoid:
Hard to say on battery life just yet. I'll know more after a day or two. I can't UV more or less with Onix vs. any other kernel. The best I can do is -75 on 100-600 and -100 on everything above that.

@existz: Thanks, I'll try that.
[Captivate Android Development] Johnny Paranoid:
Yeah, that worked. Immediate 200 point increase on Quadrant (1765). I was wondering, is there a way to turn on the phone into recovery? With some other kernels (all Voodoo I think) you could do so by holding up & down volume and power at the same time and letting go of the power button when the AT&T boot screen came on.
[Captivate Android Development] AReynante:
Can you not do that with Onix? It has worked with every other kernel I've used. Even stock
[Captivate Android Development] pizz0wn3d:
You can do it. He may need to flash the 3-button fix.

Herp derp Captivate XDA app.
[Captivate Android Development] Johnny Paranoid:
No, doesn't seem to work. I was having trouble getting into recovery. I think that mount option is unstable. When I chose "Recovery" from the power menu, the white screen hangs and I just get a regular reboot. Same if I chose "Power off". It would boot up fine, though. So what I did was go into Voltage Control and delete the boot schedule file and reset everything to stock. After that everything was fine. I think I should still clear Dalvik and cache partition, just to make sure, huh?
[Captivate Android Development] Johnny Paranoid:
Oh, it's something that has to be cooked into the kernel or ROM? I just did a quick search but couldn't find a CWM flashable .zip file. Would you be so kind as to direct me to one?
[Captivate Android Development] AReynante:
I can get into recovery with the 3 button method, the extended power menu, and AIO. No issues at all here.
[Captivate Android Development] BaDaB!ng505:
Gonna try this on my rom to see if it works
[Captivate Android Development] IDoMy0wnRacing:
Here is the cwm, "3 buttom fix" that i use.
[Captivate Android Development] IDoMy0wnRacing:
Sorry, i forgot to quote...

http://xdaforums.com/showpost.php?p=12397235&postcount=3231

one post up.
[Captivate Android Development] rajendra82:
A happy eXistZ KB1 beta 7 convert to Onix 2.0.2 100 Hz for now. Just had to try it out because of all this commotion about new recovery, and had to also see if I could get any i9000 modem to behave with my build 1007 (tljl3 is very promising so far). Have run a few stability tests and see a need to back off UV a bit I think. The top speed of 1400 MHz is stable all the way past 50 stability test runs, and Neocore has looped without freezing for over 20 minutes, but seen a couple of random freezes requiring battery pull, which seem to indicate what works on KB1 beta #7 might not necessarily work on Onix 2.0.2 at the low end frequencies.
[Captivate Android Development] steadilyshine:
Anyone else having this problem....Im running cog 4.2.2...with the jq1 modem..and the onyx 2.0.2 1000 hz kernal...now I've reflashed several times ...cleared the voltage settings davlik cache ..and whatnot...then reflashed the kernal....and my CPU is stuck at Max...just draining my batt....I am no noob....but for the life of me ...idk wtf...any suggestions....
[Captivate Android Development] steadilyshine:
I killed all processes and ...just about everything....the suckerpunch #59 ran great...I wana use this kernal......
[Captivate Android Development] LNJ:
Do you have some kind of system monitor or task manager installed?
[Captivate Android Development] steadilyshine:
I do perfect system monitor and temp CPU v2....both telling me 97-99% CPU...and constant 1000mhz...even after I kill all processes....!!!
[Captivate Android Development] steadilyshine:
No fluctuations ..
[Captivate Android Development] steadilyshine:
Ill try from scratch again tomorrow...but any suggestions would be appreciated ...