yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] WebReaper21:
Well that's not completely true. The linear scaling of power consumption vs clock rate will not hold for low frequencies, as the clock dependant power consumption is only dominating for higher clocks. At low clock rates static power consumption due to leakage through the substrate, and in our case also the radio part of the phone, will become increasingly dominating. A few months ago I also saw some measurements which showed that the linear scaling was about true above 500 MHz. Unfortunately I don't have the link anymore.

The point is that you wouldn't see much of a difference in power consumption between 25 MHz, 100Mhz and maybe even 200Mhz because of the pure differences in clock speed.

The time spent in the respective power states to complete certain tasks on the other hand may make a noticable difference.

To go even further, there is also a difference in power consumption between different loads at the same clock. So if you have 25% load at 200MHz the chip will consume less power than at 90% load at 200 MHz because more load means more recharging of capacitors and normally more cache and RAM activity, etc.

Anyway I support the second part of your answer.
[Galaxy S II Original Android Development] stevehkim:
i dont know what i did but after reflashing 2.6.6 without wiping anything its working flawlessly. deep sleep is at 95% after 20 mins screen off. pages and apps are flying with no stutter. thx gokhan and xda members for everything.

tweaked - by me

kernel - siyah the og

rom- me you eeee.
[Galaxy S II Original Android Development] chadouming:
IMHO, I'm not sure at all it scale linearly. It's not simple like that. also, 25 Mhz might worth it depending of your use of the phone.
[Galaxy S II Original Android Development] veyka:
There's not much the phone can get done in 25Mhz, and it would have a hard time waking up at that frequency if you have anything meaningful running in the background, even 100mhz can be a bit low sometimes.

I don't see the potential battery savings, with the screen on 25mhz wont be enough todo anything so it will probs not use it very much, with screen off eg playing music it might work, but at the same time I remember someone saying that it wasn't enough for even that.

Also you are more likely to get very slow wakeups or SoD's.

PBCK!
[Galaxy S II Original Android Development] minidou-77:
25 Mhz is a way too low for playing music

At 100 Mhz I hear some bugs when I change the volume so ...
[Galaxy S II Original Android Development] tolis626:
Well,it's not.As WebReaper21 said,at such low clock levels it doesn't drain that much at low clocks.It might save power,but such negligible amounts aren't worth the potential instability.I've tried,trust me. :)

I clearly stated that what I said isn't exactly accurate,didn't I? ;)

I remember that post.I don't remember whose it was(Although I suspect it was Entropy512),but I also remember there was something fuzzy about 500MHz.Anyway,that's irrelevant.I just wanted to give a simple explanation. :)
[Galaxy S II Original Android Development] incubus_fr:
Is there any way to overclock it on top of bus frequency on the S2?

Because, if I'm right, ram is clocked by the bus. I don't know if there is any improvement to come with the clock.

Maybe playing with timings (ras, cas, etc...) instead could be fun :cool:
[Galaxy S II Original Android Development] veyka:
200mhz all the way :)
[Galaxy S II Original Android Development] droidphile:
Frankly, i have never tried overclocking ram: pc or an android device.

Anyway does our mighty LPDDR3 1GB monster require OC? Already so many tunables in Siyah and i'm confused how to sync all the tweaks to the best combination possible and laugh like a maniac watching the sheer power & performance gs2 can deliver :D

We already have a 'virtual' ram OC through static bus speed scaling. We can increase the memory throughput using higher bus freq and now that there's internal voltage modification support (tegrak OC app), the higher bus speed for lower frequencies can be matched by raising the internal voltages.

Now that Samsung has launched Exynos 5250 soc which will come with a 2ghz arm (GS3?), we might not stick to S II too long :)
[Galaxy S II Original Android Development] WebReaper21:
Well then I'm sorry, I must have somehow missed the part in brackets :o

