yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] nickbarbs:
Thanks for the tip! Thats great! Somehow in my poking around and restoring nandroids + overwriting SRE 1.3.1c with your 1.4.1 kernel, i've managed to get my 1.2ghz oc back and running (???) so far stable. i'm still trying to understand what each column does in the freq_table.

1200000 200000 1050 1100

1000000 200000 1050 1100

800000 200000 1050 1100

600000 200000 950 1100

400000 200000 950 1100

200000 200000 600 1100

100000 100000 600 1000

This is the table I see posted above and since voltages are lower in the 3rd column than the fourth it leads me to believe that the 3rd is sleep and 4th column is load. However, if I increase the 4th column to 1300 for 12000000 i get a freeze on boot up.

This table however has allowed me to pass boot up and so far stay at 1.2ghz stable.

1200000 200000 1300 1100

1000000 200000 1300 1100

800000 200000 1300 1100

600000 200000 950 1100

400000 200000 950 1100

200000 200000 850 1100

100000 100000 850 1000

Color me confused!
[Captivate Android Development] Unhelpful:
The third column is CPU voltage, the fourth is "internal" and used by some peripherals. It should not really be changed as the clocks for these components do not change.
[Captivate Android Development] shaolin95:
You got it, I was running 1.3...so I can just use Odin, load this as PDA to flash?

PS Just did the upgrade and seems to be working....thanks a lot!
[Captivate Android Development] Dani897:
you can reduce the 3rd column volts in the upper freqs a bit. 1200 @ 1.2 ghz is working for me. 1300 may create too much heat on some phones and < 1200 may have freezing problems.
[Captivate Android Development] Landulf:
Unhelpful,

I understand your working on a voodoo implementation of your oc kernel. I was wondering if this will be stock voltage version(version 1.2) or oc/uv version(version 1.4.1). The reason I ask if that I know some people, me being one, have stability issues when UV comes into play.
[Captivate Android Development] Unhelpful:
Future work is likely to be based on the dynamic frequency/voltage system from 1.3. It's more flexible, as it can boot without even 600MHz added to the stock frequencies, and allows fine-tuning of OC settings for devices which may not be stable at 1.2GHz.

I'm not sure what has created the impression that OC or UV cannot be turned off since 1.3, but in fact neither is used until activated by writing to the control file.
[Captivate Android Development] Landulf:
I have no problem with that version save the fact I cannot get a stable OC/UV table created. When using kernel version 1.2(stock voltage I believe) It is rock solid. Is there a way with version 1.4.1 to ONLY OC to 1.2 without the Undervoltage option?

I have taken the table created during a boot without table and tried to add 600/1200 frequency(As without the custom table 1.4.1 seems stable also). Any advise would be much appreciated.
[Captivate Android Development] Unhelpful:
The big problem in this transition seems to be that we can only guess at the voltages used by stock kernels, which use a different, and very inflexible, method to set voltages. Stock kernels use two GPIO lines to select one of four preset voltages, and the PMIC does not appear to report voltages used at all in this mode - it's visible in sysfs as well but always reports 1.275V. You should be able to try voltages as high as 1.31V and it might be that you simply need a higher voltage for your phone to be stable at this speed.

The hummingbird is also supposed to have hardware for assessing the stability of the CPU at the current frequency, voltage, and temperature. If we can figure out how to read this information we should be able to tune voltages for optimal savings and stability regardless of what the numbers we send to the PMIC actually mean, so long as we know that higher numbers mean higher voltages.
[Captivate Android Development] madman808:
Can Should I use any old text editor?
[Captivate Android Development] raspdeep:
please note the editor you use to add / edit the file needs to be compliant to *nix format. Windows editors tend to add CR/LF which can cause problems unless Unhelpful's code already account for such differences. Maybe Unhelpful can answer this.

you can double check this by transfering the file into your phone and use "less filename" and see if every line feed has a funny character. If it has most likely that is the problem. On windows you can try notepad++ which I believe can handle *nix

Also, I'm not sure which delimiter Unhelpful use to check table tokens, that unhelpful can also reply.
[Captivate Android Development] Landulf:
I will take a look and let you know if that does indeed correct my issues. I am aware that it must be something I am doing incorrectly as with version 1.2 it is stable and also without a custom table version 1.4.1 is stable. I just for the life of me cannot figure out what it is. Will try and let you know.

*update*

