yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] DAGr8:
I dont understand .. since 1.45 / 1.54 . none of these kernel allowed me to run anything close to 1400 ..

Setiron .. whats the deal ?

1.54XT I can boot at 1502 and do some random stuff it will only freeze doin specific things ..

even 1552 will allow me to boot and do some linpack but its way to unstable

so how do you explain 1.45 / 1.54 are the only kernel that will allow me to run @1400 ????

the others simply freeze when I click apply not even doin anything else. .

Edit: freezing when applying 1288 even ...

so I thought maybe its rc3 doin somethign wrong , so I manually set it on boot @ 1288 .. it boots fine and it will apply 1400 wihtout freezing ..

weird ?
[Captivate Android Development] aleadam:
Try 1440 on the 1.5.6. It is very stable for me. I could not keep it on 1400. It may be due to the gpu freqs. Maybe my phone likes to also oc the gpu a little bit ;)
[Captivate Android Development] shaolin95:
For me only 1.4.6 was I able to do 1.45Ghz 100% stable at -75 to boot. The only thing that bugged me about it is the low linpack of 17s which do not seem right for such speed.

Other than that I normally max out at 1.350 if I want to be 100% stable.

I used to be able to even linpack at 1.6 and 1.5 with some kernels but not anymore.
[Captivate Android Development] aleadam:
Second linpak I did this morning after upping the freqs was 20.3 :cool:

Happy man :D
[Captivate Android Development] shaolin95:
Yes that looks fine which is what bugs me about 1.4.6 at 1.45 only doing 17s
[Captivate Android Development] DAGr8:
actually I m thinkin the problem was with RC3 gonna report it to XAN ,,

because

1 booting 1.56XT

2 then saving as boot using UV app (default @ 1ghz)

3 manually edit files in init.d folder

4 reboot

5 everything works as well as it did on 1.54XT (more stable it seems )

For some reason using the app to adjust the OC/UV after that works perfect no more freezing

so it seems my problem was somethign my cpu didnt like when using the 'apply for now ' even at low OC like 1288 .( well low for me anyways)

that WAS NOT the case on 1.54XT I never had a prob ...
[Captivate Android Development] eSPyeL:
Try chattr +i on the files.
[Captivate Android Development] MikeyMike01:
It says "script created".

Is there something that could be done with that script? Just a thought.
[Captivate Android Development] draxionangel:
Very good point, for some reason I was thinking about it backwards(probably due to switching back to linux recently).

So noop it is.

Thanks for pointing that out and correcting me.
[Captivate Android Development] bts0uth:
Im a little confused, lets say this:

I set the value I want and hit set values and then set on boot.

I reboot and come back to the app and the sliders ARE still what I set them as.

Is it just showing me this and its not really undervolted?

Or is the problem people are selecting set on boot and then after a reboot the app shows the voltages back at stock?
[Captivate Android Development] xan:
Hello guys.

Please check if there is a file /etc/init.d/S_volt_scheduler present. It's the script created by Voltage Control app, it should get executed on every boot. Check its contents. It should be something like that:

#!/system/bin/sh
su
#set UV
echo 75 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVLF_mV
echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/UVHF_mV
#set scheduler for stl, bml and mmc
for i in `ls /sys/block/stl*` /sys/block/bml* /sys/block/mmcblk*
do
echo "noop" > $i/queue/scheduler
done
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Captivate Android Development] SetiroN:
v1.1 out

added BFQ I/O scheduler, updated Voodoo color&sharpness

Still waiting on xcaliburinhand for a BLN update. :)

Thanks to Bedwa for his donation!
[Captivate Android Development] bts0uth:
BFQ I/Q scheduler

what does this do?
[Captivate Android Development] SetiroN:
http://lwn.net/Articles/306641/

noop might still be preferrable tho-
[Captivate Android Development] lpsi2000:
When we use overkill configuration for any of the lagfixes, why is the DB size on 124MB. I did an overkill jfs and when I went to restore system from backup, It ran out of room. How do I fix this?
[Captivate Android Development] arffer:
After reboot, the sliders (and the scheduler setting) are back at stock. The UVxx_mV files are also set back to '0', so its not just an illusion, the settings really do go back to stock after reboot.
[Captivate Android Development] bts0uth:
Well then I must be lucky because my sliders don't reset after reboot. Thanks for clearing it up for me

