Hi..
First of all I like to thank Greenify application developer for bringing such a great battery saver and powerful application for Android.
I'm running this application for the first time in my first rooted device and I really feel the difference between any other battery saver application . But, since im new to this application I don't know which application should I select for hybernate.
So, please somebody help me what applications should be put to Hybernate and which should not...
Zkmarak9 said:
Hi..
First of all I like to thank Greenify application developer for bringing such a great battery saver and powerful application for Android.
I'm running this application for the first time in my first rooted device and I really feel the difference between any other battery saver application . But, since im new to this application I don't know which application should I select for hybernate.
So, please somebody help me what applications should be put to Hybernate and which should not...
Click to expand...
Click to collapse
Search the main thread.
tnsmani said:
Search the main thread.
Click to expand...
Click to collapse
I mean system application can be hybernate? What about Smartcard Service, Wiper App, Memory, Network Location, Com Qualcomm.qcril..,etc. Cant it be hybernate?
Zkmarak9 said:
I mean system application can be hybernate? What about Smartcard Service, Wiper App, Memory, Network Location, Com Qualcomm.qcril..,etc. Cant it be hybernate?
Click to expand...
Click to collapse
As a general rule, the apps which you use most are not to be greenified. System apps can also be greenified if you have the donate version of Greenify. BUT it is dangerous and can brick your phone. So go through the main thread to know which apps can be greenified safely. Memory, network location etc are not apps. They are part of the system, so be careful.
tnsmani said:
As a general rule, the apps which you use most are not to be greenified. System apps can also be greenified if you have the donate version of Greenify. BUT it is dangerous and can brick your phone. So go through the main thread to know which apps can be greenified safely. Memory, network location etc are not apps. They are part of the system, so be careful.
Click to expand...
Click to collapse
Okay thank you so much ....for the information.
Related
Hi, I was wondering if there's an app or a setting to avoid some apps as facebook and market to auto-start when data connection or wifi are on.
Anytime I start data, their services are always started by their own.
Tony84 said:
Hi, I was wondering if there's an app or a setting to avoid some apps as facebook and market to auto-start when data connection or wifi are on.
Anytime I start data, their services are always started by their own.
Click to expand...
Click to collapse
Droid wall I think, but why would you want htem to not connect...
no, I don't want them not to connect, just want to start them manually when needed, not to start by theirself and drain memory. I want ofcourse grant them the internet acces, just want not to start automatically
Tony84 said:
no, I don't want them not to connect, just want to start them manually when needed, not to start by theirself and drain memory. I want ofcourse grant them the internet acces, just want not to start automatically
Click to expand...
Click to collapse
android does not work that way, free memory is wasted memory, it is not like windows. If that memory is need linux kills what is not needed. If you are doing to keep free memory then dont bother...I always want all my memory being used...2.3 rom handle the memory very well and there is no need to manually kill apps or use 3rd party apps to do it like task killers...they are redundant on 2.3+ roms
and from the battery draining's point of view?
and if it affects the battery, is there a way to do what I said?
Tony84 said:
and from the battery draining's point of view?
and if it affects the battery, is there a way to do what I said?
Click to expand...
Click to collapse
use juice defender pro, is a paid for app but i think you can restrict connection in that
gregbradley said:
use juice defender pro, is a paid for app but i think you can restrict connection in that
Click to expand...
Click to collapse
ok I'll give it a try, thanks
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 find that apps like Spotify or other music apps get killed after a while even if they are the only open app. Many apps that create notification for persistence also get killed very quickly on MIUI. e.g. Wakey to keep screen on gets killed to.
Is there a way to fix this?
Give them a lock in recent apps or you go to security center look for Autostart and choose your application. This helped for me
Dev111 said:
Give them a lock in recent apps or you go to security center look for Autostart and choose your application. This helped for me
Click to expand...
Click to collapse
Even if I have exactly done what you have suggested, some of my apps keep being shut down for no obvious reasons.
I am on the latest weekly developers rom by the way.
Go to Settings->Additional Settings->Battery & Performance->Manage app's and battery usage->Choose app's to restrict. Try it out maybe it works for you. If not I got no solution anymore if you find out an other method pls say it to me!
Dev111 said:
Go to Settings->Additional Settings->Battery & Performance->Manage app's and battery usage->Choose app's to restrict. Try it out maybe it works for you. If not I got no solution anymore if you find out an other method pls say it to me!
Click to expand...
Click to collapse
Tried that for the constantly closing 2 apps but still getting shut downs.
I froze as many system apps as I could to free some ram and also disabled ram management from developer's options.
first of all - amazing app!!
I have one question, maybe I got it completely wrong ...
If I hibernate an app, and restart it later again, e.g using the recent key, shouldn't the app state also be restored??
e.g. I use root explorer and navigate to a folder, then press the home key. When I get back to the application ( not using greenify) I will see the same folder that I was in before (if LMK did not kill my app of course).
But when the app was hibernated (greenifed), it always starts up "fresh"... Is this intended??
Galaxy s6, android 5.0.2 rooted
The app is stopped so is normal. Btw in Root Explorer is an option to restore your last working folder, check it if you want to go back to your folder.
MihaiSG said:
The app is stopped so is normal. Btw in Root Explorer is an option to restore your last working folder, check it if you want to go back to your folder.
Click to expand...
Click to collapse
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
That is how the app is designed. You are not supposed to Greenify every app especially those you use frequently. That will consume more battery. This is stated in the OP of the main thread by the Dev himself and repeated many times in many sub-threads.
Makes sense.
tnsmani said:
That is how the app is designed. You are not supposed to Greenify every app especially those you use frequently. That will consume more battery. This is stated in the OP of the main thread by the Dev himself and repeated many times in many sub-threads.
Makes sense.
Click to expand...
Click to collapse
Yes, makes sense.
Thank you for the clarification.
GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
I believe the closest equivalent of the IOS behavior that you are looking for is generated through Doze, a function implemented in Android phones with Marshmallows. For a more aggressive Doze behavior, you can use greenify. And if you don't have marshmallow on your phone, I believe there is a dedicated Doze app on the play store
Surfinette said:
I believe the closest equivalent of the IOS behavior that you are looking for is generated through Doze, a function implemented in Android phones with Marshmallows. For a more aggressive Doze behavior, you can use greenify. And if you don't have marshmallow on your phone, I believe there is a dedicated Doze app on the play store
Click to expand...
Click to collapse
Ok thank you. I assume the app you are taking about is shutApp... The doze app (same developer) just cuts off the network activity using a dead VPN connection. I will try shutApp on my device phone, but for now I am happy with greenify, it works great except for Chrome and YouTube... Thanks for your help..
GZA1337 said:
Root explorer was just an example. So it is not exactly the iOS feeling that an application is stopped in background and resumed afterwards...
Which means, that I should not greenify apps that I want to go back later on using the recent key - because I will get a reload of the whole app which makes the 3 Gigs of RAM completely useless ... Is this correct??
So people who greenify everything will get a bad user experience, at least on the apps they use many a time....
A little disappointing but still a great app.
Click to expand...
Click to collapse
You may try the new experimental feature - "Shallow Hibernation" if your device is running Android 6.0 and rooted. It preserves the app running context even in hibernation.
oasisfeng said:
You may try the new experimental feature - "Shallow Hibernation" if your device is running Android 6.0 and rooted. It preserves the app running context even in hibernation.
Click to expand...
Click to collapse
I will give it a try, thanks!
Hi All
I'm trying to get my head around what Huawei have done with the "Launch" functionality. My naive understanding is that it's huawei's own attempt at greenify. Killing apps that are not being used... somewhat intelligently.
I'm wondering if this actually has any impact on battery at all, it certainly stops processes from launching and running.. notifications being missed etc.
Anyone have any ideas what this is actually doing, or if the setting is actually beneficial? I thought google was against this sort of practice when doze is their solution.
Secondly, the following apps are allowed to ignore battery optimisation out of the box:
Backup
Camera
com.huawei.hiviewtunnel
Email
Google Play Services
Google Services Framework
Health
HwLBSService
Screen recording
System update
Any one know if it is advisable to set these to don't allow ignoring of battery optimisations?
Thanks
alexs1mmo said:
Hi All
I'm trying to get my head around what Huawei have done with the "Launch" functionality. My naive understanding is that it's huawei's own attempt at greenify. Killing apps that are not being used... somewhat intelligently.
I'm wondering if this actually has any impact on battery at all, it certainly stops processes from launching and running.. notifications being missed etc.
Anyone have any ideas what this is actually doing, or if the setting is actually beneficial? I thought google was against this sort of practice when doze is their solution.
Secondly, the following apps are allowed to ignore battery optimisation out of the box:
Backup
Camera
com.huawei.hiviewtunnel
Email
Google Play Services
Google Services Framework
Health
HwLBSService
Screen recording
System update
Any one know if it is advisable to set these to don't allow ignoring of battery optimisations?
Thanks
Click to expand...
Click to collapse
Allow none of them. Cause no harm
lawtq said:
Allow none of them. Cause no harm
Click to expand...
Click to collapse
I'm wondering the same thing.
Are you sure that we can allow none of them app ?
I'm not allowing any apps that need to stay running (in the background) like Garmin Connect, Ad blocker, virus scanner and some more to avoid Huawei killing them. I see no difference in battery consumption.
sonydesouza said:
I'm wondering the same thing.
Are you sure that we can allow none of them app ?
Click to expand...
Click to collapse
I've disallowed all of them. I don't see any problems
lawtq said:
I've disallowed all of them. I don't see any problems
Click to expand...
Click to collapse
And did you see any improvments ?
sonydesouza said:
And did you see any improvments ?
Click to expand...
Click to collapse
Tbh no. Lol. Battery is great no matter what. But no harm either