Compared with the App Store on the iOS platform, Android's application review system is relatively imperfect. Many domestic application developers do not comply with Google's design specifications. There are many examples of "resident backstage+mutual wake-up". Everyone is most familiar with BAT wake-up battle group. Yes, most of the applications of the three giants of the domestic Internet can be called cancer products, But every aspect of life makes us unable to get rid of BAT. Today, we will take a look at another pair of classic Xposed plug-in combinations [block operation+prohibit wake-up] that can eradicate rogue applications in addition to the well-known green guard.
The so-called skill industry has specialization. Although the green guard can achieve sleep application+cut-off wake-up, the large and comprehensive application is often less powerful and effective than the skill industry specialization. Today, let's take a look at the magic of the Xposed framework plug-in (Block Run+Disable Wakeup).
Block Run
The use of blocking operation is quite simple. After the activation is successful, the application list page will be displayed when the application is opened. After the user selects the application to be disabled, click the upper right corner to complete the configuration.
There are four categories for blocking running applications:
[- 3] Third party application (white)
[- s] System application (red)
[- e] Exclude Unblocked Apps
[- g] Google Apps
[- r] Running applications
Blocked applications are also divided into three types:
[Hexagonal] indicates that it is in the block list, but it is not currently blocked because it is opened or relied on by other programs;
[Circle] indicates that it is successfully blocked in the block list;
[Star] means that although you are in the block list, you will not be forced to kill unless you actively exit/kill them. This is mainly for automatically stopping background programs by force.
Compared with the green guard, it is simpler and more violent to prevent running. After clicking "Return" to exit, the application will be logged off from the background 6 seconds later by default. Users who are familiar with the Xposed framework should know that the framework uses the control system API to implement various functions. It is this way to prevent applications from staying in the background, which fundamentally prevents applications from staying in the background for a long time.
In addition, the developer also provides some obsessive-compulsive settings, such as Don't Keep Process. By default, after exiting the application, the service process that consumes resources will be killed after running is blocked, but the background process will be retained. After you enable Don't Keep Background Process, the cached background process will be killed when you exit the application. You can also set to kill background processes within 5-60 minutes after exiting the application.
In obsessive-compulsive disorder settings, the user can also set to automatically block newly installed applications, and can also choose to use [Sleep] instead of [Block], that is, sleep applications like green guards, rather than forcibly stop them.
No Wakeup
Disabling wake-up is a powerful tool to block wake-up between applications. It also requires the support of the Xposed framework. Wake up prohibition can be classified into four ways: CPU wake-up lock, all other wake-up prohibition, synchronization prohibition, and timer alignment.
CPU wake-up lock: Abuse of the CPU wake-up lock usually results in the inability of the device to sleep when the screen is turned off. Google's Android design allows third-party applications to start the CPU wake-up lock when the screen is turned off to maintain the wake-up state. Many rogue applications use this wake-up mechanism to maintain the application running in the background, resulting in the inability of the phone to enter deep sleep normally, which consumes a lot of power in vain.
All other wake-up locks: including Wlan_rx network wake-up lock, PowerManagerService wake-up lock, Alarm wake-up lock, Alarm_rtc wake-up lock, etc., including keeping the device awake and preventing the device from turning off the screen.
Disable synchronization: The synchronization function can also wake up the device, but for some applications that need synchronization, such as synchronizing contacts, photos, and other functions.
Alignment timer: After Android 4.4, the Alarm_rtc wake-up lock can periodically wake up the device. Starting this option can enable optimized applications to trigger wake-up at the same time as possible to reduce power consumption.
Properly set can disable unnecessary wake-up of applications without affecting message push, and reduce power consumption of rogue applications. Users can also customize the blacklist/whitelist that can wake up applications.
The settings are quite simple. Only View System Applications and Enable Automatic Configuration for Newly Installed Applications can be set in advance according to your own needs, and can be configured automatically when installing new applications. Viewing system applications allows users to set the system or Google Apps, but this option requires donation support, and there is a certain risk of prohibiting system app wake-up. Users who are unfamiliar with system applications should also be cautious.