Although I hope that my explanation might give some more insight to those people who are all about clock rates and think power states are the one and only way to judge power consumption ;)
[Galaxy S II Original Android Development] stevehkim:
If I remember correctly the kernel I ran on my Atrix (clemsyns elite kernel), RAM was OC'd to 333 mhz. The Atrix as well has 1gb of RAM and it made a pretty nice improvement overall.
[Galaxy S II Original Android Development] pikachu01:
If you want to know more of what ThunderBolt! does, you can read the Android Optimization Tips in my sig as well as the changelog. It does give some hints of what it is. Other than that, you can ask it in the forum too :) I'll be more than happy to give you the information you need :)
[Galaxy S II Original Android Development] kobi63:
Should I have a 01Siyah file inside the init.d folder? Cause I don't..
[Galaxy S II Original Android Development] cmd512:
Maybe I should have explained further: I used to have really complicated scripts that swapped between governors depending on states, etc. But, I'm currently in a "simpler is better" frame of mind, so while I appreciate your offer, my response is still no thanks. Hope you understand, just my personal preference, I'm sure your scripts are fine. :)
[Galaxy S II Original Android Development] minidou-77:
No you should't have it since you don't use the packages that gokhanmoral had made a mounth ago (or more/less I don't remember)

They (battery.zip performance.zip default.zip) have been removed from his website so now you can make your own one or use thunderbolt! scripts
[Galaxy S II Original Android Development] KcDaRookie:
@cmd512: ThunderBolt! has nothing to do with governors or cpu freqs etc, it's about system and database optimization and network performance etc...

So none of the values in your script will be nearly touched, you should take a look at it before making up your mind ^^
[Galaxy S II Original Android Development] cmd512:
I appreciate all that, but again, it has to do with diminishing returns. Yes, if I wanted to take the time to really go and tweak every little setting possible with this phone, I would certainly take a look at it. With the basic settings I have in my init.d, I am more than happy with the stability and performance I get out of my phone with stock ROM and Siyah kernel.

(Note how I'm not on some "SUPER BATTERY SAVING SUPER DUPER" deodexed ROM either. After all the previous HTC devices + SGS, I find the stock ROMs to run amazingly well on the SGS2. Again, diminishing returns.)

For me personally, at some point, the "if it ain't broke, don't fix it" attitude comes in. With the millions of posts that are posted after every gokhan release having to do with this and that being broken, I sometimes wonder to myself if much of those are from these millions of little deep level tweaks that people CAN do but don't understand the true ramifications of. Once again, diminishing returns, I simply choose not to bother. :)
[Galaxy S II Original Android Development] pikachu01:
Thanks. Applied the fix.

Did you undervolt too much? Try not undervolting and try again.

Yes. :)

Yes. :) It's a bug with Siyah though, as GM already mentioned.

CFSK (which is S98CFS).

Are you undervolting? What governor are you using?

Remove all the scripts except:

s70darky_zipalign

s78enable_touchscreen_1

s98bolt_siyah

S98CFS

S98screenstate_scaling

S98system_tweak

Check out my sig :P

Android won't kill apps when RAM is abundant. Although the app is still in memory, it won't consume battery (unless it requests for wakelock like Facebook or Lattitude).

Not sure what you mean here. Care to elaborate?

Try using OndemandX?

That sounds pretty serious. Try using OndemandX?

Try using my method of undervolting. In Android Optimization Tips. CTRL-F for "undervolt".

You can do the same using Voltage Control :)

And yes, you can do that if you want to use a script to do the same thing.

What's your ROM and can you access CWM? Try removing your undervolting settings via ADB. Google for "ADB for dummies" and go into ADB and remove all files inside /system/etc/init.d.
[Galaxy S II Original Android Development] :
@Pika you are a star you are...What are the differences by using your Thunderbolt scripts and using Lulzactive app from market? And do your scripts work for all governors?

Thanks buddy...
[Galaxy S II Original Android Development] pikachu01:
ThunderBolt! tweaks the lulzactive parameters directly. The app is just an interface. It currently works for Ondemand, OndemandX, lulzactive and smartassV2.
[Galaxy S II Original Android Development] :
Good to hear that as i am currently testing out Ondemandx and SIO scheduler...Will report back...And out of all the kernels this one gives me no lag at all even when browsing through app screens.. Using TW launcher
[Galaxy S II Original Android Development] ajvulcan:
@pikachu01 Ondemandx is the same. I have try several roms, it seems that all the samsung based roms works well, the problem is only with miui, at least with miui 2.1.6, an incompatibility maybe?
[Galaxy S II Original Android Development] olifee:
Hi!

1)

I am also on CheckROM Revo HD4 and have experienced the Wifi-problems. They are actually also described somewhere here in this thread, and I also reported them to the checkrom-forums, but somehow, they were deleted there mysteriously...

I fixed them by replacing the wpa_supplicant which ships with CheckROM RevoHD 4 with one from this board here (simply search for a build with adhoc support - although this is totally not needed for the connection, it is not BROKEN as the one included in CheckROM RevoHD 4 is. The one in the version before 4 was working fine for me, the one in version 4 showed in the logs when I enabled wpa_supplicant-debugging that something failed in Auth Phase 2).

