While Ninjas answer provided an opportunity to close many actions on the stack, please note that the Android method was created, the application cannot directly interact with another ... this is how the security function blocks most unnecessary programs, as well as malwares / virus / etc .d.
The only real way to force the application to close is to block resources for it (using the Android Settings tool to put the application in the βnot runningβ state), or switch to the next system (mainly Linux) and refuse resources, this trick but possible.
If I open the same task killer application again in a matter of seconds, the same application will appear again, which was said to be killed earlier. Now is this an application error or an Android OS?
This is an OS error, but it behaves EXACTLY as expected. No program can modify / edit your program. Like the ninja, he basically asked the system to ignore any actions on this stack. But if multi-level stacks are present ... well ... no, then this is an APP error.
Not only here, even if applications have the "Exit" option, I noticed that pressing the exit button does not exit. So where is the problem?
A programmer should NOT leave his application, because its not a complete program, you basically execute commands inside another program, so the rules must be followed. Once you get started, memory management is not in your hands, so you cannot / should not "exit" applications.
Is there another way to close the application when we want and make it behave normally?
I do not understand this. In the application life cycle, everything either behaves normally (or you know, stopped: example stopped working), or in a ready state