Auto-hibernation not working ? - Greenify

Hello.
So, I got greenify. I always thought it was a free app, but for the first time this week I really started using it and when I tried to hibernate some pre-loaded (system) apps, it didn't let me without the donation package. I thought "ok, maybe it's better. Paid apps generally know what they are doing".
But to my surprise, apps like YouTube, even Samsung's "Clock" and others, keep coming back, and even non-pre-loaded apps (such as facebook) do not stay in hibernation (at least, I always see them under the "Will hibernate in a few minutes when screen"... by the way, "when screen" what ?). So I always have to manually hibernate apps I open and use, and some keep waking up on their own anyway (when greenify promises they won't, that one has to manually execute apps for them to wake up, then that they will auto-hibernate once closed). I might be actually disappointed in paying for this. It's not working, and I turned greenify "on" in "accessibility" too.
Also, I don't want to risk flashing Xposed to still be able to get notifications when I already use TWRP and SuperSU (and my ROM is official, yet customized by myself, since I uninstalled all bloatware, then just backed up the new ROM with TWRP and reinstalled it), plus, Xposed says it is compatible with "6.0", so Idk if that includes Android 6.0.1 or not. But I wish Greenify's devs had been smart enough not to kill every push notifications.
Any greenify experts out there whom know how to finally make auto-hibernation work by itself, and make apps like Facebook quit being stubborn ?
Any light with getting notifications still too ?
Thanks in advance.

