Database Users

[Q] CPU governor settings quide - battery life

I would like to get to know the CPU governor settings with CM7 bootmenu settings in order to increase battery life. Maybe others too - hope so.
The below description I found in hrk post:
- powersave will always set the "min" and never change it
- performance will always set the "max" and never change it
- ondemand (usually the default) will raise the value by a step up when the cpu is used, and lower the value by a step down when the cpu is not (much) used.
- conservative is like ondemand but will be slower when changing frequencies
- interactive is (conceptually) like ondemand but will be quicker when changing frequencies.
- smartass is (conceptually) like interactive, but I haven't understood yet why it's so much smart and loved by users.
- userspace will do nothing at all, so don't choose it. I may hide it in a future release to avoid confusion
Anyone can add information about above modes in CM7 bootmenu?
So there are like those prefixs there:
con - this goes to conservative governor mode;
int - this one is for interactive governor;
ond - is for ondemand mode;
smt - is smartass governor mode.
But what about Clk1, Clk2, Clk3 and Vsel1, Vsel2, Vsel3 settings?
To which governor modes this Clk and Vsel settings apply?
Anyone can help/explain?

well.... Clk1, Clk2, Clk3 and Vsel1, Vsel2, Vsel3 basiclay apply to all.
Clk1, Clk2, Clk3 are the clock speeds that the proccesr will run when stepping up or down, the defaults with no overclock are 300,600,800.
Vsel1, Vsel2, Vsel3 are the voltages that the proccesor runs at when working at coresponding clock. tweaking these will make ur battery last loger.
for example
default clk3 is 800 at vsel 58
currenty i have clk 3 at 1000 with vsel3 52.
hope you have understand what i mean.
ps sorry for my bad english

There is a ready made app that can help you with the changes.
Have a look at
http://forum.xda-developers.com/showthread.php?t=898036

What about the threshold?
What it does and does it apply to every governor mode?

kaljam said:
There is a ready made app that can help you with the changes.
Have a look at
http://forum.xda-developers.com/showthread.php?t=898036
Click to expand...
Click to collapse
As stated in this thread at point 15 you should'n install Setvsel.
15) How to overclock/undervolt in CM7?
CM7 already comes with 1000/600/300 clock, but if you want to modify these settings or undervolt:
- Reboot and enter Bootmenu
- System -> Overclock
Remember that if you experience freezes, reboots and other problems OC/UV can be the cause. Try to disable in this situation.
Also, DON'T INSTALL SETVSEL!
http://forum.xda-developers.com/showthread.php?t=1065798

When I install Setvsel on CM7 and went back to Bootmen /CPU settings - it was disabled.
So installing Setvsel on CM7 disables CPU settings in Bootmenu, previously enabled there.

m_zet said:
When I install Setvsel on CM7 and went back to Bootmen /CPU settings - it was disabled.
So installing Setvsel on CM7 disables CPU settings in Bootmenu, previously enabled there.
Click to expand...
Click to collapse
Well i want my phone to be lightweight so if i can do some settings without an aplication running on my system, i'm up for it

I've tried both and I'm more satisfied with setvsel.

Setvsel is great for the ones who has no CM7 and its bootmenu with setvsel functionality implemented there.
BTW
Anyone can explain why smartass governor is so awsome?

As I said i've tried both with CM7 and I prefer setvsel.
I get better battery time with setvsel. Probably because there is a load of parameters in bootmenu you can apply but nobady cares to explain what they do

kaljam said:
As I said i've tried both with CM7 and I prefer setvsel.
I get better battery time with setvsel. Probably because there is a load of parameters in bootmenu you can apply but nobady cares to explain what they do
Click to expand...
Click to collapse
I got the same results with settings done by Setvsel and done in bootmenu CM7 CPU settings.
I compared Defy running using CM7 bootmenu CPU settings and Setvsel.
It was the same - so why bother to install an app when it is in bootmenu.
Though the CPU menu got more options to get to know and set, what this thread was made for.
As always the choise is yours - the phone is yous you can do anything with it.

well, can someone answer a question posted before? what are the thresholds and the rest of the settings?

m_zet said:
When I install Setvsel on CM7 and went back to Bootmen /CPU settings - it was disabled.
So installing Setvsel on CM7 disables CPU settings in Bootmenu, previously enabled there.
Click to expand...
Click to collapse
Do you mean we can actually use Setvsel in CM7?

I think this should help you:
http://forum.xda-developers.com/showpost.php?p=30779799&postcount=1
And this:
http://forum.xda-developers.com/showthread.php?t=1377587

[app] (update 31/07, v 0.0.4.1) avsMon for thalamus kernel / Oxygen 2

