yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] LNJ:
Mine is:

0

75

100

100

100

100

100

150

125

150

And that for all frequencies stable at 1.4Ghz.
[Captivate Android Development] shaolin95:
Sorry mate but that screenshots says nothing...remember that SuckerPunch has unlocked the FPS while Paragon leaves the FPS locked at 56 or so. ;)

Compare something like Nenamark for a fair comparison.
[Captivate Android Development] Dungeon47:
Oh, wow. Good to know. If it matters, I've never gotten above 56FPS on any kernel, except this one. I'll try the other bench and post. What are you getting with it?
[Captivate Android Development] shaolin95:
I believe this is the only kernel that has unlocked the FPS at least for Captivate. I only use Paragon and this one as are the only ones that go into high OCes :D

Paragon maxes out at 55.7 or so which is what I was getting with SuckerPunch prior to the FPS unlock.

A test like Nenamark is better because it never goes over 56..closest I have gotten is 54 with Paragon so far.

I have edited the overclocking guide to NOTE that particular case with FPS. I need to touch up that guide for sure. :-)
[Captivate Android Development] xdahgary:
So why lock down the FPS? Any insights?:confused:
[Captivate Android Development] shaolin95:
May I ask why the rolleyes?
[Captivate Android Development] pizz0wn3d:
It has something to do with the screen refresh rate being increased on this kernel. I believe he set it to 75hz. don't remember for though, but I remember seeing it in the OP.

Herp derp Captivate XDA app.
[Captivate Android Development] pizz0wn3d:
Herp derp Captivate XDA app.
[Captivate Android Development] Dungeon47:
48.6 at 1ghz on Nenamark. 49.2 at 1.4ghz.

Sent from my Android using the power of Greyskull.
[Captivate Android Development] xdahgary:
Wrong eyes...lol. Fixed it.
[Captivate Android Development] existz:
So far the only down side to upping the refresh rate is that sometimes after a flash it will only give like 4xfps...but you can just lock the screen and then unlock it and its back to 60+fps...ive got a few other things im doing on #56 right now, once i finish those ill try a few different things with the refresh rate to fix this...but for now, if you get lower than normal fps, just lock the screen and then unlock it...seems you only have to do this once after a flash..sometimes it does it, sometimes it dont..
[Captivate Android Development] shaolin95:
haha now worries. I dont think our screens can show anything over 60 fps or so or at least most people argue that we cannot see anything over that (I do not support that though) so they thought it was cool to cap it I guess.

I dislike the idea even though some people, in the computer world, argue that it is best to lock the FPS at 60fps than to have it going up to 100fps then suddenly back to 60 or 50 as it makes for an overall smoother experience...

At the end of the day my honest to God answer is...i have no idea why Samsung did it :D
[Captivate Android Development] nappent:
Is there any way to edit the "Suckerpunch" boot screen? I would like to add a little to it if that's ok. Let me know. Thanks!
[Captivate Android Development] existz:
The boot logo is actually part of the kernel source and has to be compiled with the kernel...but im open to suggestions...if you make up something just send me a pm with a link or something
[Captivate Android Development] xreflection:
Could we get the image you used and edit it?
[Captivate Android Development] existz:
Its on the first page...3rd post I think.. but only way to add it is to compile it, theres a few steps to it ..but if you all make one up, send it to me and I might use it
[Captivate Android Development] apparition:
Anyone have an idea how battery life compares on superpunch vs suckerpunch-voodoo?

Sent from my SGH-i896
[Captivate Android Development] existz:
Its about the same ...I get roughly the same amount with each one..I use alot of the same configs with sp-voodoo as I do with sp... basically the only differences are the color/sharpness tweaks, brightness tweak, lowmemkill settings, OC of course, then a few other random things (VM tweaks, a few scheduler tweaks..etc) but the things that really impact battery life are the same (governor settings, config options, kernel hz=100..etc..etc)
[Captivate Android Development] nappent:
Here is a couple that I've been working on. I do not call myself a graphics designer so I'm sorry if I don't meet some of your standard. I use Paint.net to working on these images so I can get you the PDN files if needed for some tweeking.

This one has a solid black background

This one has a textured background. Kind of a carbon fiber feel to it.

