Related
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 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. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
scandiun said:
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. Like if weren't installed from the beginning. I couldn't find anything in the user interface, the app looks more oriented to hibernate the entire phone (which I don't want).
Click to expand...
Click to collapse
Look elsewhere. Greenify doesn't "freeze" any app.
tnsmani said:
Look elsewhere. Greenify doesn't "freeze" any app.
Click to expand...
Click to collapse
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
scandiun said:
Ok look like there was a misunderstanding. Didn't mean "freeze" in the way Titanium Backup does, but rather prevent the app from doing anything unless in foreground. Greenify is capable of that, you just add the desired apps to the list.
Hibernation Manager is similar and has high ratings. Also explains things better.
Click to expand...
Click to collapse
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. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
tnsmani said:
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. Only after that the running apps will hibernate. This is the behaviour I am seeing.
Correct me if I am wrong.
Edit: Even Hibernation Manager works only when screen is off. Please read its description in Play Store.
Click to expand...
Click to collapse
Yes Hibernation Manager and Greenify only work when screen is off. 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)
Hello guys, I have a problem with the Facebook and Messenger app, they don't hibernate even if I manually hibernate them.
I tried cutting off the wakelock path, ignoring running state and enabling deep hibernation, but even after that I open the app to find them in the "will hibernate when screen is off" section. They've been draining my battery crazily!
Any other suggestions to do?
Same here. I think a recent Messenger update somehow changed something that prevents Greenify from hibernating it. I am using Lolliop via CM 12.1 Nighly (the very last one before CM 13).
I thought so too and rolled back to some older version, still the same problem with no luck. It's extremely frustrating.
Having the same problem here after their latest update.
Same problem, I mean I only lost like 4% over 5 hours but it should be a lot less, it was Facebook and messenger in my partial wakelocks
I used amplify to limit the wakelocks by them, the wakelock is called bugreporter and so far it hasn't affected notifications, and now they don't keep the device awake anymore.
You can also download older versions which didn't cause the issue here: http://forum.xda-developers.com/showpost.php?p=64816556&postcount=28
so any news about this yet?
Roberto Nigel said:
so any news about this yet?
Click to expand...
Click to collapse
What about the post above yours? That not sufficient for you?
Same here, gets woken by LollipopSerivce and stays up for hours until I manually killed it with "put in to hibernation now"
details:
CM13 nightly 20160116
Xposed 79,
Greenify 2.8 beta 9
Same with me, i uninstalled FB but i need messenger for chatting
Also the persistant notification from Messenger seems to prevent it from sleeping (Sequence : Messenger is hibernating, I receive a GCM push that wake him up but then it keep being "up" if i don't throw away the pop-up....). Or maybe i'm totally wrong dunno
CM13
Xposed
Greenify Beta 9
Same problem
Same here, really frustrating.
Same here, I came here to look if there's anyone else with this problem.
I don't want to install amplify just for fb and msn.
Sent from my LG-D802 using Tapatalk
Workaround
This may be a workaround for now but this is what I did: I tapped on Facebook to highlight it. I then tapped the three-dot menu and selected "Put into hibernation now". A popup then showed-up warning of possible data loss or functionality problems. There is a checkbox in the popup for "Always ignore app state". I ticked it and continued. I did the same procedure for Messenger.
They usually get rid of this trick
With Amplify it's ok.. no more drain from messenger..
SAme problem, back to 2.8 and it´s working
Same here now with notification from greenify... ****ing facebook wakes u every 5min... Anoying.. With the only 2gb ram my phone laggs... Lg g3... Anyway. I will uminstall ans see if my phone gets faster
I had the same problem. I installed greenfy free and saw what wakes up my apps... After i installed " Disable Services " and disable two services. It works for me in facebook, i dont know about messenger. Sorry my bad english.
reggiexp said:
Same here now with notification from greenify... ****ing facebook wakes u every 5min... Anoying.. With the only 2gb ram my phone laggs... Lg g3... Anyway. I will uminstall ans see if my phone gets faster
Click to expand...
Click to collapse
Dump the horrible facebook app and work through the FB web site instead. Or give Hermit a whirl to speed things up even further.
Davey126 said:
Dump the horrible facebook app and work through the FB web site instead. Or give Hermit a whirl to speed things up even further.
Click to expand...
Click to collapse
i did deleted on my lg g3
but on on a 3gb phone it works fine
Hello,
So I was using Greenify and hibernate Facebook app, but with the last week or so. My facebook app sometime doeasnt load, showing "cant connect right now" and I tried to search google. most issues I've found are Greenify's issue on facebook, especially when facebook got hibernated and woke up for a long time. I had to restart my device to getting facebook working again, ridiculous.
so any workaround on this? As we know that facebook app is the worst battery sucker.
I'm using Resurrection Remix 7.1.2 on Mi 5s Plus, rooted and privileged
Thanks.
Best option is to use one of the 'lite' Facebook alternatives which preserve functionality without the corresponding hit on battery life and data consumption. Also make sure non of Greenify's alternative doze/hibernation modes are enabled (aggressive/deep/shallow) as they are known to create side effects with few, if any, corresponding benefits on Android 6 and above. Good luck.
I use greenify in shallow hibernation mode and Facebook works fine and doesn't eat much battery.
I been having huge RAM consumption with UC web browser, the app has a continuous foreground activity. Now, this is only app that keeps running on background and draining my battery. Is there anyway to force UCbrowser to hibernate using the shortcut hibernate icon? I mean instead of manually open the Greenify, the hibernation icon on my desktop shortcut should do the job.
I know that Greenify does not hibernate an app with constant foreground activity but UCbrowser is way too aggressive. Ironically, i don't want to uninstall UC because i like the browser functionality but only for browsing the web not its constant background activity.
I already turn off all of its in-app notifications such as Facebook, updates, news, ads, and even the "system" notification which i found inside the UC.
I hope someone can help me dealing this problem.
MrBrowseGierza said:
I been having huge RAM consumption with UC web browser, the app has a continuous foreground activity. Now, this is only app that keeps running on background and draining my battery. Is there anyway to force UCbrowser to hibernate using the shortcut hibernate icon? I mean instead of manually open the Greenify, the hibernation icon on my desktop shortcut should do the job.
I know that Greenify does not hibernate an app with constant foreground activity but UCbrowser is way too aggressive. Ironically, i don't want to uninstall UC because i like the browser functionality but only for browsing the web not its constant background activity.
I already turn off all of its in-app notifications such as Facebook, updates, news, ads, and even the "system" notification which i found inside the UC.
I hope someone can help me dealing this problem.
Click to expand...
Click to collapse
There are many fine browsers with great feature/functionality that do not exhibit insidious UC behaviors. That said, recent Greenify builds permit ignoring foreground activity. Highlight the UC entry in your watch list and open the overflow (3-dot) menu for options.
@MrBrowseGierza: Personally, I absolutely concur with @Davey126's statement. I use the following two browsers, FOSS Browser and Firefox Klar, but I'm aware that their functionalities do not necessarily serve everybody's requirement. Especially Firefox Klar only carries a very bare minimum and is clearly focused on privacy, and as usual you must first familiarise yourself with their user interfaces. But for those two, I can clearly promise a very decent battery usage. Another personal option could be Fennec.
Anyhow, what I don't understand really: Gratefully, you were able to clearly identify a source, the root for heavy battery drainage but you only want to fight the symptoms and not cure the buddy. I don't know if this is the right way?
EDIT: Without haven't ever UC Browser installed and no own personal look into it, I checked Exodus Privacy just for fun, and I know for sure I wouldn't install or use it: https://reports.exodus-privacy.eu.org/reports/14541/
Davey126 said:
There are many fine browsers with great feature/functionality that do not exhibit insidious UC behaviors. That said, recent Greenify builds permit ignoring foreground activity. Highlight the UC entry in your watch list and open the overflow (3-dot) menu for options.
Click to expand...
Click to collapse
that's really manual way to greenify UC, I guess UC developers see-through this that's why they took advantage with this not hibernating apps with foreground activity.
I really hope greenify can fix this flaw.
MrBrowseGierza said:
that's really manual way to greenify UC, I guess UC developers see-through this that's why they took advantage with this not hibernating apps with foreground activity.
I really hope greenify can fix this flaw.
Click to expand...
Click to collapse
Flaw?? Hardly. Intentional actions that should serve as a red flag. A few comments:
- method I referenced is fully automated
- hibernated apps can be restarted unless 'wake-up' paths are severed
- there can only be one active 'foreground' app; everything else is background
- there is no "flaw" for Greenify to address
Davey126 said:
Flaw?? Hardly. Intentional actions that should serve as a red flag. A few comments:
- method I referenced is fully automated
- hibernated apps can be restarted unless 'wake-up' paths are severed
- there can only be one active 'foreground' app; everything else is background
- there is no "flaw" for Greenify to address
Click to expand...
Click to collapse
:good:
MrBrowseGierza said:
that's really manual way to greenify UC, I guess UC developers see-through this that's why they took advantage with this not hibernating apps with foreground activity.
I really hope greenify can fix this flaw.
Click to expand...
Click to collapse
In my opinion, UC Browser is intentionally coded the way that it permanently collects and transmits data of its users, and in turn obviously for the burdon of battery capacity or RAM/CPU. Just a few ideas are linked:
https://en.wikipedia.org/wiki/UC_Browser (see paragraph "Security & Privacy)
https://citizenlab.ca/2015/05/a-chatty-squirrel-privacy-and-security-issues-with-uc-browser/
http://androroot.com/2017/08/is-really-uc-browser-is-safe-risk-and.html
A web-search provides additionaly information.
MrBrowseGierza said:
that's really manual way to greenify UC, I guess UC developers see-through this that's why they took advantage with this not hibernating apps with foreground activity.
I really hope greenify can fix this flaw.
Click to expand...
Click to collapse
What Davey126 meant is that you can control UC browser by following the steps mentioned by him.
Disable password for device
2ISAB said:
Disable password for device
Click to expand...
Click to collapse
???
tnsmani said:
???
Click to expand...
Click to collapse
Sometimes, having a password setup on the device, prevents greenify from auto hibernating. It's a one in ten shot...
2ISAB said:
Sometimes, having a password setup on the device, prevents greenify from auto hibernating. It's a one in ten shot...
Click to expand...
Click to collapse
Urban legend; have never heard/seen this. Knowing what happens when Greenify attempts to initiate post screen-off hibernation on an unrooted device (via accessibility) strongly suggests the presence of a lockscreen password is not in play.
Davey126 said:
Urban legend; have never heard/seen this. Knowing what happens when Greenify attempts to initiate post screen-off hibernation on an unrooted device (via accessibility) strongly suggests the presence of a lockscreen password is not in play.
Click to expand...
Click to collapse
It deactivates auto when screen off (greenify) as soon as a password is setup on a urooted N7. fyi
I remember how much of a pain it was searching forums for a simple solution.
OP doesn't mention Android version...
2ISAB said:
It deactivates auto when screen off (greenify) as soon as a password is setup on a urooted N7. fyi
I remember how much of a pain it was searching forums for a simple solution.
OP doesn't mention Android version...
Click to expand...
Click to collapse
Interesting. There have been random public reports of Automatic Hibernation becoming disabled - either spontaneously (GUI slider doesn't stick) or after a period of time. It always seems isolated with no correlation to device, rom, etc. It feels like a permissions issue, although none are required for basic use.