yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Rrryan2:
Andromeda 1.0, Suckerpunch 41 500Hz, 1400 OC

(Sorry for landscape, got a lil carried away shaking Shootme)

Andromeda 1.0, Suckerpunch 46 500Hz, 1400 OC

Andromeda 1.0, Suckerpunch 41 500Hz, 1400 OC

Andromeda 1.0, Suckerpunch 46 500Hz, 1400 OC

Level 2 memory clear before each test. Voodoo lagfix (fast mount) and and all 4 recommended Speedmod options enabled for all tests.

Benchmarks ain't everything and the differences are minor (and it's still WAY better than stock!), but...

I'd still love to see a version with an option to either disable the brightfix or disable more of the lower settings. On my 1010 build I was actually happier with the stock auto-adjusted display. The display on it seemed noticably better than a 1007 build I got as a replacement for faulty GPS (lol) so I actually kept the 1010 and sent the 1007 back.

Thanks for all the work on this too. Really feel like the performance potential is finally unlocked. Donation sent.
[Captivate Android Development] pizz0wn3d:
Got my phone back up and running. build 46 is the nuts! Idk if it's the fresh new perception ROM or the newest update, but this is the smoothest my phone has ever been!

Can't wait to test out the battery life!

Herp derp Captivate XDA
[Captivate Android Development] roadrash7:
1000 version does not seem smoother at all.
[Captivate Android Development] shaolin95:
Results are well within the margin of error, in fact you should be getting 19s at 1400 not 18s but still no difference really. Well, one thing to consider is that all my benchmarks seem to bit a tad slower in Andromeda than with Paragon which is the reason I am waiting to have the andromeda native kernel (oced edition) before passing the final performance review on it.

As a side note, while I was never able to get 46 1000hz to hit 19s in linpack with either Paragon or Andromeda, the 46 500 XT edition does hit 19s so for some reason my phone just does not like that 1000hz version.

Hope I can get my hands on a 1450 or higher version...I am feeling lucky now with this kernel :D
[Captivate Android Development] roadrash7:
Same thing is happening with me. 13.9 linpack 1200ish quadrant With suckerpunch @ 1300. Then go back to paragon 1300 kernal and 17.7 and 1450ish. Stickin with paragon kernal for now but what is up with this. I wanna use suckerpunch man. Does it have to do with paragon
[Captivate Android Development] Auridran:
I figured I would try out the XT kernel, and my phone is significantly less stable with it than the 100Hz version, and I honestly didn't notice any difference in smoothness.
[Captivate Android Development] existz:
18+ with 1300 here, no problems, try enabling the 1200 state along with it..(100,200,400,600,800,1000,1200,1300) and see if that works. Also save your settings in VC twice to make sure they stick
[Captivate Android Development] roadrash7:
You on paragon rom
[Captivate Android Development] existz:
No, I've been switching back and forth with jpy and js2 ...the rom shouldn't matter, it sounds like the frequency is not getting activated, those scores are from running at 1000mhz, anytime you get 13-14 in linpack, your only at 1000, there's not going to be that big of a difference, since linpack calculates in mflops, its solely testing the cpu
[Captivate Android Development] WickedNite:
Idk what's wrong but as soon as I kill all the apps using task killer, it brings to one application listed on there. For example, I browsed youtube awhile ago but then after that, I killed the app using advanced task killer then it loaded back the youtube app. Tried it several times but it always does the same thing. Even other apps like xda or ebay. Idk if it's the rom or the kernel, I'm serendipity rom and this kernel at 1200mhz oc. Has anybody experienced this? I posted this also on serendipity thread so I can get more answers.

Sent from my Muscles using Brain Cells

Sent from my Muscles using Brain Cells
[Captivate Android Development] johan8:
I feel that XT1000 is a little bit smoother than nonXT 100.

If it drain much power than nonXT, I think I would use nonXT.

This kernel is sucking great !

Keep moving !
[Captivate Android Development] opcow:
Sounds like you didn't take your medicine. Have a placebo:
[Captivate Android Development] olo567:
Had another "charge death" issue, charged while phone was off, wouldn't start in the AM until a battery pull. No OC/UV had been applied yet. Ideas?

