yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] slaman:
I always get sleep deaths... and lately, charge deaths, and I have no UV for 100MHz and 200MHz... I only have -25mV for 400MHz, which I'm going to move to 0... 600MHz is only -50mV.

I need to stop the sleep deaths - it's making my phone almost unusable since it happens several times a day.
[Captivate Android Development] ccdoggy:
you could disable the higher states so that it only does 600, 800 and then stress test it for stability. i am thinking that might be the correct way of doing it.
[Captivate Android Development] ulupinar:
Lucky for you. #46 just killed my battery. Previously, I was on #45, and idle mode battery drain was ~ 2%/hr, when I tested it overnight. Then I installed #46, and my battery started draining at ~10%/hr, idle no usage!

I could not find earlier versions of the kernel, there is one link in OP, but the link has versions up to #40. Where can we get versions before #46 but after #40?

Thanks
[Captivate Android Development] froli13:
Just PM'd you
[Captivate Android Development] aalh:
till you have the cause tracked down use Captivate Keep Alive from the market

Have you heard of it?

worked for me but my phone has stopped the full bat shutdown since flashing some of the roms, dont know what stopped it but I quit having the problem and dont even have CKA installed anymore

wish I could be more specific
[Captivate Android Development] bsc7080xsc:
This might be stupid question... but do I need to disable the lagfix and/or go revert back from ext4 to rfs for system and data partitions when applying new builds ? I have been doing this for previous builds and wondered if I making it hard on myself unnecessarily.
[Captivate Android Development] Auridran:
It's unnecessary.
[Captivate Android Development] bsc7080xsc:
Thank you.
[Captivate Android Development] aalh:
#46 -no gps, flash back to #44 and gps works again

Was using #46 and had no GPS

I would see one sat and never lock

I just flashed back to #44 and I have 6+ sats and good locks

that was the only thing I changed

was it the reboot or the backflash?

in both cases it was the 100hz version
[Captivate Android Development] itdiestoday:
That's about what I get as well at the same oc.

Sent from my Captivate
[Captivate Android Development] slaman:
I remove the UV for all frequencies less than 600, and only use -50mV fire frequencies above that up to 1400 MHz. It's been good for about twelve hours with two charges and no deaths.

Like someone else posted though, my isle battery drain is 8% an hour with #46...used to be 4% an hour with previous versions albeit with more aggressive UV
[Captivate Android Development] hamburgertrain:
I always got pretty aggressive sleep death with this kernel, even with lowering the UV to -25 on each frequency. I'm not sure what to do to fix it, it could just be my phone though.
[Captivate Android Development] lrs421:
What clock speed?
[Captivate Android Development] hamburgertrain:
1.3 10char
[Captivate Android Development] lrs421:
Try lowering your clock speed. Your phone may not be able to handle that high of an Oc. Mines can't.
[Captivate Android Development] Nuskul:
Does anyone know the last # kernel to use k12t or k12u, performance has been great but my battery has been lacking since k13, using hardcore's or exist's kernel. Keep up the great work.
[Captivate Android Development] existz:
The only thing I used from hardcores k13 was adding the option to select color profiles, that has no impact on battery life...mine is similar to hardcores but its not exact, I don't use all the updates that Hardcore puts out, I just cherry pick what I want...the only full patch I used from hardcores was K12P, that's the last version I used of his, even since then I really haven't added much updates from hardcores..

Sent from my Captivate
[Captivate Android Development] slaman:
Not sure if this was directed to me but I'm running at 1400...got another sleep death so now I've removed all UV below 600 and set 600 at -25mV

Sent from my Samsung Captivate SGH-I896
[Captivate Android Development] slaman:
Trying to take a bunch of pictures and freezing after each one! I now have only -50mV for the higher frequencies...

Sent from my Samsung Captivate SGH-I896
[Captivate Android Development] existz:
Should have a new version up today, so far testers say the frequency code is more stable, more consistent, but you might have to adjust your UV ..I pulled some code from eSPyel, so big thanks to him... also using a different toolchain, so hopefully it fixes a few things...should have it up soon

