yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] LimaI896:
Me too ahaha crazy addiction
[Captivate Android Development] LimaI896:
Trying out 1.3ghz n my phone seems to like it which is weird as it didn't like 1.28
[Captivate Android Development] indomikey:
Mine previously would only take 1280, right now on 1.4 on build 40, but the benchmarks are the same or even worse currently, real-life speed, about equal.
[Captivate Android Development] LimaI896:
Real life speed increased a good amount from 1.2 to 1.3. Just waiting for my first freeze to happen lol.
[Captivate Android Development] existz:
My kernel will score lower in benchmarks because all my options/settings are slower because this kernel is geared towards battery life not speed like other kernels. If you just want to boost scores, select the FASTER mount options in recovery
[Captivate Android Development] GGXtreme:
Awesome :D Can't wait.
[Captivate Android Development] WickedNite:
To be simple, this will enable an option at recovery menu to select or apply warm/cold color to your phone? Or I don't understand it correctly? Lol.
[Captivate Android Development] LimaI896:
Is the faster mount option really that unsafe? What is unsafe about it?
[Captivate Android Development] ryude:
It's pretty safe, just not fort knox safe.
[Captivate Android Development] LimaI896:
What could go wrong though? I just dont understand the difference lol. Sorry for my noobness.
[Captivate Android Development] existz:
Correct, there will now be options to select neutral, cold or warm in recovery.

As for the FASTER mount option, they are unsafe than the SAFE option, but voodoo lagfix uses it, you shouldn't have any problems using it.
[Captivate Android Development] LimaI896:
Sooooooo your indirectly saying the faster mount option is safe but dont complain to you if somthing goes wrong? :p
[Captivate Android Development] zerkai:
Under my VC options, it shows a question mark for the 600 step: "600 Mhz: ? - 125 = ?mv"

This goes the same for the 1300 and 1400 steps. I deleted my vc control file before upgrading to #40. I tried reinstalling VC too. My states are: 1120 all the way down to 100. But it shows question marks for some reason...
[Captivate Android Development] Auridran:
Because they aren't entered into the kernel. It's purely cosmetic and does not affect undervolting.
[Captivate Android Development] existz:
Basically :P lol
[Captivate Android Development] pillz424:
Voltage control app, I have steps 1200, 800, 400, 200, 100 enabled with a check. What are you guys using for oc but best battery life?
[Captivate Android Development] existz:
As mentioned above its just not specified in the kernel, the actual VC app only has voltages specified for up to 1120, for them to show they would have to be in the source, which is something I havent done yet where I've been changing frequencies, ill add them in later on
[Captivate Android Development] r3ferrei:
Does this discussion include the loop options as well in the lagfix?
[Captivate Android Development] existz:
To get best battery life I recommend using the 600 step, that's why it was added...
[Captivate Android Development] nuwayman:
What really are the benefits overclocking? Does it really make a difference? Scores on quadrant and smartbench are higher but does it really make our phones that much faster? I guess it depends on what you do with your phone. For me I'm always on the internet browsing. Does it render internet pages quiker? Does it upload youtube vids quiker? Does it tether faster through mobile ap or through usb? Sorry for asking such a noob question. Just wanting some clarification on the subject. The stock to me seems just fine.
[Captivate Android Development] Auridran:
If the processor is the limiting factor on any of those things, overclocking helps. If you're browsing the web with your mobile internet, chances are it won't make much difference.

If you're connected via wifi to a 25mbps connection, overclocking will probably make your pages render faster.

If you play PSX games on a PSX emulator an overclock will help out framerates quite a lot.
[Captivate Android Development] LimaI896:
Lmao mounted the fast way. Though trying to boot into recovery my phone froze which was a first.
[Captivate Android Development] WickedNite:
So are you including that feature on your next release?

Sent from my Muscles using Brain Cells
[Captivate Android Development] existz:
Yea, As soon as HC releases sources for K13A
[Captivate Android Development] pillz424:
Awesome, thanks I had it backwards.

Sent from my hacktivate
[Captivate Android Development] existz:
For those that had charge death before, let me know if you still have it ..please rule out that your UV is not causing it first, as if that's the problem ill just be going in circles and wont be able to fix it, even if they worked on other kernels, make sure anyways, alot of settings in the source is different with mine
[Captivate Android Development] WickedNite:
I charged my phone last night while it's on and I woke up this morning and it is still on. Haven't experienced cod yet. That's my first time doing that test btw. Will try that again later.

