yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
What it calculates could be different in my code, not sure .. but I get the same 1354 bogomips but still get 19+ in linpack...and this is with both xt and non-xt, downloaded both from OP to verify I uploaded the correct ones

EDIT

Ok, went back to #41 and you can just select 1200 and 1400 and get 19+ in linpack, so its something in the new frequency code, ill revert it back to how it was previously so you dont have to select 1300 then disable..etc etc..give me a minute and ill update it
[Captivate Android Development] lpsi2000:
Yep, I am not getting that with LinPack, the highest I get with linpack at 1.4Ghz is 18.6
[Captivate Android Development] shaolin95:
Interesting. Will have to test Paragons kernel to see if it is this Andromeda ROM causing this less performance issue. Although everything feels pretty snappy aside from that small variance.
[Captivate Android Development] lpsi2000:
I have also noticed while troubleshooting after I unplug my power cable my battery show 97/98/99% even though it was just fully charged. At first I thought it had something to do with my ROM. But I can now confirm it has nothing to do with the ROM. I switched to SetiRON's kernel and the issue is gone.
[Captivate Android Development] Auridran:
That's odd. I'm getting ~19.5 at 1.4GHz and #45. Was only getting ~19 with #44 due to the clock bug.

lpsi2000, it is a "feature" of all 2.2.1 kernels to my knowledge.
[Captivate Android Development] existz:
Ok, i checked and with #41 you can just select 1200 and 1400 and get 19+ in linpack without having to enable/disable..etc.. so its either something in the new frequency code or the governor settings, also tested #41 and getting 1379 bogomips, so something is calculating incorrectly in #45...let me fix it real quick and ill post an update for it
[Captivate Android Development] Auridran:
I'm getting 1393.45 with #45.
[Captivate Android Development] opcow:
You aren't using an old copy of s_volt_scheduler are you? Also, how many frequency states do you have enabled?
[Captivate Android Development] lpsi2000:
What is a feature of all 2.2.1 kernels?
[Captivate Android Development] slaman:
You're lucky... I'm running 1.4GHz (UV of -50mV) on XT and the most I'm getting is 16.6

What states do you have enabled? Mine are:

1400MHz @ -50mV

1200MHz @ -50mV

1000MHz @ -75mV

800MHz @ -75mV

600MHz @ -75mV

400MHz @ -25mV

200MHz @ 0mV
[Captivate Android Development] Auridran:
The battery dropping right down to 99/98/97/etc % right after unplugging.
[Captivate Android Development] shaolin95:
Nope 3.0 RC after a brand new install so no previous ones there and I have tried different combinations like 1.0 and 1.4 only then also with 1.2 and 1.3...still the same but it seems he found something.
[Captivate Android Development] lpsi2000:
ah, nice to know. I wish these were posted on the first post of these new kernels:p. I was unaware of this and I was blaming JS3 for the issue. I have just confirmed I get the same thing with Paragon's kernel too. I am surprise I have not seen more complaints about this.
[Captivate Android Development] lpsi2000:
I enable pretty much all the ones you have here.
[Captivate Android Development] slaman:
Quandrant score for me is also 1657 with lagfix enabled...

Guess I can't complain - things are snappy for me (other than the occasional LauncherPro redraw)
[Captivate Android Development] neffarious:
Here's a new one: When i flash this Kernel i lose root. I tried in CWM to give it back but no dice. I flash GB's kernel or any other root returns.

Edit: that was on 41 and 43 and previous versions
[Captivate Android Development] existz:
Ok, got bogomips=1393 for 1400, seems with VC sometimes you have to save the settings twice for it to take effect, so if it doesnt set the first time, just save it again.. should have a build up within 30min or so
[Captivate Android Development] Dlev7:
Existz your amazing. I flashed 44 last night, was awesome really smooth but Mobile AP was not working. Then flashed build 45 a little earlier and now Mobile AP is working perfectly (using now)

Im OC'ed to 1.2, keeps going great.

What new features will be in this new build? Worth to flash or should I stick with build 45?
[Captivate Android Development] lrs421:
Mobile AP has been intermittent. It'll be fixed soon :)
[Captivate Android Development] existz:
You can stick with #45 if you want, im just updating some code so a few things calculate correctly with the frequency code, it shouldnt effect anything,

EDIT