Yes, there where cr/lf after each line. I removed them and replaced the file. Same results. It seems ok during boot which is where I would think if would have problems then when doing fast scrolling in app list bam it freezes. Or just after a random length of time bam it freezes. Back to version 1.2 I go and perfect stability. If I was unable to run at 1.2ghz(which I could understand some not able to) I would think it would not be able to run it no matter what.
[Captivate Android Development] Unhelpful:
All it reads is numbers separated by runs of whitespace, but I'm not sure whether the kernel's sscanf implementation treats both CR and LF as whitespace. Technically the values needn't be on separate lines, that's just done to make the table easier to read.
[Captivate Android Development] madman808:
I'm doing something wrong. I've flashed the kernel using Rom Manager. I've changed the freq_volt_table and added the user init script to enable 1.2 at startup. I still don't see 1200 in SetCPU. Is there another step I'm missing? How can I verify that the kernel is indeed updated?
[Captivate Android Development] Unhelpful:
Where did you save the edited file? By the way, you don't need a script for overclocking with 1.4.1, just save a freq_volt_table file in /sdcard/config, and it should load on boot.
[Captivate Android Development] madman808:
Thanks. I realized that I wasn't really updating the freq_volt_table in the /sys/... folder and ended up just copying it to /sdcard/config/ like you said in the op. Works like a charm.
[Captivate Android Development] raspdeep:
if it hangs randomly after booting, then the problem is not parsing of the file into respective variables but either your voltage setting is too low for the frequency or your chip just cannot handle that high frequency. what is Vddarm you set at 1.2ghz? are you sure the hang / freeze is at 1.2ghz and not lower frequencies?

if possible, attach your table.
[Captivate Android Development] Landulf:
I've tried 1310mv,1300mv,1275mv,1250,1225mv at 1.2ghz. And tell me this, why can my chip handle 1.2ghz when running kernel version 1.2(stock voltage I believe). I would understand if that also cause me problems. But it runs rock solid all day and night.

The latest table I tried is as follows.

1200000 200000 1310 1100

1000000 200000 1200 1100

800000 200000 1200 1100

600000 200000 1200 1100

400000 200000 1050 1100

200000 200000 950 1100

100000 100000 950 1000

Table created if freq_volt_table is not present for reference

1000000 200000 1200 1100

800000 200000 1200 1100

400000 200000 1050 1100

200000 200000 950 1100

100000 100000 950 1000
[Captivate Android Development] raspdeep:
try this:

1200000 200000 1300 1100

1000000 200000 1275 1100

sometimes it is not the highest frequencies that cause the instability, but the other frequencies. Stock 1ghz @ 1.275mA so 1.2mA maybe a little low.
[Captivate Android Development] raspdeep:
as far as i know CR is not whitespace in sscanf but i've not touched c for a decade until recently coming back to look at kernel codes :)
[Captivate Android Development] xan:
I would love to see such powerlvl defining mechanics in i9000 international kernel too.

Will make me work on .apk to create/edit appropriate file :)
[Captivate Android Development] _MuLder_:
So what isthe issue if my phone does not boot?

It's chilling at the Galaxy S screen and then shuts off....:(
[Captivate Android Development] :
Can you explain a bit further? like the steps you took etc etc.
[Captivate Android Development] Alexstarfire:
Well, it seems that I got everything working right, but my battery seems to be dying faster. Lowered the voltages as well. Been up 2 hours and it's down 15% already. It's been idling the whole time. Set CPU confirms that the phone has spent most of the time at 100Mhz, over 60%.

As such I'm wondering if there is a way to know if it's actually running at the lower volts.
[Captivate Android Development] Alexstarfire:
Is it possible to go over 1.2Ghz using this kernel?

Also, how do you set the CPU voltage? It certainly isn't the file.... unless the CPU can run at 95 mV.... at 1.2 Ghz.
[Captivate Android Development] SetiroN:
It certainly IS in the file.

Third column.

Besides, where's 1.5.1?

I really couldn't care less for Cognition, but I'd like to use Unhelpful's new kernel revision.

Also, would it be possible to have an alternative kernel with journaling disabled or eventually mounted with noatime/relatime? I know a lot of people would appreciate the option. :)
[Captivate Android Development] Alexstarfire:
Well, I must have the best phone in the world then cause it's been running at 1.2Ghz for hours with me having set it to 100mV in the file. Ran Quadrant just fine too.
[Captivate Android Development] Unhelpful:
The question is whether the numbers mean what we think they mean. The max8998 chip is visible over i2c (look in /sys/bus/i2c), and provides a standard set of properties used for power regulators... but is it just reporting the values sent to it, or actually setting them? Also I doubt the chip can go as low a 95mV, but I lack any real documentation for it beyond the Samsung sources. ;)
[Captivate Android Development] Devin5277:
need some help