Sent from my Muscles using Brain Cells
[Captivate Android Development] LimaI896:
Will let you know in the morning :thumbsup:
[Captivate Android Development] neffarious:
CD seems to be gone but i lost my precious 1280 and 1300 is no faster and unstable for me:(
[Captivate Android Development] LimaI896:
Weird, 1280 was unstable for me but 1300 is.
[Captivate Android Development] shawn122:
So I updated to #40 and now my voltage app keeps on force closing. Any ideas on what to do?
[Captivate Android Development] existz:
Did you delete your s_volt_scheduler file in /etc/init.d first? if not, delete it and reboot, should fix it
[Captivate Android Development] shawn122:
Thank you! I knew I had to delete it but forgot in my haste and then I didn't remember the location of the voltage file.

Thanks again!
[Captivate Android Development] RobertInCypress:
using #36 to run Serendipity and getting poor battery life. no OC, just normal settings
[Captivate Android Development] bsc7080xsc:
I had the same problem... and had deleted the scheduler file prior to upgrading. So I took advantage of the fact that I just backed up critical files with TITBU this morning, and flashed back to stock to start all over again. Its a couple of hours of my free time, but ends up being a cleaner install. So not that big of a deal really.
[Captivate Android Development] Auridran:
So far battery life seems stellar with #40. With 100/200/400/600/800/1000/1200/1400 enabled at UV of -150/-150/-150/-125/-125/-125/-50/-25, I'm at 89% battery and just under 10 hours of light usage.

Still tweaking the UV settings as well. #40 seems to be able to UV a whole lot more than the other kernels. So far -25 seems stable at 1400 whereas it would crash every once in awhile in #36.

Also, StabilityTest is now version 1.3, and gives an accurate measurement of stability. In the changelog it says they fixed a bug with random crashing on Motorola phones, and it seems to have fixed it for our phones as well. Something to do with JIT, which I know our phone has trouble with.
[Captivate Android Development] lpsi2000:
That should not happen even if the kernel is geared for battery life. It should run faster at higher clock speed. A few of us saw this a couple of months with SetiRon kernel version 1.4.3, even though the kernel said it was running at 1.45 but technically it was running at 1.3 based on the voltage and GPU configuration. I don't know if that is the case here, but I am sure Existz will check it out.
[Captivate Android Development] shawn122:
So what do you guys do when you under volt and then everything starts freezing? I end up having to pull the battery to reboot but then when I do reboot..the sequence starts again.

I can't open root explorer to delete the voltage file. I ended up removing my sim card and external sd card and luckily the phone didn't freeze up which gave me enough time to delete the voltage file.

Any tips are greatly appreciated.
[Captivate Android Development] lrs421:
Well, I was reluctant to post about this out of fear of retracting it but since flashing 40 upon release yesterday not a single wifi or mobile ap issue, I've been testing it extensively since. I know it wasnt just me as others experienced mobile ap issues as well. Not only do I no longer have connection issue but I can UV a good bit further and am completely stable at 1300mhz, although I only plan to run 1200. In my opinion this is the new gold standard for oc/uv kernels.

I'm still curious as to what's going on with wifi/mobile ap but both are working flawlessly on this build.

Support Existz and Hardcore, they truly deserve it.
[Captivate Android Development] ryude:
So far no charge death or sleep death. Loving this kernel.
[Captivate Android Development] bclark:
Only apply for now. You can do a slight undervolt or set to 1000 for a boot setting but any intense UV should definitely wait until you're positive that you're stable

Edit: what's awesome is that as I typed this I had a UV freeze. I seem to be able to UV less with 40 than 36 but my phone seems to dislike the 600 step. Time to try again.
[Captivate Android Development] olo567:
I'm just getting into the whole overclock/undervolt thing, but with this kernel revision I have 1.4 stable. As far as undervolting the individual steps, do you find that it's best to set each step as the limit in Voltage Control and test stability for each? Or do most of you just test stability of the highest clocks and react when your phone crashes as far as undervolts?
[Captivate Android Development] elghouchd:
What faster mount options are you talking about?
[Captivate Android Development] indomikey:
Go to recovery-> Advanced SpeedModULK Features -> Lagfix Options -> Ext4 mount options
[Captivate Android Development] olo567:
BUT this is usually not recommended with original SpeedMod because it could cause corruption if anything goes wrong, and with an OC/UV kernel where you're expecting freezes and crashes to happen, I don't think it's a good option unless you are 100% sure you are 100% stable.
[Captivate Android Development] capita:
No charge death since I installed #40 and re-enabled the kernel VM tweak. UV settings: 125, 125, 100, 100, 75, 50, 50, 25.

100, 200, 400, 600, 800, 1000, 1200, 1400 steps enabled.

Big thanks for the awesome kernel existz.
[Captivate Android Development] shawn122:
Thanks for the tip...now that I read it, it seems like the obvious thing to do...lol. I was applying as boot settings without even testing.

How is that for stupidity! Lol....

Thanks again!
[Captivate Android Development] elghouchd:
I went into recovery and went to the TWEAK options, and i pressed on all the recommended tweaks, but how do i know if they got enabled? I don't get a message saying something like "Tweak successfully enabled" or anything like that. Thanks
[Captivate Android Development] itdiestoday:
what are you all using to test the stability of your settings? I am using stability test from the market but was wondering if there is anything else I should be checking.
[Captivate Android Development] existz:
When you enable them in recovery it will show you at the bottom, when you disable them it wont show them, you can also check /system/etc/tweaks.conf it will show what tweaks are enabled, if they are not listed, they are not enabled
[Captivate Android Development] olo567:
Follow this as a guide as recommended in the first post.

http://xdaforums.com/showpost.php?p=10936691&postcount=1102
[Captivate Android Development] itdiestoday:
Thats where I started out but was wanting to know if there are any other stability test type programs out there.
[Captivate Android Development] elghouchd:
What exactly would it be showing me on the bottom?
[Captivate Android Development] existz:
The names of the tweaks... so for example if you enable all the tweaks it will show...

IOSCHED

KERNELVM

KERNELSCHED

MISC

If they are not listed, they are not enabled
[Captivate Android Development] Darryl Henley:
media volume control problem

using the stock music player the media volume control is not working right. when i turn the volume to max and then back down the sound decreases but the number gets stuck at 14 and i found that the head phone amplifier gain is changing with the volume control.

I don't know if this a problem with the rom or kernel. Could someone else test this, please?
[Captivate Android Development] AJerman:
Just FYI, my charge death has been very infrequent since I started using this kernel at build 30 or so, however, I did have it with version 39 this morning when I woke up, so whatever tweaks were done to try to fix it in 39/40 don't seem to have completely removed the issue. (unless build 40 has more tweaks to fix it, I'm updating now)
[Captivate Android Development] lrs421:
What are your UV settings like? If UV is the culprit there's no fix for it other than adjusting your settings.
[Captivate Android Development] sicmadek:
No charfe death for me last night
[Captivate Android Development] AJerman:
Don't think they are since it's so rare that it causes an issue and I don't have any lock ups on any type of stress test. If it happens more frequently, I'll try disabling UV and OC and see how it acts then. I forgot there was a couple of new clocks added with build 39 that made me adjust OC/UV.
[Captivate Android Development] existz:
Your uv could be stable with no lockups, passes every stress test etc etc, but could still cause charge death, it could only be one frequency that needs a 25mV adjustment, even if your settings worked on other kernels. It seems as of right now with most people who had charge death the VM tweak fix has fixed it, the number of charge deaths have went down by atleast 90%, so as of right now, until more reports and/or proof come in, I have to assume your uv is the problem. This is as very very tricky subject, with so many different factors in place, its hard to pin point the problem, but as for the kernel right out of the box I think the CD issue is resolved for the most part