retract my previous statement.... there was an error on my part, wasnt from the governor settings, but i got it figured out finally
[Captivate Android Development] shaolin95:
Sweet...will try the new one to see if it gets me to the 19s
[Captivate Android Development] lpsi2000:
LOL, I reported the VC needing the save twice before in this thread but I thought I was alone. Good to see I have friends in the same boat:D
[Captivate Android Development] lpsi2000:
Well I will complain until I get it right:p, I would hate to see my SGS not doing as good or better than shaolin95's SGS.:D LOL
[Captivate Android Development] existz:
Ok... looks like the bogomips issue is coming from the kernel hz=1000, ive tried changing the code back to how it was in 41, tried setting governor settings back to how it was in 41, i can get 1393 bogomips with the 100hz version, but with the 1000hz version it stays 1353 no matter what, its because of the way its calculated.. so as of right now im torn as to what to do.. I can either leave it, or change back to 500hz version, the bogomips showing less isnt going to hurt anything, its just the way it calculates it with 1000hz in place

I had originally thought it was the governor settings ,but after changing it, i flashed the 100hz version and not the XT version, so after flashing the XT it was showing different...
[Captivate Android Development] phoenix2217:
Battery Drain

Hey Guys,

Was wondering if anyone else was having this issue?

Using #44, OC to 1300. Serendipity 5.5

UV like so, using 200, 400, 600, 800, 1000, 1120 and 1300

-100, -100, -75, -100, -100, -100, -50

Rock solid. 1+ hour in NeoCore and normal usage tests show stable.

I've noticed though since I started using this (coming from GB kernel) my battery is draining FAST. 10+% an hour. I tried it with live wallpaper off, data off, made sure wifi was off and still 10+% an hour. Now, granted, i've left it at 1300 OC but I've never had an OC kernel drop this fast. Only thing I can think of is maybe there is a bug where my screen is not going to sleep? Anyone else seeing anything like this? I love how its stable at 1300 as I can't even get GB kernel stable at 1200@-50. Any ideas?
[Captivate Android Development] sicmadek:
I got another problem. Im keep getting a error when turning on wifi. It eventually works after a few minutes but not right away like before. Im not sure which kernel it started with cuz ive flashed them all as soon as you updst.
[Captivate Android Development] Rrryan2:
500Hz was already pretty d#@% snappy. If 1000Hz is causing weirdness I'd say skip it as I can't imagine it provides enough of a benefit to offset. The stability and non-goofiness of this kernel is what I'm most attracted to.
[Captivate Android Development] sixstringsg:
Are you not using the 100 step?
[Captivate Android Development] phoenix2217:
No, because in the voltage app, it says to keep it between 5-7 steps. I didn't think missing the 100 step would be such a battery drain. Could this be it?
[Captivate Android Development] existz:
You probably need to have the 100 step, but i have never tried running without it but not having it could cause it... since at idel it stays down in the 100mhz area anyways, not having it is just going to make it idel at alot higher frequency... also you cant judge battery life within a few min, hours..or even a day, after flashing a kernel give it a couple days to settle in, battery life gets better ...the battery will calibrate itself after time, giving a more accurate battery percentage
[Captivate Android Development] sicmadek:
Well i think it means your phone run at 200mhz at idle instead 100.
[Captivate Android Development] Rrryan2:
I know you've said you tried with data off but it might be worth experimenting:

Several of us (including existz himself IIRC) were having a problem with it switching constantly between 3G and HSPA(3.5G). My speculation is that in my area the HSPA signal is good enough to get but not hold a steady HSPA lock so it's fluctuating constantly, murdering battery. Easy fix is to disable HSPA using SGS Tools.
[Captivate Android Development] phoenix2217:
thx to all who responded. Im gonna try a complete re-flash (just to be sure), keep the 100 step and take out the 600. That should probably work. Will post back. Thanks again!
[Captivate Android Development] phoenix2217:
actually, i've noticed this while testing speed test. The speed test will be downloading fine, freeze for maybe half a second, and start again. during this time, the H will turn to a 3G symbol and them back to H again. Will definitely give this a try too.
[Captivate Android Development] sixstringsg:
The 600 has been known to save a lot of battery. A lot of us have been running 8 steps and been just fine (including eXistZ) so I think you should be fine.
[Captivate Android Development] shaolin95:
hahaha that was funny mate..I needed a good laugh indeed...but I will still find a way to beat you though! :D
[Captivate Android Development] existz:
you will probably want to keep the 600 step, if you check the time_in_state, the amount of time that is spent on each frequency, before the 600 step was added , 800 was the most spent, now that 600 is in, 600 is usually has the most time spent...so keeping it will help with battery life, you will be ok to have 100,200,400,600,800,1000,1200 (then one more for your higher OC)..so say 1300...it wont hurt anything, keeping the lower frequencies is going to save alot more battery life than anything, since the higher frequencies are hardly used
[Captivate Android Development] phoenix2217:
Just wanted to follow the instructions to the T :) Will leave it in and test. Thanks for the help.
[Captivate Android Development] phoenix2217:
just responded to an earlier post. Didn't realize it would be safe. Gonna try it now. Thx again! Amazing kernel!
[Captivate Android Development] AJerman:
Actually, it's the battery controller causing this. It causes less stress and damage on the battery to let charge to full, then drain down a little, then charge again while it sits on the charger for extended periods of time. If you want a 100% full battery, watch it as it charges and unplug it as soon as it gets to 100%, otherwise, it will have started to slowly drain again until it gets to a point where it kicks the charge cycle back in.

