yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shaolin95:
I am beginning to lose my mind here!

I cannot get the settings in the states_enabled_table to stick.

I have tried everything and it shows after I save and I open it back and the changes are there but then after I reboot I notice that the file shows modified again and back to the original settings.

Could it be my ROM?

I even tried removing the WRITE option from the Permissions but not even that.

Any ideas please?

I only got it to work once the first time I tried this at 1460Mhz but that froze so I had to reflash and I always do Odin one click back to stock to make sure all is gone.
[Captivate Android Development] bryman27:
No just flash both of them after the rom

so either rom, kernel, modem

or

rom, modem, kernel
[Captivate Android Development] boomerod:
Honest opinion

This is the best, fastest kernel I've tried so far - and I've tried most of them, including CogKernel2.
[Captivate Android Development] MikeyMike01:
2.0 rc worked fine on 1.4.3, but doesn't work on 1.5.

:confused:
[Captivate Android Development] existz:
Try navigating to /sys/devices/system/CPU/cpu0/cpufreq in root explorer ..then long press states_enabled_table then choose open in text editor and change it manually... reboot and it should stick...I had to do this with UV_mV_table to get my UV settings to stick with 1.4.x
[Captivate Android Development] shaolin95:
That is what I have been doing. Is there then any other way to do so? I am going to try with a different ROM just in case.
[Captivate Android Development] MikeyMike01:
Turns out I needed 2.0 rc2.

Whoops. :)
[Captivate Android Development] lpsi2000:
How did you stabilize 1.5 and at what speed?
[Captivate Android Development] SetiroN:
To who's having reboots/instability:

did you remove boot UV settings before upgrading?

I'm sorry what are you talking about? I didn't remove any features whatsoever. :confused:

I'll add 1.28 soon enough.

Yeah varying the GPU clock (both up or down) can cause instability and some phones are more sensitive than others and of course higher frequencies exacerbate the issue. Unfortunately there's no way to lock the GPU freq, I wouldn't be playing with it otherwise; AFAIK, stock clock is only achievable every 200MHz step, 1280 underclocks it slightly aswell.

I forgot to mention it earlier, I'm quite certain changing the filename is pointless, you just have to add the .sh extension on certain ROMs.

That is a ramdisk file, there's no way to make it stick. You need to edit your init.d script to include frequency adjustments or create a specific new one.

To automatically enable additional frequencies on boot, after updating Xan's app to v2.0 recreate the boot script and add the following bold text at the bottom or, eventually, create a new script starting with #!/system/bin/sh (named S_whatever.sh) and put it in there so that frequencies don't get overwritten when changing UV settings:

#!/system/bin/sh

#set UV

echo "50 50 75 100 150 150 150 175 150 150 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo 1460000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

#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 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

#!/system/bin/sh
#set OC
echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

Or have you? :)
[Captivate Android Development] shaolin95:
NO I am officially confused. :-)

I was just following what you wrote before

Did I misunderstood that then?

I guess what you are saying is that they are currently being changed by the UV settings applying at bios right? That would make sense as the only time I got it to work I have not done any changes to the Voltages .
[Captivate Android Development] lpsi2000:
I am talking about the new features you introduce in version 1.5 (everything except for new OC). Like ext2, ext4 no journal, etc...

updated CWM to include Hardcore's latest additions

slight menus reorganization

updated optimization scripts (now including battery optimizations and CIFS support)

built-in support for ext2, ext3 and ext4 no-journaling (you will see a "configuration changed" screen if you manually disabled journaling - select "No, enter recovery mode" and switch ext4 to ext4nj)

built-in support for ext4 mount optimizations (writeback mode)
[Captivate Android Development] aleadam:
If I understand correctly, there is no way to get the changes to those files stick after a reboot because they are not stored outside the ram. You can automate the modification after each reboot by simply adding those commands to the S99_volt.sh file.

the command:

echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

will make the same change you made on root manager, it just can be included in the batch file.

I can't check any of this in my own phone since I am very busy till the end of next week and I cannot afford staying with a botched phone. I keep reading the threads though and I'm very curious to test the new kernel together with the "no bs" rom. For now, my phone remains a peaceful place where there's still some love between DG's rom and SetiroN's kernel :)
[Captivate Android Development] SetiroN:
Editing that file (and subsequently changing the other to 1) immediately enables the additional frequencies, but on reboot the default settings'd be loaded again.

