What about this:
int pid = android.os.Process.myPid();
android.os.Process.killProcess(pid);
You exit the app asking android to kill your process. I think that
what is used in 3D games as most of them have and exit button, you
kill the process so that it wont drain battery and use memory.
Anyway
System.exit() kills your entire process.
activity.finish() just hides, stops and destroys your activity. Your
process is still running.
You should not call System.exit(). It could mess up Android's handling
of the lifecycles of your activities and result in an awkward user-
experience (e.g. when
You really should be able to just continue using the library. It is not
unloaded, so you don't need to reload it, and can use it again.
To be clear: using System.exit() is strongly recommended against, and can
cause some poor interactions with the system. Please don't design your app
to need
It's too bad the android team can't remove some methods like exit() to avoid
these potential pitfalls that aren't documented very well (at least in most
books). For guich, looks like you would need to implement some way of
detecting that the library is already loaded, so as not to load it again.
4 matches
Mail list logo