About
avsMon lets you easily enable or disable avs module via simple button click or even enable it on every boot. Moreover it provides information about current state of avs module, cpu frequency and voltage.
thalamus kernel comes with disabled avs module. We can easily enable this functionality for some power usage improvements (like drop to 3-4mA in screen off state) if cpu can handle those voltages, by 'echoing' 1 to /sys/module/avs/parameters/enabled. But this requires opening a terminal application and some struggle with onscreen keyboard. Inconvenient and time consuming.
A bit annoyed, I've ended up with this little application. It's basic functionality is to help to enable or disable avs module, by providing GUI to those 'echo' commands.
Additionally, it displays info about current avs state, cpu frequency and cpu vdd (pooled in user configured intervals).
This post and application originates from here: http://forum.xda-developers.com/showpost.php?p=15988562&postcount=934.
Click to expand...
Click to collapse
Current version v.0.0.4.1 (download from attached files)
Screenshoots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Todo
investigate devNull compatibility
Changelog
Code:
[b]v.0.0.4.1 | 31-07-2011[/b]
- default maximum voltage changed to 1250mV,
[b]v.0.0.4 | 31-07-2011[/b]
- option to set maximum voltage ([I]vdd_max[/I]),
- option to set minimum voltage ([I]vdd_min[/I]),
- option to apply user-specified voltages on boot,
- user interface improvements,
- bug reported by [url=http://forum.xda-developers.com/showpost.php?p=16128093&postcount=10]theyau[/url] fixed,
- multilingual support ([I]strings.xml cleanup, now ready for translations[/I]),
- about view modified - donate link added,
[b]v.0.0.3 | 28-07-2011[/b]
- option to set avs module to enabled on boot,
- user interface improvements,
- some minor code optimizations and cleanups,
- one bug traced and fixed.
[b]v.0.0.2 | 26-07-2011[/b]
- options menu in main view,
- cpu frequency and vdd information,
- user configured pooling interval for frequency/vdd,
- GUI improvements,
- changed basic program icon,
- about view & settings view,
[b]v.0.0.1 'proof of concept'[/b]
- initial release with basic functionality:
* avs status,
* enable/disable avs module
Manual
1. Enabling avs module on boot.
To enable avs module on boot, press menu key. This will open options menu pane. From there, select settings. You'll be transferred to settings view, where you have to click Enable AVS on boot option.
avsMon will now request superuser rights. If you haven't already done this, su popup will appear. For best results, check Remember box and allow.​
2. Applying user-specified voltages on boot.
To apply custom voltages, go to settings, select Voltages and then check Enable user-specified voltages on boot.
avsMon will now request superuser rights. If you haven't already done this, su popup will appear. For best results, check Remember box and allow.​
3. Changing voltages.
To change voltage levels, go to settings, select Voltages and then either Minimum voltage or Maximum voltage. Changing default value will result in immediate writing new values to vdd_min or vdd_max files in sysfs.​
Requirements
Requires 2.3 and su privileges to toggle avs module.
Fetching avs and cpu states is done with normal privileges.
Disclaimer
I don't take responsibility for any damage or data loose.
Application was tested on Oxygen 2.1.6 with thalamus kernel 2.6.35.13_r4.
I recommend to uninstall earlier version and then install current rather than update already installed one.
Final notes
If you like this little app, don't forget to press thanks button.
Donations are off course welcome.
Any features requests and comments are much appreciated.
Stay tuned, for updates....

This is nice. I shared your pain fiddling with terminal and keyboard.
Good job

Nice idea! However, I think one would not enable or disable the feature too often. I would rather put a script in /system/etc/init.d to enable it at each boot (and so I have done). I would suggest you a new feature: add a button Make it permanent to make the setting be restored at boot (if you haven't implemented it already). The implementation should write a specially crafted script in /system/etc/init.d to restore whatever setting was chosen in the GUI. Of course, your application would need a root privilege.

AlxMAX said:
Nice idea! However, I think one would not enable or disable the feature too often. I would rather put a script in /system/etc/init.d to enable it at each boot (and so I have done). I would suggest you a new feature: add a button Make it permanent to make the setting be restored at boot (if you haven't implemented it already). The implementation should write a specially crafted script in /system/etc/init.d to restore whatever setting was chosen in the GUI. Of course, your application would need a root privilege.
Click to expand...
Click to collapse
Tanks. I already have peresistent avs enabling through android service @ boot on my todo list. I think that it's much elegant solution, than writing anything to /system/etc/init.d/ (which is not so easy thou and requires remounting /system).
Simple service will start at boot, check if avs is enabled or not, then it'll enable (if user has selected so) it. Same result. No flashing or writing to init.d needed. Root privileges usage should be kept at minimum.
This will be included in one of next versions.

New version available.
Code:
[b]v.0.0.3 | 28-07-2011[/b]
- option to set avs module to enabled on boot,
- user interface improvements,
- some minor code optimizations and cleanups,
- one bug traced and fixed.

Any chance for a version for DevNull?

laba82 said:
Any chance for a version for DevNull?
Click to expand...
Click to collapse
If devNull incorporates the same kernel (thalamus), then just try it and let us now if it works. If devNull has the same kernel as Oxygen and avsMod doesn't work, then please send me PM with logs and problem description. I'll look into this.

Afaik, DevNull uses the same kernel as Oxygen, 2.6.35.13-stable [email protected] #1.
Pressing Turn on AVS does nothing only says that avsMon has superuser rights.

laba82 said:
Afaik, DevNull uses the same kernel as Oxygen, 2.6.35.13-stable [email protected] #1.
Pressing Turn on AVS does nothing only says that avsMon has superuser rights.
Click to expand...
Click to collapse
Please, send me logs. I'll look into this.

Mine says its using 1300 mv and the frequency is 1mhz
Sent from my HTC Desire using XDA App

theyau said:
Mine says its using 1300 mv and the frequency is 1mhz
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Do you have AVS enabled? avsMon now tries to read cpu states even if avs is not enabled and this could provide to such values. It's normal and will be corrected in future version. Try to enable AVS and then check readings.
If AVS is enabled and avsMon still shows such readings, then please send me logs and describe all actions and steps you've made.

New version available:
Code:
[b]v.0.0.4 | 31-07-2011[/b]
- option to set maximum voltage (vdd_max),
- option to set minimum voltage (vdd_min),
- option to apply user-specified voltages on boot,
- user interface improvements,
- bug reported by theyau fixed,
- multilingual support (strings.xml cleanup, now ready for translations),
- about view modified - donate link added,

Yay my name is in the thread
Sent from my HTC Desire using XDA App

am using oxygen 2.1.6 with thalamus kernel, setting voltages doesnt work, have tried but its still reporting old voltages, im settingmin as 850 maximum as 950 (i know my phone can take it ) but its still reporting higher voltages.

dannylill1981 said:
am using oxygen 2.1.6 with thalamus kernel, setting voltages doesnt work, have tried but its still reporting old voltages, im settingmin as 850 maximum as 950 (i know my phone can take it ) but its still reporting higher voltages.
Click to expand...
Click to collapse
When you change minimum or maximum voltage, avsMon will write this new value to either vdd_min or vdd_max in /sys/module/avs/parameters/. The rest is up to kernel and avs module implementation. Basing on thalamus comments, it should read vdd_min/vdd_max in sysfs and use those values.
Values reported as cpu frequency and voltage status are taken from /sys/module/avs/parameters/status. And here is the same as with voltages. It's up to kernel and avs module to update this file in sysfs.
avsMon is just an interface to commands you'd normally have to write manually. Nothing more.
I haven't tested voltage settings much. They're implemented based on assumption, that "this should work, because avs should read those files in sysfs". Try to change voltages and then observe your power consumption. If your phone uses less mA than normally, then it's working. If not, then we should ask thalamus for his opinion, it's his kernel

thanks for the reply buddy, im not expecting miracles from the app, just letting you know. cool app, for all i know it could be working, just the reported values are wrong, ill see how it goes and if necessary, a word with thalamus to see if he can shed any light on it may be in order.

[ASK]Stripped Down Version of Android

The Question
Seeing how our device support multi-booting into several ROMs and a few weeks ago the HTC M8 came out. The M8 features an ultra battery saving mode by dumbing down the phone into only the essential function such as messaging and phone calls.
Is it possible to make a stripped-down version of AOSP/other custom ROM?
The ROM itself could only feature a few apps such as:
Messaging
Phone
Browser
Camera
Music Player
File Manager
Gallery
WiFi
Bluetooth
With the Location and Account Sync turned off also multi-tasking turned off (make only 1 app in background), this could save a lot of battery. Also since it won't need that much horse power to run the ROM, you can turn off a few cores to save battery even further. So if one day you're in need for a longer life battery but still want to use your phone, you can boot into this ROM.
The "Lite" ROM
So instead of waiting for someone to heavily strip down an Android ROM I tried the following:
Installed MultiROM
Add a new ROM
Flashed the ROM's zip file (Slimkat Build 4 Stable) without flashing the gapps afterward
Flashed Photosphere since I need it
Flashed a custom kernel (hellscore b44)
Booted into the "Lite" version of ROM and set things up.
Remove some apps that is not needed and added some apps that are needed
The result is the following, just a simple ROM with no widgets on the homescreen and only a few apps that do not have services running on background.
Spoiler
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Phone Settings:
Keep WiFi on during sleep = Always
WiFi Always Scanning = Off
Optimize WiFi = On
NFC = Off
Lock + Touch sound and vibration = Off
Runtime = ART
Background Process = Standard Limit (since it causes FC in Google Camera if you disabled background process)
All transtion effect = 0.5x to make it feel faster
Kernel Settings:
Min Core Online = 1
Max Core Online= 2
Cores boosted on touch = 2
Min Freq = 192 MHz
Max Freq = 1242 MHz
CPU Governor = intellidemand
GPU Governor = conservative
GPU Max Clock = 320 MHz
Sweep2Wake + Sweep2Sleep = On
The Test
Still coming

uchihakurtz said:
(1) multi-tasking turned off (make only 1 app in background), this could save a lot of battery.(2) Also since it won't need that much horse power to run the ROM, you can turn off a few cores to save battery even further. So if one day you're in need for a longer life battery but still want to use your phone, you can boot into this ROM.
Click to expand...
Click to collapse
(1)Developer Options ----> Background Process Limit (At most, 1 process)
(2) You can install a kernel(you obviously need custom recovery and root for that) Then you can set the Maximum and Minimum CPUs online. This can be achieved with ak latest kernel.
Sorry I couldn't answer the previous "demands", but those 2 can be achieved on a normal ROM.

Konstantinos said:
(1)Developer Options ----> Background Process Limit (At most, 1 process)
(2) You can install a kernel(you obviously need custom recovery and root for that) Then you can set the Maximum and Minimum CPUs online. This can be achieved with ak latest kernel.
Sorry I couldn't answer the previous "demands", but those 2 can be achieved on a normal ROM.
Click to expand...
Click to collapse
I know this can be done on normal ROMs, I used to turn off some cores with hellscore too but it ends up laggy but at least it charges faster -_-"
As for background process, it just kill the apps when it's on background, opening it again will start it up again which in opposite, decrease battery life if multi-tasking. Even if the limit is enabled, some services still runs, I tried sending Whatsapp and it still receives it thus service still running.
If devs can make like a S40/Java-like ROM and with our spec, it can last days on battery like the days of Nokia 3100. :laugh:

A) Don't use apps. Only use vital apps like SMS and Phone? (Imagine that you have Ultra saving mode?)
B) Set CPU to 192mhz - 1350mhz and Intellidemand
C) Don't use a lot of 3G - Set wifi to turn off on lock
D) Undervolt
E) DONT PLAY GAMES
F) Underclock GPU to 320mhz
G) Greenify all apps except Clock and Launcher
This should easily give you 5 hours of screen on time or at least 2-3 days on one charge.

