yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] elghouchd:
Sooo....which version gives better performance, 100hz or 1000hz?
[Captivate Android Development] existz:
Some can't tell a difference, for others its not necessarily faster but 1000hz is smoother on certain things (opening app drawer..etc).. for others, 100hz is better, with me for example.. I don't do anything to where I see a difference in speed wise, and 100hz gives me great battery life..so I always use 100hz... Your not going to see one better than the other with any benchmark, it just comes down to certain situations benefiting from a higher hz value and other situations benefiting from no kernel hz--user hz conversion (100hz) ..just depends what your doing
[Captivate Android Development] AReynante:
I've always felt like the 1,000hz was smoother, but honestly, the difference is very small to me.
[Captivate Android Development] iXNyNe:
for those of you who (like me) have in the past made the mistake of not deleting S_volt_scheduler before flashing a new oc/uv kernel, i made this handy little CWM flashable zip to handle the task for you (in case you get stuck with an S_volt_scheduler that doesnt play nice with the new kernel you just flashed)

feel free to take this script and modify it for whatever you want, i claim no copyrights (i just rewrote a file from a CWM flashable package i found)
[Captivate Android Development] sinichi21:
hi exizt is the dock modification included in this kernel?
[Captivate Android Development] WickedNite:
Somehow after I deleted the volt scheduler and flashed the #53 update, seems to be that the scheduler is still there. I opened Voltage Control and the previous settings was still there. Haven't had any issues though.
[Captivate Android Development] existz:
Yes, but however I have not added in xcals latest send voice audio through dock yet... to be honest, the dock support is untested, I do not have a dock and was unable to test if its working, so if you run it..please let me know if dock support works, ill add in the route voice audio to dock when available soon
[Captivate Android Development] ninjuh:
Voltage Control says 6-7 clock modes are suggested at a time. What does everyone else do? Which clock speed do I drop to keep things stable at higher speeds? I don't understand
[Captivate Android Development] existz:
Keep 100-1000 selected for best battery life..then if you OC to say 1200, theres no need to have 1120 selected, ..also if say you want to OC to 1400, you can have 1200 and 1400 selected.. theres no need to have 1120,1200,1300,1400 selected..to many frequencies can mess up the smoothness in scaling, thats why VC recommends having 6-7, but 8 is ok also when using higher frequencies, just dont overkill it
[Captivate Android Development] RuizGT:
Just changed to 53, went to reboot to recovery through the power menu, but it isn't showing up for some reason.

Yes, I did a search.
[Captivate Android Development] ridethelight:
Got a sleep death just now, unlike any ive had before, instead of just the screen not coming back on but the phone still on(volume buttons still gave a tone) the phone looked like it was off and no buttons did anything (including power).

Forced a restart by holding volume up and power and it rebooted.

Only had 1 single sleep death with #51, I hope this doesnt become a normal thing
[Captivate Android Development] iXNyNe:
sometimes a few extra files called like schedule99 or something get made (i dont know the exact word or numbers, but theres usually two files)

would you mind telling me the names of those two files? they can be found in the same folder as the regular scheduler
[Captivate Android Development] Rrryan2:
Gosh it's good to be home

After stock UCKB1 hit, I switched over because I was still developing my gps 'fix' and thought it best to move over to the mfr and carrier-approved solution while I continued developing in the belief that it might do the greatest good over the long term. But I got tired of it fast.

But gosh I missed my SuckerPunch Kernel. So much so that I finally got sick of it earlier tonight and when I saw SP #53 had hit I couldn't resist any more. So now I'm back to the OC/UV world. And loving it. Not only are benchmarks through the roof again, but battery-sipping mode is enabled again.

And KP1's gps handling is better besides, ftw. :)

I'm on Cog4.1.1 for the moment, but I wonder if it might not be too long before I migrate back to Precision 3.5 esp. if Ryude comes up with another release...
[Captivate Android Development] existz:
I will have a new test version up tomorrow, just noticed I left a few things out from #51

-fixed safe boot to 1ghz

-modified governor threshold (better battery)
[Captivate Android Development] :
for some reason after i updated to # 53 update , my neoscore when down drastically. I even have the same settings as before

