text | Xiaoyiping Technology
Recently, a friend sent me a private message in the background and said he had a problem. The mobile phone he is using now is Huawei Mate20 equipped with Kirin 980 processor released four years ago.
According to his own understanding, the performance of Kirin 980 can basically compete with Snapdragon 778G at this stage, but why does the Huawei Mate20 in his hand start to get stuck? It is even smoother as those mobile phones equipped with lower-end SOCs that you see in mobile phone stores (the performance configuration of a large number of low-end phones on the market is not as good as that of Huawei Mate 20), such as the Snapdragon 695 equipped with Honor X30.
So, in this article we will do an in-depth analysis - to answer the question of "The performance of the processor is obviously enough, why do old mobile phones still get stuck? ", and will also give you some popular science on how to prevent and improve.
. Degraded flash memory performance is one of the core reasons for the lag in mobile phones.
In my previous article, I have shared with you an experience - , including mobile phones and computers, once these devices have frequent intermittent lag problems, most of them are directly related to the bottlenecks in the read and write nature of the hard disk.
The static memory currently used on mobile phones is mainly based on the NAND FLASH+ controller mode, which means that the structure of SSD solid-state hard disk on the PC side is the same, but the protocol is different.
. All storage media that adopts a similar structure will have a common problem. is the attenuation of read and write speed . Once the read and write speed of flash memory is attenuated, it will directly affect the IO performance of the system file, resulting in a series of problems such as lag in the system.
and flash memory have a problem of degradation in read and write performance. In addition to the lifespan problem, there is another very common problem that is - is too full of .
flash memory chip generally needs to perform an erase operation when performing a write operation. Before performing an erase operation, the data originally stored in this location will be migrated first. It can be understood that it is to migrate the data in this piece to other spare locations first, and then perform the write operation.
So if you don't have enough space at this time, the master control can only start the erase operation frequently, which will cause a brief decline in read and write performance, and what the consumer shows is that the phone is stuck and the processing task is delayed.
This is one of the reasons why new phones always give people a very smooth feeling, because the flash memory of new phones is in full health, which is incomparable to old phones.
Secondly, the flash memory performance will decline permanently with the increase of the usage cycle, because NAND FLASH and the master control have their actual service life. Once the write volume reaches a certain order of magnitude, the read and write performance of SSD will irreversible decrease. At this time, the mobile phone will experience a very obvious lag problem. Of course, the design life of mobile phone flash memory is relatively long, and it is difficult for ordinary users to use flash memory.
Solution:
1. When purchasing a mobile phone, try to buy models with large memory combinations. Judging from the actual usage situation at this stage, if the budget is sufficient, try to start at 256G as much as possible.
2. Regularly clean the storage space and try to control the space available to more than 20%. You can turn off the permission to automatically download images in WX (WX will no longer automatically download images, which can greatly reduce the space occupied by WX)
. The rogue behavior of the application leads to the occurrence of storage. (Exclusive to Android system)
Due to the lack of an effective unified push mechanism in the domestic Android market, the push of new messages to all APPs can only rely on the push process built into the APP module. In other words, as long as you can see the notification APPs are secretly residing in your memory, some of which are even stored in the memory.
Moreover, due to the disorder of the Android ecosystem, in order to give their APP the power to push information, applications on the Android system will also establish an indescribable alliance - the "association startup alliance". These APPs will reach a tacit understanding and use a built-in SDK interface to play the role of chain call wake-up. Simply put, when you open software A, you will start the message push process of B and C software at the same time. This is why sometimes I can push information in the notification bar even though I didn't open this.
Perhaps one or two processes are not afraid of the consumption of runtime memory, but once there are too many such processes, it will inevitably occupy the space of runtime memory. Once there is a bottleneck in the runtime memory space, it will frequently start the extreme memory recovery and call the flash memory space with slow reading and writing speed to interact with information, which will cause the phone to stutter. The problem of
is almost unsolvable at present, and it will not be possible until the unified push alliance is fully completed. However, at present, it is still a long way from the real establishment of the alliance.
Solution:
1. Turn off all uncommonly used information push functions. The closing methods of different systems are different. Generally, they can be set by long pressing and sliding the notification bar information left and right.
The mobile phone I currently use only retains notification permissions for phone calls, text messages, WX and necessary notifications of the system. The notification permissions for all other APPs have been closed.
. "Negative Optimization" of mobile phone manufacturers
Currently, there are many cases of negative optimization of systems that can be officially certified. Let me give you an example: According to a report in 2018, the Italian authorities imposed a fine of 5 million euros on Apple and Samsung , respectively. The reason for the fine is that these two companies are suspected of intentionally reducing the running speed of old devices through software updates .
Among them, Apple has become the first in 2017. The system will appropriately "slow down" old devices (reduce the CPU frequency) to ensure the battery life of the phone. Reducing the CPU frequency will inevitably reduce the CPU performance, thereby affecting the smoothness of the mobile phone system. This is the origin of the " speed reduction gate " that has been sensational.
Although other mobile phone manufacturers have not exposed relevant information, most of them have similar practices, and some may not be intentional. For example, some new systems have high requirements for mobile phone performance, which causes mobile CPU to be in a high frequency state for a long time, resulting in the surge in power consumption and lag problems, which are very common.
Why did the former OPPO and VIVO models always give people the illusion of "the performance is not high but not easy to stumble", ultimately because OPPO and VIVO mobile phones rarely updated the system before, especially the major versions of the underlying version.
Solution:
1. Try not to update the system for old models, especially for systems that update large versions of the system.
or above is the answer to the question "The performance of the processor is obviously enough, why do old mobile phones still get stuck? ". I hope it can help you.
END
