Preface

 

I. Common methods of life preservation

1. Monitoring Broadcasting Mode

2. Improving Service Priority

3. Double service pull up

3. Two-process pull-up

II. Multiprocess Audio Preservation Scheme

To sum up, the above method only improves the ability of the backstage operation of APP. In the case that users do not actively clean up or kill, it is still very good to test the survival effect of APP. But Gu Du magically survived by clicking on a button to clean up, because it played a silent music loop in the background. As follows:

The code is as follows:

public class PlayerMusicService extends Service {
    private final static String TAG = "PlayerMusicService";
    private MediaPlayer mMediaPlayer;
    @Nullable
    @Override
    public IBinder onBind(Intent intent) {
        return null;
    }
    @Override
    public void onCreate() {
        super.onCreate();
        mMediaPlayer = MediaPlayer.create(getApplicationContext(), R.raw.silent);
        mMediaPlayer.setLooping(true);
    }
    @Override
    public int onStartCommand(Intent intent, int flags, int startId) {
        new Thread(new Runnable() {
            @Override
            public void run() {
                startPlayMusic();
            }
        }).start();
        return START_STICKY;//note 1
    }
    private void startPlayMusic(){
        if(mMediaPlayer != null){
            mMediaPlayer.start();
        }
    }
    private void stopPlayMusic(){
        if(mMediaPlayer != null){
            mMediaPlayer.stop();
        }
    }
    @Override
    public void onDestroy() {
        super.onDestroy();
        stopPlayMusic();
        // Note 2
        Intent intent = new Intent(getApplicationContext(),PlayerMusicService.class);
        startService(intent);
    }
}

AndroidManifest.xml

<service android:name=".service.PlayerMusicService"
          android:enabled="true"
          android:exported="true"
          android:process=":music_service"/>//Multiprocess

Open the background broadcast audio service, the program in each model test as follows:
1. Huawei Mate8(7.0), one-click cleanup still survives, surviving more than 12 hours in the background black screen mode; but if the user only chooses to clean up the application, it will also be killed, which is consistent with the "Gudong" survival effect.
2. Samsung C9(6.0), a key to clean up the latest applications, the successful survival;
3. Hua4X (6.0): Clean up the latest application with one key and survive successfully.
4. Samsung Note4(5.0): Clean up the latest application with one button and survive successfully.

 

III. Through the Job Scheduler Scheme

Summary

principle

New class: AliveJobService.java

@TargetApi(21)
public class AliveJobService extends JobService {
    private static final int MESSAGE_ID_TASK = 0x01;
    // Inform the compiler that this variable cannot be optimized
    private volatile static Service mKeepAliveService = null;
    public static boolean isJobServiceAlive(){
        return mKeepAliveService != null;
    }
    private Handler mHandler = new Handler(new Handler.Callback() {
        @Override
        public boolean handleMessage(Message msg) {
            if(SystemUtils.isAPPALive(getApplicationContext(), Contants.PACKAGE_NAME)){
                //APP Lives
            }else{
                Intent intent = new Intent(getApplicationContext(), SportsActivity.class);
                intent.setFlags(Intent.FLAG_ACTIVITY_NEW_TASK);
                startActivity(intent);
                //APP was killed and restarted
            }
            jobFinished( (JobParameters) msg.obj, false ); // Notify the end of system task execution
            return true;
        }
    });
    @Override
    public boolean onStartJob(JobParameters params) {
        mKeepAliveService = this;
        Message msg = Message.obtain(mHandler, MESSAGE_ID_TASK, params);
        mHandler.sendMessage(msg);
        // Returning false, the system assumes that the task has been completed by the time the method returns.
        // Returning true, the system assumes that the task is about to be performed
        return true;
    }
    @Override
    public boolean onStopJob(JobParameters params) {
        mHandler.removeMessages(MESSAGE_ID_TASK);
        return false;
    }
}
 

JobScheduler management class performs system tasks: JobScheduler Manager. Java

public class JobSchedulerManager {
    private static final int JOB_ID = 1;
    private static JobSchedulerManager mJobManager;
    private JobScheduler mJobScheduler;
    private static Context mContext;
 
    private JobSchedulerManager(Context ctxt){
        this.mContext = ctxt;
        mJobScheduler = (JobScheduler)ctxt.getSystemService(Context.JOB_SCHEDULER_SERVICE);
    }
    public final static JobSchedulerManager getJobSchedulerInstance(Context ctxt){
        if(mJobManager == null){
            mJobManager = new JobSchedulerManager(ctxt);
        }
        return mJobManager;
    }
    @TargetApi(21)
    public void startJobScheduler(){
        if(AliveJobService.isJobServiceAlive() || isBelowLOLLIPOP()){
            return;        // If JobService has been started or API < 21, return
        }
        JobInfo.Builder builder = new JobInfo.Builder(JOB_ID,new ComponentName(mContext, AliveJobService.class));
        builder.setPeriodic(3000); // Set up to perform tasks every 3 seconds
        builder.setPersisted(true);  // When setting up the device to restart, perform the task
        builder.setRequiresCharging(true); // When the charger is inserted, perform the task
        JobInfo info = builder.build();
        mJobScheduler.schedule(info);  
    }
    @TargetApi(21)
    public void stopJobScheduler(){
        if(isBelowLOLLIPOP())
            return;
        mJobScheduler.cancelAll();
    }
    private boolean isBelowLOLLIPOP(){
        return Build.VERSION.SDK_INT < Build.VERSION_CODES.LOLLIPOP; // API< 21
    }
}

Remember to add permissions: android:permission="android.permission.BIND_JOB_SERVICE"