http://samsung-captivate.weebly.com/1/post/2011/03/new-suckerpunch-boot-logos.html
[Captivate Android Development] shaolin95:
That looks sweet dude
[Captivate Android Development] nappent:
Thank you!
[Captivate Android Development] elghouchd:
So after skimming this http://bit.ly/dC8k60 should build 55 increase the responsiveness of the phone?
[Captivate Android Development] existz:
Yes.....should help while cpu is under load
[Captivate Android Development] apparition:
Those look great. However, I do like the simple loading screen the way it is. I don't think it needs to say "loading ..." either. But that's just me.
[Captivate Android Development] elghouchd:
Yeah I dont think it needs to say "Loading" but the rest of it is nice! I like the textured one :)
[Captivate Android Development] sjavvaji:
agree with others...remove the loading...both are so good so i can't pick :D...propably the second one though
[Captivate Android Development] xreflection:
I think if you took the loading out and removed the background android, the textured one would be great.
[Captivate Android Development] nappent:
I too like the simple look of the current one, but thought maybe a little more would be nice. Secondly, it has always bugged me that no one mentions "Android" on any boot screen. Being a proud android owner, I like to make it clear what we are running but not over over the top. Anyway, this is just a idea so I'm cool with the current one or a different one.

Here is a version with out the "loading".
[Captivate Android Development] froli13:
I think if you remove the higher bugdroid it would be perfect!
[Captivate Android Development] xreflection:
Get rid of the android in the back, lol. Something is wrong it. It's like missing an arm or something.
[Captivate Android Development] nappent:
I got a copy of that up. You can find it at http://samsung-captivate.weebly.com/1/post/2011/03/new-suckerpunch-boot-logos.html

Or direct link to image: http://samsung-captivate.weebly.com/uploads/4/0/8/5/4085984/6932251_orig.jpg

I figure the images are taking up to much room in this thread.
[Captivate Android Development] elghouchd:
Love the last pic!
[Captivate Android Development] sjavvaji:
existz....new boot logo time
[Captivate Android Development] existz:
I like the concept... personally I like a clean, simple, minimal boot screen.. but I do like the textured background, might work with it some... but its gave me a few ideas, ill post some concepts afterwhile
[Captivate Android Development] opcow:
Nice logos. Personally, I like this one, but I'm a sexist pig:
[Captivate Android Development] shoman94:
ooooo... me likey
[Captivate Android Development] zerkai:
I personally prefer hardcore's Samsung i897 logo while keeping the Suckerpunch name in the 'About' menu. lol ;)

Anyways, #53 100hz has been smoothest for me.
[Captivate Android Development] existz:
Hopefully I will have #56 up in the next day or so... I will have a TEST version up later tonite, updated BFQ scheduler to v2, MORE INFO , cfq is still faster so it will stay default, but for those of you who use BFQ, it should give better results..and I also done some ext4 optimizations, which are giving faster Read/Write times according to file system test in 'Benchmark'... most gain is faster read time ...
[Captivate Android Development] froli13:
I'll wait for a while before flashing and new kernel. #55 is awesome so far! Looking forward the new kernel logo though ;)

Concerning this, I personally dislike the Speedmod boot logo option since I own a SGH-I896 :P
[Captivate Android Development] LNJ:
Would we have to disable lagfix before flashing to #56?
[Captivate Android Development] existz:
Nope, its fine to leave lagfix and/or tweaks enabled
[Captivate Android Development] LNJ:
Thanks. I shall wait patiently for the new update.
[Captivate Android Development] neffarious:
55 hard freezes for me all over the place. Soft reboots too :-( back to 54 @ 1400 :-)

Sent
[Captivate Android Development] johan8:
Great ! Like to see improvements !

In i9000 section, I see some of these,

do you think it is useful to add to your kernel in the future?

* based on bilboa1's git repo (voodoo included) - thanks !

* fixed some locks & overflows with i/o operations, GUI should be more smooth under write & heavy memory use conditions, more stability

* CPU scheduler branch prediction optimizations

* faster deactivation & reclaim of invalidated pages - (probably) memory savings

* OOM (out of memory killer) optimizations (should cleverly keep your phone running even when memory is filling up)

* optimize cacheflushs for user apps - should speed up especially emulators

* kernel compiled with optimized CFLAGS
[Captivate Android Development] aKeio:
Is my voltage control broken?

I've managed -125 from 1200 all the way down, and StabilityTest is telling me I"m running at 1.2! Best UV results in a while!

*EDIT* Looking to be stable at.. -125 -125 -125 -125 -100 -150 -150 -150 w/ CFQ!
[Captivate Android Development] xdahgary:
Try testing on apps. Camera, music player, and 3d gallery. I get random freezes when undervolted too much.
[Captivate Android Development] apparition:
Does anyone know anything about not being able to change to custom fonts in the settings menu because of the lagfix built into this kernel?

