yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RichMD:
Is there any advantage to running a non-oc version? If you don't OC (and I probably won't most of the time) then you can just set to max freq to 1000. The OC version has more code obviously but would there be any noticeable difference?
[Captivate Android Development] meadhros:
I know your beeping noise. Got it a while back while I was doing a restore back to phoenix. Was #56 kernel. The ironic thing is I did a MC and reflashed my restore and all worked well. I searched and couldn't find any good explanations.
[Captivate Android Development] 13_:
Ok, Onix is running great, but for some reason I am no longer able to clock to 1.3 and be stable. Tweaks/noTweaks, all VC settings, just will not do it anymore. So I am stuck at 1.2. Benchmarks are generally as good or better than SP#59 @1.3.

My question is, Is there something changed in Onix that would do this, or is it just me and my phone?

Don't get me wrong. This kernel is smooth like silk. Was just hoping to bump the oc with it as opposed to ticking back .1.

Sent from a Captivate on Bluedipity 6.2, Onix 2.0.1, JQ1 with Xda App
[Captivate Android Development] existz:
Alright, got a script for u guys to test...it changes the sampling_rate time, the amount of time the kernel checks cpu usage to decide on scaling up/down...this sets a longer time before the kernel checks..it should help with battery life

Just place the file in /etc/init.d/ .. once you place the fine in init.d, you will need to reboot for it to take effect ...once rebooted, you can check if the script worked by typing this into a terminal emulator or adb shell...

cat /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate

Or you can just navigate to the /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate with Root Explorer or similar ...it should read, 5000000

Download the script here ... http://berryfx.com/RobBeane/Kernel/Files/S_sampling_rate.sh
[Captivate Android Development] Beny The Kid:
I haven't tried 1300 yet. But I found while playing with VC it really didn't matter much what I was doing. Inevitably my Cappy would freeze and then I would have to do a three button reset. Changed out launcher pro for the stock one that comes with FireFly and could get it to crash if I tried......
[Captivate Android Development] existz:
Actually there is a difference, not something you might see in benchmarks, but the oc/uv code alters the voltages/frequencies, even at stock using VC..there's alot of things, calculations..etc..that's changed with the oc/uv code..this is the main reason hardcore does not do an oc version ... this is also why some people have lockups/reboots..etc when not oc/uv'ing, some phones just don't like it...so a non oc version would benefit these people ..

There was some code changed, so it could effect your max clock .. im using a different oc/uv code since going to 1.6ghz.. so you might have to re-adjust you oc/uv.. im still adjusting it some to be similar to SuckerPunch
[Captivate Android Development] 13_:
I am using adw and agree that it is most likely causing an issue at times. But my oc on sp59 was dead stable. Other than VC upgrade, nothing has changed. I have tried both 100 &1000mhz, and had none of the install issues mentioned above. I am just curious as to why.

Also: love the recovery menu and options. Winning! And like I said..is as fast or faster @1.2 as it was @1.3...lol..makes me want 1.3 even more :P

Sent from a Captivate on Bluedipity 6.2, Onix 2.0.1, JQ1 with Xda App
[Captivate Android Development] 13_:
Ok. So I'm not crazy and should not smash phone in wall. I'm happy where its at and will keep pecking away at it.

Oddly, previously could never get 1.4 ,always instafreeze but now it will stay up long enough to get 1 quadrant score of 2280 and 1.3 is instafreeze... Lulz.

Thanks for all the hard work

Sent from a Captivate on Bluedipity 6.2, Onix 2.0.1, JQ1 with Xda App
[Captivate Android Development] meadhros:
Not usually a benchmark kid but like to check if I feel differences in performance.
[Captivate Android Development] existz:
Theres quite a few factors that come into play with the frequencies/voltages, and since changing the oc/uv code it changed a few things, as I mentioned you might have to adjust your oc/uv...theres actually a few new sysfs files in /sys/devices/system/cpu/cpu0/cpufreq/ that control these values...heres some info taking from laststufo's thread, which controls those variables ..DO NOT MESS WITH THESE VALUES UNLESS YOU KNOW WHAT YOUR DOING
[Captivate Android Development] existz:
Also, I might add this as the boot screen until I can get an Onix bootscreen made up.. just something to replace Hardcores boot image..nothing fancy, just cleaned up one of the shutdown images...what do you guys think? just something in the mean time..
[Captivate Android Development] Barbarian:
That'll do.
[Captivate Android Development] froli13:
Until you get an Onix bootscreen it doesn't really matter. (To me though...)
[Captivate Android Development] aalh:
ehhh....