Actually, Phase 2 Auth setting IS saved, you can check in the wpa_supplicant-config (somewhere in /data/wifi if I am not mistaken, it's called bcm<something>.conf). The GUI just does not recognize it somehow in Android.

So the auth-bug actually appears to be a bug in CheckROM, not in kernel, at least for me.

2)

Can you try to run the scripts in a terminal-app, or even better, install sshdroid and connect to your phone via ssh (putty or cygwin on Windows) and run the scripts there? Another alternative is adb. Just to get some error message finally ;).

3) There are actually just two levels for charging power, IIRC, 450mA and 650mA. All values >450mA are interpreted as 650mA.

It's in the changelogs and at some places in this thread ;).

Good luck with your wifi!
[Galaxy S II Original Android Development] kman3d:
Hi, I have two phones that suffer from same issue of sometimes not waking up, and only by turning off the phone can be solved.

I don't OC/UV... I think this issue apeared after 2.6.2 (2.6.6 still having this issue)

Any one else having it?

Thanks!
[Galaxy S II Original Android Development] Holgott:
Hmmmm...can someone answer this issue: i was good on 2.6.6 tilltoday and i changed govenour from lulz to ondemand ..after that i had to put my phone to charger and after some mins when i was looking on it the phone was off and didnt react anymore-just black screen and it was hot all over the phone ..it just could start again when i put the charger off. Now the phone is running well again but what was this??? Any answers?
[Galaxy S II Original Android Development] stevehkim:
You had a SOD? Are you running thunderbolt? I noticed thunderbolt 2.3.5 doesnt work with siyah 2.6.6. I had SOD as well. Use thunderbolt 2.3.6.
[Galaxy S II Original Android Development] Holgott:
Im running a "clean" siyah ..just 200mhz 25mv uvted ..never had any probs like that ..hmmm running sio and lulz again now 200-1200
[Galaxy S II Original Android Development] fusionjack:
Seems fine on my MIUI about deep sleep. The only problem I have is random SOD with / without WiFi, on lulzactive or ondemandx. I know I use undervolting. So I'm back to 2.6.4 now.
[Galaxy S II Original Android Development] iqzy:
I've installed this kernel but feel it is worse than Speedmod! Battery performance is horrendous. Can anyone recommend me a good kernel? I'm running Checkrom Revo4 HD
[Galaxy S II Original Android Development] blunted09:
try siyah 2.1.1 with checkrom. it works great for me under heavy usage.
[Galaxy S II Original Android Development] jaher:
Can using setcpu with siyah cos freezes on lockscreens. Or can siyah do that. Is there any good in using setcpu woth siyah
[Galaxy S II Original Android Development] ajvulcan:
What version of miui are you runing? an official chinese one? uk? us?...or maybe one cooked like galnet miui?, and is the last one? v2.1.6?

My phone enters in deep sleep, but less that it should. The worst problem is that governors don´t work well, in concrete lulzactive, which don´t scale frecuencies, or it does from time to time, which is unacceptable,overall because it freezes in high frecuencies even with no load (doing nothing).

siyah v2.6.4 is not good for me because i play games and with that version my sgs2 freezes or reboots with worring electronic sounds and with 50ºC of temperature or even more with only some minutes playing. (maybe siyah v.2.6.5?)
[Galaxy S II Original Android Development] Hertz33:
Good God people!!!

Pages upon pages of scripts and complicated formulas, Stephen Hawking would be lost here. And all for the sake of what? I use stable rom with the 2.6.6 with no scripts what so ever and get a stable and quick device.

It sleeps like a comatosed patient(2% drain over 10 hours) and I've pushed it to the limits to see what i could get, well i got just over 2 days with 5+ hours screen time which obviously i dont need 'couse i got chargers every way i go(office, car and home). So dont over complicate things becouse you got a great kernel here which you are ruining with your mumbo jumbo and then *****in about it.

You know that you got more process power in yor smartphone then all of NASA did in 1960. And they were sending people to the moon while you sending some birds at pigs.
[Galaxy S II Original Android Development] jaher:
Wat is the most stablest version of siyah for wicked rom guys as i have 2.6.6 but some ppl are saying there is.more stable verisons for wicked rom.
[Galaxy S II Original Android Development] poochewer:
I agree completely! That was very good thinking and/or research. Not to mention "VERY INTERESTING"

