yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Mevos:
I'm using SuperPower right now and I found out I had to disable "Auto CPU speed" because it was making my phone unstable when UVed. When I had that checked, absolutely no UV was possible.

Anyone else had that issue?
[Captivate Android Development] bclark:
Yeah BC it uses odemand and drops your CPU speed way too low. I believe chainfire says in the op that galaxy S's shouldn't use it. If you switch to the non oc version you can use it ( I used to use it with xcalibur's kernel). I really don't use any of the root features just everything else and I've been using it since before it was on the market
[Captivate Android Development] nybmx:
Yes this happened to me yesterday. I was driving to school and listening to a podcast (and charging via usb) when my phone suddenly turned off. I had to pull the battery to get it started. When I tried to boot it it kept freezing while scanning the external sd. This happened over and over again and I wasn't able to get to the voltage app to change my settings. After I took my external sd card out it booted fine and I have since changed my uv settings and rebooted 10+ times to make sure it works and everything has been fine so far.

I'm assuming my issue was uv related but you say that yours isn't undervolted so I'm really not sure what happened with yours.

Running build #40 if it matters.
[Captivate Android Development] sixstringsg:
Ignore this accidental post.
[Captivate Android Development] Mevos:
It's good to have a confirmation, I've been using it for a long time too and I don't use the stuff for rooted phones either.

But the "Auto CPU speed" was one of my favorite ones because I thought it was saving me a lot of battery, After all, there shouldn't be much CPU used when the screen is off. :P

I wonder what happens to the CPU speed when the screen is off by default...
[Captivate Android Development] bclark:
Well SP took it to 400 and the 600 step was just added so probably 800? Just a guess. Maybe check time in state and the longest one will be it
[Captivate Android Development] elghouchd:
How do you clear the dalvik cache?
[Captivate Android Development] elghouchd:
Does anybody know an app that has a "time in state" feature like SetCPU had? I really want to to see if my phone is hitting 1400.
[Captivate Android Development] bclark:
Check this post by existz
[Captivate Android Development] psloan:
setcpu has it. You can see the time in state under the info tab.
[Captivate Android Development] sixstringsg:
Look a few pages back,eXistZ posted a terminal command to check. Just use "terminal emulator" from the market, it is free and copy the code in.
[Captivate Android Development] elghouchd:
Yea i saw that post but is there an app? just that it would be easier than copying and pasting that because i check the time in state a lot.
[Captivate Android Development] ccdoggy:
in recovery its one of the options within either the speedmod section or the clockworkmod section, i forget which. it will take a while to boot after doing that.
[Captivate Android Development] slider2828:
Do you guys even use stability test when you guys OC? This is a classic example of it being unstable at certain freq....

If your phone survives 20+ cycles on Stability Test, then I would say its pretty stable....

Freezing on boot, random reboots, random freezes means the core is unstable for what you OC/UV'ed it at.... period. Has nothing to do with the kernel....
[Captivate Android Development] MexicanAmerican:
I usually run SetCPU's Stress Test for about fifteen minutes, and Neocore for the same. If my device doesn't freeze, I think it's pretty stable.
[Captivate Android Development] MexicanAmerican:
Question: I've seen that most advise that you only enable one overclocked frequency if you choose to overclock.

Should you apply this practice to the higher frequencies, like 1.3 or 1.4 Ghz, or do you need to enable a frequency between 1 Ghz and those higher frequencies to maintain stability? Thanks in advance.
[Captivate Android Development] slider2828:
You should look at Shaolin95's overclocking guide to get stability. So far its 1 frequency at 1000+. That worked best for him.

I agree, but FAR too many people are complaining about instability which has nothing to really do with the kernel, more their CPU's can't handle it.
[Captivate Android Development] slider2828:
Existz....

You shoudl write in bold letters to people to download Stability Test and run it 20+ cycles to ensure stability. Clicking the buttons and enabling speed doesn't mean its stable. i think it will reduce a lot of clutter in your threads.....
[Captivate Android Development] existz:
Yea, i think for the most part, everyones issues are instability, ill post it in the OP.. also people should note that even if it passes some stress tests, it still could cause charge death and/or other issues, im not sure about all stress test, but i know some just shoot the cpu up to max freq and stresses it from there, thats not going to do any good when your cpu hits a lower freq such as 600mhz or so, if that one freq is unstable it will cause issues. You could try using VC app to setting the max clock to a lower freq, say 800mhz, then run stress test..it will then cap out at 800 and test from there, then do 600mhz..etc.. I wouldnt go to low, such as 100-200mhz, as things could get realllly slow and to sluggish to do anything..I cant say how well this will work, but in theory it should work for testing..i havent done this myself, so proceed at your own risk
[Captivate Android Development] SweetwaterBurns:
Existz,

I was poking around with system settings and noticed that as long as the conservative governor is being used, the cpu speed jumps to 800 mhz whenever I touch the screen. If you use ondemand it stays at 100 mhz so I don't think this is necessary for the driver to work, but I could be wrong. Is this behavior there for a reason or is it a bug?

I'll probably download the AOSP kernel source and run a few diffs with your source to see if the Samsung/Captivate patches changes something, but I won't waste my time if I don't need to.

Thanks for a great kernel, as well. It's exactly what I was looking for.
[Captivate Android Development] existz:
Its probably just the way the governor is, with mine it varies, sometimes when i touch/move the screen it stays around 100-200mhz other times it jumps 600-800, just depending on cpu load, the stock settings for linux/android on the conservative is up threshold=80 and down threshold=20 with freq_step=5%, in the latest version its set to up=90 and down=55 with freq_step=5%, a little more aggressive but should give better perform/battery ratio,.. but this behaviour is the same at stock settings which is the same for linux/android
[Captivate Android Development] sf1120:
How's gps performance for you guys on build 40 and 41?I'm currently running build 40 and gps is worst than when I was on build 32.When I say worst,I mean tracking is way off.It locks on pretty quick and stays locked,but tracking is really bad,unlike #32 which tracks perfectly.Considering flashing build 41.Anyone care to comment?
[Captivate Android Development] Auridran:
I run both 1.4GHz and 1.2GHz.

Also, here are the requested screenshots:
[Captivate Android Development] nybmx:
I ran Stability Test for 80+ cycles, ran neocore and other cpu intensive benchmarks and games and it was all stable before I had that issue. I am very careful about making sure everything is stable before I apply boot settings. I'm not new to either overclocking or undervolting. My issue was likely because of a lower frequency which was unstable but hadn't shown a problem during the previous 24hrs of use.

Please don't assume without asking.
[Captivate Android Development] justmart:
Which Rom? Thanks

Sent from Puerto Rico
[Captivate Android Development] Auridran:
My ROM, linked in my sig.
[Captivate Android Development] neffarious:
That looks like the phone sat unused for 3 days. I'm assuming you didn't do very much with it to ge those results?
[Captivate Android Development] slaman:
No more sleep deaths at -25mV across the board (with no OC), but now my camera doesn't work... it freezes, then reboots.

Looks like I can't take advantage of this kernel at all.

When it does work, the battery life is amazing.
[Captivate Android Development] justmart:
Sorry, with xda app I can't see the sig.

Sent from Puerto Rico
[Captivate Android Development] Auridran:
I sent probably close to 500 texts in those three days. I haven't done much with the phone other than that. A couple voice calls as well, and a few minutes of Fruit Ninja here and there.

justmart: http://xdaforums.com/showthread.php?t=932205
[Captivate Android Development] existz:
EDIT

deleted post since figured out UV was causing it
[Captivate Android Development] Psyclotr0n:
anyone done an apples to apples (as much as is possible) battery life test with regular SpeedMod?
[Captivate Android Development] slider2828:
Hence the quote testing it. Like the above thread from existz said, if you want it perfect, you going to have to clock down to every freq and test it with stability test.....
[Captivate Android Development] existz:
Should have a new version up later tonight or in the morning, basically tweaked the conservative governor some more, should give better battery life...also there will be a new "XT" version replacing the 500hz version, instead of 500hz its 1000hz, with user hz=200hz, according to testers its alot smoother.. Also updated the code for all the frequencies, should be more stable... going to run a few more test before posting, hopefully get it up tonight
[Captivate Android Development] lrs421:
Awesome, can't wait to try it out. How does battery life compare in the 1000hz vs. 500hz?
[Captivate Android Development] existz:
Some users have reported a tiny increase, but say its well worth it, others say its the same as 500hz...I personally think its the same, so it seemed for me anyways. But if you guys think it drains to much and is not worth the extra smoothness, ill revert back to 500hz..but I don't think that will be the case

Also will add car/home dock support
[Captivate Android Development] lrs421:
Awesome. How can you resist something labeled "XT". Can't wait to take it for a spin.
[Captivate Android Development] joeshmoe08:
awesome, can't wait for the new XT versions. I am ready to sacrifice some bat for more smoothness! Also existz, just curious when talking about userhz and stuff, why can't you just always keep kernelhz and userhz equal? Is it unsafe to increase userhz to certain level? I am sure there is a reason because if there wasn't couldn't you just make userhz 1000 as well which would eliminate conversion and result in same battery life as 100mhz variants?
[Captivate Android Development] lrs421:
I'm new to this, what does the user 200hz represent/mean?
[Captivate Android Development] Dani897:
i dont know if this has been covered but i noticed you credit glitterballs, does this kernel have mods that fixed the charge death issues in his overclock kernels? im tempted to flash this over yin for speed that will melt your face off but i need total stability as well.
[Captivate Android Development] existz:
No, I credit glitterballs for config options I got from him.. as far as charge death goes, it seems the only time it happens is if your UV is to low or unstable, other than that a few tweaks Ive done fixed it for alot of people, im not sure if its the same GB uses in his, haven't been able to get ahold of him
[Captivate Android Development] Dlev7:
Very very excited am on Build 41 still no charge death OC'ed to 1.2 GHz with -50,-75,-75,-100,-100,-125 CFQ. Super stable and the fastest ive ever had my phone.

Really excited to try the the "XT" version, with this would I need to delete voltage or just leave it as is because the steps are not changing.

But once more I can not tell you how amazing this kernel is + Darkyy's 9.2 there is nothing better
[Captivate Android Development] sicmadek:
i ran several quadrant test and i get 1200 at 1ghz which is fine. i then tried 1.2, 1.3, and 1.4 with no benefits. im clueless as to why.

also this is with no lag fix.
[Captivate Android Development] existz:
Are you sure you have the states enabled in voltage control app
[Captivate Android Development] johan8:
I'm using #41,

after charged to 100% then unplug the power cord,

my phone shows 99%.....

is it something wrong ?
[Captivate Android Development] sicmadek:
yup that was the first thing i checked. the only other thing i can think is there is something wrong with the quadrant app.
[Captivate Android Development] Dlev7:
Existz you think your going to get that XT version out tonight? And as I said earlier will we have to delete our old voltage control settings? I dont think we would need to cause they are the same steps.

Not trying to rush just wondering if I should go sleep : D Haha anyways thanks in advance build 41 is AMAZING
[Captivate Android Development] Dani897:
thanks for the quick answer. my phone is very prone to charge death and even without undervolt dies on kernels other than glitterballs. your answer leaves me weary because on glitterballs it would freeze well before i got charge death. i may try it but not today, ill test it for the weekend when i dont need the phone.

also i dont need 1.4ghz, i haven't successfully gotten it to run at that speed but i prefer 1.3 ghz to 1.28. though the benchmarks are about identical i think the timing plan works better at 1300, i dont know all about it but in the past 1300 seemed to be a bit smoother than 1280.
[Captivate Android Development] existz:
Yea, going to test one more thing then ill upload it, probably in about 30min-hour, you shouldn't have to delete the s_volt_scheduler file, but since I changed the frequency code and the governor acts a little bit differently now, you may have to adjust your UV settings, since the code is different now, I don't know how it will effect it, so if it seems to be unstable, adjust it...but it shouldn't effect anything, just one of those "just in case" things
[Captivate Android Development] Dlev7:
Very cool what are some features will this affect battery or no? And this will be even smoother? incredible! Well good luck keep up the good work
[Captivate Android Development] pizz0wn3d:
A smoother experience? You Sir, are raising there bar way too high for other kernel devs to compete.

But that's not my problem B-)

Herp derp Captivate XDA App
[Captivate Android Development] Dmoney5150:
Clear this up if im clueless I updated to 41 and now voltage control fcs on me I've tried everything I know to do any ideas?
[Captivate Android Development] Dlev7:
Delete etc/init.d/S_volt_scheduler

Reboot
[Captivate Android Development] mkr14:
What does "tried everything" involve? An uninstall / reinstall of the VC app fixed this for me when I had it happen.
[Captivate Android Development] ccdoggy:
no problems. nature of the beast.
[Captivate Android Development] existz:
*UPDATE*

Build #43

-New "XT" 1000hz version - replaces 500hz version (more smoother)

--Kernel HZ=1000hz | User HZ=200hz

-Modified 'Conservative' governor settings (should give better battery life)

-Updated CPU frequency code (should be more stable)

-Captivate car/home dock support

--Audio uses dock when available (no need for the Rogers Captivate dock app)
[Captivate Android Development] Dlev7:
Awesome going to try out the new XT super excited. Congrats on the new release and better battery life and even smoother seemed impossible. I dont know how you keep doing this
[Captivate Android Development] sicmadek:
damn it you keep updating and i cant help myself. this damn flashing addiction. i swear one of us is gonna end up on intervention one of these days lol.
[Captivate Android Development] johan8:
I see.

However in the previous versions it would stay in 100% for a while after unplug .
[Captivate Android Development] pizz0wn3d:
I do believe I managed to flash the update within 2 minutes of you posting it haha. Awesome. Can't wait to see how this thing is gonna perform throughout the day.

Herp derp Captivate XDA App
[Captivate Android Development] Dmoney5150:
WORKED PERFECT THANK YOU!!
[Captivate Android Development] Dlev7:
Your welcome when ever you have problem with Voltage Control thats all you gotta do. Glad I could help.

Existz: Creepily pressed refresh on the page when 43 appeared flashed immediately this things FLYS had no problems left the voltage the same everythings super stable, no COD. Well done keep it up
[Captivate Android Development] slider2828:
Hey Existz.... For some reason, my GPS is not as good as paragon's kernel. I mean its way off when compared to it. Do you know what might be the main difference? He has that GPS thing down! I only get like 9 Sats around 30 or 35, but he gets like 12 Sats and like 35-40. Same everyting, just a kernel flash.

Any ideas?
[Captivate Android Development] lrs421:
Existz, would you consider bringing the 500mhz back. I hate asking you to do extra work but it seems to perform best on my phone. I just tried 43 and flashed back to 41/500. For some reason its smoother than both versions of 43 on my phone.

Love the frequent updates!
[Captivate Android Development] existz:
Im thinking the problem is the governor settings, I got some reports that #43 final is not as smooth as the TEST version, and the only thing that changed was governor settings, ill change then back to previous settings and see if that helps .. cause everyone was seeing a difference with 1000/200 over 500/100.. in theory the governor settings should have been more aggressive but might be to aggressive.. ill see what I can do about getting it posted tonight, then if there's a demand ill bring 500hz back
[Captivate Android Development] lrs421:
See what I mean about the dedication and updates :-) Great work dude.
[Captivate Android Development] steviusthedevious:
so hey, i'm not heavy into flashing kernels, forgive my stupidity. i'm looking at flashing CM7 tonight, but to switch back, need to flash my current kernel via odin. do i just convert the regular .zip to .tar.gz and use odin, or is there some other hackery to do? i'm running darky 9.2 with build #43.
[Captivate Android Development] existz:
Im pulling #43 while i figure this out, shouldnt take me long, only 2 things was changed from TEST version to final version, testing 1/2 now..so should be much longer...sorry about that guys.
[Captivate Android Development] Kizzmiazz:
Don't know if it has always been there, but on boot when it switches from the att screen to the SuckerPunch boot screen, right up at the to its all screwed up.can't ready explain but like something else up there lol its real quick.