Too bad Oprah owns O;)
[Captivate Android Development] shoman94:
How about a big O in place of the S then put a small nix?

Onix
[Captivate Android Development] 13_:
agree ;) 10c
[Captivate Android Development] existz:
How about something like this? (without the 'nix')
[Captivate Android Development] 13_:
I like that. maybe a lil brighter ... and a tad larger size for the O part ...
[Captivate Android Development] Barbarian:
Agreed.

10char
[Captivate Android Development] existz:
Yea its actually brighter and sharper ...when uploading, it converted it from png to jpg, it lost some quality ...actual image looks better
[Captivate Android Development] fractaline:
now your talkin...
[Captivate Android Development] goodolsen:
I'm liking this also, nice and clean.
[Captivate Android Development] 13_:
LOL... I waited for you I swear :p

Also: That script above appears to be working some magic on my cappy. I will report back my findings.
[Captivate Android Development] existz:
I believe ill use the O boot screen for now...atleast until something better comes along
[Captivate Android Development] goodolsen:
Let us know when it's ready since we are all so patient around here. :)
[Captivate Android Development] existz:
Added in a tad lighter colors to break it up some, nothing drastic...let me know what you think ...

EDIT

made the O a little bit bigger...(note that the actual picture has more vivid colors..and its sharper also)

http://berryfx.com/RobBeane/Kernel/i897/Onix/onix-2.png
[Captivate Android Development] 13_:
I think you have a winner.
[Captivate Android Development] goodolsen:
x2, that looks awesome.
[Captivate Android Development] :
X3

Swyped from my captivating awesomeness with darky's rom
[Captivate Android Development] existz:
well ..looks like we have a new boot image then :)... once the sampling_rate script is tested some, and we decide the best values, ill add it in the kernel..then ill get v2.0.2 out ..but im thinking the values I used in my script will be the highest we can go without effecting performance to much..I tried 10000000 (10sec) and it was to choppy ...5000000(5sec) seems to be good ..ill keep messing with it and see if I can find a middle ground ..I've been trying to get a script going that depends on the screen state, like if the screen was off, it would set it a higher value, cause its not going to really matter how the performance is with the screen off...then when the screen is turned on, it sets it a lower value .. not sure if I can do it..but im working on it ..
[Captivate Android Development] caanda45:
existz is it you that recommends

not

to use the sgs kernel flasher? If yes please tell me why etc and thanks!!!
[Captivate Android Development] existz:
Ive seen it do crazy stuff before, after flashing with kernel flasher app it would only boot into safe mode, only way to fix it was to reflash with cwm..then ive seen some flashes not stick after flashing with kernel flasher...its just easier (in the long run) and a for sure method flashing with cwm/odin. But thats just my opinion..if you do flash with kernel flasher app and later on start to experience weird ****, try reflashing..sometimes it solves the problem
[Captivate Android Development] gibson3659:
Couldn't this be done with a script and Tasker.

...So now my Cappy will have an O every time its turned on. Just the way it should be :)
[Captivate Android Development] fractaline:
well done on the screen, slick.....

the screen state based values sounds promising...
[Captivate Android Development] existz:
Ive been trying to frankenstien FloHimself's screenstate_scaling script, which is used to set different governors depending on the screen state to set my sampling_rate values, but so far its been a no go...still going to try a few other things and hopefully I can get it..
[Captivate Android Development] fractaline:
is it a bad idea to use the governer settings in os monitor? if i feel like messing with them?

or is it better to use the options in recovery?
[Captivate Android Development] xredjokerx:
nobody answered me earlier..

with sio i dont enable "IO Scheduler + noatime" tweak right?

also--

i still cant install airattackHD without it deleting itself. i thought the JPJ kernel fixed that?
[Captivate Android Development] Soccer_Dad:
Did you really mean to make this sampling rate 5 seconds? I would have thought that maybe 100,000 was an appropriate value (sample every tenth of a second) - it will still take a half a second to cycle from low to high if you have the preferred 6 states enabled. But if I understand your discussion above, with the 5,000,000 setting, it would take about 25 seconds for your CPU to see that it needed to ramp up from 100 to 1200 (assuming a mild overclock). I imagine that might be a bit laggy.