Thank you:)
[Galaxy S II Original Android Development] eastonfr:
Im on checkrom hd v4. This kernel runs amazing for me. Unplugged phone 5am still going now at 8pm 72% left. Medium use browsing web few texts using gps for sat nav 30 and music 30 mins. For a superphone this is amazing battery life. I dont use any pikachu thunderbolt settings. I use undervolt on gpu and proc. No oc using luzactive govenor. Perhaps you just dont know how to configure kernel to achieve the best battery and performance this phone has ever seen
[Galaxy S II Original Android Development] veyka:
Maybe because some of us enjoy tweaking? That's one of the reasons this site exists!

The kernel works perfectly well without tweaking, but at the same time, its fun to bugger around with scripts, and stoof.

To each there own! :D
[Galaxy S II Original Android Development] fusionjack:
I'm using the one from miuiandroid.com (us?) and yes the latest one 2.1.6 as stated in my signature.

Did you try a clean install? Delete all scripts in init.d folder, wipe cache & dalvik, install MIUI, boot, if it is ok then install siyah?

Don't install any other scripts or apps like setcpu, no-frills, voltage control to narrow it down the problem. There will be some MIUI standard init.d scripts, but that should be ok.

Freeze usually cause by heavily undervolting. Do you by any chance undervolt ur device?
[Galaxy S II Original Android Development] reAly:
hi

somebody many posts before, said he uses 2 different gouvenors, one for display on and one for display off. where can i find that option or which script do i need?

can somebody explain that please? :)

thank you :)
[Galaxy S II Original Android Development] N6666661:
man!!!

EUREKA:D

I was runing 50-1500mHz, luzactive, inc cpu load 95% (that was stupid), pump up and down 1, screen off = MY BIG MISTAKE : I was 7 so 50 mHz in my case...

Reading your post, I have tested inc cpu load 70%, screen off min step 5 (450mHz in my case).

Guess what?! amazing battery in standby and deep sleep now!!!

Thanks a lot!
[Galaxy S II Original Android Development] stevehkim:
It's in the thunderbolt scripts. Which will do the work for you while the screen is off. Just run the scripts and change your governer of choice with setcpu or voltage control. Leave everything else.
[Galaxy S II Original Android Development] reAly:
ok i have installed the thinderbold script, but i can chose only one gouvenor in voltage control, i think tis is the one for screen on. where can i select the one for the screen of? or is this automaticly selected in the script?

thank you when it is a stupid question :)
[Galaxy S II Original Android Development] magarto:
I am using CheckRom RevoHD v4 and Siyah 2.6.6... since the last weeks (in which I have only flashed new siyah kernels when they were released), some times the GPS acquisition stopped working.

I wiped everything (including data) and reinstall rom and kernel and it worked again... today it stopped working again.

Is it a kernel bug?

Could anyone help me?

Thanks!
[Galaxy S II Original Android Development] olifee:
Also CheckRom RevoHD v4, no problems with GPS.

Can you check whether your device clock is correct? I greatly shrank the time to the first GPS-fix using ClockSync-app, it can sync to ~0.1 s precision.

Fixing time is also faster if data connection has been active at least once in the last 2-3 days when GPS was activated (it then downloads A-GPS data which helps for some days before it should be refreshed).

If ClockSync is not an option for you, FasterFix also increases clock precision (just not as much).

To debug your GPS-problems, I can recommend GPS-status app, it shows about all information you can get. So for starters, check how many satellites it can 'see' with the app, check your device clock and report back ;).

After all, kernel should not have anything to do with GPS, it should either work or not work at all. However, we once had a bug in an old Siyah release which caused time-lags (increasing time to first GPS-fix), but that has been fixed long ago...

Good luck!
[Galaxy S II Original Android Development] thunderteaser:
Everything is fine with Siyah 2.6.6 and Thunderbolt! 2.3.6, though I still have troubles with 3G. Everytime I enable data connection, it disconnects after a while or immediately. If I start Foursquare using data connection and GPS, when trying to obtain my position, it disconnects. Is it a MIUI problem, or is there something wrong? :confused:

EDIT: It seems to be a radio problem. I'm running an ICS modem (XXKP8) on MIUI. Either the modem is faulty, or ICS modems on Gingerbread are a bad mix!

Thanks in advance!

