Is there a way to keep an app always loaded into memory ready to be recalled by opening it's app shortcut? The reason I ask is I have an app that when it closes I lose my place and data but I still need to continue multitasking in other apps. I would appreciate the help
Related
Bump
Anybody?
===============
First off - I'm totally lost with Tasker. I understand it's potential, but I just can't make heads or tails of it. I'm the dumbest geek on XDA ;-D
So, a little help please: I run Visidon AppLock - but find that it stops running every once in a while. It doesn't appear to force close -- just stops or exits for some reason. I never get a FC notification, I just notice that the icon isn't there, and the service has stopped running.
Tasker SHOULD be able to relaunch an app whenever that same app closes, right? So how do I do that? Simple step-by-step for the idiot poster would be appreciated.
This is my first post. I have been contemplating freezing some apps through titanium backup. Ive notice that apps like pulse news and bloomberg run in the background when i never opened them in the first place. I would think that that's unnecessary strain on my battery and I want to freeze them. But if i freeze an app does that mean that I will need to unfreeze it in order to ever use it? If so how can i prevent an app from running in the background without completely disabling its use? My second question pertains to app permissions. A lot of the apps I download have permissions that seem a little too intrusive on my privacy. Is there a way I can store files so that no application has access to it? Again this is my first post. I did some research to see if these questions had been answered and I didnt see much. So thank you and pardon my ignorance.
The only way to effectively stop an app from running is to freeze it. And a frozen app cannot be run.
And yes the app constantly running does affect the battery. That's the main frustration with bloat. It'd be one thing if they just sat there, but they regularly run on their own. Most alternatives on the market to them don't run by themselves nearly as much.
By far the majority of permissions are not as bad as they sound. Contact the developer to see why the permissions are required. The reasons may surprise you.
What apps are you concerned about?
Sent from my SAMSUNG-SGH-I777 using XDA App
Been trying to figure this out for a while now. I have been able to fix this with a number of apps, but there are some apps that are just frustrating to deal with.
I'm wondering what exactly can keep an app running in the background, regardless of what efforts your take to disable it?
If I don't use an app much and don't want it running, I normally freeze the app. If it is an app I tend to use a bit more frequently, I take other measures such as an app manager that allows me to be extremely precise as to how and when it should run such as on startup, battery level, configuration change, application change, etc. This is a pain in the A** though and I really don't have the time to do this for every application.
With that said, I'm wondering what other methods, other than freezing and the other mentioned above, I can take to prevent an app from running in the background?
I will give you a perfect example...
There are some third-party apps I have downloaded that I know I will use occasionally. One example is CamScanner. For the life of me, I can't get this app to stop running in the background without extensive efforts mentioned above. No matter what I do, it just pops up again in running applications.
How can I ensure the app will not run in background while not resorting to freezing the app, which will prevent me from quickly accessing it when needed?
Some clarification on this would be greatly appreciated...
Thank you,
--mike
pookieguy said:
Been trying to figure this out for a while now. I have been able to fix this with a number of apps, but there are some apps that are just frustrating to deal with.
I'm wondering what exactly can keep an app running in the background, regardless of what efforts your take to disable it?
If I don't use an app much and don't want it running, I normally freeze the app. If it is an app I tend to use a bit more frequently, I take other measures such as an app manager that allows me to be extremely precise as to how and when it should run such as on startup, battery level, configuration change, application change, etc. This is a pain in the A** though and I really don't have the time to do this for every application.
With that said, I'm wondering what other methods, other than freezing and the other mentioned above, I can take to prevent an app from running in the background?
I will give you a perfect example...
There are some third-party apps I have downloaded that I know I will use occasionally. One example is CamScanner. For the life of me, I can't get this app to stop running in the background without extensive efforts mentioned above. No matter what I do, it just pops up again in running applications.
How can I ensure the app will not run in background while not resorting to freezing the app, which will prevent me from quickly accessing it when needed?
Some clarification on this would be greatly appreciated...
Thank you,
--mike
Click to expand...
Click to collapse
freezing is your only bet. definitely a pain but the built in tasking doesn't apply to all apps,especially facebook. can try alternative apps but if none exist then you still need to freeze. I unfreeze a certain batch of apps when I wake up and freeze them before bed. during the day i go along with what i'm running. i'm tryin to link special batches to say toggles or tasking with tasker to make mornings and bed work faster
sent from tapatalk on my htc rezound
Use something like Gemini App Manager. Those programs likely use triggers to auto-run. Gemini shows you the triggers applications use so you can stop them if you don't want them running whenever they want.
I use AppQuarantine for those issues. you can put widgets on the desk that let you unfreeze and start apps with one click.
sent from the desert with xda app
Thanks guys,
I will try some of these options out.
Was really trying to do this without freezing apps though. I can do it through ROM Toolbox but it is quite tedious, as this awesome app has so many options on how to handle the application. Trying to find shortcuts...
Thanks,
pookieguy said:
Thanks guys,
I will try some of these options out.
Was really trying to do this without freezing apps though. I can do it through ROM Toolbox but it is quite tedious, as this awesome app has so many options on how to handle the application. Trying to find shortcuts...
Thanks,
Click to expand...
Click to collapse
Have you tried Autostarts? There's many scenarios an app takes into account before it'll run. You can disable the app from running in each category so the only time its running is when you open it. Unless of course you don't kill it when you leave the app. Its hard to explain but when you look at the app you'll know what I mean
Sent from my SGH-I997 using Tapatalk
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Hi all,
I'm currently developing a simple alarm app. Obviously, it is essential that the user can not simply disable the app with task manager e.g. A user could accidentally close the app and therefore not get the reminder. The sound of the reminder must not go away before the user presses a few buttons in the app.
How can I do this? A non-overridable and non-closable app.
thanks so much
Because of the nature of how Android and Linux runs I don't believe this is possible as you can always force close an application. Your best option in to just have a popup or warning when the user first loads the app telling them to make sure to disable or put an exception on your app.
The stock alarm/timer app is not affected by task killers so its possible to overcome it, possibly by using an autorun condition to relaunch after its killed?
Sent from my DROID3 using Tapatalk
There are at least two apps (that I've noticed) which seem to act strange when I run them again after running them once. The strangeness vanishes if I go into recent apps, swipe the app away, then run it from scratch. I get annoyed at having to do this frequently. Would one of the many background app killers out there achieve the same effect automatically without me having to swipe the app away? Any recommendation for a killer I can restrict to just certain apps? Is there any setting on the s21 to say "never cache this app in memory"?
Claghorn said:
There are at least two apps (that I've noticed) which seem to act strange when I run them again after running them once. The strangeness vanishes if I go into recent apps, swipe the app away, then run it from scratch. I get annoyed at having to do this frequently. Would one of the many background app killers out there achieve the same effect automatically without me having to swipe the app away? Any recommendation for a killer I can restrict to just certain apps? Is there any setting on the s21 to say "never cache this app in memory"?
Click to expand...
Click to collapse
No offense but it sounds like the issue is with the apps and using an app killer to autokill the app is nothing more than band aid. The app killer would be yet another service that will run in the background using up your resources. I think you would be better off contacting the developer and see if they will allow you to submit logcats so they can fix the issue(s). This would help you and potentially help others as well. I would also see if there any alternative apps that can do the same thing.
aybarrap1 said:
No offense but it sounds like the issue is with the apps and using an app killer to autokill the app is nothing more than band aid. The app killer would be yet another service that will run in the background using up your resources. I think you would be better off contacting the developer and see if they will allow you to submit logcats so they can fix the issue(s). This would help you and potentially help others as well. I would also see if there any alternative apps that can do the same thing.
Click to expand...
Click to collapse
The most irritating one is the Chase mobile app. Attempting to contact the "developer" gets me chase customer service who wants to help me reinstall the app. Pleas to forward my mail to the actual developer are met with total incomprehension .
Okay. We might try going deeper here. Did the problem always exist or did it start randomly? If each one was working fine at one point it could be an update from the developer broke Apps. Did it start after an update to the app or the phone Rom?
Did you customize and/or disable the os or rom baked services/apps?
How long have you had the phone? Did you upgrade from android 11 to 12 and do a factory reset? Just some questions to see if there might be other root causes.
Everything is stock with all system updates from samsung applied. I'm pretty sure it started after an app update. The chase app insists "You are not connected to a network", but since I was just on chrome looking at web pages, that seems unlikely. It acts more like the app doesn't clean up everything correctly on exit, then if android keeps it around in memory, it has trash in uninitialized variables when starting back up again. I've gotten pretty good about swiping it away from recent apps, so even if they fix the bug someday, I'll probably keep doing it from reflex .
Have you looked at recent comments for the app on the play store? Are there similar complaints that started around a certain time? That would be a definitive indicator if it was an update issue.
I commented about it and since then 15 people have found my review helpful, so maybe that means they have the same problem.
Claghorn said:
I commented about it and since then 15 people have found my review helpful, so maybe that means they have the same problem.
Click to expand...
Click to collapse
Yeah...that is unfortunate. It looks like you may have to wait on the company and developer to fix it.