Additional freqs have to be enabled on each boot, so an init script is necessary.

Xan is still working on a new version of his app that supports freq tables, so in the meanwhile we have to do it manually:

just create a new file, name it Sfrequencies.sh and put it in /system/etc/init.d/

#!/system/bin/sh
#set OC
echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

My point would be making 1.5 work for everyone instead of keeping older versions updated. :)

Can you elaborate on your issues?
[Captivate Android Development] Yuna:
okay, i got WHY i can't boot normaly without making those file: default MAX freq is 1460Mhz as stated by Quadrant...

and bTW:

$ lsmod

lsmod

dhd 280020 0 - Live 0xbf232000

bthid 5037 0 - Live 0xbf2f7000

storage 1453 0 - Live 0xbf2f1000 (P)

modemctl 8028 0 - Live 0xbf2e9000

svnet 30173 0 - Live 0xbf2da000

onedram 12342 2 modemctl,svnet, Live 0xbf2d0000

Si4709_driver 20887 0 - Live 0xbf2c4000

vibrator 8534 2 - Live 0xbf2bb000

ext4 342347 0 - Live 0xbf1dc000

param 11415 0 - Live 0xbf19d000 (P)

j4fs 74608 1 - Live 0xbf184000 (P)

rfs_fat 290513 2 - Live 0xbf131000 (P)

rfs_glue 90031 1 rfs_fat, Live 0xbf113000 (P)

fsr_stl 297235 6 j4fs, Live 0xbf0c1000 (P)

fsr 408894 2 storage,fsr_stl, Live 0xbf050000 (P)

s3c_bc 3146 0 - Live 0xbf04a000

s3c_lcd 5585 0 - Live 0xbf043000

pvrsrvkm 227320 42 s3c_bc,s3c_lcd, Live 0xbf000000

$

where is CIFS?
[Captivate Android Development] ice3186:
simple question

First yes i have searched and still not found the answer.

What is the XT version about? i am kind of lost as to what it could be.......
[Captivate Android Development] existz:
Yea I've removed UV, no lagfix, set states to 1000 and also 1200, via adb recovery ... it boots for about 3sec then just reboots..over and over ...
[Captivate Android Development] lpsi2000:
I understand your point and I think that would great if that happens.

the previous version, I can boot and perform all kind of test with no issues 1.4Ghz my uv settings are in my signature.

I would love to get the same result or better with 1.5 . I am able to boot at 1.36Ghz with the below configuration. As soon as I change any of the top 4 uv settings and /or add 1.4Ghz to the Limit Max Clock, it freezes, lockup and become very unstable.

uv 50 50 50 50 50 50 75 100 100 100 with the following two lines at the botton :

echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table

echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

I am also not certain that even 1.36Ghz was stable. But I figured the idea is be able to boot first then I can always use an application or manually configure it until I find something stable to work with. The uv settings you provided in your example does not work for me because I could not even boot with those settings.

So for me, I am not sure the additional frequencies or steps are helping. It is making it more difficult to nail down the right uv settings considering we now have 10 settings vs 6 in the previous version. And I think you also made additional tweaking from the previous release to OC above 1.2Ghz.

So that is my story and issue at the moment.
[Captivate Android Development] lpsi2000:
You don't have to search far, just read the first post and changelog to see when XT was introduced and changes it brings to the table.
[Captivate Android Development] DAGr8:
I have all 0 values phone is lightning fast but linpack runaround 14.. phone he no problem booting at 1460 scanning the SD is lightning fast but again what's wrong with theepoor linpack and yes iknoe linpack is overated btw why do we absolutely need to UV ... other then battery ... to me its simple if you oc do not worry about battery

sent from the future using xda app
[Captivate Android Development] ice3186:
yea i read that

thanks i read that. I guess i did not phrase my question correctly. What are the advantages to the xt tweaks?
[Captivate Android Development] DAGr8:
I am not able to set the clock on boot reagardless of how I set it when my phone boots its always 146000 so says UV app I think it is because on reboot it becomes RO again .. while the UV sticks because another file is edited ..

also I am running Axura and I dotn have to rename the file there is an interaction between the original file and the UV app ..

Edit :

Ok didnt read that before I posted , well there you go this is why ppl cant boot this kernel (wihout doing this) if there phone cant handle 1460 because on boot it will be set to 1460 no matter what for the same reason .

