yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] ryude:
Oooohhhh, does this mean better battery life?
[Captivate Android Development] existz:
Testing battery now, still might have to tweak a few things before releasing it. Trying to find what was causing all the issues...seemed it either worked great for some or didn't work at all for others.. so its kind of like im starting all over again

Do you guys want refresh rate=72 or 60 in the final release?
[Captivate Android Development] ryude:
Well I will test it out when you release #53, my battery life is very consistent so I will know if it is better.
[Captivate Android Development] existz:
Technically it should be ok, both are captivates, only thing screen orientation might be different, but it might be the same also, not sure since I don't own an i9010 ..def let me know if you try for future reference
[Captivate Android Development] existz:
TEST-1 is up if you want to try it, check my irc channel .. would love some feedback
[Captivate Android Development] aalh:
oops

moved to irc
[Captivate Android Development] existz:
Ill look into it, all #53 test is, is K13C patch with oc/uv, which is the same OC/UV code I've been using...but im not seeing any thing like that..ill try to reproduce it
[Captivate Android Development] sjavvaji:
72 plz 10char
[Captivate Android Development] ronpinoy253:
AutoRotate Broken

Suckerpunch 50 100hz and 51 100z does not properly work with Paragon ROM 6 when using teh dropdown notification AutoRotate button. You can turn off the button (switch off on icon) and it will never be able to turn on again (switch on icon) without rebooting and the autorotate will still not be off even if icon is turned off.

Batch 1008

Paragon 6

Suckerpunch 50/51 100hz
[Captivate Android Development] Shammyh:
I've had that problem too from time to time with my JS5 based ROM. I think it has more to do with the TwFramework modifications than the kernel. Unless of course, you can fix this problem permanently by swapping to another kernel. But I doubt that would be the case.
[Captivate Android Development] ewingr:
In the OP it says:

Do you mean to create a folder on SD called /etc/init.d, or do you mean to put the file in the folder that already exists (on my phone anyway) that is under /system?

I presume the latter, but being as it does not specifically say that, I don't want to assume.
[Captivate Android Development] froli13:
In the directory already on you phone.
[Captivate Android Development] dutchschultz:
if i update from #52 sucker punch to #53 will i have to remove the "S_volt_scheduler" file out of system/etc/init.d

also i get 64 fps in neo core :)
[Captivate Android Development] johan8:
/etc/init.d is under "/" root directory.

if anything under SD, it would called /sdcard/abcde....
[Captivate Android Development] johan8:
I have been using #53-test for couple hours,

the previously camera problems seems gone!

Used barcode scanner a few times,

taking photos, change sence and effects, view photos delete photos, quit cam,

a moment later use camera take photos again.....

No freeze so far.

Just that the battery temp. seems a bit high.

During the first 5min, flip around menu and screen, snap 5 photos, battery temp. raised to 35C !

maybe battery drain fast too.

Already delete S_volt_scheduler before switch kernel.
[Captivate Android Development] AtoZ0to9:
sounds like you're a beta tester... shoudnt any problems with a test or beta version be discussed with existz and not in the forums? anways... how is the newer suckerpunch kernals? i went back to darkys rom and i can't use this kernal... been using speedmod... seems like it works off of speedmod base and i don't use OC, but love the UV... have u any experience with the suckerpunch voodoo? i can use that....
[Captivate Android Development] johan8:
Just tried his beta which is downloaded from the link in his thread Here.

Is it a big deal take about this here ?:confused:

I don't know, I don't know if he needed anyone to test it and report it.

Suckerpunch Voodoo is based on Voodoo and JPX, and added some tweaks and features.

Unlike Suckerpunch UV/OC is based on speedmod...... while speedmod is also based on JPX.

So voodoo doesn't have some speedmod tweak, but it is quite stable.
[Captivate Android Development] existz:
I don't care for you guys to talk about Test versions here, but if you have a bug report, post it in the IRC channel, if I don't respond, just post it anyways, I pop in and out through out the day.. that way ill see it ..

also, if you use the test versions, please let me know how it runs...battery life (only after running it for a few charge cycles), smoothness...etc etc.. The last time I posted the link in here, everyone just signed on to get the link and signed right back off and I literally got 0 feedback...except from the few guys who are regulars in the channel.. so if you run it and don't leave feedback, I wont know what needs fixed, or if i fixed something ..so with no feedback I have to assume there's no issues

