• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Check if app is running

iomari

Newbie
Greetings,
I have an app that says the time every half hour. I also have an app that will make sure certain apps are never killed. What i need is an app that will check periodically to see if certain apps are running and to start them if they are not.

Is there such an app?
I'm using Kitkat 4.4.2

Thanks
 
Welcome to Android Forums.

That can be done with Tasker using the Application conditions in a profile.

See the Tasker sub-forum to this forum.

... Thom
 
If you are rooted, then you can use the xposed module named "applications settings" to assign these apps as "always running". That gives them a high priority so they won't get removed from memory unless/until absolutely necessary. May or may not address your issue.
 
If you are rooted, then you can use the xposed module named "applications settings" to assign these apps as "always running". That gives them a high priority so they won't get removed from memory unless/until absolutely necessary. May or may not address your issue.

Yes I'm rooted and I have xposed installed. i had forgot about it. I'll give it a try and see if it can help.
 
There are many apps that can stop an app from terminating. Can't any of them also ensure that it is always running when terminiated (I'll B bach :-))?
 
An app to restart other apps once terminated? Don't know if a dedicated app for that, but as mentioned tasker could get your close.

I still think it is cleaner to focus on keeping the task running by assigning it as "always resident" (not "always running" as I said before). If your "always resident" app gets killed, then you have bigger problems imo.....your phone can't keep high priority processes in memory and will be doing a lot of swapping and inevitable lag. I that case, look at memory management closr. Maybe periodically reboot or clear cache. See what apps are continually loaded as "running services" and uninstall some of them.
 
I use the setting "always resident"for three apps;

1-swipepad gesture launcher. I wnt to be able to activate it quickly any time. The dev provides an option to include a perpetual notification for this purpose, but I don't want to clutter up my notifications. Always resident accomplishes the same thing without the notification.

2/3 -navfree and my tracks. These apps sometimes get killed when in the background which disrupts my navigation or my jogging record. So I label then as always resident to fix this. I also have to manually kill the app in app manager when I'm done with it so it doesn't linger long after I'm done navigating/recording
 
Hey peeps. You're all clearly more advanced than me so can you explain why you would want to force an app to stay cached (or am I missing the point here?)
I always thought that Android learned the apps you use most and gives them priority.
So what reason would there be to force an app into priority? (please explain if I've taken this the wrong way. I've been awake since a concert on Friday lol) ;)
 
I explained my situation above.

Do you have apps like Swipepad that give you an option for a ongoing notification to keep themselves loaded/ always ready to quickly launch? If so, wouldn't you rather accomplish the same thing without cluttering your notifications?

Do you have particular apps that when killed (by the system) in the background result in loss of continuity of their function? For me, this happens sometimes with navfree navigation when I hit home and open another app (even though I am in the middle of getting turn by turn instructions on navfree). Other map apps don't seem susceptible, but I prefer this app and I can make it work...why not do it. I have similar problem occasionally when recording a jog on mytracks my s4 (never had it on my kyocera which I also jog with). The result is the track stops and I need to manually start a new one. Why should I not fix these (navfree and mytrscks) by giving these apps higher priority (always resident) so they run from the moment I launch then to the moment I kill them?

Btw, I have probably 400 apps on my phone. These are the only three that I see fit to assign "always resident". (The tasker notification visible after you pull down the shade might fall in same category...haven't looked closely at tasker settings to see if I can get rid of that and replace it with "always resident"). So I am not taking over android function....just helping steer it on the general right direction fit the few particular apps and situation that it falters. . The results seem good to me and I believe the logic is sound. Would be glad to discuss it you still have some objection.

In the meantime, it might be interesting to know what apps and situation the op is referring to.
 
Last edited:
I have an app that speaks the time to me every half hour. I kind of depend on it. Suddenly today I noticed that it wasn't working so I restarted it and it's fine now. I started this thread to see if there's a way to monitor certain apps to see if they are running and if not to restart/start them.

This is not about keeping an app running, it's about starting an app when it's not running. The various methods of keeping an app resident doesn't quite help if somehow you accidentally killed the app yourself and were unaware of it.

So again, I need something to start an app if it's not running. To check at a user chosen interval.

Any suggestions?

BTW, I have an app that prevents apps for programmatically dying so I'm covered theer.
 
Back
Top Bottom