I know that there is currently no option to disable it, but maybe this will be implemented as it makes sense.
In non-root mode, every time I hibernate apps, the screen that tells me I need to force stop or enable automation comes up.
I learned that I need to press force stop, and I don't want automation because it runs in background, eating RAM.
Moreover, on a tablet, the nag screen covers a part of the force stop button.
Could an option to disable that screen over and over again be provided?
Thank you.
nick_white said:
I know that there is currently no option to disable it, but maybe this will be implemented as it makes sense.
In non-root mode, every time I hibernate apps, the screen that tells me I need to force stop or enable automation comes up.
I learned that I need to press force stop, and I don't want automation because it runs in background, eating RAM.
Moreover, on a tablet, the nag screen covers a part of the force stop button.
Could an option to disable that screen over and over again be provided?
Thank you.
Click to expand...
Click to collapse
When you enable automation, the app will close and will not run in the background. It only automates your action of force closing it.
tnsmani said:
When you enable automation, the app will close and will not run in the background. It only automates your action of force closing it.
Click to expand...
Click to collapse
I wasn't talking about the app I want to hibernate, I was talking about Greenify itself running in the background if I enable automation (see in my screenshot).
Keeping 47 MB of RAM for Greenify all the time for a few times when I want to manually hibernate apps just doesn't make sense... after all, one of it's (main) goals is freeing resources.
If I'm fine manually pressing "Force stop" (the alternative being to sacrifice 47 MB of RAM), then I shouldn't be nagged every time I do it to enable automation (I got the picture the first time.... no, thank you) . This is why there sould be an option to dismiss that "warning".
nick_white said:
I wasn't talking about the app I want to hibernate, I was talking about Greenify itself running in the background if I enable automation (see in my screenshot).
Keeping 47 MB of RAM for Greenify all the time for a few times when I want to manually hibernate apps just doesn't make sense... after all, one of it's (main) goals is freeing resources.
If I'm fine manually pressing "Force stop" (the alternative being to sacrifice 47 MB of RAM), then I shouldn't be nagged every time I do it to enable automation (I got the picture the first time.... no, thank you) . This is why there sould be an option to dismiss that "warning".
Click to expand...
Click to collapse
47MB seems high. For me, it is 24MB only. And I always have >1GB free
nick_white said:
I wasn't talking about the app I want to hibernate, I was talking about Greenify itself running in the background if I enable automation (see in my screenshot).
Keeping 47 MB of RAM for Greenify all the time for a few times when I want to manually hibernate apps just doesn't make sense... after all, one of it's (main) goals is freeing resources.
If I'm fine manually pressing "Force stop" (the alternative being to sacrifice 47 MB of RAM), then I shouldn't be nagged every time I do it to enable automation (I got the picture the first time.... no, thank you) . This is why there sould be an option to dismiss that "warning".
Click to expand...
Click to collapse
"3 processes" looks unusual, could you please capture another screenshot in the detail screen showing which 3 process in use?
Anyhow, I'm planning to remove that floating screen in the next major version.
oasisfeng said:
"3 processes" looks unusual, could you please capture another screenshot in the detail screen showing which 3 process in use?
Click to expand...
Click to collapse
Yes (attached).
It looks like Google Services bloats it up.
Can we disable those background usage reportings? Apart from free memory, they're the reason we're using Greenify in the first place.
Thanks.
nick_white said:
Yes (attached).
It looks like Google Services bloats it up.
Can we disable those background usage reportings? Apart from free memory, they're the reason we're using Greenify in the first place.
Thanks.
Click to expand...
Click to collapse
Does them linger for a long time, or just in a short time?
I hardly noticed them within in Greenify, but it definitely worth a further observation.
oasisfeng said:
Does them linger for a long time, or just in a short time?
I hardly noticed them within in Greenify, but it definitely worth a further observation.
Click to expand...
Click to collapse
I have one service and three processes running. Nothing connected to Google. See the screenshots.
tnsmani said:
I have one service and three processes running. Nothing connected to Google. See the screenshots.
Click to expand...
Click to collapse
It's 3 services in one process as showed in the screenshot, not 3 processes.
Related
Ok I have looked around and have not found the answer. SO here Goes
In windows if you want to keep the memory that you have clear of background applications, you can run system configuration and just remove the check-mark for those items you dont want to auto start.
I have Advanced Task Killer installed and will set it up to auto kill and will manual kill apps as well. Instead of consistently looking at ATK to shut down apps, is there a way to just keep all the apps you not using nor have ever started from suddenly being there and sucking the life out of your battery?
Having applications "running" in the background (i.e., still in memory but in a suspended state) does NOT negatively affect your battery life. These applications are actually just remaining in memory because that memory does not need to be used by anything else at the moment. If an active application gets to a point where it needs more memory, Android will automatically close applications that are in a suspended state (i.e., not actively being used) to make room.
In other words, using an app killer is NOT necessary and I definitely recommend NOT using one. By closing the application repeatedly, you are just causing the application to take a longer amount of time to start up next time you use it. You're making your Android experience worse by using one, not better.
There is one caveat to this, and that is when you have an application installed that doesn't play nicely -- i.e., even when you stop using that application, it will continue to use up CPU cycles (never go into a suspended state). This is actually pretty rare unless you are installing really poorly written programs, but it can happen to some popular apps too (usually the result of a bug). In this case, you should either uninstall that application or use an app killer to only kill that one app.
I've heard both sides of this argument, and don't know who to believe. I didn't think I needed a Task Killer, but then I saw it repeatedly on "top 10 apps for Android" and "must have Android apps" lists from respected sites like cnet... who to believe?!
Cnet ≠ respected
Sent from my Liberty using XDA App
drumist said:
Having applications "running" in the background (i.e., still in memory but in a suspended state) does NOT negatively affect your battery life.
Click to expand...
Click to collapse
I need to confirm this. Anyone? I dont care about memory because I bet Android excels at that, and at any rate, memory is there to be used, not to keep it empty.
But I come from a Symbian smartphone and "minimized" applications DO uses battery. Maybe little, but noticeable.
Anyone can confirm that background apps consume negligible battery juice?
Additionally, is there a nice task changer? Like windows Alt+Tab. I feel my Android like an iPhone, that I need to press the home button to move to another already opened app and that's just plain stupid. So far I'm using Multitasking Lite, but it can get sluggish once there are too many apps opened. Any suggestion would be warmly welcomed.
"Running" background apps DO NOT consume battery life unless they're actively syncing. If it's just in the memory saving the state of the app then that is fine.
As far as using a task killer, if you are manually killing apps and they keep starting back up then that is a bad thing for your battery. The app uses cpu cycles everytime it starts up again and syncs data. You can use a task killer to close apps that opened on startup or when you're done with them. If they stay closed until you choose to open them again then you're saving memory, but nothing to do with battery life.
ocswing said:
"Running" background apps DO NOT consume battery life unless they're actively syncing. If it's just in the memory saving the state of the app then that is fine
Click to expand...
Click to collapse
Thanks for confirming ;]
Darius_bd said:
Additionally, is there a nice task changer? Like windows Alt+Tab. I feel my Android like an iPhone, that I need to press the home button to move to another already opened app and that's just plain stupid. So far I'm using Multitasking Lite, but it can get sluggish once there are too many apps opened. Any suggestion would be warmly welcomed.
Click to expand...
Click to collapse
Obviously you can switch over to some apps by pulling down the notification menu and selecting the appropriate app. That only works on apps that put themselves in the notification menu though (multimedia apps and things like Google Nav usually do this).
Otherwise, you can press and hold the home button to bring up the list of 8 most recently opened apps without exiting the active app. This works but like I said, it's the 8 most recent apps, so it will list apps that aren't necessarily still running anymore. It's more of a shortcut to having to go search in your apps menu or home screens to find a recent app than a way to see what is currently running.
drumist said:
Otherwise, you can press and hold the home button to bring up the list of 8 most recently opened apps without exiting the active app. This works but like I said, it's the 8 most recent apps, so it will list apps that aren't necessarily still running anymore. It's more of a shortcut to having to go search in your apps menu or home screens to find a recent app than a way to see what is currently running.
Click to expand...
Click to collapse
What can I say, I hate pressing the home key to hunt for the icon that opens the app I already opened more than 6 other apps ago ;] Guess I'll stick to Multitasking Lite for the time being. Thanks!
I just discovered that you can get rid of apps from the recent apps menu (the square button next to the home button) by swiping them to the side. I don't know why this makes me so retardedly happy, but I am sure that SOMEONE else out there will also appreciate this tidbit of information.
Anyone else have any nuggets of joy to share?
I liked that trick also when I first found out. Another thing too is that you can hold down the app in recent menu and a quicksetting will come up to let you remove it from list or look at app info.
Remember though, this only removes it from recent apps list. It doesn't close down the app itself.
Does it really matter though performance wise? I Always thought Android puts background apps into an "idle" state where they dont take up any resources until used? Although it is cool for people with OCD like me
demandarin said:
I liked that trick also when I first found out. Another thing too is that you can hold down the app in recent menu and a quicksetting will come up to let you remove it from list or look at app info.
Remember though, this only removes it from recent apps list. It doesn't close down the app itself.
Click to expand...
Click to collapse
Yes it does close the app. It just doesn't close background processes of the app.
Swiping an app from recent apps menu removes the app from cached memory, but keeps the background sync's (if it has any) still running. So you can kill off Facebook, but it's background sync (that would be started during system boot up anyway) remains.
You can test it, if you swipe browser from recent app's memory, it has to reload the page it was on. Same with Facebook app. But Facebook app's background process keeps running until you 'force stop' it.
Android application architecture runs in two layers, foreground and background processes. UI and the things you can use are written to memory when focus is lost from those apps, clearing them from recent apps also clears the memory those apps take at the time.
Is it useful? Yeah, for some things. But it won't improve your performance in any real noticeable way. Best you can do is swipe away apps that you don't need, keeping only apps that you want to keep in memory should you re-open them again. But that's usually too much micro-management to be worth it.
kristovaher said:
Yes it does close the app. It just doesn't close background processes of the app.
Click to expand...
Click to collapse
Perhaps, BUT, not every app in the recent apps list is actually running. That's why many times (most of the time?) the screenshot isn't what you actually see when you select an app from the list--you're really restarting it.
I think it's safest and easiest to just assume that you're really only removing apps from the recent apps list, not actually managing what's running in any way.
DroidHam said:
Does it really matter though performance wise? I Always thought Android puts background apps into an "idle" state where they dont take up any resources until used? Although it is cool for people with OCD like me
Click to expand...
Click to collapse
Yeah it doesn't make any difference performance wise, but it makes the menu much more useable for me =D
Thanks for this message, this is my first android device and I've been trying to figure out how to "close" applications. Did a search in here (I think), prime manual search and googled it. I am slightly OCD and like to "close" thinks that I'm not using. Harkens back to my early Windows days when you closed apps to conserve memory.
In the manual it says to close application by clicking on an X in the recent apps menu. Though unless it is super tiny, there isn't one.
redandblack1287 said:
I just discovered that you can get rid of apps from the recent apps menu (the square button next to the home button) by swiping them to the side. I don't know why this makes me so retardedly happy, but I am sure that SOMEONE else out there will also appreciate this tidbit of information.
Anyone else have any nuggets of joy to share?
Click to expand...
Click to collapse
if you have the dock, 2 finger gestures on the touchpad act as screen swipes. i.e. swipe two fingers across the tab, the tab changes screens. Also, if you want to actually kill the apps, add teh asus task manager widget to a screen. works great!
elybug said:
In the manual it says to close application by clicking on an X in the recent apps menu. Though unless it is super tiny, there isn't one.
Click to expand...
Click to collapse
That was an ASUS Honeycomb customization. It went away in ICS...
redandblack1287 said:
I just discovered that you can get rid of apps from the recent apps menu (the square button next to the home button) by swiping them to the side. I don't know why this makes me so retardedly happy, but I am sure that SOMEONE else out there will also appreciate this tidbit of information.
Anyone else have any nuggets of joy to share?
Click to expand...
Click to collapse
if you have the dock, 2 finger gestures on the touchpad act as screen swipes. i.e. swipe two fingers across the tab, the tab changes screens. Also, if you want to actually kill the apps, add the asus task manager widget to a screen. works great!
kristovaher said:
Yes it does close the app. It just doesn't close background processes of the app.
Swiping an app from recent apps menu removes the app from cached memory, but keeps the background sync's (if it has any) still running. So you can kill off Facebook, but it's background sync (that would be started during system boot up anyway) remains.
You can test it, if you swipe browser from recent app's memory, it has to reload the page it was on. Same with Facebook app. But Facebook app's background process keeps running until you 'force stop' it.
Android application architecture runs in two layers, foreground and background processes. UI and the things you can use are written to memory when focus is lost from those apps, clearing them from recent apps also clears the memory those apps take at the time.
Is it useful? Yeah, for some things. But it won't improve your performance in any real noticeable way. Best you can do is swipe away apps that you don't need, keeping only apps that you want to keep in memory should you re-open them again. But that's usually too much micro-management to be worth it.
Click to expand...
Click to collapse
that's what I meant. I should of been more clear then. just swiping it doesn't close down app "Completely", meaning no background process either. you have to use a task manager or Force stop in order to "Truly" close n stop an app from running.
elybug said:
In the manual it says to close application by clicking on an X in the recent apps menu. Though unless it is super tiny, there isn't one.
Click to expand...
Click to collapse
There isn't any in ICS, only in HC.
i didn't know that either until last week! ice cream is awesome :]
Conduitz said:
if you have the dock, 2 finger gestures on the touchpad act as screen swipes. i.e. swipe two fingers across the tab, the tab changes screens. Also, if you want to actually kill the apps, add teh asus task manager widget to a screen. works great!
Click to expand...
Click to collapse
You know.....that Asus task manager widget does not work on mine. It doesn't matter if I press x next to one app or select kill all - nothing happpens. I think mine is broken
I removed it from one of my home screens, no need to have it if it doesn't work
demandarin said:
that's what I meant. I should of been more clear then. just swiping it doesn't close down app "Completely", meaning no background process either. you have to use a task manager or Force stop in order to "Truly" close n stop an app from running.
Click to expand...
Click to collapse
It's a bit different though, because those background processes will (likely) already be running even if you don't start the app. Most of those background processes are started by boot activity in Android and others are started by scheduling activities (such as alarms or certain notifications and sync). These will be usually restarted once app is started again too (after Force Close) and if they are not already running (and they usually are).
Force Close is unnecessary unless you know that a certain app is bad for the system and was run accidentally, etc.
Greenify is the most useful app yet made for Android but still so much can be done to make it better so I thought to make a thread to make Greenify better and I hope @oasisfeng would look at it.
Post your feature requests and suggestions here in this thread.
My suggestions: I think there should be an option, like a timer, after which greenify automatically greenifies apps even when the screen is on so that if I use a lot of apps continuously and then without turning the screen off once I start to watch a movie or play a game or anything on a phone, greenify should hibernate the background triggered apps automatically and save battery and provide better overall performance.
I know Tasker can do that but personally I don't like using Tasker because of its complex UI so I've set a shortcut on my phone when I double tap the menu button it triggers the hibernate now shortcut of greenify. But it would be of much help if greenify does it itself, having a timer of something between 1min-1hour to greenify apps automatically.
Also I would like the ram usage of greenify to be less, as sometimes it starts using as much as 60-70mb of ram, which is quite much. I hope you can find a way to reduce the ram usage.
If developer read this, i would like to have an option to disable startup apps.
If you have too much apps that starts in same time when you turn on your phone, you will have a slow boot..
I think that this is option that should exist in such great app..
And yes, some timer should exist also...
@oasisfeng
Hi sir. & tnx for the amazing greenfy.
As i talked with you I have some suggestions for greenfy & i want everyone to share more suggestions:
1) Add an option to put some apps in a group. Then put them in hibernation or degreenfy them with one click or widget.
Let me explain: for example i use some sound mods that keep special apps in memory. But when i dont listen to music i dont need them. So i want them to be in hibernation. But when i want to listen to music, i need to degreenfy them with one click
2) Add an option to deactivate & freeze some apps temporarily & easily in the greenfy app.
For example i dont want the google play services be in the memory all the time. I just need it when i want to use a google app. So i freeze it in the greenfy. & when i need it i defrost & activate it.
3)Add an option to force greenfy some apps instead of cut off the services one by one. Or an option to choose the services that we dont need them. & deactivate them.
4) Add an option to degreenfy some apps by a period of time & put it back in hibernation after that automatically.
For example: i use a calander app. That if i put it in hibernation the date that it shows freezes & sticks on a certain day. But if there be an option to degreenfy it daily for an hour automatically & put it back, it was great.
5) Add an option to change the cpu governer from ondemand(or balance) to power save automatically when the screen turns off. & when it turns on or we receive a call or notificstion it goes back to ondemand( or balance)
6)Add an option to not put in hibernation for some apps when they are downloading or uploading. ( i think it's not possible to determine this ) but just a suggesttion)
7) Add an gaming mode. That greenfy put all of the apps in hibernation instead of call,message, or apps that we mention.
kassaaam said:
Greenify is the most useful app yet made for Android but still so much can be done to make it better so I thought to make a thread to make Greenify better and I hope @oasisfeng would look at it.
Post your feature requests and suggestions here in this thread.
My suggestions: I think there should be an option, like a timer, after which greenify automatically greenifies apps even when the screen is on so that if I use a lot of apps continuously and then without turning the screen off once I start to watch a movie or play a game or anything on a phone, greenify should hibernate the background triggered apps automatically and save battery and provide better overall performance.
I know Tasker can do that but personally I don't like using Tasker because of its complex UI so I've set a shortcut on my phone when I double tap the menu button it triggers the hibernate now shortcut of greenify. But it would be of much help if greenify does it itself, having a timer of something between 1min-1hour to greenify apps automatically.
Also I would like the ram usage of greenify to be less, as sometimes it starts using as much as 60-70mb of ram, which is quite much. I hope you can find a way to reduce the ram usage.
Click to expand...
Click to collapse
Alright im not oasisfeng but i can certainly answer some questions as to why this might be possible atm
First, the so-called hibernation whem screen on will only drain your battery futher and will cut-off android system's background process for apps. To put it shortly, it'll cut-off the functions of apps that needs another app for its services.. Some instances includes xposed for whatsapp and the whatsapp itself and others alike. This will have an excessive power drain due to two reasons:
1.) Greenify will constantly monitor background time when screen on hence battery drain
2.) Hibernating apps while screen is on will only re-trigger it, as an example is facebook/messenger.. As hibernating them screen on would only awaken it again after a few seconds which results in more wakelocks and more unneccesarry battery drain
And for the ram usage i have never encountered such, the biggest i have is 11 mb so im quite puzzled.. What services are running in your greenify? I personally disable campaign tracking and analytics services to minimize ram usage
mire777 said:
If developer read this, i would like to have an option to disable startup apps.
If you have too much apps that starts in same time when you turn on your phone, you will have a slow boot..
I think that this is option that should exist in such great app..
And yes, some timer should exist also...
Click to expand...
Click to collapse
Disabling startup apps is the job of other 3rd party apps such as appopsxposed and bootmanager.. Greenify hibernates but not limits. You can never have too much butter on one bread sir
I have recently bought the donation pack for greenify and I have several questions. First of all, I want to say that the app is really fulfilling all my expectations but as someone worried about my battery performance I still have some question, but first I'll say the conditions of my smartphone:
Samsung galaxy s5 with lollipop using greenify 2.5.2 donation pack (non rooted)
Questions:
1) I cannot see apps like chrome to be greenified and I want to have them like that as I see chrome takes up to several hours of internet connection even if I have just used it for some minutes. I wonder this is possible because I suppose this can be made as in other apps like battery killers, chrome can be killed, but I just haven't seen how.
2) Everytime I open greenify there are many "pending" apps that are not hibernated, even if I click in "zzz" button or in the button that says "hibernate and turn off the screen". The only way to deal with these pending apps is to select all of them and click on "zzz". I guess there should be a way to have them automatically hibernated.
3) There is an option in the menu that talks about an automatic manner to do this but I don't see how to activate it. I have it marked the greenify options for locking the screen but there are even more things to set that I don't see where and how. Maybe you can guide me in this better. In case I have this option chosen, pending apps will be automatically closed after some minutes, as it is said? if so, how many minutes?
Thanks in advance!
paco_ramirez said:
Questions:
1) I cannot see apps like chrome to be greenified and I want to have them like that as I see chrome takes up to several hours of internet connection even if I have just used it for some minutes. I wonder this is possible because I suppose this can be made as in other apps like battery killers, chrome can be killed, but I just haven't seen how.
2) Everytime I open greenify there are many "pending" apps that are not hibernated, even if I click in "zzz" button or in the button that says "hibernate and turn off the screen". The only way to deal with these pending apps is to select all of them and click on "zzz". I guess there should be a way to have them automatically hibernated.
3) There is an option in the menu that talks about an automatic manner to do this but I don't see how to activate it. I have it marked the greenify options for locking the screen but there are even more things to set that I don't see where and how. Maybe you can guide me in this better. In case I have this option chosen, pending apps will be automatically closed after some minutes, as it is said? if so, how many minutes?
Thanks in advance!
Click to expand...
Click to collapse
Have you set Greenify to "on" in SETTINGS>Accessibility?
If you want to manually hibernate, create the shortcut from within Greenify (use the three button icon on the top right). When you use the shortcut, the chosen apps will be hibernated and the screen will be locked afterwards.
In Autohibernate, the time taken for hibernation varies but all apps should be hibernated within 10 minutes max.
For hibernating system apps like Chrome, I think you need root permission.
Yes, the accesibility for Greenify is set to activated. However this options is never enabled within the "experimental settings" menu. It's always set to off. So I have never seen my phone awaking ten minutes after to turn off all pending apps. They remain opened. Any hint?.
Best regards!
paco_ramirez said:
Yes, the accesibility for Greenify is set to activated. However this options is never enabled within the "experimental settings" menu. It's always set to off. So I have never seen my phone awaking ten minutes after to turn off all pending apps. They remain opened. Any hint?.
Best regards!
Click to expand...
Click to collapse
When you click the "always off" Automatic Hibernation option in Experimental Features, what happened? It is supposed to be a accessibility setting dialog for you to enable the accessibility service from Greenify for the first time, then Device Admin dialog to enable the other service for the second time, and being checked at last for the third time.
Here I post the sequence I do in screenshots. Evrytime I click in that button it appears the same dialog. I don't know if I'm doing something wrong...but i dont get it working and I have to hibernate manually pending apps
Thanks for helping! ?
paco_ramirez said:
Here I post the sequence I do in screenshots. Evrytime I click in that button it appears the same dialog. I don't know if I'm doing something wrong...but i dont get it working and I have to hibernate manually pending apps
Thanks for helping! ?
Click to expand...
Click to collapse
Have you enabled 'secure key guard'?
If so, disable it and then check.
tnsmani said:
Have you enabled 'secure key guard'?
If so, disable it and then check.
Click to expand...
Click to collapse
Yes! it was that!. I supposed it was enough by allowing greenify in the security menu. Thanks!
However, I wanted to have it working because I thought it was the only way to have pending apps hibernated because with the button "hibernate and lock" was not hibernating pending apps. After rebooting the phone (thing that I do seldom) it works as I expected. I guess this was the cause why greenify wasn't worked as I expected. Then, for me it is ok if I have that button since it does what I expected to.
Thanks to all!
I'm using Greenify on 4.4. Some apps like Viber or keyboard are not hibernating automatically. We can force them to, with this zzz button in which case they hibernate all the time.
I find it would be the most useful not to use zzz but to have another "Force hibernation shortcut" that would instantly hibernate all listed apps, still allowing those existing 2 shortcuts which don't hibernate all.
I hope this concept is not wrong and that it can be done. If it is, please advise how to use it.
O
TimAnd said:
I'm using Greenify on 4.4. Some apps like Viber or keyboard are not hibernating automatically. We can force them to, with this zzz button in which case they hibernate all the time.
I find it would be the most useful not to use zzz but to have another "Force hibernation shortcut" that would instantly hibernate all listed apps, still allowing those existing 2 shortcuts which don't hibernate all.
I hope this concept is not wrong and that it can be done. If it is, please advise how to use it.
Click to expand...
Click to collapse
Thats an very interesting concept,and totally possible,this used to be present on older versions of greenify but it was removed because it closed apps when they were doing something important. also,Why are you hibernating your keyboard?
danx32 said:
Why are you hibernating your keyboard?
Click to expand...
Click to collapse
I'm hibernating keyboard just because it consumes power. That's so with SwiftKey and TouchPal which are great with swype/slide functions.
Built-in keyboard in 4.4 doesn't but I don't use it. Huawei phone has this power consumption warning and those 2 are regularly on the list.
TimAnd said:
I'm hibernating keyboard just because it consumes power. That's so with SwiftKey and TouchPal which are great with swype/slide functions.
Built-in keyboard in 4.4 doesn't but I don't use it. Huawei phone has this power consumption warning and those 2 are regularly on the list.
Click to expand...
Click to collapse
Swiftkey never been battery friendly,Unfortunately Currently The only solution is to use that ZZZ button until the developer fixes that,But that's gonna take awhile since he is currently focusing on Android N support.
I feel like this should be do-able in MacroDroid using a widget button and the Send Intent action... I have never tried using that particular action though, and seems I need to get a dump of the intents and look for the right one hehe, sounds like a sober job
Some info on Intent for Tasker.. not familiar with that app but assume is similar to MacroDroid...