I installed this kernel over a stock rom, and the flash went fine, I didnt over clock it or anything, just wanted the kernel and the lag fix. day one went fine, now my phone wont boot past the galaxy s logo, is there anyway I can odin to stock, is there a 2.2 rom I can odin to then stock, I have no way to repartition the sd card in this state.

Please forgive my ignorance, I have a vibrant, and I am trying to make my friends captivate faster.

Thanks in advance
[Captivate Android Development] Unhelpful:
1.5.1 had a bug in the included update-binary and was not flashing the kernel properly. I've prepared a bugfix release that I hope to upload this afternoon.
[Captivate Android Development] Landulf:
Could/Would this account for the larger battery drain many are reporting?
[Captivate Android Development] Unhelpful:
No, it accounts for the failure to boot, even in recovery, after flashing the zip I had uploaded here. I'm looking into the power drain, but it takes a not of time to be sure whether a change has helped or not. It also takes about 20-30 minutes at my computer to put up a new update here, with all of the mirrors and notes, and I'm trying to find time today, but I haven't so far.
[Captivate Android Development] avgjoegeek:
Good luck hunting down the power drain! My phone is eating the battery faster than a fat dood at an all you can eat buffet!

Once an update is posted - can I re-flash the kernal over the top of what I have going on (Cognition take n' bake 2.2) or do I have to start from scratch?
[Captivate Android Development] Alexstarfire:
Well, that's rather my point. There is no way it should have even booted. I was purposefully trying to make the phone unbootable cause then I'd know it was messing with the voltage. Without a way to physically measure the voltage it can be difficult to know what these modifications are actually doing. I wish I had another phone so I could leave it sitting around to test battery life. Hard to tell if battery life is improved, or declined, if you're using the phone.
[Captivate Android Development] Unhelpful:
No, I mean I'm not certain the PMIC is capable of producing such a low voltage, that's probably well below its minimum. Did you look at what it claimed the voltage was set to via i2c after trying to set such a voltage?
[Captivate Android Development] Alexstarfire:
Ohhh, well I look a bit stupid there. :P I haven't looked. I didn't realize that there was only a certain range it could be set at. I'll have to go mess around with it in a bit and find out some info. I have since changed the file back.
[Captivate Android Development] Mattwp103:
Does this update fix the battery drain people were having?
[Captivate Android Development] Unhelpful:
No, because I am still seeking the cause of the apparent drain.
[Captivate Android Development] Mattwp103:
Ah ok, thanks for the quick reply.
[Captivate Android Development] roadrash7:
Im running cog 2.1.4 and want undervolting capibilities back so can i just clockwork flash version 1.4.1 and be all good
[Captivate Android Development] Alexstarfire:
Ok, I'm not sure if I checked the right file, but I think I did since it had the right value for the microvolts at the time. The file I checked was /sys/bus/i2c/drivers/max8998/6-0066/regulator/regulator.0/microvolts. I also check the max and min microvolt files that are in the same folder. The name file suggests this goes to the processor since it says ARM.

I set the freq_volt_table file to this:

1200000 200000 120 1100
1000000 200000 110 1100
800000 200000 105 1100
600000 200000 100 1100
400000 200000 90 1100
200000 200000 80 1100
100000 200000 75 1100

Upon checking the above files at 1.2Ghz it was 950000microvolts, 950mV. The minimum voltage was 750000microvolts, 750mV. Interestingly though, the max voltage has always been 1500000microvolts, 1500mV. It shouldn't be able to run at 950mV.

If that's the wrong file to check then point me to the right one.
[Captivate Android Development] thumper_1151:
ever since I installed 1.5.2 with cognition 2.1.3 my phone automatically turns on when I plug it in to charge? Anyone else havve this issue?
[Captivate Android Development] Unhelpful:
Interesting findings. All of the values in your table are less than the stated minimum of .75V. I worry that perhaps nothing is happening when voltage "changes".
[Captivate Android Development] naxir:
I tried flashing 1.5.2 over cognition 2.1.1's antim 1.9 kernel using CWMod. when the phone rebooted it still had antim's kernel. It's CWMod version 2.5.0.4. Does anyone know why that is?

edit: ok, I figured out my problem - the file: /sys/devices/system/cpu/cpu0/cpufreq/freq_volt_table only shows 1GHz as the highest available. is there a good, reliable freq_volt_table circulating? I added 1.2GHz at 1.3V, but are there any other optimizations available?
[Captivate Android Development] Alexstarfire:
Something changes, I don't know what it is though. Messing around with the "voltage" has led me to find values that are unstable, around the supposed minimum of 750mV actually. None of the values I've tried have made the phone unbootable though.

BTW, is it possible to go over 1.2Ghz using the table? I've tried putting in 1.3Ghz before but then the phone doesn't even boot.
[Captivate Android Development] DOAlaboratories:
I'm fairly sure the votage was changing. Even though i couldn't gt the OC stable on my phone, the different voltages i set it at definitely changed the stability. The lower i dropped it, the quicker my phone would freeze, black out, or reboot.
[Captivate Android Development] Alexstarfire:
I can only get my phone to freeze when the screen turns off. Not sure why that happens, but it's only when I'm messing with the volts. I'm 100% positive it's not directly changing the voltage. It's doing something though.
[Captivate Android Development] Unhelpful:
The logic that controls the table will account for higher frequencies, but none have been stable for more than a few seconds on my phone. The only things it should change with regard to CPU clocks are rounding values down to a multiple of 4MHz, and rounding then up or down by up to 1% to make them divide evenly into a higher clock.
[Captivate Android Development] Dani897:
I played with clocks for an entire day and the best I could get was 1236000 with the gpu turned down to 171753,

Best quadrant score was 2575 (ext2 lag fix) with the clocks at 1224000 and 226781. But I needed to cool the phone in the fridge to do that. You can get away with 1212000, 224557. Or 1224000, 204000. But that's a blistering 1 or 2% speed increase. Not really worth it.
[Captivate Android Development] ronpinoy253:
My freq_volt_table setup using Cognition 2.1.5 and unhelpfuls 1.5.3 kernel:

1100000 200000 1050 1100

1000000 200000 1050 1100

800000 200000 1050 1100

400000 200000 1050 1100

200000 200000 850 1100

100000 100000 850 1000

Phone boots up fine and is very stable, but no matter what I do to add the 1.2ghz row to this working table my phone will freeze or crash at the boot startup screen. No luck playing with the voltages I have tried 1.3, 1.275, 1.25, 1.2, and 1.05. Other than this I notice when I boot with this table my freq_volt_table in the \sys\devices\system\cpu\cpu0\cpufreq\ folder shows the first row with a downclocked gpu of 183333 or something roughly close to that number. Anyone know why the gpu is getting downclocked? Or why the 1.2 ghz row wont work? 1.2ghz worked for me when using the old SRE 1.2.3 with the unhelpful kernal that didnt include a modification to freq_volt_table and only changed the phones cpu max frequency to 1.2 ghz. Thanks.
[Captivate Android Development] tytdfn:
You found the bug without a adb or a logcat? You're THE unsung hero of the captivate

Using the power of the force close ;)
[Captivate Android Development] roadrash7:
Can someone explain to me how to get the freq table settings to stick in a total noob way. Some of the directions on the first page are a bit overwhelming and i cant seem to figure some of it out. Also do i flash with odin or rom manager
[Captivate Android Development] Smallsmx3:
Does 1.5. 3 work with the latest cognition rom and voodoo? Doing need to disable or just flash over
[Captivate Android Development] Unhelpful:
I use 1.5.3 with Cognition 2.1.4, I haven't tested with later versions but if designgears is using atinm kernels, then you should be able to install mine without difficulty. You don't need to disable Voodoo before changing kernels, just any other lagfix.
[Captivate Android Development] Alexstarfire:
Loving the new kernel. Battery life much improved.
[Captivate Android Development] Dani897:
The best way us if you have an external sd card. So if you have an unstable setting you can remove the card. Put a folder named config on the root of the external sd (seen as/sdcard/sd/config from the phone). From the phone the external card is mounted to /sdcard/sd, if the phone its mounted to the pc the external card is seen separate from the on board storage.

