Android Question Activity.finish

Hi,
You have to be sure to stop all services (StopService) related to your application, finish all activities (Activity.Finish) and after that only you call ExitApplication

lemonisdead said:

Hi,
You have to be sure to stop all services (StopService) related to your application, finish all activities (Activity.Finish) and after that only you call ExitApplication

Click to expand...

Thanks, I'll try. No service modules in current application. Do I still need StopService ?
Hamo

No if there is no service, you don't have to stop any

No, it doesn't work, I still have to go to settings, app manager, force stop to close the app completely.
This is the one single thing I hate about android. When I terminate an application I want it out, finished,
kaput, not still running. is there no way to do this without going to settings, app manager, force stop ?
Hamo

I am sorry but you talk about the "Force stop" button, right ? It is how it works. Look at other apps you haven't already started. On my phone they are working exactly like the way you are mentioning

finished, kaput, not still running

Click to expand...

kidding: What about the use of a bazooka ?

When I exit a program I want it to close, finish, disappear. I think it's stupid that it still runs in the background
using resources if nothing else. Who wants the engine still running after turning the key and getting out of the car ?
Hamo

Hamo said:

When I exit a program I want it to close, finish, disappear. I think it's stupid that it still runs in the background
using resources if nothing else. Who wants the engine still running after turning the key and getting out of the car ?
Hamo

Click to expand...

The engine will stop when the fuel is finished, don't worry too much

bsnqt said:

The engine will stop when the fuel is finished, don't worry too much

Click to expand...

That's partly the problem, I don't want the fuel to finish when I'm not using the car.
Hamo

Hamo said:

Is there no way to completely terminate and close the app and remove it from memory when the user presses exit. I have tried exitapplication and activity.finish but the blooming thing still stays in memory until I go to settings, app manager and force stop. Occasionally the tablet freezes and I need to ensure it's not because the app still running in the background.
Thanks for any help.
Hamo

Click to expand...

I stumped on the same issue as you have before when I started developing an android app. From what I learned and read around here it is not possible because it's the way Android was designed. This is a quote from one of the threads I've read before:

Erel said:

The process is kept in the background until the OS decides to kill it. -snipped-

Click to expand...

If you want to read more you can check out these two threads I've bookmarked for reference:
Exit.Application and Activity.Finish
exitapplication ends the app?

Hamo said:

When I exit a program I want it to close, finish, disappear. I think it's stupid that it still runs in the background
using resources if nothing else. Who wants the engine still running after turning the key and getting out of the car ?
Hamo

Click to expand...

Why? It doesn't make sense.
In the background your app waste 0% cpu cycles (if no service is used). It sleeps and need only a little bit memory. And if your system runs into low memory, Android kills your app.
On the other hand, your app starts faster if it remains in the background.

Why? It doesn't make sense.

Click to expand...

Now, I wonder if the major problem isn't this one :

exit a program ... disappear

Click to expand...

Is it the case ?

I agree with Hamo. The way Android handles exiting applications is annoying. I also do not like that Android keeps things in memory lingering. Android is not good at cleaning up memory... hence, why so many people are constantly in the APP settings pressing the FORCE quit buttons.

I consider this a design flaw in Android, that may have started out as a good idea for slow devices that took awhile to load resources and execute programs, but, on modern devices this is just an annoyance now.

The reason it becomes an annoyance is because Android will unload resources but not reset the FIRSTTIME flag, so when your app comes back to life, from a user running it again (thinking he is running it brand new again), it often can crash the app as the resources aren't there. So, the FirstTime flag is not reliable in my opinion, which kind of kills the reason for having a first time flag in the create subroutine.

This is why people want to kill off their apps, because it is the proper thing that should be done, but Android doesn't really allow it.