yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] zikarus:
+1

And the bad thing: not flashing twice forced me to flash CWM Recovery via Odin and from there on restore another Rom since my device could not be handled without a PC anymore and was not booting at all after flashing the CM7 nightly 92 update just once... May have to do with the 5.x CWM.

btw.: like the photos on your website - well done...

Edit:

Am I the only one with a device that - using 2.1 betas (vr/ondemand, no uv/oc)) - shows some micro-lags during the Open GL/Canvas tests in Antutu. I do not encounter these lags with Speedmods kernel...
[Galaxy S II Original Android Development] xeq544:
Had same issues, I was so fed up after three complete wipes that I bought premium rommanager and now everything is simple :)
[Galaxy S II Original Android Development] AndreiLux:
Well it says 577mAh for the highest state. I can drain my battery from 100% to 0% in 2 hours using StabilityTest, let's say 1100mAh total theoretical from that, add in power from 2 hours screen time and other uses and you get to your 1650mAh battery capacity. So it must be for both cores, as if it were for only one core it'd be completely wrong and the figure would be too high. Depends also on how they use that value, if they scale it with CPU usage %, scale it down for dual-core use... etc.
[Galaxy S II Original Android Development] crypticc:
Guys problem it's fixed now. let's move on so this isn't a cm thread.

:-D
[Galaxy S II Original Android Development] kickassdave:
Since you said in your first post about asking.

Could we please get a version that works with the latest (and future ones obviously) Galnet MIUI?

Thanks in advance, your work is the bomb ;)
[Galaxy S II Original Android Development] flo2075:
No
[Galaxy S II Original Android Development] Barni86:
No to post is undervolting disabled in beta13. Undervolting is enabled. :)
[Galaxy S II Original Android Development] dreamdreamt:
The voltage settings are active.
[Galaxy S II Original Android Development] Sh0cK_:
Yabancı bir forumda Türk'lüğünü ortaya koymak güzel.. Tebrik ederim kardeşim.

Great work brother, thx for all you did. Keep up to developing!
[Galaxy S II Original Android Development] kokoskokis544:
Bln not supported in the latest beta??
[Galaxy S II Original Android Development] Entropy512:
Yeah, I'm fairly certain that the 577 number is the current for both cores - the question is, for reporting purposes, is it SUPPOSED to be the dual-core current, or is it supposed to be the single-core current? e.g., is all CPU battery usage being reported as double reality?

And this may be a Gingerbread limitation, but there's nothing in the power measurement code/XML I can see that properly handles the concept of a hotpluggable second core. (It's possible for our device to completely shut down the second core.)

Oh, and it looks like the AOS reporting changes somewhere between .10 and .12. Testing .11 once my battery hits full. I realized I can greatly speed up my tests by artificially inducing drain as follows:

ping -i 5 <ip address of phone>

This will force it to wake up every 5 seconds. Any less and there's a risk of it entering a (less valid for testing) stay-awake state.