Put a copy of freq_volt_table (original is found in/sys/devices/system/cpu/cpu0/cpufreq) in the new config folder. Edit it with a text editor and the changes apply on boot. The kernel scans for this folder and file on boot.

To test if it worked read the copy of freq_volt_table in /sys/devices/system/cpu/cpu0/cpufreq/

this is the actual applied frequencies

To apply without reboot copy the content of your modified freq_volt_table file to the one in sys/devices/system/cpu/cpu0/cpufreq With this command line

cat /sdcard/sd/config/freq_volt_table > sys/devices/system/cpu/cpu0/cpufreq/freq_volt_table

It can be saved as a script in sl4a or scripter or similar app so you don't need to type that every time.
[Captivate Android Development] roadrash7:
Thanks so much man i'll try that later and let ya know how it went
[Captivate Android Development] charmartist:
Sorry but I'm a bit confused on the lag fix issue. First off, I'm assuming that I'm going to use ROM Manager to flash this and NOT Odin3, also, when he says "remove all non-Voodoo lagfixes", does this include the OneClickLagFix V2.1+ as well? Meaning, I'll have to revert back to the original filesystem and not EXT2
[Captivate Android Development] Alexstarfire:
Yes, Rom Manager to install and undo the OneClickLagFix that you have installed. Though, you might just be able to disable the Voodoo LagFix that the kernel uses. I'm not to sure on that since I haven't done it myself.
[Captivate Android Development] pillz424:
It works great with the latest cognition rom. Disable voodoo first. I use clockword mod recovery to flash zip from sd, that works better than ROM manager for me. Then enable voodoo.
[Captivate Android Development] Unhelpful:
You should not need to disable Voodoo, this kernel use the same partition layout as other Voodoo kernels and should detect your existing ext4 partition if you are already using Voodoo.
[Captivate Android Development] kennethpenn:
I went straight from Cog 2.1.5 w/Voodoo and Rom Manager installed 1.5.3.

