yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
For the guy setting UV at 100 on all, follow the mini oc/uv guide in the OP, you need to start with 25mv and test each frequency separately, there will be different UV values for each frequency ...

As for cache as ext4nj, that's normal, as its only the cache partition it does not have to be as stable as data partitions, with no journaling it allows larger apps from the market to be downloaded, since there's no journal , there's more space. Its probably not a good idea setting data partitions with nj as if they actually get corrupted you will most likely have to wipe clean. But the cache partition is fine. (I actually format mine after 5 or so kernel flashes and clear dalvik cache to prevent any issues where I flash so many everyday..just a habit)
[Captivate Android Development] AtoZ0to9:
could u recommend an UV value since the frequency has been raised? I installed #44 and have them at 100 right now... no freezing... and i understand that whatever I do is on me, and me only, just things have been changed, and I'm not sure should I be running at 100 anymore...
[Captivate Android Development] AtoZ0to9:
Sorry for dbl post, I followed that guide with the last kernal and 100uv on all clock speeds passed the tests, just this kernal is different and I'm unsure will my original settings work like they used to. and I realize whatever I do is my fault.
[Captivate Android Development] LimaI896:
The brightfix is amazing for at night in dark places to not be blinded and much better in day light. A must have IMO. :cool:
[Captivate Android Development] Auridran:
Maybe I should try it again. I get stuck in my ways sometimes.

I'm gonna try this kernel and let you know what I think!
[Captivate Android Development] tietherope:
Sorry for the noob question but what does the brightness fix do?

I understand what it does, but I mean, does it make auto brightness the only setting? Or could I still use the Brightness Level app? Thanks!
[Captivate Android Development] silverslotcar:
It lowers the brightness for the automatic brightness setting. So instead of being X bright, now (in the same light) it would be Y bright. Y being less bright!! If that makes sense.
[Captivate Android Development] Auridran:
So I guess I was just set in my ways. I like the brightness fix. So far I love the kernel as well, but gotta test it for more than a couple minutes to make a final judgment :p
[Captivate Android Development] cumanzor:
Instead of X, it would be X-X' where X' is whatever value was set by HC.

Been playing with it for while, I think I'm getting used to it :p
[Captivate Android Development] davwman:
Trying to install wont boot and fc's all over the place.
[Captivate Android Development] c0ldburn3r:
Should probably start his own thread instead of cross posting in a kernel thread.

I love the Brightness fix, I hate being blinded in the morning when I stumble out of bed to check for messages. Tested IP v6 last night and all is well, have NEVER seen wifi issues but then again I'm unable to use the 1.28ghz version. Phone HATES that speed. 1.12ghz is perrrrfect.
[Captivate Android Development] ryude:
Did you flash it from a fresh install or from another ROM? Also, you should PM me I don't want to take up too much more room in this thread.
[Captivate Android Development] LimaI896:
Im running 1.28 but its only stable when uv, crashs when its at normal voltage. If your able to be quick on start up to get to the voltage app then you can uv to stablize.
[Captivate Android Development] whitesox311:
so far doesn't seem any faster or slower than speedmod even at 1280, but then again it's only been flashed for about 10 minutes....shrug
[Captivate Android Development] existz:
I personally only use the 1.12ghz version cause with the stuff I do on my phone I don't benefit from any higher clocks, you might not notice any difference cause you might not be doing anything that needs the extra cpu speed , when I made this kernel OC was at the bottom of my list, the greatest feature about this kernel over Hardcores, is the ability to UV
[Captivate Android Development] c0ldburn3r:
Eh, I'm more than satisfied at 1.12 Ghz. Seems to be the sweet spot for my phone. :D
[Captivate Android Development] LimaI896:
I only need the extra hz as the psx4droid likes it a lot. Other then that the 1.12 is great.
[Captivate Android Development] LimaI896:
existz is there a way on the next update the 1280 is already undervolted so it can be stable on start up?
[Captivate Android Development] rootnik:
Not really possible, under volt settings are specific to every phone.
[Captivate Android Development] whitesox311:
ah, okay.

i'm going to see how the battery is on 1280 because now that i'm delving into the phone a bit more, it does seem to be a bit more responsive

thanks for the kernel!
[Captivate Android Development] Mr Sin:
Amazing!!! Running Continuum 2.0 LE + SuckerPunch 1280 @ (1280 - 100) 75, 125, 150, 150, 150, 175. Ext4/2 all + all recommended tweaks. I have a much lower UV at same OC with other kernels without losing stability, now to test battery... I would post benches but most are not cpu related, linpack at 17.8-18.3 for starters :) Great job Existz!!