It may also be possible to identify whether the infamous "AOS fix" somewhere between .10 and .12 has any effect on drain now, since it is possible to run a controlled drain test (ping it every 5 seconds for X hours and look to see if drain is different.)
[Galaxy S II Original Android Development] shr33kant:
Confirmed: usb mode is working fine now with usb debugging enabled. Both internal and external sd card are now showing up on CM7 #92.
[Galaxy S II Original Android Development] vnvman:
Heck i hate cm at times: since a couple nightlies ago i had to raise all of my voltage steps by 25, otherwise i get sod/reboots...really lame, at first i thought it was kernel related so i used cm stock for a day but the issues were still there...this is quite annoying ;(

Did anybody face the same issue?
[Galaxy S II Original Android Development] maxeli:
Latest beta reports guys? I'm to much of a noob to f**k around with bootloops and other more difficult issues... Latest beta bug free?? Can be used in the latest miui multilingual (from langthang) rom?
[Galaxy S II Original Android Development] shr33kant:
Could all this OC/UV be seriously f00king our phones cpu's? :eek: I'm glad I don't do any OC/UV anymore tbh.

I don't think I can be bothered to flash MIUI just to test this...I'm going to bed. Just do a nandroid backup and flash it, then report back to us? You can always go back to your nandroid if it all goes pear shaped.
[Galaxy S II Original Android Development] lpsi2000:
That is common with CM.
[Galaxy S II Original Android Development] Entropy512:
I need to run one final test to confirm, but it looks like it's going from .11 to .12 that makes the AOS bug change its character.

Fixed? Not necessarily. In fact it may be worse, as discussed in other threads, in that drain continues but it is no longer reported in battery usage. It'll take quite a lot more testing effort to determine if it is affecting drain at all. (At least one overnight test with .12+ and one with .11-)

Edit: Confirmed, it's going from .11 to .12 that reduces AOS reporting. It does not reduce drain though. (Need to specifically test in more detail, but drain increases without AOS increasing in my ping test.)
[Galaxy S II Original Android Development] Fibercoax:
workin fine beta 13 + BLN 0.15.10 beta
[Galaxy S II Original Android Development] BULL3TPR00F:
Hey can someone let me know where i can grab the latest test betas? All i saw in the OP was the stable 2.0 (but didnt see a link to any blog or anything to find the beta).

Is it a closed beta test?

EDIT: nvm stupid me, found the link to his blog
[Galaxy S II Original Android Development] syahrulzaman:
http://www.gokhanmoral.com/
[Galaxy S II Original Android Development] BULL3TPR00F:
Yeah thanks, i read through the original post again and saw the link, completely missed it the first time.

Thanks anways lol
[Galaxy S II Original Android Development] spradling:
10charrrrr
[Galaxy S II Original Android Development] terenceleechan:
can anyone post a tested method of undervolting to 25mv that sticks through a reboot? i've gone through this thread and there are so many methods, which one really works? or someone just organize them into one post? thanks!
[Galaxy S II Original Android Development] Nghtmare:
Wow on Batista 2.3 i get max 5500 on quadrant, but running on CM7 i got 7089!! How is that possible with the same kernel??
[Galaxy S II Original Android Development] caanda45:
Just shows me that quadrent is a crock of $hit.
[Galaxy S II Original Android Development] Nghtmare:
Lol could be.
[Galaxy S II Original Android Development] chadouming:
The way CM7 handle files is more efficient than sammy. That explain why CM will always be ahead in benchmark.
[Galaxy S II Original Android Development] caanda45:
Maybe but from what I have heard quadrent is not set up to appropriately test dual core phones....but I do take all my results on it with a grain of salt...
[Galaxy S II Original Android Development] lsj_87:
Having problem with online apps such as "livescore" , "LINE" and etc since kernel version 2.0. the apps keep on show no internet connection but actually the phone is connected to the internet through wifi/data. everything works fine in version 1.8 but not 2.0 above. only occur on few apps. do anyone having this problem ?
[Galaxy S II Original Android Development] SmallHunter:
Got any intro about the setcpu ? sorry i am new user galaxy S II
[Galaxy S II Original Android Development] Nghtmare:
That's also true, anyways everything will change with ICS.
[Galaxy S II Original Android Development] queenkong:
Thanks so much for this amazing kernel! It not only solved issues of my phone with MIUI 1.10, it also improved my phone's performances!!

Great work!

Now to test for battery life, but I am confident it will be good :))
[Galaxy S II Original Android Development] :
airplane mode/gsm coverage

hi,

in 2.0, i having issues with smartassv2 governor.

if i apply this governor, and after a time on it (1-2 hours)

i set the airplane mode, the gsm coverage is lossed, but not the 3g session.

next, when i unset the airplane mode, the gsm coverage is not recovered

until i reboot the phone.

i have downgraded to 1.8 and seems not having this issue.

anyone with this problem¿?
[Galaxy S II Original Android Development] agabey_42:
siyahkernel very goot but miui rom siyahkernel fm radio does not work with

========

gökhan kardeşim eline koluna sağlık, miui rom yükledim ve senin 2.1 beta kerneli attım fm radyo çalışmadı miui romda. sonra siyah kernel v2 yükledim ama yine fm radyo çalışmadı. miui rom ile uyumsuzluğu konusunda bir bilgin varmı???(Ankara'dan selamlar.)
[Galaxy S II Original Android Development] Auridran:
Overclocking and undervolting alone should not do anything to harm the processor, unless the overclocking causes the phone to heat up beyond safe thresholds. Overvolting on the other hand can cause degradation, but it's usually not noticeable for years unless you're overvolting by a significant amount.
[Galaxy S II Original Android Development] jayquinten510:
I would have thought uv would have decreased processor wear?
[Galaxy S II Original Android Development] Auridran:
If anything, yes, it would.
[Galaxy S II Original Android Development] boqonx:
You would also increase the chance of processing corrupted bits, since the transistors would be running at lower-than-rated normal operating voltage. This is why undervolting/overvolting varies from batch to batch, it really depends on how well the transistors are running below/above the rated voltage.
[Galaxy S II Original Android Development] Auridran:
This is also correct. I was specifically talking about affecting the processor's life, however.
[Galaxy S II Original Android Development] yoplaboum:
2.1b13 works very well good job ! ;)
[Galaxy S II Original Android Development] Zanr Zij:
Do you undervolt? How about your setting?

