yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] opcow:
I have hard locks using the camera. I've never had a problem with SuckerPunch unless I was using the camera. The phone can consistently be made to freeze by loading the camera app and switching back and forth between video and still modes. It generally takes several switches, but the phone will eventually freeze.

So, this morning I installed the Paragon 1300MHz kernel. I switched back and forth between still and video modes in the camera app until my thumb got tired. No freeze. I don't think it's a faulty camera. Too many other people report the same issue and if it were the kernel change while still OC/UVing probably wouldn't have fixed it. There may be many more people with this problem but they just have been lucky and not gotten hit with it yet. I didn't get hit for a while, and when I did I lost a very important video (I blame myself for that, of course, shooting an important video on an overclocked phone with not fully test software isn't really a good idea).

If I had to guess, I would say it's related to the refresh rate change. There is definitely something funky with that anyway as people (myself included) have seen random 50 fps caps which seem to come and go for no clear reason. I don't really see the benefit of that change anyway, other then maybe to boost neocore scores.
[Captivate Android Development] Auridran:
I'd say that's definitely a possibility. I personally have not had any hard locks from switching back and forth between camera and video modes, doing pretty much what you did with the Paragon kernel. Something weird is going on, especially since a lot of people said they've had to back off their OC/UV settings in the newest version, where I've been able to UV slightly more on certain frequencies.

I think I've finally found stable OC/UV settings too. Over two days of uptime with no crashes (fingers crossed) of any kind so far.
[Captivate Android Development] RonH54:
Good to hear but I think the Beta Version are good to go with SpeedMod/SuckerPunch it the Final 9.3 that is suppose to possibly have problems with these Kernels. I hope the info I was told about Final was wrong here was what was Posted.

"I really recommend Voodoo as your kernel. It's stable and easy.

We will fully concentrate on Voodoo.

SpeedMod is gonna have a hard time in the future with v9.3.

Sorry to say this."

"We have to make workarounds (which delays the ROM releases) for SpeedMod because it doesn't use standards... Partitions etc. you know.

Will write more when v9.3 Final is here."

"No.... in v9.3 FINAL you don´t ever turn on Tweaks

You can enable LagFix but leave SpeedMod Tweaks alone'"
[Captivate Android Development] xdahgary:
@opcow I also switched the paragon's 1.2ghz kernel. No problems at all. Definitely not the camera app. I'm thinking the low memory tweaks is the cause.
[Captivate Android Development] ccdoggy:
what are the commands to view the logs? assuming its through adb shell.

I am trying to research my battery drain and general interest and it would be helpful if i could read through some logs. I did try some general dmesg commands but nothing ever came up.

Thanks.
[Captivate Android Development] neffarious:
Just another Camera App problem having soul here. Also, having some random related soft reboots. using serendiptiy 5.11
[Captivate Android Development] existz:
i "think" ive got the camera issue figured out, im able to switch back and forth 50x with no problems...waiting for testers to confirm..
[Captivate Android Development] existz:
On a side note... I've been working on a new voodoo based kernel (lagfix, sound, color/sharpness), its not a OC/UV kernel, but its UV'd 50mV by default...plus wayyy more.. its in testing now, hopefully I can release it this weekend if any of you are interested
[Captivate Android Development] pizz0wn3d:
Ooh la la.

Can't wait. Are you still going to continue developing this over?

Herp Derp Captivate XDA
[Captivate Android Development] Grandelama:
Nice! What could be the advantages over suckerpunch in your opinion?
[Captivate Android Development] existz:
Yea ill continue to work on both.. but i might have to drop one of them once the official froyo source comes out, which ill worry about that when the time comes, hard telling when we will actually get the sources

It should be more stable all around, as OC/UV can cause alot of issues..it will be more of a kernel for people who just want to flash something and go on, dont have to continue messing with different settings to get it stable...I guess you could say more user friendly...with this it will be UV'd 50 by default, which i believe almost all users can handle 50mV..if it proves to be to much ill lower it 25..but it should be fine for everyone.. Ill be bringing alot of things that i done to SuckerPunch over to the Voodoo kernel, so it will be kinda similar, trying to push for the best battery life possible..but there will be a few changes as well
[Captivate Android Development] :
Any chance it will be based off of the new AT&T kernel so that it will have the audience drivers included, or can you inject those drivers with any kernel?

Im looking forward to your next kernel, as my phone dosent like to be OC'd. Good luck.
[Captivate Android Development] existz:
As of right now it will be based of i9000 JPX..atleast until the sources for official froyo are released, then ill probably convert it over to the new sources
[Captivate Android Development] neffarious:
If that happens is there any chance it will support HUPSA modems?
[Captivate Android Development] joeshmoe08:
Question: Will the new kernel still be voltage control compatable for just uv? I am asking because will there be a way for people who want to uv more to be able to do so?
[Captivate Android Development] existz:
Originally I didnt plan on it, since the UV code is part of the OC code, and with this kernel I didnt want an OC/UV kernel, just UVing some by default to help with battery life.. ill see what i can do, but i dont know if i can do it or not without having OC
[Captivate Android Development] sjavvaji:
hey...the att froyo ota is coming out tomorrow...so the source should follow soon like it did for eclair right...i was hoping that i can still use i9000 roms because no offense...they are so much better (i9088 is decent too)...is it possible to apply the audience drivers to the i9000 suckerpunch...
[Captivate Android Development] froli13:
Would it be possible for users to change the default UV without having to recompile the kernel? Or it would be the same as using the VC app?
[Captivate Android Development] existz:
I agree, ill continue to use i9000 based kernels/roms even though official froyo is out, atleast until we start seeing some good aosp roms.. ill still keep SuckerPunch the way it is, i9000 based, then the Voodoo kernel ill convert over to captivate froyo source.. As far as the audience driver, yea im sure it wont be hard to port over, im sure xcaliburinhand or someone will get it done
[Captivate Android Development] existz:
No.. theres really only 2 choices, either having OC/UV or not.. i just figured I would lower some of the voltages down to help with battery life, its either that or leave it stock.. i cant make the UV configurable unless theres OC, and with the Voodoo kernel it wont be OC/UV...which that doesnt mean I wont make a OC/UV kernel from official captivate source..i plan on making one later on
[Captivate Android Development] sjavvaji:
so suckerpunch (in i9000 form) with audience drivers is possible with source?...for clarification
[Captivate Android Development] existz:
Yea im sure it will be done, once we get source ill do what I can unless someone else gets it first, then ill just add it in... which im pretty confident it will/can be done, alot more challenging stuff has been ported
[Captivate Android Development] abee_13:
can this kernel be used with cognition 4 even though its i9000 based. I really like this and want to stick with it.
[Captivate Android Development] froli13:
Yes. You need to flash a i9000 modem though.
[Captivate Android Development] existz:
I take what I said back, the Voodoo version WILL be Voltage Control compatible, but with no OC..so users will be able to UV for all frequencies
[Captivate Android Development] doreyu:
A Voodoo kernel with UV sounds awesome!
[Captivate Android Development] existz:
Should have it up soon..hopefully late tonite/tomorrow
[Captivate Android Development] AReynante:
Sad to hear for me about the no OC/UV, but I guess for the majority of people it would be better that way. I hope you keep with the OC/UV version for as long as you are able to, I love it :) Thank you for all your hard work!
[Captivate Android Development] existz:
SuckerPunch will always be OC/UV, but SuckerPunch-Voodoo will only have UV capabilities ..no OC..and ill work on both
[Captivate Android Development] WickedNite:
So what's the main difference between this and SuckerPunch-Voodoo?