Im finishing up a few things and should release #53 later today

EDIT

Also to those of you who have always had problems with SuckerPunch, if you could try #53-TEST, id really appreciate it...alot of things changed and would love to know if it helped for you guys.. visit my IRC channel for download info
[Captivate Android Development] slider2828:
Man you are the best existz.... I will try SP #53! Also I can't wait till the movie comes out!!!
[Captivate Android Development] cumanzor:
Any changelog for #53 test 3?
[Captivate Android Development] existz:
For #53-TEST 1 I basically started with a fresh jpx source then updated to K13C patch from the K12P I was using, then adding oc/uv... thats all it basically is, except a few different options at compile time, which is the same options ive been using. Then for TEST 2 ive only changed refresh rate to 72 so far..still working on a few things, ill have a full changelog up once #53 is complete.. right now im just starting fresh, so theres really not much added yet..also updating my repo on github, wiped it out and starting over on it as well..all from the beginning
[Captivate Android Development] ridethelight:
What the hell happened to #52? Did it brick your device so you struck its existence from the face of the planet?
[Captivate Android Development] existz:
Lol nah, there was actually #52 test builds up, but it never made it pass testing.. then I decided to start over from clean source and that became #53...so instead of renaming it #52, I left it as build #53 so I didn't confuse testers
[Captivate Android Development] RobertInCypress:
Can't wait to try #53! Been using #51 - kinda buggy but pretty quick.

edit - i dont mean the kernel was buggy, i just had it OC'd funny and it would glitch.
[Captivate Android Development] ridethelight:
I dont even see a reason for an update other than feature addition. 51 has been the most stable with my aggressive undervolting and by far has gotten me the best battery life.
[Captivate Android Development] gibson3659:
Use the app I am developing to save a conservative scheduler init to a zip that you can restore via cwm. It is a pain to recover from bad saved ov/uv settings via the other methods. Look for MakeUpdateZip in the captivate apps forum.
[Captivate Android Development] froli13:
#51 is good for me too. Stellar battery life: unpluged for 13 hours, screen on for 1 hour 30 minutes and 55% battery left!

UV like crazy, 100% stable.

1200/-100, 1120/-100, 1000/-100, 800/-125, 600/-100, 400/-150, 200/-150, 100/-150

EDIT: Never been able to UV that much before running Twingerbread ROM
[Captivate Android Development] shoman94:
Can anyone tell me the difference between this and Suckerpunch voodoo?

I'm a newbie with no idea what they are.... thanks
[Captivate Android Development] AReynante:
This is based off of Hardcore's speedmod K13C, and the voodoo one is, well voodoo based. This one OC/UV's while the voodoo kernel only UV's

Just in short, if anyone would like to add to help inform, please do so. :)
[Captivate Android Development] shoman94:
Well besides overclocking... are there any pluses and minuses to each?
[Captivate Android Development] AReynante:
I have only used the voodoo one for half a day or so, but I like OCing. In my experience I feel like the phone is smoother, but all the phones have different (cpus?), so every user likes a different feel. If I remember right, I get better benchmarks on this kernel vs. voodoo, but that isn't something to base it off of.
[Captivate Android Development] upNsmokeAllDay:
Love it.
[Captivate Android Development] ThisWasATriumph:
Existz, is is possible to make an extra warm option for the color profiles or would Hardcore have to implement that? My launch phone is very blue.
[Captivate Android Development] existz:
Haven't heard much back on #53 so I have to assume its ready to release, still touching up a few things but ill try to release it later tonight
[Captivate Android Development] johan8:
Just used it for a day, it is stable.

but can't tell about battery life, I think it is normal,

in idle about 1%/h.

Only one thing, 3D graphics can't reach over 60fps,

mine just 55.5fps.
[Captivate Android Development] existz:
Yea for TEST 1 I didn't change the refresh rate, but ill have it increased in the final
[Captivate Android Development] sjavvaji:
since you are not on irc

i would like to report that the random charge and sleep deaths were a result of a screwed up S_volt_scheduler...existz...tell people to clear their S_volt_scheduler so they don't run into issues...like u said, although the uv code is the same there might be some differences...make sure to change the refresh rate to 72hz...i think its good to release...i also got 1% drain per hour

