yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
As long as Hardcore is ok with it, ill do my best to keep everything updated, and not just with Hardcores settings/features, I will be adding in more of my own features as well.. the one thing I want to get out, is im not trying to copy all of Hardcores work, granted this is based off his K12P patch, but im wanting to put out something that incorporates all the best features to give the best battery/performance ratio... so in short, if Hardcore, or anyone for that matter, puts out sources for something that we can benefit from, ill update it
[Captivate Android Development] Auridran:
I would love to test this kernel out, but I can't bring myself to like the brightness mod. I would much rather use an application like Total Screen Control to change that kind of thing.
[Captivate Android Development] jaxf250:
Now we're talkin.....

Awesome.

Thank you. Ah Thank you very much. </elvis>

Loaded, OC/UV set, charging up tonight... will test battery life tmrw.

Already my Nitrodesk Touchdown app is flying once more....

Bliss....... :D
[Captivate Android Development] opcow:
How can I install this kernel on my playstation?

Also, benchmarks must, as we know, be taken with a grain of salt. However, all else being equal, they are indicative of performance to some degree. This kernel scores lower on quadrant than the latest GlitterButt @ 1000MHz.
[Captivate Android Development] ccdoggy:
I am wondering if you can clear up something for me.

There are two different Speedmod kernels released (250hz, 500hz), does the above mean this one is 100hz? if it is not then which is it?

I asked about battery usage on 250vs500 and this was the response.

Battery 250 vs 500hz
[Captivate Android Development] opcow:
I wonder if the CONFIG_HZ setting in this and SpeedMod have anything to do with their poor benchmark scores (extra interrupt generation or something). Personally, I don't see any benefit. My UI feels perfectly smooth at 256Hz.
[Captivate Android Development] existz:
Alright guys, you twisted my arm :P A 1280 version should be coming tonite, testing it right now, if all goes good ill post it :)
[Captivate Android Development] LimaI896:
I ment my psx4droid lol, on speedmod I lagged horribly as the playstation I think needs 1.1 ghz to run properly.

So far I have been stable on the current uv settings. -125, -125, -100, -100, -50, -50.

Can't comment on battery life till tomorrow with a full charge. Trying to kill my battery completely right now.
[Captivate Android Development] LimaI896:
Amazing, hope it works unlike gbs.

Hopfully this comes before I go to sleep ahah :D
[Captivate Android Development] Nickel Dime Bay:
lol nice THANK YOU! :D
[Captivate Android Development] WickedNite:
I've asked this on a different thread and I'm gonna ask this here to also have other answers. Why do you uv? What does it do on your phone? How does it affect it? I'm sorry for this noob question, I'm not fan of oc/uv. Lol.
[Captivate Android Development] LimaI896:
Whats an irc?
[Captivate Android Development] iNFRiNGE:
it's an elite under ground world that I can't talk about in public but some day you may be allowed in there.

JK it's a private service for groups of people to chat. and personalized through certain channels Internet Relay Chat (IRC)
[Captivate Android Development] gibson3659:
Sorry, guess I got my kernels crossed. Either way, my phone didn't like 1280 too much at boot.

May I make another suggestion then? Include a 0/uv 1G limited init script in the cwm zip to protect the noobs and those unsure of the oc/uv capabilities of their phone. It won't make any difference to those of use using the SGS Flasher.
[Captivate Android Development] cumanzor:
So I've been running release #26, undervolted, TLJL3 modem, Cognition 3, for half a day and I have to say that this kernel is AWESOME. Battery life is absolutely insane!! I think I might try the #27 again, just for giggles and ****. But I'm definitely getting some good UV results with #26.
[Captivate Android Development] ccdoggy:
IRC chat

+10char
[Captivate Android Development] zerkai:
Nice :) Whats your settings at? I'm still trying to stabilize :)
[Captivate Android Development] iNFRiNGE:
Whats your settings if I may ask please?

YOU ARE DA MAN! Cheers

And uhh same question you beat me to it lol
[Captivate Android Development] zerkai:
I just failed 50/50/75/75/125/125 @ 55 passes (bogomips: 1103.87, load: 1.70, 35c, 20:57 -- for whatever thats worth lol)

Now running the stability test with 50/50/75/75/100/125 :)
[Captivate Android Development] WickedNite:
How can I test mine? What tool or app are you using?
[Captivate Android Development] zerkai:
Search "Stability test" in market, and/or neo something.

