yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] ccdoggy:
I vote lose a few megs for not making it look like its going to lock up and die. Really had me scared the first few times i saw it.
[Captivate Android Development] lrs421:
Hmmm. I've only seen it for a split second when going into recovery. Not during normal reboots.

I say leave it alone. Afraid it will break my wifi :)
[Captivate Android Development] airbillion:
I like the extra ram. Who cares about the att boot screen. It only happened once for me anyway.
[Captivate Android Development] IStern:
Mobile AP is still iffy for me...most of the time it errors out connecting packet service.
[Captivate Android Development] zerkai:
Doesn't show up in Speedmod, but that's probably because it doesn't have a SuckerPunch logo to transition to
[Captivate Android Development] Auridran:
Keep it. I haven't even noticed this.
[Captivate Android Development] airbillion:
existz,

Hardcore had released the final version of k13a. Has he posted the source yet? Maybe an update soon?
[Captivate Android Development] Nuskul:
Good Morning, I'm sorry to inform you that I had charge death last nite. I went over 24 hours, still had about 25% left and used it heavy, best battery life I've seen. My phone doesn't seem to like UV, i cant go more than -25 across the board, using stability test will crash after 5-6 passes. Any suggestions? Using #39
[Captivate Android Development] olo567:
Run stability test with no UV and 1000 max clock. Then undervolt from there. Try not adding higher frequencies until you can get the stock clocks stable.
[Captivate Android Development] opcow:
Same here. Didn't have it with #36 and earlier.
[Captivate Android Development] lrs421:
Try what I did. In the tweaks menu enable ipv6. Reboot. After rebooting go back into the recovery menu and disable it. This was the only kernel version that tweak worked with.
[Captivate Android Development] aalh:
using #40 100hz

Phoenix 4.5 rom

battery is doing great, less than 1%/hr while I was sleeping

1400 1300 1200 1000 600 200 100

0 0 0 -50 -75 -75 -75

I will see how it does at work today and report back
[Captivate Android Development] wonner:
Yeah, didn't have it on #38 either. Not a big deal to me though.
[Captivate Android Development] tiuk:
When I tried this kernel I flashed with cwm, booted up fine, but when I later rebooted was stuck in a constant boot loop; had to reflash my previous kernel.
[Captivate Android Development] ryude:
Did you set your undervolt settings at boot? That can cause boot loops if your settings were unstable.
[Captivate Android Development] existz:
Running a test version now (just making sure nothing weird happens), should have it posted later today, as soon as I get home ill upload it
[Captivate Android Development] lrs421:
Cool. Have you decided to keep the 350mb version?
[Captivate Android Development] tiuk:
I believe I did; they were the same as I had used with glitterballs so I didn't think anything of it. Thanks, going to try flashing it again and being more cautious.
[Captivate Android Development] ryude:
You can't undervolt this kernel as much as others due to the way he tweaked it.
[Captivate Android Development] existz:
As of right now im keeping it, we will see how it goes in this build, then if you guys would rather go back to the 340mb i will, i want to see if your mobileap/wifi still works in this build, kind of curious about it
[Captivate Android Development] lrs421:
Trust me, if it doesn't work I'll let you know :)

Thanks again for EVERYTHING!
[Captivate Android Development] Grandelama:
@Build 40 500hz

It seems that my phone doesn't like UV so much, in particular on slower frequencies..

I have found my "stability" with:

1200 1000 800 600 400 200 100

-50 -75 -75 -100 -100 -50 -50

anything less = COD

Battery is doing -2.5 % per hour with light usage and 5 widgets with data download and update interval 3 hours, little more than -1.6 1.7%/hr while sleeping
[Captivate Android Development] justmart:
You guys that reported great battery stats... Are you using 100hz or 500, because I have 500 and my.batt has drain fast.

Sent from Puerto Rico
[Captivate Android Development] davwman:
100hz

Ryude's Precision v2.0

Suckerpunch Latest

Jk3/Jl2 > Long Island area

Ryude's Amazing Monochrome
[Captivate Android Development] justmart:
Thx! Will try that now.