from 65.4 to 48.7 . I mean even the normal score for Captivate is 55 :(
[Captivate Android Development] olo567:
Hmmm. Did you try the volume toggle trick from before? Just ran once, got 64.3.
[Captivate Android Development] :
No I just did a normal run before. Volume toggle trick ? I don't even know what that is lol

so I flashed it through CWM and then changed the settings of UV and OC from the mini guide up here and applied boot settings and then

Checked the neocore and score went down to 48.7
[Captivate Android Development] olo567:
I think it was set the media volume to zero, then run it. Then you should be able to bring the media volume up again and still get a good score. Not sure if it applies anymore. I have all the recommended speedmod tweaks applied in CWM and the custom memory timings from the OP as well, not sure if that matters.
[Captivate Android Development] :
So I deleted and flashed again and now everything is normal.

Thanks though :)
[Captivate Android Development] existz:
Mine does that sometimes after a flash, all I have to do is run fps2d or something, then lock my screen then unlock it and when I run a gpu benchmark again I have 65fps...not sure why it does that but...iono
[Captivate Android Development] MikeyMike01:
I think I found a stable level. The UV is disappointing, but the OC is more than in the past.

Noop

1400 -0

1200 -25

1000 -50

800 -75

600 -100

400 -125

200 -150

100 -150
[Captivate Android Development] xdahgary:
So I tried build 53 last night...ran neocore and got 64fps (nice), ran linpack and got 14. Kept running linpack and getting 14 with it saying it's at 1ghz. Probably your run at 1ghz at boot parameter, but why neocore can get up to 64fps? is not reliant on cpu speed? Anyways, did camera test and froze on my original settings. 3 button rest and lowered settings and did camera test again and froze. 3 button reset again and to my surprise, my homescreens were blank. All my shortcuts and widgets gone. :(:mad:
[Captivate Android Development] existz:
Hows it running so far? Better than previous versions?
[Captivate Android Development] slider2828:
I am still on the TEST #53 and geezus the battery is phemomenal.... I would say almost >1% drain for me per hour....

Just when I run programs it drains, but what can you do on 1300mhz.....
[Captivate Android Development] MikeyMike01:
Better, yes.
[Captivate Android Development] ridethelight:
So the sleep death a experienced before probably wasnt a sleep death, but probably a straight system freeze like i experienced 2 minutes ago in the middle of a text message. If it happens again Im going to switch back to #51 and see if it persists

That is, unless a new version comes out :)
[Captivate Android Development] existz:
Since i started from a clean source and changed quite a few things, you will most likely have to adjust your oc/uv settings compared to #51...
[Captivate Android Development] existz:
I've got a new test version up, modified governor threshold, should give better battery life...should help during use
[Captivate Android Development] Auridran:
So after using #53 for awhile, it seems a whole lot smoother than #51, and seems to give about the same battery life. No bugs to report.
[Captivate Android Development] M1nur:
just kinda curious what people are getting on their quadrant scores?
[Captivate Android Development] ninjuh:
I'm running #53 and I have a question.

Whenever I turn my screen off, then unlock, the phone is sluggish and slow, but once I open an app then go back to home screen its wicked fast from that point until I put the phone in standby again. I've tried all different combinations of clock speeds/uv settings all with the same result. Anyone experiencing this?
[Captivate Android Development] ridethelight:
I got another freeze in the middle of typing. Going to try and mess with my UV and see if anything helps. Also just remembered that my problems started when I enabled the 600mhz state and disabled 1120(to keep the recommended 7 states as recommend by existz a few pages back) Going to try disabling it again and see if i get a freeze.

The only score that matters is how well you like your phone. Benchmarks will tell you somethings but its hard to relate those to actual use. Quadrant has been bashed to no end as being useless. This was all discussed a few pages back
[Captivate Android Development] :
One more thing I have noticed or maybe just happening with me

When ever I reboot my phone and then go to check battery use, it always resets for some reason :confused:
[Captivate Android Development] ninjuh:
That's what its supposed to do.
[Captivate Android Development] doreyu:
Weird, this was performing very well then I switched to SP-Voodoo. I made sure the voltage settings were not in etc/init.d before flashing back to this.

It booted and kept freezing, it retained unstable UV settings for me, even when I didnt have it UV'd like that before going to Voodoo.

I had to quickly get into voltage control to fix it
[Captivate Android Development] slider2828:
Check your RAM usage, I have noticed that when it falls under 100MB things tend to drag...
[Captivate Android Development] slider2828:
I think they are completely different base code, so I wouldn't switch back and forth like that..... IMHO....

