Define a concept first. The memory we usually refer to refers to the system cache, that is, the "memory" seen by the "display power" software. This cache is usually relatively small, less than 65,438+0 megabytes. That is, the mobile phone is stored, the memory card is stored, and the data cache area used when the program of the machine's own system runs. It plays a role in storing mobile phones, storing memory cards, and exchanging data between the machine's own system and the machine's cpu. This bridge is often the chief culprit of plane crash and death, and the usual plane crash and death are more or less related to it. The memory we will talk about in the future is this "memory" instead of "mobile phone storage". Attention, everyone! Mobile phone storage is equivalent to our computer hard disk. In a mobile phone, like memory card storage, it is just a storage device, not a memory (an interesting phenomenon in a mobile phone is that we call our own storage part machine memory, which really misleads many people). Ok, we understand what memory is, and then let's talk about why the lack of storage space in the mobile phone will lead to a crash.

Let's take an example first: Remember the old computers in earlier years! Usually their hard drives are not very big. When we are crazy about storing things in it, and the hard disk is almost full but not full (for example, there are more than 100 megabytes of space left), do computers often appear? Yes, that's the blue screen. Why the blue screen? Isn't there still 100 megabytes available? This should start from the principle of computer data storage: no matter what program the computer is running, it is necessary to read the relevant data used by this program from the hard disk and store it in the memory, and then the cpu will take out the data used for its calculation from the memory (this also has to go through the "bridge" of the first-level and second-level caches that the cpu comes with). The first-level and second-level cache plays the same role between memory stick and cpu as the memory stick does between hard disk and cpu, which speeds up data exchange. When reading from the cpu, you should know that the cpu reads data from the memory stick much faster than directly reading data from the hard disk, which greatly improves the speed of program execution. After the calculation, the cpu will execute the calculation results. For example, if the calculation result is to execute an instruction: open the folder, then the computer will display the contents of the folder. For example, when we input a document, the cpu of the computer calculates what text we input by tapping the keyboard, so it puts the text we input there, that is, in the memory, until we give it a command to "save" the text we input, it will transfer the content we input from the memory stick to the hard disk. However, the fact is that the computer can run because of the calculation of cpu. All our actions, even the display on the monitor, including moving the mouse, have to be calculated and commanded by the cpu, and the complicated and huge intermediate results of these calculations and commands are often temporarily stored in the memory stick. Only when the cpu thinks that the memory can't be loaded, or we give the computer a save command, will it be transferred to the hard disk. During this process, the hard disk will always be stored. At this time, the cpu has to spare energy to check the storage location on the hard disk from time to time, so that the next storage can be connected from this location. When our hard disk is almost full, the remaining space often exists in the form of fragments, which increases the difficulty for cpu to detect and store it on the hard disk at any time. In addition, the previous cpu was not very fast and the memory bank was not very large, so this dump should be carried out frequently. This large amount of data exchange causes the cpu to run wildly, which may lead to a crash. This is why the computer often appears blue screen or crashes when the remaining space is not much.

Well, talking so much about computers is just to attract attention to our mobile phones. As mentioned earlier, the storage in the mobile phone and the storage in the memory card are all storage devices in the mobile phone, not real "memory", but equivalent to the hard disk in the computer. The real memory is "memory" with less than 1 megabyte space (which we can see by software "displaying power" or files). Speaking of this, I understand why the mobile phone is more likely to crash when the storage space is insufficient. There is no need to say more about the similarities between the smart phone system and the computer windows system.

Everyone uses OxiosHibernat, a software that releases memory. Have you noticed a very interesting phenomenon? That is, under any circumstances, no matter how slow your system is, no matter what program you used before releasing the memory, as long as you click OxiosHibernat to release the memory, the released memory will never exceed 888k K. That's right, because the "storage memory" itself is only 888k, how can it release more than it? Our famous software for releasing memory is equivalent to the memory in the computer and the memory in the mobile phone, not the memory and memory card in the mobile phone.

The crash caused by improper operation can be avoided unless you have no experience in using computers. Although it is a smart phone, neither the operating system nor the cpu can compare with the computer. Therefore, it is recommended that telephone friends use it in a single thread, and it is best not to do anything else when the program is being executed (when the "busy" symbol appears). For example, your mobile phone is searching for a picture in a card. At this time, you may want to quit the search by pressing other buttons, but the persistent phone must be searched to the end, and the two sides are deadlocked.

