yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Yuna:
Feels like FPS cap is bigger: can't pass 50FPS mark on quadrant 3d planet test...
[Captivate Android Development] AtoZ0to9:
i can run 100 on everything... but i cant seem to break 1300... random reboots on 1400, but i didnt really try to fix it by changing UV, i just lowered the clock...
[Captivate Android Development] AReynante:
Well my phone must just be bad then lol. This is as high as I can go:

100/200/400/600/800/1000/1200

150/125/ 75/ 75/ 50/ 25 / 0

Any "lower" of a UV and I get random freezes and reboots
[Captivate Android Development] doudou1408:
Sorry for this idiot question but il on mi phone and i must know if this kernel works on i9000 international. Thanks
[Captivate Android Development] existz:
Well, not really, it will work but a few things will be messed up (auto rotation) , however it is built off of i9000 jpx sources, it wouldn't take much to make it fully work, there's a couple things in my source I would need to change to make it work on the i9000, such as hpcall for example, but nothing major...im thinking about releasing it for the i9000 but I want to wait till I get sleep/charge death 100% fixed

Sent from my Captivate
[Captivate Android Development] olo567:
Better than me. I can't go higher than -50 on 100 without sleep freezes. But I can run 1200 and 1300 at -25 stable. Very strange.
[Captivate Android Development] neffarious:
i want 50 too!
[Captivate Android Development] existz:
Soon my friends...soon :P

So far heres the changelog for #50 ..changes can be seen here https://github.com/existz/SuckerPunch-SmR/commits/

Build #50

-Added in stricter no merge semantics for block I/O

-implement aio request batching

-Factor out page reference checks (vmscan.c)

-revert back to BFQ scheduler by default (optimized and tweaked)

-optimized conservative governor

-actually fixed boot clock to 1ghz (should fix random freezes/reboots on boot)

-various VM tweaks adjusted

-Internal SD USB mount now works in recovery

-New Android lowmemorykiller tweak: increases usable ram by 12mb (tweak in recovery)
[Captivate Android Development] pizz0wn3d:
Can't. F*cking. Wait.

I have a question though. I've been using the "autokiller memory optimizer" app, and I was wondering if I should just uninstall it and use the kernel defaults?

Herp Derp Captivate XDA
[Captivate Android Development] neffarious:
+1 and WANT WANT WANT
[Captivate Android Development] existz:
It really depends on user preference. Also you can enable/disable the tweak in CWM.. Before you could use up to about 290MB/339MB RAM, but now it can go up to 304MB/339MB or so. With the tweak off, the settings are, 2560,4096,6144,10240,11264,12288 ..with the lowmemorykiller tweak on, the settings are, 2560,4096,6144,7168,8192,9216 ...which the tweak is actually not as aggressive as with the tweak off, it just makes LMK not kick in so soon...so depending on what settings you use in 'autokiller memory optimizer', its up to you
[Captivate Android Development] doudou1408:
Existz can you confirm me this kernel works on I9000 international ?
[Captivate Android Development] existz:
No it does not, its reoriented for the captivate and a few other things depends on this, so the screen rotation and a few other things will be off.. however it wouldnt be that hard to make it work for the i9000, since its based off of JPX sources, but i would have to change a couple things in the source... ive thought about releasing it for the i9000, but after I get a few bugs worked out, i might do it
[Captivate Android Development] existz:
*UPDATE*

Build #50

-Added in stricter no merge semantics for block I/O

-implement aio request batching

-Factor out page reference checks (vmscan.c)

-revert back to BFQ scheduler by default (optimized and tweaked) delete S_volt_scheduler or it will use CFQ by default

-optimized conservative governor (should give better battery life)

-actually fixed boot clock to 1ghz (should fix random freezes/reboots on boot)

-various VM tweaks adjusted

-Internal SD USB mount now works in recovery

-New Android lowmemorykiller tweak: increases usable ram by 12mb (tweak in recovery)

NOTE As with any kernel/rom, give it a couple full charge/discharges before commenting on battery...sometimes after a flash, the battery calibration can be off, so after giving it a few full charge/discharges, the battery will recalibrate itself.
[Captivate Android Development] AReynante:
Flashing 50 now. :)

Why is it that whenever I look for the volt_scheduler to delete, its never there? Is it because I never save as boot settings? (I am assuming so now that I think about it)