Sent from my Captivate
[Captivate Android Development] lrs421:
You guys should really lower your clock speed. 1300/1400 is unstable for a lot of people. UV alone isn't going to fix your charge death if your clock speed is too high. Try 1120 or 1200.
[Captivate Android Development] hamburgertrain:
I'm not getting charge death, I'm getting sleep death, and it runs perfectly stable otherwise.
[Captivate Android Development] lrs421:
Sleep death translates to instability. It wouldn't hurt to live with a lower clock speed for a couple of days to see if things improve.
[Captivate Android Development] hamburgertrain:
Just set it down to 1.2 which has always been stable with other kernels, and got sleep death. Whomp :/
[Captivate Android Development] itdiestoday:
Changed back to the 500 edition. Bogomips show 1182 in stability test where as the 1000 version showed 1161. Think im going to stick to the 500 for now

Sent from my Captivate
[Captivate Android Development] existz:
Just want to point a few things out real quick. An unstable OC/UV causes sleep/charge death, if it was the kernel alone causing it, it would happen to everyone... so even if it passes a 100 passes in StabilityTest you can still get charge/sleep death, its the OC/UV... this is why I don't use these, or atleast go by them, all that most stress test does is test at max clock, so if your lower frequencies is unstable, your not going to know it, I've posted numerous times how to test these...so if you get charge/sleep death and can pass all stability test (all your doing is passing that test at max clock) you still need to lower your OC/UV.. this is why I don't support OC/UV, only add it as an option. This has been discussed over and over.. So unless its happening to everyone, or almost everyone, check your settings.

Sent from my Captivate
[Captivate Android Development] hamburgertrain:
On glitterballs kernel I could easily crank everything down without sleep death, while I can't using this. Just thought i'd point it out, It seems lowering my undervolt has fixed it for now, but just something I noticed.
[Captivate Android Development] lrs421:
GB kernel isn't built exactly the same, the code varies so the OC/UV varies.
[Captivate Android Development] sicmadek:
Why run 1.3 or 1.4? Yea phone scored higher quadrant and linpack with it but for everyday use i notice nothing over 1ghz.
[Captivate Android Development] existz:
*UPDATE*

Build #48

-Updated frequency code (should be more stable) (thanks eSPyel)

-Changed toolchains to 2010.09-51

NOTE since I changed the frequency code, you might have to adjust your OC/UV settings....Also I will only have 2 versions in the next release, so let me know which you prefer, the 500hz or 1000hz version
[Captivate Android Development] froli13:
Downloading XT-1000hz now! Thanks for you hard work on this great kernel!

What are you planning for future releases?
[Captivate Android Development] lrs421:
Got the non XT version up and running. Will report back later.
[Captivate Android Development] existz:
I also want to clarify something. When I say the updated frequency code should be more stable, what I mean is, is it should be more consistent and reliable..(NOTE I said "should"). Its not meaning that you will be able to get a higher max clock, ...which you might actually be able to, or you might not be able to overclock as high as you could before...so you might have to lower your OC or UV ...this should make the kernel overall feel more 'solid'

Sent from my Captivate
[Captivate Android Development] roadrash7:
Which kernal is the 100hz one i see three on the op and i know its not the 1000hz one.
[Captivate Android Development] shaolin95:
That key your is YOU.

You may not needed but others do, like for example for my emulators. ;)
[Captivate Android Development] existz:
The non-xt one...

As stated in OP..

Non-XT-- kernel hz=100hz user hz=100

XT version-- kernel hz=500 user hz=150

XT-1000-- kernel hz=1000 user hz=200

Sent from my Captivate
[Captivate Android Development] apparition:
Got unplug/plug reboot this morning with #46. I flashed #48 XT (500Hz) just now. See how that goes at 1.4ghz

Sent from my SGH-i896 on XDA app
[Captivate Android Development] sicmadek:
Must of the clocking that high dont play emulaters all day. Their phones just on a desk or in a pocket while at work. The option is nice but im just saying it isnt a must.
[Captivate Android Development] lrs421:
I have to agree, Shaolin is a beast and needs the speed :) a lot of others just want to see how fast angry birds can open.
[Captivate Android Development] existz:
The way I see it is, if you actually do use cpu intensive apps/games, then overclocking helps alot, but if all you do is surf the web, listen to music or text, then you don't need to overclock..you will never see a difference... When I do something that needs extra cpu power, I will set it to 1300-1400, but when I don't need it (95% of the time), im just using 1000mhz.