BTW IRC is a good place for support and chat #SuperOptimizedSGS @ Freenode
[Captivate Android Development] existz:
I've already done this, set it to boot at 1200 and 1000...still get endless boot cycle
[Captivate Android Development] ice3186:
is anyone stable

Is anyone able to get their phone stable on any version with any setting over the 1400 mark? Not at 1400 but the 1450/1460 mark? It boots up and runs like hell and then crashes both v 1.4.3 and 1.5? I would love to know what your combination Rom is and what voodoo magic your used to keep it running more than 5 seconds.
[Captivate Android Development] DAGr8:
Exactly what I have been saying , or maybe SEtiron wanna shed some light on this ?
[Captivate Android Development] Yuna:
Hmm, i am booting with success and using device @ 1200 with 1.5 kernel (NOT! XT) :)

my scripts for boot:
[Captivate Android Development] DAGr8:
ya forgot to mention to all I am on XT ....
[Captivate Android Development] tiger4j:
DAGr8...

It sounds like you didn't edit the 2nd file. I had that problem, but when I edited the 2nd file and ran linpack I got like 25.5. It should be around 2 files below the file where you input you values. Just turn a zero to a 1 and it turns it on. Should show the exact file in op.

*update_states* is the name of the file.

If you've already done that then I apologize.
[Captivate Android Development] existz:
I've tried both...with same results
[Captivate Android Development] Stephenv1971:
I think this may explain why I was unable to flash anything in clockwork unless I flashed 1.4.3 first. Even then it took several tries to flash 1.4.3 as my phone kept rebooting mid flash.
[Captivate Android Development] DAGr8:
wow I must be blind not only I still dont see this in the OP but file wont let me mod it it always revert back to 0 ?????
[Captivate Android Development] Killemalll:
I flashed v1.5 over Axura RC1. Everything is working perfectly. Thanks!
[Captivate Android Development] boomerod:
Hey, check Linpack and Quadrant scores. Mine went down significantly using 1.5; I flashed back to 1.4.3 1280, and scores went back up: 17-18.5, and 1800-1900.
[Captivate Android Development] shaolin95:
I am finally getting somewhere with this one..1400Mhz is now stable with '50 which I could never get with 1.4.3....it seems 1460 my GPU does not like as I get weird video artifacts...1440 I am trying to reach now.

My Linpack at 1400 is in the mid 19s so it seems correct and my Quadrant, for any who cares is in the 2000 range
[Captivate Android Development] bts0uth:
Will not work for me.

I have tried adding the following to my S_Volt_Scheduler script (which DOES keep my U/V and max cpu freq values after a reboot)

echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

and I have tried creating a new file in init.d with this

#!/system/bin/sh
#set OC
echo 0 0 1 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

and nothing works. The update_states file always shows 0, it never changes to 1 after a reboot.

I don't get it, how the hell do my U/V settings stay but the 2 lines I added do nothing? Really makes no sense to me.
[Captivate Android Development] DAGr8:
same exact thing here .. Im running th eXT one , I gonna try the non XT now , woudl really help if a few could join IRC chat so we could just talk live while testing ...
[Captivate Android Development] r.iqbal87:
Same issue here I wonder if changing permissions would do anything.