But in SP couldn't you just limit to 1000mhz and just call it the same as SP-Voodoo? I mean that is really the only difference.... no need to switch back and forth

On a side note: DID YOU SEE THIS ISH!!!!!

Gingerbread for Galaxy ported with this guy.... JV1 Based.....

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

Hopefully SP will work for this, but I doubt it.
[Captivate Android Development] olo567:
My whole phone will sometimes freeze up, I'd get the -.. buzz indicating an FC, and the whole phone would reset (soft reset, just restarted screen, apps, and cell radio, not whole power). At first I thought it was my UV settings, but even with UV off I have the issue every once in a while when returning from sleep.
[Captivate Android Development] slider2828:
Time to reload everything.... Seriously.... It will be the best way to work out bugs of this nature....
[Captivate Android Development] froli13:
I OC to 1200 and enable every states from 100 to 1200 and everything is smoooth :) It's even smoother since I've enabled the 1120 state curiously...
[Captivate Android Development] WickedNite:
It feels like my phone heats up when on standby when it's on my pocket. It noticed just now, heated up a couple of times. I only using 1200Mhz and uv'd as crazy.
[Captivate Android Development] Chillyw:
I noticed this earlier today too, pulled my phone out of my pocket, it was very hot. I'm not overclocked or undervolted at all yet.
[Captivate Android Development] Chillyw:
I got this as well earlier without UV or OC on.
[Captivate Android Development] WickedNite:
Good to hear that I'm not the only one, anybody else?
[Captivate Android Development] pizz0wn3d:
Yeah I've had a few lockups, but haven't posted about it because I wasn't sure if it was my uv settings or a kernel issue, though I haven't uv'd any more than I have on previous versions. I'll post again if I figure out what's causing it, but I'm not a dev so I don't know as much as others as far as that stuff goes.

Good luck figuring out the problems existz :D

Herp derp Captivate XDA app.
[Captivate Android Development] olo567:
Doesn't occur with other kernels, specifically speedmod which this is based off of.
[Captivate Android Development] crazililazn:
With build 53, using the memory timings file causes launcherpro to force close everytime i reboot. It only happens once, but it didn't happen at all when on build 51. I know the problem is the mem timings because when i delete the file, it is fine. So it must be something with build 53 and the memory timings. Anyone else with this problem? x.x

Adding to my post, I noticed that w/o the mem timings, my phone is significantly snappier, especially when multiple apps are open. With the mem timings, having multiple apps REALLY slowed the phone down :X
[Captivate Android Development] Jaeden09:
Can we get a tutorial or a link to a post in the OP on how to install the lagfix properly for this kernel from recovery?

Thanks :) Awesome Kernel, if I knew how to do the lagfix properly.
[Captivate Android Development] existz:
goto recovery, speedmod features...lagfix...enable lagfix...
[Captivate Android Development] pizz0wn3d:
...reboot...choose a "Yes..." option...
[Captivate Android Development] AReynante:
It should already be enabled, no? Mine was
[Captivate Android Development] Shammyh:
Hey existz,

Are the >= #53 kernels still using the JS5 initramfs? Just wondering.

Also I've noticed some odd quirks starting with version 53. Long boot up times (in the kernel stage, before android loads), random one to two second events where everything moves really slowly, and personally I feel like my UV threshold is less forgiving.

#51 was rock solid for me though...
[Captivate Android Development] ridethelight:
definitely switching back to #51, it was absolutely solid for the longest. #53 is giving me freezes and reboots for no reason (was fine for 2 days then a bunch of freezing).

Either that or my phone has the reboot of death.

edit: Did some additional testing. Im 90% sure its the pesky 600mhz state, I lowered my the clock limit and disabled states down to 600mhz and my phone froze 1-2 times a minute running stability test or not. First I'm disabling just 600mhz and working my way down from 1ghz running stability test 1.4 to confirm its only the 600mhz state

Edit 2: Since disabling 600 i havent had one problem. Running limited to 400 right now and all seems well. I find it surprising that 600 doesnt like -125mv but 800 handles it all day long.

Is it worth making 600 stable by decreasing UV, as apposed to skipping it?
[Captivate Android Development] Swishaa:
Hey are you going to make a kernel for cm7? Just wondering , don't want to seem demanding (:

