yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] StefanHamminga:
changing freq_table works for me in b9, but not in b8... so try to upgrade first.

You don't need the whole script to see if it works, you can test it by doing:

cat /sys/devices/system/cpu/cpu0/cpufreq/freq_table

to see the current table and

echo "1600 1400 1200 1000 800 500 200 25" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table

to set the new values, with another 'cat' to verify.
[Galaxy S II Original Android Development] AndroidGX:
Just tried this, it looks good and working but once in Voltage Control, it's 200Mhz which is still the lowest active value :confused:
[Galaxy S II Original Android Development] StefanHamminga:
Strange, can you check with SetCPU? Because I used that to check and it works with the new frequencies for me.
[Galaxy S II Original Android Development] tolis626:
Exactly what StefanHamminga said.

Download GScript(it IS your friend) and make two scripts,each with the commands that Stafan posted.If 100MHz still refuses to become 25MHz,try changing another frequency to see if it'll work.For me,beta 8 changes 1600 to 1624 just fine upon boot.

Thinking about it now I'm still wondering why I want those 24 extra MHz... :p
[Galaxy S II Original Android Development] AndroidGX:
Ok just checked with SetCPU and it is working ! thanks guys :)

I guess Voltage Control is not optimized with beta8+ then :D
[Galaxy S II Original Android Development] atomic339:
Can someone tell his GPU UV or OC?

Sent from my GT-I9100 using Forum Runner
[Galaxy S II Original Android Development] YaocH:
I did as instructed and after echo command, the values still remain as per before.
[Galaxy S II Original Android Development] zadkyn:
radio fm no working in miui 21.10.11 i have kernel 2.1b9
[Galaxy S II Original Android Development] tolis626:
You're welcome dude.Happy to help those who want to learn without becoming annoying.You know what I'm talking about. ;)

Do you use voltage control?If yes,change to another app,like SetCPU and see what happens.

Although it seems that there is a problem with beta8.Try beta9 or beta 7 and check it out again.Although beta8 works like a charm for me...
[Galaxy S II Original Android Development] Witherwings:
Greate Rom Thank you.
[Galaxy S II Original Android Development] Gowind:
buddy totally agree to what you say but at least for me the cwm 5 gives issues. i cant flash any zips using my cwm 2.0 app now. but most of the stuffs work in CWM Recovery though. but there also i faced an issue the other day. i couldn't restore a nandroid backup. it said md5 sum mismatch.

i have searched the forum and came up with a recovery.fstab file which i pasted in /etc but still the same..

never had such issues in earlier versions of cwm and i dont want to leave my favourate kernel just because i don't know the fix to this issue :confused:
[Galaxy S II Original Android Development] Witherwings:
YaocH, Check you have write permissions of the file.

Also check that you write the current path.

There might be something runing on background that prevent those values from being changes.
[Galaxy S II Original Android Development] jdmcivic:
same prob here. i can echo out the cpu freq values. set the min scaling freq .everything is applied when i did a cat. however 25mhz is not shown on cpuspy. 200mhz is still the lowest freq.

btw, how come with 2.1 i cannot set the up_threshold and sampling rate for ondemand¿
[Galaxy S II Original Android Development] YaocH:
Alright, it seems that voltage control was screwing with the values. I uninstalled it and now am able to edit the lower limit to 25MHz, however upper limit is still capped at 1600MHz. Am using b9 already, started to face this issue when I changed to b8 from b7. In b7 I was able to change the upper limit to 1696 with voltage control installed and had no permission issues also.

---------- Post added at 11:00 PM ---------- Previous post was at 10:54 PM ----------

As mentioned in my previous post, i added chmod a+w+x to my script which gives all permissions to all users for that file. I have determined that voltage control was affecting the changes. Nonetheless, thanks for your help!(:
[Galaxy S II Original Android Development] AndroidGX:
Of course ;)
[Galaxy S II Original Android Development] skiflyer:
hey guys.

since v2.0, the phone's always freezing when i want to wake it up. set the profile in setcpu between 500 and 100 mhz, always freeze... also with 500-200.. only when i disable the profile it's not freezing.. but why? does anyone had / has the same problem?

but everything is ok with v1.8 :s