Posted from my Captivate running Doc's JPO v7.5 rom with SetiroN's i9000 SuperOptimized, ULF, OC/UV, 340Mb, Re-Oriented kernel v1
[Captivate Android Development] KaLiBLeeK:
Just flashed 1.1; got JFS overkill setup earlier after flashing 1.0.1.

Sweet geebus, I love this kernel. Haha. Smoothest my phone has ever run.

Sent from my Samsung Captivate (XDA-App)
[Captivate Android Development] SetiroN:
Enter the advanced lagfix menu and disable Bind.

Next item on the list, besides BLN, is checking init.d execution. I don't have time right now, but I'm going to educate about it as soon as I can. I have a feeling CWM optimization scripts override script execution.
[Captivate Android Development] arffer:
I checked, and yes, that file is created. It is identical except for the last line is missing, as I do not have mine set to limit the max freq.
[Captivate Android Development] xan:
Well.. If the file is there, problem is elsewhere. Try to run this script (or the one which u got) manually, and see if it runs and sets the UV and sched. If it does, the kernel has different/no support for init.d scripts.

BTW there could be a possible problem with 1.1 kernel, since it added BFQ. Voltage Control wont recognize it... You wont be able to select BFQ from VC and it wont be able to detect running sheduler (any). Please report, will try to change implementation soon.
[Captivate Android Development] MarlowXim:
Possible BLN fix

I'm guessing you took parts of the kernel from hardcore's source here xdaforums.com/showthread.php?t=822756

He's updated the code such that he also had a similar BLN problem. Perhaps updating with his new code might fix BLN.
[Captivate Android Development] arffer:
I'm still on v1.0.1 without the BFQ.

I did try and run it manually from within the /etc/init.d directory as su:

./S_volt_scheduler and just for completeness sh ./S_volt_scheduler

No error was reported, just came back to the shell prompt.

I checked the UVxx_mV files, and neither were updated. I also checked the timestamp on the files, and it had not changed.

Permissions on both files was 644.

