by BigInJapan » Wed Jul 10, 2013 12:28 pm
rovingcowboy, that stop button in the notification tray is an Android 4+ feature. It's not present when you run MMA on Android 2.x. Us poor suckers that are still on Gingerbread don't really have a Quit option of any sort.
BamaJon, if you've been using Tasker for a while, this likely isn't the first time you've found an app that doesn't respond well to the Kill command. I know I've personally run into that a good bit. I just did a quick test and found that if I left "Use Root" unselected, Kill did nothing. If Use Root is selected, Kill took MMA out of focus but did not stop all of the processes (note that my phone is rooted).
My suggestion to you is to take the Kill out of your Exit Task and just use a Go Home instead. MMA should continue to run for approx 60 seconds after the Go Home is issued, and then it should shut itself down cleanly. At least, that's what I'm seeing in MMA 148.
rovingcowboy, that stop button in the notification tray is an Android 4+ feature. It's not present when you run MMA on Android 2.x. Us poor suckers that are still on Gingerbread don't really have a Quit option of any sort.
BamaJon, if you've been using Tasker for a while, this likely isn't the first time you've found an app that doesn't respond well to the Kill command. I know I've personally run into that a good bit. I just did a quick test and found that if I left "Use Root" unselected, Kill did nothing. If Use Root is selected, Kill took MMA out of focus but did not stop all of the processes (note that my phone is rooted).
My suggestion to you is to take the Kill out of your Exit Task and just use a Go Home instead. MMA should continue to run for approx 60 seconds after the Go Home is issued, and then it should shut itself down cleanly. At least, that's what I'm seeing in MMA 148.