Mashed_Potatoes said:
A) Don't use apps. Only use vital apps like SMS and Phone? (Imagine that you have Ultra saving mode?)
B) Set CPU to 192mhz - 1350mhz and Intellidemand
C) Don't use a lot of 3G - Set wifi to turn off on lock
D) Undervolt
E) DONT PLAY GAMES
F) Underclock GPU to 320mhz
G) Greenify all apps except Clock and Launcher
This should easily give you 5 hours of screen on time or at least 2-3 days on one charge.
Click to expand...
Click to collapse
Actually I flashed a new ROM (Slimkat) without flashing the gapps + hellscore b44 and added Hellscore Manager to tweak all the above, also in Developer Settings enabled "No Background Process". The size doesn't even reach 300mb. I haven't tested the battery life though. Anyone wanna try?
Sent from my blazing fast Nexus 4

Hey, and why dont you try to take the zip file from a rom and manually remove its unnecessary apks???
Also, I suggest you to flash a kernel... I used faux kernel... Great battery
This thread could be interesting for those who leave home for some days
EDIT: You can install the stripped down version of that rom with MultiROM so you can have access to all functionalities again with only one reboot

bamsbamx said:
Hey, and why dont you try to take the zip file from a rom and manually remove its unnecessary apks???
Also, I suggest you to flash a kernel... I used faux kernel... Great battery
This thread could be interesting for those who leave home for some days
EDIT: You can install the stripped down version of that rom with MultiROM so you can have access to all functionalities again with only one reboot
Click to expand...
Click to collapse
Yeah, actually that's what I did. So I have two ROMs intalled, 1. a full Slimkat version installed with gapps and all my 100 apps and games, and 2. a simplified Slimkat version where gapps are no more and some apps removed + a few basic apps that I use daily such as Opera Mini, XDA Forum, Hellscore Manager, and Android Central App, also the new Google Camera for taking pictures. No chatting apps installed at all.
I'll test how long it last since tomorrow I'll be travelling.

