yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Dani897:
ok so I set to 1.2 @ 1.25 volts last night. worked great!

so today I fiddled with it more and would you believe it as my volts went down my quadrant scores went up!. 2525 so far.

I'll warn that setting volts lower ran stable in quadrant and passed the stress test but the phone did freeze on shut down. I went back up but I'm not posting the number because I don't want to be blamed that there phone crashed. my shutdown animation is a little choppy. and I haven't run any games yet.

unhelpful, can this kernel be clocked higher than 1.2? I haven't been able to make a setting stick above 1.2 yet, but it runs at lower voltages, so I have a feeling it has more in it.

I'm afraid to go to 1.3 and I'm wondering if there is an increment that it needs to be like the gpu.
[Captivate Android Development] LinuxNewb:
So I don't want to read hundreds of posts but can someone pst am update of how they're doing on this
[Captivate Android Development] Unhelpful:
I've set higher clocks and I'm fairly sure they worked correctly, but none have been stable. CPU clocks are rounded down to the nearest 4MHz, or may be rounded up or down by up to 1% in order to reuse a PLL from a higher clock.
[Captivate Android Development] Dani897:
linuxnewb

if you mean how do you set the clocks then you need to copy the table file with all the clock settings to a folder. edit it with a text editor, then overwrite the original with the concatenate command. "cat"

the best way is to write the command as a script. I'm having trouble making the script executable to run at startup if someone can explain that to me I'd be grateful.

I can run it in sl4a with a home shortcut. which I prefer for testing right now.

the original file location is /sys/devices/system/cpu/cpu0/cpufreq/freq_volt_table

my file is /sdcard/sd/table

script looks like

#! system/bin/sh

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

I'm sure someone is gonna tell me a better way.
[Captivate Android Development] Unhelpful:
v1.4

You can now store your own freq_volt_table in /sdcard/sd/config, /sdcard/config, or /system/etc/config, and it will load on boot. Also all init scripts are interpreted by the system shell and do not need the executable permissions set.
[Captivate Android Development] :
@Unhelpful Cant we use the UV app from the i9000 OC/UV kernel thread? found here:

http://xdaforums.com/attachment.php?attachmentid=396456&d=1283819814
[Captivate Android Development] Unhelpful:
No, because it was designed for raspdeep's kernel that uses a different control file and a different format. But for v1.4 all you should need to do is copy the control file to a new folder named "config" on internal or external sd and edit it. External is safest for trying new settings since you can just pull the card and reboot to revert - otherwise you would need to reboot into recovery and use adb to remove the file.
[Captivate Android Development] :
Ic so can you contact the guy that made the apk, to try and make it compatible with your kernel??
[Captivate Android Development] Dani897:
For some reason I couldn't get it to stock on boot, who knows.

I'll stick with v 1.3 for a few day though.

I have gotten higher clocks to stick but its unstable, I'm guessing the lack of heat dissipation is the cause.

When I charge the battery I need the voltage a little higher for stability or it freezes on shut down. without the charger plugged in I can turn the volts down to 1150 without issues. with the charger 1200 is better but I still recommend 1250. but I think 1300 is too high for some phones.

I think we have reached a threshold at 1.2ghz. any further overclocking may need a modification to cool the cpu
[Captivate Android Development] darcjrt:
Media scannet is not running at startup and phone will not recognize internal and external sd cards
[Captivate Android Development] Unhelpful:
It won't load on boot? It works fine for me, where exactly are you storing your freq_volt_table? It looks for /sdcard/sd/config/freq_volt_table, /sdcard/config/freq_volt_table, and /system/etc/config/freq_volt_table. Also any method like an init.d script that worked with 1.3.1 should still work with 1.4.
[Captivate Android Development] theoddjosh:
Same thing is happening to me. I installed v1.4 over the last version and now my phone won't recognize ext or internal SD cards.

So i decided to reflash to stock JF6, then flashed JH7 again.

Once again installed SRE v1.3.1c and then installed unhelpful kernel v1.4.

Same issue again, phone won't recognize external or internal SD cards.
[Captivate Android Development] Dani897:
sorry, it wouldn't on boot with init.d on 1.3