Sent from my GT-I9100
[Galaxy S II Original Android Development] pimser:
with b13 i cant set my max to 800mhz using same script linke in b9. in b9 i had no issues at all with it.

any idea?

thx

EDIT: according voltage control my uv setting are set by the script but not my cpu max. with vc im able to set the max but its not working with the script. hmmm?
[Galaxy S II Original Android Development] jayquinten510:
I cant for the life of me find Gok's post on b13, can anyone link to it?

The actual post as well as the file.
[Galaxy S II Original Android Development] CA3iR0:
Isnt 2.1b13 compatible with bln?

Im not getting "buttons light notifications" at all after i updated to the last beta and the last Cyanogenmod nightly... fffuuuuuuu
[Galaxy S II Original Android Development] bandit79:
No Problems with 2.1b13 and BLN
[Galaxy S II Original Android Development] Rockin_Zombie:
all the betas are posted on his website:

http://gokhanmoral.com/
[Galaxy S II Original Android Development] gokhanmoral:
I removed the delay before executing init scripts.

there is something which sets the maximum freq to 1200 during startup. I don't know what it is.

if you want to change the upper level, either use setcpu (it has its own delay) or put "sleep 30" at the beginning of the script.
[Galaxy S II Original Android Development] CA3iR0:
Here's the error.

And i see some more users complaining about the same bug...
[Galaxy S II Original Android Development] gokhanmoral:
I do not install the required library automatically anymore (to avoid possible conflicts with new bln implementations).

if the rom doesn't support bln, you need to execute /sbin/siyah/inst-liblights.sh to copy the necessary library.
[Galaxy S II Original Android Development] cheewaca:
I´ve the same issue and more lag in galery and over aplications menu with 2.0 final, 2.1 b12 and b13.
[Galaxy S II Original Android Development] BoneMo:
My Voltages settings:

1600Mhz - 1350mV

1400Mhz - 1300mV

1200Mhz - 1250mV

1000Mhz - 1125mV

800Mhz - 1050mv

500Mhz - 925mV

200Mhz - 900mV

100Mhz - 875mV

Rock stable on my phone
[Galaxy S II Original Android Development] xeq544:
I cant change the frequency steps in freq table. When I change it and save it (mounted as read/write) it just doesnt save. Root explorer says its saved but all the values return to default when I reopen it. I only managed to get the lowest step changed from100 to 50.

I wanted to set up my frequency steps as follows: 1400,1200,1000,800,400,200,100,50 or 1200,1000,800,600,400,200,100,50
[Galaxy S II Original Android Development] nerotix:
I had 2.1b13 installed and it was working good last night, this morning I woke up and my phone had wouldnt wake up ;/ Didn't had any UV settings and the only thing I changed was minimum to 100. Anyone experienced this too? I'm on MIUI 1.10.21.
[Galaxy S II Original Android Development] kickassdave:
I am confident you can UV much more than that!! I've always been able to manage the following.

1200MHz - 1150mV

1000MHz - 1075mV

800MHz - 1000mV

500MHz - 925mV

200MHz - 850mV

100MHz - 800mV

Ain't had one crash.... just waiting on this kernel supporting the latest version of the Galnet MIUI.

:(
[Galaxy S II Original Android Development] Zanr Zij:
Compare to my previous setting on Siyah 2.0 kernel, your setting is too high.

1600 - 1350mv

1400 - 1250mv

1200 - 1150mv

1000 - 1050mv

800 - 950mv

500 - 825mv

200 - 800mv

100 - 775mv

When I increase about 25mv each step/state, 2.1b13 still cause my phone freeze.

How about your battery performance?
[Galaxy S II Original Android Development] terenceleechan:
anybody can give detailed steps on how to edit frequency table? also how to make it stick through a reboot? thanks!
[Galaxy S II Original Android Development] xeq544:
+1 Would love this too
[Galaxy S II Original Android Development] AndroidGX:
The only solution I found to really make the "S_volt_scheduler" script working after a reboot is to create that script directly by "Voltage Control" app (requires a clean reboot before), (Menu > Save as boot settings), once it's done you open the file with "Root explorer" which is located in "/etc/init.d/S_volt_scheduler" in R/W and ...

after this :

echo "Starting Insanity Volt Scheduler $( date +"%m-%d-%Y %H:%M:%S" )" | tee -a $LOG_FILE;​

add this :

echo "Set Frequency Table" | tee -a $LOG_FILE;

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

echo ""

echo "---------------"
​

and modify your UV values located right after :

echo "Set UV" | tee -a $LOG_FILE;​

once it's done, save and quit. (and delete the auto backup generated by root explorer, if needed).

Now you can reboot and it will works each time you reboot. :)