EDIT: Currently testing 75/75/75/125/125/125, It's been 25 minutes, 64 passes. Kind of weird this is still going but my other tests failed. EDIT2: Failed at pass 119, 45 minutes.
[Captivate Android Development] cumanzor:
Right now I'm using 100/100/125/125/150/150 (1120 to 100). Noop scheduler. I've been running this way for almost half a day, and been charging for around an hour with no death charge so far.

Haven't tried any stability test as I didn't know about it.

Btw, Voltage Control 3 still has this strange bug where it sometimes doesn't detect all the frequency steps.
[Captivate Android Development] existz:
For those of you using noop, just wanted to throw out there that Hardcore actually recommends cfq, he has actually spent alot of time tweaking it for cfq, that's what some of the tweaks are in cwm, I personally use cfq as well, however, you can use whatever you want, just want to throw it out there, that it has been carefully tweaked to use cfq by default
[Captivate Android Development] zerkai:
Aw man, I'm at 100 passes with noop... lol. Should've stuck with the default cfq, but I saw the 3rd post using noop.
[Captivate Android Development] sf1120:
What are the benefits of running it @cfq and noop?I have a problem trying to run it on noop where I select it and then apply it,exit voltage app and re-enter it,it will default back to cfq.Any ideas?Voltage is sticking tho.
[Captivate Android Development] zerkai:
I had that problem as well, I think I needed to enable read&write on /system.
[Captivate Android Development] sf1120:
Do you think that will help it stick?But I still wanna know what the difference is between cfq and noop tho.
[Captivate Android Development] zerkai:
It worked for me... probably that + re-installing the Voltage app from: http://xdaforums.com/showthread.php?t=829731 -- but it might be the same file attached somewhere on the first page.

I had to force-close the app and re-open it then it's fine. Just for the hell of it, I used your settings (but with cfq) - 62 passes so far. EDIT: Failed at pass 80 (30 minutes)

Just got a charge death... :(
[Captivate Android Development] existz:
I ended up posting it at github, link is in OP, as for the toolchains, I used 2010.09-50, just grab the latest from codesourcery
[Captivate Android Development] sjavvaji:
yea...u pulled if out of my mouth...i was about to say the same thing...i have been using cfq on this kernel for a while when i realized this
[Captivate Android Development] VFO:
So so far still no issues with sleep deaths since going to the 128hz version. One interesting thing I have found is when looking at CPU spy it shows a definite difference between the 128hz and 1000hz. With the 1000hz the 100Mhz and Deep Sleep were the clear highest percentages. On the 128hz version it is spending little to no time at 100 through 600 but much higher on 800 and 1000 Mhz. Deep Sleep is still the most used as I my phone tends to spend the majority of the time in standby. I don't know what exactly if anything this means just a notable difference between the 2 versions that I have seen.
[Captivate Android Development] bballer182:
Hey existx, I think you missed this a few pages back

http://xdaforums.com/showthread.php?t=1025561

This looks like it would be a cool option to have if you want!?
[Captivate Android Development] existz:
Dont think it will work since almost all of the kernel debug has been disabled..except logcat, which can be activated in recovery (android logger)
[Captivate Android Development] bballer182:
Gotcha :-)

Sent from my OC'd Samsung Captivate
[Captivate Android Development] geokilla:
If I charge my phone when it's off, it shouldn't be undervolting correct? I keep on going into Kernel Panic Mode when the battery is about 60% charged.

Sent from my Samsung i896
[Captivate Android Development] aalh:
It had not had a SD since this morning, I am thinking the SD was a unplug lockup not a sleepdeath

still have Soft Locker disabled :D

since I have been able to let my phone enter deep sleep again, my bat life has almost DOUBLED

No UV

non-stock clocks used 600, 1200, 1300
[Captivate Android Development] diablo009:
Can anyone pls tell me what file is updated when I disable states in Voltage Control. Deleting the S99_volt isn't helping, and my disabled state "1000" is not being enabled.
[Captivate Android Development] existz:
If your asking what file controls the states enabled, (ie. if you enable/disable a state in VC, the file it writes to)..it is /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table... (0=disabled 1=enabled)..do not delete this file... When you save settings in VC, it just writes to this file, then when you save boot settings, it writes to this file on boot..
[Captivate Android Development] diablo009:
Thank you sir. I forgot to re-enable the "1000" state when switching to a kernel with no VC support. Now I know :)

Edit:

I do not have the file "states_enabled_table", but I have a file called "scaling max frequency". :confused:
[Captivate Android Development] Bren Dekura:
Anyone had issues with audio payback volumes dropping considerably swimmingly at random? It seems to happen regardless of program and eventually returns back to normal after a while. Only happened with 2.04 and 5.....