Update: Sorry I forgot to mention it was cfq, now it's UV'd to (1280 - 100) 100, 125, 150, 150, 150, 175 :D
[Captivate Android Development] LimaI896:
Wow your uv settings are intense. Tried to do -150/-150 and lost stability
[Captivate Android Development] cumanzor:
I do 75/75/125/125/150/150 (1280 - 100) and it holds out perfectly. Been trying 175 for the lowest values but they are unstable.
[Captivate Android Development] existz:
No one is probably going to be able to tell ya anything besides 25mv as every phone is different. Some people can handle 100mv on a certain frequency, some can't handle 50mv, there's really no recommended settings, just going to have to try each step, 25mv at a time... watch out though, an unstable or to low of a UV will cause charge death, lockups, reboots,freezing, FCing...etc.. read through the thread, there's been alot of discussion about how to start out testing ..alot.. if you have any problems first step is to lower your clock or uv..

And remember, even if it passes a million passes in stress test, if the uv is to low it can still cause charge death

Also remember, that most stress test usually maxes the cpu out and test from there, so if your 600 step is unstable, your not going to know it with a stress test, since only the max freq is being tested..im not sure about all of them since its been so long since I've used one, if it passes what I need it to do everyday, then that's good enough for me...but you can try setting the max clock in VC down a step then run it, then knock max clock down again, keep doing that till you go thru all the frequencies..you can read a few pages back on the discussion we had about this as well
[Captivate Android Development] Auridran:
I can't wait to flash #44! I'm going to wait until I go to bed though, as I want to see just how long I can make this battery last.
[Captivate Android Development] slaman:
I have tested frequency by frequency starting with incremental under voltage... Found out that 400mhz was a limiting voltage and could only take -25mv...all frequencies under that are at default otherwise they result In sleep deaths....

After running at least 15 passes in stability test, I use the camera to test...switching between camcorder and camera normally freezes the phone if it it's too under powered despite passing stability tests...
[Captivate Android Development] pizz0wn3d:
Aww mann, another build up already? I hate missing out on all the fun >.<

Went to Odin flash back to stock so I could try out the Perception 10.3 rom, forgot to disable the ext4 lagfix stuff and now I'm stuck in a boot loop. >.< None of the button combinations to get into download mode are working, so now it looks like I have to go make a jig. fasdfsdfgsdf.

