Now I haven't seen this anywhere while trying to find a fix so I may possibly be sharing a new idea.
I know that we already have Greenify and such apps to extend our phones battery life, but what I find is that in some way or another they reduce the overall performance of it.
My idea is to create a Tasker profile where the phone runs at normal performance during screen on but recognises when the display is locked and reduces the CPU speed to its minimum, because surely being at anything more is a waste of CPU energy?
I have created a profile that's activated by a display off event, followed by a System >> CPU task called "Lower CPU" that reduces the max frequency to the value of min frequency.
When activated it does lower the speed while the screen is off, but once I turn the screen back on it takes a reboot to get the cores speed to increase again even if I turn off the Tasker profile.
It won't allow me to create an exit task for an event context so do I need to create a new profile to raise the CPU speed in an event of a screen on? Or is there a way to use a plugin like Trickster Mod to lower and raise it instead?
Apologies for it being so long, I'm not sure if I'm making it more complicated? But help please!
Thank you!
P.s - the images are screenshots of CPU-Z 1. Before locking the screen. 2. Immediately after unlocking the phone 3. About 2 minutes after unlocking the phone and it just doesn't return to normal
AJHylton said:
Now I haven't seen this anywhere while trying to find a fix so I may possibly be sharing a new idea.
I know that we already have Greenify and such apps to extend our phones battery life, but what I find is that in some way or another they reduce the overall performance of it.
My idea is to create a Tasker profile where the phone runs at normal performance during screen on but recognises when the display is locked and reduces the CPU speed to its minimum, because surely being at anything more is a waste of CPU energy?
I have created a profile that's activated by a display off event, followed by a System >> CPU task called "Lower CPU" that reduces the max frequency to the value of min frequency.
When activated it does lower the speed while the screen is off, but once I turn the screen back on it takes a reboot to get the cores speed to increase again even if I turn off the Tasker profile.
It won't allow me to create an exit task for an event context so do I need to create a new profile to raise the CPU speed in an event of a screen on? Or is there a way to use a plugin like Trickster Mod to lower and raise it instead?
Apologies for it being so long, I'm not sure if I'm making it more complicated? But help please!
Thank you!
P.s - the images are screenshots of CPU-Z 1. Before locking the screen. 2. Immediately after unlocking the phone 3. About 2 minutes after unlocking the phone and it just doesn't return to normal
Click to expand...
Click to collapse
I understand what you're getting at, but it's really not necessary to do such a thing. CPU cores clock down and all cores except for core0 usually shut down when the phone goes into sleep mode, so the amount of battery you're saving is negligible doing this. If your phone is running hot while the screen is off, then you likely have wakelock issues and that's something separate you need to tackle.
MishaalRahman said:
I understand what you're getting at, but it's really not necessary to do such a thing. CPU cores clock down and all cores except for core0 usually shut down when the phone goes into sleep mode, so the amount of battery you're saving is negligible doing this. If your phone is running hot while the screen is off, then you likely have wakelock issues and that's something separate you need to tackle.
Click to expand...
Click to collapse
Ohh I see, thank you for explaining. I would have thought that this would be implemented somewhere as otherwise it would have been a clear battery drain but I thought I'd double check lol
Doze Mode
What version of Android are you running? If you're on Marshmallow, adjusting the CPU may not be necessary as it has Doze mode and using either Naptime or Doze Settings Editor and adjusting the settings can defintely increase battery life when the device is sleeping.
If not, I suggest using PowerNap with Xposed and Greenify.
In fact, Greenify has Tasker integration so you can set it to hibernate apps upon screen off situations.
Of course, all the apps I listed need root access...
Another helpful resource to help with power saving can be found at http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
You will have to adjust it based on your device and kernel of course, but I've experinced great power savings using a combination all I've mentioned
Ozonethegreat said:
What version of Android are you running? If you're on Marshmallow, adjusting the CPU may not be necessary as it has Doze mode and using either Naptime or Doze Settings Editor and adjusting the settings can defintely increase battery life when the device is sleeping.
If not, I suggest using PowerNap with Xposed and Greenify.
In fact, Greenify has Tasker integration so you can set it to hibernate apps upon screen off situations.
Of course, all the apps I listed need root access...
Another helpful resource to help with power saving can be found at http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557
You will have to adjust it based on your device and kernel of course, but I've experinced great power savings using a combination all I've mentioned
Click to expand...
Click to collapse
Alright thank you for that, I'll take a look at those. I'm currently using a Oneplus Two on OxygenOS 2.2 which is based on KitKat. I have been looking at Xposed modules as that's what really made me root this phone but apparently I need to go through steps to make SeLinux permissive because at the moment nothing from Xposed works. And considering yesterday I spent hours unbricking this phone, I'm going to stop fiddling with it for a little while :laugh:
AJHylton said:
Alright thank you for that, I'll take a look at those. I'm currently using a Oneplus Two on OxygenOS 2.2 which is based on KitKat. I have been looking at Xposed modules as that's what really made me root this phone but apparently I need to go through steps to make SeLinux permissive because at the moment nothing from Xposed works. And considering yesterday I spent hours unbricking this phone, I'm going to stop fiddling with it for a little while :laugh:
Click to expand...
Click to collapse
You can set SeLinux to permissive using the code below in your terminal app or adb shell (found here):
Code:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
Or if that's too much for ya, SeLinuxModeChanger works as well. Keep in mind that Google marks this as harmful but that's only because they don't want to changing SeLinux.
Ozonethegreat said:
You can set SeLinux to permissive using the code below in your terminal app or adb shell (found here):
Code:
su
mount -o remount,rw /system
mkdir /system/su.d
echo "#!/system/bin/sh" > /system/su.d/permissive.sh
echo "setenforce 0" > /system/su.d/permissive.sh
echo "0" > /sys/fs/selinux/enforce
chmod 755 /system/su.d/permissive.sh
Or if that's too much for ya, SeLinuxModeChanger works as well. Keep in mind that Google marks this as harmful but that's only because they don't want to changing SeLinux.
Click to expand...
Click to collapse
I have actually tried the SELinuxModeChanger to change it and when I run 'getenforce' in Terminal it says permissive but Xposed still doesn't work even then. The steps I was told to try are http://forum.xda-developers.com/oneplus-2/general/guide-disable-selinux-to-allow-xposed-t3331105 which seems a little more intense lol.
I'm going to try the code now and see if that works, if it doesn't is it likely that that's not what's stopping Xposed from working?
Update: I tried the code and running getenforce on the terminal says permissive but the Xposed modules still dont have any effect when activated
AJHylton said:
I have actually tried the SELinuxModeChanger to change it and when I run 'getenforce' in Terminal it says permissive but Xposed still doesn't work even then. The steps I was told to try are http://forum.xda-developers.com/oneplus-2/general/guide-disable-selinux-to-allow-xposed-t3331105 which seems a little more intense lol.
I'm going to try the code now and see if that works, if it doesn't is it likely that that's not what's stopping Xposed from working?
Update: I tried the code and running getenforce on the terminal says permissive but the Xposed modules still dont have any effect when activated
Click to expand...
Click to collapse
Strange. Both worked for me and I've had no problems. Might be the rom you're running. I'm not sure.
this entire thing could be achieved with a init.d script which I used to use back in 2012.
Screen off- powersave governor...
screenon- normal governor
coming from the note 4 edge to the note 7 I have grown accustomed to an actual edge panel and miss it greatly. i cant stand that i have to choose a specific location for the panel to reside rather than being able to swipe from anywhere...
i have already increased the size to its max so i know it shouldnt be more than a few lines of code to make it even larger... but how possible is it?
something that xpose could tackle or would the bootloader need to be unlocked with a modded ROM?
We're talking bootloader unlocked status here
Hey guys,
I am using the default OS that comes with the Huawei P10, and my phone is not rooted.
After the update to Android 9.0 with EMUI9 the pull down menu (quick menu from notification bar) is unbearable large. It seems like there are different DPI settings for the pull down menu only.
I actually can not stand the large icons, so normally I change to DPI 430 and/or change the size of text/display in the display settings.
However, it seems this does not have any impact anymore on the pull down menu.
Does anyone experience the same and has any idea how to fix this?
Markus
markus985 said:
Hey guys,
I am using the default OS that comes with the Huawei P10, and my phone is not rooted.
After the update to Android 9.0 with EMUI9 the pull down menu (quick menu from notification bar) is unbearable large. It seems like there are different DPI settings for the pull down menu only.
I actually can not stand the large icons, so normally I change to DPI 430 and/or change the size of text/display in the display settings.
However, it seems this does not have any impact anymore on the pull down menu.
Does anyone experience the same and has any idea how to fix this?
Markus
Click to expand...
Click to collapse
It is same for me and unfortunately it is default setting. I didn't try to modify anything with root yet but i seriously doubt that it is even possible to do something like that.
Same here. The dpi wont stick. I hope its just a bug. Not some crappy implementation from huawei.
How can I activate vibration intensity on this phone? If I go to settings > sounds and vibration, the option is not there!
you cant
loop4444 said:
you cant
Click to expand...
Click to collapse
Really? Why is that? It's such a basic function...
Really SAMSUNG?? Just bought that phone - attempt to rehome from Xiaomi and this is the first thing I find.. but there is more. Xiaomi offers more granular android configuration out of the box - battery icons, performance and battery settings/optimization, resolution change (dpi).. when I opened settings on this phone I was quite shocked how limited it is..
Just to confirm - bottom line is Samsung knows about this limitation and has no interest to provide phone with proper interface since it is from mid-range family??
hello people
i really need help with my signal
i need to know how to adjust the mobile signal throught the hidden menu
please
thank you
Hi These settings can be activated with the code * # * # 4636 # * # *
Does it make a difference?
Sage said:
Does it make a difference?
Click to expand...
Click to collapse
Yes it does. You can neglect certain types of signals or approve others. If that is not properly set for your xarrier, it drains a lot of battery and it will make your signal weak/slow
Sage said:
Does it make a difference?
Click to expand...
Click to collapse
In fact this "menu" is available natively on OnePlus device, Xiaomi as just a "prefered" network option 5G > 4G > 3G" so the signal is not really optimized and switch often for nothing.
For exemple if you take in Xiaomi only prefered 4G you will have (in my case) :
GSM/WCDMA/LTE
And no... It's better to put * # * # 4636 # * # * and select
LTE/WCDMA/GSM
For a better LTE stability (priotity), you can also choose "LTE" only, depend your location it's useful, above all if you have VoLTE/VoWiFi