Killing Apps, how is it other apps can do this but not Tasker?

[Mark S]

Apparently since 2.2, Tasker is unable to kill apps because the
ability to do so has been watered down by Google. Well if that's the
case, how is it that task killers still work fine?

If it really can't be done in Tasker, maybe we could have it so Tasker
can link up with a task killing app and kill them through that. For
example, I have a widget that when you tap it, it kills all apps, why
not have Tasker do that exact action for certain contexts?

[Pent]

> Apparently since 2.2, Tasker is unable to kill apps because the
> ability to do so has been watered down by Google. Well if that's the
> case, how is it that task killers still work fine?

You got me. Will have to look if that's the case.

Pent

[BossMan]

> Well if that's the
> case, how is it that task killers still work fine?

Do they? I don't have froyo but I read that auto-kill function does
not work in task killers anymore, only killing by hand works.

BR,
A.

[Stefan Sarzio]

With eRay I can't properly kill apps any more. With one are you using,
@Mark S?

[Mark S]

I'm on Froyo and I'm using Advanced Task Killer, it kills all apps
everytime without fail.

[Mark S]

>> only killing by hand works.

I'm just using my phone doing whatever I want and then a flash box
will pop-up and say something like "6 apps killed" and it seems to be
telling the truth, so I don't think it only has to be done by hand.
Maybe there is an issue with killing apps with the phone on sleep? I
can't confirm whether my task killer does that successfully but I can
try and do some tests if you want.

[BossMan]

Pent,

I did a brief search and I am wondering: isn't that only related to
adding a new permission for Tasker, namely:
android.permission.KILL_BACKGROUND_PROCESSES ?

http://developer.android.com/sdk/android-2.2.html#api

BR,
A.

[Pent]

> I did a brief search and I am wondering: isn't that only related to
> adding a new permission for Tasker, namely:
> android.permission.KILL_BACKGROUND_PROCESSES ?

It's held. And there would be a security exception if it was
unrecognized.

Pent

[Pent]

Rooted phone Mark ?

Pent

[Mark Sanger]

Yes, it's rooted.

[Pent]

Then we probably have the answer. It's probably just killing the
process directly instead of going through the Android API.

Pent

On Aug 5, 3:45 pm, Mark Sanger <msan...@gmail.com> wrote:
> Yes, it's rooted.

[Springfield Operations]

Is this a dead issue. Are we going to have a resolution to this?

[Pent]

> Is this a dead issue.  Are we going to have a resolution to this?

It's resolved. I've put it on the todo list next to 'root functions'.

It's not possible since Froyo without root.

Pent

[Springfield Operations]

I am rooted, Should it work being rooted

[Pent]

> I am rooted,  Should it work being rooted

No, because Tasker doesn't request root permissions yet.

Pent

[Emory]

I'm _NOT_ rooted and "Advanced Task Manager Free" DOES kill apps and
background processes successfully in FroYo on Droid 1. I don't know
if this interests you or even helps, but I thought I'd throw that out
there. It seems it isn't necessarily a root-only feature in 2.2?

[Mark Sanger]

Ttanks for mentioning that Emory, this thread is back on!

[Stefan Sarzio]

Upon installing it, I'm greeted by:

--- cut here ---
Change Log

Version 1.7

Iin Android 2.2, the SDK has been changed were terminating
applications will not end the associated services and notifications.
Currently it will only kill the application's immediate background
process. Due to this, I will be transforming and adding a number of
functionalities over the next few weeks to make this app into more of
a backup and application manager. I apologize for any inconvenience.
--- cut here ---

If I try to kill an app with it, it looks as if it's been killed. But
if I try to confirm with eRay, it still shows the app as running on
all three tabs (Process, Task, Service).

[zeroprobe]

The Kill App function does not work on my HTC Desire Froyo 2.2

Is there anyway around this?

[zeroprobe]

I'm rooted if that helps,

Ahh, I didn't see the above posts for some reason.

[Emory]

Ah yes, OK. I do see that now. Killing a "background task" seems to
succeed perfectly, however killing a foreground task (EG Pandora)
fails miserably, and gets really messy if we try killing something
with running services...

Well never mind then :( I guess I'll just have to cave and root!

[DocHogan]

Not a Tasker user yet (SP user ATM), but probably switching to it in
the next few days.

As a workaround to the 2.2 no-kill issue, which is really frustrating
me right now, is it practical, or even possible, for Tasker to send an
app to background and then kill it?

[Pent]

> As a workaround to the 2.2 no-kill issue, which is really frustrating
> me right now, is it practical, or even possible, for Tasker to send an
> app to background and then kill it?

Try it.

If an activity is not foreground, it's background.

Try Go Home (launcher is foreground), then Kill App.

I can't remember exactly what the new API does and have no time for
testing.

Pent

[Cameron]

So I didn't read up this change in 2.2 and when my HTC Incredible got
the update today, I noticed this in the matter of seconds. Really
sucks too.

The "iheartradio" app on my phone that I use daily simply won't let
the phone sleep like it should. Even if I Menu>Quit in the app, it is
still there, open to some degree, not letting the phone sleep
completely. I see about a 10% increase in awake time unless I manually
kill it (so for every 20 minutes the phone is "sleeping," the awake
time still goes up by 2 minutes, and sometimes way more). Not the
fault of Google or Android, I know, but I was aware of it and simply
had Tasker kill it when I took the headphones out of the jack. Worked
beautifully. As soon as I actually kill the app, the % went well below
a couple percent at most. Does it every time.

I understand the reasoning behind it, but really blows. Naturally, it
is best for the app developer to make an app that doesn't do this...