Now I amz a sad pandas. =*( I wish radioshack was still open.
[Captivate Android Development] johan8:
Actually you don't need to disable lagfix in switching kernel, because they all using ext4 FS.

I was using voodoo lagfix previously, then switch to speedmod,

and now switch to suckerpunch.

Nothing need to disable.

I think you did something wrong.....

Try hold Vol-Down+Power (not both VolUp+Dn) to enter Download mode.
[Captivate Android Development] AtoZ0to9:
I have done MUCH testing to identify the problem with my setup. Before flashing #44, I was using #41...

Everything runs stable on both, and performs amazingly as expected from your work. But still a problem exists and I do not believe it is my phone nor user error.

Here are my results:

#44 1200OC, 100UV on ALL selected

#41 using same settings:

Went back to #44, and got nearly identical results as the first screenshot

Second run with #41, same settings:

Don't take this wrong, I love your kernals, and am in NO WAY COMPLAINING NOR DISRESPECTING YOUR WORK, but something is not working right.

Any ideas what it may be?
[Captivate Android Development] AtoZ0to9:
Try to get into download by holding both vol buttons while phone is off, and inserting USB...
[Captivate Android Development] pizz0wn3d:
I've tried every button combination I've come across, to no avail. (volume up, vol up+down, vol down, vol up+down and power button, etc...)

I wasn't switching kernels, I was using Odin3 one click to revert back to stock 2.1, and it went through successfully. Then I tried to boot up my phone, which it did, over and over and over and over and over and over and over hahaha.. :(

So it looks like i'm going to need a jig to solve this problem, unless I can somehow get it to work before I finally give up and go to bed tonight.

Feel free to give me any advice you guys feel like, but I don't want to derail this thread tooooooo much. :P
[Captivate Android Development] pizz0wn3d:
Are you using SetCPU? If so, uninstall it. It makes bad things happen to your performance.
[Captivate Android Development] xbeamelite:
im also getting low quad scores of 1200. But I'm hitting 16 in linpack. Don't know why I'm getting such low quad scores. No set cpu, oc to 1200 on vc
[Captivate Android Development] JEANRIVERA:
try these it worked for me in a boot loop:

take the battery out for at least 5 minutes

press all the buttons on your phone with the battery out for 30 sec. (this will drain any energy left on the board)

then press vol up + vol down at the same time while connecing to usb in your pc it will go to download mode if it worked

good luck!!!!
[Captivate Android Development] pizz0wn3d:
Try messing with your UV values at different frequencies. I was getting ~16 linpack scores at one setting before I lowered the uv by 25mV (can't remember which frequency). After the change my linpack went back to averaging 17.5

But of course the plural of anecdote is never going to be facts, and I'm no expert on how these things work.
[Captivate Android Development] pizz0wn3d:
I'll try that out, but honestly I think my phone is just ignoring the hardware buttons altogether because it tries booting as soon as I connect it to the usb cable. I read something about this being known as a hardware lock?

Regardless, I'll try anything at this point. I just wish I lived next door to a 24/7 Radioshack.

/crossfingers
[Captivate Android Development] JEANRIVERA:
let me know if it worked
[Captivate Android Development] pizz0wn3d:
No go :(

Tried putting the battery in both before and after connecting to usb, and even connecting to usb without the battery at all just for good measure. McWeaksauce.
[Captivate Android Development] itdiestoday:
@ B-Naughty. Are you sure you have the 1200 step enabled in vc app? If you have system panel app, open that and move the screen around while in that app and see if the cpu jumps to 1.2ghz. That'll tel you for sure if you're oc'd or if your settings were applied.

Sent from my Captivate

Serendipity 5.5

SuckerPunch-SmR #41 @ 1.2ghz

LF a modem that will survive the DC METRO gauntlet
[Captivate Android Development] justmart:
This did the Trick!!!!

I turned off my DATA at night and the battery dropped from 89 to 88 in 6 hours! That is AWESOME!
[Captivate Android Development] bclark:
Great! I'm glad it worked!
[Captivate Android Development] davwman:
That's normal for this kernel. It is one of a kind! Even with data on I've yielded similar numbers with my setup. Samsung wishes it had developers like this in house! Before my current setup I was seriously considering getting rid of this phone and have not thought about it since!

Ryude's Precision v2.0

Suckerpunch 100hz Latest

Jl2 > Best on Long Island

Ryude's Amazing Monochrome
[Captivate Android Development] beerbaronstatic:
What I do is take the battery out, plug the phone into usb, hold down the volume keys and reinsert the battery, should put you into download mode
[Captivate Android Development] justmart:
It is possible to TURN OFF data while the screen is OFF. WITHOUT Tasker. Thanks!
[Captivate Android Development] lrs421:
How does the real world experience feel? Benchmarks are useless. When I ran eclair I use to hit 2k with one click lag fix and it never felt as snappy as this. In other threads devs ignore quadrant results for these same reasons. They do not validate the speed of your phone. If you want a higher score flash the non xt version and enable faster mounts. In my experience the non xt version scores higher in quadrant but again that doesn't mean anything.
[Captivate Android Development] lrs421:
All of a sudden the static at&t screen has activated my OCD :) Its gotta go, lol. 10mb be damned!

By the way, In digging the 200hz version, so is my battery ;)
[Captivate Android Development] ccdoggy:
use adb to send the command: adb reboot recovery

adb goes live about half way through the kernel loading and so you can pass commands into it if the host has usb debugging enabled.
[Captivate Android Development] zecstone:
help please

I'm new to this, performance is awesome but I get static over Bluetooth calls. Don't know how to fix this.
[Captivate Android Development] lrs421:
What modem are you using? Is it a non i9000 one?
[Captivate Android Development] existz:
Make sure to use an i9000 modem, this is an i9000 kernel made to work on the captivate..there's quite a few floating around, jk3 jk4 jl2 jl3 jpd kp1
[Captivate Android Development] zecstone:
I'm on Simpfinity 1.60 rom, how do I check what modem I'm on? Lol
[Captivate Android Development] existz:
Settings/About Phone/Baseband Version
[Captivate Android Development] lrs421:
According to the op of the rom you're using Bluetooth static is a known issue. Sounds like modem incompatibility.
[Captivate Android Development] zecstone:
My baseband version is I896UXjL1. Which one do I need to flash with?
[Captivate Android Development] lrs421:
Any i9000 modem. Existz mentioned a few in his second to last post.
[Captivate Android Development] zecstone:
What I really like is the hardcore brightness fix. Is there any other way to get this
[Captivate Android Development] lrs421:
Basically makes it darker in low light and brighter in the sunlight. Its built into the kernel.
[Captivate Android Development] zecstone:
I had flashed the znkp1 with the same results. Do I have to flash znkp1 before flashing the SuckerPunch?
[Captivate Android Development] existz:
You can flash it before or after, doesnt matter, the kernel will not touch the modem, so if you flash it first it will still be there after flashing suckerpunch
[Captivate Android Development] lrs421:
No it's the ROM. Its built from a non i9000 source. You need a i9000 rom, kernel and modem for full bt and hsupa support.
[Captivate Android Development] shaolin95:
Anyone getting 1400 with the 1.4Ghz option? I normally get about 1380 or so when looking at it with Stability test but with this one I am getting 1350Mhz instead which matches the linpack performance numbers so is not quite getting me the 1400Mhz to break into the 19s.

Regards
[Captivate Android Development] sjavvaji:
Same issue
[Captivate Android Development] zecstone:
Ok thanks guys I understand now
[Captivate Android Development] existz:
I changed the frequency code based on laststufo's setup, so something could be off...but ill look into it and get it fixed

EDIT

was looking over the code and i see what the issue is, ill have it fixed in the next release
[Captivate Android Development] slaman:
This method still didn't work... got a freeze when trying to boot into recovery from the extended power menu... lowered all my highest UV settings, still freezing... now it's a game of trial and error
[Captivate Android Development] existz:
Ill have Build #45 up soon..mostly bug fixes....anything else you guys can think of that needs to go in this build?

-Updated frequency code, should correct 1400mhz being 1350mhz

-Reverted back to 340mb ram (tiny snow on boot fixed)
[Captivate Android Development] shaolin95:
Sweet...thanks for looking into it so quickly...not that there is anything wrong with 1350Mhz of course :D
[Captivate Android Development] lrs421:
Well.... :-)
[Captivate Android Development] lrs421:
Existz, how about raising the volume to -7db in voodoo sound like hardcore does. I like the boost and it'll keep me from adjusting it :)
[Captivate Android Development] existz:
Did previous builds show 1400 correctly, just build 44 was wrong? or has it been doing that on every build?
[Captivate Android Development] davwman:
Existz, are you still using 100hz version?