Or am I missing something (not entirely out of the question - I'm a geophysicist, not a computer guy).
[Captivate Android Development] disellusional:
has anyone tested this for wifi fix?
[Captivate Android Development] 13_:
Alright, back at 1.3 stable and smooth, this what I found.

I reflashed with CWM, cleared cache,dalvik,batt stats, voltage settings using the 100mhz ver.

The script for sampling rate made my phone work at 1.3Ghz but with a noticeable lag as it ramped up. I removed the script and went back to cwm. There I left the mem timings enabled and disabled the Tweak for CPU and now have a Super stable 1.3Ghz. Re-enabled CPU tweak and no matter what VC settings it was crash time.

Then I backed off to 1.2Ghz with Tweak enabled. Flawless. Almost as good a performance as 1.3 Ghz without Tweak. The CPU Tweak disabled and the performance at 1.2Ghz fell off slightly but definitely noticeable.

So my final findings are that Mem timing in CWM = awesome :)

The Tweak for cpu = performance boost at lower clocks, possible conserving battery.

Reg OC without CPU Tweak = buttery smooth

The sampling script I'm sure would save battery, it seems to be the ultimate "sleep" button. The ramp up seemed a little to long, however it enabled my phone to run at 1.5Ghz w/Tweak for about 10 min w/o 2 min. before reality caught up to it ...lol.

After playing its obvious this is a way more robust kernel and love the Onix recovery :D

Almost final Voltages.

1300 -25

1200 -50 /-75 < cant decide

1000 -75

800 -75

600 -75

400 -75

200 -100

100 -125

Linpack - - - 18.346 18.006 18.294

Quadrant - - - 1873 1898 1965

NenaMark - - - 49.9 50.1 49.4

Neocore - - - 64.9 64.9 64.7

Antutu - - - 2229 2197

An3dBenchXL - - - 28322

For some reason i can never get a stable clock on this phone without 600 and 1200 so I just leave them.

Fantastic work existz.
[Captivate Android Development] johan8:
SuckerPunch is very good kernel !

Now, the new Onix is much more advance !!

Excellent captivate kernel ever !

UV : 100~600 : -125mV

OC to 1.3G

Linpack : 18.2~18.6
[Captivate Android Development] AReynante:
Anyone using this kernel running Serendipity 6.2?

Whenever I flash this, and try to boot back up, I get stuck on my boot animation, and I have to reset and flash my default kernel (paragon).

I make sure that I don't have any voltage settings stored, (Which names can the settings stay as besides S_Volt_Scheduler?)
[Captivate Android Development] prayii:
I am. Running great for me.

OCed to 1.2 GHz and UV at every step.
[Captivate Android Development] AReynante:
Ugh. I have no idea what the problem is then. I've tried the cwm script from existz to remove settings, I've tried the option inside onix recovery, I don't know why I can't boot up with this.

(It happens on the Suckerpunch kernel too)

Edit: so when I flash my usual kernel, it works fine
[Captivate Android Development] n4n4k1:
I am also running this on Serendipity 6.2, OC'd to 1200, UV'd, memtimings tweak enabled, and I've got to say this is the most solid, snappy and stable setup I've had so far. Amazing battery life and reliability, you guys really do an amazing job.

My Voltage Control Settings:

-------------------------------------------

Scheduler: sio Limit Clock: 1200 Mhz

1200 Mhz - -75mV

1000 Mhz - -75mV

800 Mhz - -75mV

600 Mhz - -100mV

400 Mhz - -100mV

200 Mhz - -125mV

100 Mhz - -125mV
[Captivate Android Development] AReynante:
Is my phone just stupid then? Lol. I'll just try a full wipe tonight
[Captivate Android Development] Soccer_Dad:
I just loaded last night over Serendipity 6.2, and don't seem to be having any problems through multiple boots. I have been hacking my framework to get the look "just so", so I've been through multiple flash/reboot/test cycles, and everything is fine so far.

I'm on 'battery saver' settings, so I'm mildly overclocked (1.2) and undervolted a tad (25-100), with none of the other tweaks. I'm guessing it was a bad flash. Or maybe a lagfix issue - I lost root once converting system to ext4. Some bit just got copied wrong, I guess.

I found the battery loss on Paragon to be more than what I wanted, so I always come back to Speedmod/Suckerpunch/[now]Onix.
[Captivate Android Development] existz:
You can actually leave it enabled, it will still set noatime, but theres not many IO tweaks, i removed most of them for right now since using SIO scheduler...im still in the process of moving things around..adding/removing..etc.. but just leave it enabled to set noatime on all partitions