Sent from my Captivate
[Captivate Android Development] froli13:
I think 1200mhz is a good balanced OC for those who just want some extra power. It's good for games, everything is a bit faster it and doesn't decrease battery life that much if you have good UV settings.
[Captivate Android Development] roadrash7:
Thanks sorry i missed that.
[Captivate Android Development] existz:
No prob, its easy to overlook...next version will only have 2 versions, 100hz and a XT version, still deciding on which one to keep, 500 or 1000

Sent from my Captivate
[Captivate Android Development] lrs421:
I've grown really fond of the 100 version clocked @ 1200. Perfect blend of speed and battery life for me.
[Captivate Android Development] lrs421:
Time to go buy the wife something for Valentine's day. I'll play with my phone on line :)
[Captivate Android Development] existz:
Yea the 100hz version will stay no matter what, I only use it, it gives the best battery life plus great performance

Sent from my Captivate
[Captivate Android Development] b0wz:
Truly is here, I can crank it up to 1400 for fun, bust out 19+ linpack scores, 18-1900 quadrant scores (useless i know) and 55.6 neomark scores.......but at 1200 with small uv's.....battery life just rocks...on the non XT 100hz version....and its still wicked fast for full animations on the cosmic themes.
[Captivate Android Development] eSPyeL:
existz,

Hope the updated code helps out! :D
[Captivate Android Development] apparition:
When browsing media heavy sites with flash, the extra OC makes a huge difference --it makes things smooth. 1.0 to 1.4ghz is a huge difference. 1.2 is probably the best balance though since the extra OC to 1.4 from 1.2 is pretty marginal browsing performance wise

Sent from my SGH-i896 on XDA app
[Captivate Android Development] sicmadek:
im just tired of seeing people complain cuz they went from 19 down to 18.5 linpack. big whoopdy do! you wont see any difference of .5 linpack when playing any game.
[Captivate Android Development] lrs421:
Currently running 1200/100 with modest OC

75

100

100

100

100

100

125

This thing is sipping battery. Great work!
[Captivate Android Development] Rrryan2:
To some degree, yeah. Benchmarks are far from everything and are not necessarily going to translate directly into user experience.

But they can still be at least semi-useful as a basis for comparison when gauging the effectiveness of successive changes to the kernel.
[Captivate Android Development] ridethelight:
I dont have to delete volt_sched every time I update the kernel do i?
[Captivate Android Development] existz:
No, not unless I change the order of the frequencies, i will always let you know to delete it when I post an update
[Captivate Android Development] ridethelight:
Cool, thanks.

How would I even do that anyway? I looked for the file and couldnt find it.
[Captivate Android Development] nybmx:
Either by deleting your settings in the voltage app (using the 'remove boot settings' option) or by using something like rootexplorer.
[Captivate Android Development] slaman:
Will try that... I left the house today at 11 with full charge... used the phone for about 10 minutes of calls, two sleep deaths (lowered UV settings), about 10 photos (four freezes, lowered UV settings more each time it happened), a little bit of browsing about 45 minutes of GPS, and it died at 6PM.

Looks like I'm going to try to the 100Hz version and cap my OC to 1200Hz... will keep my UV settings unless I see more sleep or charge deaths.

Even though existz provided a way to test stability (cap max frequency to 600Hz and test UV settings using Stability Test), I still got sleep deaths for the lower frequencies despite the passed tests. I simply can't UV any of the lower frequencies.
[Captivate Android Development] lrs421:
Good luck. Getting it right can be a Pita
[Captivate Android Development] sjavvaji:
hmm...nice idea
[Captivate Android Development] existz:
Off Topic

For those of you interested, I just started working on a JL1 2.2 Voodoo based kernel...I just now started messing with it so it will probably take me awhile to get it built the way I want it...im doing a few things different than SuckerPunch, but battery life is also the main goal with it as well...once im ready, ill let u guys know

Sent from my Captivate
[Captivate Android Development] opcow:
Cool. I did a couple of personal JL1 ULK and Voodoo builds but just don't have time to go further. I'll be looking out for this.
[Captivate Android Development] byrdtulsa:
im new to flashing kernels .. i have phoenix rom and 1st wanted to know if it will work with this and also whats the diff. between the 3 downloads on the page...
[Captivate Android Development] aalh:
It works fine

I have been using SP with Phoenix since #30 or older

The diffs have been covered previously

