exit an app after set amount of time

[benzylic]

Sometimes I'll open up Pandora, or Spotify to listen to as I try to go to sleep. I dont really like leaving it open all night though so is there an app or a way to close Pandora or spotify after like an hour or so? Im on android btw.

 

[Anubis]

you could use tasker to shut them or data off at a certian time. im sure other aps could do it as well but i know tasker can

 

[cl-scott]

Timeriffic is a free app that can handle that sort of thing as well. At least as far as shutting off the data connections.

Llama is a cool profile app that can also do things based on the time of day, and one of the options is to kill an application.

 

[AFurryReptile]

Some custom ROMS have a "quiet hours" option that disables all notifications and sound after a certain time at night. Might be something to look at if you're into that sort of customization.

 

[benzylic]

Llama has the settings I want but seems to only work intermittently. It will close Pandora but leaves the now playing in the notification window which I can deal with, just kind of annoying. It only closes spotify once though then wont do it again. I set it up to when active application is spotify or pandora, kill with root after a 2 minute delay.

When reading about tasker I found the linked post, and im wondering if that might be coming into play with llama. I'm stuck on gingerbread for another month or so, before I can upgrade.

I'll keep messing around though, and if it doesnt work out I'm only streaming off of wifi so no biggie.
http://androidforums.com/android-ap...r-profiles-everyone-using-18.html#post3668063

Might go ahead and buy Tasker though, seems awesomely robust

 

[cl-scott]

Llama takes some time and patience to really get your head around, but the developer is actually pretty responsive. One weekend I was a moron and set one of my sound profiles to change the ringer and notification volumes, but it wouldn't save. Turns out I set the ringer to silent, so naturally it's not going to work, but the developer was willing to respond to emails.

But in your case, if you look in the advanced settings, there's an option to allow an event to keep firing/triggering for however long a condition is true.

 

[benzylic]

Llama takes some time and patience to really get your head around, but the developer is actually pretty responsive. One weekend I was a moron and set one of my sound profiles to change the ringer and notification volumes, but it wouldn't save. Turns out I set the ringer to silent, so naturally it's not going to work, but the developer was willing to respond to emails.

But in your case, if you look in the advanced settings, there's an option to allow an event to keep firing/triggering for however long a condition is true.

Yeah I saw the repeat option, I wasnt quite sure how it worked though. Seemed to me if it keeps checking conditions it would kill your battery, but maybe it doesnt work like that. I'll mess with it some more tonight.

 

[Headcase_Fargone]

you could use tasker to shut them or data off at a certian time. im sure other aps could do it as well but i know tasker can

Have you ever tried to use Tasker to kill an app? It doesn't work very well at all because of the way Android handles its processes.

For a while I was attempting to make a script that would kill TuneIn Radio when Bluetooth disconnects from my car stereo.

The standard Kill command didn't work. The "use root" option didn't kill it either. Even writing a script using pkill on TuneIn's process(es) didn't work. The app would always pop back up after a few seconds or minutes.

 

[benzylic]

Have you ever tried to use Tasker to kill an app? It doesn't work very well at all because of the way Android handles its processes.

For a while I was attempting to make a script that would kill TuneIn Radio when Bluetooth disconnects from my car stereo.

The standard Kill command didn't work. The "use root" option didn't kill it either. Even writing a script using pkill on TuneIn's process(es) didn't work. The app would always pop back up after a few seconds or minutes.

I've been reading about that, it seem before Froyo doing this would have worked fine but after froyo google changed the way app killing was handled, namely limiting the ability for apps to kill other apps.