P.S.: Thanks pikachu01 for your answer! I'm using Voltage Control to set my scheduler, though I liked PimpMyCPU a lot more!
[Galaxy S II Original Android Development] stevehkim:
im using miui and no data drops whatsoever. maybe try a diff modem?

tweaked - by me

kernel - siyah the og

rom- me you eeee.
[Galaxy S II Original Android Development] tinuz97:
My talking sound is to low when i use this kernel :-( Further it is working for me great.
[Galaxy S II Original Android Development] KurskS:
@Pikachu: Do u know any script to disable fast dormancy so I can use it in MIUI ROM?:D

Sent from my brilliant Viper skinned Apple iPad 2 using the superior Tapatalk Premium
[Galaxy S II Original Android Development] tolis626:
Well,you're welcome. :p
[Galaxy S II Original Android Development] magarto:
Thank you very much for all the information and help :)

Also for the best i9100 kernel :)

I had ClockSync installed and it showed 0.36 s of difference so I synced right now.

If problem persists I will check debug information with GPS status (anyway it drains battery).

The problem is that I have very low signal from sattelites... I will remove my aluminium case also to be sure that it is not the reason.

Thanks again.
[Galaxy S II Original Android Development] sjpn:
I just started using this kernel. Set the speed as 1600 with setcpu. It set lulzactive via auto detect. I used camera zoom fx pro and took 2 successive pictures using ready made filters and it crashed the phone. Any ideas what settings I should try?
[Galaxy S II Original Android Development] xan:
Will adding "sleep 20" to vc script fix the "set on boot issue"? if so expect a fix release tomorrow :)
[Galaxy S II Original Android Development] cmd512:
Yep, otherwise VC's boot settings don't stick. :)
[Galaxy S II Original Android Development] tolis626:
@droidphile

Hey man,that thing with time in state not showing happened again.So I checked if the file is there in the cpufreq directory as you suggested.Well,it's there but it's empty,as expected.I have absolutely no idea what this might be related to though.
[Galaxy S II Original Android Development] eXnikaru:
what`s the best setting for lulzactive app?

Is this setting-pump up step=4 pump down step =1 up sample=10000 down sample 20000

which is from pikachu best?
[Galaxy S II Original Android Development] xan:
Ok - 20 secs delay on boot script loading added. Can it be shorter? like 10 secs? I'm not on samsung rom.. so really cant tell ;p

version 2.9.8r2
[Galaxy S II Original Android Development] Dennys_Santos:
Guys!!!

Where can I read about "Smooth Scaling Parameters"?

echo ??? > /sys/devices/system/cpu/cpu0/cpufreq/smooth_target;

echo ??? > /sys/devices/system/cpu/cpu0/cpufreq/smooth_offset;

echo ??? > /sys/devices/system/cpu/cpu0/cpufreq/smooth_step;

Thanks...

---------- Post added at 09:34 PM ---------- Previous post was at 09:31 PM ----------

I read on the site that the U.S. "Fast Dormancy " is already off by default in the ROM MIUI.
[Galaxy S II Original Android Development] olifee:
No problem, you're welcome :).

Actually, I'm also just a user loving this kernel, the credit (best i9100 kernel) should go to gokhanmoral, he deserves it :).

The aluminium case might really cause some problems. You could check if there is no other (magnetic) metal added somewhere by checking the compass in gps-status, if the needle is big / small and the µT-value is off (i.e., very different from 50) there is also something else apart from aluminium somewhere as part of the case.

I am only using a silicon 'case' here and even have GPS inside my home (although fixes take somewhat longer there and I have to be in a room with big windows, but it works with AGPS-data ^^).

Let's have fun with the best kernel ever ;).
[Galaxy S II Original Android Development] veyka:
Or set the script permissions? or both? ;)
[Galaxy S II Original Android Development] kikoexe:
i dont know if this issue was already raised but i experience lags in music when i wake the phone from deep sleep or even if the phone wakes from deep sleep when receiving sms.. using 2.6.6, stock settings..
[Galaxy S II Original Android Development] AMDPOWERFIST:
Quick question about Siyah v2.6.6

Quick question about Siyah v2.6.6

With the default stock Siyah v2.6.6 does it come with any UV / OC settings?

Does the default stock Siyah v2.6.6 come with an enhanced charging capabilities?

Or are both of these settings manually entered via scripts / applications?

Thanks
[Galaxy S II Original Android Development] atomic339:
Which charging set do you use?

Wysłane z mojego GT-I9100