and better than I could restate

use the SGS kernel flasher for a painless swap

dont even need to disable lagfix, when flashing from the included Phoenix kernel (Speedmod)
[Captivate Android Development] Rrryan2:
Sweet! DonkeyPunch is on the way!
[Captivate Android Development] aalh:
I vote for *****Slap kernel
[Captivate Android Development] kytrauma:
Edit post is a reply to slaman's

If you are getting more than 2 or 3 sleep deaths a day it is most likely a hardware issue. I just had my cappy replaced due to this.

I called ATT and any phone made before nov '10 has the possibility to develooe this issue and it us a known problem. My old cappy worked perfect for 2 months then started doing this and it got worse pretty quick.

Att gave me 0 hassle about exchanging it.

Btw lovin my new one. OCd to 1400 where as my old one didnt even like 1200. Lol
[Captivate Android Development] slaman:
Interesting! I bought the Captivate because of the internal sd issues with Bell's Vibrant, so I really hope this phone doesn't have a hardware issue... Don't think it does since I haven't seen the issue when I don't UV or use a different kernel.

Sent from my Samsung Captivate SGH-I896
[Captivate Android Development] kytrauma:
If you dont have the issue on any other kernal then ignore my post. If you change kernals and it persists then look into getting an exchange.
[Captivate Android Development] elghouchd:
Is the XT 1000 version supposed to get 20 mflops in linpack?
[Captivate Android Development] existz:
No, I redone most of the code, there was one piece of code I used for 1400mhz in a test version that would get 20mflops consistently, but it wasnt as stable, so i used a different code..so its probably going to bench lower, probably 19-19.5
[Captivate Android Development] Dlev7:
Hey Existz, Im on build 45 XT 1000 version and its great super stable and OC'ed to 1.2 never gotten COD or Sleep death but I am getting a little less battery life.

Not saying its bad battery life but that being say today I had good battery compared to what I used to have, that being said with build 30 (s) at the 500 I would get anywhere from 30-40 hours of just good use.

So what would you recommend here for build 48: Non-XT, XT, XT 1000?

I am OC'ed to 1.2 and am not a heavy user, I like having the nice speed bump when using apps, texting, email, and music, but I like battery. So Im staying at 1.2 cause please not im getting good battery but which of the three would your recommend.

Besides that GREAT kernel.
[Captivate Android Development] existz:
I personally recommend non-xt (kernel hz=100 user hz=100) it provides the best battery life, and performance is great.. some users have ditched 500/1000 and now using 100hz, but it varies in different situations, but overall 100hz version is the best battery/performance ratio between the 3 imo
[Captivate Android Development] Dlev7:
Alright thanks im going to try it out. No need to delete the voltage or change anything right?
[Captivate Android Development] existz:
You dont have to, shouldnt cause any problems..but do note that I changed all of the frequency code, so you might have to adjust your OC/UV..so if you are not able to set a certain UV or max clock as before, this is why..
[Captivate Android Development] xbeamelite:
Just noticed this, not sure if anyone else has getting either fc or video player freezing. On build #46. Dont know if this is kernel or due to the oc uv. on 1.2, with -50 uv across the board..trying 48 to see if it makes a diff
[Captivate Android Development] Dlev7:
Just flashed 48, the 100 HZ one and your completely right, I obviously cant comment on battery life but there is no difference at least in my mind with me using it. I also lowered my OC down to 1.12 as I realized that I dont really need that much of an OC, and I cant tell the difference in battery life.

Everything seems the same, and Im assuming that the combination with the non XT version of Build 48, with only a 1.12 GHz OC with -50,-50,-75,-75,-100,-100,-125 settings I should see a good increase in battery life? Right? : D

But as I said previously this this still flies!!!

EDIT: This is also something really funny, Im getting 15.8's to 16 on linpack, and I lowered my OC and changed to the 100 HZ. Existz this is the best! haha. Ill comment later on battery life once I use the phone
[Captivate Android Development] existz:
I personally can tell a difference in the non xt version over the xt's in terms of battery life, before I even released this kernel, I was using 100hz, its always gave me the best batt life... but remember, usually after flashing a kernel, give it a couple charges to settle in, if something changed in the battery calibration, it will calibrate itself over some time...so if you don't see a difference right away, or even if its worst right off, give if some time to recalibrate...flashing different kernels/roms can cause it to mess up the calibration. But you should see a difference, atleast I do