uchihakurtz said:
Yeah, actually that's what I did. So I have two ROMs intalled, 1. a full Slimkat version installed with gapps and all my 100 apps and games, and 2. a simplified Slimkat version where gapps are no more and some apps removed + a few basic apps that I use daily such as Opera Mini, XDA Forum, Hellscore Manager, and Android Central App, also the new Google Camera for taking pictures. No chatting apps installed at all.
I'll test how long it last since tomorrow I'll be travelling.
Click to expand...
Click to collapse
Please, post results when you are back... I am a battery saver enthusiast!!!

Sure thing bro but I'll only use the standard battery detail thing found on the Settings.
Sent from my Nexus 4

uchihakurtz said:
The size doesn't even reach 300mb. I haven't tested the battery life though. Anyone wanna try?
Sent from my blazing fast Nexus 4
Click to expand...
Click to collapse
Why dont you just delete some system and priv-app apks? My CM11 from 210 mb goes down to 140mb when I delete all those things. Even SlimRom and PA went down to 130. Battery life is ok with me. 1 day with ak's kernel.

Konstantinos said:
Why dont you just delete some system and priv-app apks? My CM11 from 210 mb goes down to 140mb when I delete all those things. Even SlimRom and PA went down to 130. Battery life is ok with me. 1 day with ak's kernel.
Click to expand...
Click to collapse
Yeah it's rather small so it doesn't significantly affect my main ROM. I don't want just one day, it's normal getting a day of use using hellscore. I want to test if an Android smartphone can achieve 3-4 days of use like the days where Nokia 3100 was still around.
So unfortunately I couldn't test a full whole day since I had some stuff I need to do on my main ROM, so I only used it for 3-4 hours. Battery was kinda good though, it only drops 2-3% surfing the internet on WiFi for 30 minutes with low brightness.
It took 20% of battery with 1 hour of screen on time which consist of 20 minutes of music through speaker, 30 minutes on full browser (WiFi), 15 minutes on Opera Mini (EDGE), and took 10 pictures with the camera. But I don't think that's good enough.
I'll post my phone and kernel settings on the first post, any suggestion on reducing battery life please tell. I'll try using the Slimkat Lite ROM until the battery dies when I'm fully charged again and post the result here.

AK Kernel Profile - Synapse

As the title suggests, this thread is for people to post their profiles with each other in an effort to not clog up the development thread. Synapse is a great tool with a ton of variations. Feel free to share what worked and what didn't.

jlevy73 said:
As the title suggests, this thread is for people to post their profiles with each other in an effort to not clog up the development thread. Synapse is a great tool with a ton of variations. Feel free to share what worked and what didn't.
Click to expand...
Click to collapse
now that's a good and wise idea
hope that Profile Save/Restore gets fixed for Synapse and we'll find here some interesting presets to test on from more experienced users
Thanks

I'll just list the things that I changed. Cause Synapse won't let me save profiles. Heard it's still being worked on So that's good news
CPU max frequency - 1574MHz
CPU Governor - interactive_pro
Intelliplug enabled with performance profile active. CPU max screen off at 729MHz. No undervolting yet
I/O -ROW with 1024 KB read-ahead.
Laptop mode enabled
There's way more stuff to tune and I'll play around with them when I have more time which will be in a week
I tried 1.2 GHz for a day and it was still smooth even on Facebook which is quite a surprise
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshot proves it all.
Cheers everyone and lets light up this thread with profiles and all
Sent from a Device codenamed Bacon!