edit: governor -> smartass v2
[Galaxy S II Original Android Development] psychoid:
check and raise your uv values 25/50. hope it helps :rolleyes:
[Galaxy S II Original Android Development] skiflyer:
not really. only the point of time, when it freezes is a bit delayed. can unlock it, then it freezes... but i have even 1000 mV @ 500 mhz - it's quite high, isn't it? saw others with 850@ 200 mhz...:confused:
[Galaxy S II Original Android Development] jdmcivic:
it would be nice if u posted ur cpu and gpu voltages for us to help u..
[Galaxy S II Original Android Development] frogman:
Its a Kernel
[Galaxy S II Original Android Development] redbullman:
I'm going to have 2 go back to cm7 for the time being, as the lack of Bluetooth calls whilst screen off makes this a no go for me as I make calls whilst driving a lot. I've brought this issue up 3 times and no one has even responded to me. When its fixed I will reflash this kernel as its fantastic. There is no problem when using CM7 so it must be fixable.
[Galaxy S II Original Android Development] crazykamui:
USB connecting....

Hmm.. I'm korean SGS2(M250S) user...

kernel 2.1-beta8 is usb connecting(adb or USB) - succeed

kernel 2.1-beta9 is usb connecting(adb or USB) - not succeed

Why..T.T check plz...

------------------------------------------------------------

Sorry Driver reinstall...... connecting Succeed... Sorry;;;;;.....

-------------------------------------------------------------

oops..;;;; external_sd not connet....

sdcard is connet Yes..

Your kernel is best kernel.. ^^ big Thanks..

ps : Sorry iam little English..
[Galaxy S II Original Android Development] skiflyer:
Sorry. Here you are :)

Sent from my phone.

---wrong file. will update immediately ---
[Galaxy S II Original Android Development] skiflyer:
sorry 4 double post. phone froze... :(

Sent from my phone.
[Galaxy S II Original Android Development] Bene2k11:
25Mhz works well, great. :)

With best regards from my ExynosROM-powered SGS2 always running the newest version of Siyah-Kernel.
[Galaxy S II Original Android Development] ozzyblack:
MANY THANKS TO YOU. XXX

KI4 rom on the siyah 1.8 Reccord battery live... AWASOME SUPER. HEAVY USE more than 2 days..
[Galaxy S II Original Android Development] usul1685:
Thanks for the answer. Do you (or osmebody here) know when Samsung will be moving to a new base?

Sent from my GT-I9100
[Galaxy S II Original Android Development] crypticc:
Md5sum mismatch. Did you rename or relocate the folder?
[Galaxy S II Original Android Development] Bene2k11:
Hey guys,

I'm in trouble.

Could someone please post the init.d script Voltage Control creates?

I'll have to make a flashable zip out of it to make my phone boot again without restoring anything. ;D

Thanks in advance,

Bene
[Galaxy S II Original Android Development] rauschkugl:
aos bug on beta 7 was very strong for me. it was also shown again. will test beta 9 now.
[Galaxy S II Original Android Development] peachpuff:
What voltage you running at 25mhz?
[Galaxy S II Original Android Development] Bene2k11:
Still the standard one, I have to get my phone working again, before I can work on the voltages ;D
[Galaxy S II Original Android Development] gokhanmoral:
I have made some modifications in cpu and voltage scaling part.

everything is "rock stable" on my device with stock frequencies.

I have even tried 25-25 conservative screen-off profile and didn't have a single lockup today.

therefore, I am "temporarily" disabling undervolting support in beta10.

normally, undervolting will be more stable with the new code because samsung has changed voltage scaling logic in "cpufreq_high.c" and during 200-to-500 transition the voltage is set to the voltage value of 1000 first. I did the same... during 100-to-200 transition, I set the voltage to the voltage value of 800MHz which makes the transition more stable.

however, I want to be sure that the new code works well on stock frequencies for everyone.