Sent from whatever I want att To think I have
[Captivate Android Development] Yuna:
maybe you people created file in windows format? try to re-create using unix file format ;) e.g not 2 symbols for line change, but one
[Captivate Android Development] bts0uth:
can you just post your file? lol
[Captivate Android Development] crazililazn:
:/ my phone cant get 1400 stable no matter what. even with no undervolt or 25 UV... Going back to 1.4.3 and sticking with 1280 mhz for now :(

Seriously though, i think a 1300 mhz setting would be really nice :x
[Captivate Android Development] bedwa:
Myself I fell back to the 1400 1.4.3 kernel cause the 1.5 seemed unstable and my quadrant sites dropped to pre-froyo levels. First time I've had any quirkyness from these kernels, but it was too much to just live with. IRC's not a bad idea though.
[Captivate Android Development] MikeyMike01:
Linpack went down from ~18 to ~14.

Quadrant went down from around 2200 to 1700.

I recognize that benchmarks aren't everything, but for now I've gone back to 1.4.3.

I probably did something wrong. Anyone gave an idea? All I did was flash it and update Voltage Control.

Sent from my Captivate.
[Captivate Android Development] existz:
I know my script is good cause I had to make one to set mount options commit=60,nobh and it works
[Captivate Android Development] crazililazn:
I just realized. On 1.4.3, you know how for the 14xx kernels, the default voltage is 1.35 V, then what are the default voltages for the other clock speeds, like 1 ghz, 800 mhz, etc. Are they the same as before, or have they increased as well?
[Captivate Android Development] d1g1talphyre:
I noticed the same thing MikeyMike01. Thought something went wrong, but at least someone else is reporting the same issue.

Haven't noticed any lag in games, or anything else. Just some lower than average benchmark results.
[Captivate Android Development] shaolin95:
Wondering why you guys are getting slower performance...mine just went up as expected.
[Captivate Android Development] crazililazn:
May i ask what your voltage settings are for 1.4 ghz?
[Captivate Android Development] bts0uth:
This is driving me insane.

update_stats will NOT change. I change 0 to 1 and save and it instantly goes back to 0. Nothing I do gets it to stay on 1. Not root explorer or a script file.

Same directory, right under update_states is UV_mV_table and it works perfectly and saves settings how it should.

So confused, been trying to get this working for hours. Waste of time I guess, nothing is working
[Captivate Android Development] crazililazn:
you arent suppose to change those, those are ramdisk files, they will never stay. You are suppose to add those 2 lines from the OP into the S_volt_scheduler file or w.e its called in the etc/init.d folder.
[Captivate Android Development] bts0uth:
I have done that. Typed it all out manually in root explorer and saved it. Did nothing, that file still has a 0 and not 1 even though I added the echo 1 command in my script.

What really gets me, is my voltages and max cpu freq load after a reboot but yet the two commands we add at the bottom do nothing.

Also, I tried copy and pasting the lines, tried making a separate file, tried adding .sh and not .sh and pretty much every combination. Nothing is working
[Captivate Android Development] crazililazn:
its not suppose to stay as 1. What the lines do is change the update_state file to 1 ON BOOT, so it applies the other frequencies you enabled (changing the 0 to 1) in the states_enabled_table file.

So basically, if you added the 2 lines correctly to your S_98_volt.sh file or S_Volt_Scheduler file, then the OC frequencies (anything higher than 1 ghz) should be applied on your phone.
[Captivate Android Development] DAGr8:
I just redi the file manually within the phon e, my linpack went back up to 19 ... I wonder why because the file still has 0 no 1 just like him :
[Captivate Android Development] DAGr8:
ok enlighten me ... the 0 on boot is chngedto a 1 but whn eI manually check it it is stil a 0 .. I ma very confused .. im still on XT tho , so I think now ill flash non XT just to test ...
[Captivate Android Development] crazililazn:
Its not suppose to stay at 1. When changed to 1 ON BOOT, it applies the OC frequencies from your states_enabled_table and then changes back to 0 once it applies the frequencies.
[Captivate Android Development] DAGr8:
ok well then Im all set , only getting 20 tho , on 1.43 I was getting over 22 @ 1450 mhz
[Captivate Android Development] crazililazn:
Try running it again? 1st run is usually a bit lower than normal :] and 20 sounds like you have 1.4 ghz enabled.... for the line... you are suppose to change the "0" to "1" according to the clock speed you want to enable.

So if you want 1460 the line should look like this:

1 0 0 0 0 1 1 1 1 1

If you want 1460 and 1200, it should look like this:

1 0 0 0 1 1 1 1 1 1

Get the pattern? each zero stands for each clock speed, going from highest to lowest, left to right. So, if you used the line in the OP, that means you only have 1.4 ghz enabled and not 1.44 ghz or 1.46 ghz.
[Captivate Android Development] DAGr8:
ya silly me im set like this :

1010111111

but hmm wait my states_enabled_table is not changing ..
[Captivate Android Development] crazililazn:
anyone mind sharing their UV settings for 1.4 ghz? no matter what i cant get it stable X.x
[Captivate Android Development] Killemalll:
Yeah, the scores are lower with 1.5 for me as well, but the phone feels as fast as with 1.4.3

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] joeshmoe08:
Actually Setiron I did read that but thanks anyways for making sure. :)

I just got my captivate and really don't need to restore anything with titanium so I am just going to jump to Method #3 and do steps 2-3. Great job on the kernel by the way.
[Captivate Android Development] DAGr8:
ok all my thing seem to apply for some reason even using notepadd++ wanst working at first ..

