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:
Hi,
I am using the latest Greenify version (donation package) v2.6.2 in order to hybernate some apps causing wakelocks when my phone is in stand-by mode. I was also trying to hybernate all the google apps, such as google play store or google play services, which worked out perfectly by cutting off some reactivation paths.
In order to update my apps weekly or monthly I wanted to take these apps from the greenify list, which was successful at first glance. However, I am now facing problems in regreenifying them, especially when it comes to the google play services. I have no idea why, but this times greenify always tells me that it fails to hybernate google play services for no apparent reason. Also it does not show me the scissors tool to cut off the wakelock paths.
Has anybody of you experienced the same problems? Is there any solution for my problem? Thank you for your help!
If you use beta 5, that's why:
Beta 5
Foreground app no longer hibernates even if "state always ignored" is checked.
Reduced the impacts of wake-up cut-off.
FIX: Native processes cleaning.
FIX: Wake-up action in Tasker plug-in on Android 5.x.
FIX: No longer list disabled apps.
Click to expand...
Click to collapse
MihaiSG said:
If you use beta 5, that's why:
Click to expand...
Click to collapse
Actually not, I am using version 2.6.2 according to the application.
I have seen problems after I hibernate an app called " Google App" similar issues
Still the same problem. Reinstallation of greenify and Xposed didn't work out, unfortunately. Did they change something inside of greenify without a new version?
Team - I am running the latest version of greenify posted on the playstore. I've followed guides for enabling agressive doze on android 6.0 on my moto x pure (non root) -- including adbing to the device to grant permissions on the app. It seems to be working most of the time. The device seems to go to sleep and i've seen a great increase in battery. However, seemingly randomly i'll notice battery draining fast. When i look at my usage its google play services keeping the device awake 100% of the time. If i reboot the phone, google play services stops doing that and all is well for awhile, till it repeats. I've been unable to find the cause of this. I imagine i'm missing some information that we might need to track this down. thanks in advance!
tange1 said:
Team - I am running the latest version of greenify posted on the playstore. I've followed guides for enabling agressive doze on android 6.0 on my moto x pure (non root) -- including adbing to the device to grant permissions on the app. It seems to be working most of the time. The device seems to go to sleep and i've seen a great increase in battery. However, seemingly randomly i'll notice battery draining fast. When i look at my usage its google play services keeping the device awake 100% of the time. If i reboot the phone, google play services stops doing that and all is well for awhile, till it repeats. I've been unable to find the cause of this. I imagine i'm missing some information that we might need to track this down. thanks in advance!
Click to expand...
Click to collapse
That may not have anything to do with Greenify unless you have greenified Play Services. If you have, remove it from hibernation.
Usually Play Services will go berserk upon updating itself in the background. What you can try is clear it's data and cache and reboot. If you have TWRP, do it in recovery. If not, do it in Settings>Apps.
tnsmani said:
That may not have anything to do with Greenify unless you have greenified Play Services. If you have, remove it from hibernation.
Usually Play Services will go berserk upon updating itself in the background. What you can try is clear it's data and cache and reboot. If you have TWRP, do it in recovery. If not, do it in Settings>Apps.
Click to expand...
Click to collapse
Thanks for the info. Here's what i've done:
I removed greenify, performed the actions you suggested and left greenify off for about 12 hours. No issues with google play services and keep awake. I reinstalled greenify and everything was good for a number of hours. Unfortunately the play services keep awake started again about 3.5 hours ago. The phone has a solid 'awake' bar in battery settings and play services is the culprit with 3.5 hours awake. While i dont blame greenify, there's some sort of correlation of events here that I can't explain.
tange1 said:
Thanks for the info. Here's what i've done:
I removed greenify, performed the actions you suggested and left greenify off for about 12 hours. No issues with google play services and keep awake. I reinstalled greenify and everything was good for a number of hours. Unfortunately the play services keep awake started again about 3.5 hours ago. The phone has a solid 'awake' bar in battery settings and play services is the culprit with 3.5 hours awake. While i dont blame greenify, there's some sort of correlation of events here that I can't explain.
Click to expand...
Click to collapse
Do you have Xposed? If so, install AppOpsXposed and untick the "Keep Awake" function of Play Services. Another thing you can try is uninstalling the update to the Play Services, reboot and then manually update it and again reboot.
If it is still not arrested, Google is your friend.
Unfortunately I've the same problem on my OnePlus 2 with stock ROM. I've installed Greenify two days ago, and enabled aggressive doze with amazing results! Last night I enabled Doze on the Go (using ADB) and since unplugging my phone this morning there is this constant wakelock of Google Play Services. Disabling Doze on the Go as well as reinstalling Greenify didn't help. Looking forward to a solution!
This is a known problem. Sometimes it's worse and sometimes less, but Google Play Services is a known offender in this manner. And Google processes in general. Part of the reason for this is that Google often wakes up your device, periodically, to track your location (horrible, yes, and it continued to happen for me even when all Google location options I could find, as well as GPS, were turned off).
Solutions that have reportedly worked for some people in the past (try one at a time or all of them) - they don't require root:
-Make sure you do not Greenify/freeze/hibernate Google Play Services, or similar processes, as this may make the issue worse.
-Clear cache and data of Google Play Services.
-Manually update Google Play Services to latest APK version available from your device, downloaded from the web. Make sure you select the right version for you. http://www.apkmirror.com/apk/google-inc/google-play-services
-Try turning off as many Google background features as you can, such as location tracking/history, etc.
I guess some of these steps may only work after the next reboot, so reboot the device when you're done.
But as I said, this process is a known big offender. The above may not work, or may work temporarily. The stronger and more permanent solutions require root (you don't really need to try the above options if you do these). The more of them you do, the less 'keep awake' you should experience:
-Install Xposed Installer app and install Xposed Framework, so you can use the modules mentioned below...
-Use AppOpsXposed module (or CM Privacy Guard if you have it) to deny keep awake permission to Google Play Services, and other Google background apps.
-This is a big one: Install Amplify (Xposed module) from the Play Store, and it will automatically take care of limiting Google wakelocks. That's it. If you pay for the pro version, then you can additionally tweak and limit all wakelocks, alarms and services on your device (pretty cool and useful, but more involved, so for advanced users).
Cultar said:
..............
-This is a big one: Install Amplify (Xposed module) from the Play Store, and it will automatically take care of limiting Google wakelocks. That's it. If you pay for the pro version, then you can additionally tweak and limit all wakelocks, alarms and services on your device (pretty cool and useful, but more involved, so for advanced users).
Click to expand...
Click to collapse
The unpaid version of Amplify will block a maximum of a couple of wakelocks related to location. Only the pro version is capable of blocking other wakelocks and alarms including those of Play Services. But as you said, it is not automatic and you will have to set it up.
Any updates on this?
Google play services is awful
MSK1 said:
Any updates on this?
Google play services is awful
Click to expand...
Click to collapse
Not a Greenify issue. Some devices/ROMs/configs seem more susceptible to GPS runaway. Clearing GPS cache+data on occasion followed by an immediate reboot has proven helpful for some. Good luck.
The Greenify app (root mode) identified a particular Broadcast Receiver, the "PackageMonitorReceiver$RegisteredReceiver", that wakes up the Play Store whenever certain apps are booted on certain occasions. I applied the cutoff, but the Play Store still pops up in Greenify every time I start up my VPN app, not only ignoring the cutoff but apparently ignoring the fact that the app has been run multiple times (the Intents are package_added, package_removed, package_changed, package_first_launch, and external_applications_(un)available; I'm not sure which one it might be reacting to).
I do not even have to activate the VPN service for this to occur, only launch the app. For other apps, the Play Store will run in the background on the first bootup but will stop afterwards. Both brand new apps and this VPN app will still cause the Play Store to reenable its Receiver service (which I disabled in MyAndroidTools only to see it reactivate itself each time I use another app) and ignore Greenify's path cutoff despite the cutoff still being active and recognized within the client: Greenify shows that the VPN app is what woke the Play Store up and that the wakeup path has already been cut off. This may not be a Greenify "problem" but it might be worth mentioning that the cutoff isn't being honored.
animeme said:
The Greenify app (root mode) identified a particular Broadcast Receiver, the "PackageMonitorReceiver$RegisteredReceiver", that wakes up the Play Store whenever certain apps are booted on certain occasions. I applied the cutoff, but the Play Store still pops up in Greenify every time I start up my VPN app, not only ignoring the cutoff but apparently ignoring the fact that the app has been run multiple times (the Intents are package_added, package_removed, package_changed, package_first_launch, and external_applications_(un)available; I'm not sure which one it might be reacting to).
I do not even have to activate the VPN service for this to occur, only launch the app. For other apps, the Play Store will run in the background on the first bootup but will stop afterwards. Both brand new apps and this VPN app will still cause the Play Store to reenable its Receiver service (which I disabled in MyAndroidTools only to see it reactivate itself each time I use another app) and ignore Greenify's path cutoff despite the cutoff still being active and recognized within the client: Greenify shows that the VPN app is what woke the Play Store up and that the wakeup path has already been cut off. This may not be a Greenify "problem" but it might be worth mentioning that the cutoff isn't being honored.
Click to expand...
Click to collapse
If you have Xposed Framework installed try the MyAndroidTools module which attempts to address this behavior.
Davey126 said:
If you have Xposed Framework installed try the MyAndroidTools module which attempts to address this behavior.
Click to expand...
Click to collapse
Don't have Xposed, unfortunately. If possible, I'd like to avoid it anyway
animeme said:
Don't have Xposed, unfortunately. If possible, I'd like to avoid it anyway
Click to expand...
Click to collapse
Understand, but recognize w/o Xposed you loose access to more advanced tools and methods - including those utilized by Greenify that are not entirely contained to user selectable Xposed features.
Davey126 said:
Understand, but recognize w/o Xposed you loose access to more advanced tools and methods - including those utilized by Greenify that are not entirely contained to user selectable Xposed features.
Click to expand...
Click to collapse
Yea, it seems Deep Hibernation was required. Unfortunate since I had just gotten safetynet working with microg. Oh well, thanks for the bad news :silly:
Can I disable permanently Google play protect? Or Google play protect not allowed to uninstall an app I want.
Hello Arist!
Here are some instructions i found by googling. Does it help you?:
How to Disable Play Protect
Settings.
Google.
Security.
Google Play Protect.
Tap on Cog-wheel.
Select Scan apps with Play Protect to turn it off.
Source: https://www.technipages.com/how-to-enable-disable-google-play-protect-in-android
is it possible to disable google play protect on android tv 9?
I'd like to know any way to disable it on Android TV (shield) as well. I've seen posts saying to turn off verify apps in settings but this doesn't work.
Although I had never turned on Play Protect, tonight I got a notification from Google Play Protect telling me to uninstall a malicious app.
It seems that my device is being permanently monitored by Google, despite deactivating the service.
How can this be prevented?
I would like to be able to determine who is allowed to scan my device and who is not.
And when a service is deliberately deactivated, my expectation is that it is actually switched off.
psychofaktory said:
Although I had never turned on Play Protect, tonight I got a notification from Google Play Protect telling me to uninstall a malicious app.
It seems that my device is being permanently monitored by Google, despite deactivating the service.
How can this be prevented?
I would like to be able to determine who is allowed to scan my device and who is not.
And when a service is deliberately deactivated, my expectation is that it is actually switched off.
Click to expand...
Click to collapse
I also cannot get Play Protect to stop scanning even though I have double, triple, quadruple checked the settings. It is toggled off. Yet it won't stop telling me that I have one app that isn't safe (I know it is, so I'm not concerned)...
Has anyone figured this out yet?
You can try adb
adb shell settings put global package_verifier_user_consent -1
To re-enable play protect:
adb shell settings put global package_verifier_user_consent 1
About an hour ago the freakin' Play Store, which for whatever reason I had defrozen, informed me that “for security reasons” or whatever it had removed permissions from a bunch of apps. Of course Google Play Protect (or maybe is it Google Pay Protect? LoL!) was disabled, as it has always been, but it still removed permissions from my apps. Well, that was enough, my patience ran out.
So, I fully uninstalled Google Play Store. This is the real way to disable Google Play Protect. No more @#$% in my system now.
zecabra said:
You can try adb
adb shell settings put global package_verifier_user_consent -1
To re-enable play protect:
adb shell settings put global package_verifier_user_consent 1
Click to expand...
Click to collapse
Did it work when you tried it?
As far as I remember, when you install a file, they warn you about the danger of downloading viruses, but you can ignore this warning and download anyway.
Does Google Play protect identify payloads created with msfvenom ? I just bought a phone with android 12 and play protect on it. I wanted to install a back door in my phone