UPDATE:I tried running the script again, but this time not as su. And it ran just fine, it updated the UVxx files. It appears that having the script execute su internally when it is already being run from an su user level prevents it from running. I tried commenting out the 'su' in the script, and as expected it then ran fine when run from an su userlevel. I have no idea as to why the redundant 'su' would prevent the script from running, it should just be ignored.
[Captivate Android Development] Cezar`:
This is by far the most complete kernel I've used so far!!! Congrats man!!

1 note: it can be used on roms which had installed excalibur's kernel. Just leave the first option untouched and put the rest as described in the first post and chose the first option after rebooting the phone
[Captivate Android Development] airbillion:
Can we still use the voltage control with the BFQ I/O scheduler or does this do something else? I read the release notes, but I'm not sure what it does.
[Captivate Android Development] xan:
Just came with the same conclusions :) Check ur PM, thanks for your report, it was really helpful!
[Captivate Android Development] shaolin95:
Interesting. Testing right now.
[Captivate Android Development] r.iqbal87:
Anybody else getting random restarts during app use? Im running 1.4.7 1400xt . I've tried various voltage combos but the issue is persistant. Im assuming it has something to do with the config since, rather than freezing as would occur under under high cpu load, it automatically restarts, weird huh? Anyone else experience this? Any solutions?

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] aleadam:
I get restarts some times with high OCs and/or too much UV. Try a lower freq kernel.
[Captivate Android Development] shaolin95:
Tried this but I am not getting the settings to stick...argh!
[Captivate Android Development] existz:
It keeps freezing for me at 1344 but I can flash 1.4.7 and 1344 is 100% stable.. I did check and 1344 is the max freq, it is sticking ... so iono.. I've tried different UV settings and still does it no matter what... I've set it with xans app and set it manually ...so guess back to 1.4.7 for me
[Captivate Android Development] aleadam:
Try removing 1200 and/or 1288 steps
[Captivate Android Development] shaolin95:
I am having issues removing steps is like my phone wont obey me...what are you changing and where exactly?
[Captivate Android Development] r.iqbal87:
I quoted the wrong post I meant to quote the first one suggesting to try a lower clocked kernel.

Thanx for the response. Yes, that would be the first approach. And I have tried many of the different clock speeds with their respective kernels. And it is true the issue does not occur with lower speeds. But the reason I posted is because I feel that it is possible to achieve stability with the kernel I have, because normally when I flash a kernel with a high clock speed and my phone cannot handle it, the indication that the kernel is too much, is a complete system freeze. This situation is different, as rather than a complete freeze I get an auto reboot. An anomoly to the normal situation of freezing, I use to determine whether my phone can handle a kernel or not. That is why I was leaning toward a possible configuration issue that may be causing the reboots. Also, when the phone is on, it shows complete stability, based on being able to run benchmarks back to back with quadrant advanced and linpack as well. So, I don't understand how it does not auto reboot during those types of high stress situations, and why it does under low stress situations? Is it possible that auto reboots occur due to the gpu and that freezes occur due to the cpu? Since the gpu is clocked at 205 on the kernel im using which is different, I believe, from the standard 200, that previous kernels had it clocked at?

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] existz:
Already tried that...I had normal 100-1000 and then 1344 but still locks up..
[Captivate Android Development] aleadam:
I just use voltage control app. If that doesn't work try using a terminal emulator in the phone or adb and the good old echo 0 0 1 (etc) > states_enabled_table
[Captivate Android Development] shaolin95:
From my experience the problem is you are not really pushing the phone enough to check stability use Neocore for GPU and Stability Test (kinda of prime95 for android) to really test the phone. At least 30 loops of Stability test and a few of Neocore.

For me is always tricky to find a balance UV setting where Neocore does not freeze and Stability test does not crash.

From what I can see, at least for my CPU, Neocore freezing means too much voltage and Stability Test crashing measn too low so finding that middle ground...that is the holy grail
[Captivate Android Development] aleadam:
If it reboots when idle maybe is too low voltage on the low freqs, or too high a voltage jump to get to high freqs when needed. But, again, as I told you before, sometimes I just get a reboot instead of a freeze. And sometimes an app just disappears without the f/c window. Who knows what's happening with the cpu in those moments...
[Captivate Android Development] shaolin95:
This is so much trickier than any PC CPU I have ever OCed that is not even funny! :D

BTW, can some of you do a test for me please guys.

Test the 1.4.6 1.45Ghz Kernel (XT or normal) and let me know how it goes for you.

That is the only kernel of all I have tried that allows me to hit 1.45Ghz fully stable while the others max out at 1.350Ghz fully stable.

A 100Mhz difference is quite outstanding.
[Captivate Android Development] momulah:
Do I flash through ODIN in PDA slot?
[Captivate Android Development] shaolin95:
If you are flashing the .tar file then yes.
[Captivate Android Development] aleadam:
Can you send it to me? I don't have it here. I'll try first the jpx rom and then I could play with a few kernels.
[Captivate Android Development] johan8:
Simply do not do any UV .....0 0 0 0.....

Probably you haven't give enough working voltage.
[Captivate Android Development] sjavvaji:
how do i know the uv settings are working...i applied them and they stick through boot...i have them all set to -200mv and the phone is running fine...i am using the voltage app version 3 alpha...im running on 1.4.7 1400mhz w/assonance 5.0...am i doing anything wrong? on cogkernel4...i had to set them around -125mv to -175mv for stability
[Captivate Android Development] shaolin95:
Added a picture of how good it does for me..33 loops of Stability Test. I have done 100 with that one.

Thanks mate!
[Captivate Android Development] johan8:
Do you know what is UV(under-voltage) ?

Let's say the CPU working voltage is 1.3V, you set -200mV,

the voltage supply to CPU will become 1.1V,

it would be unstable due to insufficient correct voltage.

You set all to -200mV !???:eek:

Good for you can survive with that!

Try NOT to deduct too much, your CPU will get mad.

And, we are not able to check the UV value is really working or not,

all you set in VC is just a value.
[Captivate Android Development] johan8:
All 1.4.6 are here

http://xdaforums.com/showpost.php?p=9789491&postcount=1965

But I think 1.4.7 would be better.
[Captivate Android Development] shaolin95:
The test is for 1.4.6 1450Mhz because it has been the only one, and I have tried them all, that has given me a fully stable 1450Mhz speed...100Mhz over any other I have tried.
[Captivate Android Development] johan8:
Now I'm trying 1.5.6 xt.

so 1.4.6/7 1450Mhz, or 1.5.6 1450Mhz,

which is better ?

If I have time I would also try them all.....
[Captivate Android Development] shaolin95:
My phone has only done 1.45Ghz with

1.4.6

BUT the the weird thing is that linpack is only in the 17s which at that speed should be in the 20s or at least 19s
[Captivate Android Development] Xstop:
LOL, Your crazy man...! :D

But from what I've read, you've done extensive testing to find the right speed that will give you 100% stability. So the current speed your running it at now, which I'm assuming your sig, does the back of your phone get hot at all?

I'm running 1.4.7 @1200, and it still gets warm back there. But with no stability issues at all.
[Captivate Android Development] shaolin95:
Not much really although Utah is pretty cold where I live near the Spanish Fork Canyon any way :-)

I run it at -75 UV so that helps too.

Between work, the Ice Rink and flashing the phone...thats like 90% of my day
[Captivate Android Development] lpsi2000:
Yep, I am in agreement with you there. I love the 1.4.6 version 1.45Ghz. but my Linpack is at 18. I see you are now using the ROM I have been using as my based for my customized version. The way I have that ROM right now it is just as fast if not faster than Axura. Which modem are you using?
[Captivate Android Development] johan8:
I'm using 1.5.6 1288Mhz, linpack is 17~18 :rolleyes:
[Captivate Android Development] K1kk0m4n:
Thanks For this :)
[Captivate Android Development] shaolin95:
Your point being? Did you read the previous posts...this has been mentioned already plus I recall Setiron(?) mentioning something about linpack results not being completely a deciding factor because for most of the phone things CPU speed was still king so that is what I am trying to determine here...if 1.45Ghz is better than 1.35Ghz or lower even with lower linpack results... :rolleyes:
[Captivate Android Development] zippox180:
I keep getting a syntax error when trying to flash cwm kernels. Tried 1.5.6 xt and 1.5.6 and 1.4.7 no luck any ideas i apologize in advance if discussed in my work van not alot of time to search.:p
[Captivate Android Development] shaolin95:
Did you try Odin as well?
[Captivate Android Development] johan8:
You need to recognize the file, it is not a recovery mode update file.

Flash it in odin.
[Captivate Android Development] capita:
If I'm not mistaken, he was trying to flash the cwm versions, not the odin flashable tar. I got the same syntax error when I tried flashing the 1.56 and 1.47 cwm variants.

Going to go the odin route.
[Captivate Android Development] aleadam:
True. 1.5.6 CWM does not work.

I just made and attached a new one, if anyone is interested.
[Captivate Android Development] aleadam:
Did that finally work that for you? I see that you're using the 1.4.7 @ 1.45 finally. How did you get it to work?
[Captivate Android Development] shaolin95:
oops wrong signature...1.4.6 fixing now
[Captivate Android Development] joeshmoe08:
Guys what is diff between XT and normal and what is default voltage for 1.5.6.

Edit: NVM I found out myself
[Captivate Android Development] joeshmoe08:
DAMN I can do up to 1552 overclock but not 1600.... :(
[Captivate Android Development] shaolin95:
Is that Stability Test and NeoCore stable?
[Captivate Android Development] chisnz:
I'm currently running xcaliburinhand's I9000 reoriented v2.2.1 kernel on top of JL3 (and with Assonance 5.0).

Can I simply reflash SetiroN's kernel 1.4.7 or 1.5.6 straight through CWM or will I have to disable any lagfix? Any recommendations on which Setiron kernal's going to work reliably in this setup at the moment?
[Captivate Android Development] sjavvaji:
yea...i oc my pc...i understand how it works...i was getting now high uv's on cogkernel 4...like -150mV on everything except 1000mhz...no stability test/neocore issues...i was just surprised i could turn it all the way down on sentiron's...anyway i think it is working...1.4ghz and sipping battery like i have never seen before...i got the golden batch i guess
[Captivate Android Development] shaolin95:
Different kernels so I dont think you can compared how each voltage really works.

Congrats on the 1.4Ghz!
[Captivate Android Development] sjavvaji:
thanks...it never gave me a problem so i might try the 1400-1600 range during the holidays
[Captivate Android Development] sjavvaji:
so w/ this 1.4ghz, every voltage at -200mv stable...ive gotten 10.5 hours so far w/ 50% battery left (i did calibrate)...this included like 15 texts, music, 20 minutes of south park, 1.5 hour long fruit ninja tournament, 20 minutes of youtube, and facebook browsing...madd nice
[Captivate Android Development] shaolin95:
So you are running 1.4.7 @ 1400Mhz with all frequencies at -200 stable?
[Captivate Android Development] capita:
Stable at 1.4ghz on the 1.5.6 kernel. But no UV applied. Freeze at -75s across the board. Will attempt to UV bit by bit tonight when I have some time.

fwiw linpack at 19.5ish and quad in 1600s

running axura 2.5
[Captivate Android Development] sjavvaji:
yea...pretty much...that is why i wasn't sure if the settings actually applied. The battery life is so much better and they stick through boot so i think it is working...i tried the 1440 one...it booted but the gpu o/c made it very, very unstable...ill flash the 1600 one on friday when i finally have free time
[Captivate Android Development] shaolin95:
When you guys say stable are we talking about Stability Test 30-50 loops and NeoCore stable as well?
[Captivate Android Development] sjavvaji:
neocore is stable and so is stability test although i only had time to do like 20 loops before i had to go somewhere
[Captivate Android Development] sjavvaji:
can i still get into clockwork if i flash 1600mhz v1.4.6 and find phone is not stable enough to boot android?
[Captivate Android Development] capita:
Bah, as I read this, stability test just fc'd on me......on the 29th run. temp hit 42 degrees

neo was fine
[Captivate Android Development] aleadam:
Yes. Make sure you have another cwm flashable kernel on the sdcard to make your life easier. A similar kernel (e.g., another 1.4.6 or 1.4.7) with low o/c would be perfect to avoid problems with different lagfixes.

No, these are different lagfixes. Add a file or directory named disable-lagfix on your sdcard/Voodoo folder and reboot.
[Captivate Android Development] aleadam:
Oh well, I thought you may had resolved it. I still owe you that test.
[Captivate Android Development] sjavvaji:
ok...it won't be oc'ed in download mode so i can flash back if i have issues right?
[Captivate Android Development] mikewong27:
can someone upload 1.4.7 CWM zip file? Thanks

Mike
[Captivate Android Development] chisnz:
Thanks very much.

I'd like to try 1.4.7 but can't see a CWM version on page 1. Is there a 1.4.7 CWM version sitting around somewhere else, or is it simply just a matter of copying the zImage from a non-CWM into the kernel_update directory from any of the CWM versions?
[Captivate Android Development] aleadam:
Right. You can use cwm or download mode regardless of o/c in normal boot.
[Captivate Android Development] aleadam:
Which one?

That's right. You can make it that way.
[Captivate Android Development] arcardinal:
I have a feeling that xan's voltage app is not working for me. I am running setiron 1.4.7 oc at 1200 mhz. I have tried xan's v2.0rc5 as well as the 3.0a3 and have all values set to 200, overclocked at 1200 mhz, and noop. I have been running with this setup for about 6 hours today and no fc's or freezes at all. I have checked the uv table and it says all values are set at 200. Is there any other way to see if the uv is actually being applied?

I have to assume my uv is not actually being applied. Anytime I've tried uv at even 50 for 1200 mhz on all of setiron's other versions besides 1.4.7, I had an immediate system freeze upon applying in xan's app, and would have to do a restart. Or, maybe I just have a special phone? I just find it hard to believe that im able to set all uv values to 200 and still be stable, something doesnt seem right.

Anybody have any ideas?
[Captivate Android Development] sjavvaji:
dude...i have the same EXACT problem except im at 1.4ghz
[Captivate Android Development] arcardinal:
Im assuming your issues just started with setiron 1.4.7?
[Captivate Android Development] sjavvaji:
yup, exactly
[Captivate Android Development] joeshmoe08:
ya I did like 10 neocore tests and 40 stability loops before I got bored and stopped. Its completely stable at 1552.
[Captivate Android Development] DAGr8:
go in proper directory and check them files manually in /sys/devices/system/cpu/cpu0/cpufreq ... UV_MVtable states_enabledtable if they show your settings on reboot then your settings are being applied /.

if all them files there have proper value set then try editing
[Captivate Android Development] sjavvaji:
just flashed v1.5.6 and the voltage works fine...it appears to be because the voltage app isnt compatible w/ v1.4.7
[Captivate Android Development] aleadam:
what does /sys/devices/system/cpu/cpu0/cpufrew/UV_mV_table say? If that's a row of zeros then UV is not being applied on boot.

You can also try hitting apply for now in voltage control app. This will inject the settings directly into the cpu. See how stable is then, without rebooting.
[Captivate Android Development] aleadam:
I tested several iterations of 1.4.7 including the released one and voltages are applied. The app IS compatible.
[Captivate Android Development] arcardinal:
When I go into UV_mV_table it states all values are at 200, even on reboot. I have also edited them manually.
[Captivate Android Development] Doug8796:
shaolin95 what is your nenamark score now?
[Captivate Android Development] sjavvaji:
mine were like that too
[Captivate Android Development] Doug8796:
I tested 1440mhz on another build and i found it to be a great deal slower than 1400mhz. Could someone run nenamark on it and see if they get above 53.8?