fyi i was able to get it stable at the same settings i had it at before
[Captivate Android Development] AReynante:
Looking forward to the release! I didn't test it out, I hadn't been following this thread for the past couple days. I am running paragon6 right now, but I had been running SP since 41 or so :) Love it
[Captivate Android Development] existz:
Thanks, didnt even notice I wasn't connected to IRC, ill make sure to note it in the changelog, appreciate the feedback
[Captivate Android Development] slider2828:
Agree battery drain went down to 1% an hour on JL2 which was a lot better than before. Gallery and Camera doesn't crash and works great!

The Ram management seems a lot better than #51 and overall very stable compared. This one is definitely awesome. Haven't found a problem yet and currently on noop.

Sorry I haven't found anything that is a flaw.....
[Captivate Android Development] existz:
*UPDATE*

SuckerPunch-#53

Delete Voltage Control settings before flashing

-Rebuilt from scratch, to much to list

-Based off Hardcores K13C

-GPU refresh rate increased

NOTE If you get lower FPS than usual, lock the screen then unlock it and you should get 60+ fps ... also make sure to delete your Voltage Control settings, S_volt_scheduler in /etc/init.d, before flashing!! <--This is a MUST!
[Captivate Android Development] doreyu:
I was one of the people having problems with the previous version. Would get random freezing even with no oc/uv. I wanted to help test but I had a few tests lately and worried about it freezing overnight and missing my alarm :D

I'll give your final a shot now
[Captivate Android Development] Auridran:
Just installed, testing now. Will let you know my results after awhile of testing.

EDIT: Well, so far I can't even test it. Every application that needs superuser access says that it can't obtain it with this kernel.
[Captivate Android Development] existz:
How did you flash it? Kernel flasher app?
[Captivate Android Development] Auridran:
Through recovery. After having issues with kernel flasher, I stopped using it.

I tried flashing it again to no avail. I'm going to try going back to #51 and see if that fixes it, or if something just happened to break after flashing.
[Captivate Android Development] existz:
If anything just install root via cwm, install su+busybox... no problems here ..
[Captivate Android Development] AReynante:
I've never had problems with the kernel flasher, and I've used it a lot. I'm about to try to flash #53 with it, so I'll let you know how it goes.
[Captivate Android Development] doreyu:
Well i've got it running just fine so far. But I was wondering, are we required to execute S_mem_timings.sh file?
[Captivate Android Development] Auridran:
Yeah, I'm not sure what the heck happened. Even after I installed su+busybox through recovery it did not work.

I reflashed for about the fifth time, then installed su+busybox, then fixed permissions, then deleted cache and dalvik cache and it finally worked.
[Captivate Android Development] antonyfl:
possible to request a 500Hz or 600Hz version?
[Captivate Android Development] existz:
Clearing dalvik cache and cache could have been what fixed it, clearing it usually helps when there's weird problems like that
[Captivate Android Development] AReynante:
Just flashed successfully with the kernel flasher, UV'd back to my usual settings, OC to 1200. No problems so far, running smoother than I remember 51 running.

I'll post about battery or other problems later on, once I've had time to test it out
[Captivate Android Development] xidium:
I'm about to try this kernel for the first time. Any user suggestions as far 100Hz or 1000Hz goes? Which do you guys prefer?
[Captivate Android Development] existz:
Its not a requirement but is recommended for optimal ram performance.. just place in /etc/init.d
[Captivate Android Development] doreyu:
Oh yeah I did place it there, but if pressed on it asks if it should be executed or not. Guess I should just leave it and not do that.
[Captivate Android Development] existz:
I always use 100hz... gives best battery life, plus performance is really good
[Captivate Android Development] existz:
Yea you don't have to execute it, just place it there and when you boot, it will automatically run it
[Captivate Android Development] johan8:
Or just place the file into /data/init.d/

no remount is needed.;)
[Captivate Android Development] johan8:
500,600, doesn't make big difference.

Maybe a littttle bit smoother, maybe not.
[Captivate Android Development] johan8:
Maybe just download problem, try download again.