Running #45-1000hz, might try #46 @ 500, didn't notice any change in operation with the 1000.
[Captivate Android Development] DunDunDario:
Yup I experience this same thing. I tried reinstalling suckerpunch, settings different states and clocks, but still nothing. :(
[Captivate Android Development] shaolin95:
So I tested 1000 , 500 and 100 and 100 actually gives me the best performance. On Stability test is shows 1393 with 100Hz while the 1000Hz version shows 1354....I know it is not supposed to be Mhz listed in Stability test but whatever it is, the lower number goes hand to hand with lower performance. I score around 19.3 or higher with 100Hz while never hitting 19s with the 1000Hz ...interesting how my phone reacts with these versions.
[Captivate Android Development] RonH54:
I have always used the 500 or 1000 version of this Kernel. I have only hit the 19's one time with Linpack but I can't remember exactly which version it was. I know it wasn't 44 or 46 I think it was 41 and my top state is 1280 or 1300.
[Captivate Android Development] elghouchd:
Can someone explain to me the difference between the XT versions and the non XT version? Also, when i want to update this kernel, should i always delete my s_volt_scheduler before updating? Thanks!
[Captivate Android Development] shaolin95:
If your phone is like mine, try the 100Hz version...you might get a nice surprise like I did ;)
[Captivate Android Development] slaman:
Had a charge death this morning after lowering UV a bunch after sleep death issues.... had run stability tests and the whole works, but this morning woke up to an off phone.

I'll try #46 and the 500Hz XT version.
[Captivate Android Development] joedon3:
I'm getting the same thing with mine. at 500hz, I would score between 17.9 and 18.1 on Linpack. When I moved to 100hz, I was scoring 18.3+ consistently.

Edit: with my CPU at 1.3
[Captivate Android Development] shaolin95:
So something is odd with how the other are being calculated I guess as we were supposed to get more performance not less...guess we can have the best of both worlds since 100Hz is supposed to give better battery life yet performance is also a bit better :-)
[Captivate Android Development] Darryl Henley:
been testing the 1000 vs 500 and i don't see any difference. after seeing the comments about the 100, i loaded it up. for me, the 100 is faster and smother than the other 2.
[Captivate Android Development] slider2828:
Glad you made the switch.... I love this kernel and its super stable and battery life is great!.... Only thing is that GPS suffers a bit vs the Paragon kernel, but else its the best out there....

Hows your GPS?
[Captivate Android Development] shaolin95:
Actually I havent make the switch yet..I just like to test everything under the sun to see what fits my phone better LOL

I like this one a lot and nice that he keeps it up date all the time.

I still use Paragons as my main one as I get some odd restart issues with this one when connecting or disconnecting the power (usb or or wall) to it. It is perfectly fine and stable after other than that which is quite odd.

I am hoping to try a faster version of it...I have the feeling this kernel has the best change for my phone to go over 1400....we shall see if he wants to come up with a faster edition :-)
[Captivate Android Development] existz:
The restart when connecting/disconnecting to power could be caused by which toolchains I use, as I know DG had this problem when trying out the one I used...but what is weird, is this is the first report of it, other than DG using them on a different source, so im not sure what to make of it yet, with a couple 1000s of downloads, either yours is the only one or some just haven't reported it, if others have this issue please let me know and ill try a different toolchain
[Captivate Android Development] shaolin95:
Must be a Utah thing as DG and I are both in Utah lol

Not sure what to think about it...the phone runs all stability tests perfectly fine but randomly when plugging or unplugging the power boom..goes off.

So any chance of a higher speed one...I am feeling lucky LOL
[Captivate Android Development] sixstringsg:
Haha is your goal to cook eggs on your phone?
[Captivate Android Development] johan8:
With #46, after fully charged and unplug power cord,

the battery level will drop from 100% to 98% immediately.

I think it is something wrong with the battery measurement.
[Captivate Android Development] sjavvaji:
so far amazing...the only kink you have to work out it the slightly quirky wifi...and how about 1.4ghz just for kicks :D...and what are your plans to update along hardcore...will u stay on p and produce your own stuff or will u switch bases as hardcore makes big changes?
[Captivate Android Development] astrocrep:
I also want to give a big thumbs up... this is giving me the best battery life I have ever seen with a custom rom from Doc's I9000 kitchen with a JK4 modem.

Keep up the awesome work!
[Captivate Android Development] diablo009:
Can anyone pls confirm if "enabling logger" in the recovery console is making security apps like app protector work.
[Captivate Android Development] existz:
Im more than likley going to stay on P but ill add the changes to my source when Hardcore releases them, ill just cherry pick what I want to add as well as add my own features...