And forgive me if you posted about it earlier and I didn't see it
[Captivate Android Development] existz:
Yes, keep the 600 step, just because one step can handle a certain mV, doesn't mean another one can....most problems are from just assuming...lower your UV!
[Captivate Android Development] mkr14:
Yes it does
[Captivate Android Development] existz:
I get better battery with 1120 over 1280, so in my experience 1280 does use more
[Captivate Android Development] WickedNite:
Okay. I guess I'll stay with 1120 then. Thanks for answering!
[Captivate Android Development] nickm50:
Here you go!
[Captivate Android Development] chrisz5z:
was able to complete a run with Smart Bench 2010 :), stable so far @1280 w/500hz

stock scores were 1056/2439, running @ 1280 they are 1290/2955
[Captivate Android Development] nickm50:
1396/2956

10char
[Captivate Android Development] PuffinNugz:
its doing something screwy with your linpack. im pulling 17.9-18 mflops and 1424/3093 on smartbench with gb's kernel. Just more proof these benchmarks don't mean much.
[Captivate Android Development] Aus_Azn:
If this kernel doesn't have charge-death when overclocked, I'll try it. Any experiences with an overnight charge yet?
[Captivate Android Development] leets4uc3:
Smart bench 2010???

edit: 1425/3099 with gb's kernel
[Captivate Android Development] existz:
I wouldn't go comparing benchmarks between mine and GBs, I can already tell you mine will score lower, im pretty sure I use slower mount options (you can enable faster mount options in cwm if you just want to boost your scores, but its not recommended as it can end up causing corruption), plus I probley use other settings that take a hit in scores, but its better on battery, im not aiming to be fast, my main goal is to have great battery life, something close to Hardcores but with the option to UV
[Captivate Android Development] existz:
I've yet to have a charge death and I've been using this configuration for over a week now, I've ran every version, plus I've tested out countless others in the process, still yet to have it happen, so its kinda hard for me to test fixes as I can't tell what works, what doesn't, I messaged GB, hoping to figure out how he fixed it, as soon as he answers me or he releases his source ill try to get this fixed
[Captivate Android Development] WickedNite:
Exactly. I don't mind scores or benchmarks, I just want a stable, fast, and battery efficient kernel which results to SuckerPunch.

Sent from my Muscles using Brain Cells
[Captivate Android Development] leets4uc3:
After a good battery test tomorrow, I am going to try this out

Serendpity. Awesome.
[Captivate Android Development] rootnik:
If I somehow got a 25 linpack I would never flash anything or even reboot ever again. :D
[Captivate Android Development] dmshaefe:
Just installed on the FF 2.0.5 release and works very well. I am getting the highest linpack I have ever gotten (17.9 ish) and 1430's on quadrant. Excellent work! Haven't tried charging yet so we will see how that goes.
[Captivate Android Development] TRusselo:
ok this is my first oc kernel. just flashed and installed voltage control.

i flashed the 1280mhz version 250/default

in voltage control under the 1280 heading the voltage is just a ? mark no voltage like the rest of the list.

Is this normal?

there were no previous file in system/ect/indt.d/

does setcpu have anything to do with it? although it was disabled (no boot)
[Captivate Android Development] mkr14:
This kernel rocks Existz! 0 Problems and everything is solid. Thank you for this!
[Captivate Android Development] Auridran:
I'd just like to say that your kernel grew on me so fast I decided to include it in my ROM release :)
[Captivate Android Development] TRusselo:
GREAT! cant wait to try a canadian rom! (hopefully not americanized) but any advice for my question 2 posts up?..
[Captivate Android Development] Kizzmiazz:
Yeah I have to say man thank you for this kernel. I finally decided to give it a shot and I have to say it is very fast and smooth. Have not had any problems so far, just loaded it though lol, and am very pleased.

Thanks Again Existz

Sent from my SuperDuper!Captivate | PHOENIX RISING 4.1 | Firebird 2 v0.5 | Member of Team Phoenix
[Captivate Android Development] DrGoodspeed:
i use launcherpro and have the mem timings, but it hasnt fc'ed once even after reboots.

i also have not had one reboot, fc, or freeze, but my uv is only -75 for all
[Captivate Android Development] Chillyw:
My phone started running really hot again today while on standby. Its not consistent and has only happened twice, but it gets hot enough to worry me. I'm also not OC'd any.
[Captivate Android Development] existz:
*UPDATE*