source
[Captivate Android Development] xreflection:
Slowly working my way toward my max UV settings..

Currently at

1200 -75

1000 -75

800 -75

600 -75

400 -75

200 -125

100 -150

This is a long painful process, I must say. It also kills the battery so fast running all the stability stuff, lol.
[Captivate Android Development] b0wz:
Is the script update still needed for SP # 55 ? (not really needed, but recommended)
[Captivate Android Development] existz:
Yes, the mem timing script is still needed if you want optimal memory performance...but use the link in the OP, the location has changed
[Captivate Android Development] b0wz:
Sweet, thanks for the quick reply....will add it in. now if my signature would auto update everytime I make changes.........:D
[Captivate Android Development] aalh:
I am using 1.4

I see bogomips in top left

I dont see clock speed anywhere
[Captivate Android Development] existz:
Correct, it shows bogomips ...bogomips is not the same as mhz, its a calculation based on a few things, ..if you notice, the kernel hz value will effect the calculation, its not the same when using 100hz version or 1000hz version..
[Captivate Android Development] b0wz:
Quick question to the group, how many states (freq.s) are recommened, or can you just run them all? I see some people running 5, some running 8, and right now I am only running 7 (100,200,400,600,800,1000,1200). Is there a prefered number?
[Captivate Android Development] existz:
There's really not a preferred number, but you do not want to many states enabled, cause it can actually make things slower, you don't want to many states for the cpu to have to scale... I always try to keep it every 200mhz ...

For example, when OCing to 1400, I would have ..

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

..But if the cpu has to scale to many frequencies that are close together, it can slow things down..
[Captivate Android Development] b0wz:
Sounds good, my phone is real quick at 1200, and it seems to run 1400 just fine (great benchmarks), but for everyday normal use, I really can't tell the differance between the 2, so 1200 with 7 clicks it is. 1400 is just a click click away (voltage control) if I really need to show off ;) tnx
[Captivate Android Development] GGXtreme:
After several days of battery drain and sleep death, my phone is finally acting normal. 14 hours on, 2 and a half hours of screen time (at several brightnesses between 26 and 100), still have 60% battery left :D Peformance is fantastic (especially with emulators).
[Captivate Android Development] xiLLeNtz:
can i ask what your config is? man, if i could do this then that would be PERFECT
[Captivate Android Development] pizz0wn3d:
It's called leaving your phone on standby for 11, then racking up the display time in the last 3 :P

or maybe I'm just a ridiculously heavy user, because I can only get 7-9 hours on andromeda. 8-10 on precision. I'll be testing out Dragon tomorrow. I've never gotten more than 10 hours of battery life out of my phone.

=/

Herp Derp Captivate XDA app.
[Captivate Android Development] GGXtreme:
Enabled States: 100,200,400,600,1000 (no oc/uv)

No SetCPU

Screen Brightness: 26/100 in UI (75/100 if outdoors), 75/100 in games and videos (100/100 if outdoors)