Edit: Should I leave the scheduler on BFQ? I have always used noop. I don't know the difference though.
[Captivate Android Development] existz:
Yea if you dont save as boot settings it will not write the file. As for the scheduler, originally noop was better for ssd in a sense, but hardcore has tweaked the scheduler settings so that they work better, i recommend using bfq for now, i might end up reverting back to cfq in a future build, i dont know yet since im still tweaking some of the scheduler settings
[Captivate Android Development] AReynante:
Alright, well thank you for that :)
[Captivate Android Development] Auridran:
Well, in #50 I'm unable to get rid of the performance bug. Turning down the media volume does not fix it like in #49.
[Captivate Android Development] froli13:
Every time my battery is getting correctly calibrated you come up with a newer/better version... And of course I need to flash it! :P
[Captivate Android Development] airbillion:
Same here. Cant break 50 fps.
[Captivate Android Development] existz:
i will try a test version and see if the refresh rate is the issue ...also working on something else, once i finish this up and test it i will release it..hopefully later tonite/tomorrow
[Captivate Android Development] elghouchd:
Why set the refresh rate back to 60?
[Captivate Android Development] sjavvaji:
maybe you can leave it for the xt version...it definitely helps
[Captivate Android Development] froli13:
Just got 64.6 in Neocore, 1700 someting in Quadrant and 16.5 in Linpack with #50 100hz

Edit: 1200 OC
[Captivate Android Development] existz:
Ill make a test version for you and airbillion, ill drop the refresh rate back down to see if it has any affect, I don't see any of the other changes I've made causing a drop in performance...which I know nothing I done in #50 caused it since it started in #49 correct?

I just can't figure it out since its only happening to a few people, there might be another factor in there somewhere between you and airbillion...

Sent from my Captivate
[Captivate Android Development] existz:
I fixed my post, what I should have said was... ill try a test version for them just to see if that is the issue, cause yea it does help, if its only happening to them and no one else then something else could be the issue

Sorry for that post, im doing a 100 different things, got to much **** going on lol..

Sent from my Captivate
[Captivate Android Development] Auridran:
I'm not sure what it could be. Yes, it started happening at #49. I tried flashing a JS3-based ROM just to make sure it wasn't my ROM causing the issues, and I get even lower performance in FPse and Neocore now.
[Captivate Android Development] airbillion:
Thanks. Im not sure what the issue is. I just converted to the rfs file system before the 49 and 50 updates, maybe that is the problem. I'll convert back to ext4 right now and see if that changes anything. Let you know in a few.
[Captivate Android Development] Auridran:
Already tried many different filesystems with no change.
[Captivate Android Development] existz:
I personally think its from the refresh rate, most of the changes I've made are scheduler, VM and governor tweaks, they would be causing it for everyone if that was the problem... I guess since all gpu's are different some just don't like the higher refresh rate..but I don't understand why changing the volume fixed it before..its something weird...

Sent from my Captivate
[Captivate Android Development] Auridran:
Here's something even weirder for you: After flashing back to my CWM backup, I'm now at full FPS again.
[Captivate Android Development] b0wz:
No issues found here, running BFQ @ 1300 mhz....neocore says 64.6, linpack says 17.902, and quadrant (useless I know) says 1838

Hardware varies big time, my phone for the life of me, does not like the Firebird kernels at all, the wife's....just the opposite.....both bought at the same time
[Captivate Android Development] existz:
Well its not the refresh rate then, something else is def causing it, i cannot think of what in the hell it is...very strange..but ill look into a few things and see if i see anything.. so for now ill leave the refresh rate the way it is.. but im glad you got it working..
[Captivate Android Development] airbillion:
Changed back to ext4 and still have the low fps. No change for me either. I wonder what the issue is? I have great performance otherwise, just wondering why it would change so much.

Edit: neocore 48.6 @ oc 1200

Not that benchmarks like quadrant or neocore mean that much, but I use them to gauge performance between different kernel flashes. Anyway, keep up the great work, this is the best kernel by far for battery and performance. Thanks!
[Captivate Android Development] opcow:
I had the 50 fps cap on #49 and then flashed #48 and it was gone then flashed #49 and it was still gone. Not having it on #50 either. The only thing I did besides flashing back to #48 was I temporarily (didn't save it to init.d) set my max clock from 1300 to 1200.
[Captivate Android Development] shaolin95:
The performance issue is with 3D mainly so run Nenamark for example.
[Captivate Android Development] yummybar:
Im having the same problem, i was on Speedmod and got 64.5 neocore, switched to #50-1000 and #50-100; and neocore dropped to 47.8
[Captivate Android Development] AReynante:
I don't know if what my scores are matters, but:

