How to manage remaining memory on your Android phone

The original poster: Hakurei Reimu Views: 1141 Replies: 1 Posted in: 2012-03-04 18:57:20
Users of Android phones may have installed task management software. Is it really necessary to install task-ending software when using Android phones? Everyone has also discovered during use that many software will appear in the task list immediately after being terminated, or it will appear itself after a while. Task management keeps ending background programs, but it does not bring much improvement to the running speed of the phone. Why is this?

[Text] In fact, you don't need to care so much about the remaining memory size of your Android phone. Many people have brought their habits of using other systems to their Android phones, and not all smartphone systems are the same. The design that most Android applications do not exit actually makes sense. This has something to do with the system's process scheduling mechanism. If you know java, you can understand this mechanism better. 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 when the value is lower than this value, the system will close things that the user does not need according to a list. Of course, this value is set very small by default, so you will see the memory hovering at a very small value. But in fact it doesn't affect the speed. On the contrary, it speeds up the next application launch. This is originally one of the advantages of Android. If you manually close the process, it is not necessary. Especially software that automatically shuts down processes.

Some people may say, then why is it slow to run large programs when there is little memory? In fact, it is very simple. Opening a large program when there is not much memory left will trigger the system's own process scheduling strategy. This is a very resource-consuming operation, especially when a program frequently requests memory from the system. In this case, the system does not close all open processes, but selectively closes them. Frequent scheduling will naturally slow down the system.

So, does process management software still have value? In fact, there are still some. Before running a large program, you can manually close some processes to release memory, which can significantly improve the running speed. However, some small programs can be completely managed by the system itself. Many friends still have a question, will it consume more power if the program is not turned off? Let me also explain here that when an Android application is switched to the background, it has actually been suspended and does not consume CPU resources. It only retains the running state. So why do some programs still return to the main interface when they are cut out and re-entered? 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 only applications with services consume power in the background. This can be seen in the process management software, and the name is service. Therefore, applications without services consume no power at all in the background and there is no need to close them. This design is inherently a very good design. The next time you start the program, it will be faster because there is no need to read interface resources. Why turn them off to obliterate the advantages of Android?

One more thing, why do Android applications seem to consume so much memory? As we all know, applications on Android are Java and of course require a virtual machine. Applications on Android have independent virtual machines, that is, each time an application is opened, an independent virtual machine will be opened. The reason for this design is to prevent the virtual machine from crashing and causing the entire system to crash, but the price is that more memory is required.

As for why switching becomes slower after opening a large program or opening several programs, the specific analysis is as follows:

A large program has been opened, occupying 70% of the memory. If you want to run another program, which still requires 50% of the memory at this time, a process of releasing or compressing the memory occupied by the large program is required, so it appears to be slow for a while.

Several programs have been opened that occupy a total of 80% of the memory. When running a new program, another 20% of the memory is needed. Since the system memory has never seen the remaining 0, that is, there should be some free memory left. Then you need to select one or several of the previously opened programs to close. This process also consumes system resources, so it will be slow for a while. In other words, when you manually end the program, you are releasing memory for the system. Even if you don't end it, the system will automatically end the program to release memory when memory is needed.

Programs that are not running in the background (without services) will not consume power even if they are not terminated. Programs running in the background (with services), such as some players or real-time monitoring software, will naturally consume power. This shows that ending the process is not useless. We only need to see which service consumes power and which program is running in the background. You can see it by looking at the service. If such software is no longer used, it should be terminated.

Taking QQ as an example, a normal exit will leave the running status of QQ in the process management, but it does not consume power and does not occupy the CPU. If you just switch out (press the house key instead of exiting), then it will naturally consume power, because the program is still running and QQ is still online.

There is something to note here. Although both the house key and the return key can switch out the program, the effect of the two is very different. The return key can be regarded as the program has exited, while pressing the house key switches the program to the background to run, and the software does not exit!

The above designs are all to ensure the stability of Android. Under normal circumstances, at most a single program will crash, but the entire system will not crash, and there will never be a prompt for insufficient memory. You may be too poisoned by Windows and always want to reserve more memory, but in fact this will not necessarily increase the speed. On the contrary, it will lose the system feature of fast program startup, which is not worth the gain. You may wish to change your mindset and habits to use the android system.
reply 🤍 0 📤 share collect
Oops, I messed up again!
— All replies loaded —

Leave a Reply