I'm fairly certain this logic is built into the battery controller hardware and not the Android software at all (though I can't remember 100%), either way, it's been around longer than 2.2.1.
[Captivate Android Development] existz:
Im going to put up a new XT version, this one will be kernel hz=500 - user hz=150 ... let me know what you guys think over the previous XT-1000/200hz ... Also as for Stability Test showing different mogobips, it changes due to the Kernel HZ, so with 100hz version its going to be different than 500hz or 1000hz version.. it doesnt hurt anything, its just calculated differently. If you guys think I should bring the 1000hz version back I will, just want to try something different.. as the 1000hz version could be overkill
[Captivate Android Development] lpsi2000:
Yeah, I figured you will get a good laugh out of it.
[Captivate Android Development] lpsi2000:
Well I only experienced this with these new kernels in past few weeks.
[Captivate Android Development] AJerman:
Yeah, it'll happen with the stock 2.1 software as well.
[Captivate Android Development] existz:
UPDATE

Build #46

-New XT version (reverted back to 500hz)

--Kernel HZ=500 | User HZ=150

-Optimized governor settings

-Reverted back to 340mb ram (fixes snow on boot)

NOTE You might have to save your VC settings twice the first time you set them. Also, let me know what you all think about the new XT version over the previous XT-1000/200 version
[Captivate Android Development] zerkai:
When I was using the xt version, my screen got pretty warm pretty fast when I was on a 5 minute call. About to flash 46 100 now!
[Captivate Android Development] slaman:
Moderate use:

1400 38497

1300 8981

1200 11311

1000 18971

800 110021

600 27793

400 26542

200 92977

100 7210

(I just enabled 100 a little while back, so probably not accurate)