I have it set to 1460 and its lighting fast fastest I have seen my phone no random freezing (knocks on wood) witch clearly indicates its the gpu that was givin me issue on previous kernel (1.4.3) ...

I tested with setcpu and it confirms Im running at 1.46 Ghz BUT my linpack barely touch 20 ... sometimes 17 so for some weird reason its not much better then on 1.4 ghz (almost worst ).... although it feel much faster no doubt

Wanna specify I was getting 21 - 22 @ 1450 on previous kernel (1.43 non XT )

I dont care about bench too much irl phone is faster AND STABLE so kudos to you for this one SETIRON !!!!

I m running 1.5 XT on AXURA A2T6 ( I bundled the kernel inside of it )

I also one click jf6 right before

for some reason it seem the files in /sys/devices/system/cpu/cpu0/cpufreq/

dont like to be modified to often ,,, I have it set to 1000011111

oh insane battery drain btw need to play with voltage more right now its set to all 0s
[Captivate Android Development] shaolin95:
Every cpu and system is different but mine are

1400 -50

1360 -50

1200 -50

1000 -50

800 -75

400 -100

200 -100

100 -100

I cannot get anything over 1400 though...not that I complaining about finally getting 1400Mhz :-)

It seems my GPU does not like to be messed with at all.
[Captivate Android Development] magicman0:
Are you testing in "performance" or "conservative" mode?

Getting 19-20 on 1360 in linpack(my phone refuses to OC any higher :( )
[Captivate Android Development] crazililazn:
lol, my phone sucks at overclocking.... Tried your settings and it rebooted. Changed the 1400 setting to -25. and it crashes on the 3d test of quadrant... Dammit.

Why does everything i get suck at OCing >:O even my i7 sucks -_-
[Captivate Android Development] bts0uth:
1350 used to be stable on my phone but 1360 keeps freezing on the graphic tests of quadrant. ive tried with 0 U/V and everything up to -75. Nothing makes it stable.

Can't wait for a 12800 version!
[Captivate Android Development] shaolin95:
Your seems to be like mine...does not like speeds that mess with the GPU.

I am able to get 1400 now which I couldnt do before but any of the settings that affect the GPU and it gets all weird.
[Captivate Android Development] crazililazn:
1360 seems perfectly stable for me with -25 UV. I cant get 1400 stable no matter what. Have tried from 0-50 UV... :'(

Weird how when i try to get 1.4 ghz stable, when i have the UV at 0, it cant pass the 3d test in quadrant, but if i have the UV at 25, it can. However, either way, both settings are unstable... Lol, its the same with 1360 too.
[Captivate Android Development] JOe K.:
What's the situation on a wired headset (for phone calls with mic) on v1.5? Has that issue been resolved?

Thanks,

JOe K.
[Captivate Android Development] crazililazn:
That issue has not been solved on any reoriented kernel, and probably wont be until an official froyo build has been released.
[Captivate Android Development] lpsi2000:
I finally got it to work at 1.46 but it does not seem to be stable. I get occasional freezes here and there but it seems to happen mostly when I use the phone while it is plug in power
[Captivate Android Development] crazililazn:
Lol nice~ what I would do to get it working at 1.4 x.x
[Captivate Android Development] existz:
Looks like xcaliburinhand just got his reoriented working with wired headset support
[Captivate Android Development] lpsi2000:
Trust it was a pain trying to get the settings right so I can have the phone working at all frequencies. After further testing it looks like 1.44Ghz is going to be my daily use. 1.46Ghz is not stable enough for me. My uv configuration is in my signature.
[Captivate Android Development] glitterballs:
Advanced ext4 only works for sure. It seems as though none of the jfs options works. I've tested advanced jfs only, that definitely doesn't work, overkill jfs -not bound doesn't work. These options will give you the recovery loop. When you try to use jfs the file system is written in about a second, which makes me think that CWM isn't returning an error. I'm guessing that jfs wasn't included in the compilation options.

At the least the OP should be updated to tell people to only use voodoo or ext4 (or probably ext2/ext4). xcaliburinhand's config file would've included ext2/ext4 during compilation, which is why voodoo, advanced ext4, and probably advanced ext2/ext4 work.
[Captivate Android Development] kamots:
Right on! thank you