Ryude's Precision v2.0

Suckerpunch 100hz Latest

Jl2 > Best on Long Island

Ryude's Amazing Monochrome
[Captivate Android Development] shaolin95:
To be honest I have not tried it since the last versions you sent me as I had issues even getting 1344 stable with those but this one at 1350 seems very stable and fast so cant wait for 1.4 to see if I get it going too :D
[Captivate Android Development] sicmadek:
Im having the issue as the last build. No matter what clock and voltage setting i use i cant get higher than 1250. I can get almost 1100 at 800mhz then 12xx at anything up to 1.4ghz. The phone never freezes so im wondering if the setting are ever sticking.

Im on precision v2.5 btw.
[Captivate Android Development] existz:
Getting ready to upload..1400 step is fixed, getting 19+ in linpack..

As for adjusting volume, ill look into it for next release, theres a few sound tweaks i want to do, so will save that for another update :P
[Captivate Android Development] existz:
Yea something is not sticking, are you sure you have the correct states enabled in Voltage control app?
[Captivate Android Development] existz:
UPDATE

Build #45

-Reverted back to 340mb ram (fixes snow on boot)

-Updated frequency code (fixes 1400mhz being 1350mhz)
[Captivate Android Development] sicmadek:
Yes enabled states. When i go to system info inside the quadrant app it says cpu frequency 800, min 100, and max 1400. I dont if its accurate at all. Can someone else check theres and see what it says?
[Captivate Android Development] AtoZ0to9:
Nah, I'm using the VoltageApp in the first post, not the second post.

Thanks for the tip, gonna try that. Pretty sure it was enabled, but only by performance with the scores, and also by trying 1400, and having my phone randomly reboot, so it must be taking the settings.

Yea, I'm gonna try the other kernal, and when #45 hits, I'll try that as well. Phone feels solid. The settings I use are 100 for everything, and things wok fine... I'm ext4 all the way...

