What if the Android phone daemon doesn't shut down? Android Phone daemon cannot close workaround

Android Phone Daemon can't close workaround

The problem with Android's back-end is entirely due to the Android broadcast system. In simple terms, when a user installs a program, the system will record the function of the program like the interviewer, when the user is using the mobile phone, the system state changes will produce various events, these events need some program to process, the system will send broadcast message, and these can handle this matter of the program will be enabled, Which program to use, this is the system by default program or user-selected program to handle this event.

For example: Just as you open a company, Android is your housekeeper, those programs are the employees who come to you, the housekeeper will record the ability of these workers, such as a will scrubbing, B will be big health care. When you want to scrubbing, the housekeeper will call a to come to help you scrubbing. When you want a big health care, the housekeeper will call B to come and give you a big health care. Even if the program is in hibernation, it will be called up. That is, no matter how you shut down these apps, when you need it, it's a screw, where it needs to be nailed.

And, of course, there are programs that you don't need to start from, this is because of interest, many domestic rogue software has changed the priority of their own programs, plus the addition of the authority to terminate other programs, as well as the function of increasing the daemon, when the detection of their own people were killed, A direct resurrection allows the program to be resurrected with blood full of blue. Other social software is to ensure that the message can be pushed in time, but also to make some priority changes.

Android Phone daemon can't close workaround

If running memory is large, is it not necessary to shut down?

In fact, the concept of Android system design is to dilute the user's management of the background, the allocation of mobile resources to the system can be completely. Android sets a threshold, which defaults to a very small number, so we see little memory left, which in fact does not affect the speed of the phone, and it has its own rules to reclaim these memory, and when memory usage reaches a critical value, Opening another program system again selects some programs that are less important to turn off to free up memory for the program to run.

And the reason we feel the phone is going to slow down when you open a large program is that when you open the program, this program will apply memory to the system, because the system will not shut down all processes, but only selectively to shut down, so will mobilize a large number of system resources to operate, naturally will be slowed down the system. Changing the threshold of the system will improve a lot, but it may also cause problems.

Therefore, the background of the program itself does not need to shut down, if you run a large program can be manually shut down, this can significantly improve the speed, and the normal use of the time does not need to take care of it. As for the size of the memory, unless you have a large memory to a certain extent, you install N more apps will eventually reach this threshold.

Okay, the reason that Android phone daemon can't be shut down, and the solution that the Android phone daemon can't shut down. Here is a small series for everyone, I hope to help.