Flash it through CWM update, it is easier.
[Captivate Android Development] Soccer_Dad:
It's hard to make the decision to flash to #53 from #51. I'm getting absolutely insane battery life, compared to the last half dozen kernels I've tested. I get a 1% drain every two hours in standby. I get a 6% drain every hour with the screen set to never go off, or turning it on and off to manipulate various programs during today's staff meeting (that's 16 hours of pretty solid use). I'm leaving wifi on tonight, and I expect that will triple my battery drain - I might have only 66 hours of life rather than 200.

Thanks again for a great kernel.
[Captivate Android Development] antonyfl:
well personally I would prefer a 500Hz version. What was the reason for axe-ing the 500 hz
[Captivate Android Development] nybmx:
Just flashed 53 100hz (coming from 51) and its smooth as butter. Words with friends works again and scrolling throught menus and the app draw feels smoother. Great job as always.

Just a quick question though. Is this still optimized for bfq or is it back to cfq? Does it even matter?
[Captivate Android Development] sicmadek:
I would like to know about scheduler as well because i like to use noop.
[Captivate Android Development] johan8:
Using #53 100hz, CFQ.

it seems always stick with 800Mhz during normal use,

and the battery temp. seems a bit high.....

Packet data is OFF, wifi ON for ~10mins browsing webpage and market.
[Captivate Android Development] spradling:
Dude, updating to K13C base is big news! You should put it in the title!

I found out by chance just because I was bored because there aren't many rom updates recently and checked what's new with the suckerpunch update lol

Never tried SuckerPunch, I'm exited to test it now and use undervolt!

I think speedmod got a couple of battery tweaks between the last suckerpunch speedmod base and K13C (check the speedmod change log), so maybe it might be even better!

If not you can always flash back to #51 i guess.
[Captivate Android Development] 41LY45:
Awesome kernel. #53 works like a charm on Andromeda 1.2.

Runs well on 1.2Ghz. :D

Thanks again for teh awesum kernel though!
[Captivate Android Development] froli13:
There's a 1000hz version instead.
[Captivate Android Development] olo567:
Went back to Speedmod 13C with Cog 4 just to test stability of the ROM itself for a while, now that #53 is released I'm back to SuckerPunch! I just flashed Cog 4.1.1 last night so it might be a few days before my battery calibration has stabilized, but so far so good with this kernel.
[Captivate Android Development] doreyu:
It's been running great. I've had a lot less battery drainage.

I did have one random reboot while browsing the facebook app. I was testing out my usual higher voltages, and lost them at boot. Although I think from 1120-1000 i was (50,75,100,100,125,125,150). I went to back to safe ones for now.
[Captivate Android Development] spradling:
So far great! No problems at all, everything went smooth.

I set max clockspeed to 1Ghz and UV to -100 (Looking for maximum batt life, happy with speed).

I tried -125, passed both tests but crashed on launcherpro 3d launcher :(

Haven't tested the battery yet, looking forward to it, it's my first time undervolting.

Thanks for the kernel!!!!! :D

Edit: Running it with Darky 9.3 and JK4
[Captivate Android Development] psloan:
quick update, i flashed 53 this morning. I had my phone freeze twice after setting the same UV settings I had one 51%. one freeze was while charing with the phone off. Very strange. No freeze since backing off the under volting by 25% each level.

Not stellar battery yet, on my first charge, getting about 8% drain per hour while traveling to work this morning listening to my pre-downloaded podcasts.
[Captivate Android Development] neffarious:
the states drawer from the VC app is not there with this version. Are all states enabled now by default?

NVM somehow my 3.0 was replaced by 2.0... Swapping now

EDIT: that was it.
[Captivate Android Development] olo567:
Phone just crashed with UV settings that were stable on #51. Loosening it up now.
[Captivate Android Development] existz:
Since I started from a fresh source and alot of things changed, your oc/uv settings might need adjusted...this is normal
[Captivate Android Development] WickedNite:
Gonna try new update later on, looks good based on the changelog.
[Captivate Android Development] prayii:
My phone has always hated me anytime I've tried to OC/UV using any kernel.

Flashed #53 and am successfully running battery sippingly smooth.

Thank you existz.
[Captivate Android Development] MikeyMike01:
Giving 53 a go...

Does that mem script work work any kernel, or just this one?
[Captivate Android Development] sjavvaji:
delete ur previous s_volt_scheduler...i had similar problems while testing
[Captivate Android Development] existz:
Hey I know you have always had issues, let me know how it goes.. as for the memory timing script, it only works on this kernel, and maybe the paragon kernel, I know he uses similar oc/uv code. It will work with kernels that have /sys/devices/system/cpu/cpu0/cpufreq/AC_timing_registers sysfs files

Also make sure to delete the S_volt_scheduler file, if you leave it, it will cause problems...not sure why, even if you use the same settings, everyone who left it had issues, once deleted then flashed, you can re-save your settings
[Captivate Android Development] MikeyMike01:
Oh... I just left it from last time. No problems (yet).
[Captivate Android Development] existz:
If you do run into issues, try deleting it and rebooting, I know some had issues with stability when leaving it.. not being able to UV the same, lockups and reboots..etc..then deleting it solved it.. but u might be ok, I left mine and its been fine.. but let me know how it goes, curious as to see if its better
[Captivate Android Development] WickedNite:
Noop, bfq or cfq? I need insights. :)
[Captivate Android Development] Auridran:
Yeah, I'm definitely not stable at the same UV settings as #51, but so far I've only had to drop 1.4GHz from -25 to 0. We'll see if that is stable over the next couple days.
[Captivate Android Development] existz:
CFQ... i had switched to BFQ in the last version, but CFQ is alot smoother..thats why its default now
[Captivate Android Development] MikeyMike01:
I always use noop. I think it's irrelevant, honestly.
[Captivate Android Development] existz:
I always get faster read/write scores using cfq over any other, the benchmark "Benchmark" can test file system.. but might not be the issue for everyone though
[Captivate Android Development] crazililazn:
Hmm, using build 53, and with settings that were stable with build 51, I have had 3 random freezes.
[Captivate Android Development] ridethelight:
Updated to 53, reset UV/OC to my #51 settings. Doing a stability test burn to confirm stability, so far the same as #51. Hopefully battery life stays awesome.
[Captivate Android Development] shoman94:
Curious.... I was running Suckerpunch voodoo with lagfix enabled..... was getting mid to upper 1400's quadrant scores.... with #53 I''m getting 1250..... aren't they about the same? No overclocking btw.....
[Captivate Android Development] MikeyMike01:
For starters, words with friends seems to be "fine"*.

*It opens up to a giant url and you have about half a second to click a game before it pops up. Completely unrelated to kernel, and is because if ad blocking.
[Captivate Android Development] MikeyMike01:
Quadrant is literally the worlds worst benchmark.
[Captivate Android Development] existz:
Alot of different things can cause that, with voodoo vs speedmod, voodoo uses different mount options...etc... you can set FASTER mount options in recovery if you want higher quadrant scores. ..but don't base anything solely on that, one stupid, un-noticable thing can change quadrant scores drastically and you will never notice the difference or even benefit from it..its best just to disregard benchmarks all together as they are inaccurate imo

But technically no, they are not the same..even though you can use ext4 on both, there's still some differences ..mount options, vm tweaks, scheduler tweaks...etc..etc
[Captivate Android Development] zerkai:
What settings and battery are you managing?
[Captivate Android Development] shoman94:
So what benchmark should be used that will show real results then?
[Captivate Android Development] existz:
There really is none that show "real" results, they just give you a ballpark figure, even that is sometimes not accurate..just use it in real world situations, that's your best test..
[Captivate Android Development] ridethelight:
How happy you are with your phone
[Captivate Android Development] shoman94:
hmm... I personally cannot tell a difference between the two..... so far anyways.....
[Captivate Android Development] existz:
If your talking about the difference between the 2 kernels...I don't either, sp and sp-voodoo give me about the same battery life, same speed/smoothness.. it just comes down to user preference, some like to oc, some prefer voodoo color/sharpness over hardcores settings...etc..etc...
[Captivate Android Development] shoman94:
I installed the 100mhz version.... is that mainly a non overclock version?
[Captivate Android Development] existz:
Its hz, not mhz...it has nothing to do with the cpu speed, both versions are the same except the 100hz has a kernel hz value of 100hz, the 1000hz version is 1000hz, HZ is an internal timer value used by the Android/Linux kernel. It affects the timer granularity of some kernel functions.

With the 100hz version, it eliminates the kernel hz--user hz conversion, giving better battery life without hurting performance.. but if you go to high with the hz, drivers will start to break..ie wifi will not work..etc

Here's a good read on it.. http://kerneltrap.org/node/464
[Captivate Android Development] shoman94:
Yea it was a typo... not sure why I wrote that.

Good read thanks.....