To check you could try lowering the lower steps first (100,200,400,600) since when its asleep idel, its most likely using those frequencies
[Captivate Android Development] ccdoggy:
Its the new feature of the latest voodoo sound. It is in place to help reduce distortion. I dont know too much about it but supercurio knows whats best.
[Captivate Android Development] 305Freak:
Hi existz, could you please post a walk through as to what to do after flashing the kernel? I know its no big deal, it just seems like some basic instructions in the OP or maybe in post 2 with some conservative OC/UV levels for performance/battery would be very helpful. I'm sure most people would be a little confused at first as I was although a quick forum search was all it took to find some answers. New users of the kernel would appreciate it and it would save a lot of repetitive questions.
[Captivate Android Development] elghouchd:
I heard the Faster mount options could be dangerous? Is that true? Under what conditions?
[Captivate Android Development] RonH54:
Love #40 so far. With Darky 9.2 with 4 Recommend Tweaks ON and Ext4 on Data and System. I am using States 1300,1000,800,600,400,200,100 with these UV in same order, 0,50,50,75,75,100,100. These UV were just the 1st I tried and phone been Stable,No CD and it did well on Stability Test,Neocore and NenaMark if that really means anything. Battery life is at 93% after 6 hrs with WiFi On and Light use. I might to tweak UV some and may give 1400 a whirl just to see.
[Captivate Android Development] lrs421:
Existz posted about this a few pages back. A lot of people use it, not a big deal. Voodoo lagfix uses the faster mount option with no issue. So basically, you "should" be ok. Check the comments a few pages back.
[Captivate Android Development] lrs421:
Yup wifi and mobileap are officially fixed for me. Great, now I'm bored :(