Sent from my Muscles using Brain Cells
[Captivate Android Development] existz:
-SuckerPunch-

Hardcores Color Brightness/Sharpness fix

Uses Speedmod initramfs ULF (ext4 lagfix is similar to voodoo lagfix, but not the same, plus has tweaks)

OC/UV support

-SuckerPunch-Voodoo- mainly for those that prefer voodoo color/sharpness and those that do not want to OC but want to UV

Voodoo lagfix, Color/Sharpeness fix

UV Support (no OC)
[Captivate Android Development] slider2828:
Wow you are amazing. Anyways yeah I dunno what is going on with 51, but 48 seemed awesome on kernel 100mhz.... Any ideas why?
[Captivate Android Development] johan8:
Testing on #52-Test1

it is terrible with Camera.

Take some photo, view inside camera app, delete photo, quit camera......

Then photo freeze.....:(
[Captivate Android Development] Doug8796:
how does this compare to SetiroN?
[Captivate Android Development] johan8:
The latest SetiroN is quite stable and smooth! (unknown kernel Hz, but the smoothest I've ever used)

However it is already 2 months ago,

lack of HPcall, Voodoo sound, latest sharpness fix etc..

Sounds like the developer has stopped making kernel....

If you don't need those features, you may try.
[Captivate Android Development] aalh:
ahhhh

someday.....

all the good stuff happens, someday

:rolleyes:
[Captivate Android Development] cumanzor:
Using Test 52 as well, camera is working fine for me. Can record at 720p as well.

Question, does this kernel work with Cognition v4?
[Captivate Android Development] Chillyw:
Earlier, I had gotten some freezing. Well, since I removed the RAM timings, my freezing stopped and I'm undervolted like crazy with #51.

I'm OC'd to 1.12 ghz and my voltages are -125, -125, -125, -100, -100, -75, -75 and I haven't had a freeze yet. My battery lasts forever!
[Captivate Android Development] crupp:
Cool. Thanks. I'll see if we get voodoo sound 3. 9 before flashing.

Sent from a Serendipity ROM
[Captivate Android Development] existz:
Im working on it now, but keep in mind I got 4 versions I have to compile and upload, that will take the most time lol

EDIT

Compiling now...2 down 2 to go
[Captivate Android Development] Barbarian:
This kernel is great so far.

Sent from my Captivate running FireFly 2.0.5
[Captivate Android Development] opcow:
Yeah, I'm not a fan of this kernel hz jacking up. I have a feeling the super smoothness people report is just a placebo effect. I haven't seen it. Granted I haven't really tried and I don't have 2 phones to test head to head, but if there is a difference it can't be huge. And if 500Hz is good why not 1000Hz? There is probably a sweet spot and it's probably somewhere around the standard value used in stock firmware.
[Captivate Android Development] existz:
Theres certain situations where 500hz is alot smoother than 100 or stock 250, I believe it just comes down to how you use your phone, same with OC, some people dont do certain things to where they will even notice it, And for 1000hz, if you go to high it will start to break drivers, things will start to not work, this has been tested before, finding the middle spot, and as far as I know 500hz is that, but like I said, some users will never see a difference, but other users, depending on how they use the phone, 500hz make a world of difference
[Captivate Android Development] nickm50:
Just changed to this kernal.

Getting linpack score of 25.296

Quadrant score is 2035

I know the numbers don't mean anything, but its nice to see them high :)

Running the 1.28/500hz version.

I am anxiously waiting for the voodoo sound 3 version.
[Captivate Android Development] silverslotcar:
25 linpack with what lagfix?? Bcuz its not just ext4.
[Captivate Android Development] WickedNite:
Does the 1280 makes any difference on the battery life?
[Captivate Android Development] sjavvaji:
ooo...he's uploading...the build 24 and 25 are gone
[Captivate Android Development] Nickel Dime Bay:
lol @ 25 on linpack, now THAT id like to see!
[Captivate Android Development] nickm50:
stock Canadian rogers 2.2 rom

suckerpunch kernal #25 (1.28 version)

all tweak options enabled

modem: jk4

speedmod lagfix

ext4/ext2

data_fs=ext4

cache_fs=ext4

dbdata_fs=ext4

data_loop=ext2

cache_loop=ext2

dbdataloop=ext2

bind data false
[Captivate Android Development] nickm50:
what app do I use to take pics?
[Captivate Android Development] sjavvaji:
is there any reason this is not recommended?...basically, is it safe to use?
[Captivate Android Development] gibson3659:
Charge Death

I've had a few charge deaths with this kernel, but so far it has only happened when I use a mini2micro adapter on my mini cable plugged into the oem ac adapter. The adapter does not support data, so apparently the captivate expects a full usb connection to charge normally. I noticed in the past that if I tried to charge the phone with this cable/adapter combo while the phone is off, it boots automatically.

So if you are experience charge deaths, try an oem ( or another full ) usb cable.
[Captivate Android Development] silverslotcar:
drocap 2 or shootme from the market. I prefer shootme.
[Captivate Android Development] existz:
**UPDATE**

Build #26-27 (01/27/11)

-Updated Voodoo Sound v3
[Captivate Android Development] realcoofox:
THX for update! i'll try it. hope it is stable.

Send from my I897 using XDA app via GFW
[Captivate Android Development] WickedNite:
Any answer for this?
[Captivate Android Development] existz:
I personally use 1120mhz kernel hz=100 and it gives me the best battery life
[Captivate Android Development] WickedNite:
But does the 1280 drains the battery faster or it's the same with 1120?
[Captivate Android Development] slider2828:
Hmmmm maybe it was that RAM timing script I forgot I had that loaded. Will try again..... Maybe its my fault.... not existz... sorry buddy!
[Captivate Android Development] opcow:
It does, but you'll need to change the modem as well.
[Captivate Android Development] cumanzor:
In other words, no audience chip support then....

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] gibson3659:
I've started a new app that the oc/uv community might be interested in. Please take a look at MakeUpdateZip http://xdaforums.com/showthread.php?t=968224. I wish I would have had it when I was looking for my stable oc/uv points.

Thank.
[Captivate Android Development] Dino.:
I thought I was the only one also! lol! Idk what happen but it was limited to 800mhz and only the states up to 800 were enabled. but after a freeze in the gallery, it would hit 64.#fps constantly. When before the freeze it was 48.#fps

Now OC to 1200 it still says 64.#fps also.I posted on the app forum but no response. does it make a diff if I'm using 3.0 not 3.0a3?

I honestly like the OC, so I hope you can at one point make the new voodoo OC-able lol.

build#51-S 5.11-KP1

100/200/400/800/1200

-150 -125 -125 -100 and -75
[Captivate Android Development] Majortom420:
Been using sucker punch since inception and 51 really screwed the pooch on me. Power button is acting really wonky, Long press doesn't shut down the phone, nor does it bring up the recovery option overlay. Had to download rom manager to force the phone into recovery mode.

I downgraded and I'm still running into the same issue, power button works fine for sleep and works fine as the "OK" button in Clockwork recovery, but doesn't have any real function other than that. Looks like I'm going have to do a complete wipe which is really unfortunate. Hope you can fix this in your next set of updates until then I'm going back to SpeedMod.
[Captivate Android Development] Auridran:
This does not sound like a kernel issue to me, but I could be wrong.
[Captivate Android Development] Shammyh:
Perhaps this has something to do with the ROM paired with the kernel, not the kernel itself. I too have used almost every revision of SuckerPunch since Existz started compiling it.

I'm using #51 w/ Precision 3.5, and it's the smoothest experience my little Captivate has ever had. Also getting like 30-40 hours of battery with moderate usage. And since no one else seems to have those problems, it's probably something on your end, not the kernel.
[Captivate Android Development] opcow:
I agree with the others; it's doesn't sound like the kernel is the problem. That sounds like something is corrupted in your ROM. Particularly since going back to a kernel which was good before doesn't fix it. There's nothing to be fixed in the next release since you are the only one having that problem.
[Captivate Android Development] AReynante:
I know that the amount you can OC/UV varies by the phone, but I have a question.

On my phone right now, my settings are:

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

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

Is it normal to have the higher states able to be UV more? Because if I raise the 400~1000 anymore, stuff freezes every now and then. Just wondering if I'm abnormal :p
[Captivate Android Development] existz:
Usually the higher frequencies need all the juice they can get, so they will most likely not be able to be UVd as much as the lower ones...

I usually run ...

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

150,125,125,100,100, 100, 75
[Captivate Android Development] AReynante:
I figured that, just because thats how it works. But I don't know why I can uv my 1120 state more then 400~1000.
[Captivate Android Development] Auridran:
For my UV I have the following:

100MHz: -150

200MHz: -125

400MHz: -75

600MHz: -100

800MHz: -125

1GHz: -150

1.2GHz: -100

1.4GHz: -25

So, I don't think it's uncommon to have some frequencies UV less on the lower end of things.
[Captivate Android Development] Dino.:
how were you able to test the stability of the intermediate states accurately?(as in knowing that 600 is stable at -100 or 800 is stable at -125)

*Cough* read my response above to see what i have run into:confused:

EDIT:grammar>.<
[Captivate Android Development] AReynante:
I turned off all of the higher states, so that it maxed out at 800, 600, etc.
[Captivate Android Development] Auridran:
Yup. This.

Testing 200 and 100 is painful :p
[Captivate Android Development] Shammyh:
I for one, always have to keep my 100 MHz step at -100 or lower (higher voltage) or else my phone will sleep to death. Yet I can usually get 200, 400, and sometimes 600 to be stable at -125/150.
[Captivate Android Development] johan8:
I dont' have sleep either sleep death or charge of death,

except phone will freeze with cam (camera or barcode)

Take some photos, change sence or effect.....quit cam....,

use cam again..... photo will freeze.

Tried No oc/uv everything default, phone also freeze after some usage of camera.

Changed to Speedmod, no more phone freeze.

I think the OC code has some problems.
[Captivate Android Development] ridethelight:
23hrs and 15 minutes sincle unplug and at 72% battery with light-moderate use.

Really liking this undervolting stuff

1200/-100

1120/-100

1000/-100

800/-125

400/-125

200/-125

100/-125

No sleep/charge deaths to date.
[Captivate Android Development] sjavvaji:
my new, more agressive, yet stable uv values...still cant increase the 100mhz uv because i get charge death if i do

100MHz: -100

200MHz: -125

400MHz: -150

600MHz: -125

800MHz: -150

1GHz: -150

1.2GHz: -100

1.4GHz: -25

im really starving the processor, aren't I?
[Captivate Android Development] psloan:
Best on-time i have gotten. this is with low-moderate use.

1200 -100

1000 -100

800 -125

600 -75

400 -125

200 -125

100 -125
[Captivate Android Development] elghouchd:
Paragons kernel VS this kernel?
[Captivate Android Development] froli13:
Never tried Paragons kernel but this one is GREAT on battery! You should give it a try! It's the best way to know wich one works best for you ;)
[Captivate Android Development] mgfjd:
I have the problem with the camera button switching between video and camera.
[Captivate Android Development] existz:
I need more info...oc'ing? uv'ing?
[Captivate Android Development] AReynante:
Hey existz, I just wanted to know, are there any major differences between #51 and paragon's OC kernel? Because they're both based off of speedmod.
[Captivate Android Development] TheMathMan:
Anyone know if this works on the Armani i9010?

I currently have the Ursa Minor ROM working on it but I know that was built from the original i9010 kernel.
[Captivate Android Development] existz:
Should have an update soon... I've started over from a clean source, removed alot of useless stuff, this build should be more stable than the previous ones..
[Captivate Android Development] froli13:
Great! I'm looking forward to this!
[Captivate Android Development] Barbarian:
Sounds great!
[Captivate Android Development] comdei:
is the suckerpunch icon from the movie suckerpunch?

just saw a commercial and it looks the same.
[Captivate Android Development] Auridran:
As was answered before, yes it is.
[Captivate Android Development] psloan:
yes please, can we have some more.
[Captivate Android Development] sjavvaji:
ur awesome
[Captivate Android Development] gordec:
Guys, I'm currently on dilli 6.0 with his stock dillpickle kernel. Really want to try this out with all the great reports on battery life.

1. Just wondering if I need to remove the lagfix before flashing suckerpunch?

2. Also any suggestions for which version I should try the 1000hz or 100hz and recommeded settings for the voltage.

3. What's current dilli ROM users' experience with SuckerPunch.

Thx
[Captivate Android Development] froli13:
The answers for your question 1 and 2 and mentioned in the first and second post of this thread.
[Captivate Android Development] gordec:
I read through post 1 and 2 few times. All it mention is that recommend ext4 lagfix. Doesn't say anything about whether you should remove the current one you have on or just apply over it. Sorry I'm not as android savvy as some people, I like to here very specific answers.
[Captivate Android Development] froli13:
Sorry I thought it was mentioned, my bad. To answer your question, if you come from an ext4 lagfix like voodoo or speedmod, no you don't have to disable lagfix.

And I would suggest you the 100hz version. It has less impact on battery life and doesn't make a big performance on performance.
[Captivate Android Development] doreyu:
1. no need to disable lagfix, they're compatible.

2. it really depends on your phone, start at -25 across the board and select [Apply for now]. Then increase it if it is stable. You can get away with UVing more at lower clock speeds, I am currently at 25,25,50,75,75,100 on his Voodoo kernel. I have been stable at 75,100,100,125,125,150 before. DO NOT apply the them as boot settings until your certain your phone can handle the settings.

3. couldn't tell you
[Captivate Android Development] Auridran:
The whole "you can undervolt more at lower frequencies" is a rule of thumb, not the only case. Many of us who have done extensive testing have found that some of the frequencies in the middle can't undervolt as much as lower/higher ones.
[Captivate Android Development] existz:
Cleaned up the OP some, easier to read... Also pulled downloads, will have an update soon, hopefully tonite or tomorrow morning.. rebuilt from clean source, removed alot of useless junk.. should be more stable.. Currently testing #53 (note- a few things might change from TEST to STABLE)
[Captivate Android Development] pizz0wn3d:
woot!

Can't wait.

Herp derp Captivate XDA app.