The ambient temperature is too low, leading to a crash.

For a long time, whether the ambient temperature will cause the crash has been a topic of debate among the majority of aircraft friends. The answer is yes, low temperature can really cause a plane crash! However, this is not a defect of mobile phones. On the contrary, the self-protection function is poor. Windowsmobile2003 operating system has the function of detecting the ambient temperature. The thermometer software we use relies on the windowsmobile2003 operating system to detect the temperature. In fact, it only reads the temperature detected by the operating system itself, not the "thermometer" software itself can detect the hardware temperature. Some people say that the thermometer detects the temperature of the battery, which is one-sided. In fact, it is to find the code that can judge the current and voltage of a certain part of hardware in windowsmobile2003 operating system, and measure the temperature through conversion. This code is controlled by hardware, which means that the voltage of this hardware is very sensitive to temperature. This hardware is usually cpu or "cache" (not memory, that is, it is not what is usually called mobile phone storage), and of course there are sometimes batteries. This is also the reason why "thermometer" can be used on windowsmobile2003 on some mobile phones, but not on windowsmobile2003SE of some machine friends. The reason is that there are great differences in code segments between 2003 and 2003SE. The thermometer is still looking for the code in its original position, but of course it can't be found. Even the same machine, if the battery of another brand is replaced, sometimes the temperature cannot be read because of the change of code segment. It is this temperature change that causes the hardware current or voltage change inside the machine, and then causes the reaction of the system monitoring part. However, due to the incomplete software design, it may be a number of loopholes in the design, or it may be that the designer simply did not take into account that the operating system was left to fend for itself, or even "crashed" to reach the temperature tolerance, preventing the machine from continuing to run. This is indeed a big problem for the system designer to solve! So why does the windowsmobile2003 operating system react to low temperature? I don't want to explain too much, which involves the working principle of liquid crystal. In order to make the LCD of the mobile phone display normally, it is necessary to ensure that the mobile phone runs in a certain temperature range, so the operating system must monitor the temperature. The vast number of machine friends can do an experiment in person and start the machine at a relatively low temperature (such as below 5 degrees). After the screen of the machine loading system appears, the system will automatically shut down and refuse to start, thus realizing self-protection.

On the contrary, when the temperature is relatively high, such as higher than 24 degrees, or when the sun shines directly on the screen, the response speed of the machine is much higher, and the response time of the screen should be shortened by at least half. At the same time, the display has been completed without any delay! It is worth mentioning that the phenomenon of freezing caused by low temperature not only occurs in standby time, but also occurs in "flight mode", so it is not wrong to take a "death" photo!

Conclusion: No matter how strong the mobile phone is, we should give it some temperature. When there is a crash caused by low temperature, there must be a second crash, and the temperature of each crash is higher than the last one. The high temperature of the last plane crash may be unbearable for you. Especially friends in the north, pay more attention in winter. It's best to put your mobile phone outside your underwear, not around your waist like a farmer.

Crash for no reason during standby.

Now it's the turn of the problem of unprovoked crash in standby. Most of the crashes during standby are caused by the software running mode of windowsmobile2003 operating system. We know that our mobile phones are usually used for making phone calls, which is also a priority for software designers of windowsmobile2003 operating system. Therefore, when the mobile phone is on standby, most of the mobile phone resources are given priority to the standby signal part. On the other hand, windowsmobile2003 operating system should also take good care of our own DIY software, automatically search the information of the software we installed every once in a while, and make a record through cache. If this record is long and complicated, and the operating system is busy with signal communication with the base station, it is necessary to search for machine information and make a record, which may lead to a crash during standby. This is why software such as OxiosHibernat releases memory (cache). Indeed, when the machine automatically reloads the searched information every once in a while, and does not release the original information, the cache space (instead of the mobile phone storage) becomes smaller and smaller, and the probability of crashing increases! This phenomenon is serious in a few mobile phones, but it has been reduced due to the use of 2003SE and the increase of cache.

