Related
Introducing the new variant of Bali kernel, Bali for CM7. The main goal of this kernel is the same as other Bali kernel, balanced performance and battery life. I can't guaranteed you will get the same battery life as Bali for Froyo but you will definitely get an improve battery life over stock kernel.
Features:
- OC/UV up to 1.4GHz (Safe boot to 1GHz) [require setCPU from market]
- Voodoo Sound v10
- Voodoo Color
- Multiple CPU governor, smartass included (default: ondemand)
- Multiple IO scheduler (default: BFQ)
- LED notification support (no external app required)
- CIFS support
- Support SetCPU screen off 100/400 profile
- Dock sound redirector support [need Galaxy Dock Sound Redirector app from market]
Disclaimer:
As always, I'm not responsible with any damage cause to your phone.
Special Thanks:
- Team Whiskey - you guys are awesome.
- Alexia - for great work on the new splash image.
- Supercurio - for awesome work on Voodoo
- xcaliburinhand - for wonderful work on dock sound redirector.
- Everybody at CM dev community for their hard work on this awesome ROM.
- Everybody at #teamwhiskey for beta testing this kernel and their support.
I apologize if I miss anyone ..
Flashing Instruction:
- If you're coming from another kernel, flash "Ultimate Kernel Cleaning Script" by lippol94 first (http://www.multiupload.com/XFH1GCK4MB)
- Once that's done .. then flash Bali-CM
If you don't know how to flash then this is not for you.
Download:
Bali-CM_v2.2.2
Change Log:
Code:
- 2.2.2 [10/18/2011]
CM update
Re-enabled LED by default
- 2.2.1 [9/12/2011]
Fixed screen jitter issue
- 2.2 [9/10/2011]
Upgraded BFQ to v2
Added Smartass v2 with extra tweak
Fixed ondemand and tweaked for smoother experience
Set ondemand as default governor
Other fixes and tweaks
- 2.1 [9/1/2011]
Disabled SLQB and revert back to SLUB
Disabled LED notification for the time being
Added more UV settings
GPU tweaks
Added v(r) scheduler
Added Tiny Preempt RCU
And other tweaks and fixes
- 2.0 [8/25/2011]
Disabled ramzswap and switched to zram
Enabled zcache for better IO performance
Memory tweak, now gives you 340MB
More tweaks
- 1.2.1 [8/19/2011]
Fixed video playback issue
Fixed battery report when charging, it goes to 100% now
- 1.2 [8/18/2011]
Updated source with the latest CM patches
Added SLQB slab allocator for better memory management
Added more tweaks
- 1.1.1 [7/26/2011]
Fixed kernel instability that cause random reboot
- 1.1 [7/26/2011]
Added Voodoo color V2
Fixed UV portion to make it easier to manage
Added Voltage Control support
Added compiler tweak
- 1.0 [7/22/2011]
Initial release
A little explanation on different governors (taken from Lord ClockAn thread):
- interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
- smartass - Is an improved version of interactive governor
- 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.
Q and A:
My screen has green, yellow, or orange tint.
Use Voodoo Control to set color profiles (courtesy of d_phekt)
Screen RGB Multipliers:
Red = 230996000
Green = 230996000
Blue = 2704668800
Screen v1 Gamma Hack:
Red = -50
Green = -53
Blue = -44
is GPS still functional with this kernel?
gamikzone said:
is GPS still functional with this kernel?
Click to expand...
Click to collapse
Yes .. GPS still functional.
drhonk said:
Yes .. GPS still functional.
Click to expand...
Click to collapse
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
gamikzone said:
im about to flash this hows ur battery life compared to stock? im getting pretty good battery on stock who knows how great it will be with this
Click to expand...
Click to collapse
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
drhonk said:
Just like other Bali kernel .. it takes 2 - 3 days to settle in, but my beta testers reported anywhere from 15 - 20 hrs average. I myself got 18hrs with 2 push email accounts, twitter, sms, and few calls.
Click to expand...
Click to collapse
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
gamikzone said:
thats good im getting around 14 hours with stock, have u tried the ondemand setting for your cpu? i seem to get better battery life with that compared to conservative
Click to expand...
Click to collapse
Try smartass with this kernel ..
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
i think i will try this out tonight
I believe this will be ok to use with miui.
Nice animation.
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
jay661972 said:
I believe this will be ok to use with miui.
Nice animation.
Click to expand...
Click to collapse
Trying it out , any recommeneded UV settings?
Sent from my T959 using XDA App
jay661972 said:
Looks like not meant for Miui. after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
It does work on miui,
Sent from my T959 using XDA App
drhonk said:
Try smartass with this kernel ..
Click to expand...
Click to collapse
would downloading SetCPU and just setting the governor to smartass improve battery life? or do you have to actually UV and all that
Really, how did you do that? I did the clean script first and flash Bali.
es7241 said:
It does work on miui,
Sent from my T959 using XDA App
Click to expand...
Click to collapse
Okay I will try this one more time.
jay661972 said:
Okay I will try this one more time.
Click to expand...
Click to collapse
confirmed .. it works on MIUI since I just flashed MIUI with it.
jay661972 said:
after seeing the animation (Approved Cyanogen Bali), it turns black and wont turn on. Need to pull the battery.
Click to expand...
Click to collapse
Same here except im flashing from trigger redux #12 and ive tried flashing from trig w/glitch and w/du jour
Sent from a cell tower to the XDA server to you.
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
drhonk said:
confirmed .. it works on MIUI since I just flashed MIUI with it.
Click to expand...
Click to collapse
jay661972 said:
now that's the trick. if you have glitch kernel, you need to re-flash stock miui rom then flash Bali. It works now for me
Click to expand...
Click to collapse
So you can't flash bali on miui energy? You have to revert to stock miui?
Sent from my T959 using XDA Premium App
HELLO AND SALAM SATU MALAYSIA
Since i was newbie about android,
i try to overclock my Xperia X8.
so i went to market and i found Antutu CPU Master.
the problem is i found something that i never heard before.::::::
"GOVERNOR"
could someone told me..what is governor actually...
and what different better the governor module?
i only found about smartass..the other module..i didnt find in xda forum.
i hope someone could help me here..before i accidentally brick my phone.
Cpu governor is control the Cpu freq.
- The OnDemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed.
- The Conservative sets the CPU speed in a similar way to the Ondemand governor, but scales the CPU up much less rapidly. This would theoretically save battery power, but may lead to less responsiveness.
- The Userspace governor is currently useless. It’s another way for applications to set the CPU speed that setCPU does not use.
- The Performance governor always keeps the CPU at the maximum set frequency.
Additionally, he makes reference to another option, which is not currently part of the setCPU app, so I am assuming that this is one that was removed in later versions.
- The Powersave governor always keeps the CPU at the minimum set frequency.
- Except for “Userspace,” no matter which governor you set, the CPU will always stay within the bounds of the maximum and minimum speeds you set in setCPU.
tony-noob said:
Cpu governor is control the Cpu freq.
- The OnDemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed.
- The Conservative sets the CPU speed in a similar way to the Ondemand governor, but scales the CPU up much less rapidly. This would theoretically save battery power, but may lead to less responsiveness.
- The Userspace governor is currently useless. It’s another way for applications to set the CPU speed that setCPU does not use.
- The Performance governor always keeps the CPU at the maximum set frequency.
Additionally, he makes reference to another option, which is not currently part of the setCPU app, so I am assuming that this is one that was removed in later versions.
- The Powersave governor always keeps the CPU at the minimum set frequency.
- Except for “Userspace,” no matter which governor you set, the CPU will always stay within the bounds of the maximum and minimum speeds you set in setCPU.
Click to expand...
Click to collapse
thanks button click =)
btw,what apps u use to overclock.?
and what governor u preferred? and what is ur min n max scale?
naim.kamiya said:
thanks button click =)
btw,what apps u use to overclock.?
and what governor u preferred? and what is ur min n max scale?
Click to expand...
Click to collapse
I'm not using any app. I overclocked in my system (alfs+GDX). My governor is OnDemand. Min 129mhz - max 748 mhz.
tony-noob said:
I'm not using any app. I overclocked in my system (alfs+GDX). My governor is OnDemand. Min 129mhz - max 748 mhz.
Click to expand...
Click to collapse
owh.ok...
thanks again.
im not using GDX,,but..can i install alfs in my phone?
im using Linux Escha Arch v1
naim.kamiya said:
owh.ok...
thanks again.
im not using GDX,,but..can i install alfs in my phone?
im using Linux Escha Arch v1
Click to expand...
Click to collapse
Offcourse you can install alfs but you should unlock your bootloader...
tony-noob said:
Offcourse you can install alfs but you should unlock your bootloader...
Click to expand...
Click to collapse
i already make it,...
thanks a lot.
last question...what version u have?
it is ok to use alfs kernel with different roms,not GDX?
naim.kamiya said:
i already make it,...
thanks a lot.
last question...what version u have?
it is ok to use alfs kernel with different roms,not GDX?
Click to expand...
Click to collapse
I have vesion 5. You can use alfs with other roms but maybe wifi won't work or vibration....
tony-noob said:
I have vesion 5. You can use alfs with other roms but maybe wifi won't work or vibration....
Click to expand...
Click to collapse
i use alf kernel version 3..
so far,i didnt find any bug.
wifi n vib work very well with my linuxperia arch v1 rom.
i use antutu benchmark..i get 1881..
superb ..thanks a lot.
1881 good. Do you like LinuXperia v1 ? Come soon LinuXperia Esca Arch 3 ( overclock, bravia hack, xloud, dsp manager vs )
alessiocerci said:
1881 good. Do you like LinuXperia v1 ? Come soon LinuXperia Esca Arch 3 ( overclock, bravia hack, xloud, dsp manager vs )
Click to expand...
Click to collapse
Cant wait for linuxperia v3
Sent from my E15 using xda premium
GUys anyone know why the msm-dcvs governor for our Xperia SP cpu is buggered?
it's supposed to be Krait optimized, yet I just checked the governer parameters on Trickster Mod and it's got the MAX CPU speed set at 384 mhz
I tried changing it and applying it in Trickster Mod, but it doesn't apply nor stick ...
all the other Parameters are 0
any ideas guys
raziel123 said:
GUys anyone know why the msm-dcvs governor for our Xperia SP cpu is buggered?
it's supposed to be Krait optimized, yet I just checked the governer parameters on Trickster Mod and it's got the MAX CPU speed set at 384 mhz
I tried changing it and applying it in Trickster Mod, but it doesn't apply nor stick ...
all the other Parameters are 0
any ideas guys
Click to expand...
Click to collapse
I seem to be having the same problem. Running 257 with stock kernel (LB +root). The MSM-DCVS kernel doesnot seem to be working. it is always stuck at the min frequency. is there any way yo fix this?
I donot plan on moving to 4.3 stock as the comments here arent very good about the experience.
Note!
Only for stock 4.3
Click to expand...
Click to collapse
Features
Gamma Control - HOW-TO
DoubleTap2Wake - HOW-TO
Sweep2Wake - HOW-TO
Advanced Xperia Recovery - HOW-TO (Only v5 and above)
Based on 10.4.1.B.0.101 kernel sources
Xperia Advanced Recovery Bootloader
CPU overclock upto 1.944 GHz
Undervolting
Built with Linaro 4.8.3 toolchain using -O3 optimisation
Updated Prima WLAN drivers
Additional CPU governors - SmartMAX | SmartMAX_eps | Intellidemand 5.0 | Intelliactive | Preservative
Tweaked SIO and added FIOPS, Zen, VR, BFQ (7.2) and ROW block schedulers
USB force fastcharge
Updated Ondemand and interactive governor
Compressed kernel using XZ
Tweaked voltage regulators
Interactive GPU Governor
Uses CPUQuiet from Nvidia
Click to expand...
Click to collapse
Installation instructions
Flash in CWM/TWRP
Click to expand...
Click to collapse
Un-Installation instructions
Use the AROMA Installer in the zip to uninstall
Click to expand...
Click to collapse
Credits
Sony - I love what they do and only wish they got more recognition. They deserve it.
faux123 - For almost all kernel features
DoomLord - For the RAMDISK
Click to expand...
Click to collapse
Donors
Source
http://bitbucket.org/nikhiljan93/xzkernel
Click to expand...
Click to collapse
XDA:DevDB Information
[Stock-Kernel] XzInnere [Linaro-4.8.3], a Kernel for the Sony Xperia Z
Contributors
alnikki25k
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 5.0
Stable Release Date: 2014-03-29
Created 2014-01-27
Last Updated 2014-03-28
Reserved
HOTPLUG CONTROL, GOVERNORS, SAMPLE CONFIGS:
Thanks to n3ocort3x
With cpuquiet + load stats governor u get a brilliant battery life while keep it snappy.
I recommend leaving the governor on load stats (hotplug depended on load) to get the best results.
If you want to keep it balanced, and yeah, most users want that:
governor: smartmax
cpuquiet governor: load_stats
If you want ultimate performance:
governor: interactive (up treshold 65) or smartmax (lower tresholds)
cpuquiet governor: load_stats
SMARTMAX GOVERNOR
===============
awake_ideal_freq 594000
boost_freq 1242000
suspend_ideal_freq 384000
touch_poke_freq 1242000
Leave the rest untouched
Click to expand...
Click to collapse
For a more power-saving governor (Recommended)
New! Preservative
Click to expand...
Click to collapse
Thanks to bedalus
This is just for the record, and for those interested. The previous version of Preservative worked like a combination of smartass and conservative. It would scale straight up to the optimum frequency if there was any load (like smartass), then scale up one step at a time (like conservative) if the load was above the required threshold. This worked pretty well, and helped keep the frequency low. But sometimes it was keeping it low for too long, and a few users (myself included) noticed occasional hangs, presumably caused by a pile up of critical code that didn't get executed in time.
To improve responsiveness, but keep the frequency as low as possible was quite a challenge. I took the existing logic and chucked most of it in the bin...
(Remember, it's keeping the frequency low, and not UV that saves power - read this thread, especially post #2 for more background on this issue)
...what came to replace it was a fairly original hybrid, inspired by ondemand. Ondemand works by jumping to the top frequency when there is any load. This is usually overkill. So, you might have been at 100% CPU utilisation at 384MHz, so ondemand will jump straight to 1512MHz. However, when it gets there, the utilisation is now only 30%, so it will scale down to 486MHz.
Preservative now works a little like this. Whatever frequency it is currently at, if the utilisation hits 100%, it will scale up. But scaling up to max like ondemand? In the example above, this was the worst kind of overkill. Scaling up to max just to find scaling up one step would have been sufficient. But do we need to scale up one step, or as many as possible? There's no way to know for sure. You have to scale up before you can measure if the extra CPU cycles were enough or not.
This issue is what Preservative attempts to overcome: if the load is high, it will scale up, but not always to max. Let's label the frequency steps: 384=A 486=B 594=C 702=D 810=E 918=F 1026=G 1134=H 1242=I 1350=J 1458=K 1512=L
Conservative would take 11 calls to the governor to get from A to L, if L was required. Ondemand would go straight there. Ondemand is often overkill, conservative is often underkill. I'd like a compromise. Here's what Preservative would do:
Code:
L <- 4th step selected by preservative
K <- 3rd step selected by preservative
J <- 2nd step selected by preservative
I
H
G <- 1st step selected by preservative
F
E
D
C
B
A <- sat here until there is load
It splits the difference between whichever frequency it is at and the top frequency, and jumps there. If it is still under high load, it will do it again. So if it is idling, then needs to get to the top, it takes three more calls than ondemand, but seven less than conservative. Not only that, but it has also skipped over a large chunk of the slower steps that conservative would crawl through.
Scaling down also works in a similar way. Preservative will work out what step would be sufficient to manage the load, then jump halfway to that step on the first call. This is because, unlike ondemand, there is no down-threshold. Preservative will scale up when the load exceed the up threshold, but as soon as this is no longer the case, it will start attempting to scale back down to save power. It does not wait for load to reduce to drop below a certain point. Loads fluctuate. If went straight back to A, only to come back back to L, it would have to scale through G J and K again. However, dropping to G then D then B before A means if it does have to scale back up towards L, it doesn't have as far to climb, meaning less calls to the governor, and that the best step can be achieved quicker.
There has also been an adjustment to the up threshold. When the device is idle, the up threshold will automatically adjust to be more relaxed about scaling up. This means while the device is idle (e.g. when you are just reading some text) it becomes increasingly sensitive to changes in demand. When you touch the screen it will extremely responsive.
Conversely, when the device is hitting the top frequency, the up threshold will become increasingly strict. So if you are gaming, and putting a lot of load on the CPU, it will aim to be as efficient as possible, and only scale up if it really has to, to ensure that no cycles are wasted at these high power hungry frequencies.
Whenever it goes from hitting L to hitting A, or visa versa, the threshold will reset to default. The sysfs location of this tunable remains at:
Code:
/sys/devices/system/cpu/cpufreq/up_threshold
It will accept values of up to 127, higher being more power-saving. The default is 100, but editing the file changes this value. If you want to use a different value on a permanent basis, add the line
Code:
[B]echo 84 > /sys/devices/system/cpu/cpufreq/up_threshold[/B]
to /etc/init.d/00config
and it will then restore your setting of 84 (or whatever) every time you reboot. Remember it will be overwritten if you flash updates to the kernel, so make a copy of your edited file. However, I believe 100 is a pretty good default.
Click to expand...
Click to collapse
Reserved
Changelog
Next-Release-TO-DO
XzI - v6
Kitkat - 230 Sources
Massive changelog
Large amounts of debugging code removed
Click to expand...
Click to collapse
Current-Release
XzI - v5
Intelliactive CPU governor
New! Advanced Xperia Recovery Bootloader
New! Preservative CPU Governor (Read more)
Kernel mode NEON
MSM CPU Frequency Limiter / a.k.a Snake Charmer(in faux app) support
Kernel Futex tweaks
MSM Memcopy enhancements from Motorola Mobility
Higher Bus Speeds @ Lower cache clocks = Higher performance @ Lower Temperatures + More Power Savings
Generic tweaks
Click to expand...
Click to collapse
Previous releases
XzI - v4
Sony 10.4.1.B.0.101 Sources
Tap2Wake/Sweep2Wake using evgen method
New Power-Aware Workqueue algorithms
AROMA Installer
XzDualRecovery
Lots of debugging removed
BFQ-v7r1
Interactive GPU Governor
Removed Simple GPU Governor
Removed MultiROM
Click to expand...
Click to collapse
XzI - v3
MultiROM Xperia for Xperia Z - http://www.youtube.com/watch?v=9f9gG1sRNog
- Initial implementation. Not functional. Just testing boot.
Revert Power-Supply drivers back to 4.2.2
Intellidemand Governor 5.0
Click to expand...
Click to collapse
XzI - v2
Lower undervolt to 600 mV
Sound Control 2.0
Gamma Control
SLUB updates
Updated Adreno drivers
Use O3 Optimisation
Tune BFQ
System Config Clean-up - Quite experimental
Click to expand...
Click to collapse
XzI - v1
Initial Release
Click to expand...
Click to collapse
Download
Click here
Click to expand...
Click to collapse
MultiROM
Coming Soon
Placeholder
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Kocayine said:
Cool! Good job. What would you say is the advantage in this kernel over XzKernel?
Click to expand...
Click to collapse
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
alnikki25k said:
Almost no setup needed. Everything works with a good default configuration. Uses a completely different hotplug governor.
Click to expand...
Click to collapse
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Kocayine said:
I guess including DoubleTap in the kernel would make it too much like your other kernel, right?
Click to expand...
Click to collapse
Yup. May not include that. But will have Gamma control.
No sound control right?
alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
You sure you cant make a version with doubletap? I dont need very advanced kernel, just some governors and stuff and now I got used to the tapping as well : (
BTW, how about the wakelock fixes and so from XzKernel, are they included here?
beniamin24 said:
No sound control right?
Click to expand...
Click to collapse
This is just the first release. It'll be added next.
my phone reboots after trying to undervolt in trickster mod app
braacic17 said:
my phone reboots after trying to undervolt in trickster mod app
Click to expand...
Click to collapse
It works for me. Clear all settings in TricksterMOD and try again.
alnikki25k said:
It works for me. Clear all settings in TricksterMOD and try again.
Click to expand...
Click to collapse
nope. still not working i tried everything even in faux123 app but it just reboots.
well its not so important for me right now. kernel is awesome and i can see better battery life on my xz 4.3 !!
thanks ! :laugh:
alnikki25k said:
Yup. May not include that. But will have Gamma control.
Click to expand...
Click to collapse
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
What about exFAT? Is it work properly?
-totonio- said:
When you include gamma control I'll switch to this kernel
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
.. and doubletap.. then we got all that is needed
Not for deodexed right?
Inviato dal mio C6603 utilizzando Tapatalk
Exactly what i need, a battery oriented / balanced kernel, while keeping it slim.. Keep up the good work!
Waiting for gamma control.. ??
Edit Note: i've missed the part which state that double tap wont be included here.. Sorry..
Sent from my C6602 using Tapatalk
Hi,
I'm using Co-Core 8.2 and I want to test One Power Guard to improve my battery life.
But I don't have any idea about which CPU governor and I/O scheduler to choose.
Could someone tell me which combination provides the best balance between power-save and performance?
I'm on Jelly Bean 4.1.2
NB. Cocafe recommends PegasusQ as CPU governor and either SIO/ROW for I/O scheduler but I would like to get some feedback from people already using One Power Guard.
Thanks in advance
luisblop said:
Hi,
I'm using Co-Core 8.2 and I want to test One Power Guard to improve my battery life.
But I don't have any idea about which CPU governor and I/O scheduler to choose.
Could someone tell me which combination provides the best balance between power-save and performance?
I'm on Jelly Bean 4.1.2
NB. Cocafe recommends PegasusQ as CPU governor and either SIO/ROW for I/O scheduler but I would like to get some feedback from people already using One Power Guard.
Thanks in advance
Click to expand...
Click to collapse
Pegasus and sioplus
OR
Hotplug and sioplus
DaRkRhiNe said:
Pegasus and sioplus
OR
Hotplug and sioplus
Click to expand...
Click to collapse
Thanks for the answer. I will give a try with Pegasus
However I noticed that sioplus is not available on One Power Guard settings. Only row and sio.
Is sioplus available in Co-core 8.2?
These apps like this just drains your battery. If you want play with CPU, download a CPU controller app. (like SetCPU) and install CoCore 9.0 which is newest version.
When you don't use phone ; 600 MHz Max & HotPlug
When you don't use phone V2 ; 600 MHz Max & Ondemand & deeper sleep status
When you lock phone, don't decrease speed (too much) because it will use whole CPU if it needs ; 800 MHz Max & Ondemand Q/Lulzactive Q/Pegasus Q
When using ; 1000 MHz Max & Ondemand/Interactive/Lulzactive Q/Pegasus Q
When you get mad and crazy about performance, lock the min to max; 1000 MHz min and max & Ondemand & SmartAss (still exists or not I don't know)
If you increase minimum speed it will keep it. So I suggest always keep min to 200MHz. (if exists 0 MHz I don't remember it too)
Edit: and don't go deeper sleep if you use hot plugger governors like Hotplug, Pegasus, Lulzactive Q
FYI
http://forum.xda-developers.com/showthread.php?t=2312491
Powered by CM11
Thanks guys,
I will compare the battery draining with One Power Guard just to give it a try.
If I don't notice any improvement then I will tweak with SetCPU
King ov Hell said:
Edit: and don't go deeper sleep if you use hot plugger governors like Hotplug, Pegasus, Lulzactive Q
Click to expand...
Click to collapse
Hi again,
What exactly do you mean wit "deeper sleep"?
Is that an option or when the display is off after several minutes?
Sorry for my ignorance
luisblop said:
Hi again,
What exactly do you mean wit "deeper sleep"?
Is that an option or when the display is off after several minutes?
Sorry for my ignorance
Click to expand...
Click to collapse
Go to the CoCore's thread you'll see. It's deep sleep level which can increase your battery life when you don't use the device. It's not about using, it's about when it's stand-by.
Ok
After one day even if One Power Guard is a nice app I prefer to switch governor depending on the display status. So I was thinking about using tasker (instead setCPU) which is already running on my phone and this way not adding more background processes.
I set a couple of task using the CPU control from tasker. It is working fine switching governors but I noticed that the frequencies (min and max) don't change. I tried even with shell script and still I don't get to set the max frequency. Then I prefer to make you a couple of questiosn:
-In tasker when using the CPU control. If I change governor. Should it be set in both CPUs (0 and 1) or only in a single one? In my case i set the governor in both.
-I use the terminal to check the current governor and max frequency (for instance for the cpu0)
cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governorcat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
As said above the governor is succesfully changed but that's not the case for the frequency. Then I tried to run a shell script to change the max frequency as follows:
echo #frequency > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
But it seems not working neither. So I wonder if I'm doing something wrong.
NB. By the way I'm happy using the governor hotplug while not using my phone (thanks for the advice). In normal use I set pegasusq with sio and seems working great.