Sent from my Captivate
[Captivate Android Development] surfed.tk:
I just came across an interesting issue, if I have wifi turned on and put the phone into airplane mode and turn off the screen it will hardlock. If I then push volume up & power I get a weird unknown download mode screen / message. I can repeat this every time. 2.0.5

Sent from my Samsung captivate.
[Captivate Android Development] H3llstorm:
This doesn't happen on my phone. What ROM and modem are you using?
[Captivate Android Development] existz:
Just an update for those of you following Onix, 2.0.6 (maybe 2.1.0) will have alot of fixes from 2.6.32.10 - 2.6.32.27.. im currently working on updating the kernel to a higher kernel version..not sure if ill stop at 2.6.32.27 or start into 2.6.33.. but so far ive got quite a few fixes/updates added, ill probably go ahead and update the whole kernel (even things thats not for us..updating the whole kernel source).. just incase for future reference.. I have to do this manually, updating commit by commit..as the 2.6.32.10+ patches will not patch successfully.. so it might take me awhile to get everything updated..
[Captivate Android Development] aalh:
I appreciate the effort existz
[Captivate Android Development] geokilla:
I'd like to add that the UV/OC settings were saved as only apply for now and not during boot. The Kernel Panic Mode is really a problem for me because I need all the battery life I can get.
[Captivate Android Development] thresherhorn:
Keep fightin the good fight! We appreciate it! :D
[Captivate Android Development] surfed.tk:
Continuum / kc1

Sent from my Samsung captivate.
[Captivate Android Development] johan8:
You're really kind of kernel fighter !

;)
[Captivate Android Development] abee_13:
Don't know whats going on but I've been having sleep death issues for the past 2 versions of onix. Ive tried it with and without oc/uc/uv. any ideas?

Sent from my cappy UC'd 900mhz and UV'd running di11is rom/ Onix kernel
[Captivate Android Development] geokilla:
Did you undervolt or overclock? Check the above couple posts. I'm getting a similar problem as well.
[Captivate Android Development] Seanbest:
No oc or uv. Plugged it back in. Happened again.

Sent from my Captivate (Phoenix Unleashed JS8) using the XDA App
[Captivate Android Development] Nickel Dime Bay:
gotten 2 sleep deaths 1 with no UV and 1 with very little UV

2.0.5
[Captivate Android Development] geokilla:
So I'm not the only one. Unstable kernel...
[Captivate Android Development] LNJ:
I've not experienced a single issues in any of the Onix builds.

No sleep death, charge death or kernel panics.

And my second Cappy which I acquired last week for my wife has been running Onix 2.0.4 since day 1 and I have set up all my alarms 1 minute after hers fearing that hers may encounter the SD or CD issue but so far no issues to report.

Mine is a 10.12 and hers is a 10.10 so not sure if the build dates have anything to do with this!
[Captivate Android Development] bballer182:
Im with you. Build 1012. And not a single issue. Solid kernel! I've run every public release...

Sent from my OC'd Samsung Captivate
[Captivate Android Development] AReynante:
I am also running perfect. I update on every public release, OC to 1400, UV pretty well too. No deaths or panic modes.

Love your work existz :)
[Captivate Android Development] fractaline:
curious..... I have a 1008 and a 1006 both using onix and all good... the 1008 is my daily driver and i've pushed it much more, but the 1006 is oc'd to1200 and so far so good......

i have had some freezes on the 1008 in messing with my oc/uv settings and a single sleep death that i believe to be also related to too much uv....

there seems to be some issues with some phones but what's the pattern.....
[Captivate Android Development] AReynante:
I don't know about specific build number problems, but my phone is a 1007 (warranty phone), and it runs fine with oc/uv at the numbers below:

1400 ~ -0

1200 ~ -25

1000 ~ -50 (I think I can go -75 though)

800 ~ -100

400 ~ -75

200 ~ -125

100 ~ -150
[Captivate Android Development] LNJ:
I run:

1400 ~ -0

1300 ~ -75

1200 ~ -125

1000 ~ -125

800 ~ -125

600 ~ -100

400 ~ -150

200 ~ -125

100 ~ -150
[Captivate Android Development] LNJ:
New Nightly is up. Flashing now!
[Captivate Android Development] fezzy102:
Where can we get the nightly build?
[Captivate Android Development] fractaline:
Irc channel link in the op, I haven't joined but it's there.

_______________________

@Elisa and AReynante,

Did you isolate and test each step as you added them to find those stable settings? Or just shift them around til success arrived?

