From the way I understand greenify, it deals with different aspects of APPS (job scheduler, AsyncTaskStatus etc), However I am wondering, how does it deal with streaming apps? (Pandora, netflix) etc...
For instance, I have all these apps that are Radio apps that I do not want running unless i'm streaming. I've not tested this, but does Greenify equate a "running app" (one it won't hibbernate) to one who has something like "Partial wave lock on"?
I'm just trying to understand what qualifies as a task/event/job that will keep app running vs hibernating.
read forums related with greenify you may get your answer
katsumeiyo said:
From the way I understand greenify, it deals with different aspects of APPS (job scheduler, AsyncTaskStatus etc), However I am wondering, how does it deal with streaming apps? (Pandora, netflix) etc...
For instance, I have all these apps that are Radio apps that I do not want running unless i'm streaming. I've not tested this, but does Greenify equate a "running app" (one it won't hibbernate) to one who has something like "Partial wave lock on"?
I'm just trying to understand what qualifies as a task/event/job that will keep app running vs hibernating.
Click to expand...
Click to collapse
That's a process state set by Android system, it will tell whether this app is active or not. Greenify use this state as the main condition, plus some other clues (e.g. persistent notification).
Related
hi all, im an owner of a sam.charge. I use the app called "System" and it lists about a dozen apps that are stored in my cache or that are using memory when I have not innitiaited the service or app...
I'm most familiar with computers so I'll relate it to that; is there some type of command line that I can use to stop some of these apps from auto start and being stored. For instance on windows you can 'msconfig' what programs are allowed to start on boot up.
Here is a list of apps that I want to stop: AccuWeather.com, Android Booster, Google Voice, HeyTell, Amazon's Appstore, Market, Music, etc.
Most are cached/ inactive but none the less in my task manager when freeing up memory when I notice things to be lagging I'd imagine these to be guilty. Android Booster always lists these as killed apps as well when optimizing...
Im familiar somewhat with how android works being that it often fills a large portion of your memory with what it wants to and frees space as it is needed but these apps for me are rarely used...
Im big on battery life being Im in and out of Sales accounts and rely on my phone heavily so I dont want these things running in the background sucking up resources. Not to mention I like a snappy phone...
If anyone could educate me on this topic Id really appreciate it... I may be mistaken on a few things so call me out on it, since im sure I am... Also, I know their are app freezers and applications you can program to kill apps at a set interval but again I would like the least amount of garbage running as I can
Sent from my SCH-I510 using Tapatalk
Some of the basic services are must to be initiated/running all the time such as launcher, keyboard, google voice, market, etc.. so as to run your phone smoothly . This is the default setting of android os. And anyway why do you want to close/stop the services case restarting services uses more battery than kepping them running on the memory ....
mlm2588 said:
hi all, im an owner of a sam.charge. I use the app called "System" and it lists about a dozen apps that are stored in my cache or that are using memory when I have not innitiaited the service or app...
I'm most familiar with computers so I'll relate it to that; is there some type of command line that I can use to stop some of these apps from auto start and being stored. For instance on windows you can 'msconfig' what programs are allowed to start on boot up.
Here is a list of apps that I want to stop: AccuWeather.com, Android Booster, Google Voice, HeyTell, Amazon's Appstore, Market, Music, etc.
Most are cached/ inactive but none the less in my task manager when freeing up memory when I notice things to be lagging I'd imagine these to be guilty. Android Booster always lists these as killed apps as well when optimizing...
Im familiar somewhat with how android works being that it often fills a large portion of your memory with what it wants to and frees space as it is needed but these apps for me are rarely used...
Im big on battery life being Im in and out of Sales accounts and rely on my phone heavily so I dont want these things running in the background sucking up resources. Not to mention I like a snappy phone...
If anyone could educate me on this topic Id really appreciate it... I may be mistaken on a few things so call me out on it, since im sure I am... Also, I know their are app freezers and applications you can program to kill apps at a set interval but again I would like the least amount of garbage running as I can
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
If you find apps that you don't use, you can use a program to freeze them. Just search for freeze in the market. I personally use a free app called System Tuner. Freezing prevent them from starting up and therefore you cannot use them, but later on you can un-freeze them if you need to.
Optimize toolbox
I use this one, had a bunch of other features.https://market.android.com/details?id=cn.opda.a.phonoalbumshoushou&feature=search_result
Thanks all for the feedback...
To reply to the first response; I have read that about battery life. That, the more you kill apps and reopen them that it takes longer for the app to start up and thus sucking up battery life... I probably should not have mentioned battery life in my post being that I have a car charger and that it contradicts what im trying to accomplish (going over my post, it was stupid of me given what you just mentioned). Also, I'm not so much concerned with market apps or google voice as I am about the apps I installed myself. Those ones are the ones that bother me.
To the other posts thanks for the recommendations I will like into those options. I'm just trying to prevent extra apps from running in the background so freezing them is a last resort.
I'm looking for something that I can type in terminal possibly on program into the OS or app itself to keep it from auto starting... possibly a command line?!
Any developers input? Can this even be done. I'm still very much a beginner but its not beyond my comprehension to do something like this... I know its different but I play around with linux, web design, c++ stuff so if you post directions I can follow smoothly our atleast figure it out if you point me in the right direction
Sent from my SCH-I510 using Tapatalk
It's not exactly what your asking for but have you tried Gemini App Manager:
https://market.android.com/details?id=com.seasmind.android.gmappmgr
You can use it to disable/re-enable an app's autorun settings. When you first open it it will list all user apps currently in memory. Clicking menu then expert mode will give you a list of all apps. Long press an app then click configure autorun.
Just be careful with changing the autorun settings of system apps like market.
"preventing apps from autostarting"
I like this topic a lot!
I think the question(s) and "assumptions" the OP holds are all valid. So I'd really like to hear the answer to the actual question, not a spew of why the question isn't valid.
How do you stop apps from starting up on their own? (like microsofts msconfig)
Pretty simple question and I cannot find the answer! I've been in software for many year and I'm rather stunned by the responses people are giving - which basically say "who cares, android O/S handles it for you".
Well, lets face it:
*If* the user didn't call for the app, and had no desire to use it, then the "system" loading it even ONCE, is one too many.
*If* the app is a DESIRED app, (OR device required), *BUT* uses data - then if the user didn't want to use it; "yet" - then thats DATA & BATTERY life --> **WASTED**
If the user suspects the APP is misbehaving; one sure fire way would be to SEE it running, when they didn't ask it to!
If you are pure paranoid, or simply want extreme app control....
The kinds of answers people are giving is truly along the the lines of "we dont know, but you're silly for caring"
SOYLENT GREEN!!!!!!!!!!!!!!!!!!!
:cyclops:
jr67 said:
It's not exactly what your asking for but have you tried Gemini App Manager:
https://market.android.com/details?id=com.seasmind.android.gmappmgr
You can use it to disable/re-enable an app's autorun settings. When you first open it it will list all user apps currently in memory. Clicking menu then expert mode will give you a list of all apps. Long press an app then click configure autorun.
Just be careful with changing the autorun settings of system apps like market.
Click to expand...
Click to collapse
I'm going to test this out too! And I'll post success if it does well!!!
Hi
First of all thank you Oasis for creating a tool to fix things that shouldn't be broken to begin with! You are an example for a lot of developers :good:
I've read the first couple of posts on the original thread but I still have a few things that are not clear..
The advice of Oasis himself is too hibernate only those apps that misbehave. He states that hibernating apps will also remove them from the memory, which will come with a performance/cpu usage penalty when you want to use them again.
In the video tutorial however Josh greenifies almost every application that doesn't need push notifications.
So this would mean that when I use an application that doesn't have notifications but I open frequently, for example Nu.nl, a dutch newsapp, it will always have to reload the app from scratch instead of loading it from memory?
So baically the best way to use Greenify would be to NOT just greenify most apps, but to use the analyzer frequently and see what's running in the background and greenify those that don't depend on notifications?
Then newsapps that don't push news, image viewers, file managers, system tools like SD Maid and simple games that don't use internet should be ok not being greenified?
Is there no big list available of apps that misbehave or are safe to keep de-greenified?
Thanks in advance for any help on this.
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
marchrius said:
Basically you got it right. Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. For my experience, sometimes is better to disable a background service than greenify an app, if the app "misbehave" for this service only (of course you'll have to check if the app still works). An example: guaranteedhttpservice and tracksyncservice in shazam...
Click to expand...
Click to collapse
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
latino147 said:
Where can I find and disable things like tracksyncservice? I also use Shazam but I can't find both services you mentioned in Greenify nor TiB?
Click to expand...
Click to collapse
"Disable Service" (and "Autostarts") from play store.
marchrius said:
"Disable Service" (and "Autostarts") from play store.
Click to expand...
Click to collapse
Ah, I believed those were two functions withing Greenify I couldn't find
wtf, FB has 62! services! None of them where active though, until you open the app, then it was 3.
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
The only issue with this second method being that you don't always really know what these services do.
latino147 said:
So you can choose between greenifying an app which will basically kill all services from an app, even background services on one hand, and choosing specifically which services too disable, like you did with Shazam.
Click to expand...
Click to collapse
Exactly. Take google play services for example. If you greenify it, you'll lose gcm and other functions and that's not advisable at all (in fact greenify hides it). But with disable service (and autostarts/system tuner)you can choose what to disable while still mantaining gcm, location services (when needed), sync etc. I can' remember what I did in system tuner regarding gplay services (I followed some tutorial), but with disable service I disabled analyticsservice (this one will reactivate itself unless you do some tweak with system tuner), refreshenabledstateservice, playlogreportingservice, googlehttpservice, playlogbrokerservice, adrequestbrokerservice, gcmschedulerwakeupservice, advertisingidservice, adsmeasurementservice, locationwearablelistenerservice, nlplocationreceiverservice, geocodeservice, dispatchingservice and playlogservice. A reboot is needed. Haven't lost a single function since weeks (gcm, location, autosync and every google app in general are working 100% fine).
Same story with play store. Apps wake it very often, so greenify it does more harm than good. Instead, you can disable pendingnotificationsservice, contentsyncservice and dailyhygiene (and will still be fully functional).
Of course these are little tips to increase performance and battery life even more. I use greenify for 90% and more of apps that "misbehave" and disable service/autostarts/system tuner for the remaining 10% "misbehaving" apps. However, an app "fixed" with such methods will stay cached while with greenify is completely closed (resulting in more cpu/time/battery consumption when loaded again).
The only issue with this second method being that you don't always really know what these services do.
Click to expand...
Click to collapse
Like I already said, for general purposes you'd better simply greenify the "misbehaving" apps. If you use it/it is woken very often, you can consider these methods.
Yes, it's a "trial and error" thing. Unless you're disabling services with self-explainatory names such as "pushservice".
Never installed Facebook official app but I heard many times that is a notorious hogger and takes many personal datas too, for which you can look for xprivacy xposed module as well.
I'll start experimenting with it today :good:
I'm sorry if something like this has come up before, it's quite hard to search for specific things like this and I probably look stupid for just realising this now but here goes:
I always assumed that Greenify would only hibernate apps that I myself didn't have running (ie apps that weren't in overview or the foreground) yet I've recently realised that apps in the overview page (recent tasks) on lollipop are also susceptible to being greenified. Is it possible to have apps be excluded from hibernation whilst they are in overview?
For example, I greenify the Eurosport app because it runs a service even though I have push notifications off for it, but I still want to be able to have it in the background and jump back to it without it reloading, so the ideal would be I could leave it in the overview and multitask into it again later. However if the screen has been off for a few minutes Greenify hibernates it meaning it requires a reload, which may in fact use more battery overall than I saved by greenifying it in the first place.
Is it possible to add the condition that apps only get greenified once they've been cleared from overview/recent tasks/multitasking (whatever you want to call it)
It has been discussed before.
1. Android 5.0 removed the ability for an app to get the list of recent apps.
2. Recent app list is actually managed by Android system. An app in the list does not mean its process is still running, and some being squeezed out of the list also do not mean their processes are ended.
So it's not reliable for hibernation to depends on the recent apps list.
In your case, if that app does not cause battery issue, it's suggested to keep it out of Greenify for process to be cached.
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
mermaidkiller said:
On my Mate 9 (running Oreo 8.0, no root) I installed Greenify, but Greenify displays that e.g. Opera is greenified, but in an Android task manager (Android Assistant app) it shows it is still eating CPU. The same applies to e.g. Brave browser which has 'no background' according to Greenify.
Does Greenift really hibernate apps ?
Click to expand...
Click to collapse
Of course it does. The size/activity in this forum plus frequent mentions in respected publications over many years should offer some clues to its integrity. Whether it is working on your device is a different matter.
Greenify does best on rooted devices as unharnessed ROMs can both undo actions and/or misrepresent status. It's quite possible an app placed in hibernation was later woken via internal trigger that Greenify can not suppress on an unrooted device. In the case of Opera (my preferred browser) there is regular syncing of tabs and downloading of *cough* 'news' if you have those features enabled.
I also question info coming out of the "Android Assistant" app. On my device it claimed all apps had zero CPU...including itself. Also did not display system partitions correctly nor properly detect the sensor suite. Granted I only spent a few minutes poking around. Maybe some switches needed to be thrown.
Finally, you probably don't need Greenify on Oreo as Doze does a find job with power management.
planetera said:
Don't I really need Greenify on oreo? Is Doze on Oreo really that good? Can you confirm please? I've been always using Greenify but if I don't need it on Oreo, I'll remove it
Click to expand...
Click to collapse
Well don't take my word for it. Simply remove all apps from Greenify's hibernation list (hopefully there are not many there), observe device behavior over the next few days then make your own decision.
planetera said:
Well, thanks for information. Just made a quick research and everyone says Greenify is trash on Oreo. So I just uninstalled it. Thanks for heads up. Glad I've seen your comment
Click to expand...
Click to collapse
Trash? Err-no. I have it installed on every one of my devices for valid reasons. Needed for generic power management on Doze capable ROMs? Probably not (and as such serving no purpose). Enjoy your device.
planetera said:
ok, but, when Greenify hibernates an app, you don't get notificaton froms this app, but when Android itself hibernates the app, you still get notifications, how does these two compare?
Click to expand...
Click to collapse
It varies by app, developer approach and user settings. Many apps will experience delayed notifications with Doze while other punch right through. Greenify can be configured to permit notifications but only if the app utilizes GCM (Firebase). Aggressive doze, light hibernation, Xposed framework availability and several other variables contribute to notification behavior. If your head is spinning it should! End users should not need to know the contents of the underwear drawer. Best practice is to simply let Android do its thing without 3rd party tools unless one understands their behavior and application. At one time such tools were needed to achieve acceptable app/device performance and battery life. Not so today. Is such a simplistic solution 'optimal' form an enthusiasts point-of-view? Probably not. It is acceptable/reasonable from an end-user perspective? In most cases 'yes' yielding a good balance of performance and battery life with minimal interaction for those who simply want to enjoy their device vs. manage it. Good luck with whatever direction you choose.
Agree one hundred percent!
Greenify on Oreo is an appendage that is best left out in my opinion, since for most, Oreo itself manages the drain admirably. Though I have it installed, it is more by way of habit than necessity. I have experienced Oreo without Greenify and have no complaints.
Greenify is STILL works.
But its benefit on recent Android versions is not as prominent as on earlier versions.
Coz we already have Doze starting from Marshmallow.
It works for me. I have a samsung tab a 9.7 sm-t550 with an aicp 8.1 rom (lineageos based). Therefore it doesn't have the built-in samsung app device maintenance. I've also discovered a little trick to using greenify that I want to share. I use greenify with another app called shutapp. Shutapp is an app that helps you force stop apps running in the background. Except I don't do that. I use it solely for the purpose of having an accurate number of apps running in the background. Then I open the app to see which ones are running. Next I open greenify and hibernate them. I use this method, because I found that when you force stop the apps they will open back up again. Also, I use the widget from shutapp and not the floating bubble which requires extra permissions granted. The widget does the same thing without the extra permissions. This method I discovered has improved my ram and battery life drastically. I can tell because I use status bar mini pro to monitor my ram speed constantly. And finally I do have Xposed with the donation package of greenify, didn't want to leave that out. Not sure if it makes a difference or not, but wanted to be accurate. That's it, hope that works for somebody else, take care.
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
ovizii said:
I hear that greenify isn't really needed on Oreo but how about the xposed version of greenify? That ads a couple of more features, does any of those change the verdict to "must have on Oreo" for greenify?
Click to expand...
Click to collapse
tnsmani said:
The verdict doesn't change. Use of Greenify on Oreo may become "must" only if you have a rogue app which can't be controlled otherwise. Even then, it might be better to seek alternative apps instead of trying to control it with Greenify.
Click to expand...
Click to collapse
Greenify works just fine on recent Android builds. It is a tool that can be very beneficial when properly used to produce a specific outcome. That said, it is rarely needed on Android 6+ as doze handles most of the heavy lifting. Enjoy using your device vs trying to fix problems you haven't identified.
My background apps are killed way too often. Is it possible to change that behaviour? Even music apps are killed while I'm playing music.
I have tried several custom roms and kernels but nothing seems to change the settings. Is either able to change RAM management settings?
I have also tried several apps that claim to be able to change RAM management settings without success.
Disabling battery optimisation doesn't help.
I have uninstalled unused apps and disabled autostart (boot completed receiver) for non-essential apps to reduce RAM usage.
When I use a RAM monitor it will show RAM usage at ~75% when apps are killed.
My old phone (Note 4) only had 3 GB ram but could still keep more apps in memory.
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
ChazzMatt said:
I don't have that problem.
Have you tried Greenify or similar app to hibernate unwanted apps running in the background? They will only open then when being used and will automatically hibernate again when closed.
Click to expand...
Click to collapse
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Telorast said:
That's the reverse of what I'm looking for. I want the apps in the background to keep running.
Click to expand...
Click to collapse
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Worth a try. Installed Greenify and added most apps with ignore background-free.
Telorast said:
Worth a try. Installed Greenify and added most apps with ignore background-free.
Click to expand...
Click to collapse
I even hibernate alleged background free apps, just in case.
ChazzMatt said:
Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Click to expand...
Click to collapse
VERY TRUE!
This always infuriated me, not just on phones, PCs too, all the way back to the DOS days. An obsession with running in the background, as if it's particularly clever. :cyclops:
I've also found that turning off battery optimization for apps I don't want killed helps. I've had the same experience with music and podcast apps getting killed in the background and turning off their battery optimization usually fixes it.
There are some simple things to try that do not require any special apk's. One is to look in the apps section of the "Developer options" sub-menu. The default settings work well in most instances. Perhaps you accidently enabled closing of apps when a background limit has been reached or have ticked force closure of apps on exit.
Another place to look is in the "Power saving exclusions" sub-menu in the Battery settings. Music makes some boring forms of exercise less tiresome and provides additional motivation for activities that are challenging but fun (mountain biking). The music should not stop, but it might for default settings. Enabling a power saving exclusion for your music app will keep it running.
ChazzMatt said:
Then you misunderstood what I wrote. Read it again.
It's exactly what you want, because then apps you don't want running won't take up your RAM and kick off the apps that you do want running. Like your flashlight app should NOT be running the background all the time. One example. Lots of devs think their apps are most important and should always run in the background, so when you "launch" them they are there instantly.
Like I said, I don't have your issue. My apps I WANT running stay running.
If you hibernate the UN-wanted apps, that will give more freedom to apps you DO want running in the background.
There are other apps besides Greenify which may do that task even better, it's just the most well known. It shows you complete list if apps running in the background and you can choose which you WANT to run and which you want to stay killed until you choose to activate them. Those apps will be forced hibernated from then on -- until you manually activate them. When you close them, they will STAY closed and not run in the background sucking up your RAM. It also allows you to go through your entire inventory and decide yes/no. For instance, weather widget, email, yes. Benchmarking app, NO.
Click to expand...
Click to collapse
Been using Greenify for a bit now and doesn't seem to help much. It shows a bunch of hibernated apps but multitasking is still nearly impossible.
I had assumed the problem was related to the Mem Free settings rather than actual free memory but no one here has mentioned it. Is that because no one else thinks it's the problem or maybe I have misunderstood what those settings do?
I thought apps were free to use as much memory as they want until certain thresholds on total memory usage were met, then the system would ask or force apps to release memory.
Apps that let you edit those settings usually shows several thresholds where the system gets progressively more aggressive at freeing memory as memory is running out. But they all look hopelessly out of date so maybe it works completely differently today?