Related
hi i have only just got the hero and was wondering how to close apps properly. i have noticed that when you hold the home key for a while a window pops up showing some apps ...is this how you close them? or is simply pressing the home key shutting them .
The long press on home just brings up a list of apps that have been recently run. It's almost a task switcher, but not quite!
Many apps will exit if you "back" out of them - i.e. when in the app keep pressing back until you get back to the home screen. However, this isn't the case for all applications. Some may have an explicit exit or close button, whereas others may have nothing at all.
However, Android is pretty good at managing its own applications, and will kill/exit them as necessary. In my experience, there's little to be gained from explicitly killing applications using a task killer, but some people swear by it.
Regards,
Dave
foxmeister said:
The long press on home just brings up a list of apps that have been recently run. It's almost a task switcher, but not quite!
Many apps will exit if you "back" out of them - i.e. when in the app keep pressing back until you get back to the home screen. However, this isn't the case for all applications. Some may have an explicit exit or close button, whereas others may have nothing at all.
However, Android is pretty good at managing its own applications, and will kill/exit them as necessary. In my experience, there's little to be gained from explicitly killing applications using a task killer, but some people swear by it.
Regards,
Dave
Click to expand...
Click to collapse
Most Task Killers free up memory thats used by background apps.
so basicly back out of the app and let android do the rest of the worring. thanks for advise
risterdid said:
Most Task Killers free up memory thats used by background apps.
Click to expand...
Click to collapse
Yes, but the point is that Android itself will start killing applications if it starts to run low on resources. (see http://developer.android.com/guide/topics/fundamentals.html)
Regards,
Dave
I'll attempt to sum it up once and for all, to try and set the record straight.
In Android's virtual machine, there is no functional differentiation between "closing" an app and "switching away from" an app. They are the same (the exception is things like music players which need to keep playing after you switch away from them, but even then only the 'service' part needs to keep running).
Whenever you switch away from an app, its current state is remembered so that even if it is effectively "killed" it can be returned to in just that state next time it's opened. Then Android either kills the process or it keeps it open, killing it when it needs the memory. You won't notice any difference between either scenario, except maybe that an app loads a little bit faster if it was kept in memory. At any rate, "closed" apps do not "run", and they do not take RAM or CPU cycles from other apps.
In terms of process/memory management, Android's VM has more in common with a web browser than a desktop OS - sure it can remember your state when you switch apps (like switching tabs, going back/forward/home in a browser) but whether behind the scenes it loads it all into and out of memory when you switch back and forth, or it all stays in memory is irrelevant to the user. Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Once you understand this you understand that all these 'task killer' apps are really unnecessary - all they'll do is make it slower to restart an app once closed. They don't reclaim RAM that was previously unavailable to other apps.
To cut a long story short, pressing "home" is a great way to close an app, whether you want to return to it later or not.
MercuryStar said:
Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Click to expand...
Click to collapse
that is not true for me, my firefox can eat a lot of resources as long as it is open. and i can see a performance difference when having a lot of apps open on my hero. not that it would be a problem, but you can see the menus scrolling more "fluid" after killing all bg apps, for example.
kendong2 said:
you can see the menus scrolling more "fluid" after killing all bg apps, for example.
Click to expand...
Click to collapse
I would wager that's the placebo effect. It feels faster because you believe it should. If you understand how the OS works you realise that apps you've switched away from do nothing to slow down or take memory from any other app (see my exception above about apps that launch background services such as music player).
kendong2 said:
that is not true for me, my firefox can eat a lot of resources as long as it is open. and i can see a performance difference when having a lot of apps open on my hero. not that it would be a problem, but you can see the menus scrolling more "fluid" after killing all bg apps, for example.
Click to expand...
Click to collapse
I do notice this too. There is a general 'sluggishness' with my Hero when there are lots of app sleeping/running/hibernating/whatever in the background. As soon as I kill off a few unwanted ones, all the menus scroll faster and home screens change quicker.
And this is not the placebo effect either. The menu's DO scroll more fluidly after I have killed a few apps, regardless of how you describe the RAM management...
Micksta said:
And this is not the placebo effect either. The menu's DO scroll more fluidly after I have killed a few apps, regardless of how you describe the RAM management...
Click to expand...
Click to collapse
exactly, you can tell easily if it is one motion or looks like it is "skipping frames". even it is only because it takes the device some cpu cycles to kill other apps, it does make a difference. like i said a rather cosmetic one, since it doesn't really effect the general usage. nevertheless i like to know what is running and what's not, and so far im running good with advanced task manager free.
WOW i didnt expect a massive response for my question but i thank you all for your responses
MercuryStar said:
I would wager that's the placebo effect. It feels faster because you believe it should. If you understand how the OS works you realise that apps you've switched away from do nothing to slow down or take memory from any other app (see my exception above about apps that launch background services such as music player).
Click to expand...
Click to collapse
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Daniehabazin said:
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Click to expand...
Click to collapse
Just as a matter of interest, do you use swapper or AppsToSD?
My phone never gets into the situation you've described, but even though I do have the full version of TasKiller, I almost never use it, and I don't see a need at present to use AppsToSD.
In addition, I'd imagine that having a swap partition would cause an issue with Androids own memory management, since I guess it can't distinguish between real and "virtual" memory. So where a "non-swap" device would start killing processes, a "swap" device would just continue on regardless because it thinks it still has physical memory available.
Regards,
Dave
Yesterday I downloaded "Advanced Task Killer Free"... anyone who has experiences with this? Is is better than just "Task Killer" or is it just an updated version of "Task Killer" ?
thanks!
have been using atk free for a while (lol 2 weeks since i got the hero) now, i really like it. its advantage over all other task managers IMHO: it has an ignore list, things you ignore are not shown in the running tasks list. in the list you have check boxes, where you can select the tasks that will be killed, and this list is remembered. for example "htc sense" is on my ignore list, but "music" is only checked, so i can uncheck it when i don't want to kill it while listening to music. next time i want to kill music i just have to tap the checkbox, no dealing with the ignore list here...
Daniehabazin said:
that's not true, my phone gets so sluggish sometimes that i can't answer a phone call, the phone doesn't register that i press the answer button. and when that happends i usually have like 20 mb of free ram.
Click to expand...
Click to collapse
I get this problem a lot, and in answer to fox meister, I don't have AppsToSD.
I don't know if the problem is RAM or CPU related, but the CPU often jumps to 100% when things are really slow.
Is the issue likely to be background apps, or widgets even?
Sausageman said:
I get this problem a lot, and in answer to fox meister, I don't have AppsToSD.
I don't know if the problem is RAM or CPU related, but the CPU often jumps to 100% when things are really slow.
Is the issue likely to be background apps, or widgets even?
Click to expand...
Click to collapse
Same for me with the processor.
When i reboot my phone i usually have 90 mb of free ram, after starting a few applications, like browser and phonebook, it plummets down to 20 mb.
I do have some extra applications that starts as services, like systray monitor and 3g watchdog.
when i open atk after a fresh reboot i see that some applications that i don't even use is started, like footprints, settings and calendar, even my webrowser is started, whats up with that, can it be disabled?
I think the issue is that we have some applications that autostart withous us using them, and also programs that we download that autostarts as services and maybe having memory leaks...
I came to chime in with my experiences of the CDMA hero and sluggishness.
I watch memory like a hawk (thanks Mogul) and I too have around 80-90mb free ram on start, but it can get down to around 30 rather quickly. Once it gets down here, I notice that screen transitions and random lag occurs in apps. If I go into Advanced Task Killer and kill many of the stragglers, my menus are as smooth as can be.
It is most certainly NOT a placebo effect.
One thing I really like about Advanced Task Killer (pay version) is that it has the "Auto End" feature, where it will kill all apps not chosen to be excluded at the interval that you choose. For example, I have determined the system applications that need to be on all the time, and I've excluded those. Every hour, ATK kills everything else. For the most part, my Hero hovers around 70MB now at all times, although it can get down there to around 30-40MB if I'm right around the 1 hour mark.
That feature alone makes it much better than Taskiller IMO. Totally worth 99 cents
This definition would imply that android works exactly like the iphone osx? I mean saving "screenshots" of the last state of an app. But NOT having real multitasking?
Because it's not possible to have multitasking and at the same time "inactive" background apps everytime you hit the home button...
MercuryStar said:
I'll attempt to sum it up once and for all, to try and set the record straight.
In Android's virtual machine, there is no functional differentiation between "closing" an app and "switching away from" an app. They are the same (the exception is things like music players which need to keep playing after you switch away from them, but even then only the 'service' part needs to keep running).
Whenever you switch away from an app, its current state is remembered so that even if it is effectively "killed" it can be returned to in just that state next time it's opened. Then Android either kills the process or it keeps it open, killing it when it needs the memory. You won't notice any difference between either scenario, except maybe that an app loads a little bit faster if it was kept in memory. At any rate, "closed" apps do not "run", and they do not take RAM or CPU cycles from other apps.
In terms of process/memory management, Android's VM has more in common with a web browser than a desktop OS - sure it can remember your state when you switch apps (like switching tabs, going back/forward/home in a browser) but whether behind the scenes it loads it all into and out of memory when you switch back and forth, or it all stays in memory is irrelevant to the user. Nobody worries that a long forum page on another tab or in their back button history is occupying 80 megs in the background or not, the browser takes care of loading/unloading it from RAM as needed, and that's just like how Android's VM works when switching between various pages of various apps.
Once you understand this you understand that all these 'task killer' apps are really unnecessary - all they'll do is make it slower to restart an app once closed. They don't reclaim RAM that was previously unavailable to other apps.
To cut a long story short, pressing "home" is a great way to close an app, whether you want to return to it later or not.
Click to expand...
Click to collapse
Shahpur.Azizpour said:
This definition would imply that android works exactly like the iphone osx? I mean saving "screenshots" of the last state of an app. But NOT having real multitasking?
Because it's not possible to have multitasking and at the same time "inactive" background apps everytime you hit the home button...
Click to expand...
Click to collapse
No, you've not understood the explanation.
The iPhone will always* terminate an application that isn't on its list of "approved" multi-tasking apps once it isn't active any more (i.e. you've switched tasks).
Android will try to keep whatever it can in memory, but eventually will start killing processes in order to keep the system running.
So, if you're on an iPhone listening to something on Spotify and you want to browse something on the web, the iPhone will "kill" Spotify when you switch to the web browser. On Android this won't occur except in the most critical of resource low situations, but then again, I'd imagine other apps would get killed before Spotify.
Read this article, specifically the section from "Component Lifecycles" onwards specifically "Activity Lifecycle", "Saving activity state" and "Processes and lifecycles".
Regards,
Dave
* Unless it has been jailbroken!
Hi
I'm currently having problem with apps they are auto opening themselves.
Sometimes at startup when I open my open and use Helix/ADW all launcher manu apps are open automatically. It eats like 50MB of memory and battery.
And even while my screen turns off it opens app. I was sleeping and my screen is turn off/sleep and I check task panel it got apps open even the screen is lock.
Got No Idea on this. Why my apps are auto opening.
And do I need to debrand?
I just got a unit Unlocked
X10i
Baseband 1.0.14
Build Number R1FA014
Kernel 2.6.29-rel [email protected]#2
Do I really need to debrand?
Does it reset my phone and my settings/apps will be deleted?
TIA
It's not the X10, it's an Android thing.
Then how to get rid of this auto opening app? I never exp. this on 1.5 and 2.1 on my HTC Hero just on this 1.6
Get Automatic Task Killer or something similar, and set it to kill apps on open...if you find the apps opening affects your performance.
Also, if they're apps that sync with a service, make sure all syncing is off, or they'll keep coming up anyway, to try to sync with the cloud.
as a personal anecdote, once I stopped using task killers, the phone started running more stable and quicker.
So Task killers are not good?
I check my Task Panel once i boot my phone tons of APPS are open
Like Bluetooth file transfer
SMS Backup and Restore
Email
Alarm Clock
Calender
Settings Voice Dialer
It opens on startup.
seriously I just boot up my phone and use ADW Launcher and those open up automatically? what does those do? for startup? there are tons more like 25 apps on startup. This thing is not good since I'll do task killing always even the phone is screen off. My phone is opening Voice Dialer Handsent SMS even though i dont have message or calls received.
It's like every min or hour I'll do task killing it kills battery
Well, Alarm Clock has to be on, so it knows when to go off... If you don't have any alarms set, delete all the alarms that are in it.
Email is on by default, since it's a smart phone. If you don't have an account set up, email won't sync, and thus, isn't really doing anything. Calendar will attempt to sync with google if you set it up, but if not, again, shouldn't be doing anything. SMS will start to monitor for incoming SMSes. A lot of services start so they're there when you try to start them up. Basically, anything that has to sync to the internet to update will start automatically.
If things like Photoshop Mobile or a game or something start up, those should be killed.
Stand alone apps that don't access the internet should have no business starting up on their own.
Some people on here claim task killers are great and help a lot... some claim they do nothing. I'm torn, because the phone feels a bit faster than when I used the task killer everytime I unlocked the phone. If your phone is new, cycle the battery a few times, and let it 'break in' and, eventually, the battery life should improve.
Thanks. I'm just a little bit worried that I'm not aware that there are many task opening with me noticing or knowing it and use much battery as I do.
Some apps open automatically
I know that apps auto close ok , here's its invers..
Any how use some task killers frequently to kill them....
Or just unistall them
.....:thumbup:
................................................................................................
Can somebody help me? I am running my xperia x8 and as i know since i rooted and got myself new rom i was wondering why my games work slow but after a little research i found out that official Facebook app is working in background so i unninstaled but now my question is is there someone who has some facebook app non-official which i can run without the problems?
PS: Sorry if spam on this thread but i cant make new threads on this app (or i can but i cannot figure it out)
Sent from my X8 using xda app-developers app
gr3yh0und said:
Thanks. I'm just a little bit worried that I'm not aware that there are many task opening with me noticing or knowing it and use much battery as I do.
Some apps open automatically
Click to expand...
Click to collapse
Android works by loading EVERYTHING it can into memory, up to a threshold and then removes apps from memory if they're not being used and memory is required for newly initiated applications.
Some apps have a terminate and stay resident approach and are seen as 'services' and they just stay active no matter what. Email, Calendars and status bar and etc never leave memory cause they're all waiting for there big moment, an email, an appointment, a finger touch etc.
Using a task killer doesn't really do anything, cause as soon as you 'kill' the process and the moment there is available memory again the process will just return to active/inactive memory because that's the way Android memory processing works.
If you have root access you can delete/freeze system apps you don't require.
A 'slim' Android v2.3 ROM shouldn't have more than approx 110 system apps. Less that 95 if you're good.
gr3yh0und said:
I check my Task Panel once i boot my phone tons of APPS are open
Like Bluetooth file transfer
SMS Backup and Restore
Email
Alarm Clock
Calender
Settings Voice Dialer​
Click to expand...
Click to collapse
Most of the apps you listed are system apps and will, by their nature find there way into memory all the time. That's just how it is.
After a few hours of use many of the non-used apps will drop out of memory and others will take their place.
Loading applications into memory has a time and processing cost and so if it's already in memory, it's quicker to access.
However the Android system doesn't know your usage traits at start-up and that's why some less used system applications may be seem in memory until they're weeded out by those you do use. Again, nothing to worry about,
Using an XPERIA X10i with ~384MB of memory leaves little room for bloatware and thus a lean running machine is the order of the day for the XPERIA X10i.
Hi there
sorry for asking I am somewhat new to Android.
I read very often that Google Maps should be froozen because it is a battery sucker. Now I am wondering how an application could drain the battery when I actually do not run the application.
How does Android itself deal with applications and quitting them?
I read conflicting recommendations about task managers stating that Android itself deals with this better.
So what is this freezing of apps? Does it prevent Android from starting it automatically?
Thanks for any education
Claas
Android is based on multi tasking ..ie many apps can run in the background even though you are not using it at the moment..say if you are using maps and once you're done you just exit it. However maps app will be running in background if not exited in proper manner( either using the app or by going to running services in settings and force closing).
Also certain apps are configured to autorun under certain circumstances ..say for maps or Facebook app! -try keeping your wifi /data off! Go to settings/apps/running services/menu-cached process and force close Facebook,maps however once you turn on data /wifi they will run automatically! Just check it out yourself ..
Solutions for such problems could be either to use autorun managers or to freeze the app -freezing makes the app unavailable for use until you de-freeze!ie it blocks the app from running ..
Above said statements /examples are from my experiences!correct me if I'm wrong!
Sent from my LG-P500 using Tapatalk
Yes but be careful, if you use task killers to kill them, they may start again and this will consume more battery than the program running.
Imho the best way to go about this is the following:
- go get Quick System Info PRO from Market (it's free)
- set it up so that it places a CPU usage icon on your status bar (the notification for that icon is also animated)
- when you find the device is sluggish and CPU usage is high, tap the notification and go to the Processes tab
- sort by CPU usage
- kill whatever it is that is using the CPU
And you may also kill all tasks just once before going to bed or something, just in case.
To stop maps, use autostarts disable all maps have in there, then you can be cool
Sent from my LG-P500 using xda premium
I have kinda nooby question... i am using a phone with stock gingerbread and i am using an advanced task killer. I know a lot of people say that I shouldn't do it, but it just makes my phone a lot faster and smoother. As a noob, i have one question: is task killer really harmful to my phone and is it better for me to not use it? If you say yes, please provide me some specific reason why. Thank you ask much guys!
Sent from my Nexus S using XDA App
its not that bad... but u should not kill background services!
keep settings on safe... don't use aggressive mode
applications u know u use often for example- browser or music player... u can add to excluded section... currently im using ZDBox and it works perfect... it also has additional features that you will need... hope this helps
I only use the ATK to kill an app that's not responding well.
For example, when I was using CM7, sometimes my Google Reader app would hang and display a loading symbol for a long time instead of displaying my articles, and the arrow that shows transmission over the network wasn't displaying so I knew it wasn't waiting on data, I would use ATK to kill ONLY Google Reader. Then I could go back into the app and it would load very quickly.
But since I switched to an ICS ROM, I haven't had that same issue and haven't had a need for ATK.
Also, do note that it does take processing power, and therefore battery power, when your phone decides to restart any of those apps you are killing, and it will restart apps.
For a great explanatory article, see here:
http://androidandme.com/2011/11/app...lers-still-dont-give-you-better-battery-life/
and also the links in the phrase "(see here, and here, and here)".
So in short, they are not exactly "harmful" but they don't provide any real benefit if you "kill everything, every time."
It is a common myth that more RAM = better performance, and this is a result of the market being dominated by Microsoft for so long. Android does not equal a desktop OS. Free RAM literally does nothing. In fact, it is wasteful to have bunch of free RAM. Android manages RAM very effectively and aggressively works to ensure that you have sufficient resources to do whatever it is you want to do. If you notice an increase in performance with a task killer, it is because you have a misbehaving app. Watchdog is the only task manager I would recommend, all it does is watch for apps that are using an abnormal amount of resources and alerts you. Part of the Android experience is the emulated multi-tasking, or having several apps saved to memory simultaneously to facilitate ease of switching between them. An app in the background will not affect the performance of your device, it is not using any resources. Aside from that, if you end a task, it will usually just start right up again, using more resources, because that is how Android is designed to work.
So, I would say finding the misbehaving app is a much better option than a task killer. They were important in eclair, maybe even FroYo. But anything above that they are unnecessary.
i dont really believe in android"s app managmentbut task killers make it only worst IMHO
I have to agree with member devator22.
Android is not Windows. Android is basically Linux and Linux is using a different memory management than Windows does. (Although Windows has got a lot of improvements during the last years)
RAM which isn't used, is wasted! That's a fact.
So, if you run a specific application, some of its data my be cached. Linux is reporting this as "buffered" (you can see the amount by running the 'top' command)
There might be a more or less big chance to hit this cache. If so, the data is loaded much faster ( definetly > 10 ) than if it had to be requested from the file system.
By killing your application by a task manger you are releasing this buffered resources (actually you are forcing the OS to release it). In the worst case you are wasting your advantage of loading already cached data from the RAM. In the best case you are gaining nothing because your device has to load it from the file system anyway.
(sorry for my english )
Get watchdog!
/end
*just because nobody understands you, doesn't make you an artist..
Thank you so much for these replies! I really appreciate it! I decided to keep my task killer but not use it aggressively. I probably will use it to end apps that i really find it pointless. And also to the people who said android dies it's own task managing, you're right but wrong at the same time. When i didn't use my task killer, android did killed some apps in in order to launch more apps, but it left only like 10mb of 300mb, which i found little odd and also it mainly killed launchers which was very annoying.
Sent from my Nexus S using XDA App
Task killer will speed up your phone if you know what you're doing. Only kill tasks that you are familiar with...e.g. apps that you know you have launched and won't be using anymore. Those apps running in the background can slow down your device.
If I'm on ICS, its better to use the bult-in task killer, or download one from the market?
Guys, he's not saying he does it for the memory. He says the phone's smoother. I don't know whether this is true, but if there are background tasks performing operations that he doesn't want them to do, it's *absolutely appropriate* to kill them.
The flip side of that is that the applications will eventually be automatically started again, and that startup takes extra CPU time. As long as the process startup and process killing happens when the screen is off, I would think this could improve the responsiveness.
But I think on most people's phones, the background processes really don't use a lot of CPU...
I know by default even Gbs memory management isn't the best. The app priorities are a bit weird aand the launcher gets killed to easily. Running the v6 supercharger scripts and making the launcher hard to kill and fixing the priorities and changing the oom settings makes any from wicked fast
Sent from my PG86100 using xda premium
I am not rooted, so I can't do anything that involves rooting.
Sent from my Nexus S using XDA App
Instead of killing an app over and over again install something like Gemini App Manager and disable the app's autostart permissions. For example, dropbox and dropbox sync are set to automatically start at boot or when there's a connectivity change. I understand why they're set to do that but for my purposes I only needed them to start when I actually used them.
Having said that, I no longer use Gemini and have never used an automatic task killer. I think android (ICS) does a good enough job managing it's memory that I don't need to be anal about micromanaging it myself. I think it also helps that I'm not an appaholic. I'm very picky about what I install and will only keep an app installed if I regularly use it.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
Jinx Lumos Joke said:
If I'm on ICS, its better to use the bult-in task killer, or download one from the market?
Click to expand...
Click to collapse
Built-In is much better
im on ics on my captivate and it runs beyond smooth
like stated before having free RAM with not do anything
android has a good way of muti tasking
Seems like many applications spring back up after "killing" them though the Android task manager or any of the task managers available in market. Is annoying the hell out of me. If im not using the app I dont want it to.run in the background..
I understand that messaging applications need to run in background but not all.
How do you guys make sure
that any application which you close "remains" closed until the next time you open it?
Thank me if I helped you..
~n0tr1x on t989~
You might try Gemini app manager to disable auto start apps
Sent from MARVEL using Tapatalk 2 Beta-4
Easy Task Killer can help too..
use Easy Battery Saver too along with it!
Thanks.for your replies guys. However.i believe the main question here is,.how.to.stop these background app processes from running until the next time I start them manually.
Problem with task managers is that they stop these apps after a certain interval. Once they do, the.apps restart after 2-5 seconds. And.remain there till the next interval of the task killer is reached. This in turn take up more memory a compared to keep the running.. In addition, these apps run in the background on their own taking up a junk of memory/processor space..
Thanks again for your replies. Please correct me.if my understanding is wrong and you are feel otherwise.
Thank me if I helped you..
~n0tr1x on t989~
Those "apps" that you say keep opening are actually the processes running in the background. I know of many apps that keep re-enabling their processes after killing them. (IE: Facebook, some Google stuff, and a couple games that run in real-time)
Best solution: try to go into the app's settings and see if there is an option to disable anything that would require a background service to run, IE: sync, updates... If not, then just stop killing that app. Ignore it in the list or set a task killer to ignore it. If the app keeps re-opening, you killing it all the time is only doing bad because it puts more stress on the operating system because it has to take the time to reinitialize the app/service. If you are really that anal about background running apps, set android to limit a lower amount of background apps to run.
Like asdot suggested above use Gemini App Manager to disable the apps autostart permissions. If an app is set to automatically start after a certain intent is broadcast by the system (ie, at boot, or at a change in connectivity, etc.) you can use Gemini to stop that app from automatically starting. You can stop an app from automatically running in the first place instead if trying to kill it after it has started.