I'm still getting the odd freeze when going above 1200 but I confess I haven't yet gone through that process...

Just winging it in daily use.

Do you find the freezes are too much uv?

Sent from my fire fly'n liberated captivate

{onix enhanced}
[Captivate Android Development] johan8:
HERE
[Captivate Android Development] rajendra82:
The place where you get everything from existz:

http://berryfx.com/RobBeane/

go into /Kernel/Nightly/
[Captivate Android Development] H3llstorm:
For a second, I read that as "go to /Keira/Knightley/".

NVM
[Captivate Android Development] aalh:
sleep death is back. I went a full day with no SD, I wake up this morning to find it off

I turn it back on and check it a few minutes later, it is off again.

the only difference was I tried -50 on all the enabled voltages

so it would seem the code in this kernel is a bit pickier about uv

I have no UV and I disabled 600

I will see how it goes today
[Captivate Android Development] LNJ:
I tested each frequency individually with stability test, quadrant or neocore.

Sent from my GT-I9000
[Captivate Android Development] diablo009:
Try disabling 900 too. I had a freeze up once with 600 and 900 enabled. I didn't get any freezes after disabling them.
[Captivate Android Development] geokilla:
Went into Kernel Panic Mode again. My phone was on standby too, UV/OC. So it's not a charging problem.
[Captivate Android Development] existz:
Wanted to point out an awesome app by Shane87, Voltage Control EX, it adds the option to select the cpu threshold tweak right from VC, it gives you 3 options, Battery Saver, Performance and Stock .. by default the kernel uses Battery Saver settings so it will default that ..also, if you are using the threshold tweak in recovery, you will need to disable it before setting it in the app as boot settings, as the kernel tweak will override the app setting on boot .. Also shane87 has added the time in state to the app, when you pull up the states, it will show it for every step ... an all in one for VC! Check it here... http://xdaforums.com/showthread.php?t=1030994
[Captivate Android Development] H3llstorm:
What is "charge death" and "sleep death"?
[Captivate Android Development] geokilla:
Another Kernel Panic Mode! Maybe it's the tweaks in the recovery menu that is causing this....

I'm currently undervolting all steps by 75mV, with the states set to: 100, 200, 400, 600, 900, 1120. Hope it works.
[Captivate Android Development] existz:
Charge death is when your phone is connected to the charger and when it goes to sleep, you can't wake it...just a black screen, you have to do a battery pull to turn it on...

A sleep death is basically the same as above, but when its not connected to a charger
[Captivate Android Development] topiratiko:
Awesome! What are the chances we can convince hin to add a screen off profile to limit mhz with screen off? I just need to swap this already.

Sent from Paragon Optimized
[Captivate Android Development] existz:
I was getting ready to ask if you have the memory timing tweak enabled...try it with it disabled . Alot of different things can cause a kernel panic...a kernel panic is simply the kernel turning itself off when it detects a fatal error which it cannot safely recover from hardware or software related...also it can panic if voltages are set to low.. I've yet to reproduce the problem, if it was the kernel it would be happening to everyone..so there's something else either by itself or in combination that's causing it

http://en.m.wikipedia.org/wiki/Kernel_panic
[Captivate Android Development] goodolsen:
I've got -75 on 100, 200, 400, 800, 1000, and 1200 and only those states are set.

No CD or SD issues, I also have the MemTiming tweak turned on.
[Captivate Android Development] surfed.tk:
-150 100

-125 200

-100 400

-100 800

-100 1000

-75 1200

-50 1300

All stable except with wifi on and going into airplane mode. All tweaks enabled.

Sent from my Samsung captivate.
[Captivate Android Development] Vivified:
I just flashed Onix 2.0.5 and have to say that it is very smooth and responsive. I have been using SuckerPunch-Voodoo for some time due to how stable it is. I have used Onix and had the CD issue in the past, I will report on whether or not it is still an issue tomorrow.
[Captivate Android Development] TRusselo:
useful picture...
[Captivate Android Development] existz:
Tonights nightly should be fully updated to 2.6.32.10 maybe .11, taking me along time to update commit by commit...lol..but getting closer
[Captivate Android Development] geokilla:
Yep it's enabled.