So how to solve this problem, in fact, everyone will, just pay attention to the order: First, hard start, restore factory settings. Then run safely for 7 days, without installing any software or inserting a memory card, and the temperature is at least higher than 15 degrees. (The so-called safe operation means that it is not allowed to crash in the middle, which requires that the ambient temperature should not be lower than 15 degrees when it is turned off, especially when it is turned on in the morning, to ensure that the body temperature of the machine is higher than 15 degrees. If there is a crash in the middle, it is necessary to restart hard and recalculate the number of days. The purpose of this is that when the windowsmobile2003 operating system searches for its own software (in the system), it finds that there is no "intruder", that is, there is no software installed by the user (in the mobile phone storage and memory card storage) and marks it. After this mark is completed, when the user installs the software by himself after the safety period, the machine will search again, and it will start searching from below this mark, that is, only the storage of the mobile phone and the storage of the memory card will be searched, and the search for the self-contained software will be skipped. Otherwise, if we install new software immediately after hard boot, then every time we boot it, we think it is a lot of newly installed software, and every time we boot it, we will tell ourselves that there are a lot of intruders, so that every once in a while, we will automatically re-search the information of new software in all the spaces, which increases the burden of machine search. The result is often nothing wrong from the beginning. Over time, the use of our installed software (new information) contains all kinds of information used every time, and this information often becomes garbage in mobile phones. Most users often find that the memory of mobile phones has become smaller, which is caused by this information. Constantly writing the records of the original program, when the system automatically searches every once in a while, the burden is gradually aggravated, and the worst result is inexplicable collapse during standby.

During the safety period, users should pay attention to the "tester". The so-called "trial run" means that you should use the machine frequently in these seven days, and use all the functions of the machine, such as "games", "shortcuts" and various settings, to increase the system's familiarity with the software.

After the safety period, you can plug in the memory card and install software for the memory card and mobile phone. From then on, every time the machine searches, it is actually just searching for the software information in the memory card and the mobile phone, and it will ignore the search for the mobile phone itself. I want to emphasize here that some mobile phones without memory cards will crash, largely because the operating system is unfamiliar with the software. Pay attention to the test machine in the safety period, and be sure to install the software in the memory of the mobile phone after the safety period. When we follow the above method and plug in the memory card, we can see that there is an additional "storage card”storage card from the file manager. From now on, the machine will not actively search, so all the icons of the software installed in the card will be displayed in the same unrecognized label style after booting. Only when we give the machine a stimulus and order it to search the information in the card will it search.

We can do an experiment: turn it off first, then turn it on, and press the left soft key "Start"/"Other"/"Other". You will find that all the software icons installed on the card are unrecognizable label styles. Then press "Home" to return, and then press "Start"/"Other"/"Other". Similarly, the software in Cary is still labeled unrecognizable! Yes, the machine did not actively search the software information in the card, and the software information in the cache was reduced. Such machines are usually not easy to crash, which is our purpose. So how to stimulate the machine to search? We can press "Other" to the last page, enter "Games", open "Lingyun Aspiring" to play, then close the game and return to the home page. This time, let's take a look at the software icon installed in the card. How's it going? The icons have become the original faces. Why can playing "games" stimulate the machine to search for program information again? First of all, this is a big game; Secondly, this game comes with the machine. When we run this game, it will take up a lot of resources, which is what we usually call space. This "space" of course includes "cache", so when a large amount of data comes in, the machine will empty the original search program information, pour out the space and go all out to ensure the operation of the game. The game is over, the space is restored, and the machine has to search the installed software information again. In this search, the information installed in the card is read into the cache and the icon is restored.

five

Software problem

The main reason is that there is a fatal BUG in the design of mobile phone software, which leads to the crash. For example, when a mobile phone runs a program, if there is a logical error between the subroutine and the main program, there will be an instruction error whenever the mobile phone runs to the program, which is a bit like illegal operation in a computer, and then it may crash. Generally speaking, the crash caused by software bugs has such a characteristic: every time a command is run, that is, every time the same operation is performed, it will crash. If the phone always crashes like this, it can be preliminarily concluded that it is a software problem. To solve such a crash, you can generally solve it by upgrading the software. However, such an upgrade can only upgrade the software version. After the upgrade, the function of the mobile phone will not change, but some software bugs are solved during the upgrade process. Reduce the chance of collision. Unfamiliar with the software when upgrading will cause instability of the mobile phone. If you upgrade, please make a backup in advance to prevent the software from recovering after the phone upgrade fails.