This is truly an amazing kernel.
[Captivate Android Development] existz:
I dont post instructions on how to OC/UV because I don't support it, I just include it as an option, something you do at your own risk, as per the disclaimer in the OP, by flashing you agree you know what you are doing. Since ALL phones are different, some can't make it to 1280, some can do 1300+ with no problem, some can handle 125mV on a certain frequency, some can't handle 75mV. So if I supported it, 99.9% of the time the answer would be 'check your OC/UV', as theres no guarantee and an unstable OC/UV will cause alot of problems (charge death, reboots, freezing, FCing..etc) So if there's issues caused by an unstable OC/UV then its not a kernel related issue, its simply because the phone can't handle it.. so if its not a kernel related issue then its out of my hands ..

Theres an OC/UV guide by shaolin95 in the OP for people that need help finding their max settings, other than that I can't/won't provide any other support
[Captivate Android Development] existz:
Finally! Lol..glad its working.. all that's left now is to wait for hardcore to release K13A sources so I can get neutral/cold/warm versions selectable in recovery..
[Captivate Android Development] lrs421:
Can't wait :)
[Captivate Android Development] olo567:
That would be awesome. Great job existz, I was using Speedmod for the longest time, but I love that you offer the OC/UV option while staying current with the same great battery life!
[Captivate Android Development] olo567:
Get the voodoo control app from the market, and its an option for force analog volume keys. You can turn it off there.
[Captivate Android Development] c0ldburn3r:
....IP v6 google it. We are all on IP v4 it's the next generation of IP addresses, limit less unlike ipv4.
[Captivate Android Development] existz:
Update coming later today, im trying out a few different Kernel HZ settings, should be smoother now, I removed all references to FM Radio in Voodoo App, and I might just disable IPv6 Privacy since its causing issues with Wifi connectivity since I added it, most users dont even know what it is, so I doubt most of you will miss it, IF i do disable it, it will just be until a proper fix is done then added back in.. but i will mess around with it first and see if I can fix this issue
[Captivate Android Development] cumanzor:
Hmmm... I just went from GB's impressive sounding name kernel to this one. I'm just wondering... does GB's kernel has the Voodoo Color patch, and does this one has it? Maybe it's just a placebo effect but it looks kinda different.
[Captivate Android Development] Nickel Dime Bay:
Kernel is super smooth, running 9 hours on 125,125,125,75,75,75 excellent work my man. 1280 btw
[Captivate Android Development] Auridran:
This kernel has the brightness fix that Speedmod has, while GB's does not.
[Captivate Android Development] ryude:
Also, if anyone tried out my ROM please let me know if you had any issues and if you would like me to continue updating it.

On Topic: Can't wait for the new update, kernel is running rock steady at 125/125/100/100/75/50 @ 1120.
[Captivate Android Development] cumanzor:
Yup that's it. Definitely looks less bright than GB's kernel. GB's also has the color/sharpness fix I think. It might just be my eyes but I think I can tell the difference... (heck, even GB says he doesn't see it but oh well).