Sent from my SuperDuper!Captivate | Precision v2.5 Smaller Is Better | SuckerPunch-SmR XT #43 | Member of Team Phoenix
[Captivate Android Development] existz:
Yea its due to the 350mb ram settings, i tried doing a version just with 340mb settings and it doesnt do that, it wont hurt anything, i asked everyone which one they wanted,...to keep 350mb or go back to 340..not sure which im going to do yet, but im going to try and fix it first before having to revert back
[Captivate Android Development] existz:
Alright..fixed the stutter/lag problem with #43, getting ready to upload #44 ..so shouldnt be much longer..again, sorry about that
[Captivate Android Development] Kizzmiazz:
Oh no, that's cool, was just wondering. Either is cool. But really the extra 10 megs really don't anything for these phones either lol. I hardly every reboot my phone though either, so again really dont matter lol

I thought maybe I screwed the pooch with something lol

Sent from my SuperDuper!Captivate | Precision v2.5 Smaller Is Better | SuckerPunch-SmR XT #43 | Member of Team Phoenix
[Captivate Android Development] slaman:
I'll be the first to voice my opinion... I'd prefer to stick with the version that doesn't have the snow... I don't notice the extra 10MB of RAM, and I don't want anyone using my phone to ever have a chance to say "iPhone doesn't do that" heh.
[Captivate Android Development] existz:
*UPDATE*

