Per the subject, the application AutoStarts (https://play.google.com/store/apps/details?id=com.elsdoerfer.android.autostarts&hl=en), which can be used to disable apps that starts automatically (boot time, auto) no longer updated since 2011.
Moreover, it does not seem to work in JellyBean, as some apps I know starts in the background is not shown in the AutoStarts app.
I tried Gemini, but it doesn't tell me WHICH service is starting, so it can actually break the app.
Anyone have recommendation for AutoStarts replacement?
Try Disable Service https://play.google.com/store/apps/details?id=cn.wq.disableservice it receives timely updates and finds services a lot faster than AutoStarts.
youngbrod said:
Try Disable Service https://play.google.com/store/apps/details?id=cn.wq.disableservice it receives timely updates and finds services a lot faster than AutoStarts.
Click to expand...
Click to collapse
I tried that, but like Gemini, it doesn't tell me which services are started during boot or auto start.
I actually had an issue with the app that it won't stay since I turned off all services. I then have to manually try it one by one to see which one is required for the app to function.
ROM Toolbox Pro does what you are looking for, plus lots more. I'm not sure if the lite version does it also.
A newer version of autostarts is at https://f-droid.org/repository/browse/?fdfilter=autostarts&fdid=com.elsdoerfer.android.autostarts
This thread should be in the Q&A section. http://forum.xda-developers.com/forumdisplay.php?f=1236
famewolf said:
A newer version of autostarts is at https://f-droid.org/repository/browse/?fdfilter=autostarts&fdid=com.elsdoerfer.android.autostarts
This thread should be in the Q&A section. http://forum.xda-developers.com/forumdisplay.php?f=1236
Click to expand...
Click to collapse
That's interesting, why would the Dev stop updating it in Play Store?
Anyone genius ??
Why I see the same apps appearing muliple times in Autostarts ?
Does anyone know if you can Freeze the AutoStarts app after making changes to the system and it will still work, or does the AutoStarts app need to actively be running all the time to function?
I'm just basically asking if it's a process that always runs and monitors for these processes starting and stops them, or if it is just something that modifies some Android files and runtime parameters and triggers so that the blacklisted processes don't automatically start on their own in the various specified situations.
Related
When I open some Apps, 10 other Apps open along with it. Is rooting the phone the only way to have access to the means to stop this?
Thanks,
-Adam
Don't pay so much attention. In general, those applications don't use your cpu and battery. Android has its own task manager system.
Yeah dis is even happening to me,the reason is so simple like one app needs the other apps so they are even opening up.
Devil_Dude said:
Yeah dis is even happening to me,the reason is so simple like one app needs the other apps so they are even opening up.
Click to expand...
Click to collapse
what the appl you using which is opening others appl can u name the apps
if you kill apps, they will probably get restarted automatically and left in the background. If the apps are working correctly, this is not a problem, as a well coded app does not use CPU/battery when in the background.
Actually, I just quit using a task manager to kill tasks (I just let Android kill them as necessary) and I have no problems (phone is not slower, power drain is not higher).
Maybe the thing is that after you stop a task in a task manager it does not update immediately and you don't see the task being restarted, and when you go into the task manager after running some app just then you see the apps restarted.
Also, some apps are very generic (maps) and used by other apps, and some apps need to be running all the time (latitude, mail client, widgets, etc.) and killing them would make them not work properly (widgets no longer updating, not getting new emails, etc.).
My advice is to leave the apps running if you are not very sure of what you are doing, because the OS will eventually kill unnecessary apps, and until then they should not use any CPU or battery.
Only thing is to stay away from badly written apps, the ones that use too much CPU even when in the background or when phone is sleeping. You should probably wait for a night after installing a new app to see if you have higher drain. If so, just uninstall and search for an alternative.
shhbz said:
what the appl you using which is opening others appl can u name the apps
Click to expand...
Click to collapse
Like any Google app by searching is opening. Google search and by using voice search its opening voice search app and so on.
Sent from my LG-P500 using XDA App
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 would like to have the maximum of control on running processes, but I feel I have not enough control, so I hope you can help me
I know that being root, managing processes and disable "autoruns" is a quite easy task but unfortunately my device is not an easy to root phone
Furthermore, I saw that Android (4.1.2 Jelly Bean) performance is very bad when you have many apps installed or you used many apps recently. Yes I listen about the internal management and I am aware that it is not a suggested practice but since I want to have control on what is happening and i have serious concerns about the algorithms to free RAM (maybe bull****), so I prefer to do it on my own risk
What I am doing is go to
-Settings, Application manager, Running, "Show cached processes"
- Settings, Application manager, Running, "Show services in use"
Identify what apps are in use and i don't like, then go to
-Settings, Application manager, All,
select app and Click "Force Stop"
Doing it my device has a better performance however, some apps still going alive after some time, for instance: Email ( I saw other in the past)
Using "Autoruns" app and checking "email" app I can see with changes of state can start "Email" however, sometime "email" is reenabled after be manually stopped but none of previous conditions happened.
How can I kill "email" or other app and force to stay off? (disable it and install other email app is not a valid answer)
I would like to use email/others as an standalone app, I mean use when I want and have out of memory when I am not using.
Besides, the autoruns, is there any scheduled task or something like that to open apps?
Of course I want to root my phone and I am waiting until someone will find a proper way to root, in fact I think that an android without rooted is like a car with square shape wheels
I think I found the cause for "mail" app being executed automatically, today it went alive after select "flight mode"
Now I would like to control Google play services, I am seeing some of these being executed continuosly, can they be killed? how?
dapgo said:
I would like to have the maximum of control on running processes, but I feel I have not enough control, so I hope you can help me
I know that being root, managing processes and disable "autoruns" is a quite easy task but unfortunately my device is not an easy to root phone
Furthermore, I saw that Android (4.1.2 Jelly Bean) performance is very bad when you have many apps installed or you used many apps recently. Yes I listen about the internal management and I am aware that it is not a suggested practice but since I want to have control on what is happening and i have serious concerns about the algorithms to free RAM (maybe bull****), so I prefer to do it on my own risk
What I am doing is go to
-Settings, Application manager, Running, "Show cached processes"
- Settings, Application manager, Running, "Show services in use"
Identify what apps are in use and i don't like, then go to
-Settings, Application manager, All,
select app and Click "Force Stop"
Doing it my device has a better performance however, some apps still going alive after some time, for instance: Email ( I saw other in the past)
Using "Autoruns" app and checking "email" app I can see with changes of state can start "Email" however, sometime "email" is reenabled after be manually stopped but none of previous conditions happened.
How can I kill "email" or other app and force to stay off? (disable it and install other email app is not a valid answer)
I would like to use email/others as an standalone app, I mean use when I want and have out of memory when I am not using.
Besides, the autoruns, is there any scheduled task or something like that to open apps?
Of course I want to root my phone and I am waiting until someone will find a proper way to root, in fact I think that an android without rooted is like a car with square shape wheels
Click to expand...
Click to collapse
more info about processes, mem and autostart
I am still fighting with Android and how it manages processes, now I am sure that my main problem became each time I went into flight mode or it is restarted.
But it is not only Email being executed and being using in memory but other processes that I am not using doing that, such as:
(Mem. on OS monitor- Mem. in "service in memory"(android settings))
Event: Connectivity changed
-youtube 22.2MB-6.2MB
-Google play services(com.android.gms) 26.8MB-12MB
-Maps 20MB-4.9MB
-Factory Test (18.6MB -3.4MB)
Event: after Startup
-youtube 22.2MB-6.2MB
-Software update (18.0MB-4.3MB)
-Internet (com.android.browser) 18.9MB-3.3MB
There many apps which are executed after events like previous but they are closed after a very short time, but I am frustrated about those which are not unloaded.
Regarding "Email" app I decided to use a free email app and as Email cannot be disabled, so, I removed the accounts associated to email app, however even without accounts configured, it still being launched and wasting resources. can I avoid it?
What do you think?
dapgo said:
I think I found the cause for "mail" app being executed automatically, today it went alive after select "flight mode"
Now I would like to control Google play services, I am seeing some of these being executed continuosly, can they be killed? how?
Click to expand...
Click to collapse
It's not possible to do what you want without root, unfortunately (unless you're talking about normal apps, in which case you can uninstall them to keep them from running). An alternative would be to use Greenify, though it won't be fully automatic without root either.
What about editing the startups rights?
Has anyone used APK permission remover?
GermainZ said:
It's not possible to do what you want without root, unfortunately (unless you're talking about normal apps, in which case you can uninstall them to keep them from running). An alternative would be to use Greenify, though it won't be fully automatic without root either.
Click to expand...
Click to collapse
Apk permission remover never stops an app from automatically starting. It only helps in removing the permissions we see during installation.
dapgo said:
What about editing the startups rights?
Has anyone used APK permission remover?
Click to expand...
Click to collapse
You still want to do this 2 years and 7 months later? That's one late reply there
GermainZ said:
You still want to do this 2 years and 7 months later? That's one late reply there
Click to expand...
Click to collapse
Yes but after SO long I found the app 'autorun manager pro', and it allowed to disable triggers /autoStartups/autoruns
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)
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
devsk said:
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
Click to expand...
Click to collapse
Did you try the shallow hibernation or normal hibernation?
devsk said:
I am trying to understand why apps restart instead of resuming from where they hibernated. I thought the point of Greenify was to not kill the app but to hibernate it and resume it later from the same point.
A simple case of reproduction of this is: start playing a puzzle in andoku, hibernate it in greenify and move back to it. It goes back to the main screen and not show the screen of that specific puzzle that I was solving before gibernate.
Is greenify even working?
Click to expand...
Click to collapse
Yes, Greenify is working on many (tens of) thousands of devices. Likely YOUR device, rom or kernel is aggressively clearing memory due to limited resources. What are you using?
tnsmani said:
Did you try the shallow hibernation or normal hibernation?
Click to expand...
Click to collapse
I tried both but app restarts instead of resuming.
Yes, Greenify is working on many (tens of) thousands of devices.
Click to expand...
Click to collapse
What's your definition of working? It runs and does something or works as in if an app is hibernated and started, it resumes. If its the latter, its clearly not working...
devsk said:
I tried both but app restarts instead of resuming.
What's your definition of working? It runs and does something or works as in if an app is hibernated and started, it resumes. If its the latter, its clearly not working...
Click to expand...
Click to collapse
Not going to engage on this level. Greenify stands on its own merrits.
If not happy with the results nor willing to share device/rom/config info that might help with 'problem' determination then it probably ain't the right tool.
Davey126 said:
Not going to engage on this level. Greenify stands on its own merrits.
If not happy with the results nor willing to share device/rom/config info that might help with 'problem' determination then it probably ain't the right tool.
Click to expand...
Click to collapse
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
devsk said:
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
Click to expand...
Click to collapse
Just for interest, I'd downloaded and installed Andoku. Greenified Andoku. Played a few minutes and stopped within the game. Closed Andoku. Ensured Andoku was hibernated. Opened Andoku and was able to resume my game exactly at the point where I'd closed Andoku.
Just for completeness although most likely unimportant in this matter: Andoku had no internet access granted in AFWall+.
Personal conclusion: Greenify (currently on v4.6.3) works exactly and perfectly as advertised!
Personal remark: I concur with @Davey126. Unless you provide sufficient information about device, ROM, kernel and "configuration" (e.g. Magisk, Xposed, XprivacyLua, tools that restrict permissions, services, broadcast receiver etc.) most likely nobody is able to support you.
devsk said:
Are you able to resume any app from EXACTLY the same spot as you hibernated it from, after you manually hibernate it?
Aggressive OS/ROM does not matter. We are talking about a single app, hibernate manually, try to resume right away. The example of andoku I gave is a small app which does not require a whole lot of memory. So, I should be able to resume it right after hibernating it.
Click to expand...
Click to collapse
Android hibernation is not the same as Windows hibernation. Resumability is not assured - especially on a resource constrained or highly 'tuned' ROM. You should probably read up on how it works and the primary objective of Greenify which is to suspend unwanted background activity. In that respect it shares many characteristics with doze.
Oswald Boelcke said:
Just for interest, I'd downloaded and installed Andoku. Greenified Andoku. Played a few minutes and stopped within the game. Closed Andoku. Ensured Andoku was hibernated. Opened Andoku and was able to resume my game exactly at the point where I'd closed Andoku.
Click to expand...
Click to collapse
Did you use the pause/resume feature of the Andoku game or did you just click the game to start it again, and it resumed where you left off? Typically, if you resume using the game's feature, you have to click through 3 times to resume your game. If the app is resuming from where it left off, its 1 click just to start the game.
If you resumed the app as if you switched to it using app switcher, then something definitely is broken on my end.
Just for completeness although most likely unimportant in this matter: Andoku had no internet access granted in AFWall+.
Click to expand...
Click to collapse
I do the same.
Oswald Boelcke said:
Unless you provide sufficient information about device, ROM, kernel and "configuration" (e.g. Magisk, Xposed, XprivacyLua, tools that restrict permissions, services, broadcast receiver etc.) most likely nobody is able to support you.
Click to expand...
Click to collapse
I am stock Pixel 3 XL with Magisk 18.1 root. Nothing else. I have given all perms needed by greenify.
Android hibernation is not the same as Windows hibernation.
Click to expand...
Click to collapse
I think this is where likely the disconnect is. I started using greenify several years ago (I have been here on these forums for a while, I keep that dated forum reference in my signature for remembering how far android and this community has come). If I recall correctly, I used to be able to resume apps, just by clicking or switching to them. Now, I notice a different behaviour: the app restarts from scratch. That's all. Obviously, I preferred the app to not start but resume like I was just switching to it.
I don't know if this is relevant in this case, but doesn't Greenify in non-root mode just force stop apps? I believe this to be the case because I can see it happening; i.e., when hibernation is triggered, for each app hibernated the app info screen briefly appears and the warning dialog about force stopping an app flashes on screen momentarily.
olliebean said:
I don't know if this is relevant in this case, but doesn't Greenify in non-root mode just force stop apps? I believe this to be the case because I can see it happening; i.e., when hibernation is triggered, for each app hibernated the app info screen briefly appears and the warning dialog about force stopping an app flashes on screen momentarily.
Click to expand...
Click to collapse
Correct. The equivalent happens on rooted devices just in a more efficient and largely transparent manner. If the ROM later opts to recover some/all of the resources consumed by the 'hibernated' app standard Android memory mgmt rules apply. In most cases that means only critical pointers are retained which may or may not contain sufficient information to resume from the point the app was in when last in the foreground.
Davey126 said:
Correct. The equivalent happens on rooted devices just in a more efficient and largely transparent manner. If the ROM later opts to recover some/all of the resources consumed by the 'hibernated' app standard Android memory mgmt rules apply. In most cases that means only critical pointers are retained which may or may not contain sufficient information to resume from the point the app was in when last in the foreground.
Click to expand...
Click to collapse
But AIUI, force stopping an app is essentially killing the app process. So for the app to start afresh when next launched, rather than resuming from where it was left, would be expected behaviour.
Is Greenifying an app functionally better than disabling Background Activity from the app's Battery Usage page (a new setting in Oreo)? IWHT the latter achieves the same result but without killing the app.
I am running root mode. So, let's not talk about non-root mode.
If a hibernated app is going to restart from scratch instead of resume, I might as well just clear all apps (that I fed to Greenify) on screen off with 5 min delay using tasker/automate. Why bother with anything else?
The point of Greenify was to be able to resume the app after hibernate as if you just switched to it. This used to work, I have tested it in the past. Not anymore though.
olliebean said:
But AIUI, force stopping an app is essentially killing the app process. So for the app to start afresh when next launched, rather than resuming from where it was left, would be expected behaviour.
Is Greenifying an app functionally better than disabling Background Activity from the app's Battery Usage page (a new setting in Oreo)? IWHT the latter achieves the same result but without killing the app.
Click to expand...
Click to collapse
Well, no ... but this is not the place for that discussion. Not going to get into Android 101 or validating speculation around various actions.
---------- Post added at 05:18 PM ---------- Previous post was at 04:52 PM ----------
devsk said:
I am running root mode. So, let's not talk about non-root mode.
If a hibernated app is going to restart from scratch instead of resume, I might as well just clear all apps (that I fed to Greenify) on screen off with 5 min delay using tasker/automate. Why bother with anything else?
The point of Greenify was to be able to resume the app after hibernate as if you just switched to it. This used to work, I have tested it in the past. Not anymore though.
Click to expand...
Click to collapse
Sorry it is not working with your device/kernel/ROM/root solution. Could be an adverse interaction with the doze mechanisms in Android 9, aggressive memory management settings (eg: VM, LMK), resource mapping of the app(s) you are trying to hibernate, etc. I have not see a lot of feedback from Pie users as doze generally addresses rogue background activity and corresponding power drain. So the behavior may be different on that platform. I use Greenify on a variety of devices for other reasons for which it continues to work well. Just another tool in shop; appropriate selection is the key to success. Good luck.