My phone won't stay on. Keeps restarting and freezing.

Any clue?

Edit: Well I'm just reflashing to stock. Ever since v1.2, no go on the Unhelpful kernels on my Captivate. My phone is one of the ones that can't handle any of these overclocks with undervolts, etc.

Edit #2: Tried 1.5.3 from stock JH7. Still freezes after like 10 seconds once I unlock the device on first boot.

Edit #3: Got it to work from stock JH7 with this table on my external SD:

1000000 200000 1050 1100

800000 200000 1050 1100

600000 200000 950 1100

400000 200000 950 1100

200000 200000 600 1100

100000 100000 600 1000

Edit #4: Stable with this:

1100000 200000 1050 1100

1000000 200000 1050 1100

800000 200000 1050 1100

400000 200000 1050 1100

200000 200000 850 1100

100000 100000 850 1000
[Captivate Android Development] charmartist:
How do I install this kernel with Rom Manager? I installed Cognition 2.1.5 over the stock ROM after updating to JH7 using Mini Keis. In Rom Manager, do I just install it using the "Install rom from SD" option?
[Captivate Android Development] kennethpenn:
Correct! Then choose zip from SD and choose Unhelpful's .zip!
[Captivate Android Development] tytdfn:
So far so good with this table. Great find, great kernel

Yay no more fc
[Captivate Android Development] Smallsmx3:
No 600 step? Why not?
[Captivate Android Development] kennethpenn:
No particular reason. I copied from another member a couple of pages ago. You can always add a 600 step if you want!
[Captivate Android Development] charmartist:
I applied Cognition's HSUPA fix, if I use this kernel will I lose the HSUPA fix and be capped at 384kbps Upload again?
[Captivate Android Development] Unhelpful:
Yes, this kernel will not support the HSUPA modem.bin, you'll need to install a Captivate modem.bin with it, or voice calls will not work properly.
[Captivate Android Development] Demented71:
how do I enable the OC? I just updated to Cog 2.1.6 with your kernel, and it won't go higher than 1ghz?

EDIT: I think I have it now. I read back just one page. I didn't want to read all 37 pages on how to do it...but just saw how, so gonna try now.
[Captivate Android Development] Smallsmx3:
I had over then I have been trying to change the voltage and the 1200000 step on the table disapeared. I dont have an external sd card and i cant get any of the settings to stay. When i try to copy and paste it tells me there's not enough disk space
[Captivate Android Development] roadrash7:
I was having this problem too. Instead of coping, zip the files then go extract them and move em to sd/config and edit. I got that far but i still cant get the editted settings to stick after reboot. Anyone care to help????
[Captivate Android Development] Smallsmx3:
And i dont have an external sd card
[Captivate Android Development] roadrash7:
You can put the config folder in your internal sd,but even after u do that edit the settings and reboot i still cant get em to stick. I must be missing something
[Captivate Android Development] roadrash7:
Were do i find user inits to put in init.d
[Captivate Android Development] dirtblade:
It is working good so far. Thanks!