funCrash93 said:
now that's a good and wise idea
hope that Profile Save/Restore gets fixed for Synapse and we'll find here some interesting presets to test on from more experienced users
Thanks
Click to expand...
Click to collapse
For me works like a charm...
Select your Profile then on the top press the checkmark. Then press the "Resore Selected Profile" Button. Now you will get a Toast with success loaded and "Restart Synapse".

Test was done with - CrDroid 5.5 ART.
CPU max frequency - 1574MHz
COU Multicore - Agressive
CPU Governor - Smartmax_eps
Intelliplug enabled with balanced profile active. CPU max screen off at 729MHz. 50 mV undervolting +-
I/O -Deadline with 1024 KB read-ahead.
GPU - 389MHz with Conservative
Laptop mode enabled
TCP Congestion - hybla
Fist half of the day, was heavy usage (playing Leo's Fortune), however I noticed a slighty higher battery drain, when my phone got hot (at earpiece, back&front) after 2hours +- ?.
Anyway, school day was over & I went home and did the usual light stuff, checking Facebook, Snapchat, writing messages on phone and over MightyText.
I'm satisfied so far. Going to try the interactive_pro next.
Idle: 5-7mV

now running @sien1996 's profile (except Max Screen Off Freq. : haven't set that one)
so far ok, will update later w/ Gaming Experience

Where can I find intelliplug option? I only see mpdecision under hotplug...

Chaplan said:
Where can I find intelliplug option? I only see mpdecision under hotplug...
Click to expand...
Click to collapse
It's in the hotplug tab right under mpdecision

sien1996 said:
It's in the hotplug tab right under mpdecision
Click to expand...
Click to collapse
Can't find it... Really can't. Does it say intelliplug?

Chaplan said:
Can't find it... Really can't. Does it say intelliplug?
Click to expand...
Click to collapse
Yeah. It's the one with the 'balanced' 'eco-performance' stuff. And the hysteris value and touch boost stuff. Don't even need to scroll, it's right there when you click hotplug.

Where can I find the Laptop mode option?

depends
Chaplan said:
Can't find it... Really can't. Does it say intelliplug?
Click to expand...
Click to collapse
sien1996 said:
Yeah. It's the one with the 'balanced' 'eco-performance' stuff. And the hysteris value and touch boost stuff. Don't even need to scroll, it's right there when you click hotplug.
Click to expand...
Click to collapse
i'm using synapse on several devices and kernels and thus have to bring to your attention that what you see there depends on the kernel while the kernel you can use and it's tunables depend partly on the device. that's one of the goals of synapse that it adapts to the available tunables, depending.
so i would suggest that you (finally) mention your config, kernel (probably AK ) and device and perhaps post a screenshot of the hotplug tab so we can see what's there and not and help further.
http://forum.xda-developers.com/attachment.php?attachmentid=2912743&stc=1&d=1409049574

Nexus 5 with uber sabermod faux...

that's it
Chaplan said:
Nexus 5 with uber sabermod faux...
Click to expand...
Click to collapse
looks like if this config simply does not provide the option to use intelliplug.
most people here are using AK-Kernel on OnePlus One so this config is not widely spread and thus, including myself, i cannot
not provide you with a lot of quality input but certainly you do not have that option. i think (read somethin in git) @ak will
sooner or later make a kernel for the hammerhead, perhaps @ak you would confirm or deny this assumption quickly
however, if that will be the case i recommend to use that kernel or elementalX which i'm currently using on my Nexus 5, which i'm using for 9 months now
with a few never lasting sidesteps to try others. by the way came from franco in late november 2013.

Faux sound problem for UKM is fixed ... Now all work like a champ ... And its free [emoji7][emoji7][emoji7][emoji7]
[email protected]

ak said:
Faux sound problem for UKM is fixed ... Now all work like a champ ... And its free [emoji7][emoji7][emoji7][emoji7]
[email protected]
Click to expand...
Click to collapse
How do I enable faux sound? Or is it already done?
Sent from my A0001 using Tapatalk

cashyftw said:
How do I enable faux sound? Or is it already done?
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Enabled under sound tab.
[email protected]

best i found for touch response
this profile is the best i found till now "WIP" to optimize the lack of responsiveness of the touchscreen, especially when double tapping to wake but in general as well.
battery consumption with these settings is around 2% in 9h 30' in idle, SOT is around 7h ( +/-30' ) depending on apps and radios mostly used.
as usual battery performance is relative to config, usage, radio signals etc. so the above serves as a clue. only tells what happens on my device.
[URL="https://www.dropbox.com/s/magnzah8lngy3k2/888.tgz?dl=0"]https://www.dropbox.com/s/magnzah8lngy3k2/888.tgz?dl=0
[/URL]
IMPORTANT NOTICE:
In the process of copying profile files from Dropbox and probably from other sources it occurs that the file name is changed to xxxx.tgz.gtar while to correct name MUST be xxxx.tgz, in this case that would be 888.tgz. if the file does not have this correct name before you try to restore it in synapse it will say: Invalid File further you have to check the "√" sign on top each time it appears, while upon restarting the app "Synapse" which you have to do from within the app not closing and re-opening the app. when the app has opened you have to non-intuitively hit "X" not "√"