Sent from Puerto Rico
[Captivate Android Development] AJerman:
Has anyone targeted a certain setting for wake lock caused by OC/UV? When the phone is asleep, I can only assume that it's going to spend most of it's time at the lowest speed step possible. Should we look to that step's voltage settings in the case of wake lock? I'm getting wake lock with the latest kernel still, and I didn't have it before, and since I'm using the same voltages for all steps aside from 1280 being changed to 1300, I'm not sure what to look at.
[Captivate Android Development] ulupinar:
I am using #40 with di11's 5.6 ROM.

Wifi fails to get the proper IP addresses from AP sometimes. I have to turn WiFi off and on again. I used to have this issue with stock 2.1. I never had it before with 2.2 ROMs. I do not know if this is related to your 340 vs 350 MB memory allocation.
[Captivate Android Development] lrs421:
I don't think existz was directly implying a relationship between the two. There certainly something going on with mobile AP and wifi. Did you try the tweak I mentioned above?
[Captivate Android Development] existz:
The wifi/mobileap problems started after adding IPv6 privacy extensions. If you have ipv6 privacy enabled, disable it, if you don't have it enabled try going into recovery and enable it, reboot, then go back to recovery and disable it, Seems to fix it...thinking about just disabling it all together since its caused more issues than its worth

So far the only issues from 350mb is a tiny amount of random snow when it transitions from att boot screen to kernel boot screen, but I think I can fix it and keep the 350mb
[Captivate Android Development] tiuk:
Is it possible for a kernel to disable logcat? Because I can't seem to view it with any app now.
[Captivate Android Development] ulupinar:
Thanks for the info. The wifi seems to be working for now. But I have to test it more, as I had the issue intermittently.

Thanks
[Captivate Android Development] lrs421:
Its listed in the op. Android logger has been disabled. You can enable it in the recovery mode.
[Captivate Android Development] WickedNite:
Does restoring to stock and doing a master clear affects the performance of battery life? It's been a while since I've done that and I wonder if it will help my battery life lasts longer. My battery now doesn't lasts for 12 hrs, that's moderate usage. For some people that shared their experience, it seems that their battery lasts more than 12 hrs. And I envy them. Lol.
[Captivate Android Development] existz:
*UPDATE*

Build #41

-Neutral/Cold/Warm color profiles now selectable from Recovery

-Option to disable darkest auto-brightness level from Recovery
[Captivate Android Development] elghouchd:
Does anybody know if there is like an "ondemand" scaling for the Voltage App, or if there are scaling options?
[Captivate Android Development] lrs421:
Is neutral the default?
[Captivate Android Development] elghouchd:
What are color profiles? Sorry for the very noobish question?
[Captivate Android Development] lrs421:
Yes it is :D answered my own question.
[Captivate Android Development] lrs421:
Image tweaks. Nuetral is balanced, Warmer adds a little more red to the screen(almost cinema like) and Cold/Cool adds a little more blue. To each his own.
[Captivate Android Development] existz:
Now that charge death is some what under control, added color profiles and finally set on oc/uv frequencies I can concentrate on the wifi/mobileap issues...(unless something else comes along).. hopefully they are totally fixed in the next build.
[Captivate Android Development] zerkai:
Is snow fixed in this one?
[Captivate Android Development] lrs421:
Sounds great. I too think it's IPv6 related, just not the way I thought. I flashed the Kernel with IPv6 disabled and got an error message on the mobileap, I went back into recovery and enabled it and mobileap connected immediiately. I then tried it twice more with the same result, what's bizarre is that it worked the other way around in build 40. Atleast we know what's causing it, IPv6.
[Captivate Android Development] lrs421:
It's still there. Existz says he may be able to fix without tossing the 10mb :)
[Captivate Android Development] existz:
Nope its still there, its due to the 350mb settings, I made a version with 340mb settings and its not there, if I change it back then it happens again. Its not going to cause any issues, just looks ugly the split second its on, im going to try a few things and if I can't fix it, then its up to u guys if you want to keep 350 or go back to 340
[Captivate Android Development] existz:
Yea its the same for me, has been since I added it in, seems sometimes it acts like it gets stuck or something, but since everything else is out of the way I can work on it, if I can't fix it I will disable it in the source, im clueless as to why its doing this ..

Also in the next version im going to mess around with trying a kernel hz=1000hz version, I've seen some kernels trying it without issues, also will play with jumping the user hz up to 150 or 200hz (if theres no side effects)
[Captivate Android Development] elghouchd:
Hey existZ,