Data disabled (I go over 200MB way too easily >_<), Bluetooth disabled, GPS disabled (enabled rarely, but it's not a common thing for me), Wifi enabled occasionally

KeepTheLightsOn and Blinky BLN

Running LauncherPro (4 full homescreens, enabled: animations, rotation, 3D app drawer; no updating widgets [only a Widgetsoid switcher, PowerAMP large widget, Google Search, DigiClock and Gauge Battery])

Haptic feedback disabled (except for lockscreen)

All recommended tweaks + CIFS and VPN support enabled in recovery

Warm screen color

Recommended ext4 lagfix (ext4+ext4nj, no ext2 loop mounts)

Watching up to 2 hours of HD video a day

Playing N64/GBA emulators up to 3 hours a day

Using wifi for up to an hour a day

Between 10 and 20 texts a day

Less than 5 calls a day

Learning Japanese up to 2 hours a day
[Captivate Android Development] ccdoggy:
I LOVE this kernel, but am wondering if there is any chance to get a version which supports the fugu tweaks?

to be honest I have no clue what they are or what they do but this kernel is unusable if the ROM has them enabled. The rom becomes uber smooth with the tweaks and I, like some others, would really like to still be able to get your oc/uv and battery saving kernel in it to use.

Thanks again.
[Captivate Android Development] existz:
To be honest, I don't know why its not compatible...I seen a few other kernels that doesn't work with it either, but I have no clue where to even start looking...I would have to start completely over from a stock source to find out what it is (which I might do when I get time).. so if someone can shine a light on what's causing the incompatiblity...

But if you want to use my kernel, you "should" just be able to replace /system/bin/app_process and /system/bin/system_server with stock versions..that's all fugutweaks are, is those files from 2.3.3 I believe...so if your using a js5 build, grab those 2 files from either a js5 rom that doesn't use fugutweaks or from a stock js5 rom..etc..etc ..
[Captivate Android Development] shoman94:
What kernel has it enabled? I don't think it's kernel related.
[Captivate Android Development] shoman94:
See this: http://darky.ficeto.com/community/i...your-phone-much-smoother-without-lagfix.1504/

EDIT: And here: http://xdaforums.com/showthread.php?t=981125
[Captivate Android Development] existz:
Some ROMS have it added, but seems SP doesn't work when its added, its just 2 files added from 2.3.3 I believe, or 2.3.1 or some ****... but both SP kernels don't work with it when others do...which I seen in i9000 thread for fugutweaks im not the only one, there's a few others...but my KB1 kernel works fine .. I have no clue what's causing SP not to work, or even know where to begin.. Which those 2 files can be replaced with the stock version of the files and SP will work.. When I get time I might try to start from a stock source and work my way up, trying to find what's causing it
[Captivate Android Development] existz:
Thanks, but still not seeing anything specific as to why it wont work.. it mentions file system on /system, but that's not the case..as sp-voodoo and my kb1 kernel use the exact same...so if it was due to lagfix, it wouldn't work on KB1 either... so there's something else causing it.. which my KB1 kernel is kind of a mix between SP and SP-Voodoo, so im clueless...
[Captivate Android Development] shoman94:
According to the OP it shouldn't effect the kernel.... has someone tried it with SP#55 and it messed it up? A bunch of people say speedmod k13c is fine... nobody posted with either SP kernel.
[Captivate Android Development] existz:
Yea there's been a few reports about both SP kernels not working with fugutweaks...had some reports on irc
[Captivate Android Development] bitnerd:
Someone mentioned that this is the problem that cropped up in the latest Serendipity version. When I run SP55 then my whoke desktop is just gone. If I run Paragon and the one it came with then things work fine. If you have something you would like me to test on it I can but I'm heading offline for a little while now
[Captivate Android Development] ccdoggy:
well I just tried your suggestion. backed up those 2 files and then flashed #55 again. tried to copy in recovery with adb but it would not give me permissions.

so i thought if i booted it i might be able to get permission. but then it booted just fine and have had ZERO problems with it. oc/uv works great.

before i flashed the kernel I did restore all my settings and what not to the device and rebooted twice if that counts for anything.
[Captivate Android Development] existz:
I've got a few ideas ill try...since Speedmod and my KB1 kernel work, it shouldn't leave much that's not in those but is in SP and SP-Voodoo.. so hopefully it wont take long to narrow down the issue ..but I still have no clue where to start, so..hopefully its a quick find
[Captivate Android Development] shoman94:
I hope so cause I love this Kernel and want the tweaks...lol
[Captivate Android Development] bitnerd:
Same here. It's the first kernel I jump to when I do an update
[Captivate Android Development] froli13:
I just include it in every ROM/updates I download before flashing it. :cool:
[Captivate Android Development] existz:
Think I just figured out whats messing up SP with Fugutweaks...will have an update soon
[Captivate Android Development] MaximumPotential:
Hey Existz, What kernel do you prefer for better battery life and stability with UV. I have been using SP-Voodoo for a while now and it is very consistent but i haven't tried SP in a while. Are there major differences between Voodoo lag fix and just enabling lag fix on SP? Also will SP voodoo get Fugu tweaks working or just SP? Thanks in advance sir.
[Captivate Android Development] existz:
They both usually give me about the same battery life, so I really cant recommend one over the other, as its about the same for me.. Theres really not that much difference between them, just comes down to user preference..(voodoo color..min brightness..etc.). and yes, sp-voodoo will get fugutweaks compatible
[Captivate Android Development] MaximumPotential:
Thanks for the quick response. I think I will try SP 55 then because I feel like it would be easier flashing new ROM's without going to stock if I didn't have Voodoo.
[Captivate Android Development] existz:
*UPDATE*

SuckerPunch #56

-now works with FuguTweaks

-updated BFQ to v2
[Captivate Android Development] froli13:
existz, you're the man!! Downloading now!

Thanks again for you hard work. Will donate soon!
[Captivate Android Development] existz:
Let me know how it goes, I tested it personally and just had 1 other person test and it worked fine, but just to triple check, let me know if it works
[Captivate Android Development] iXNyNe:
What are these fugu tweaks?

Edit

Found these, maybe link changelog item to something like this to alleviate questions from people who don't search and read for themselves (me)
[Captivate Android Development] existz:
It replaces /system/bin/app_process and system_server with files from 2.3.3, making things smoother/quicker... supercurio states it gives the responsive of gingerbread
[Captivate Android Development] froli13:
Working fine for me too. Everything is so sooth! Thanks again!
[Captivate Android Development] existz:
awesome, appreciate it :)
[Captivate Android Development] ridethelight:
I kept wondering why flashing #55 kept breaking serendipity 6 last night. Now I know why! thanks existz
[Captivate Android Development] shoman94:
You are the man.... The support you have in this forum is crazy.... I owe you a beer.... wish you lived around here so I could buy you one personally.
[Captivate Android Development] shaolin95:
Can any one run Nenamark for me to see if we are getting into the 52s or so range again?