As for the wifi, im looking into some things to fix this, worst case ill disable IPv6 Privacy, which solves this, until I do figure it out..
[Captivate Android Development] sjavvaji:
nice. so can u reduce the notification noise on headphones?...i nearly blew out my ears when i got a text...i think hardcore changed this is q...this is y i asked the previous question
[Captivate Android Development] slaman:
You are officially a rock-star... My battery drain of 7-10% per hour is now gone!!!

I am running -75,-75,-75,-100,-100,-100 stable so far... will try to push this a bit more.

No tweaks enabled as of yet.
[Captivate Android Development] existz:
Yes those apps rely on debug, so turning it on let's them work
[Captivate Android Development] diablo009:
Could you pls confirm this. I have 'debug mode' on/off in my current kernel too, and it is set to off. And my security apps still work. So am confused.
[Captivate Android Development] sjavvaji:
K12Q: 24-Jan-2011

- Disabled Android debug logger / logcat (can be re-enabled in Tweaks)

- Disabled all kernel debug messages (printk) for increased efficiency

- Changed boot logo to I897 logo for AT&T Captivate version

- Changed /cache to ext4nj in recommended ext4 lagfix to fix large Market downloads

- Optional IPv6 Privacy support in Tweaks

- Voodoo Sound v2 compatible

- Fixed loud notification problem with headphones

- Fixed popping / clicking noise when music and FM radio is stopped / started

- Better FM Radio sound:

- - Really removed the high pass filter and DRC from FM Radio (restores full bass)

- - Turn on 4FS mode for ADC in FM Radio (smoother high frequencies)

- - Turn on 128x oversampling for ADC and DAC in FM Radio mode

- Adjusted volume of FM Radio and Media Playback to be similar

- General sound quality improvements:

- - Maximized digital mixer output to improve SNR and resolution

- - 128x oversampling option in Voodoo Sound enabled by default

- - Explicitly disable DRC and NG during media playback, if +1.5dB mode is NOT selected

that part
[Captivate Android Development] existz:
Ill look into it, with my version it uses stock voodoo sound 2 settings instead of hardcores new sound settings, with P it only had voodoo sound 1 so I manually updated it to voodoo snd2
[Captivate Android Development] sjavvaji:
thanks for all the help existz...love the kernel
[Captivate Android Development] lrs421:
+1. Been playing with 1120 version all morning. Its sweet.
[Captivate Android Development] existz:
Try using an emulator and type "logcat" , if it works then android logger is still enabled, also in mine and in hardcores, printk is disabled as well
[Captivate Android Development] phoenix2217:
Wow, all I can say is its FAST. OC UV 1280 and running stable. 50+ passes with stability test and looped necore for about 30 minutes. Well done. First kernel to get me past 1000 OC UV and stable :)

Settings are from lowest to highest

Noop

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

Gonna try for even lower.
[Captivate Android Development] magnumrt562:
Does this have the voodoo color/sharpness fix?
[Captivate Android Development] LimaI896:
I'm running -125,-125,-125,-100,-75,-50
[Captivate Android Development] sjavvaji:
running 1280mhz to 100mhz

i have -125, -125, -150, -125, -125, -125

But then again i have a phone that can do 1.45ghz stable

so far i have lost 1% per hour in two hours of just leaving the phone alone...this is better than the speedmod...i was losing 2-3% per hour there but too early to tell
[Captivate Android Development] joeshmoe08:
Yes its based off of speedmod k which had sharpness fix.
[Captivate Android Development] magnumrt562:
Im lazy. Thank you. HAHAHA
[Captivate Android Development] existz:
UPDATE

Build #24-25 (01/27/11)

-Added Kernel HZ=500 Varient (Should be smoother)

-Tweaked more config and compiler options for stability

-Removed references to FM radio in Voodoo App

Im still working on the Wifi connectivity issues, so bare with me just a little bit longer...
[Captivate Android Development] neubauej:
I have been running the gb 1280 kernel on perception with my uv at -50 across the board. -50 in 1280 is the only way the phone doesnt freeze. Higher or lower and it freezes. 17.5 or so linpack 1820's quadrant. Rock solid at those settings.

Tried this kernel, and it just plain wont run. Constant freezes. I did remove the old scheduler, and Voltage control adjusts this kernel just fine. I tried all 3 versions of #46 and no difference. It wont stay stable for me at any voltage setting even non oc and no uv. It will barely boot, and often wont.

