Related
hi
is there any app that blocks another apps to start. for example if i close the facebook app and remove it from the memory with the task manager, facebook starts after 10 seconds again. i dont mean apps like task killer that kill the app after it started. i hope you understand my question
Sorry for my bad englisch
Autostarts, startup manager, and system tuner.
Sent from Failtrix, the crappiest phone on the market.
Rom toolbox I think does this
Sent from my SGH-T989 with Cyanogenmod 9 Nightly Power.
emyaz said:
hi
is there any app that blocks another apps to start. for example if i close the facebook app and remove it from the memory with the task manager, facebook starts after 10 seconds again. i dont mean apps like task killer that kill the app after it started. i hope you understand my question
Sorry for my bad englisch
Click to expand...
Click to collapse
Android by design kill tasks when the resources become sparse. For this to work, an app must be able to request to be restarted once this occurs - the app (or more correct, "service") is sticky. This is why when you close the facebook app, it's restarted within seconds anyway.
If you are running Android 4 (ICS) or later, you can tell the phone not to autostart apps at boot directly from the Settings menu. Enter settings -> apps -> all, select e.g. Facebook, then click the button "Disable". Now it's gone, and for real this time! The disable button is at the place on the "Uninstall" button, and uninstallable apps are not possible to disable this way - but you can always remove them.
Some apps are neither disable nor uninstallable, though.
But if the autostart app is parental control r something like that, it wold be harder. Firstly the thing would not let you to settings. You could fool it when some settings notification appears, like there is wifi, by clicking on it you will get there without a problem, but you would not be able to delete it. To deal with it, I do personally recommend this: Root your device, get total commander for android (no, trust me, ES would not make it), open TC, get to mnt/asec where are stored installed apps files, find folder attached to that app, change the permisions that everybody could write in it, change ownership and group to some of your other apps and delete that folder. At the end, there shoul be emty folder with an emty folder in it. That should **** up the app so much that its not going to work anymore. Now you can do whatever you want.
Use Purify app
u can use boot manager module in xposed
I'm using clean master and it allows me to bock these app from autostarting.
It can solve by greenify pro smartly. You can google for greenify. After installing greenify (xposed installer) (need allow some feature) allow the modules it will work 100℅. If any errors message me on Facebook/n3xt2u
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:
How to remove whats app from greenify? the new update doesn't show any option or may be I am missing something obvious. I don't want whatsapp to be hibernated
Did you try to highlight Whatsapp in the hibernated list and click the menu button? You will see the option to degreenify the selected app. Click that and it is degreenified.
tnsmani said:
Did you try to highlight Whatsapp in the hibernated list and click the menu button? You will see the option to degreenify the selected app. Click that and it is degreenified.
Click to expand...
Click to collapse
In teh latest version when I highlight it then shows 2 options one is X another is zzZ I clicked on X so whats app is no more in hibernated list but I am still not getting messages unless I open whatsapp
which means it still is hibernated.
I got the message saying
"Despite degreenified apps still stay in hibernation until you wake it up by explicitly launching it" so I have opened it its not in the app list but still remains hibernated.
Am I missing something? cant I get whatsapp back out working normally?
Those options are for hibernating (zzZ) and cutting off the wake up path (not X but a scissor). What you should have done is to click the menu button (three vertical dots). Then you would have got the option for degreenifying. What you seem to have done is to cut off the wake up path.
You can try to clear the cache and data of Greenify and see whether Whatsapp works. But it will involve selecting all the apps again to greenify. Otherwise I think that you may have to uninstall and reinstall Whatsapp.
I am not an expert on this so wait for some more comments before attempting to do anything.
Actually new version changed a bit so I could not find those option, anyway Just restarted the phone & seems what app is running now, I can see it in running apps will wait to get a message, hopefully its working now.
sgsI9003 said:
Actually new version changed a bit so I could not find those option, anyway Just restarted the phone & seems what app is running now, I can see it in running apps will wait to get a message, hopefully its working now.
Click to expand...
Click to collapse
IF you are facing similar problem in the future, you could actually backup your WhatsApp conversations (TiB or other backup tools you admire) and uninstall WhatsApp. After uninstalling, reboot, and then reinstall WhatsApp. Launch WhatsApp first and then attempt backup restore for your WhatsApp app.
This is a known problem and proved to some people faced it. Unfortunately however, Greenify has no way to fix this, as this is much more in behalf of WhatsApp's fault. You can search in the old thread if you are interested.
Remove Apps from Auto-Hibernation
1. Open Greenify App
2. Look for the app you want to keep open under the "Pending Manual Hibernation" list.
3. Press AND HOLD the app for a few seconds.
4. When new menu appears across the top, press the "X" button to remove it from the auto-hibernate list.
This is for Greenify App v2.8.1 on Android (Galaxy Note 5 on AT&T Network).
Trying to de-greenify stopwatch/timer app
I have a stopwatch and timer app which does not sound its alert when Greenify is active. If I force stop Greenify I get the alerts. The app does not show on Greenify's list of hibernated apps , even when a timer is in progress, so I can't work out how to de-greenify it.
Any ideas?
itm said:
I have a stopwatch and timer app which does not sound its alert when Greenify is active. If I force stop Greenify I get the alerts. The app does not show on Greenify's list of hibernated apps , even when a timer is in progress, so I can't work out how to de-greenify it.
Any ideas?
Click to expand...
Click to collapse
- if on MM/Nougat remove app from optimize list using ROM interface
- avoid using aggressive/shallow doze (experimental features)
auto hibernate when app is closed : eg. FB, music players many other apps & services stay on even no need after closing.
If anybody know how to auto stop these with other apps or tricks, plz let me know!?
Per App Hacking doesn't help..
------
auto start when screen is on : eg. I don't need clean master to stay on when I'm not on wifi and screen is off.
again, any workaround for this?
Greenify is already the greatest app out there, but if it had these features, it would b God of apps IMHO
kennyk09 said:
auto hibernate when app is closed : eg. FB, music players many other apps & services stay on even no need after closing.
If anybody know how to auto stop these with other apps or tricks, plz let me know!?
Per App Hacking doesn't help..
------
auto start when screen is on : eg. I don't need clean master to stay on when I'm not on wifi and screen is off.
again, any workaround for this?
Greenify is already the greatest app out there, but if it had these features, it would b God of apps IMHO
Click to expand...
Click to collapse
I think that you have not understood the working of Greenify correctly. It comes into play for hibernation only after the screen is off. When screen is on, it merely collects info about the apps that are running, closed etc to determine which apps are to be hibernated once screen is off.
Reg. auto hibernation, do you have root and have you enabled it in Device Administrator and Accessibility under Settings? Under which mode are you running Greenify: Root, Boost or Unrooted? And have you enabled Auto hibernation within Greenify and selected the apps to be greenified?
Check the thread title
tnsmani said:
I think that you have not understood the working of Greenify correctly. It comes into play for hibernation only after the screen is off. When screen is on, it merely collects info about the apps that are running, closed etc to determine which apps are to be hibernated once screen is off.
Reg. auto hibernation, do you have root and have you enabled it in Device Administrator and Accessibility under Settings? Under which mode are you running Greenify: Root, Boost or Unrooted? And have you enabled Auto hibernation within Greenify and selected the apps to be greenified?
Click to expand...
Click to collapse
It's a wish list. you don't understand what wish list is?
I fully understand how Greenify works.
Use Tasker and task kill plugin.
And for Greenify create hibernate shortcut and don't forget that it won't hibernate of application is in recent Apps list.
It's easy to kill every app on exit.
Just use LMT(PIE) app , and instead of standard ''home, or back button'' use ''KILLAPP'' button from PIE menu.
In combination with greenify it works fine.
I was think to use only PIE(pie ''kill app process'' on exit), but this is not the same, greenify realy put this apps in hibernation.
So i must use combination of these 2.
Would be great, that greenify do this itself..
Firstly, I'm a non-root user of Greenify. When I first installed it (over a year ago, I believe), I was able to add most of my apps to hibernation (by hitting the "+" button and then "show all apps", then "More" at the bottom, and then choosing the apps from there. I admit, I have many apps installed (I know, it's not great and I tend to collect apps more than I use them but that's why I installed Greenify) so once I went to hibernate all those apps, it would take a bit but eventually go through with the additions. From then on, I would periodically add newly installed apps to the hibernation protocol through the same routine (+, Show all apps, More). I hadn't installed new apps for awhile until recently, when I decided to do another round of additions but for the past few months, any time I've tried, I get the loading circle for a second before it freezes and nothing happens - I have to close the app and reopen it only to run into the same issue again. I can hibernate the apps previously added with the widget and from the app itself but I can't add any new ones to the hibernation list. I've tried multiple times and even let my phone sit there with the frozen spinny circle to see if it just needs time to load but after 5 whole minutes of waiting, I had to give up. I do have a lot of apps but most of them have been given the hibernation treatment so the remaining pool of apps to be added to the list should be relatively small and when I choose the option to "hibernate system apps", system apps show up in the list when I hit the "+" (although I haven't added any system apps to the hibernate list for fear I could mess with my phone's functionality) but I when I hit the "More" option at the bottom, it does the same spinny-circle freeze thing again and marking or not marking "show all apps" makes no difference. I have a Galaxy S8, update to Oreo 8.0 so I'm wondering if this is an issue I'm running into because of the update, but I think I had this problem before joining the Beta. Any help would be greatly appreciated. I also have the donation package - I've had it since shortly after installing Greenify and there weren't any problems since then before the last few months. Thanks!
ActionGabby said:
Firstly, I'm a non-root user of Greenify. When I first installed it (over a year ago, I believe), I was able to add most of my apps to hibernation (by hitting the "+" button and then "show all apps", then "More" at the bottom, and then choosing the apps from there. I admit, I have many apps installed (I know, it's not great and I tend to collect apps more than I use them but that's why I installed Greenify) so once I went to hibernate all those apps, it would take a bit but eventually go through with the additions. From then on, I would periodically add newly installed apps to the hibernation protocol through the same routine (+, Show all apps, More). I hadn't installed new apps for awhile until recently, when I decided to do another round of additions but for the past few months, any time I've tried, I get the loading circle for a second before it freezes and nothing happens - I have to close the app and reopen it only to run into the same issue again. I can hibernate the apps previously added with the widget and from the app itself but I can't add any new ones to the hibernation list. I've tried multiple times and even let my phone sit there with the frozen spinny circle to see if it just needs time to load but after 5 whole minutes of waiting, I had to give up. I do have a lot of apps but most of them have been given the hibernation treatment so the remaining pool of apps to be added to the list should be relatively small and when I choose the option to "hibernate system apps", system apps show up in the list when I hit the "+" (although I haven't added any system apps to the hibernate list for fear I could mess with my phone's functionality) but I when I hit the "More" option at the bottom, it does the same spinny-circle freeze thing again and marking or not marking "show all apps" makes no difference. I have a Galaxy S8, update to Oreo 8.0 so I'm wondering if this is an issue I'm running into because of the update, but I think I had this problem before joining the Beta. Any help would be greatly appreciated. I also have the donation package - I've had it since shortly after installing Greenify and there weren't any problems since then before the last few months. Thanks!
Click to expand...
Click to collapse
You may have to go through a tedious process. Clear the data and cache of Greenify, uninstall it, reboot and then reinstall it. Grant the necessary permissions through adb. Then choose all the apps that you want to hibernate. Other than this, I don't think that there is any other way to solve your issue.
Be aware that backing up and restoring the settings of Greenify may also restore the issue you are facing.
tnsmani said:
You may have to go through a tedious process. Clear the data and cache of Greenify, uninstall it, reboot and then reinstall it. Grant the necessary permissions through adb. Then choose all the apps that you want to hibernate. Other than this, I don't think that there is any other way to solve your issue.
Be aware that backing up and restoring the settings of Greenify may also restore the issue you are facing.
Click to expand...
Click to collapse
Also recommend being judicious about what apps are added to Greenify's action list. With the introduction of doze Android does a pretty good job reigning in resource abusers. Adding a huge portfolio of apps to Greenify has few/no upsides and can potentially lead to greater resource consumption and poor overall device behavior. Greenify is best used for targeted action against demonstrated 'bad actors' that do not respond well to native resource management. On Oreo your list of Greenified apps should be quite small.