anyway... undervolting will be disabled in beta10.
[Galaxy S II Original Android Development] kalpik:
AOS bug is still present in Beta 9 :(
[Galaxy S II Original Android Development] atomic339:
So which app will you recommended for beta 10 to control oc?

Sent from my GT-I9100 using Forum Runner
[Galaxy S II Original Android Development] gokhanmoral:
it will be present in 2.1beta releases...

read my previous post about this to learn about the reason.
[Galaxy S II Original Android Development] gokhanmoral:
anything...
[Galaxy S II Original Android Development] kalpik:
Yeah.. I know you haven't merged .14 sources yet :)
[Galaxy S II Original Android Development] pixiebob:
i have read somewhere that it is ineffecient to block frequence, if you expect more battery life,because it will take more time to enter in sleep mode. so i think it is better to not use profil who limit freq screen off
[Galaxy S II Original Android Development] gokhanmoral:
and also I changed my mind about that AOS thing. it doesn't drain battery.

or else I wouldn't be getting 1.5 days with heavy usage (3+ hours of screen on)

I will still merge .14 sources while trying to find the reason that masks AOS...

but it will not be in the beta phase...
[Galaxy S II Original Android Development] kalpik:
I agree with you.. There is no difference in battery life with or without high AOS usage.
[Galaxy S II Original Android Development] Gowind:
No I did not. Before installing an ext SD card, my backups were stored in the phone's USB storage. Since I installed a memory card a backup folder was created automatically in it by cwm app and files were saved in it. But these files could never be restored by cwm app. In fact from cwm recovery 5.x.x onwards I could never flash any zip through cwm app.

Since cwm app was unable to restore my backup, I went to recovery and created a backup. This time the backup was made in the USB storage and when I tried to restore it, md5 sum mismatch.

I have gone to speedmod. Cwm recovery 4.x.x has returned and now I can flash any zips via cwm v2.0 app.

It's a really good kernel but I miss my siyah :(
[Galaxy S II Original Android Development] kunacs:
All my respect , this is the best Kernel, for me perfectionist kernel junky, but AOS bug does drain my battery now.

So pls don't forget the update source.

Keep up, u are the god of hell good sgs2
[Galaxy S II Original Android Development] lpsi2000:
I was going to ask which ROM you are on and also weather you had other scripts doing stuff too.

Based in my experience this issue is directly related with the fact you have backups with version 4 and you are trying to restore them with version 5 or you have backups with version 5 and trying to restore with version 4. Otherwise backup and restore works well.

When I had old (version 4) backups, I would install kernel 1.8 temporarily to do the restore then I was good. But now these days all my backups are with version 5

Yes, I am aware of the issue with CWM app but that is small price to pay so I can use my external SD card with CWM recovery. Backup and Restore seems to be faster with version 5 but then again it might just be me:D

Look at this, doesn't it feel really good that you figured out your issue and chased it down. At the same time you contributed to this thread. I personally do not use Voltage Control, so my help would have been headed in the wrong direction (may be).:D I have also learned something from your post.

My next comment is not a personal attack in any form or shape, but if you have dedicated the same amount of time and effort prior to your previous two posts, then this thread would have 2 less posts.:p

---------- Post added at 01:49 PM ---------- Previous post was at 01:46 PM ----------

If you have not figured it out yet, see my post above for an explanation of MD5 mismatch or CWM app.
[Galaxy S II Original Android Development] gokhanmoral:
I have reverted to 4.0.0.2 and won't go to any version higher until cf-root uses a newer version.

beta10 will have CWM recovery v4.0.0.2
[Galaxy S II Original Android Development] lpsi2000:
I am sorry to hear that, but it is what is., for you guys that are using CM7 this change will be interesting. Considering how CM7 swaps the storages (although I like the way CM7 does that).
[Galaxy S II Original Android Development] nerotix:
wow that sux balls, ill pass on this kernel then ;/ time to switch to CM kernel.

thanks
[Galaxy S II Original Android Development] :
Why exactly?
[Galaxy S II Original Android Development] AndroidGX:
Will you add the opportunity to enable 25Mhz automatically each reboots without having to use "Script Manager" and go to SetCPU to manually set min to 25Mhz to get it really enabled ? that would be awesome ! :)