Will anything get wiped off my phone when i update to build 41? Do i have to do anything before i update? Thanks :)
[Captivate Android Development] existz:
No, updating to a newer verion will not wipe anything. If you was on a different kernel, or on any SuckerPunch kernel before #40 then delete your VC settings, delete the file S_volt_scheduler in /etc/init.d ..
[Captivate Android Development] existz:
Im going to open this up to the public, im messing around with trying kernel hz=1000hz, and with different user hz at 150hz and 200hz (default user hz=100), if all goes well this will replace the 500hz version. Since theres so many different things that could break, with just one person..or even a few, it would be easy to overlook something..so everyone is free to try..(NOTE- these are TEST versions, they may or may not cause some issues, so only use them if you know what you are doing and you know how to fix it if somethings goes wrong)...there will be NO SUPPORT for these, im just taking bug reports right now.. to test, join my IRC channel, #suckerpunch, theres a web link in the OP for those that dont use IRC...The link to the TEST versions are in the TOPIC, so read it! ...as of right now i only have 1000hz-150hz version up, im working on a 1000hz-200hz version and will post it later...remember there is NO SUPPORT for these, so use at your won risk

If you DO find a bug, report it in the IRC channel, NOT in this thread please!...i always discuss my test versions there, so if there's a problem let me know there and ill get back to you as soon as I can.

I've been running 1000hz-150hz for a few and its smooooth... no initial problems, so far so good
[Captivate Android Development] DrDubzz:
quick question, if I don't alter anything in voltage control, this kernel will default to max speed of 1000 right?
[Captivate Android Development] existz:
Correct, all versions default cpu at 1ghz (stock)
[Captivate Android Development] sjavvaji:
I don't see it yet...is it up?
[Captivate Android Development] RonH54:
I am presently on #41 with States 1300,1000,800,600,400,200,100. I going to give 1400 by dropping 1300 but keeping the other states. Is it OK to make that big a jump from 1000 to 1400 or should I have another State in between 1000 and 1400 and drop a Lower State to stay in the 5-7 range for States?

Thanks
[Captivate Android Development] ulupinar:
Yes I did apply the fix you mentioned. However, I still have the WiFi IP address not assigned probperly issue. I need to turn off and on wifi again to get a proper IP address. This may not be related to the kernel though. I think the problem started with di11i's rom. I am not sure though.
[Captivate Android Development] lrs421:
That's weird. You may want to assigning a fixed IP address. This worked for me on eclair
[Captivate Android Development] existz:
Looks like I forgot some info in the change log, in #41 it also includes some modified tweaks to the kernel scheduler...so the actual changelog should look like this...

Build #41

-Neutral/Cold/Warm color profiles now selectable from Recovery

-Option to disable darkest auto-brightness level from Recovery

-Kernel scheduler tweak modified (improves GPS response)

-Updated initramfs
[Captivate Android Development] elghouchd:
Is there a color profile which takes the blue tint off my phone?
[Captivate Android Development] crazililazn:
Choose warmer.
[Captivate Android Development] existz:
Yea just use the warmer profile

-If your screen is to 'blue' then use the 'warmer' color profile, as it makes it more yellow/red to even it out

-If your screen is to 'yellowish/red then use the 'colder' color profile as it makes it more blue to even it out

-If you can not tell a difference between the 2, or want something kind of in the middle then use the neutral color profile
[Captivate Android Development] existz:
Yea its up, check the IRC channel for the link
[Captivate Android Development] elghouchd:
Oh no first random reboot

Edit: another one