I guess it's a problem of permission on the file but even if we set after, it's not working. You really need to generate a new clean script by Voltage Control.
[Galaxy S II Original Android Development] BoneMo:
about 3 - 4 days of light usage with Villain ROM 3.0 and i also have 2000mAh battery
[Galaxy S II Original Android Development] vandanh15:
thank you.

about sharing it.

it will be very promising at the baterry of S2.
[Galaxy S II Original Android Development] nightranger73:
That's because UV will give you only 10/20 minutes more. The main consuming responsible are display and modem while CPU stays most of the time in deep sleep and when it's working you save only 75/100 mAh

On heavy usage you could have better results but again display and modem usage will raise
[Galaxy S II Original Android Development] boqonx:
I'm not sure if this had already been discussed before, but has anyone ever thought of dynamic scaling for GPU? (both voltage and clock)
[Galaxy S II Original Android Development] xeq544:
Did that, changed values here to

echo "Set Frequency Table" | tee -a $LOG_FILE;

echo "1200 1000 800 600 400 200 100 50" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table

echo ""

echo "---------------"
​

But after reboot all my values stay on default.... :(
[Galaxy S II Original Android Development] BoneMo:
well i am going

TO TEST VOLTAGES:

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

1600Mhz 1350mV

1400Mhz 1275mV

1200Mhz 1175mV

1000Mhz 1100mV

800Mhz 1000mV

500Mhz 925mV

200Mhz 875mV

100Mhz 850mV

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

or is it still to much in your opinion ??
[Galaxy S II Original Android Development] tristecire:
@xeq544

Maybe 50 isn't a valid uc value, test the same with 25 as last value

and see if it works.

And it seems you must keep 200 as the second low value, too.
[Galaxy S II Original Android Development] terenceleechan:
thanks! 10char
[Galaxy S II Original Android Development] frankcilo:
Battery life with beta13 seems very good!

With all prevoius version of this kernel battery life isn't good how Ragemod kernel, but now is good!
[Galaxy S II Original Android Development] Bene2k11:
Hey my beloved Siyah fellows,

I'm currently working on my freq_table and the related small UV.

Firstly, my current settings(which freeze the phone ;D ):

1200 Mhz @ 1275 mV

1000 Mhz @ 1200 mV

800 Mhz @ 1100 mV

600 Mhz @ 975 mV

400 Mhz @ 900 mV

200 Mhz @ 875 mV

100 Mhz @ 850 mV

50 Mhz @ 825 mV​

As I said, these settings cause a freeze.

So my questions are the following:

What voltage values would you suggest to make the phone boot properly at all?

Do you think the frequencies are chosen well at all or would you suggest something else?

Not related to the subject directly: In the updater-script of a flashable zip, is it necessary to give the flashed init.d script 0755 permissions?

I hope there's someone to help me out.

Thanks in advance,

Bene2k11
[Galaxy S II Original Android Development] holyshit1:
I am very pleased of battery life, for 8 hours it drains only 4% from 100% to 96%. I am with beta13. Amazing!!!
[Galaxy S II Original Android Development] xeq544:
first of all, you should test each step individually, go back to stock values on all steps.

Select performance governor and 1200mhz, undervolt by 25mv, check stability, undervolt by another 25mv and check stability, repeat untill your phone freezes and return back to last stable value. Repeat for each frequency step. Worked for me and now I have rock stable phone.

But the issue with the freq table not changing still persists for me ! aaaargh. No matter what I set, either directly in the freq table or in the voltage control init script it still stays at default ! (beta13)
[Galaxy S II Original Android Development] mikebike20:
New update of voltage control (only extreme version, paid version) including same features as cpu spy.

To Gohkan : kernel 2.b13 is running fine on miui 1.10.21 but we still can'tuse radio fm and a bug od dispaying usb bebugging still here too even when you unplug yur phone. Hope you can fix that mate...
[Galaxy S II Original Android Development] tristecire:
@xeq544

Some few posts higher in the thread, i suggested you

that some values, or combination of values are not OK

and not writable.

Unbelievable, but true.

So, try with 25 and then 200 as lower values.

For me it worked.

I know that there are not your wanted values, but seems it's the only way to go.
[Galaxy S II Original Android Development] xeq544:
Unbelievable, but I already tried that. I also tried changing just the first step, or just the fourth step. I've tried everything.
[Galaxy S II Original Android Development] AndroidGX:
Of course I forgot to mention that you need a clean boot without any saved UV settings :

- for Voltage Control : Menu > "Remove boot settings"

- for SetCPU : Voltage tab >

untick

"Set on Boot"

... reboot > and then you follow my steps ;)