Looks like the 800 and 200 are most used, but the higher frequencies are still definitely used!
[Captivate Android Development] DunDunDario:
When I set the phone to 1400 in set cpu, the phone freezes. How can I fix this?
[Captivate Android Development] beerbaronstatic:
Not all phones can handle that high of an OC, so the only fix is to not use it I would guess. 1280 seems to be the highest some phones get stuck at
[Captivate Android Development] sixstringsg:
Use Voltage control, not Set CPU
[Captivate Android Development] DunDunDario:
Yeah. I tried 1300 and it freezes in Neocore. I guess I can only do 1200. :(
[Captivate Android Development] lrs421:
Also note, the OP mentions not using set cpu.

Use voltage control and check the mini oclocking guide by Shaolin, in the OP as well.
[Captivate Android Development] DunDunDario:
I tried to but it looks complicated. It couldn't select any overclock with it. :confused:
[Captivate Android Development] DunDunDario:
Ok I'll take a look at the guide. Thanks.
[Captivate Android Development] existz:
SetCPU will cause tons of problems, follow the mini guide in the OP
[Captivate Android Development] lpsi2000:
It is better but I cannot get Linpack over 18.8 @ 1.4Ghz
[Captivate Android Development] existz:
Make sure to only have 1 frequency above 1200 selected, so if you want to have 1400, you would select 100,200,400,600,800,1000,1200,1400 ... also do a level 2 clear in task manager, that way theres no app in the background hogging the cpu, then run it a couple time to get your medium score
[Captivate Android Development] lpsi2000:
I already had the frequency selection configured as you specified above and did

level 2 clear. Level 2 clear only ensure that 18.8 was consistent this time around. No jumping between 17 and 18, consistently at 18.8xx
[Captivate Android Development] slider2828:
Hey Existz whats the major difference between 100mhz kernel and user vs XT 500mhz....

Is 500 just faster? In what way? I know 100mhz saves more battery....

Any light you can shed on the subject?
[Captivate Android Development] existz:
I just can't figure this **** out, after my first run I hit 19.2+ every time..iono, even though there's really no difference between .4mflops, I don't know why you can't break 19..

Not sure if this will help, but heres my full setup..

100,200,400,600,800,1000,1200,1400

150-125-125-100-100-100-75-75

Using ext4 on everything, slower mount options and first 4 tweaks on with logger off
[Captivate Android Development] slider2828:
Yeah I get 19.2 consistently but in the end it fails stability test.... But its nice seeing consistent numbers.... Wow you can underclock like that? Mine would fail on the dime when I hit apply LOL.
[Captivate Android Development] existz:
yea and those are my stable settings, no charge death...been running them since i got the phone monthes ago... :P (well except the 1400 step, i usually cant get it stable, but its the same setup for 1280 stable and 1300 -50mv
[Captivate Android Development] froli13:
Where can I find build #45 XT ?
[Captivate Android Development] lpsi2000:
I cannot OC like the above, I have keep 1.4 at 50 or 25 or 0 nothing more or less. Everything is already ext4 and I will try the slow mounts 4 tweaks.
[Captivate Android Development] existz:
Im going to put up a 1000hz version of 46 in just a min, i want to put both up so people can tell me which is better
[Captivate Android Development] froli13:
Great! Thanks for your hard work!
[Captivate Android Development] existz:
no problem...at first I wasnt going to do a 1000hz version, but ended up deciding to go ahead, that way you guys can run both and let me know if you see any difference
[Captivate Android Development] Loggik:
How much more battery would I lose with the 1000Hz v.s. the 500Hz? Is it very significant?

Edit: I did notice an initial difference in smoothness. But I'm still worried about battery drain... lol I know I sound paranoid ):
[Captivate Android Development] existz:
UPDATE

#46 XT-1000hz Version download added

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

I will only end up keeping one of the XT versions, so speak up and let me know which one you think is best.. There was alot of people downloading the TEST version but no one commented on it, everyone just signed into the chat to get the link and then exited out right away.. if you guys dont let me know which one you would like, i will end up deciding myself...and i will only do 2 versions (100hz and then a XT version)
[Captivate Android Development] existz:
I don't see any difference in terms of battery life between 500/1000.. some users reported a tiny tiny drop, so it may vary, but shouldn't be much if so
[Captivate Android Development] leets4uc3:
what is the difference? ima newb sorry but i have no clue
[Captivate Android Development] Loggik:
Thanks for the reply (: I'll run this for a day or so and report back later. But like I said, I do indeed notice quite a significant increase in smoothness, especially when running multiple applications (I also use ADW Launcher EX, which is running a thousand times smoother). Also, I installed the 1000Hz #45 build. Is there any difference between #45 and #46 that I should update for?
[Captivate Android Development] existz:
Really theres no difference between the 2, just cleaned up some code, but you shouldnt see any difference.. so using #45 for now will be ok
[Captivate Android Development] Loggik:
In basic terms, the 1000Hz will feel faster. As stated before, there may be a minor drop in battery life, if any. But note, there may be no difference in the feel at all. My phone does personally feel snappier, but it all depends on the user and the phone. So that's the difference. I'm not sure on Stability Test scores, though I don't think 500Hz v.s. 1000Hz entitles any stability test differences. Just test out which one you think is better/snappier and report back with your findings (:
[Captivate Android Development] froli13:
Build #41 had kernelhz=500 and userhz=500

Right?
[Captivate Android Development] existz:
No it was kernel hz=500hz and user hz=100hz

On all previous builds it was ..

100hz version (kernel hz=100hz user hz=100hz)

500hz version (kernel hz=500hz user hz=100hz)

but in the latest the 100hz version is the same, but the 500hz version has a higher user hz and added a 1000hz version

100hz version (kernel hz=100hz user hz=100hz)

500hz version (kernel hz=500hz user hz=150hz)

1000hz version (kernel hz=1000hz user hz=200hz)
[Captivate Android Development] beerbaronstatic:
So far I agree that 1000 feels smoother and so far not noticing a battery difference but we'll see
[Captivate Android Development] Grandelama:
Going from #44 1000hz to #46 500hz I couldn't really notice any decrease in smoothness (I'm using GoLauncher). I didn't see any improved smoothness the first time I went from 500 to 1000hz as well. Maybe I'm not sensible enough :D

Too little time to evaluate any influence on battery life
[Captivate Android Development] sjavvaji:
i like the 1000hz...i notice an immediate change in smoothness (more than from 256mhz to 500mhz that speedmod has)
[Captivate Android Development] RonH54:
On 46 now. I can't see much difference in Smoothness from 1000 back down to 500. Using 1300,1200,1000,800,600,400,200,100 with UV of 50,50,50,50,75,75,100,100. Stable so far have run 50 cycles of Stability Test and 10 min of Neocore.
[Captivate Android Development] steph2:
I have #45 seems fast and smooth i love it uses a bit more batt then speedmod kernel but is extremely faster I downloaded build 46 and try it I can only get up 2 1300 stable so far but ofc its a ton of testing but worth it

Thanks
[Captivate Android Development] r.iqbal87:
So i got over 19 and since i have been doubted before, i included a screen shot :-)

sent from tapatalk
[Captivate Android Development] DunDunDario:
is 14.2 a good linpack score for max clock of 1300? I followed the guide and it doesn't appear that anything is overclocked.
[Captivate Android Development] joeshmoe08:
existz my feedback: After testing both 500mhz and 1000mhz variants, I personally feel that you should keep the 1000mhz. The reason is because there is a difference in smoothness that I can tell, and battery drain diff. is not very noticeable. Any ways, if you want battery life you go to 100mhz and stay away from XT. I think XT kernel's should be meant to achieve speed. If you have any questions I will be glad to answer them.

Edit: also haven't been keeping up with the posts, so have you fixed the initial bugs dealing with oc (1400 showing 1350) and bmp indication in stability app?

Edit 2: Forgot to mention that I perfer that you keep 340mb rather than 350mb.
[Captivate Android Development] IStern:
That doesn't seem right, I'm seeing 17.8ish with 1300
[Captivate Android Development] Dani897:
you may get an ocasional low reading but i have gotten 18.2 @1300 14.x is really low. maybe the setting didnt stick.
[Captivate Android Development] DunDunDario:
Can you give me your voltage settings please? I'm very new to this overclocking thing. :o
[Captivate Android Development] ulupinar:
I have also tested with ton of stability test and Quadrant scoring. the phone passes with flying colors. When I OC, the phone has the most difficulty with the google goggles, especially if I quickly keep pushing the buttons, 4 buttons at the bottom. Can you guys test goggle goggles for stability.

Thanks
[Captivate Android Development] DunDunDario:
It seems no matter what setting I put, it doesn't stay overclocked. I can tell because I put it on 1200 and get about 14.1 with linpack. I then put it on 1300 and get around the same score.
[Captivate Android Development] froli13:
You've got my vote for 1000hz as well! Keep up the good work!
[Captivate Android Development] existz:
did you make sure to enable the correct states in VC? and set the max clock
[Captivate Android Development] bclark:
1000! I definitely feel as if it runs smoother than the 500.
[Captivate Android Development] WickedNite:
How about the battery life?
[Captivate Android Development] DunDunDario:
Yes I did set the max clock. As far as enabling the correct states, I'm not sure what you mean. If you mean the - numbers, yeah I try setting different values. Also tried the ones people listed in the thread. But still, nothing. :(
[Captivate Android Development] WickedNite:
What he means is the States option below Voltage Control. You should select what OV state you want, for example, you said 1300 right? It should look like this:

☐ 1400 Mhz ☑ 1300 Mhz

☐ 1200 Mhz ☐ 1120 Mhz

☑ 1000 Mhz ☑ 800 Mhz

☑ 600 Mhz ☑ 400 Mhz

☑ 200 Mhz ☑ 200 Mhz
[Captivate Android Development] DunDunDario:
Ok I flashed the paragon 1300 kernel and set the max clock to 1300 and it worked. So I reflashed the sucker punch kernel and set it to 1300 and it didn't work. So I guess my phone doesnt want to use the sucker punch kernel. Shame... :(
[Captivate Android Development] bclark:
Battery life has been good but after switching from the test 1000, to the 500 xt and now the 1000 again, I really can't give you a proper gauge. Although I do feel the battery on 1000 drains slightly quicker when the screen is on. When off it is the same.
[Captivate Android Development] nybmx:
Did you do what was said above and set the states?
[Captivate Android Development] jjtitus098:
I really can't tell a difference between 500 and 1000. I've decided to run 100 though for better battery life and I still feel like it is smooth...