Thanks!
[Captivate Android Development] froli13:
Ran it a couple of times and I'm getting around 47-49. I never got passed 50 though.
[Captivate Android Development] existz:
I havent tried Nenamark but im still getting 60+ fps in everything else... remember, sometimes you have to lock the screen then unlock it for it to take effect
[Captivate Android Development] shaolin95:
Thanks mate
[Captivate Android Development] froli13:
Just got 68.2 and then 64 in neocore
[Captivate Android Development] froli13:
Please delete this
[Captivate Android Development] jcr81:
I oc'ed to 1200 and with the fugu tweaks im getting linpack of only 14.5 and quadrant of 1300 which is low but I swear the responsiveness has increased exponentially! Do you think those gingerbread files could be throwing the tests off?

Sent from my Samsung Captivate
[Captivate Android Development] existz:
You will get a higher linpack than 14 when oc to 1200, are you sure you enabled the correct states? also make sure to save your settings twice in VC, sometimes it doesnt stick
[Captivate Android Development] froli13:
You won't see any benchmark improvement using fugu tweaks, by the way...
[Captivate Android Development] jcr81:
Yeah I wasnt familiar with the "states" menu. Now im back to 17 linpack.

Sent from my Samsung Captivate
[Captivate Android Development] jcr81:
Holy scrap. My phone has never run this fast!!

Sent from my Samsung Captivate
[Captivate Android Development] TRusselo:
actually JUST with fugu and stock phoenix kernel N64oid has NEVER run smoother, cant wait to try with overclocking now!
[Captivate Android Development] doreyu:
Do you suggest BFQv2?
[Captivate Android Development] existz:
I recommend CFQ... I always get better performance/results with CFQ
[Captivate Android Development] 13_:
Freakin' awesome update!!11!!

Winning!

oc to 1.3

linpack - 18.112 -18.473

quad - 1833

nena - 51.2fps

neo - 66.3

oc settings

1300 -25

1200 -75

1000 -100

800 -75

600 -75

400 -100

200 -100

100 -100

also Serendipity 6.1

for some reason #55 was kicking my ass all over the place .... :rolleyes: ... but this ....this is wonderful :D
[Captivate Android Development] jcr81:
Anyone else having issues with wif? Mine doesnt sleep when the screen turns off. Happened after flashing sp56 and enabling fugu:(

Sent from my Samsung Captivate
[Captivate Android Development] antonyfl:
one annoying bug (for me alone) that I have found with suckerpunch: When I use 100 Hz, the "Impossible Game" runs slowly. When I use 1000Hz, the impossible game runs too fast :P Im using lagfix with Fugu

but otherwise great work
[Captivate Android Development] Dmoney5150:
i have the same problem wifi isnt working properly anymore...
[Captivate Android Development] existz:
Try clearing cache and dalvik cache in recovery...also reboot your router... and are you using fugu tweaks? Just wondering cause Im starting to think theres a connection
[Captivate Android Development] jcr81:
I rebooted a few times and wifi is back to normal...

Sent from my Samsung Captivate
[Captivate Android Development] psloan:
How does one use these tweaks? I installed #56.
[Captivate Android Development] existz:
Click the link to fugutweaks in the changelog in the OP...just flash with cwm