Thanks for all the help and info guys, I'm just gonna keep trying different things until I get the best results...
[Captivate Android Development] dizx:
I...

Cannot...

Keep up...

But I like this kernel! :)

100 UV across with 800MHz cap, no lagfix.
[Captivate Android Development] slider2828:
I don't hate the snow in sunny california for the extra worthless 10MB hahaha... I can't get 1400mhz anyways ahahah
[Captivate Android Development] existz:
Quadrant reads the settings for the cpu code, so it should say max is 1400 no matter what you set it to, because that's the max available in the code, also for current frequency, it reads the current frequency, so if its at 800 at the time of reading it, it will show 800, if you go back out and back in it will show if the cpu freq has dropped, so it might show 600 or 1000 next time, so all that is correct
[Captivate Android Development] johan8:
Woo !!

I like 350MB and I don't mine the snow, is it ok to use #44 ?

:p
[Captivate Android Development] existz:
Yea you can use it if you want, the 350mb is useless as android starts killing processes to save memory anyways, way before it gets close to 340/350, so you will probably never benefit from it, or even need it

Mine hardly ever gets past 250mb, let alone needing 350
[Captivate Android Development] AJerman:
Is this something that can be adjusted? The point at which Android's auto kill kicks in? This being my first Android phone, I'm really surprised how much memory I really do use. It gets annoying trying to watch a flash video in the web browser and it killing everything else running.
[Captivate Android Development] johan8:
Yes, you're right:p

It is so difficult to reach 300MB unless there is any single software need huge amount of memory.

I don't use any auto-taskkiller, I know android will do that for me.

So I also wonder is it possible to tweak its auto-kill behavior,

then more apps can run/keep in background.
[Captivate Android Development] olo567:
Excuse my ignorance, but the 2 files you continue to update are now XT and non-XT versions. The XT has Kernel Hz as 1000 and User as 200? And the second is what? 500 and 100?

Can anyone give a brief overview of what exactly are Kernel and User Hz? Not urgent obviously, just can't find any solid info around.
[Captivate Android Development] shaolin95:
Did you upload the right file? I still show 1354 instead of the usuals 1380 or and still not hitting 19s. :-)
[Captivate Android Development] existz:
Ill double check, but im sure I did.. im hitting 19.5

Which version, XT or non XT? Im assuming XT...check how much ram is left, if its 350 its the old version, if 340 its correct

EDIT

just downloaded from OP and getting 19.2-19.5.. I've noticed when using 1400mhz, I have to enable the 1300 state, save settings, then disable it, then everything is fine, 19+ in linpack.. not sure why...but ill look into it
[Captivate Android Development] shaolin95:
OK I will try doing that as it is indeed the right one.

Could it be the Andromeda Rom?

I tried 1300 and stability test shows 1257 for example.

So I guess I need a 1450 version to hit 1400 with this Rom/kernel combo lol
[Captivate Android Development] lpsi2000:
I still can't get linpack at 19 on with new kernel, anyone else able to get it.
[Captivate Android Development] shaolin95:
Me neither. Are you still showing 1354 in Stability Test?

What ROM?
[Captivate Android Development] lpsi2000:
Can you post your uv configuration so we can try that because I am not getting the 19 and 19.5 would be nice.

Edit: and my RAM does say 340MB
[Captivate Android Development] lpsi2000:
I am was the same ROM in your signature then I just now flashed back to my customized Darky's 8.X because I wanted JPY to check another issue.
[Captivate Android Development] existz:
The bogomips in stability test is not the same as mhz, that's why it shows differently..(shows 1354 bogomips, and not 1400).. http://en.m.wikipedia.org/wiki/BogoMips?wasRedirected=true

What I done was activated 1200,1300,1400 steps in vc and saved it, then turned around and unselected 1300 and saved again..then in linpack I get anywhere from 19-19.5 mflops

My UV settings are (from 1400,1200,1000 down)

50,75,100,100,100,125,125,150

You can check the max set frequency by typing this in a terminal emulator...

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Captivate Android Development] shaolin95:
I see but with every kernel I would show 1378 when going for 1.4Ghz never 1354 and my linpack results confirm the speed showing though.

I will try those steps again.
[Captivate Android Development] AJerman:
I've gotten 19+ in the past with 1.4 GHz, but not with build 45. I am trying XT though, and I've always used 100 MHz before, in case that makes a difference.