As for airattatckHD, im not sure, the only thing thats used from JPJ is the kernel modules, not the kernel source itself..so its still JPX source but with JPJ modules
[Captivate Android Development] LNJ:
What version of VC do you have installed? Try uninstalling it first before flashing the kernel. Then install the latest version.
[Captivate Android Development] 13_:
Yes. No problems. Deleted mem timings, uninstalled VC, reinstalled new VC, reboot into CWM, clear cache, dalvik, batt and VC settings, flashed Onix, flashed Onix( I'm paranoid), rebooted, success.

Sounds like you got some stubborn files that don't want to leave.

Sent from a Captivate on Bluedipity 6.2, Onix 2.0.1, JQ1 with Xda App
[Captivate Android Development] H3llstorm:
I've flashed various Suckerpunch and Onix kernels over the last few weeks, and never got stuck on the boot animation.

Two things:

Is it a custom boot animation? I remember seeing somewhere on the forums that these sometimes cause problems.

The only lock-ups I had (after booting) were due to timing scripts in etc/init.d - you might want to check this folder.
[Captivate Android Development] AReynante:
I got it, it wouldn't flash via cwr, so I tried the kernel flasher, and it worked fine. I feel pretty stupid now
[Captivate Android Development] prayii:
Does anyone control their screen brightness manually or does everyone leave it on auto?

Which way would be better for battery life? If you manually adjusted the screen for viewing - not just leaving it on full blast - or leaving it on auto?
[Captivate Android Development] Barbarian:
I always leave it on the lowest setting personally.
[Captivate Android Development] existz:
Same here.. I usually alway have it on the lowest setting, then just adjust brighter when needed..if im out in the sun or whatever..

On another note, updated the test script some, lowered the sampling_rate back down some more, from 5sec to 1sec, see if that makes a difference...also added freq_step , which is the percentage of your max cpu freq the cpu increases/decreases by..default is 5% (1000÷5=200), changed to 10% (1000÷10=100) so it should spend more time at lower freqs..let me know if it effects anything..i still might have to lower sampling_rate down some more, but see how 1sec does (These are Battery Saving Settings!, dont use if you want max performance...ill tweak that next)

http://berryfx.com/RobBeane/Kernel/Files/S_cpufreq_tweak.sh
[Captivate Android Development] abee_13:
We put this in the init.d folder again?
[Captivate Android Development] nappent:
Anyone else have busy box issues? I was installing tibu and I kept getting busybox error but no error messages for details. I went back to #59 and every thing now works. When I install onix I did clear all the cache and d cache.
[Captivate Android Development] existz:
Yep, make sure to remove the old script
[Captivate Android Development] grkmaster:
Just to make sure, Car dock fix is in the Onix build as well?
[Captivate Android Development] existz:
Not yet, havent added it back..but ill add it back with 2.0.2
[Captivate Android Development] grkmaster:
Oh ok.. Im on CM7 right now and debating to come back again even though its a good build but with some issues. From seeing all the posts about how great this kernel with the newer roms, I kind of want to test it out but Car dock has become a necessity now for me
[Captivate Android Development] silverslotcar:
I have been running this kernel for awhile now and I am seeing great battery life with this and Serendipity 6.2. I have minimum brightness on, not using gps, and not using autorotation though. I also have 1200hz oc and a decent undervolt. First four tweaks enabled in Onix recovery too (loving the blue recovery). Good work Existz, keep it up!

UV settings:

step 100 -100mV

step 200 -100mV

step 400 -75mV

step 600 -75mV

step 800 -75mV

step 1000 -50mV

step 1200 -50mV
[Captivate Android Development] goodolsen:
I just changed from Paragon to Serendipity 6.2 and the phone seems smoother with this kernel and Serendipity. Battery life seems improved also.

Overall this is an excellent kernel, thanks for that existz.
[Captivate Android Development] nappent:
Blue is nice but it can be pretty bright at night. I've always been a big fan of the red recovery look, but that's just me.
[Captivate Android Development] RonH54:
Is there or is there going to be an Onix(suckerpunch) Voodoo version. I am about to go back to Darky 9.4 ROM and at one time it was Recommend to use a Voodoo base instead of a Speednmod based Kernel? Not sure if that still true or not.

Thanks
[Captivate Android Development] gibson3659:
I don't know if it is possible, but can you toggle autorotation based on screen state with a scripts? If so, combine it with this scaling script. I currently do it in Tasker (screen off=autorotation off) and is saves a noticeable amount of battery.
[Captivate Android Development] fractaline:
So, I was testing oc1.3 on#59 last night and went to put my son to bed but feel asleep myself. So in about six hours it went through 372 runs of stability test ...........

Yes it did freeze after I backed out. But it was still going when I woke up.

I'm new to oc,ing but that seemed interesting to me.

Sent from a fire fly's abdomen using morse code
[Captivate Android Development] silverslotcar:
Yea bright to show off the beautiful screen. Plus u don't spend much time in recovery so its not likes its draining battery.
[Captivate Android Development] IStern:
Overall, very good update...but I get consistently better results, in benchmarks and real life usage, when I use CFQ instead of SIO
[Captivate Android Development] geokilla:
Hey existz, for your kernel Hz, wasn't 256Hz the Samsung default settings? And 500Hz was the recommended one by hardcore? I just realized that you're the first one to offer only 100Hz and 1000Hz, and there's nothing in between. I haven't tried your kernels yet but wouldn't 500Hz be the best of both worlds in terms of battery life and smoothness?
[Captivate Android Development] existz:
Ah..imo not really...with the 100hz it actually eliminates the kernel hz--user hz conversion ..since both = 100hz, giving better battery life while not effecting performance compared to stock, maybe even 500hz.. so imo, 100hz is the best choice for those who want max battery life,.. its not just about having a lower value, it actually effects the way some things are calculated ..here's a decent read on high res timers http://kerneltrap.org/node/464
[Captivate Android Development] shoman94:
Awesome boot screen... I love simple...
[Captivate Android Development] xThe Enforcer:
Will test tomorrow!
[Captivate Android Development] shaolin95:
So I tried it and was able to linpack and run some Stability Test at 1.5 but at 1.6 linpack almost all the time will not finish...it was fun trying though :-)
[Captivate Android Development] existz:
Ill try to get 2.0.2 up tomorrow, it wont be anything major, probably just have the new boot screen and ill add dock support back .. im still working on some more tweaks and some features, but might be a few more days to test them
[Captivate Android Development] shoman94:
sweet