magnamentis said:
this profile is the best i found till now "WIP" to optimize the lack of responsiveness of the touchscreen, especially when double tapping to wake but in general as well.
battery consumption with these settings is around 2% in 9h 30' in idle, SOT is around 7h ( +/-30' ) depending on apps and radios mostly used.
as usual battery performance is relative to config, usage, radio signals etc. so the above serves as a clue. only tells what happens on my device.
https://www.dropbox.com/s/magnzah8lngy3k2/888.tgz?dl=0
IMPORTANT NOTICE:
In the process of copying profile files from Dropbox and probably from other sources it occurs that the file name is changed to xxxx.tgz.gtar while to correct name MUST be xxxx.tgz, in this case that would be 888.tgz. if the file does not have this correct name before you try to restore it in synapse it will say: Invalid File further you have to check the "√" sign on top each time it appears, while upon restarting the app "Synapse" which you have to do from within the app not closing and re-opening the app. when the app has opened you have to non-intuitively hit "X" not "√"
Click to expand...
Click to collapse
Thanks, will give this a try with the new 0.33 build that just got posted.

magnamentis said:
this profile is the best i found till now "WIP" to optimize the lack of responsiveness of the touchscreen, especially when double tapping to wake but in general as well.
battery consumption with these settings is around 2% in 9h 30' in idle, SOT is around 7h ( +/-30' ) depending on apps and radios mostly used.
as usual battery performance is relative to config, usage, radio signals etc. so the above serves as a clue. only tells what happens on my device.
https://www.dropbox.com/s/magnzah8lngy3k2/888.tgz?dl=0
IMPORTANT NOTICE:
In the process of copying profile files from Dropbox and probably from other sources it occurs that the file name is changed to xxxx.tgz.gtar while to correct name MUST be xxxx.tgz, in this case that would be 888.tgz. if the file does not have this correct name before you try to restore it in synapse it will say: Invalid File further you have to check the "√" sign on top each time it appears, while upon restarting the app "Synapse" which you have to do from within the app not closing and re-opening the app. when the app has opened you have to non-intuitively hit "X" not "√"
Click to expand...
Click to collapse
Running this profile now, downloaded properly without the need to change the file name. Proper feedback soon.
Oneplus one/PA 4.5 beta 3/AK

Advanced Interactive Governor Tweak (thanks SoniCron & xSilas43)(+ Battery Tips)

