Is there a stable 1.3Ghz OC kernel because i tried FuguMod 2.2 BE but my phone overheated.
RafayelG said:
Is there a stable 1.3Ghz OC kernel because i tried FuguMod 2.2 BE but my phone overheated.
Click to expand...
Click to collapse
Except 2.2 FuguMod, No
Maybe you kept 1.3Ghz continously...
Try using OnDemand or Conservative Scaling and profiles of screen off and stuff..
dharamg3 said:
Except 2.2 FuguMod, No
Maybe you kept 1.3Ghz continously...
Try using OnDemand or Conservative Scaling and profiles of screen off and stuff..
Click to expand...
Click to collapse
i just saw one at Kyrillos' Rom Here changelog of V5.0 and 4.1 but i can't find them on Marcellusbe's thread
RafayelG said:
i just saw one at Kyrillos' Rom Here changelog of V5.0 and 4.1 but i can't find them on Marcellusbe's thread
Click to expand...
Click to collapse
Ohh...those 1300MHz are Alpha kernels and full of bugs..
I've tested it...and i tell you, you dont want those...
better to try using Profiles of SetCPU with 2.2BE
dharamg3 said:
Ohh...those 1300MHz are Alpha kernels and full of bugs..
I've tested it...and i tell you, you dont want those...
better to try using Profiles of SetCPU with 2.2BE
Click to expand...
Click to collapse
do you got any sugestions for profiles?
SetCPU:
1) Max: 1300 Min: 166 Scaling: Ondemand Set on Boot:Tick
2) Profiles: Enable
Battery < 50% Max:667 Min:166 Scaling: Ondemand Priority: 80
Screen Off Max:222 Min:166 Scaling: Ondemand Priorty: 100
Time(Set the time when you are usually asleep) Max: 333 Min: 166 Scaling: Ondemand Priority: 90
3) Advanced: Set on boot
Up Threshold: 90
PowerSave Bias: 400
dharamg3 said:
SetCPU:
1) Max: 1300 Min: 166 Scaling: Ondemand Set on Boot:Tick
2) Profiles: Enable
Battery < 50% Max:667 Min:166 Scaling: Ondemand Priority: 80
Screen Off Max:222 Min:166 Scaling: Ondemand Priorty: 100
Time(Set the time when you are usually asleep) Max: 333 Min: 166 Scaling: Ondemand Priority: 90
3) Advanced: Set on boot
Up Threshold: 90
PowerSave Bias: 400
Click to expand...
Click to collapse
trying it now will report tomorrow
Im looking for stable undervolt settings I have currently mine set at
1600 Mhz - 1400 Mv
1400 " - 1300 "
1200 " - 1250 "
1000 " - 1175 "
800 " - 1050 "
500 " 950 "
200 " - 850 "
100 " - 825 "
My settings are stable but maybe someone can put out where I can still undervolt and retaining stability.
Im using stock + Siyah Kernel.
I'm not trying to be rude, but it's a bit useless since not every devices can handle the same settings...
And of course you can still undervolt. You will find YOUR best settings when you're at the lowest values and your phone is still stable. If you're going too low, you'll have to reboot the phone and set the voltage a bit higher.
But if you want an idea, mine is running rock solid with these settings :
100MHz @ 825mV
200MHz @ 825mV
500MHz @ 850mV
800MHz @ 950mV
1000MHz @ 1050mV
1200MHz @ 1150mV
I'm also on stock KI8 + Siyah 2.0b6
Keep trying by 25mV
Siyah Kernel
Cognition 1.5.1
100Mhz @ 775mV
200Mhz @ 800mV
500Mhz @ 825mV
800Mhz @ 950mV
1000Mhz @ 1050mV
1200Mhz @ 1150mV
1400Mhz @ 1275mV
1600Mhz @ 1350mV
What exactly constitutes stable? Half an hour on a stability test? 1 hour? 2 hours? a month?
jayquinten510 said:
What exactly constitutes stable? Half an hour on a stability test? 1 hour? 2 hours? a month?
Click to expand...
Click to collapse
Stability Test is crap. Play a game for an hour to see if it's stable.
ithehappy said:
Stability Test is crap. Play a game for an hour to see if it's stable.
Click to expand...
Click to collapse
Haha, normally I would, but my HSC exams start tomorrow :/ Last school exams ever! Hopefully will get me into uni. I was just running stability tests in the background when I was studying, but maybe I will leave it till after the HSC.
skuizy said:
I'm not trying to be rude, but it's a bit useless since not every devices can handle the same settings...
And of course you can still undervolt. You will find YOUR best settings when you're at the lowest values and your phone is still stable. If you're going too low, you'll have to reboot the phone and set the voltage a bit higher.
But if you want an idea, mine is running rock solid with these settings :
100MHz @ 825mV
200MHz @ 825mV
500MHz @ 850mV
800MHz @ 950mV
1000MHz @ 1050mV
1200MHz @ 1150mV
I'm also on stock KI8 + Siyah 2.0b6
Click to expand...
Click to collapse
Good setting....i'm using without problem from 3 days.
Question:
Do you set governor from 100 to 1600mhz or standard 1200?
ithehappy said:
Stability Test is crap. Play a game for an hour to see if it's stable.
Click to expand...
Click to collapse
CPU stress test in setcpu is a goodone. USing the two cores completely for testing, most of the games make use of GPU a lot and some CPU, so playing games alone wont help you in testing the stability.
Spreadsheet of Governor Power Use
BENCHMARK DATA
Summary
Out of the five most popular governors (ondemand, conservative, smartassV2, lazy, and lulzactiveV2) which one can save the most battery?
Total power use is calculated from the mA drain at the frequency x the %age of time spent at that frequency. mA drain figures available here.
Best Power Saving Governors
Best for Screen ON: Ondemand
Best Screen ON + performance: SmartassV2
- Good choice if you need a performance governor with some power saving
- SmartassV2 is also the winner of the governor benchmark: here.
What about when my Screen is OFF?
Best Governor for Screen OFF
Without Deep Idle: Same as Screen ON > Ondemand
With Deep Idle: Any governor...
...now it get's technical...
...Why 'any'? If you look at the spreadsheet, on average, with music ON and the screen OFF, the difference between the best (smartassV2) and worst drain (lazy) is 0.05mA (a tiny amount). Harrb already did a 10 hour test to establish how much each governor drains the battery while using deep idle:
Harbb's spreadsheet
Here's two of Harbb's results (phone's own stats for battery drain with matr1x):
- 23% - Lazy with DI
- 15% - SmartassV2 with DI (35% more efficient)
And my results (mA drain using matr1x):
- 0.30mA - Lazy with DI
- 0.24mA - SmartassV2 with DI (20% more efficient)
Harbb's result is the most reliable, as my original battery drain mA readings were all somewhat approximated due to the difficulties of reading accurately off a small scale on the analogue amp meter, especially when the scale is logarithmic and the mA drain is in the lower register. This means, if I assume my Smartass mA reading is correct, then my Lazy reading should be 0.405mA
While playing music, with the screen off, with DI enabled,
over a period of 1 hour:
a constant drain of 0.240mA = 864mA
a constant drain of 0.405mA = 1458mA
So choosing SmartassV2 over Lazy would prevent about 600mA being wasted in one hour. To put this in context, that is enough to power your screen for 3 seconds (assuming a drain of 200mA).
Since it will take about 3 seconds to change your governor, in practice, it would be a waste of effort to bother. Pick your preferred governor for screen ON, and don't worry about what happens while the screen is off (again, only if you have deep idle. If you don't, but want some power savings with the screen off, choose ondemand).
F.A.Q.
[Q] But Harbb's data clearly shows that the battery drain is much better under smartassV2. How can you say governor choice doesn't make a difference?
[A] Harbb's result is an 8% benefit over ten hours, so in one hour it's a 0.8% benefit. It's not a very practical amount.
For more battery saving tips, see my battery drain thread: here.
Where did the other benchmarks go?
Battery Drain Benchmarks: this thread
All ICS ROM Benchmarks: this thread
Kernel Features and Benchmarks: this thread
CPU Governors and I/O Schedulers: this thread
These tests were based on an the procedure first used by XDA user glennkaonang. Credit and thanks to Glenn. Thanks to r_data, mathkid95, steve.garon, and eugene373 for their kernels.
Conservative is not the Best
When the screen is ON, i.e. the phone is in active use. Generally Conservative does not save power. This is because most developers have included a tweaked version of conservative that keeps the frequency at its highest state for longer to improve the responsiveness.
There is one exception where conservative saves more power than other governors, and that is when the screen is off, music is on, deep idle is on, and this only applies specifically to Air Kernel. However, we are talking about a tiny amount of power (for more detail, see the first post.)
PLEASE NOTE: Steve Garon does not include deep idle, but is working on it, neither does Eugene, but I've asked him to consider it. For these two kernels, if you are listening to music with the screen off, currently, the best power saving governor is Ondemand.
Governor Parameters per Kernel
SG-NS-ICS (11th FEB TEST VERSION)
-Conservative
Sampling Rate: 40000
Up Threshold: 80
Down Threshold: 20
Ignore Nice Load: 0
Freq Step: 5
Sampling down factor: 1
-Ondemand
Sampling Rate: 40000
Up Threshold: 95
Ignore Nice Load: 0 (settable in SetCPU)
Powersave Bias: 0
Sampling down factor: 1
-SmartassV2
Awake ideal freq: 800000
Sleep ideal freq: 100000
Sleep wakeup freq: 99999999
Min CPU load: 25
Max CPU load: 50
Ramp down step: 256000
Ramp up step: 256000
Down rate: 99000
Up rate: 48000
-LulzactiveV2
Inc CPU load: 60
Pump up step: 1
Pump down step: 1
Screen off min step: 3 @400
Up sample time: 20000
Down sample time: 40000
MAT1X v17.0
-Conservative
Sampling Rate: 40000
Up Threshold: 80
Down Threshold: 20
Ignore Nice Load: 0
Freq Step: 5
Sampling down factor: 1
-Ondemand
Sampling Rate: 40000
Up Threshold: 95
Ignore Nice Load: 0 (settable in SetCPU)
Powersave Bias: 0
Sampling down factor: 1
-SmartassV2
Awake ideal freq: 768000
Sleep ideal freq: 245000
Sleep wakeup freq: 99999999
Min CPU load: 25
Max CPU load: 50
Ramp down step: 256000
Ramp up step: 256000
Down rate: 99000
Up rate: 48000
-LulzactiveV2
Inc CPU load: 60
Pump up step: 1
Pump down step: 1
Screen off min step: 5 @400
Up sample time: 20000
Down sample time: 40000
ICUP SPEEDY-7
-Conservative
Sampling Rate: 39062
Up Threshold: 70
Down Threshold: 30
Ignore Nice Load: 0
Freq Step: 5
Sampling down factor: 1
-Ondemand
Sampling Rate: 30000
Up Threshold: 95
Ignore Nice Load: 0 (settable in SetCPU)
Powersave Bias: 0
Sampling down factor: 1
-SmartassV2
Awake ideal freq: 800000
Sleep ideal freq: 100000
Sleep wakeup freq: 99999999
Min CPU load: 25
Max CPU load: 50
Ramp down step: 256000
Ramp up step: 256000
Down rate: 99000
Up rate: 48000
-LulzactiveV2 (not settable in NSTools, checked /sys/devices/system/cpu/cpufreq/lulzactive/)
Inc CPU load: 90
Pump up step: 4
Pump down step: 1
Screen off min step: 6 @400
Up sample time: 10000
Down sample time: 40000
AIR KERNEL 3.0 (TEST VERSION)
-Conservative
Sampling Rate: 20000
Up Threshold: 60
Down Threshold: 20
Ignore Nice Load: 0
Freq Step: 5
Sampling down factor: 1
-Ondemand
Sampling Rate: 40000
Up Threshold: 95
Ignore Nice Load: 0 (settable in SetCPU)
Powersave Bias: 0
Sampling down factor: 10
-SmartassV2
Awake ideal freq: 800000
Sleep ideal freq: 100000
Sleep wakeup freq: 99999999
Min CPU load: 25
Max CPU load: 50
Ramp down step: 256000
Ramp up step: 256000
Down rate: 99000
Up rate: 48000
-LulzactiveV2
Inc CPU load: 60
Pump up step: 1
Pump down step: 1
Screen off min step: 5 @400
Up sample time: 20000
Down sample time: 40000
The I/O Scheduler Selections
I selected the likely/proven best I/O scheduler for each kernel and governor combination, based on my previous work here: http://goo.gl/iJXWI
-SG-NS-ICS and Matr1x
Conservative: cfq
Ondemand: noop
SmartassV2: noop
LulzactiveV2: deadline
Lazy: deadline
For these two it's a little different in places:
-ICUP Speedy-7
Conservative: cfq
Ondemand: deadline*
SmartassV2: deadline*
LulzactiveV2: cfq*
Lazy: deadline
-Air Kernel
Conservative: deadline*
Ondemand: noop
SmartassV2: sio*
LulzactiveV2: noop*
Lazy: deadline
I've emboldened and marked with an * where the differences are.
UPDATE: Summary now includes more detail.
I was unable to complete the necessary details and caveats when I first opened the thread as I desperately needed sleep! Hopefully someone can check over my conclusions and make sure they all add up.
bedalus said:
UPDATE: Summary now includes more detail.
I was unable to complete the necessary details and caveats when I first opened the thread as I desperately needed sleep! Hopefully someone can check over my conclusions and make sure they all add up.
Click to expand...
Click to collapse
Awesome Benchmark again bedalus. Very instructive
I would add these points to the conclusions:
- There is a big difference in governors power consumption when screen is on (more than 10 mA between the best and the worst against a small 0.05 mA difference when screen is off)
- Conservative is the worst governor for screen on usage according to the benchmarks (Taking this point with reserves because conservative was tweaked by kernel developers).
- If we have a high "screen on" usage, onDemand will save us so much power
- If we have a low "screen on" usage, it should be better using SmartassV2 and have the best performance for the little time we use the phone
Waiting for your feedback on this bedalus.
Bedalus is loving benchmarking too much that sometimes, he tries to benchmark his benchmarks
tchaari said:
Awesome Benchmark again bedalus. Very instructive
I would add these points to the conclusions:
- There is a big difference in governors power consumption when screen is on (more than 10 mA between the best and the worst against a small 0.05 mA difference when screen is off)
- Conservative is the worst governor for screen on usage according to the benchmarks (Taking this point with reserves because conservative was tweaked by kernel developers).
- If we have a high "screen on" usage, onDemand will save us so much power
- If we have a low "screen on" usage, it should be better using SmartassV2 and have the best performance for the little time we use the phone
Click to expand...
Click to collapse
0.05mA difference: good point. I should probably mention that in the OP.
Yeah, conservative sucked pretty badly on all four of the kernels. Weird.
For me, all I do now is use my phone to check XDA, and I don't use it with the screen off, so I can save power with ondemand. But smartassV2 is provides a very smooth experience. What do I want more? Battery life or smoothness? Hmm... decisions, decisions...
EDIT: Just noticed your benchmark benchmark idea. Only if I am not sleeping.
bedalus said:
0.05mA difference: good point. I should probably mention that in the OP.
Click to expand...
Click to collapse
If you found that the last two points are useful, can you also integrate them in the OP too?
bedalus said:
Yeah, conservative sucked pretty badly on all four of the kernels. Weird
Click to expand...
Click to collapse
Yes it was a surprise to me too but when joining your benchmark results and the theoretical basics of conservative, it all makes sense. Conservative is taking too much time to compute a task (scaling up slowly). It also scales down too slowly when finishing. This is noticeable especially in discontinued use like browsing.
bedalus said:
For me, all I do now is use my phone to check XDA, and I don't use it with the screen off, so I can save power with ondemand. But smartassV2 is provides a very smooth experience. What do I want more? Battery life or smoothness? Hmm... decisions, decisions...
Click to expand...
Click to collapse
I don't think that you can "feel" the performance difference between ondemand and smartassV2 in such tasks. it should be better to stick to ondemand in this case I think
Yeah, testing ondemand now, back on slim ics, feels the same as smartass.
I'll look at the OP tomorrow, early night for me today.
kernels ; battery ; ROM ; gov/sched
bedalus said:
Yeah, testing ondemand now, back on slim ics, feels the same as smartass.
I'll look at the OP tomorrow, early night for me today.
Click to expand...
Click to collapse
I hope you will sleep smoothly now that this benchmark is finished
Can you indicate what schedulers you use for each of the governors? In my experience schedulers also have an effect to battery life so it'd be good to see whether they're the same or different.
nice work.. AGAIN
so this explains why im happiest with ondemand.
deetailed said:
Can you indicate what schedulers you use for each of the governors? In my experience schedulers also have an effect to battery life so it'd be good to see whether they're the same or different.
Click to expand...
Click to collapse
You could visit bedalus' other benchmark thread http://forum.xda-developers.com/showthread.php?t=1478418&page=1 and see which fits your taste best.
Anyway, great job on this new benchmark thread, bedalus.
I can't believe that you would actually go further on this.
Looking at your results, the best for me would be ondemand.
I rarely used my phone, only for messaging and XDA-ing , so most of the time the screen is off.
And as tchaari said, I couldn't see any difference between ondemand and smartassV2 in terms of performance.
Once again, thanks bedalus
Frankly, I thought everything that could be benchmarked already was. However, this data proves even more useful! Thanks, bedalus.
Now there is nothing left to tweak on my phone!
AeroEchelon said:
Frankly, I thought everything that could be benchmarked already was. However, this data proves even more useful! Thanks, bedalus.
Now there is nothing left to tweak on my phone!
Click to expand...
Click to collapse
There is ALWAYS more to tweak on our phones
Good work bedalus, your lack of sleep truly amazes me. I think we can enhance this a bit more by messing around a little with modified conservatives though. It shouldn't be very difficult at all to scale it down far quicker. I'm doing a couple of usage tests with various conservative settings and will let you know if i get any setups that may fit the bill.
As we know, conservative can easily give better performance than ondemand if told to, but i reckon we can get the best of both worlds. Does anyone know where i'd be looking to find the defaults of each governor in the kernel source? Saves me kernel crackflashing.
deetailed said:
Can you indicate what schedulers you use for each of the governors? In my experience schedulers also have an effect to battery life so it'd be good to see whether they're the same or different.
Click to expand...
Click to collapse
To save me trying to copy and paste on my phone this early on the morning, just follow the link below to gov/sched and you'll see a summary in the first post about which scheduler goes best with which governor, e.g. ondemand and noop.
kernels ; battery ; ROM ; gov/sched
simms22 said:
nice work.. AGAIN
so this explains why im happiest with ondemand.
Click to expand...
Click to collapse
Does morfic tweak on demand, I can't remember, I think I read it somewhere... ?
For completeness, and to save Harbb from becoming an emaciated crackflasher like us, I might just go through all the governers for each kernel I tested and note their settings down in the third post.
bedalus said:
To save me trying to copy and paste on my phone this early on the morning, just follow the link below to gov/sched and you'll see a summary in the first post about which scheduler goes best with which governor, e.g. ondemand and noop.
kernels ; battery ; ROM ; gov/sched
Click to expand...
Click to collapse
I think he was asking which scheduler you used with this benchmark. I'd bet it's deadline.
edit: bedalus, at least give me a couple of kernels to do and i'll note them down. You've had enough fun
bedalus said:
To save me trying to copy and paste on my phone this early on the morning, just follow the link below to gov/sched and you'll see a summary in the first post about which scheduler goes best with which governor, e.g. ondemand and noop.
kernels ; battery ; ROM ; gov/sched
Click to expand...
Click to collapse
Ah, I don't mean to ask what scheduler is recommended for each governor (because I've already got that info from your gov/sched thread ). Like Harbb said, I'm just asking that the specific scheduler used in this battery-saving benchmark is mentioned, whether you use the recommended for each or use the same scheduler for all of them (also I'm a she, not he ). Every phone is different and usage habits vary too, so I like to replicate the setup of benchmark winners to see if what you find best is best for me too.
My apologies deetailed. At least i got something right
As i said before, it is most likely deadline that was used since it has very uniform capabilities with each governor. Clarification would definitely be nice though, lack of sleep can do weird things.
tchaari said:
I don't think that you can "feel" the performance difference between ondemand and smartassV2 in such tasks. it should be better to stick to ondemand in this case I think
Click to expand...
Click to collapse
After repeatedly flashing all the kernels, ROMs, and trying all the governor / scheduler combinations that are possible, I've become attuned to the device. For some people they may 'feel' the difference intuitively, others might imagine a difference. But for me, I've had over ten years of practice in timing tiny fractions of a second, all thanks to sound engineering. For example, I used to add Haas delays to close mic'ed instruments to simulate 'early reflections', giving the psychoacoustic impression of greater depth and imagining to these instruments in the mix. These delays are anywhere from 5ms to 40ms.
For me, smartassV2 will always go from input on the touchscreen to an animated transition virtually instantaneously, but with ondemand, if you are coming from an idle state, there is always a little delay. It's tiny, maybe 100ms, but for a sound engineer, 100ms is a huge gulf.
S2 custom kernel tuning thread
Updated: 22/10/15
Welcome to my universal tuning guide for the Samsung Galaxy S2 i9100. This guide will cover different profiles I've created to meet every single situation, whether you want to save more battery life or to have more gaming performance.
Here is a following list of kernels that this thread will apply to:
- DorimanX kernel
- Apolo kernel
- Gustavo kernel
- DU kernel by Arnab
- Other kernels with variable changing support with underclocking and overclocking support
Guides:
- General Profiles
- Special Profiles
- Kernel Specific Profiles
List of things to do:
- Down threshold tuning
Changelog:
Code:
[B]24/10/15:
v1.1 [/B]
- updated most profile settings
- Added sampling rate tuning
[B]22/10/15:
v1 [/B]
- initial thread bring up[/SIZE]
General Profiles
These profiles will suit most devices and are generally used by most people with custom kernels. Of course, settings here are found on all custom kernels listed in the OP.
Please also be mindful that some governors behave better on certain kernels than others. Here is a list of governors that are known to work well on the following kernels:
- DorimanX kernel -> HYPER
- Apolo kernel -> PegasusQ
- Gustavo kernel -> PegasusQ (I think most governors work fine anyway)
Normal use/Default
Max CPU frequency: 1200mhz
Min CPU frequency: 200mhz
CPU governor: Ondemand/PegasusQ
Sampling rate: 50000
Up threshold: 85 or 75
IO scheduler: SIO/CFQ/ROW
Performance
Max CPU frequency: 1200
Min CPU frequency: 200
CPU governor: HYPER/NeoX/PegasusQ
Sampling rate: 50000
Up threshold: 60
IO scheduler: SIO/ROW/ZEN
Even more performance!!!
Max CPU frequency: 1300mhz (Personally, I don't recommend 1600mhz because it can be unstable, 1300mhz or 1400mhz should be fine on most devices)
Min CPU frequency: 200mhz or higher (Don't set this too high, personally, I think anything below 500mhz is still capable of good performance)
CPU governor: HYPER/NeoX
Sampling rate: 30000
Up threshold: 50 or 60
IO scheduler: SIO/ROW/ZEN
Gaming
Max CPU frequency: 1200mhz
Min CPU frequency: 200mhz
CPU governor: HYPER/NeoX/PegasusQ
Sampling rate: 40000
Up threshold: 60 or 75
IO scheduler: SIO/ROW/ZEN
Battery life
Max CPU frequency: 1000mhz
Min CPU frequency: 200mhz
CPU governor: Ondemand/zzmoove
Sampling rate: 120000
Up threshold: 90
IO scheduler: SIO/noop
Even more battery life!!
Max CPU frequency: 800mhz
Min CPU frequency: 200mhz
CPU governor: Ondemand/zzmoove
Sampling rate: 120000
Up threshold: 90
IO scheduler: SIO/noop
Special Profiles
These profiles are for people who want the best settings for specific situations
Good gaming performance with less battery drain
Max CPU frequency: 1200mhz
Min CPU frequency: 200mhz
CPU governor: Ondemand/PegasusQ
Sampling rate: 80000
Up threshold: 80
IO scheduler: SIO/ROW
Good gaming performance with even less battery drain
Max CPU frequency: 1000mhz
Min CPU frequency: 200mhz
CPU governor: Ondemand/PegasusQ
Sampling rate: 80000
Up threshold: 80
IO scheduler: SIO/ROW
Minimum drain from watching videos
Max CPU frequency: 800-1000mhz
Min CPU frequency: 200mhz
CPU governor: Ondemand/PegasusQ/zzmoove
Sampling rate: 100000
Up threshold: 85
IO scheduler: SIO/ROW
Minimum drain from listening music
Max CPU frequency: 800-1000mhz
Min CPU frequency: 200mhz
CPU governor: Ondemand/PegasusQ/zzmoove
Sampling rate: 120000
Up threshold: 90
IO scheduler: SIO/ROW
Kernel specific Profiles
These profiles are for people who have custom kernels that have unique settings
gsstudios's dorimanx default profile
Max CPU frequency: 1200mhz
Min CPU frequency: 200mhz
CPU governor (AWAKE): HYPER
CPU governor (SLEEP): Ondemand
Awake Up threshold: 70
Sleep Up threshold: 75
IO scheduler (Awake and Sleep): SIO
TCP algorithm: Westwood
gsstudios's optimized apolo kernel profile
Max CPU frequency: 1200mhz
Min CPU frequency: 200mhz
CPU governor: PegasusQ
Up threshold: 75
IO scheduler: SIO
Any suggestions will be great so that our fellow S2 users can have the best custom kernel experience!
I also encourage sharing of your own profiles in this thread. Just stay on topic and all will be fine :good: :victory:
@gsstudios
http://forum.xda-developers.com/showthread.php?t=2432029
This thread should be in OP. I learned a bit from there , because i could take a profile , test it , adjust some valumes test (...) again again... and finally create STweaks profile , thay suits be best.
MikiGry said:
@gsstudios
http://forum.xda-developers.com/showthread.php?t=2432029
This thread should be in OP. I learned a bit from there , because i could take a profile , test it , adjust some valumes test (...) again again... and finally create STweaks profile , thay suits be best.
Click to expand...
Click to collapse
I will have to ask eskriminal to update the stweaks OP, but since we don't see him on XDA anymore, this may not happen.
Is there a chance someone will add back the 100MHz CPU step? Siyah had it and I think it helped save power in some situations, like when playing music.
Also, can someone recommend a widget to quickly change profiles? Voltage control was good but it doesn't seem to work anymore.
apphoarder said:
Is there a chance someone will add back the 100MHz CPU step? Siyah had it and I think it helped save power in some situations, like when playing music.
Also, can someone recommend a widget to quickly change profiles? Voltage control was good but it doesn't seem to work anymore.
Click to expand...
Click to collapse
What kernel are you using? Dorimanx kernel allows underclock to 100mhz, apolo kernel uses stock frequencies, Gustavo kernel also allows 100mhz (i think)
Edit: Gustavo kernel doesn't support 100mhz
gsstudios said:
What kernel are you using? Dorimanx kernel allows underclock to 100mhz, apolo kernel uses stock frequencies, Gustavo kernel also allows 100mhz (i think).
Click to expand...
Click to collapse
Using Gustavo_s kk kernel 04-02-TWRP-TRIM... 200mhz is minimum, according to Synapse. To be honest, I've had bad experience with Dorimanx kernels before (tried 5-6 versions, always buggy or horrible performance). I might give it another try, I see that you maintain it now. Thank you.
So I wanted a different thread to make a list of different Power Profiles from users of my custom Kernel. My threads are usually pretty big so it gets hard to manage and this is also a safe place for me to post the defaults I'm using.
I'll review each profile and include your Power Profiles in the app if they seem to make sense.
Please follow the template below when posting. Keep off-topic, requests, etas and useless conversations out of here.
FrancoKernel defaults:
Low Power Cluster
Max CPU freq: 1440000
Min CPU freq: 384000
Governor: interactive
Governor parameters:
above_hispeed_delay 0
go_hispeed_load 100
hispeed_freq 0
target_loads 85 600000:45 787200:50 960000:60 1248000:80
timer_rate 20000
min_sample_time 60000
ignore_hispeed_on_notif 1
max_freq_hysteresis 80000
timer_slack 30000
Max Power Cluster
Max CPU freq: 1824000
Min CPU freq: 633600
Governor: interactive
Governor parameters:
above_hispeed_delay 20000 960000:40000 1248000:20000
go_hispeed_load 90
hispeed_freq 960000
target_loads 90 1248000:95
timer_rate 30000
min_sample_time 20000
ignore_hispeed_on_notif 1
max_freq_hysteresis 80000
timer_slack 30000
Input boost frequency
Low power cluster: 1248000
Performance cluster: 768000
Input boost duration
1500
Join the beta here http://beta.franciscofranco.xyz and starting with the next beta8 profiles will be included and be available to apply in a single tap.
FrancoKernel thread: http://n5x.franciscofranco.xyz
Saved to post profiles from users.
Saved to post profiles from users.
What's your opinion on these?
I'm using the Glassfish 1.2 profile since 2 days with your latest kernel, seems to be working great, cannot give an elaborate opinion yet though, obviously.
sigurd_LU said:
What's your opinion on these?
I'm using the Glassfish 1.2 profile since 2 days with your latest kernel, seems to be working great, cannot give an elaborate opinion yet though, obviously.
Click to expand...
Click to collapse
I think there's a lot overcomplication in all of those, but I'll include one or other because users like to play with 'em.