Governors - I/O - Freq questions - combos - T-Mobile Samsung Galaxy S II SGH-T989

So I have started playing around with those. I searched over google for some awsners but since my brain started bleeding i tought i'd create thread. ( hey I work overnight, I should be sleeping).
So far it looks like this (On CM9 stable with Darkside 6.1)
Prio 100
Screen off 540-192 ON DEMAND
Prio 90
BAT > 122F 756-384 ON DEMAND
Prio 85
Charging ANY 1728 - 1026 BADASS
Prio 82
IN CALL 1080 - 384 ON DEMAND
I/O NOOP
Prio 80
APP CHROME 1512 - 1026 ON DEMAND
I/O NOOP
Battery > 10% 1782 - 1092 BADASS
I/O NOOP
So not sue if the combo of screen on screen off is ok...Also Should i ALWAYS set a I/O Scheduler ??
Thank you for your time

NLPUNITED said:
Need advice on combos for Governors and I/O Schedulers. I searched a bit on google and the forums but did not quite find what i was looking for.
Currently on CM9 and Darkside 6.1
SETCPU:
100
screen off 540-192 ONDEMAND
90
batt> 122f 756-284 ONDEMAND
85
Charging Any 1728-1026 BADASS
82
IN CALL 1080-384 ON DEMANDE I/O NOOP
80
Chrome APP 1512 -1026 ON DEMAND i/o noop
79
Batt > 10% 1728-192 BADASS I/O NOOP
Not sure on when or how to use NOOP. Also, not sure about my screen off/ on combo
Should noop be always ON ? Looking for Good battery life since mostly texting and fooling around the phone. Games at times.
Click to expand...
Click to collapse
Your setup looks good. Not sure about you Chrome profile, why have the min so high? I like having my screen off at that exact range, exept on conservative As for the i/o scheduler, it depends on the kernel. Im using TDJ;s also, and he recommended noop on his, so thats what I use
Setcpu
100
Screen off 540-192 conservative
99
In Call 1188-192 badass
98
Battery <=15% 1026-192 badass
97
Screen on 1512-192 badass
Battery lasts all day, no juicedefender, on AOKP, lets me switch to 2G on screen off.
I play games and xda app, get an easy 4 hours screen time

LoopDoGG79 said:
Your setup looks good. Not sure about you Chrome profile, why have the min so high? I like having my screen off at that exact range, exept on conservative As for the i/o scheduler, it depends on the kernel. Im using TDJ;s also, and he recommended noop on his, so thats what I use
Setcpu
100
Screen off 540-192 conservative
99
In Call 1188-192 badass
98
Battery <=15% 1026-192 badass
97
Screen on 1512-192 badass
Battery lasts all day, no juicedefender, on AOKP, lets me switch to 2G on screen off.
I play games and xda app, get an easy 4 hours screen time
Click to expand...
Click to collapse
Will try it with conservative on Screen Off...Tought i read somewere it's better to keep it on Demand so you dont have bugs when going on ?

NLPUNITED said:
Will try it with conservative on Screen Off...Tought i read somewere it's better to keep it on Demand so you dont have bugs when going on ?
Click to expand...
Click to collapse
On AOKP ICS, havent noticed any bugs due or SOD (Sleep of Death) I get an easy 20hrs batt life with moderate use

So far 1:30 screen up time, played games and such. Still at 60% Bat. Prety damn good and i use a screen lock pattern wich must drain a bit more.

Related

What is the best setting for SetCpu?