I'm on #50--1000, and I get a 64.3 neocore
[Captivate Android Development] RonH54:
My Neocore scores have went like this for what it is worth. I was getting around 55 FPS with Build 48. Then with 49 it dropped to 48 FPS now on Ver. 50 I am getting 64 Fps. I am using 1200 as my Highest State
[Captivate Android Development] johan8:
Here is Captivate section,

of course everything are for Captivate i897 only.

If you want such powerful kernel, go for Super Optimized Kernel by laststufo in i9000 section.

It also contain VoodooSND4, full tweak, .....

OC up to 1.6Ghz..... and VSF.....etc.
[Captivate Android Development] johan8:
Battery life is so good !

Actually I'm not a heavy user.

Most of the time wifi and 3G packet data are off if not in use.
[Captivate Android Development] IStern:
Hm...with build #50 I'm seeing "cell network death" while connected via usb. Happened twice today. No signal, had to reboot to get it back.
[Captivate Android Development] Killemalll:
I get 49.2fps in Nenamark at 1200Mhz with Build #50.
[Captivate Android Development] pizz0wn3d:
48.6 everytime on Neocore =/

last time I ran that benchmark (build #48), I was consistently capping out at 55.X fps.

I wouldn't have noticed any performance decreases though had I not ran the benchmark.

Also, I'm oc to 1300MHz

Herp Derp Captivate XDA
[Captivate Android Development] airbillion:
That is my score every time too. Im on 1200 oc.
[Captivate Android Development] Auridran:
Unless you're running demanding 3D apps, you probably wouldn't. There is an enormous increase for PSX emulation between the kernel having performance issues (Neocore ~48) compared to it running fine (Neocore ~64). I ran Neocore after I noticed my PSX emulation slowed down by a large margin.
[Captivate Android Development] ryude:
Getting 65+ fps here.
[Captivate Android Development] Yuna:
Some crazy **** going out there:

On first couple of boots, with default Oc (we have it?) i got 40+ FPS on 2d quadrant and max 50 on planet test (3d)

after some time, and oc to 1120 i get not 19-20 fps in 2d test and 65 fps in planet test...

also i had froze at playing angry birds @ 1200...

NEVER had any lockouts on setiron kernel at this freq...

looks like some things are changin...

kernel maker, look at changes... maybe you have changed smth and now memory adresses are changed too - and so broken some things...

e.g read why Microsoft does very extensive testing to patches - there is a holes in kernel and bugs...
[Captivate Android Development] bamonkey:
im so freakin' happy this is back to working on Darky's rom now that im trying out that rom again. so #50 is here and i gotta say there are some firsts...so far lol. by god my captivate seems to be running stable at 1.3ghz for the first time...EVER! and this has been a constant trail and effort with a ton of different settings and MAYBE my cappy is finally just getting broken in where its starting to accept it but either way major kudos. bfq is back and im not sure if i see any difference *shrug*. linpack around 18 and neocore breaks the framerate cap. so really.. best.. version... EVER for me so far.

in case anyone is wondering my captivate is pretty fickle so here are my OC/UV ..all steps from 100 to 1300 checked: 50,50,75,75,75,75,75,75,50.

yes for some reason i have to keep the low end voltage up a bit higher than most and the high end of my clock at a certain 'unknown' voltage' but -50 seems to be the only one that keeps 1300 stable on this kernel.
[Captivate Android Development] airbillion:
I don't know what changed, but now out of the blue, I am hitting 64 fps in neocore and 65 on the planets on quadrant. I don't know what changed, I havent changed anything. Only thing I can think of, is I just updated the voodoo control app, but that should have nothing to do with rom performance.

Now I'm getting the best performance I have ever achieved! Excellent job existz I'm really impressed.

Edit: Just rebooted and now im capped again at 50 fps again. What the hell? I wonder what is going on?

Edit 2: reboot, test 50 fps...screen off then back on test again 65 fps on both. I dont know what the issue could be.

Thanks!
[Captivate Android Development] xdahgary:
Me too. I got 65 fps on neocore. I wont reset.
[Captivate Android Development] ridethelight:
I always make sure to do a level 2 memory clear before any testing, maybe that has a factor in peoples drastically different results? Interesting that reboots effect it so much though, my tests on #50 OC'd to 1200 were 64.5 on neocore and 16.6 on linpack

Since flashing to #50 ive also been getting quite a bit better reception/data services speed in my house, could this be the kernel or maybe ATT finally did something for once.
[Captivate Android Development] johan8:
What is your tweak OC scheduling settings ?

Mine OC1.3, BFQ,

always got 65~67fps in Quadrant planet test.
[Captivate Android Development] airbillion:
Currently getting 65 on planet and neocore, but with same settings I have had the 50 fps cap for some reason.

1200 oc bfq

50 50 75 100 100 100 100: 1200 to 100
[Captivate Android Development] johan8:
This result seems ok to me.

And I never do memory clear and kill task, it is pointless in current android system.
[Captivate Android Development] xbeamelite:
I'm on #49, first time first time i tried neocore last week it scored 48fps. Just retried and hit 64.5. Didnt do any changes. I'm getting amazing battery life finally #49(30hrs with over 2 hours screen time, half hour of gps and over 2 hrs talking).

Does #50 actually feel faster? Right now I'm Oc'd at 1200. its quick but i thought #48 was quicker (but not as great batt life).
[Captivate Android Development] gibson3659:
I'm getting 64.5 on Neocore with no oc.
[Captivate Android Development] gibson3659:
Hey eXistZ,

I am able to boot/reboot into #50 at least 50% of the time with no freezes. I have rebooted 3-4 times to test it, so I should finally be able to make this my daily kernel. It must have been the boot frequency fix. I'll let you know if anything changes.

Thanks for the great work.
[Captivate Android Development] Smallsmx3:
I've been using hardcores kernel for quite some time. I have been thinking about trying this one out.....I know its based off k12 p but it looks like its been updated along with hardcores latest upgrades....so is it saf to say its based off k13 b?
[Captivate Android Development] existz:
It has most of the features as his latest k13b, plus some.. the last full patch that I used was k12p, but added in most of the new speedmod features

Sent from my Captivate
[Captivate Android Development] Smallsmx3:
All I have to say is so far so good......undervolting really helps alot....only lose about a % an hour while in idle which is what I've been looking for
[Captivate Android Development] RuizGT:
Ugh, charge death. Zeroed out the voltage setting, same thing.
[Captivate Android Development] neffarious:
I am having the same 48.x FPS across the benchmarks on 3d. I flashed back to 49 and 64.x. I am using the 100hz version on both.
[Captivate Android Development] RonH54:
It is wild how each phone can be different. I had just the opposite happen on Fps. 48.x on #49 build, 64.x with #50. I also am using 100hz version with 1200 as highest OC. I am on Dakry 9.2 ROM so ROMs I guess does have some effect I would think.
[Captivate Android Development] neffarious:
valid point- Dipity 5.8 1300 OC
[Captivate Android Development] neffarious:
kk odd i just ran it again at 1400 and got 48.5 on 49. very strange.
[Captivate Android Development] neffarious:
Reboot, set to 1400 same results, set to 1300 and same thing. So very strange. going to reflash 50. Same results 48.5
[Captivate Android Development] r.iqbal87:
I dunno if this is case specific, but is it possible that implementing the low memory feature is adversely affecting battery life? And I have already deemed that battery calibration is not the cause. TIA.

Btw. Im using

#50 build, ugl2, (-100, -100, -75, -50, -25 for 100, 200, 400, 600, 800, 1400 respectively)

Serendipity 5.8.
[Captivate Android Development] nybmx:
Running the same set up as you and getting the same results on #50.
[Captivate Android Development] wonner:
#50 100hz OC'd to 1200mhz

Neocore - 64.8 FPS

Nenamark - 50.1 FPS
[Captivate Android Development] ronpinoy253:
Charging Death #50

Starting to get charging death when charging phone to full.

-Charging phone to full and receive full charge message

-Unplugging charger, phone reads 98%,

-Plug in charger again, phone charges.

-Phone reads full charge message again...frozen.

-Repeat steps if not frozen...will eventually freeze after a couple times.

Batch 1008

Supernova ROM 2.1

Suckerpunch 100hz #50
[Captivate Android Development] evrionis:
which scheduler to use

Can someone suggest which scheduler to sue? Is there any difference between them. I have been using this kernel for a while and really like it.
[Captivate Android Development] froli13:
Read the OP and the FAQ It is normal, so you don't need to charge 20 times after it says it's at 100% ...

No wonder why it would eventually freezes...
[Captivate Android Development] froli13:
I suggest the one that the dev of the kernel suggest. In this case: BFQ.

If you wanna try another one, try noop.
[Captivate Android Development] slider2828:
I like noop, its been a little more stable for me than bfq. Build #50 on batch 1001
[Captivate Android Development] johan8:
Mine is also batch 1008,

now using suckerpunch 100hz #50,

but no COD or frozen so far on my i897 with i9000 stock rom.

After full charged message show up, unplug then battery read 98%

Charge again until full charge message show up again,

unplug, battery kept in 100% finally.

Don't know it is celebrated or not, need some more days to test.

But now GPS has very bad reception, can't find any sat.
[Captivate Android Development] Grandelama:
1000hz #50 is working very well for me. I dont' use banchmark nor emulators, though.

I'm slightly increasing my UV and it seems more stable, no charges of death so far. I will see how far I can go.
[Captivate Android Development] johan8:
I've deleted OC/UV settings then reboot with default clock settings,

neocore score was below 50fps.

But after a hour of (normal) using, neocore run at 64.5fps again.
[Captivate Android Development] xdahgary:
I think I know what the problem is. You've set the kernel to boot up at 1ghz. However, even applying new settings thru voltage control the affect doesn't apply right away. I rebooted the phone. Setup voltage control for 1.2ghz overclock. Apply for now. Ran Linpack and got 14 @ 1ghz. 15 minutes later ran Linpack and got 16 @1.2ghz.
[Captivate Android Development] ryude:
Been getting a lot of boot freezes when using bfq scheduler, switching to noop or deadline fixed it or at least seems that way.
[Captivate Android Development] johan8:
I have tried CFQ and BFQ but no problem on my phone.

Just that CFQ gives better benchmarks maybe better performance,

BFQ let GPS works better.
[Captivate Android Development] coderunner:
Is the regular one 500hz or 100hz?
[Captivate Android Development] existz:
Its 100hz, there is no 500hz now, only 100hz and 1000hz
[Captivate Android Development] existz:
I've updated my source some, im now using oc/uv code from laststufo, all voltages show in VC now, you have 2 new files in /sys/devices/system/cpu/cpu0/cpufreq/....AC_timing_registers_data and AC_timing_registers_row... as well as frequency_voltage_table ... hopefully this fixes charge death. Also the 1400mhz frequency is overvolted to 1500mV (the rest are the same as before), but you will more than likely have to reset your UV settings for all frequencies, no promises you wont.. Also some vm tweaks have been added ...plus alot of over things (full changelog to come soon) ..it might be a day or two before a release, still haven't got it to testers yet ...so if you don't hear from me for a day or two, this is why. ..
[Captivate Android Development] cumanzor:
Hi existz,

What changed between 49 and 50? 50 seems to be completely unstable for me, even at stock settings.
[Captivate Android Development] elghouchd:
I'm having some trouble, everytime I boot my phone, it freezes, and I'm pretty sure it's cause of overclocking.. I'm on build 50. Any suggestions? I hope I won't have to restore my phone...
[Captivate Android Development] existz:
Changelog on the first page....whats not stable? i need more info
[Captivate Android Development] cumanzor:
Thanks. Phone just crashes after random activities, like browsing the web or using the camera. Since it's random I cannot really reproduce it easily. I went back to 49 and it works fine.
[Captivate Android Development] johan8:
Hi existz,

I've downloaded your #51-test1.

Will report here if I find anything.
[Captivate Android Development] sjavvaji:
add the k13c source that was just released and make this bliss
[Captivate Android Development] Tweak4fun:
Same thing, Same batch (1008), #50, SuperNova 2.1.

I even saw it while recalibrating the battery. I charged all night with phone on, it read full the next morning. I unplugged it, powered off, plugged it in, the charging indicator came on and froze. Battery pull, reinstall, plugged it back in....same thing it froze. Unplugged, booted and all is well so far.

I have never experienced CD (that I know of) while the phone was charging while the phone was on. I have used MANY roms & kernels, LOVING Suckerpunch though!

Thanks for your work! Thank you Hardcore as well!
[Captivate Android Development] elghouchd:
Somebody please help me, i really need to use my phone today.Thanks
[Captivate Android Development] indomikey:
can you get to recovery? flash update.zip or different kernel that doesn't OC/UV
[Captivate Android Development] aalh:
set your phone to not overclock or uv

change the scheduler

DONT use setcpu

use voltage control app
[Captivate Android Development] existz:
already done :P
[Captivate Android Development] sicmadek:
Well last night my started freezing bad when trying to use google navigation. First time ive ever had a freezing problem.
[Captivate Android Development] elghouchd:
I cant use my phone beacuse it freezes 2 seconds after it boots up.
[Captivate Android Development] ThisWasATriumph:
I'd love an extra warm version as my launch phone is still quite blue with the warm setting turned on.