Guess im going back to 40.
[Captivate Android Development] lrs421:
The phone shutdown or reboot? What were you doing? What exactly occurred?
[Captivate Android Development] zerkai:
Don't know what it is, but my battery finally doesn't drop from 100 to 97-98 anymore after unplugging. :)
[Captivate Android Development] elghouchd:
It was a shutdown, and on my first one i unlocked my phone and went to the app drawer, then shutdown. On my second one, i was running the psx4droid and then BAM.Shutdown. Could setcpu be causing it? Im using that for my CPU stress test cause i dont know any other app that does a stress test.
[Captivate Android Development] lrs421:
Don't use setcpu and check your UV settings. Stability test has been a reliable stress test since its recent update. Check the market, after you check your settings. There's an oc guide in the op. Start there.
[Captivate Android Development] existz:
Sounds like your OC or UV is unstable, cause if according to what you described, its happening when you put stress on the CPU, so something there isnt 100% stable. Even if stress test says it is, cause with those stress test it usually just maxes the cpu out and test from there, as in the real world, with the conservative governor, it increases and decreases the CPU speed rather than jumping to max speed, so when you went to do those things it could have been at 800mhz for example, and if its not stable when being used at that speed, due to low voltage or whatever, its going to crash, as if you are running a stress test at 1.2ghz or whatever, then its not going to stress the other steps. Try lowering your OC/UV
[Captivate Android Development] elghouchd:
Ok thanks, gonna delete SetCPU, and use the new stability test (was using v1.2 and i heard that it was unreliable but now there is a 1.3 so im gonna use that). Thanks!:D
[Captivate Android Development] lrs421:
Try what existz posted above as well, clock speed may need adjusting also.
[Captivate Android Development] elghouchd:
So i added the warmer profile cause i have the blue tint, but i dont think the tint is gone. Compared to my friends iphone 4 my phone still looks a little blue (i see a little difference). Do you think the warm profile should have removed the tint? Maybe there is no difference and i just feel like there is because i installed the profile it should be better and i am hallucinating it (placebo effect)?
[Captivate Android Development] existz:
Its not going to remove it completely for some users, hardcore just made a color profile adjusted to be more 'warm' the only way you will be able to get it perfect is to modify the color settings yourself in the source code

The profiles do work, when I set the cold profile, when booting I can see the SuckerPunch logo change colors to the colder profile, so I know it actually changes it
[Captivate Android Development] elghouchd:
Weird i just got a "Process System is not responding" message after booting up my phone.
[Captivate Android Development] Auridran:
Just wanted to post another update on my battery life:

2 days, 7 hours at 34% battery.

Over an hour of screen time, texting for most of that screen time.
[Captivate Android Development] DOAlaboratories:
Finally hit 1400 stable with build 40! :D
[Captivate Android Development] crazililazn:
I get it randomly too. However, it doesn't cause problems, the phone still boots fine. Would be nice to have it fixed though :D
[Captivate Android Development] aalh:
as meaningless as it is, I just topped 2000 on Quadrant for the first time

had to share

no other kernel has done that
[Captivate Android Development] existz:
I've yet to have 1 system process not responding or FC. Try clearing dalvik cache. There's something else causing this, if it was because of the kernel alone, it would happen to everyone, there's another factor in there somewhere... also, I know I sound like a broken record, but unstable oc/uv can cause this, as well as causing corruption which can cause this to...which im not saying the kernel is not part of it, but the kernel + something else is could be the problem
[Captivate Android Development] slaman:
I keep getting sleep deaths / shutdowns with no OC and an UV of -50 across the board...will move to -25...kind of sucks to not be able to Uv
[Captivate Android Development] jjtitus098:
How in the world did you get that good of battery?? That is rediculous. Did u even use your phone? Lol

Sent from my Captivate running Precision v.2.0 with SuckerPunch @ 1200mHz.
[Captivate Android Development] Auridran:
Like I said, over an hour of screen time and most of that time was spent texting. An hour of screen time for texting is a buttload of texts :p
[Captivate Android Development] WickedNite:
I wish my phone would do that for me. I can't even make it lasts for atleast 12hrs with moderate usage. I'm uv heavily and just using 1120mhz. Woosh.

Sent from my Muscles using Brain Cells
[Captivate Android Development] Grandelama:
Is a battery calibration needed/advised after every new kernen flash?
[Captivate Android Development] existz:
Not really, it usually recalibrates itself to an extent after 2-3 days of use anyways, i flash probably 10-15 kernels a day without any problems

EDIT -(off topic)

Also for those of you who want to see how long each step is being used without having to buy SetCPU or some other app, type this command into a terminal emulator or adb shell..it will give you a list of how long each step is being used

cat /sys/devices/system/cpu/cpu0/cpufreq/stats/time_in_state
[Captivate Android Development] pizz0wn3d:
10-15 kernels? Holy **** that has to do terrible things to your battery haha.

Do you know of any apps that maybe monitor your cpu over time and show how much of that time is spent at each step? I'm about to go look for something like that in a second, but a recommendation would be nice if you know of any.

Herp derp Captivate XDA App
[Captivate Android Development] froli13:
I wish I could UV as much as you do!
[Captivate Android Development] justmart:
Are you serious??? Last night my battery drop from 81% to 40% in 5 hours... Wifi OFF.