25Mhz doing awesome work in idle/sleep (even if it's not detected on "CPU Spy"). I just hope it won't break our chips !
[Galaxy S II Original Android Development] Gowind:
nope i have made one backup with cwm app and the other within cwm recovery. both instances had recovery 5 installed.

anyways glad its confirmed that cwm app doesnot work with recovery v5.
[Galaxy S II Original Android Development] lpsi2000:
I think you just contradicted yourself, if CMW app does not work with recovery 5 (which we know), how can both backups were done with recovery 5 installed if you done one of them with the app?
[Galaxy S II Original Android Development] Gowind:
no buddy cwm app works with recovery 5.x.x but it wont function properly. say when you flash an update it will let you choose the update and reboots but then the update is not flashed. in the same manner when i tried to backup my rom through the app it made a backup in the ext memory card but when i tried to flash it, it was unable to do so. so i guess the issue is with flashing an update.
[Galaxy S II Original Android Development] lpsi2000:
@gokhanmoral

Sorry needed to quote myself, but I hope you reconsider the change to CMW recovery 4. Version 4 provide no additional value beside getting the CMW app working. For some us who are trying different ROMs (CM7, MIUI, etc...) where the kernels from these ROMs already have version 5, it will be mess switching between kernels and backups. As I said previously when you made the decision to go to version 5, I was reluctant at first, but then I saw why a lot people wanted 5. Also being able to use my internal and external SD is a great thing with version 5.

just my two cents on that topic and I am done with it.

---------- Post added at 02:18 PM ---------- Previous post was at 02:17 PM ----------

IC, okay thanks.
[Galaxy S II Original Android Development] caanda45:
Okay guys not as technical as you guys here, looks like I picked up cwm 5.0.2.6 here from the siyah kernel. (which I still use)

I have re-flashed 2.0 and still have cwm 5.0.2.6 but I have read in the op it is reverted back to 4.0.0.2. I gather the 5 series is not compatible with Chainfires app 2.0 (which explains why a couple of back ups never showed up after the back up)....so the question is how do I get back to cwm 4.0.0.2 and have it stay??? Read the above posts and now completely confused on what I should use....five has flashed okay some stuff for me......
[Galaxy S II Original Android Development] AndreiLux:
Regardless if the AOS percentage is correct or not (imho my testing, it roughly is, but there's issues with power consumption estimates that are not kernel bound but ROM bound, especially on Siyah), the cause of it going up is something that seems to be unfixable and does correlate to drainage and can be seen via other monitoring methods than just looking at AOS % in the statistics. It doesn't matter if the patch is applied or not as that won't affect it, but it would still be good to know what it does. But I already told you this...

Also +1 on CWM5, there's no reason other than political ones to keep staying on v4.
[Galaxy S II Original Android Development] stuliv12:
+1 reconsider ?
[Galaxy S II Original Android Development] Bene2k11:
PUSH... come on guys, please help me... :/
[Galaxy S II Original Android Development] caanda45:
Okay just flashed CF Root kernel v4.4 KI4 and back to cwm 4.0.0.2 re flashed the siyah kernel 2.0 and cwm 5.0.2.6 is back??? So the op says reverted back to 4.0.0.2, kind of confused here.....:eek:
[Galaxy S II Original Android Development] tristecire:
adb shell on recovery

@Bene2k11

Can't you repair it from an adb shell on recovery

(mv S_volt_scheduler S_volt_scheduler.old )
[Galaxy S II Original Android Development] crypticc:
Shame. I had same error and got it back by putting clockwork mod version temporarily to the version I used to make that backup.
[Galaxy S II Original Android Development] dtekkt:
My opinion of switching the cwm version is, that it isn't necessary, for me cwm app works, maybe an older version has problems with it? I'm using v2.0, if you wants I can upload it
[Galaxy S II Original Android Development] myakove:
Only from B10
[Galaxy S II Original Android Development] Bene2k11:
I don't know how this works. :(
[Galaxy S II Original Android Development] tristecire:
android SDK on your computer

@Bene2k11

I think the first good thing is to install the android SDK on your computer.

You gain access to the device ever it's bricked, by holding three buttons at the same time when booting ( you get recovery, then you can adb commands, it means android debugger). ggogle it, mate.
[Galaxy S II Original Android Development] Gowind:
no comments about switching the recovery version. but even i am using cwm v2.0 app. just try to flash another kernel with it and see for yourself. it will reboot but the update wont be flashed.
[Galaxy S II Original Android Development] AndreiLux:
I have no such issues.
[Galaxy S II Original Android Development] Bene2k11:
yeah, actually I know how it works but the connection here is to crappy(to download bigger files). ;D

Anyways, I got it working again, my fault was to write "s_volt_scheduler" instead of "S_volt_scheduler" ;D

Still, thank you for your help mates

With best regards from my ExynosROM-powered SGS2 always running the newest version of Siyah-Kernel.
[Galaxy S II Original Android Development] dtekkt:
Then you may have permission errors or something I am using it on every siyah kernel released yet and never had issues, btw using b7 right now and it also works there
[Galaxy S II Original Android Development] tristecire:
So, cool again

@Bene2k11

I'm happy for your fix.
[Galaxy S II Original Android Development] Gowind:
could you please tell me how i can fix that permission error.
[Galaxy S II Original Android Development] Rodrigo Vilhena:
Hello Guys, I've tried to flash this Kernel in a Insaity cm 48, using odin, and CWM, but after flashing I'm stock in boot screem Samgung Galaxy S2, the first boot screen.

Any tip how to flash it?

Am I doing some think wrong?

Tks.
[Galaxy S II Original Android Development] tanoxxx:
is by this mornig i try to do it, but can do it :(:(:(

i dont know why :confused::confused::confused:

i make exactly like this guide, but the value when save and exit are not saved.. and setcpu dont have a new 25mhz step :confused:

im so really confused :(
[Galaxy S II Original Android Development] caanda45:
Sorry not sure what you mean? todah rabah
[Galaxy S II Original Android Development] dtekkt:
Try uninstalling and reinstalling the app. In this way it gets deleted from superuser and also the userdata is deleted, hope it works for you
[Galaxy S II Original Android Development] tristecire:
just first and last

@tanoxxx's

Just modify only first and last, or , better just last.

1600 .........25

keep 8 steps in the scale.
[Galaxy S II Original Android Development] steemool:
What causes more battery drain: lesser % of CPU load on aa higher frequently or higher load percentage on lower frequencys proportial? It's essential difference between ondemandx and smartassV2 governors, i guess (correct me if I'm wrong, cuz I've seen a guide to governors behavior somewhere at this forum, a any related link would be very appreciated). What governor, except powersave (which is too laggy for me), is about battery saving? I want to set it for setcpu to use when under 50-40% battery left. Any advices?

Thank you guys for your responses!
[Galaxy S II Original Android Development] m2smoe:
my score on beta9:
[Galaxy S II Original Android Development] Jal253:
Thanks for the kernel, really impressive

Samsung Galaxy S 2

Checkrom Revolution v1

SiyahKernel v2.0
[Galaxy S II Original Android Development] tanoxxx:
Yeeeeeeeeeee :):)

Really Thanks :)

you have centered the problem...

the problem was a step.. must to be only 8

sorry if wrong that :( and thanks all guys have help me but first

thanks of the god of kernel: gokhanmoral :):):)
[Galaxy S II Original Android Development] myakove:
v2.1 beta10 will be with CWM 4
[Galaxy S II Original Android Development] xeq544:
Anyone please ? :( I dont wanna go back to samsung rom and I also dont want to wipe everything everyday to flash a new nightly....
[Galaxy S II Original Android Development] paaaulo:
2.1 b9 - App Protector Pro won't work. It doesn't load or it loads all the time - unable to unlock app.

With 2.0 it works flawless.

Thank you for your work.
[Galaxy S II Original Android Development] rauschkugl:
Does anyone have problems with kies air? It closes itself all the time on my phone. Don't know if it's kernel related but it worked on the same rom some time ago. Also reinstalling and wiping cache didn't help.

Sent from my GT-I9100
[Galaxy S II Original Android Development] Gowind:
thanks buddy but that didn't work too. but i am glad that now my restore works within the cwm recovery. i have read that cwm recovery 5.x.x can restore backups from ext sd card but i couldn't figure out how. can you help.
[Galaxy S II Original Android Development] dtekkt:
Really strange... you mean the restore works within the app? Sorry I don't use an external sd, so I never used and needed it, maybe someone else could help you
[Galaxy S II Original Android Development] Fibercoax:
Do i need to calibrate battery after a kernel flash too? or only rom.

Weird happen to me , bat jumped from 35 to 17 in one hit , and it crawling up the % automaticly ( looks lmao ) ( no battery loader )

im on beta 9
[Galaxy S II Original Android Development] frogman:
Just after Rom flash see here: http://xdaforums.com/showthread.php?p=18600161#post18600161
[Galaxy S II Original Android Development] cobhc:
As great as this kernel is, I think I'm going to go back to the stock CM7 kernel unless anything can be done about mounting the external SD card as mass storage, and sorting out ADB which is broken in Beta 9.
[Galaxy S II Original Android Development] AndroidGX:
Did you gave a try to "adbWireless (Widget version)" app from Market ? I'am actually using it with beta9 on Samsung ROM, and works like a charm here. Furthermore you don't have to plug everytime the USB cable to get it working, very usefull :)
[Galaxy S II Original Android Development] BoneMo:
i think that somewhere in Cyanogenmod Settings is a checkbox ..and when you untick it...internal storage and SDcard swaps...so then will computer see the external SD ...i hope i am right :o
[Galaxy S II Original Android Development] Gowind:
no buddy, restore never works within the app if you are on 5.x.x

i was telling about the cwm recovery.
[Galaxy S II Original Android Development] Galaxy_Fan:
@gokhanmoral :

Please stay on cwm 5!!!

Otherwise I can't use your kernel anymore on cm7.

Please, please, please!

:-)

Sent from my GT-P7510
[Galaxy S II Original Android Development] kickassdave:
Am I the only person constantly refreshing these pages till they find a mention that it now works with the latest (Galnet) MIUI??

:(

Can't wait till the (completely dark and non-existent) boot issue is gone.

Love this kernel.