If you greenify it, you'll lose gcm and other functions and that's not advisable at all (in fact greenify hides it). The only issue with this second method being that you don't always really know what these services do.Įxactly. 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.
Wtf, FB has 62! services! None of them where active though, until you open the app, then it was 3. "Disable Service" (and "Autostarts") from play store.Īh, I believed those were two functions withing Greenify I couldn't find 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? An example: guaranteedhttpservice and tracksyncservice in shazam. 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). Use the built-in analyzer as well as disable service and autostarts to check apps' behaviour. Is there no big list available of apps that misbehave or are safe to keep de-greenified?īasically you got it right. 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? 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? 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? In the video tutorial however Josh greenifies almost every application that doesn't need push notifications. 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. The advice of Oasis himself is too hibernate only those apps that misbehave. I've read the first couple of posts on the original thread but I still have a few things that are not clear.
#How does greenify work how to
That's enough for me, but do you know if any app that does it also when the screen is on? (App always hibernating unless on foreground)Ī few questions about how to use Greenify efficiently Hiįirst 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 Yes Hibernation Manager and Greenify only work when screen is off. Please read its description in Play Store. This is the behaviour I am seeing.Įdit: Even Hibernation Manager works only when screen is off. Only after that the running apps will hibernate. My understanding is, when you add apps to the autohibernate list and when you continue to work with one app in the foreground, any other hibernated app will continue to run (if started while you are working or if already running) till the screen is locked. Hibernation Manager is similar and has high ratings. Greenify is capable of that, you just add the desired apps to the list. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Ok look like there was a misunderstanding.
I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want). Like if weren't installed from the beginning. How to greenify apps? I want to use greenify to "freeze" a certain apps when are not in foreground, do don't check in the background for location, connect to internet to update, and so on and so forth.
0 kommentar(er)
