thanks a lot everyone...
now my apps running fine... :)
On Tue, May 26, 2009 at 9:11 PM, Mariano Kamp wrote:
> You see the tasks of the most recent activities. If you select one and the
> attached app and process is still running it will be brought in the
> foreground, if not it will be started f
thanks but if thats the case, why does the sdk provide
Process.killProcess(Process.myPid())???
& wat does android actually do when i call this method as above???
On Tue, May 26, 2009 at 7:51 PM, Mariano Kamp wrote:
> In short: Don't worry.
>
> A bit longer: Android manages the apps' states.
>
i tried that out... ddms says that the process died...
but when i long press the home button to see the running apps, i see mine as
well...
then y does ddms say that the process was killed???
Is it a bug that a dead process still gets displayed along with other
running apps???
can any one temme y t
I never saw a need for that and don't know what would happen. Try it out.
My guess would be, that you can kill the processes launched by your user id.
On Tue, May 26, 2009 at 4:41 PM, Sujay Krishna Suresh <
sujay.coold...@gmail.com> wrote:
> thanks but if thats the case, why does the sdk prov
You see the tasks of the most recent activities. If you select one and the
attached app and process is still running it will be brought in the
foreground, if not it will be started first and then brought into the
foreground.
That's what I meant with "Don't worry about it. Android OS manages that."
AFAIK, Process.killProcess(Process.myPid()) is equivalent to
System.exit(0) in Android, but I stand corrected.
On May 26, 4:41 pm, Sujay Krishna Suresh
wrote:
> thanks but if thats the case, why does the sdk provide
> Process.killProcess(Process.myPid())???
> & wat does android actually do w
Yes, you can use System.exit(0) in your own app. I applied this myself
for some time when I could not track down a bug in my app that ate
memory by creating new threads without killing old ones upon app
restart, and System.exit(0) then provided a temporary workaround to
start fresh until I later f
hmm so wats the no of apps that are shown??? i get varyin no based on the
currently runnin apps... not basd on recently used apps...
On Tue, May 26, 2009 at 8:48 PM, Urs Grob wrote:
>
> Longpress in home only shows the last accessed apps, not the currently
> running apps.
>
> -- Urs
>
> On Tue, M
Longpress in home only shows the last accessed apps, not the currently
running apps.
-- Urs
On Tue, May 26, 2009 at 5:13 PM, Sujay Krishna Suresh
wrote:
> i tried that out... ddms says that the process died...
> but when i long press the home button to see the running apps, i see mine as
> well
In short: Don't worry.
A bit longer: Android manages the apps' states.
The user keeps on doing things, launching tasks, firing intents etc. and
when Android OS doesn't have enough memory left it kills of apps that are in
memory, but don't seem that important anymore, e.g. because the UI is not
vis
Say i wanna do something like java's System.exit(0)...
jus to make sure that my application is not running anymore...
I wanna kill my own app... not other apps... this should be possible...
On Tue, May 26, 2009 at 7:38 PM, Marco Nelissen wrote:
> On Tue, May 26, 2009 at 6:56 AM, Saurav Mukherjee
On Tue, May 26, 2009 at 6:56 AM, Saurav Mukherjee <
to.saurav.mukher...@gmail.com> wrote:
> how do i kill an android application
Why would you want to do that?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups "Androi
12 matches
Mail list logo