Build #44

-New "XT" 1000hz version - replaces 500hz version (more smoother)

--Kernel HZ=1000hz | User HZ=200hz

-Reverted back to previous governor settings (no cpu stutter/lag like in #43)

-Updated CPU frequency code (should be more stable)

-Captivate car/home dock support

--Audio uses dock when available (no need for the Rogers Captivate dock app)
[Captivate Android Development] slider2828:
Ahh...... sexiness returns. #44 is much better than #43 especially nenamark!

Geat Job!
[Captivate Android Development] sicmadek:
Nenemark? (10char)
[Captivate Android Development] slider2828:
Nenamark is a 3d FPS Benchmark tester... Probably the most accurate out there right now.... Download it.
[Captivate Android Development] Kionic:
Great...flashing 44 now. Also I prefer the extra 10 mb.
[Captivate Android Development] Kizzmiazz:
Well all I have to say so far Existz is DAMN this kernel is fast. I'm running ryude's new precision rom and #44 xt with no lag fix and boy this thing is fast lol Amazing with no lag fix how fast. Plus, forget to mention last time I said I would lol, now that the charge death is fixed I think you finally made me have a reason not not use firebird, suckerpunch is my new favorite kernel lol.

Now fix the boot screen lol

Sent from my SuperDuper!Captivate | Precision v2.5 Smaller Is Better | SuckerPunch-SmR XT #44 | Member of Team Phoenix
[Captivate Android Development] Kizzmiazz:
Dg has proved many times that you would never notice that 10 megs and helps no where. Android phones kill apps way before then and personally I have never gone that low anyway lol

I'm like the above poster a few back. Even though its not a deal breaker it does bother me when I see it and this kernel is so perfect why have a flaw ;)

Sent from my SuperDuper!Captivate | Precision v2.5 Smaller Is Better | SuckerPunch-SmR XT #44 | Member of Team Phoenix
[Captivate Android Development] existz:
Yea, to be honest I seriously doubt anyone will ever truly take advantage of the extra 10mb, like you/DG said, android starts killing process automatically before it even gets close to that, so ill probably revert back to 340mb in the next version unless I can figure out the problem, I would have done it in #44 if this conversation was 10min earlier lol.. but ill continue to work with it after I remove it and add it back in for ****s and giggles whenever I figure it out
[Captivate Android Development] AtoZ0to9:
My phone is freezing in the extended power down menu after setting the UV values... using the XT version on a freshly installed ODIN Darky 9.2... I set the UV values to 100 for all clock frq I plan to use... Also froze when in the voltage app when I put it to 200... Should I be adjusting my UV settings to neither of those with this new kernal?

EDIT: Had installed #43... gonna keep testing...
[Captivate Android Development] Nickel Dime Bay:
I was looking at the stuff in recovery and on my lagfix settings it says CACHE EXT4NJ or something like that, isnt it supposed to be just EXT4? what is the NJ?
[Captivate Android Development] IStern:
Maybe it's just my phone, but I get better perceived UI performance, better 3D performance, and better benchmarks using the 100hz version of this kernel. I hope suckerpunch will always have a 100hz version!
[Captivate Android Development] slider2828:
100UV for EVERYTHING? Higher freq needs more voltage. Start reducing 25 at a time and use it.... 200 is just not possible, never seen anyone undervolt at any freq 200....

No Journaling. Its fine, its a little faster...