Can't wait
[Captivate Android Development] fractaline:
looking forward to the boot screen:)

question about the scaling values, in onix2 it seems like using the performance tweak would allow more uv'ing and possibly compensate a bit for the battery use???

reguardless of the battery would that tweak allow more extreme uv settings?
[Captivate Android Development] xtremekilla09:
I know you probably already decided on the boot screen, but I wanted to give it a shot. I have a few more in mind, I will put them up when I am done.

If you have anything particular in mind, I would gladly help out.

This kernel rocks!
[Captivate Android Development] snorkle:
Dont know if this has been addressed yet, but after installing this my phone doesnt play music from the speaker, and after putting in my headphones the Speaker works but just the speakers and only when the headphones are in. Also i cant hear anything when i call anyone unless i put it on speaker.
[Captivate Android Development] echelonMCRhartgrenade:
I also had this problem! I just rebooted my phone then everything went back to normal :)
[Captivate Android Development] shoman94:
I gotta question for you... Is there a tweak you can do to boost in call volume some. I'd like to have that extra boost for loud situations.
[Captivate Android Development] goodolsen:
Awesome been waiting for the bootscreen "fix". I like something a little fancier than the current one.
[Captivate Android Development] snorkle:
tried that a couple times, didnt work =*(
[Captivate Android Development] sinichi21:
try to wipe the 2 cache, then flash this again or try using odin to flash the kernel
[Captivate Android Development] nickm50:
THIS is AWESOME!
[Captivate Android Development] grkmaster:
So you have 1300mhz with CPU tweak off and getting around 1800 on quadrant? is this quadrant standard or advance?

Also I im running pretty stable at 1300 with pretty much the same freq. steps. and the four options enabled in tweak options... Thanks for a starting point to use :-) and existz, seriously awesome. I think im going to try and push the limit of the phone! (slowly though) lol

EDIT:

So as of now as my phone is charging and I put it to restart and the phone doesnt reboot (seems to freeze as it shuts down) I take out the battery and the usb turn it on and place the usb on as its booting and I come to the phone to see its frozen again on the lockscreen. I dont know if this is related in any way to a charging death issue? Im gonna see if I can replicate it and see if I can get you a log. Also whats the program to do a stability test to make sure my phone can hang for a while with 1.3ghz

Im trying to do the kmsg but it doesnt seem to work. All it does is create a log.txt with no info and file size 0