Big thanks and All Credits to @soniCron, @xSilas43, @kraatus90, and @Vinnom
Usual Disclaimer
Code:
/* *** Disclaimer
* Your Warranty is now Void!
* Others and I are not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app failed. Please do some research
* if you have any concerns about these kernel tweaks
* before implementing them! YOU are choosing to make these modifications, and if
* you point the finger at me or other's mentioned for messing up your device, I will laugh at you.
*/
Original thread is below by @soniCron and additional tweaks by @xSilas43.
- Settings in that thread are meant for Nexus 5X and Nexus 6P but he provides a guide that should be understood thoroughly.
- Do Not Forget To Give THANKS To Both. Worked with me on understanding process and settings.
Warning: Read the original post and understand. Settings I provide further down are perfected for my use and Moto X. Further tweaking might be needed on your end.
http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
---------------------------------------------------------------------------------------------------------------------------------
For Our Moto X (2nd Generation):
[Please read everything below at least TWICE]
Warning:
1. Read above "the line (-----)" if haven't already
2. Settings are CM13 based
3. Other ROM and Kernel, settings and frequencies could differ (see above linked thread for how to determine appropriate settings)
What's need
1. Root (duh!)
2. Backup up ROM using TWRP
3. Store Backup somewhere safe
4. Kernel Adiutor or similar (to change kernel settings)
5. Make changes as below (be sure to toggle "Apply on Boot" at sections used)
6. Reboot into TWRP
7. In TWRP file manager, backup and move (or delete) power.msm8974.so file. Located in system/vendor/lib/hw/power.msm8974.so or system/lib/hw/power.msm8974.so. (CM13 won't let changes like go_highspeed_load otherwise)(need to do this everytime you flash a new nightly)
8. Reboot, wait about 30s, go into Kernel Adiutor and verify settings
Settings Beta (based on @soniCron's Ghostpepper v1.1 and @xSilas43's DarkSpiceBeta)
Above_HighSpeed_Delay:50000 652800:60000 883200:20000
Go_HighSpeed_Load: 200
HiSpeed_Frequency: 300000
Min_Sample_Time: 70000
Target_Loads: 98 300000:64 422400:55 652800:12 729600:74 883200:9 960000:83 1036800:15 1190400:85 1267200:18 1497600:86 1574400:10 1728000:13 1958400:16 2265600:99 2457600:100
Timer_Rate:50000
Time_Slack:-1
io_is_busy:0
Max_Frequency_hysteresis:0
Boostpulse_duration:0
CPU Boost:
Interval- 0
Sync Threshold- Disabled
Input Interval: 0
Input Boost Frequency- Disabled for all cores (everytime reboot will have to change, it doesn't stick reboots).
I/O Scheduler- fiops (BFQ might be good (CM team keeps it updated and better for multitasking))
Read Ahead-1024kB
GPU:
Governor- simple ondemand
Click to expand...
Click to collapse
Settings 1Alpha (more aggressive than Beta)
Above_HighSpeed_Delay:50000 729600:60000 1036800:20000
Target_Loads: 98 300000:64 422400:55 652800:12 729600:21 883200:83 960000:83 1036800:15 1190400:85 1267200:18 1497600:86 1574400:10 1728000:13 1958400:16 2265600:99 2457600:100
Everything else same as Beta
Click to expand...
Click to collapse
Settings 2Alpha (more conservative than Beta)
Above_HighSpeed_Delay:50000 729600:60000 883200:20000
Target_Loads: 98 300000:64 422400:55 652800:81 729600:21 883200:9 960000:83 1036800:15 1190400:85 1267200:18 1497600:86 1574400:10 1728000:13 1958400:16 2265600:99 2457600:100
Everything else same as Beta
Click to expand...
Click to collapse
If running @kraatus90's kernel (stock ROM) try @Vinnom's setting first (http://forum.xda-developers.com/showpost.php?p=65346117&postcount=11). My settings would need modified.
Notes:
1. Still a work in progress
2. Goal is to use most power to voltage efficient frequencies, determined to be 1574400 on research elsewhere
3. Adjust as needed using guidance from @soniCron's thread linked in above section
Respond how it works. Better battery? Worse Battery? Smooth? Lag?

Improving Stationary idle drain (doze).
Big Thanks and All Credits to @p0isonra1n and @Arstoien
- Do Not Forget To Give THANKS To Both.
Usual Disclaimer
Code:
/* *** Disclaimer
* Your Warranty is now Void!
* Others and I are not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app or other important functions failed. Please do some research
* if you have any concerns about these Doze settings
* before implementing them! YOU are choosing to make these modifications, and if
* you point the finger at me or other's mentioned for messing up your device, I will laugh at you.
*/
What's need:
1. Doze Settings Editor (http://forum.xda-developers.com/android/apps-games/root-doze-settings-editor-android-t3235130)
2. Knowledge of various "Doze Settings Editor" settings and flow of Doze. Helpful in fine tuning settings to you. Summarized by @Arstoien here (http://forum.xda-developers.com/showpost.php?p=63962529)
@Arstoien's recommended settings
Arstoien said:
Here's what I use (in seconds):
inactive to – 900 (15 min)
sensing to – 20
locating to – 0
location accuracy – 20.0
motion inactive to – 900 (=15 min)
idle after inactive to – 0 (after sensing and locating are passed, don't wait further)
idle pending to – 150
max idle pending to – 600
idle pending factor – 2
idle to – 1800 (=30 min)
max idle to – 21600 (=6 hrs)
idle factor – 2
min time to alarm – 900 (=15 min)
max temp app whitelist duration – 120
mms temp app whitelist duration – 60
sms temp app whitelist duration – 20
things I'd consider changing depending on usage:
inactive to – depending on how often you turn on the screen. Generally my idea is that if I haven't turned it on for 15 min, I probably won't do so again any time soon.
motion inactive to – this timeout basically does this: after the device has detected movement (either from Sensing state or from Idle), it'll wait this much before using the sensors again to check for motion. So if you move a lot, increase the value for better battery. If you don't move a lot, decrease for better battery.
idle pending to – if you have apps that sync media, or other big files, you may want to increase this. I think Titanium Backup, or other similar apps, will need much more time to do scheduled backups, so keep that in mind also. Otherwise one minute seems to be enough for most apps to do their job. You can use 2–3 minutes + a little higher max_idle_pending_to, to be on the safe side, if you're worried. I don't think it'll make that much of a difference.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=64810397&postcount=954
Notes:
1. Have not had time to work on different settings yet. Using @Arstoien's recommended settings until then.
2. Will see better idle battery if tweaked to your usage tendancies. See Step 2 of "What's Need" above.

Additional
Usual Disclaimer
Code:
/* *** Disclaimer
* Your Warranty is now Void!
* Others and I are not responsible for bricked devices, dead SD cards, thermonuclear war,
* or you getting fired because the alarm app or other important functions failed. Please do some research
* if you have any concerns about these additional settings
* before implementing them! YOU are choosing to make these modifications, and if
* you point the finger at me or other's mentioned for messing up your device, I will laugh at you.
*/
Screen Calibration (remove yellow (warmness))
Thanks and All Credits to @wrinklefree (http://forum.xda-developers.com/showpost.php?p=59092146&postcount=3017)
Warning: These are meant for the Nexus 6. It shares same generation Samsung AMOLED as Moto X.
1. CM13: In Settings -- Display -- Live Display. Change Display Mode to Disable all Adjustments (possibly could leave on)
2. Kernel Adiutor -- Screen
3. Toggle Apply on Boot
4. Red to 32125
5. Green to 32125
6. Blue to 32768
Notes:
1. Still on warm side. Not as extreme as stock.

Trying now, thanks
FYI, I couldn't get to power.msm8974.so from the TWRP file manager, so I just booted up and used the CM File Manager. Had to redo the kernel settings and restart, see how it is.

jmsfang said:
Trying now, thanks
FYI, I couldn't get to power.msm8974.so from the TWRP file manager, so I just booted up and used the CM File Manager. Had to redo the kernel settings and restart, see how it is.
Click to expand...
Click to collapse
Important make sure Go_HighSpeed_Load doesn't reset to 50. It usually happens when the screen is turned off for about 10s and back on. If you removed power.msm8974.so it shouldn't reset.
Also remember Input Boost Frequency should be disabled for all cores. It needs to be set whenever you reboot. For whatever reason it doesn't stick through reboots.
Use an app like BetterBatteryStats to monitor the CPU frequencies. It will determine if there is a problem.

Thanks, I checked and everything is running accordingly
I usually use my phone for music (bluettooth speakers) and I've noticed that with this setup, google play music tends to hiccup particularly when the song is about to change. Any idea on how I can narrow that down?

jmsfang said:
Thanks, I checked and everything is running accordingly
I usually use my phone for music (bluettooth speakers) and I've noticed that with this setup, google play music tends to hiccup particularly when the song is about to change. Any idea on how I can narrow that down?
Click to expand...
Click to collapse
1. Did you change the Doze settings? If so reset back to original. See if issue persists.
2. Did you change I/O Scheduler to FIOPS? Try changing to BFQ. See if issue persists.
3. Using Kernel Adiutor. Go to frequency table and reset timing. See what the frequency is like while playing music at that spot.
4. Try changing first number in Above_HighSpeed_Delay from 50000 to 45000. See if issue persists. If issue persists try 40000. See if issue persists.
5. If does we have to modify your Target_Loads values.

Visi0nofExcellence2 said:
1. Did you change the Doze settings? If so reset back to original. See if issue persists.
2. Did you change I/O Scheduler to FIOPS? Try changing to BFQ. See if issue persists.
3. Using Kernel Adiutor. Go to frequency table and reset timing. See what the frequency is like while playing music at that spot.
4. Try changing first number in Above_HighSpeed_Delay from 50000 to 45000. See if issue persists. If issue persists try 40000. See if issue persists.
5. If does we have to modify your Target_Loads values.
Click to expand...
Click to collapse
Thank you for all the help!
I'll work through these suggestions, it'll probably take a few days to test them all thoroughly. I'll let you know what I find
Thank you again for your help!

Anyone experiencing same Bluetooth issues as @jmsfang?
Would like to verify if single or widespread issue.

Can i use it into Kraatus90's v3 kernel?

WOW man! I liked the idea of sharing our profiles here, as we can get more views and spread the word.
I'm still trying to balance better my settings, and I'm getting good performance and apparently, better battery saving (not confirmed yet, has to test more).
I'll share things here, so ppl can try other settings to, if they want.
Guys with hiccups problems, I suggest you to take a look at my profile.
Ah, I didn't test your suggestion for Doze settings yet. I'll try from now ^^
Download here
To apply my profile, just save it somewhere (lets say /sdcard/ to keep it simple), then run in terminal emulator:
su -c "sh /sdcard/profile"

Updates-
1. Updated Interactive Governor Tweaks (Beta)
2. Added additional Interactive Governor Tweaks (Alpha1 and Alpha2)
3. Added Screen Calibration Settings (http://forum.xda-developers.com/showpost.php?p=65339931&postcount=3)
4. If running Kraatus90's kernel (stock ROM) try Vinnom's setting first (http://forum.xda-developers.com/showpost.php?p=65346117&postcount=11). My settings would need modified a bit.

I forgot the Above High Speed Delays for the Alphas. Added to OP. Make corrections if used either Alpha1 or Alpha2.

Have you tried MadDog? I was actually using that config before this, I think out of all (4?) of them, that one was best for me.

jmsfang said:
Have you tried MadDog? I was actually using that config before this, I think out of all (4?) of them, that one was best for me.
Click to expand...
Click to collapse
Yes; tried all. I stopped using it couldn't tell you why. Goal is find what works best for you. My configs work best for me and aren't the end all.

I think I could balance good enough my settings.
download.
Here is what I could get:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Enviado de meu XT1097 usando Tapatalk

Vinnom said:
I think I could balance good enough my settings.
download.
Here is what I could get:
Click to expand...
Click to collapse
Your governour is just using full time full speed, because of mistakes in file.

heineken78 said:
Your governour is just using full time full speed, because of mistakes in file.
Click to expand...
Click to collapse
In fact, it wasn't using full time full speed. At least, "time in state" told me it. The most time was spent at 268 MHz, later at 1038 and later 1728 (tha max I set).
I noticed that min_freq was written wrong, fixed it, but now I can't nothing more. My phone is hard bricked and I don't know when I'll have another

This is random, srry...
Visi0nofExcellence2 said:
Updates-
1. Updated Interactive Governor Tweaks (Beta)
2. Added additional Interactive Governor Tweaks (Alpha1 and Alpha2)
3. Added Screen Calibration Settings (http://forum.xda-developers.com/showpost.php?p=65339931&postcount=3)
4. If running Kraatus90's kernel (stock ROM) try Vinnom's setting first (http://forum.xda-developers.com/showpost.php?p=65346117&postcount=11). My settings would need modified a bit.
Click to expand...
Click to collapse
Hi, I understand that you guys hav the moto x 2014, and I really feel like there is potential for these interactive settings to also help the moto x pure(2015). I hav been reading the sonicron thread and have applied the Nexus 5x eclipse profile, apparently the profile with the best battery. And it has been a alright not that great really, but can you guys help me what interactive values are best for the new moto x, I am trying hard to understand, but I don't know, thanks a lot..

harshi1 said:
Hi, I understand that you guys hav the moto x 2014, and I really feel like there is potential for these interactive settings to also help the moto x pure(2015). I hav been reading the sonicron thread and have applied the Nexus 5x eclipse profile, apparently the profile with the best battery. And it has been a alright not that great really, but can you guys help me what interactive values are best for the new moto x, I am trying hard to understand, but I don't know, thanks a lot..
Click to expand...
Click to collapse
Moto X Pure (2015) uses Snapdragon 808, same chip as Nexus 5x. We do not have that chip, it is hard to help. Try original Nexus 5x thread.