Android power consumption (12) — power saving and endurance mutual wake up

Time:2021-3-21

Power saving and endurance – wake up to each other

Description of mutual arousal

After installing 100 apps, I accidentally opened a wake-up app. After a while, the background secretly started 30-40 apps.

Mutual awakening app

01 Baidu app family:

This is a very interesting “gourd baby” phenomenon. Take a chestnut as an example, you accidentally click on any of the above family applications, and the phone lights up and unlocks. At this time, the gourd baby is opened,

He will immediately wake up all the gourd babies in the family, “everyone, start up backstage quickly. We will send messages and advertise in the notice column later.”.

You can check the “running application list” in the settings, and you will find that many applications have started.

The harm of mutual Awakening

01 if all apps in the family are started at the same time, the system will be stuck for a short time due to too many background starts;
Every day is a small case

Start mode of mutual wake up

Method 1:

System broadcast (power on, unlock) - > start push service, that is, SDK technology that the third-party app will never be killed > > after all the family apps registered with the same push service are executed

Method 2:

Start pushservice regularly through alammanagerservice - > start all family apps registered with the same push service in the background;

Method 3:

Content provide reads data and starts app - > starts push service, that is, SDK technology that the third-party app will never be killed;

Mode 4:

Start app under disguise of activity or foreground process > start push service, that is, SDK technology that third party app will never be killed

The family app is started in the background;

The above similarities lie in the fact that the push SDK technology completes the mutual wake-up operation. The main reason is that the official Google itself is blocked, and the brand manufacturers have to castrate the Google service. As a result, they can’t manage the push messages uniformly like IOS. As a result, the domestic application market environment tends to be profitable, and blindly push their own advertising messages to non users in the background according to their own interests Gu’s users.

resolvent:

1. Self start Management: restrict the back-end self start behavior of the application when it is turned on; PS: after years of wisdom and courage between mobile phone manufacturers and rogue applications, the self start management of brand mobile phones on the market can well restrict the self start of programs. Of course, the previous method of purely disabling the boot broadcast component has awakened rogue applications to each other

Of course, there are solutions. After all, the road is higher than the devil, and we all make progress with each other.

2. Background cleaning: it mainly uses the app dormancy technology to prevent the background startup and mutual wake-up of the application. The technical implementation here is also very clever;

3. Notification management: the application that does not want to appear advertising information in the notification column will be screened and displayed. Here, the message display function of rogue application is mainly disabled through permission management;

4. Android settings – > WLAN – > click the menu key to select advanced – > the drop-down list of keeping WLAN connection in sleep state {always, only when charging, never (will increase data flow)}. If it is not set to always, then after we lock the screen and sleep, the program will be in no network state, and the corresponding app users will always be in offline mode, which not only saves power, but also further limits the application interaction Awake behavior;

The above similarities lie in the fact that the push SDK technology completes the mutual wake-up operation. The main reason is that the official Google itself is blocked, and the brand manufacturers have to castrate the Google service. As a result, they can’t manage the push messages uniformly like IOS. As a result, the domestic application market environment tends to be profitable, and blindly push their own advertising messages to non users in the background according to their own interests Gu’s users.

resolvent:

1. Self start Management: restrict the back-end self start behavior of the application when it is turned on; PS: after years of wisdom and courage between mobile phone manufacturers and rogue applications, the self start management of brand mobile phones on the market can well restrict the self start of programs. Of course, the previous method of purely disabling the boot broadcast component has awakened rogue applications to each other

2. Background cleaning: it mainly uses the app dormancy technology to prevent the background startup and mutual wake-up of the application. The technical implementation here is also very clever;

3. Notification management: the application that does not want to appear advertising information in the notification column will be screened and displayed. Here, the message display function of rogue application is mainly disabled through permission management;

4. Android settings – > WLAN – > click the menu key to select advanced – > the drop-down list of keeping WLAN connection in sleep state {always, only when charging, never (will increase data flow)}. If the setting is not always, then after we lock the screen and sleep, the program will be in no network state, and the corresponding app users will be in no network state all the time

Offline mode can not only save power, but also further limit the mutual wake-up behavior of applications;