V880 + manually close the program? Mistakes in Android

Andriod is developed based on a Linux system. This is very important because I believe many people or even some experts will ignore this and fall into a misunderstanding. What are the misunderstandings? It is to manually turn off the search, and pursue a larger memory surplus.

We are used to the Windows system and get used to the concept of larger and faster memory. This concept is also maintained when you use Android mobile phones. The program is often closed manually to save memory. Actually, this is not necessary. As an andriod system, or a Linux system, it is totally different from a Windows system, so their memory view is totally different.

Next I will explain why I don't care about the memory size. In fact, I have already published this article in the forum. This time I will be a porter and send it again, but the red ones are some of my own feelings. So it is also an article I have tested. If you are interested, verify it.

Most Android applications do not exit the design, which is related to the system's scheduling mechanism for processes. If you know Java, you can better understand this mechanism, Because Java itself has a garbage collection mechanism. Similar to Java's garbage collection mechanism, the andriod system has a rule to recycle memory. There is a threshold value for memory scheduling. Only systems below this threshold value will close things that are not needed by a single list. Of course, this value is set very small by default, so you will see that the memory is always at a very small number. But in fact it does not affect the speed. On the contrary, it accelerates the next application startup. This is one of the advantages advertised by Android. It is not necessary to manually shut down the process, especially the software that automatically shuts down the process. (This is why I am talking about not to manually close the process. And I believe that as a stable system, the setting of each value should be the most balanced, so there is no need to blindly pursue the value size, enough .)

You may ask, why is it slow to run large programs when the memory is small? This is actually very simple. Opening a large program when there is not much memory left will trigger the system's own process scheduling policy, which is an operation that consumes a lot of system resources, especially when a program frequently requests memory from the system. In this case, the system does not shut down all open processes, but closes them selectively. frequent scheduling will naturally slow down the system. (This is why large programs are slow at the beginning, but gradually resume normal speed later. Of course, the adjustment time depends on the quality of the machine .)



Is process management software necessary? It is necessary. Before running a large program, you can manually close some processes to release the memory, which can significantly improve the running speed. However, some small programs can be managed by the system itself.



Speaking of this, netizens may ask again if the program will consume more power. Some netizens are concerned about whether traffic will be charged. Let me talk about the principles of the android background and you will understand it. When the Android app is switched to the background, it is actually suspended and does not consume CPU resources. It only retains the running status and consumes little traffic. (This is why we switch out some programs and re-import them to the main interface of the program ). However, if a program wants to process something in the background, such as playing music, it will enable a service. Services can continue to run in the background, so only applications with services consume power in the background. This can be seen in the process management software. The label is service. I will not talk about broadcasting or anything. Therefore, applications without services have no power consumption in the background, and there is no need to disable them. This design is a very good design. It will be faster when you start the program next time. Because you do not need to read interface resources, why should you disable them to erase the advantages of Android?



Another is why an Android app seems to be so memory-consuming. This is because applications on Android are Java and virtual machines are required. Applications on Android have independent virtual machines, that is, each application opens an independent virtual machine. The reason for this design is that the failure of the virtual machine can avoid the entire system crash, but the cost is that more memory is needed. (So we will find that, if the andriod system is used normally, there are very few crashes, except for the bad firmware changes .)



The above design ensures the stability of Android. Under normal circumstances, a single program may crash at most, but the entire system will not crash and there will never be any prompts of insufficient memory. (You may get used to using Windows. The concept of memory is too poisonous. You always want to keep more memory, but in fact this does not necessarily increase the speed, on the contrary, it is unnecessary to lose the system feature of fast program startup .)

I also downloaded the process management software when I was using it. Later I found that it was slightly different (because I played a small number of large games), so I am very confident in andriod's ability to adjust the memory.