SuckerPunch-#54

Delete Voltage Control settings

before

flashing

-Adjust Conservative governor threshold (better battery life)

-Fix safe boot to 1ghz

-Tweaked sched_latency and min_granularity

NOTE

These are a few things I left out from #51, it should help with battery life even more. Also, if you were having stability issues on boot, this build should help with that.
[Captivate Android Development] froli13:
Just lower you UV on the 600mhz state. I'm also having "issue" with this state, so I just lower the UV for this state.

My UV settings are:

1200/-100 1120/-125 1000/-125 800/-125 600/-100 400/-150 200/-150 100/-150
[Captivate Android Development] ridethelight:
Had this happen today. Battery went from 90 to 50 in 2 hours then down to 20 in another 1 hour, battery temp was at 41 from sitting in my pocket idle. Hopefully 54 is better than 53 :/

Edit: This is all after i enabled 600mhz and lowered UV to -100, which i tested last night in stability test for 15 minutes. Maybe I need to run stability test for longer....
[Captivate Android Development] crazililazn:
Stability test only tests the stability of your highest frequency.
[Captivate Android Development] sinichi21:
Im using the suckerpunch 54 test is there a difference on the official release? I don't know if its kernel base but im having trouble with my wifi not turning on sometimes had to go to setting and toggle it a few times to activate and once I deactivate it my signal drop never happen to me on sp vodoo and sp 53
[Captivate Android Development] existz:
Try flashing to 54 and clear cache/dalvik cache ...there's no changes in #54 over #53 that would effect wifi
[Captivate Android Development] aalh:
Desktop population delay with 100hz(std) kernel

ROM: SuperNovaJS5

I have been hunting the cause of an issue I had and stumbled into it.

I was running #53 100hz, and have been running SP for a while now, usually the 100hz version

I have had as long as a 60sec or longer delay after the phone boots before seeing anything on the desktop, and the app drawer is empty as well for the same delay. This has been going on for weeks, I thought it was a dirty restore, so I mastercleared and started from scratch

it still happened

I downloaded #54 tonight, both versions

by chance I picked the 1000hz version and flashed it first

the phone booted and the desktop was loaded as fast as it had ever been

so I flashed the 100hz #54 and the delay was back

to confirm I did it two more times with identical results

the app drawer is still empty on 1000hz and the widgets say "loading..." but the icons are loaded and the shortcuts are active

unlike the 100hz which gives me a useless phone for the first minute after completion of booting.

it is like the 100hz kernel waits for media scanning to be done before it even tries to populate icons
[Captivate Android Development] aalh:
when that starts happening I toggle airplane mode

it seems to help sometimes
[Captivate Android Development] airbillion:
I have have had the same problem for a while too. I will try the 1000hz rom to see if it fixes it.
[Captivate Android Development] LNJ:
Any advantage using Voltage Control over SetCPU?

SetCPU is working fine for me on OCed sppeds but haven't run it long enough to see how it affects battery life.

So far seems stable.
[Captivate Android Development] existz:
DO NOT USE SETCPU!!

The OC/UV code is pretty much wrote for Voltage Control, use it...you have to enable which "states" are to be available and then set the max clock, which that cannot be done with SetCPU...plus you cannot UV with SetCPU...it will cause more problems than its worth
[Captivate Android Development] jonski89:
Charge death

hi existz... i got a charge of deah with #53 last night... after setting up the settings psloan posted on irc...

now, i downloaded VC 3.01

will try to check this forum for good settings for UV then i'll get back to you...

Thanks.
[Captivate Android Development] aalh:
well the OP says in bright red letters

DO NOT USE SETCPU
[Captivate Android Development] aalh:
it didnt fix it.

The phone didnt crash while I slept, but 5min after I wake it up to check the time and set it back down, I notice it is booting, since I did not turn it off, it should not be booting

and in addition the desktop delay is back:eek:

I did not have reboots and shutdowns on the 100hz kernel, so I am going back to it

I would discuss this in IRC, but I cant use IRC for some reason

any client I try gets a socket error and disconnects constantly

Not your fault, but it does make it difficult
[Captivate Android Development] froli13:
Are you using LauncherPro? If yes, just kill it when you phone is booted using task manager and it should be fine.