Apps that wake up on device's boot:
Camera
Clock
Featured (apps) *widget
Email (Samsung app)
Facebook
Galaxy Apps
Gallery
Gmail
Play Music
Google+
Hangouts
Internet (Samsung's browser)
Maps
Memo (Samsung)
Messenger (Facebook)
My Files (Samsung)
Opera Max
Photos
Recarga Certa (Samsung's app for adding creds to SIM)
Smart Manager
Theme Store
Twitter
Video (Samsung)
YouTube
Some of these are the ones that keep waking up during operation (not just on boot), such as Facebook, Clock and Opera Max.

Related

A few questions about how to use Greenify efficiently

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:

[Q] System apps automatically wake up after Greenified

Hi. My phone is rooted and using Greenify Donation Package. I have greenified some system apps which I never use it like Google+, Google Search, Hangout, Google Stand, Google Movies. However, I realized that those apps automatically wake up by itself eventhough I never open them. Anybody experiences like this?
They always do. In Google's scheme of things, everything is interconnected.
If you open even a paid third party app, it will wake up Playstore which will in turn wake up Download Manager.
What you should do is, when the app greenified by you shows up in the 'to be hibernated' section, highlight it by touching it. You will see a scissors icon along with zzz. Click the scissors icon and you will get a dialog box which will inform you which app/process woke the app. If you are sure that you do not want the app to be woken up by the app/process shown, you can click 'continue' and the link will be severed. After that, the greenified app will not be woken up by that app/process.
But be sure of what you are doing, because if you cut an essential link, something may cease to work and you may end up with a dead phone.
Thanks a lot tnsmani
mind741 said:
Hi. My phone is rooted and using Greenify Donation Package. I have greenified some system apps which I never use it like Google+, Google Search, Hangout, Google Stand, Google Movies. However, I realized that those apps automatically wake up by itself eventhough I never open them. Anybody experiences like this?
Click to expand...
Click to collapse
If you don't use them, try to freeze them

[Q] Finally realised something about greenify

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.

Facebook app and Greenify

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.

Nexus 5X weird behavior (malware?), possibly caused by FB Messenger or Pixel Launcher

Some very weird things started happening on my phone earlier today. It's a Nexus 5X, running 8.0 Oreo, with the October security patch. I'm not rooted and I'm careful about what I install. The phone is fairly new, from this summer.
I will begin with describing what I did in the hours before this started. I can think of two things that possibly could have started it:
1) Two of my Facebook contacts sent malicious links to me an hour before. It looked like Youtube videos but was not. I did NOT open any of these links, knowing directly they were harmful (not sure if you can be affected by just receiving them, not clicking on them?). I received them in the Messenger Lite application (an official app from Facebook with scaled-down functionality).
2) A few hours before the Facebook links, I sideloaded an APK containing the new Pixel Launcher. I got the APK from Android Police/APK Mirror.
Can't attach links, but Google for: Hands-on with the updated Pixel Launcher, including the new Pixel 2 features [APK Download]
The APK was working fine and nothing seemed odd with it (I used the launcher for a few hours). As long as Android Police know what they uploaded, this shouldn't be the cause for my problems. I bet on Facebook Messenger instead. (People that click such malware links typically get their Facebook accounts hacked, however my account seems fine and my account didn't spam others with the same link. I did not change password or did anything else to "recover" my account yet).
So what happened after this on my phone?
Here is the first thing I noticed. I open Play Store to install updates. It turns out I have one update pending, it's called BankID. This is a major Swedish app used by nearly every smartphone user in the country, and it's for signing into government websites, bank websites, insurance company websites, and much more. When I click update in Play Store two things happen almost instantly:
1) Six pictures are downloaded from Messenger Lite to my phone. That makes no sense, how could clicking a button in Google Play trigger something to happen in Messenger Lite? In fact I tried it three times, with the same behavior every time. (Well, actually opening the Messenger Lite photo album, there are only photos there I already downloaded, so nothing new seems to be added there - but the photos were probably re-downloaded I believe).
2) The BankID update downloads to 100 % (the downloading takes a little longer than expected), then it halts and does nothing, i.e. it's not installing. No error message, it just stops there. I can choose to abort and try again, which I do three times or more, with exactly the same behavior.
Also, I now notice Play Protect hasn't run for two days, but when I try to run it, it seems to be down. After ~30 seconds of scanning it says "App verification temporarily down". "App verification temporarily down" could very well be connected with the halted update I just described? It still says it hasn't run for two days after this.
When I experiment, I notice other things that are very weird indeed.
1) Notifications in Gmail, Snapchat and possibly other apps aren't coming through. By opening the apps, I can sync manually.
2) When I move a file to a new folder using the Downloads app (Files app, stock one) I get a error message saying the move operation failed. This also triggered the photo notifications from Messenger Lite (same behavior as described above, with six photos). However, after a while the moved pictures are indeed in the right folder, even though the error message saying otherwise.
3) After some time I remove "app data" for the Google Play app. When I open it after that, there are now three app updates pending (e.g. Google Wifi also). But the same behavior occurs, when I try to download one or all of them, I get the Messenger photo notifications and the updates halt at 100 % without installing. So the BankID app - which could be targeted by attackers for obvious reasons - could just be a coincidence. It could have happened with any app I suppose, this was the only one pending right then. But still, why couldn't Play Store detect other pending app updates until I refreshed it the way I did? Was Play Store blocked from connecting to Google (or forced to connect to some other server, perhaps?).
What did I do after all of this?
I uninstalled three apps:
-Facebook Lite
-Facebook Messenger Lite
-Pixel Launcher APK
However the uninstall process was very odd. A process called "Package Installer" had a notification saying "Uninstalling Lite" and "Uninstalling Messenger Lite". It didn't seem to be working, it was stuck after some time. I restarted my phone and the apps seem to be gone now, at least they aren't listed in Settings --> Apps. So the uninstall process was successful I suppose, even though it didn't seem to work.
After I restarted my phone I also noticed:
-When I install Messenger Lite from Play Store now, it's easy to uninstall it the way it should be - in mere seconds.
-When I open Play Store, updates are now installing fine. Play Protect is also scanning fine now.
Everything looks back to normal now. But I'm not trusting my device. I'm gonna factory reset it. Before I do, I wonder:
-Can I feel safe the wipe would erase whatever malware I might have had on the phone?
-Is there something I could do to let us know what caused this? Upload a log here somehow?
The only piece of advice I have received as of now is: "Try restarting in safe mode, installing some AV software, and generally looking for suspicious processes." I haven't done that yet, would it still be a good thing to do? Must I install AV software before rebooting into safe mode, or could I install it directly from safe mode? (App suggestions, AV software?).
Usually I'm very careful and security-minded. I haven't had something like this happen before. So I'm very intrigued and mad about this. I'm gonna change my Google account and Facebook account passwords later on I think (I already have 2-factor authentication enabled).
One last thing: When I install Pixel Launcher on my non-rooted phone, it's not running as a system app if my understanding is correct. (At least it shouldn't be). But none the less, when I wanted to uninstall it I had to go into Settings --> Apps and tap "Show system apps" to find it in the list. Is that normal? Perhaps it doesn't mean anything, I just want to know.
Thanks for your advice in advance. Anything else to add? What should I do know? All you might have to say is appreciated.
Come on now guys, someone must be able to help?
If I factory reset the device, will it be clean? I didn't mess with custom ROMs, root, the bootloader or something else. (I suppose the bootloader is locked).

Categories

Resources