I currently don't have any Kernel Panic Mode. Let's hope it stays this way. The weird thing was that I was able to UV by 100mV with SuckerPunch-Voodoo. But it wasn't really stable either. Maybe my Captivate just is a bad batch and requires more voltage...
[Captivate Android Development] existz:
Yea the amount which you can UV by may vary from kernel to kernel..(sometimes even the same kernel depending on updates)...alot of different things come into factor...ie..the actual oc/uv code, the cpu threshold values, certain tweaks...etc..etc.. its always best to start clean when adjusting oc/uv settings when switching kernels ..
[Captivate Android Development] goob1284:
Alright so I downloaded the newest nightly, and it seems to do wonders for the battery, but the wifi comes in and out once in a while. Any suggestions? Or is this a bug?
[Captivate Android Development] markmunsch:
Yeah I've noticed the UV is really dependant on the phone. Been using OC/UV kernels for awhile, tried Onix when switching ROMs to Continuum. 2.05 has been great for me, while 2.04 was causing serious battery drains with my phone, with no real evidence as to what or why but the kernel was the only thing that had changed. I've got a 1006 phone, and if I push the UV past -75mV at 100 or 200 it's nothing but CDs and SDs. Therefore I run -25mV @ 1200, -50mV @ 1000, and -75mV at 800,600,400,200, and 100. It isn't much but it does help battery life a bit, getting through a day of hard use without having to run for a charging cable.
[Captivate Android Development] existz:
2.0.5 should help with battery ...or the latest nightly/s
[Captivate Android Development] geokilla:
-50mV at all steps I posted earlier didn't work. Still going into Kernel Panic Mode when the phone is idle/sleeping. I have the first 5 tweaks enabled in Recovery. I'll try disabling Optimized Memory Timings tweak and see if it helps. Maybe the CPU Performance Threshold is causing a problem too...
[Captivate Android Development] goodolsen:
I would try turning off the CPU tweak first, I'm running with memory tweak with no problems.
[Captivate Android Development] RandomZero:
I installed 2.0.5 along with the firefly 2.8 update and it broke video players ability to play avi files, but switching to speedmod fixed it.
[Captivate Android Development] fractaline:
@geokilla, try ditching 600&900, I never had kernel panic, but I could not oc above 1200 without a freeze... Until yesterday I removed 600 and it is soo oo much smother and I'm stable (so far) at 1400......

1400, -0

1200, -50

1000, -75

800, -100

400, -100

200, -125

100, -125

for me getting rid of 600 was like a new improved kernel...

Worth a try. our phones have different attitudes but it helped me alot.

Sent from my fire fly'n liberated captivate

{onix enhanced}
[Captivate Android Development] existz:
Ive yet to ever have a kernel panic...disable everything and undo your oc/uv, putting it back to stock... then start from there..if it still does it with all the tweaks disabled and stock clock/frequencies..then its not the kernel causing it..
[Captivate Android Development] geokilla:
Will try this later.

Will try that later.

Yes sir. Will disable all the tweaks, even the recommended ones and leave everything at stock. But first, I need to charge my battery!
[Captivate Android Development] TRusselo:
i have the blanks filled in the best i can do for an idiots guide to kernel options...
[Captivate Android Development] existz:
IO Scheduler + Remount Noatime

-as of right now theres really no tweaks for IO scheduler as I use SIO, and theres no tuneable options for SIO..

-Remount Noatime- mounts the noatime option..with noatime it stops recording the last file access time when the file is just read. The noatime option eliminates all the writes to the disk each time a file was just read which previously used to happen with atime. However a write is made to a disk in case if a file is being changed/written.

Kernel VM Management

-tweaks /proc/sys/vm/dirty_writeback_centisecs and /proc/sys/vm/dirty_expire_centisecs

CPU Peformance Threshold

-sets more performance based settings for the cpu threshold..it will scale higher quicker and not scale down as fast

Optimized Memory Timings

-sets more optimal memory timings

Enable Read-Ahead Tweak

-Adjust vm_max_readahead value to 1024kb

Enable CIFS Support

-adds CIFS support, if you dont know what CIFS is, you dont need it...http://en.wikipedia.org/wiki/Cifs

Enable TUN Support

-adds TUN support, again, if you dont know what TUN is, you dont need it.. http://en.wikipedia.org/wiki/TUN/TAP

Enable Custom Bootanimation Sound

-title says it all...enables custom bootanimation sound

Enable Android Logger

-enables logcat.. only use if you need to debug or if a certain app depends on it..if not, dont use it..saves alot of battery

Old lowmemkiller Settings

-enables default lowmemorykiller settings...Hardcores modified settings are default

Read-Write /system

-enables read/write on system..
[Captivate Android Development] TRusselo:
Awesome! couple q's in red above....

and what are the (R) (0) stand for?
[Captivate Android Development] zerkai:
(R) recommended, (O) optional