Doze sleep pattern

test result
Samsung C9(6.0): One-click cleaning and force stop can wake up APP;
Samsung Note4(5.0): One-click cleaning and force stop can wake up APP;
Huawei Glory 4X(6.0): One click of clean-up and force stop can wake up APP;
Huawei Mate8(7.0): Failure (possibly shielded by Huawei);

IV. Huawei Pushes SDK

MyHwPushReceiver.java

public class MyHwPushReceiver extends PushEventReceiver{
    private final static String TAG = "MyHwPushReceiver";
    @Override
    public void onToken(Context context, String token, Bundle bundle) {
        Log.i(TAG,"Connect to Huawei push server. token="+token);
    }
    @Override
    public boolean onPushMsg(Context context, byte[] msgBytes, Bundle bundle) {
        Log.i(TAG,"Receive through message:"+new String(msgBytes,"UTF-8"));
        // Start the application
        return false;
    }
    @Override
    public void onPushState(Context context, boolean connectState) {
        Log.i(TAG,"Connect to Huawei Push Server:"+(connectState?"connected":"disconnected"));
    }

    @Override
    public void onEvent(Context context, Event event, Bundle bundle) { 
        //Click to open the notification bar
        super.onEvent(context, event, bundle);
    }
}

HwPushManager.java

 public class HwPushManager {
    private static HwPushManager mPushManager;
    private Context mContext; 
    private HwPushManager(Context mContext){
        this.mContext = mContext;
    }
    public static  HwPushManager getInstance(Context mContext){
        if(mPushManager == null){
            mPushManager = new HwPushManager(mContext);
        }
        return mPushManager;
    }
    public void startRequestToken(){
        //Request Token from the server
        PushManager.requestToken(mContext);
    }
        //Whether to receive the passing message from the server
    public void isEnableReceiveNormalMsg(boolean isEnable){
        PushManager.enableReceiveNormalMsg(mContext,isEnable);
    }
        //Whether to receive self-rendering messages
    public  void isEnableReceiverNotifyMsg(boolean isEnable){
        PushManager.enableReceiveNotifyMsg(mContext,isEnable);
    }
}

 AndroidManifest.xml

    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
    <uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
    <uses-permission android:name="android.permission.READ_PHONE_STATE" />
    <uses-permission android:name="android.permission.WAKE_LOCK" />
  <!-- Third Party Relevance :Receive Push Messages (registration, Push News, Push Connection status, label, LBS Reporting Results) Broadcasting -->
        <receiver android:name=".receiver.MyHwPushReceiver" >
            <intent-filter>
                <action android:name="com.huawei.android.push.intent.REGISTRATION" />
                <action android:name="com.huawei.android.push.intent.RECEIVE" />
                <action android:name="com.huawei.android.push.intent.CLICK" />
                <action android:name="com.huawei.intent.action.PUSH_STATE" />
                <action android:name="com.huawei.android.push.plugin.RESPONSE" />
            </intent-filter>
            <meta-data android:name="CS_cloud_ablitity" android:value="@string/hwpush_ability_value"/>
        </receiver>
        <!-- PushSDK:PushSDK Receiving External Request Event Entry -->
        <receiver
            android:name="com.huawei.android.pushagent.PushEventReceiver"
            android:process=":pushservice" >
            <intent-filter>
             <action android:name="com.huawei.android.push.intent.REFRESH_PUSH_CHANNEL" />
                <action android:name="com.huawei.intent.action.PUSH" />
                <action android:name="com.huawei.intent.action.PUSH_ON" />
                <action android:name="com.huawei.android.push.PLUGIN" />
            </intent-filter>
            <intent-filter>
                <action android:name="android.intent.action.PACKAGE_ADDED" />
                <action android:name="android.intent.action.PACKAGE_REMOVED" />
                <data android:scheme="package" />
            </intent-filter>
        </receiver>
        <receiver
            android:name="com.huawei.android.pushagent.PushBootReceiver"
            android:process=":pushservice" >
            <intent-filter>
                <action android:name="com.huawei.android.push.intent.REGISTER" />
                <action android:name="android.net.conn.CONNECTIVITY_CHANGE" />
            </intent-filter>
            <meta-data
                android:name="CS_cloud_version"
                android:value="\u0032\u0037\u0030\u0035" />
        </receiver>
        <!-- PushSDK:Push service -->
        <service
            android:name="com.huawei.android.pushagent.PushService"
            android:process=":pushservice" >
        </service>
        <!-- locale|layoutDirection Do not recreate after switching languages activity -->
        <activity
            android:name="com.huawei.android.pushselfshow.richpush.RichPushActivity"
            android:process=":pushservice"
            android:theme="@style/hwpush_NoActionBar"
            android:configChanges="orientation|screenSize|locale|layoutDirection"
            android:screenOrientation="portrait">
            <meta-data android:name="hwc-theme"
                android:value="androidhwext:style/Theme.Emui"/>
            <intent-filter>
                <action android:name="com.huawei.android.push.intent.RICHPUSH" />
                <category android:name="android.intent.category.DEFAULT" />
            </intent-filter>
        </activity>
        <activity
       android:name="com.huawei.android.pushselfshow.permission.RequestPermissionsActivity"
            android:theme="@android:style/Theme.DeviceDefault.Light.Dialog.NoActionBar"
            android:launchMode="singleTop"
            android:screenOrientation="portrait"
            android:configChanges="orientation|screenSize|locale|layoutDirection"
            android:exported="false">
        </activity>

test result

 

Reference link:

https://blog.csdn.net/andrexpert/article/details/75174586

https://blog.csdn.net/andrexpert/article/details/75045678