Will give this a try. Is there a way for me to easily bump the brightness or do I have to recompile the kernel? Because I have no idea how to do the latter lol.

Wireless is working fine here btw.
[Captivate Android Development] ryude:
You mean you need it brighter than max brightness?
[Captivate Android Development] cumanzor:
Yeah. Well, sort of. Thing is, in the other kernel, it's just brighter, overall, each setting.
[Captivate Android Development] Auridran:
Yeah, that's what happens. I don't like not having control over it either. I like being able to tweak the brightness settings to my liking using Total Screen Control, so I haven't tried this kernel yet.
[Captivate Android Development] silverslotcar:
You can ask Existz how to remove HC's brightness fix. But that would probably be a task.
[Captivate Android Development] ryude:
Honestly, I've never noticed any better battery life with the lower brightness. I would prefer it put back to stock brightness.
[Captivate Android Development] psufan5:
Agree. even with it on the lowest setting, never really noticed more battery.
[Captivate Android Development] cumanzor:
Cool! Didn't know of that app. Downloading now.
[Captivate Android Development] existz:
To change the brightness settings back to stock you would have to edit certain files, Hardcore has made new steps and settings, after you changed everything you would have to recompile it, but I should be able to revert it back, might take me a day or two, but ill look into it for the next release

EDIT

If I revert it back to stock, ill still offer the brightfix version as well
[Captivate Android Development] MikeyMike01:
People don't like the brightness fix? I rather enjoyed not being blinded at night and being able to see outside.
[Captivate Android Development] silverslotcar:
+1 me too....and for me, lower brightness does save battery.
[Captivate Android Development] existz:
Im like you, I like the bright fix, im always in a place where I need to dim my screen, so the bright fix solved that for me, if I can revert it back I will make 2 versions, one with it and one without it
[Captivate Android Development] Shammyh:
Hey existz, thanks a lot for creating this kernel. I too have been looking into recompiling hardcore's patches with Rasdeep's OC/UV patches. And this seems exactly what I've been looking for.

Just a quick question, any chance you will post the source code (and perhaps toolchain) you used to compile this kernel?
[Captivate Android Development] airbillion:
+1 for lower brightness settings...i think it saves battery life and I think it Is way too bright without the lower settings.
[Captivate Android Development] existz:
For those of you that wanted links to older builds, here ya go...ill also keep newer builds updated on there as well

http://berryfx.com/RobBeane/SuckerPunch/
[Captivate Android Development] Dlev7:
Update on the battery life after some serious daily work. I was using it all day, data on the entire time. OCed to 1.2. But I only use 3G now after 12 hours=25% lost.

This is with a ton of texts. Checking XDA a lot. 10-15 emails. Facebook. Ect

Thanks existz
[Captivate Android Development] Auridran:
Just updating my battery life from this post. I'm now at 70% battery at 1 day, 3 hours of uptime. Massive amount of texts sent and received in this time, but not much else done on the phone. I guess I received several emails as well.
[Captivate Android Development] froli13:
Which scheduler are you using?
[Captivate Android Development] Auridran:
cfs - I used to use noop but I figured I would give cfs another go.
[Captivate Android Development] existz:
I left out some scheduler tweaks in build #40, but i will include them in the next release, just waiting on hardcore to release his new sources for the color profiles then ill release a new build
[Captivate Android Development] Kionic:
Hmm...pretty good battery life. Uv 150,150,150,125,125,125,100,75,75,50
[Captivate Android Development] bclark:
Uh, to my understanding you dont have to UV the states you aren't using. Not that it hurts anything but as a heads up.

Do you have all states enabled?
[Captivate Android Development] zerkai:
Am I the only one that has a weird flick of distortion during a startup process with #40? The distortion looks like a TV channel with no signal, or the "Missing No. pokemon" (if you guys played that way back when) it shows up on the very top half of the screen for a second or two before going to the 'SuckerPunch' logo
[Captivate Android Development] existz:
Im getting it as well, for some reason its due to the new mem settings for 350mb ram, i just done a version identical to #40 with the old 340mb settings and it does not do that... not sure why its doing that, but shouldnt cause any problems.. but its up to you guys if you want to keep the 350mb ram or not