I'm running Srendipity 4.3, JL2, and Version #41 with cfq @ 1ghz

UV 100 200 400 (-150) 600 800 1000 (-100).

Pics!! or it never happened.
[Captivate Android Development] itdiestoday:
Im having an excellent time with this kernel. I don't think ill ever get battery life because my commute will wreck any battery life I feel I may have until the weekend

Currently 1200—100.

-100, -100, -100, -100, -100, -125, -150

Can't seem to make it fail or crash. Get tue feeling im doing something wrong. Ran over two hours in stability test with no errors. Also no errors or fc in neocore/linpack/quadrant. Maybe I have a decent phone.

Serendipity 5.5

SuckerPunch-SmR #41 @ 1.2ghz

LF a modem that will survive the DC METRO gauntlet
[Captivate Android Development] lrs421:
Something must be running in the background or you need to calibrate. I lost 3% over 7 hours last night.
[Captivate Android Development] bclark:
+1 you have to have something running. I lost 4% over 7 hours and I'm OC'd to 1300 and running the 1000hz test version
[Captivate Android Development] justmart:
I don't have anything in the background, just normal services and I've just have 1 widget [beautiful widget] Maybe bad signal???
[Captivate Android Development] lrs421:
Shouldn't really matter in sleep mode. How long have you been running the kernel? Usually takes a couple of days to settle. Not that's completely necessary, when's the last time you calibrated or wiped battery stats?
[Captivate Android Development] bclark:
That may be it. Try shutting off your data connection when you sleep. This will seriously cut down on needless drain, especially if you do not charge at night or need that widget to update. Or try SuperPower
[Captivate Android Development] lrs421:
^^Also check your wifi sleep policy.
[Captivate Android Development] justmart:
My wifi policy doesn't work since I flashed Speedmod... I posted that over there... but nobody find the solution... And I think is a common bug.
[Captivate Android Development] lrs421:
If you have a bug that prevents your phone from sleeping there's your battery drainer.
[Captivate Android Development] tiuk:
Found it after I posted and forgot to update, thanks.

Why is it "not recommended"? Performance reasons?
[Captivate Android Development] lrs421:
I recall hardcore mentioning something about battery life. I believe it's a resource hog.
[Captivate Android Development] olo567:
My phone's been pretty stable, with a very light UV, and I usually charge with the phone off. I had assumed that charge death was a freeze with the phone on since I didn't think the OC/UV settings did anything without the phone booted, but today I checked my phone while plugged in and off by pressing vol up, it showed 100% but froze there and wouldn't boot until a battery pull. Is that charge death? Could that even be related to the kernel and my UV settings? Or just an unrelated hiccup?
[Captivate Android Development] lrs421:
Sounds like an UV freeze. Try adjusting 25 at a time starting with the lowest frequency.
[Captivate Android Development] justmart:
It is just the wifi policy... that is why I turned the wifi OFF.
[Captivate Android Development] shawn122:
I am not sure if anyone has had this issue but every time I reboot my phone freezes when it starts scanning the external sd card.

I then have to do a battery pull, remove the sd card and then restart. Once the phone restarts I then pop in the sd card and all is okay.

I installed the latest speed mod kernal and I don't get this problem.

Any ideas? I didn't undervolt or anything like that.
[Captivate Android Development] lrs421:
Are you certain its just the wifi? Something else is going on there. Otherwise your battery wouldn't be draining so fast when the screen is off and the phone should be sleeping. I've flashed lots of kernels and never experienced that sort of loss. If it were a kernel issue there would be several reports of this sort of behavior.
[Captivate Android Development] ccdoggy:
There really needs to be a wiki or something for battery drain problems and solutions.

A few things to look at for increasing battery:

disable 3G, use 2G only if possible, HSUPA, HSDPA

select the radio band which gives you the best signal in your area. sometimes it likes to bounce between signals and that drains.

wifi uses lessbattery then cell data, leave it on when connected and cell data off (use an app)

different modems are better/worse in different locations, try a different one.

Turn off the auto rotate

*Make sure to turn off auto update on apps like twitter, facebook, and such*

and more.

it all may come down to your area and applications as to your success with battery life. try a different rom/kernel/modem and see what happens.
[Captivate Android Development] justmart:
Can you recommend an app for check what can be the cause? THX!