Does my phone just suck, and i got lucky on the gb kernel? Help!
[Captivate Android Development] slider2828:
Yeah it takes couple of on phone, off phone, one phone charges to get it calibrated.... Not a big deal... but yeah thats how you fix it. I think its actaully more accurate since, it doesn't really charge 100% while the phone is on. Thats just a manuf. bs...IMHO
[Captivate Android Development] davwman:
Wow! No updates today...
[Captivate Android Development] slider2828:
What ROM are you running? I think this plays a big part in it too!
[Captivate Android Development] neubauej:
Perception 10.2
[Captivate Android Development] existz:
Lol, the day is still young my friend...only 1pm here ..not sure if ill put anything out today or not, still working on a few things..but I might :P
[Captivate Android Development] slider2828:
Hmmmm.... Try another ROM like Paragon..... or Serendipity... see if that works better.... Was your install of Perception clean? From a JF6 Master Clear?
[Captivate Android Development] neubauej:
I might have to...

Clean install, formatted sd cards, and odin to jf6 master clear.

Flashed perception, then gb's kernel.
[Captivate Android Development] slider2828:
Yeah you might have to.... Try Paragon! Its a fav so far and fast.... Good luck man!
[Captivate Android Development] shaolin95:
There goes my super awesome idea for a new kernel feature! :D

Seriously it does not get that hot so I am thinking it might be able to handle a bit more but who knows.
[Captivate Android Development] olo567:
I have the issue. I assumed it was charge death, but the phone is actually responsive until I unplug the cord. Has only happened to me after being plugged in for a long time, as in overnight.
[Captivate Android Development] beerbaronstatic:
the unplug charger reboot happened to me too once, I mistook it for a force close /hard crash
[Captivate Android Development] Tweak4fun:
Using #39 500 with phoenix 4. OC' d to 1200. 4 days now no issues. This morning, I noticed that the screen looked strange. It said kernel panic. It was on the charger all night. Could this be some weird form of charge death?
[Captivate Android Development] existz:
Alright, ill start messing with different toolchains and see if we can't fix this, might take a couple a builds though, as I wont know until you guys try it
[Captivate Android Development] eSPyeL:
What toolchain and compiler optimizations are you using?

edit: nm, just saw the compiler flags in the OP
[Captivate Android Development] existz:
I was using 2010.09-50 .. with basically same as Hardcore.. -O2 -mcpu=cortex-a8 -mfpu=neon -mfloat-abi=softfp
[Captivate Android Development] DocRawk:
How difficult would it be to integrate xcaliburinhand's car/desk dock support? That car mount looks pretty nice...
[Captivate Android Development] existz:
Its already included...check the changelog in OP
[Captivate Android Development] Loggik:
Okay, reporting back on my experience with the 1000Hz. I started messing around with the overclocking, because I'd never overclocked my phone before. I put started at 1200 and didn't notice any great Linpack scores, so I went up to 1400 (I was seriously worried about battery though), and I could run one or two Linpack tests before the phone froze. Then later in the day yesterday, I tried changing my wallpaper, and while scrolling through the default wallpapers on the phone, it froze again. So not very stable.

After that, I flashed the #46 500Hz and OC'd to 1400 with the same UV settings. Now I have no issue with freezing. I ran Stability Test on it throughout the whole night (maybe a little excessive, I know), and it was still running this morning.

Sadly though, I'm probably going to stick around an OC of 1200, because I can't compromise the battery that I used today. I'm a student, going to school from 6:15 in the morning to 3:00 PM (not school times, but when I unplug/plug in my phone before and after school hours). My phone started at 100% obviously, and is now down to 51% according to my battery mod.

Thank you existz for all of your hard work on this amazing kernel!
[Captivate Android Development] slider2828:
At 1200MHZ you might as well use the 100mhz kernel version. Its smoother and has better battery life. Try it out!
[Captivate Android Development] opcow:
I don't think so. With the 1000Hz kernel your apps are getting interrupted a lot more often and there is some overhead processing cost to that.
[Captivate Android Development] opcow:
I haven't had a reboot, but I unplugged and the phone just shut off or either was frozen with the screen off.
[Captivate Android Development] existz:
The next version will have an update OC/UV code thanks to eSPyel, and also I changed toolchains to 2010.09-51 ... on all previous versions at 1.4ghz I was getting 19.2-19.5 consistently in Linpack, with the new version im getting 19.7-20.2 consistently ...so it looks like there "some" performance gain, results may vary.. But I just put it up for my testers, so if its on par with previous versions and is stable, hopefully I can get it up tonite or tomorrow
[Captivate Android Development] shaolin95:
Looking forward to this. :-)
[Captivate Android Development] itdiestoday:
I've been messing with the 1000 today and I like it a lot. I went from 100 to 500 to 1000 and the jump from the 500 isn't really noticeable but still nice. I must say, im quite surprised there's no updates today because you've been on a tear. Lol. Also, with all three kernels I consistently hit the 1880 quadrant score but have never made it once to 17 in linpack. Currently sitting at 1.2ghz.