Guys! What is the best setting for Set Cpu? I need to conserve battery. My battery lasts about 12 hours. Im using a Reflex S 2.04 rom but i shifted to Leedroid 2.4.1. My settings are 768 On demand and 245 max 245 min on demand for powersave.
What is smart ass? How does it affect the system?
On SetCpu, I run overclocked 1200 till under 80%
Then about 80
700 at 70% battery
600 at 50%
I don't wish to run lower, as the desire gets a little wonky below 500mhz
3 profiles. I can get 3 days battery
I use no frills CPU - oc 1114, ondemand governor 245-1114.
Get about 12 he's heavy use, up to 2 days light. Today I have done 3+ hrs train journey with music, browsing and SMS, checked mail, now hanging about on this forum! 41% left.
All other governors are ****. Just use ondemand.
Im set at 128-1190 ondemand.
Sent from CM7
Meaple said:
All other governors are ****. Just use ondemand.
Click to expand...
Click to collapse
Why?
I use smartass @128-768 Mhz.
remember to use screen off feature (saves a lot of battery)
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
MatDrOiD said:
Why?
I use smartass @128-768 Mhz.
Click to expand...
Click to collapse
Because they don't work well. When you need CPU power they tend to lag and it takes that little extra longer which does my head in. Whether it's just me I don't know but it is so annoying. I have noticed it when playing games like RoboDefence. That's why I stick to ondemand because it actually works.
for the sleep off what is the best setting? screen off 245 max 245 min on demand? or 245 max 128min smart ass?
With smartass you do not have to set a profile for screen off. Smartass uses automatically the min cpu-frequency you set. So if you set smartass for screen off, you have two "screen off"-profiles. I think that could cause problems. You should set the screen-off-profile on [email protected] to avoid waking up problems, which can occur with this min 128 and max 245 for screen off-profile.
Meaple said:
Because they don't work well. When you need CPU power they tend to lag and it takes that little extra longer which does my head in. Whether it's just me I don't know but it is so annoying. I have noticed it when playing games like RoboDefence. That's why I stick to ondemand because it actually works.
Click to expand...
Click to collapse
+1 Agree totally
Ondemand is the only governor which doesnt make my phone lag.
westleydan said:
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
You can find this in the wiki...
westleydan said:
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
From SetCPU-Website:
ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.
userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Click to expand...
Click to collapse
smartass governor – is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works – by taking over the idle loop – is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the “old” minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 352Mhz (or if your min frequency is higher than 352 – why?! – it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Click to expand...
Click to collapse
Source: http://www.ziggy471.com/2010/11/07/smartass-governor-info/

Undervolting - good idea or not?

I'm wondering if anyone's undervolted and to what values.
I'm also wondering waht the deafult values are and if they change per kernel.
Is there a way to disable SetCPUs undervolting settings?
Has anyone improved battery life with profiles? On the Eris this was the only way to get usable battery life.
Or not. I gave up undervolting after I actually compared battery life at stock values vs undervolted (on my old phone, sgs4g) and discovered it does nothing for battery life.
Edit: undervolting "might" marginally increase standby battery life, but considering how good this phone already does... it certainly won't increase actual screen on usage.
Sent from my Galaxy Nexus using xda premium
Depends how low you under volt. Got more battery life, maybe about an hour, after finding optimal battery life on my gfs Gnex.
If you don't under volt correctly, of course it won't improve battery life.
From my sexy white, Nocturnaled HTC One X
If you're not overly comfortable with undervolting, then using one of the many kernels with Smart Reflex will do a mild undervolt for you. If you are comfortable, then the only way to find numbers good for your phone is to try and test. I tweaked mine down to the point that I was occasionally getting hot boots when the screen was off and media was playing. Tweaking the numbers back up added the needed stability. Even little things like kernel or ROM revisions can change what voltage is or isn't stable. Another example is that when I updated my Jellybro CM10 version the other night, along with updating leankernel from 4.1.0exp3 to 4.2.0, I had to increase a few of my voltages to avoid hot boots.
Just for example numbers, here are mine:
Code:
1350MHz -- 1200mV
1200MHz -- 1150mV
920MHz -- 1050mV
700MHz -- 950mV
350MHz -- 825mV
These numbers will vary from device to device and even between ROM/kernel combinations, so don't use them as hard fact.
Thanks. On a phone like this it might not make a huge difference but on the Eris (Where stock battery life could sometimes be 6 hours if you actually used your phone) an undervolted kernel with setcpu could turn those 6 ours into 48.
Thanks Cilraaz, I'll try those voltages out and benchmark a bit to see if they're stable for my system.
Two things I can say for sure:
1. you will have very limit battery gain by undervolting with Gnex, no matter how low you try.
2. undervolting will bring some stable issue if you get too low, like lose signal and reboot.
I am using Kernel Franco GPU 384 Stock rom on my 4.1.1 and did undervolting
Current configuration:
384Mhz
950mv
------------
729Mhz
1050mv
-----------
1036mhz
1125mv
----------
1228mhz
1275mv
-------------
I did not change the frequencies of overclocking, because I'm not using them.
I felt an improvement in battery consumption unless the unit is heating up.
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
I've read many times undervolting isn't worth it.
Hungry Man said:
Just curious - what kind of profiles are you using? I have a "Screen off" that's 350min and 700max. I figure that's fast enough f someone calls me.
Click to expand...
Click to collapse
I'm using the following with SetCPU: default (1350MHz-350MHz), charging, CPU temp > 64, and battery < 35%.
If you're using a kernel and governor that support hotplug, then you likely don't want to use a screen off profile. The combination of the two can tend to cause sleep-of-death or hot boots.
I Am Marino said:
I've read many times undervolting isn't worth it.
Click to expand...
Click to collapse
Most people don't want to spend the time to do it right.
I'm actually not used to the new kernels. I haven't messed with my eris in about a year and back them there was "smartass, on demand, performance," and some other one that clocked down instead of up
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Hungry Man said:
Can you explain th escreen off profile causing issues? I don't even know what hotplug is lol I've been out of Android for a long time.
Click to expand...
Click to collapse
Hotplug disables one of the CPU cores when the screen is off. Some governors, like hotplugx, will also attempt to disable a CPU core during periods of low CPU usage. For some reason, this combined with a screen off profile can cause some problems. I assume it's because of the "screen-off-max-freq" that Imoseyon mentions in the quote below.
Personally, I prefer the interactivex governor with leankernel by Imoseyon. From his kernel thread:
With interactiveX V2 (for gnexus), things are a bit different, since gnexus has built-in support for screen-off-max-freq for all its governors. I took the new interactive code in gnexus, added early_suspend support (screen off/on trigger), and then added logic to the code so the governor uses the phone's built-in hotplugging capability to turn off cpu1 when screen is off (and then turn it back on when screen comes back on). Cpu1 goes offline entirely - no idle, no sleep.
Click to expand...
Click to collapse
I think undervolting helps - my phone is running 728 - 1228 using the interactive governor, with voltages of 600 mV, 700 mV, and 800 mV (728 MHz, 1036 MHz, 1228 MHz respectively) and I haven't had any issues so far. I know there are some reports that say undervolting doesn't help much, but those are when people undervolt by like 50 mV, whereas here I'm going like 400 mV under lol. (Yes, smart reflex is off).
Thanks Cilraaz. Good to know.
So turning the screen-off profile could improve things? Honestly, my system does fine at 350mhz with screen off. Turning a core entirely off would probably help though.
If I use hotplugx governor that would disable one core when the screens off, right?
Hungry Man said:
If I use hotplugx governor that would disable one core when the screens off, right?
Click to expand...
Click to collapse
Hotplugx will disable a core when the screen is off or when there is low system load. Depending on your kernel/governor choice, other governors may do it also. On leankernel, for instance, interactivex will disable a core when the screen is off, but not on low system load.
Ok, thank you.
I haven't done any comparisons of before/ after since I undervolted/ underclocked first thing. But I was browsing for hours while listening to music while talking to a friend with GTalk. talked for about 1.5 hours with someone, Left it on overnight (10 hours), woke up, used it to talk (voice to text) to someone via GTalk, and it's 3:25PM right now and I still have a fair amount of battery life left.
I'd heard mixed things about the battery on this so I'm happy.
My voltages:
1650: 1300
1520: 1250
1350: 1175:
1200: 1125
920: 1000
700: 925
350: 900
I stress tested each one without a crash.

SetCPU Profiles

A couple weeks ago, I installed SetCPU to help with battery life. It did great! But, I didn't see the amazing improvement that I thought I would.
So, I did some research and found out about Profiles. Profiles are settings that you can make that will be applied when certain conditions are met.
Below are the profiles that I have created on my Nitro. I have seen 11 to 12 hours of medium use from my phone with these settings. If you have any suggestions on changes, please let me know. I'd like to find the absolute best settings and share them for everybody.
Profile Name: Screen Off
Conditions: Screen Off
CPU Max: 384Mhz
CPU Min: 192Mhz
Governor: powersave
Priority: 90, Exclusive
Profile Name: Charging Any
Conditions: Charging Any
CPU Max: 1512Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 85, Exclusive
Profile Name: In Call
Conditions: In Call
CPU Max: 810Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 80, Exclusive
Profile Name: Battery <= 10%
Conditions: Battery <= 10%
CPU Max: 594Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 75, Exclusive
Profile Name: Battery <= 25%
Conditions: Battery <= 25%
CPU Max: 972Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 70, Exclusive
Profile Name: Battery <= 50%
Conditions: Battery <= 50%
CPU Max: 1242Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 65, Exclusive
Profile Name: Battery <= 75%
Conditions: Battery <= 75%
CPU Max: 1350Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 60, Exclusive
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
noemtfj said:
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
Click to expand...
Click to collapse
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
drumist said:
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
Click to expand...
Click to collapse
I don't do much with my phone in the way of heavy gaming or video watching. I am going off of the last couple days of having SetCPU enabled and getting almost 15 hours of medium use out of my phone.
noemtfj said:
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
Click to expand...
Click to collapse
It was an arbitrary number.
Does anybody find this kind of post meant to make peoples phones better helpful? It seems like every time I post something that I personally have found to make the Nitro even more awesome gets a tone of comments basically telling me that none of it will ever work. I'm sure that if people would just try the things I post, they would be happy.
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
scott0 said:
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
Click to expand...
Click to collapse
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
mattman86 said:
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
Click to expand...
Click to collapse
yeah, i guess it's diff for everybody, just like the roms eh, some get great batt perf on 1 and sucky on another and someone has exactly opposite.
anyhoo, my jd ultimate settings are
Status
advanced profile
graphical notification->quickbox
Controls
wifi enabled->wifi preferred
brightness min 20% mid 45% max 150% (gotta get the most of this screen in the sunlight!)
light sensor fast
cpu min 192 mid 918 max 1512
governor ondemand
schedules
none, i also turned off night schedule as i have the phone plugged in during those hours.
triggers
Apps enabled
Configure->configure apps allow on during screen off->pandora
Location enabled
****************i find it makes a world of difference to give jd =>3 days to get it all right.
make sure setcpu is out of the way as well.

Best io scheduler for battery?

What is the best io scheduler battery wise?
Sent from my SGH-T999 using xda premium
Don't know if "best" threads are allowed, but in either case, I prefer using Zen or SIO for battery and Deadline and CFQ for performance.
Hope that helps.
Seriously i dont play with the scheduler for maximizing my battery, i've downloaded CPU Tuner because theres is Proliles options. With theses profiles you can make the frequency drop to 594 mhz ( i stay safe ) or even lower when the trigger ''Screen Off'' is activated. AND THAT SAVE JUICE A LOT. I've make a test this morning and i was suprise, i've lost 8 % in 45 minutes with heavy utilisation with max brightness GPS BlueTooth ( everything that suck like a B*** juice ). So far this is the best way to save battery, a lot of tweaking and configuration but you should give a try ! :laugh:
PS : Everything on stock & rooted And Also dont forget to clean wipe your phone every 3-6 month with a battery draining ! (i've also gain 25 % back of my little batt. by doing this ! )

[FREQUENCY] Saving Battery Life of your SGY![UPDATED]

Here are few Settings for suitable Battery Life
These settings can be implemented using No-Frills CPU Control or any alternative!
LIGHT USAGE:
GOVERNOR: SMARTASSV2
MIN: 156Mhz
MAX: 624Mhz
I/O: NOOP
GET AS MUCH AS 3-4 DAYS OF BATTERY LIFE in a SINGLE CHARGE
AVERAGE USAGE:
GOV: ONDEMAND
MIN: 156Mhz
MAX: 832Mhz
I/O: NOOP
GET AS MUCH AS 1-2 DAYS of BATTERY LIFE in a SINGLE CHARGE
HIGH USAGE:
GOV: LIONHEART
MIN: 312Mhz
MAX: 832Mhz
I/O: NOOP
GET AS MUCH AS 1/2-1 DAY of BATTERY LIFE in a SINGLE CHARGE
VERY HIGH USAGE:
GOV: LIONHEART
MIN: 624Mhz
MAX: 832Mhz
I/O: NOOP
GET AS MUCH AS 3-5 HOURS of BATTERY LIFE in a SINGLE CHARGE
A THANKS is appreciated
Re: [FREQUENCY] Saving Battery Life of your SGY!
i recommand Lineheart
Want To Ask Question? Ask Here
Thanks,
TechnoSavie
Performance governor will never let your frequency go lower than 832mhz so setting a min frequency is useless
Powersave will never let it go higher than 156mhz so read above
Bcm21553 will only use 312mhz and 832mhz...
Sio is slightly better than Noop
arnavsynergy said:
Here are few Settings for suitable Battery Life
These settings can be implemented using No-Frills CPU Control or any alternative!
LIGHT USAGE:
GOVERNOR: SMARTASSV2/POWERSAVE
MIN: 156Mhz
MAX: 624Mhz
I/O: NOOP
GET AS MUCH AS 3-4 DAYS OF BATTERY LIFE in a SINGLE CHARGE
AVERAGE USAGE:
GOV: ONDEMAND/BCM21553
MIN: 1562Mhz
MAX: 832Mhz
I/O: NOOP
GET AS MUCH AS 1-2 DAYS of BATTERY LIFE in a SINGLE CHARGE
HIGH USAGE:
GOV: PERFORMANCE
MIN: 312Mhz
MAX: 832Mhz
I/O: NOOP
GET AS MUCH AS 1/2-1 DAY of BATTERY LIFE in a SINGLE CHARGE
VERY HIGH USAGE:
GOV: PERFORMANCE
MIN: 624Mhz
MAX: 832Mhz
I/O: NOOP
GET AS MUCH AS 3-5 HOURS of BATTERY LIFE in a SINGLE CHARGE
A THANKS is appreciated
Click to expand...
Click to collapse
AVERAGE USAGE:
GOV: ONDEMAND/BCM21553
MIN: 1562Mhz
MAX: 832Mhz
I/O: NOOP
GET AS MUCH AS 1-2 DAYS of BATTERY LIFE in a SINGLE CHARGE
1562? or just typo?
Also like technosavie, I use lionheart. Try it :good:
booterbotter said:
AVERAGE USAGE:
GOV: ONDEMAND/BCM21553
MIN: 1562Mhz
MAX: 832Mhz
I/O: NOOP
GET AS MUCH AS 1-2 DAYS of BATTERY LIFE in a SINGLE CHARGE
1562? or just typo?
Also like technosavie, I use lionheart. Try it :good:
Click to expand...
Click to collapse
I have updated it... Sorry for the 1562Mhz... 156Mhz it is Srry! And I updated it just now... PERFORMANCE replaced with LIONHEART!
Reply Someone
Maybe some examples regarding the USAGE like Texting, Music or Data mode something like that i think
iMaker said:
Maybe some examples regarding the USAGE like Texting, Music or Data mode something like that i think
Click to expand...
Click to collapse
Updating
Using stock rom with hell_fusion kernel. Freq at 624-312mhz, ondemand+sio gives me at least a day and a half.
Wifi turned on, playing games once in a while, music for a bit too often, and a lot of facebook.
Sent from my GT-S5360 using xda app-developers app
These settings were for Savie #1, #54 and percy #1 hell fusion #50
Sent from my GT-S5360 using Tapatalk 2
[Q]
What is the recommended kernel? Is hell's fusion #50 good for all needs, or kuro's kernel better?
Also is Merruk Kernel v2.0 (1.248GHz) stable to be used for everyday apps?
SaketJoshi said:
What is the recommended kernel? Is hell's fusion #50 good for all needs, or kuro's kernel better?
Also is Merruk Kernel v2.0 (1.248GHz) stable to be used for everyday apps?
Click to expand...
Click to collapse
I used Merruk but it occurs a fex probs sometimes... For some needs you need to have stock recovery not cwm soSaviekernel or Kuro is highly recommended
death_sinker said:
I used Merruk but it occurs a fex probs sometimes... For some needs you need to have stock recovery not cwm soSaviekernel or Kuro is highly recommended
Click to expand...
Click to collapse
Kuro's kernel is definitely a keeper! Its very light.
Sent from my GT-S5360 using xda app-developers app
kitbeks said:
Kuro's kernel is definitely a keeper! Its very light.
Sent from my GT-S5360 using xda app-developers app
Click to expand...
Click to collapse
Yeah!
Bcm + cfq is good.
Bcm + noop is slightly smoother, but eats battery.
Well, for battery, you can't go wrong with powersave and sio.
As for me, though, i use scary+deadline. Seemed pretty balanced for me.
Galaxy Y lover, Galaxy Note fan. Press thanks if i helped!
what setting will be good for browsing with opera mini for good battery life
Abhii1902 said:
what setting will be good for browsing with opera mini for good battery life
Click to expand...
Click to collapse
I dont know
Interesting. Thanks.

Categories

Resources