How Android Works--why we don't need to close the program manually

Content is collected from the Internet, and is subject to deletion
Do not care about the size of the remaining memory, in fact, many people are using other systems to bring the habit of coming. Android most applications do not exit the design actually makes sense, this and the system on the process of scheduling mechanism has a relationship. If you know Java, you can get a clearer idea of this mechanism. In fact, similar to Java's garbage collection mechanism, the system has a rule to reclaim memory. There is a threshold for memory scheduling, only below this value the system will press a list to shut down what the user does not need. Of course this value is set very small by default, so you will see memory hovering in very few numbers. But in fact he doesn't affect speed. Instead, speed up the next time you start the app. This is one of the advantages that Android has advertised, and it's not necessary to artificially close the process. Especially the software that uses the auto-off process. (This solves the misunderstanding that everybody has to close the process!) ）
Someone here will say, why is it slow to run a large program when memory is low? In fact, it is very simple, in memory for a long time to open a large program, it will trigger the system itself to adjust the process scheduling policy, which is very consumption of system resources, especially when a program frequently to the system to request memory. In this case, the system does not shut down all open processes, but selectively shuts down, and frequent scheduling naturally slows down the system. Therefore, the forum has a change in the memory threshold of the program can be a certain improvement. However, changes can also cause some problems, depending on the setting of the value.
So, is there any need for process management software? Some. Just before you run a large program, you can manually turn off some processes to free up memory, which can significantly improve your running speed. However, some small programs can be completely managed by the system itself.
When it comes to this, some friends may ask if the program is not going to consume more power. I'll just talk about the fundamentals of Android backstage, and you'll see. When the Android app is switched to the background, it is actually paused, does not consume CPU resources, and retains only the running state. So why do some programs cut out to re-enter the main interface. However, if a program wants to process something in the background, such as music playback, it will start a service. The service can continue to run in the background, so there are only applications with services that consume power in the background. This can be seen in the process management software, the tag is the service. As for the radio, I'm not involved. So no application with the service in the background is completely non-power consumption, no need to shut down. This design is a very good design, the next time you start the program will be faster, because there is no need to read the interface resources, why should you turn off the advantages of this android? (Tell us how to use process management software properly)
There is also a reason why Android an app looks so consumed by memory. As you know, Android apps are Java, and of course they need virtual machines, and Android apps have standalone VMs, which means that each application opens a separate virtual machine. The reason for this is that you can avoid a crash of the virtual machine and crash the entire system, but at the cost of more memory. (not the same as Saipan, Android is not easy to crash restart)
These designs ensure the stability of Android and, under normal circumstances, up to a single program crashes, but the whole system does not crash, and there is never a hint of insufficient memory to appear. Everyone may be poisoned by Windows too deep, and always want to keep more memory, but in fact, this does not necessarily increase speed, but the contrary has lost the program to start the system characteristics of the fast, it is not necessary. You might as well use this system as I say.
Good luck to everyone, this system is open for 10 days and half a month is no problem, not windows.
The following is a maintenance method
This article comes from Seto のテーマ here thanks!
Multi-work systems, multi-task system
This word is actually more for users and programmers than for the system itself, because no system in the world is not multi-worker.
So why do you have this term?
The reason is very simple, because in fact retasking refers not to the system itself, but the operating environment.
What is the difference between retasking and non-multi-worker operating environments?
When a program is executed, the system has several steps:
1. Put the main program into RAM
2. Executing the program in RAM
3. In accordance with the needs of the program, the use of RAM allocated to the program
In the execution of the program, the multi-and non-multi-worker operating environment is not separate, and at the end of the program.
Multi-Operating environment:
1. Reclaim the RAM used for the program
2. If the program itself is not set to close itself, the main program will be left in RAM
3. If the procedure does not work, it will be on standby in the background, otherwise the background is executed.
Non-multi-operating environment:
1. Force the program to close
2. Reclaim the RAM used for the program
3. Remove the main program from RAM and retrieve the memory
When it comes to this, the difference between a multi-worker and a non-multi-worker will be clear to everyone.
This is the biggest difference between the Iphone, Featured phone, and the multi-work environment of Windows Mobile (WM), Symbian, and Android.
The Iphone always has enough RAM to operate the system, so the system runs smoothly.
A multi-system such as WM, Symbian, and Android can become blunt after a certain number of programs are executed.

How Android Works--why we don't need to close the program manually