Great work

Sent from my Captivate
[Captivate Android Development] existz:
lol..yea I havent actually done that many test versions today either, usually im flashing around 8-10 versions a day, but only done 2-3 so far lol...ive got a test version out, if it comes back good and stable ill have an update.. just have to wait on testers to report back..
[Captivate Android Development] lrs421:
So I've been away for a few hours and your sneaking out a new version :-)

Looking forward to it!
[Captivate Android Development] existz:
Check the OP, the difference between the 2 is the non xt version has kernel hz=100 and user hz=100, the XT version has kernel hz=500 user hz=150, and the XT-1000 version has kernel hz=1000 user hz=200... as for deleting the s_volt_scheduler, you dont have to delete it when updating builds, unless I change the frequencies, which I will post it if I do, and will tell you that you need to delete it in the change log
[Captivate Android Development] elghouchd:
So it sounds like the XT version is smoother?
[Captivate Android Development] itdiestoday:
you will be pleased with all three versions. :eek:
[Captivate Android Development] elghouchd:
Oh no im getting around 16.7 in Linpack when i updated to the XT-1000mhz version :( I used to get around 19.2
[Captivate Android Development] Lertets:
gotta say this is the best kernel I've tried. It's got everything I need; blazing fast speed + battery life.

I hope the benchmark junkies never change this. Keep up the great work.

Also I'm currently running

Build #44-XT 1000

Continuum 2.2

KP1 Modem

Today, I've listened to music for 3 hours, sent 50 text messages and talked on the phone for 10 min.

I'm sitting at 74% and have had the phone unplugged for 10.5 hours.

THANK YOU!
[Captivate Android Development] gibson3659:
I have similar issues on boot, but mine is stable if I can get it up without freezing. It will often freeze regardless of uv/oc. I love the 600 step, but since it won't boot reliably I am trying the Paragon kernel.

edit: BTW, I am also running Perception. It is the only ROM I have found so far that supports my required Exchange policies besides stock.
[Captivate Android Development] zuNcHAN:
I have the same issue. So far have only fully discharged/charged once, i'll keep trying and see if it becomes fixed. I did wipe dalvik cache/cache/battery stats.
[Captivate Android Development] lrs421:
This is a characteristic of 2.2.1 roms and kernels. Ignore it, it's a battery saving feature.
[Captivate Android Development] Shammyh:
Ditto. Also had a Charge of Death the other night, but that may have just been a fluke. The unplugging problem is reproducible though.
[Captivate Android Development] existz:
Ill have a new test version up soon, i put one up a little bit ago but have since reworked more of the frequency code, also using a new toolchain, we will see if it makes a difference with plugging/unplugging, the new code should make everything more consistent, you might have to adjust your UV settings since the code was changed..I might make it public, if I don't, I should have a new release up tomorrow
[Captivate Android Development] apparition:
How exactly do you guys test for stable UV settings for clock speeds inbetween your lowest and max clock? I know I can test my stability for OCs of 1.4ghz, for example, and I know that if my phone has sleep death, then my lowest clock (ie. 100mhz) UV setting is too low. But how exactly do I test stability for clocks like 200, 400, 600, 800mhz, etc?
[Captivate Android Development] IStern:
I generally set the OC freqs at -25 to start, -50 for 1.0ghz, and -75 for everything else. If your phone lives through a night of charging, then drop 100mhz to -100, do another night of testing etc etc. If you're UV-ing too much for the middle frequencies, usually a benchmark program or even everyday use will cause a freeze.

Trial and error, basically 8)
[Captivate Android Development] froli13:
For all the doubters out there, battery life is stellar with #46 XT-1000Hz version. 14 hours since unplugged and still at 35% screen on for 1h13. OC/UV settings are in my sig.
[Captivate Android Development] Killemalll:
This is what I get at 1.2ghz with #46 XT and Darky's 9.2

Sent from my SGH-I897