Unless there is some evidence that the exact same problems wouldn't happen
again, sorry no.
On Tue, Nov 23, 2010 at 2:05 PM, reistar wrote:
> Do you think this will ever become available again in some form to 3rd
> party apps? I understand the problems task killers caused, but there
> are legiti
I hope not. Task killers are more trouble than they're worth, IMO.
Android OS already provides a way to Force stop an application. And right
next to the Force stop button is the Uninstall button,
--
You received this message because you are subscribed to the Google
Groups "Android Developers" gr
Do you think this will ever become available again in some form to 3rd
party apps? I understand the problems task killers caused, but there
are legitimate reasons for a user to force stop an app. (Like
automating closing programs after an event using a program like
Tasker.)
Thanks,
-Bryan
On Nov
On Tue, Jun 15, 2010 at 3:10 PM, Happy C. wrote:
> Does the "Force stop" in the setting of android 2.2 also use
> "KillBackgroundProcess" or use the system level API (developer can't
> use directly) to make it?
>
Force stop uses the brutal real force stop mechanism that is no longer
available to
Could you elaborate on this?
On Oct 13, 9:01 am, Jerry Fan wrote:
> You can use getRunningTaskInfo compare against getRunningAppProcessInfo. If
> process of particular component is not in runnAppProcess list, then you know
> it is deleted. I used this trick to work around the new kill process
> b
You can use getRunningTaskInfo compare against getRunningAppProcessInfo. If
process of particular component is not in runnAppProcess list, then you know
it is deleted. I used this trick to work around the new kill process
behavior.
On Thu, Jul 22, 2010 at 11:12 PM, Marcin_GUmeR
wrote:
> Is there
Is there any way to replicate old behavior of task killers in froyo?
(i.e. kill everything associated with an app, including notifications
etc. and make it never come back, unless manually restarted)
It can be from command line using root.
Thanks
On Jun 16, 12:10 am, "Happy C." wrote:
> Hi Dian
Hi Dianne,
Sorry to bother you.
Does the "Force stop" in the setting of android 2.2 also use
"KillBackgroundProcess" or use the system level API (developer can't
use directly) to make it?
I have tried the "KillBackgroundProcess" and adding the related
permission, but it can't stop the running ap
Thanks for the extra info and apologies for falsely slandering your
API naming :)
I was under the impression that the UI activities of a package were in
the same process as it's services ? So I had noticed the UI was not
affected and therefore assumed the services were being targetted
specifically
On Wed, Jun 2, 2010 at 1:18 AM, Lee wrote:
> killBackgroundProcesses works (you need a permission for it), but it
> merely restarts the background services, so it's a little poorly
> named.
>
Actually it does exactly what it says -- it kills a process. If an
application has a service that it wa
killBackgroundProcesses works (you need a permission for it), but it
merely restarts the background services, so it's a little poorly
named.
Lee
On Jun 1, 4:26 pm, Mats wrote:
> Hi,
>
> I have an app killing feature in one of my apps but up to API 7 i
> always worked with restartPackage(String P
On Jun 1, 4:26 pm, Mats wrote:
> I have an app killing feature in one of my apps but up to API 7 i
> always worked with restartPackage(String PackageName); but since API 8
> its deprecated so I tried killBackgroundProcesses(String PackageName)
> but that didn't work either.
Googlers on this grou
12 matches
Mail list logo