I haven't flashed 1.4 yet. I'm still playing with settings. I thought it was because it wasn't executable but I may have made a simple mistake. thanks for the reply though.

I prefer it stock on boot right now so I don't need to pull the external sd card if I push it too far.

so far I've gotten it to 1236 mhz with the gpu at 206 mhz. and briefly at 1224 and 226 (not stable).

i don't think we are likely to find a stable setting that benchmarks better than your original setting. and I think I need more knowledge of the logic behind it to even try.

I think that phone with the 3000+ quadrant score had additional cooling and either had the gpu way overclocked or had some tricks going on with the file system beyond the lagfix.
[Captivate Android Development] thumper_1151:
Same issue SD card not recognized :(
[Captivate Android Development] designgears:
+1

cannot see internal sdcard
[Captivate Android Development] mostyle:
same here as well.. I inserted the kernel into the latest release of SRE making sure to delete the other 'unhelpful.kernel' and inserted this one into it.. thought I screwed something else up until I came here..
[Captivate Android Development] Unhelpful:
If somebody having this problem could boot the attached debug build and pull /system/user.log via adb while it's running, it would be a big help. I've rebooted several times and can't reproduce the problem. It needs to be booted normally, user init isn't run in recovery.
[Captivate Android Development] thumper_1151:
I can't Evan download the file on my phone it says no SD card installed. I can't do a clockwork or recovery mode install because it didn't evan recognize te SD card. If I insert it with adb can I run it from a system folder? I am sorry but I am still verry new to android, with very little Linux experience.
[Captivate Android Development] Unhelpful:
All you should need to do is flash the new kernel, boot, and use adb to pull the log. The log doesn't reside on SD, and adb doesn't need SD to work, either. Are you not able to use the keys to boot recovery to flash the new kernel? All of the changes are only in init.rc and shouldn't have any effect on recovery mode at all...
[Captivate Android Development] s3ct0r3:
Very weird.

I experienced the no SD card recognition too. I power cycled several times, ultimately getting the phone to recognise the cards (both int and ext).

I was getting nervous, because none of my computers can actually read the fs on my external SD card.

I do have a question: when I use ClockwordMod recovery to flash the kernel, the screen goes crazy and zooms in on the text at random. I'm actually not sure if the kernel is installed. Unhelpful, does your kernel have a specific name reflected in uname? SetCPU crashes when I attempt to alter the clocks ... sigh
[Captivate Android Development] designgears:
So just power cycling got the sdcards to work?
[Captivate Android Development] s3ct0r3:
So it would seem for me. I know get "Prepping mass storage ..." notifications when I boot.

I just power cycled several times, and now it works. I did, however, plug in the drive into a Windows 7 machine in an attempt to write the older kernel to it. (I run a Mac and my NTFS drivers were reporting that the drive was unreadable.)

Perhaps there's something in what I had done to remedy the situation. I no longer get unavailable errors.
[Captivate Android Development] Unhelpful:
Very strange... probably somehow has to do with mounting the sdcards to look for config files there, but they're all unmounted before other things are allowed to start. If I make a test build that doesn't use the sdcards, could somebody give it a try and see if the problem goes away?
[Captivate Android Development] Dani897:
I would test it, I haven't used adb and I'm not a programmer but I can sure tell you if it works.

I too upgraded to 1.4 and must remove the external card to mount it. I didn't make /config directory on the internal (thank god) and i can't seem to make a /system/ect/config directory. if you can explain that part to me.

edit: the card finally mounted on boot, but I didn't change anything. I can still test the modified kernel but I don't know if it will tell you much now.
[Captivate Android Development] mostyle:
I'll give it a try.
[Captivate Android Development] Unhelpful:
Nevermind, just flash 1.4.1, which should fix it. I wasn't able to reproduce this problem on stock, but flashing the latest SRE got it to "work". There was a bad interaction between SRE and the scripts updates in 1.4, I've worked around it so 1.4.1 should fix the trouble.
[Captivate Android Development] rsx19:
does that mean i can flash 1.4.1 right over 1.3, or do i need to re flash
[Captivate Android Development] thumper_1151:
Sorry if this is a dumb question but can I install just the bad script or can I install 1.4.1 through Odin? I can't install through recovery because I can't save to my SD. I tried rebooting multiple times but still no SD.
[Captivate Android Development] darcjrt:
Do i put a file named config in the root of.the external sd or.should i create a folder named config in the ext sd and put a file.named freq_blabla?
[Captivate Android Development] REAVER117:
Unhelpful, any chance you could work with neldar to implement the backlight notification system from the I9000 thread?

http://xdaforums.com/showthread.php?t=772672
[Captivate Android Development] warri:
I just started getting the blackscreen on reboot that DG was experiencing a couple days ago.

I tried to change the font and the phone just blackscreens, once i take out the battery, and boot again it works fine....

Also adb reboot does the same thing

adb reboot recovery works

adb reboot download works

It was happening while using SRE1.3.1b +JH7+ext4 lagfix (with Kernel 1.3.1)

i upgraded to 1.4.1 Kernel to see if maybe it was a 1.3 issue, and it is still happening.
[Captivate Android Development] s3ct0r3:
Unhelpful,

On the old kernel, I'm able to reproduce the issue only if I hot reboot the phone (rebooting at the shell or ./adb reboot).

Now, on the other hand, if I actually deactivate the device and boot cold, the SD cards mount without flaw.

I know that you implemented a work-around, but maybe this will help you pinpoint the problem (if the work-around doesn't already).
[Captivate Android Development] TMC_Sherpa:
There are differences between the NAGSM cypress-touchkey.c and the I9000 but it shouldn't be impossible. The tricksy bit is the Sep 6th code drop from Samsung changes the CONFIG to use the Melfas files on the Captivate instead.

Nothing I love more than a nine way diff party.... Ugh.

Sherpa
[Captivate Android Development] designgears:
that was because of some undervolting issues...
[Captivate Android Development] warri:
Interesting cause I'm running at 1.3V and lowest at 700..maybe my steps are too big?
[Captivate Android Development] Dani897:
^ too low on the low end. and you may be able to come down on the high end 25-75 milivolts. below that may cause random restarts when charging or the phone to freeze on shut down any time the phone is hot but otherwise run stable.

after crashing the phone several times (ext2 lagfix) experimenting, something on my phone got corrupt so I can't speak for a good low voltage yet. flashing to stock fixed it. so I can try again but I doubt anything under 850 will be stable.
[Captivate Android Development] warri:
Thanks that fixed it for sure..850 is the lowest you can go I guess
[Captivate Android Development] Unhelpful:
A folder named "config" on either internal or external SD, with your freq_volt_table file in it. It will look on the external card first, then the internal.
[Captivate Android Development] darcjrt:
Thanks a lot!!. Now which is the best way to know if the file is in the correct format, or if it worked?

Thanks and next pay check I will def donate!!! Great job!!!!
[Captivate Android Development] Unhelpful:
The easiest thing to do is probably to open the control file /sys/devices/system/cpu/cpu0/cpufreq/freq_volt_table as a text file - I can use the editors in both EStrong and Astro explorers to do this, and Root Explorer should work as well for those who use it. The contents of this file are generated when it is read from the actual CPU and GPU clocks as they were applied. Most editors will probably not be able to save properly to this file, although you can try to if you want to apply clocks without saving them to apply on boot.

If your editor won't work properly saving to the control file, you can save your modified file somewhere else and use cat in terminal emulator or adb shell to apply the new file. This is probably a good idea if you aren't storing your on-boot frequencies on external SD, because otherwise you will need to know how to get in via adb in recovery to delete them if they cause your device to fail boot. If you put them on external SD, you can just pull the card to disable them.
[Captivate Android Development] Unhelpful:
I'm trying to upload a tarfile for Odin. Mediafire and Github both time out every time I try to upload a kernel package on my wireless, and I won't have much time at home until the weekend. If you already have clockworkmod recovery, you should be able to boot that and then use adb push to send the new zipfile to the SD card. I'll keep looking for a way to upload an Odin file, since that will probably be easiest for Windows users who hit this bug.

If you have a pre-1.4 version, flashing straight to 1.4.1 should be safe - it simply corrects the problem that occurs using 1.4 with the disable media scanner feature in SRE, and other than that functions just like 1.4.
[Captivate Android Development] Reefermattness:
Works great man, fixed the media issue for me. Didn't even need to reboot after flashing SRE, just made sure to flash 1.4.1 second in clockwork recovery. Its up and running!
[Captivate Android Development] commander2k:
Sorry if this has been addressed already, but I edited the file with root explorer to OC to 1.2 ghz, but everytime my phone restarts it sets back to 1 ghz. Can I fix this?
[Captivate Android Development] Unhelpful:
Yes, make a directory named "config" in either internal or external SD, and save your modified freq_volt_table there to have it loaded on boot.
[Captivate Android Development] commander2k:
Done and done. Thank you very much, awesome work! Thanks for the fast response too
[Captivate Android Development] LGSilva:
If I use the freq_volt_table below my phone freezes after 1 minute or so:

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

but if I remove the first line it's all good. I'm using JH7 and your latest kernel. I was able to run at 1.2 before... any ideas?
[Captivate Android Development] Dani897:
^volts too low! especially the 1200 and the sleep modes. below 850 it may seem fine but i encountered sleep death at random. I feel 900 is the ideal setting. I mean do you realize that you're peak setting is 75% greater than your lowest setting and even that is too low. the span should not be that large.

my phone freezes on shutdown below 1125 on the overclock setting. but otherwise seems fine and passes the stress tests. I recommend no less than 1175 for the overclock based on my phone. but it varies from phone to phone.
[Captivate Android Development] Landulf:
After getting stability without 1.2 oc in version 1.4.1 I tried to add the overclock step and am unable to get it stable even stepping up 5mv at a time starting at 1050. So Back to version 1.2 I went and all is happy. My question is, is version 1.2 compatible with (or will it be) the voodoo fix that is soon to come out. The reason I ask is I love your version 1.2 as it runs rock solid and linpak scores are wonderful with it. but I would also like to run voodoo. Seems there is much talk about adding it with 1.4.1 but as I said I cannot get it to run on my phone in an overclocked fashion and linpak suffers without it oc'd. Thank for the hard work Unhelpful.
[Captivate Android Development] Unhelpful:
Older versions would have used 1.275V at 1.2GHz, have you tried starting with that and working down? You may also want to try increments of .25V, I believe some of raspdeep's users had stability issues if they used smaller steps.
[Captivate Android Development] shaolin95:
I am sure I am missing something but I installed this using the SRE 1.3.1 update.zip and I just copied the freq table the way it was from the sys location to the sd and created a config folder for it.

I rebooted but it still only gives me 1.0ghz as the max.

I am missing something? The first time I installed this kernel (first version) it was overclocking automatically and my phone was perfectly stable so this version has me confused...sorry.
[Captivate Android Development] Landulf:
Yes, I have tried that at 1275mv at 1.2ghz. I started at 1050(very low I know) and stepped up at 5mv increments all the way to 1300mv never had stability. Thought I was there a few times till running setcpu stress and then insta-lockup. I will through it back in and try that a second time for the sake of it. Just a side note at 1.1ghz I can run fine but it drops my linpac scores compared to version 1.2 oc at 1.2ghz. (Not that I should complain it's till better than stock LOL)
[Captivate Android Development] thumper_1151:
I found a quick way around the problem with no need for you to upload a tar file for odin. for the newb like me if you had this problem simply use odin and flash the stock kernal and pit file from the i9000 thread and that will fix the sd issue without erasing any apps or personal data then you can install 1.4.1 through recovery. I don't know why i didn't try this sooner, but I am still very new to android!!
[Captivate Android Development] warri:
you can just flash the 1.4.1 through recovery over 1.4 with out going through odin. It wont touch any of your data or apps, since you are just flashing your kernel
[Captivate Android Development] Unhelpful:
I believe SRE 1.3.1 is still using my 1.3.1 kernel. You will need to upgrade to my 1.4.1 kernel to use the auto-loading feature, and you may also need to remove SRE's OC script from /etc/init.d, as this would run after the auto-lead and could replace the auto-loaded table.
[Captivate Android Development] Unhelpful:
Sadly this seems to have happened to some people. It may be that the top voltage used by stock kernels isn't actually 1.275 - that value appeared in a table but the voltages in that table are never actually read, a different voltage-setting function is used which requests one of 4 pre-defined levels. You might need to try up to 1.3V to see if that makes it work for you. I've run up to 1.325V without problems, but some start to see instability at the voltage regardless of clock.
[Captivate Android Development] Landulf:
I'll try a bit above 1300mv(near that 1325mv). Been playing with the tables to see how low I can go with 1.1ghz. I assume sleep death is due to too low at the lower frequencies? Anyways still playing. Just loved the stock voltage with OC of version 1.2 due to stability.

Thanks again for your work.
[Captivate Android Development] thumper_1151:
I couldn't flash through recovery, my SD wouldn't show up.
[Captivate Android Development] warri:
Yea this is correct that happened to me..and I scratched my head for about 5 min then I figured it out
[Captivate Android Development] Unhelpful:
You should be able to send the file to your phone with ClockworkMod Recovery using adb, with the command "adb push	/sdcard". Without ClockworkMod you would need to connect using adb shell first and mount the card with "mount /dev/block/mmcblk0p1 /sdcard". You could also flash an older kernel using Odin, then use that to copy 1.4.1 to the phone.
[Captivate Android Development] shaolin95:
Ok guys so I copied the file to the config folder and I can see it running at 1.2Ghz when I boot up with the CPU TEMP widget but the problem is 1.2 does not seem to kick in all the time and after a while it seems to not go over 1.0 unless I restart. With the previous version of the kernel 1.2 was always perfectly stable to I did not modified anything just copied the freq table from sys to the config folder.

Help Please.

Thanks
[Captivate Android Development] networkdood:
'If you want to build yourself, see the toolchains thread for known-working tools. Run

Code:

make ARCH=arm i897_defconfig

make ARCH=arm menuconfig optional

make CROSS_COMPILE=/path/to/toolchain/arm-none-eabi- zImage change if using a different toolchain

tar c -C arch/arm/boot/zImage >captivate_zimage.tar

Flash captivate_zimage.tar as PDA in Odin - see other threads for how to use Odin and where to get it. Use menuconfig to select a different initramfs source if you wish, by default an included one at usr/initrd_files will be used.

Starting with v1.4, create a .build_config file to change any variables and run build_kernel.sh to build tar flashable with Odin or update.zip.'

ok, these commands do not work for me and neither does 'tar' to compile a .tar file for flashing...anyway you could post a tar file for flashing....thanks!!
[Captivate Android Development] Unhelpful:
If you look on "the" info tab in SetCPU, you'll find a "time in state" table that details the time spent at each speed. The CPU changes speeds much more frequently than the display in SetCPU updates, but that table will always show the time spent at each speed, in hundredths of a second. I can see the time for 1.2GHz increase steadily on my phone even when I can't catch it at that speed in the main tab.
[Captivate Android Development] Unhelpful:
Updated, I've attached a tarfile for Odin for 1.4.1 to help people stuck with the 1.4+SRE bug. Sorry this took so long, I haven't had enough time at home to update. Also removed 1.4 downloads, as it's just 1.4.1 + bugs. ;)
[Captivate Android Development] shaolin95:
I dont have SetCPU but I noticed by running the Linpack test which should be in the 9s when Oced to 1.2 and not in the 8s. And I do get 9s for a while but at some point it just stops kicking in.

I can see the phone on 1.2Ghz right after I boot but it just stops kicking in later on, a bit strange. Do you suggest I keep SetCPU then?
[Captivate Android Development] Unhelpful:
Wait, which version are you using? I fixed a bug in 1.4 that was causing the cpufreq policy, which determines the maximum and minimum speeds, to reset after a while. If you're using 1.3 you need to upgrade to 1.4.1.
[Captivate Android Development] nickbarbs:
Funny enough i'm digging this bug because I was tired of the unstable situation my phone was in before. This way I have SRE + no OC which is no longer available. Noticed the bug a day ago but i've done a nandroid because my phone is working PERFECTLY now.
[Captivate Android Development] nickbarbs:
can anyone clarify for me, is the third column sleep voltage, and the fourth column load voltage?
[Captivate Android Development] Unhelpful:
Actually, you can just delete the script that enables OC/UV from /system/etc/init.d, I believe it's named E_overclock. That should give you stock clicks and voltages without needing to rely on a bug, and will also remove the reduced voltages that the script installs.