Sent from my Captivate
[Captivate Android Development] existz:
Its not the kernel, if it was, everyone would be getting it...anytime there's a problem, and its not happening to everyone, then something else is causing it..check your oc/uv

Sent from my Captivate
[Captivate Android Development] xbeamelite:
I just flashed 48 still happening. Freezes then fc. Its only when I'm playing 720p version of top gear (mkv). When I'm playing a dvd version of italian job its ok. Any explanation you can think of? Don't know why uv would only affect certain files. Loving the kernel otherwise.
[Captivate Android Development] existz:
Yea, unstable OC/UV might not be the problem since its only a certain file.. Does it happen with other kernels..or just mine? It could be a rom issue also.. but ill look into it and try to play some mkv's and see if I can reproduce it
[Captivate Android Development] xbeamelite:
I havent noticed it on any other kernel, but then again I'm not always playing mkv files, just happened to watch and notice it now. Running phoenix 4.5. Everything else on the kernel is amazing, from batt life to speed. Thanks for an awesome kernel.
[Captivate Android Development] xbeamelite:
The mkv is on my external sd, could that be the problem? The other vids I tested are in the internal sd... Trying to play a 720p from external you think could b the problem?
[Captivate Android Development] johan8:
I don't think it will be any problem playing media from external SD.

Actually you can simply rename MKV to MP4, then you can play it with internal player.

However if it contain DTS soundtrack, you need to install 3rd party player.

I always watch Fringe season3 720p on my Captivate without any problems.
[Captivate Android Development] johan8:
Voltage Control

Basically I haven't any problem with SuckerPunch kernel, this kernel is great !

However the voltage reading is missing in 600 1.3 1.4Ghz.

Is it something wrong ?
[Captivate Android Development] nybmx:
Nope. That's just how it is. Don't worry about it. Those frequencies can still be undervolted fine, they just don't display properly in the app.
[Captivate Android Development] bsc7080xsc:
Off-topic I know, and if there is a link to point me to ...great.

So I go to trade my phone in, I want to start off right and collect the following before flashing back to custom setups :

- Device Id

- Unlock code ?

- esf folder ?

- ?
[Captivate Android Development] gibson3659:
Perception

Is there anyone using this on Perception? I have a lot of trouble booting this kernel as it usually freezes during or immediately after the media scan. I've even had it freeze on CWM. I've tried no tweaks, no voltage settings, 0 uv/oc, and various uv/oc setting on the top end. Nothing I do will make this boot consistently. It is great when I do manage to boot it. Until I figure it out or it gets resolved, I can't use it.

Are there any logs I could provide that might help fix it?
[Captivate Android Development] mark1962nc:
This kernel is awesome....works great for me!

Originally oc'ed to 1300 and it seemed to work fine, until I experienced a freeze while updating multiple apps simultaneously. Stepped down to 1200 and haven't had any issues since.

I've followed Shaolin95's mini-overclocking guide which was extremely helpful!
[Captivate Android Development] sicmadek:
Ok so twice now this has happened. When the phone is booting up to the point where it starts the media scan it just freezes. I slide to unlock then it says system is not responding. About 30 seconds after i click wait it does everything like it supposed to. I have no undervolts or overclock.

Also i have lagfix on.
[Captivate Android Development] apparition:
I still get -2% charge immediately after I unplug my phone from 100% fully charged on #48 xt. Any ideas on why?

Sent from my SGH-i896 on XDA app
[Captivate Android Development] xreflection:
I have similar issues with my launcherpro install with lagfix on the speedmod kernal. I believe it has something to do with the conversion to ext4. Before I convert to ext4, i have no issues.

That has been established as a battery preservation feature of android phones (and most modern electronics for that matter). Its to prevent overcharge if the phone is kept on the charger for extended periods of time.
[Captivate Android Development] shaolin95:
I honestly have not been using any lag fixes with 2.2.1 based ROMS. I have yet to see anything that they do to help and in fact I feel it gets worst with the lagfixes...for example the gallery (I have tons of icons and wallpapers) stutter a lot with ext4 for me at least.

Also note that for me, letting the ROM install ext4 then convert back to rfs does not work fine...if I install the ROM directly with RFS then it works great for whatever reason.