And I agree with tristecire, 50 is way too low, it's even more a not a authorized UV value, lowest possible on 2.1 beta is 750mV (if my memory is good).

On 2.0 it's 800 (info in first post of the thread).
[Galaxy S II Original Android Development] tristecire:
So, sorry, working here. Editing with root explorer, no way with 200 100 25,

then written with 500 200 25, can't say why, but surely gokhanmoral knows.

Now it's on a script in init.d, working too, but with the known limit to 1200 at boot. Haven't yet tried the sleep 30 at beginning of the script as suggested by gokhan.

---------- Post added at 11:50 AM ---------- Previous post was at 11:47 AM ----------

@AndroidGX

50 and 25 are uc values, not uv ones.
[Galaxy S II Original Android Development] AndroidGX:
Ah ok sorry, I tought you guys were talking about mV :D :)

BTW, gokhanmoral, beta13 has a very good battery life, I can confirm too, RC way is not so far I guess :)
[Galaxy S II Original Android Development] nerotix:
I can confirm this aswell. However this morning my phone wouldnt unlock with beta 13, and I didnt UV, I only set minimun to 100. So I've no idea why it wouldnt wake up.

Thanks
[Galaxy S II Original Android Development] joeyfong:
So we need to flash the kernel twice in cm for solving the boot logo stuck problem?
[Galaxy S II Original Android Development] Galaxy_Fan:
No. Just don't use the cwm app ,go into recovery, wipe cache and dalvik ,flash!
[Galaxy S II Original Android Development] _Garry_:
I did flash the newest kernel via CWM. Went smooth like **** XD
[Galaxy S II Original Android Development] joeyfong:
I will try when the nightly out later, thanks
[Galaxy S II Original Android Development] kartalgurhan:
Sorry for quoting my prev message but I found the diagnosis of AndreiLux:

http://xdaforums.com/showpost.php?p=18259203&postcount=3148

Therefore my question is:

in case of a freq_table having the following values:

1400 1200 1024 824 524 224 150 75

and when I touch the screen , to which CPU frequency will the touchscreen driver locks?

using 2.1b13

thanks again
[Galaxy S II Original Android Development] AndreiLux:
224MHz in your case.

Btw Gokhan; are you circumventing the freq_table changes when entering sleep to stick to the 800MHz "specification" ?
[Galaxy S II Original Android Development] WebReaper21:
I'm not 100% sure, so correct me if I'm wrong, but I belive the values are set too low. Gokhan said in a previous post that the new frequencies could not be lower than the next default step. I had the same problem and after I changed this in my skript, it worked.

These are the minimal steps that worked for me: 1401 1201 1001 801 501 201 101 25

Although the 101 MHz are almost never used and thus I raised the lower steps a bit.

You may set some steps higher if you want to.

Hope this helps...
[Galaxy S II Original Android Development] kartalgurhan:
thanks for the quick response. Somehow, it is difficult to confirm but seems like I keep getting 524. Of course, there could be other background processes that makes it harder to confirm.

regards
[Galaxy S II Original Android Development] bgx:
Then you must set these values:

1401,1201,1001,801,501,201,101,50

it should made this:

1400,1200,1000,800,500,200,100,50

The reason is that you only could change in the range between the stock values! ;)
[Galaxy S II Original Android Development] DobermanS:
!!!!!

Huge problem with beta 12 and 13 on MIUI.... :eek:

When phone connected to car BT and trying to dial,phone freezes,screen shuts down,till the call drops and the phone gets alive after a minute...
[Galaxy S II Original Android Development] xeq544:
Thank you :) I hope voltage control gets updated with these changes so we dont have to do this manually.
[Galaxy S II Original Android Development] jayquinten510:
Hey, love your work gok!

On flashing the new beta13, setting my previous uv values has resulted in several freezes. These values were very stable on 2.0.

Why is this happening?
[Galaxy S II Original Android Development] energie:
raise your voltage
[Galaxy S II Original Android Development] bundi22:
how come cwm backup is backing up to external SD? it is failing because I don't.have enough room. how do I switch it? thanks
[Galaxy S II Original Android Development] jayquinten510:
Thanks, I know how uv works.

But why can I use the same voltages with no freezes on 2.0, but on v2.1 get loads of freezes?
[Galaxy S II Original Android Development] energie:
again.....its a different kernel.

raise your voltages, u wont gain considerable juice with UV.