移动应用
443
需要APP暗屏情况下进行后台执行一些任务,但是google现在为了优化手机的体验,以及流畅性,做了很多的限制,电量优化,休眠模式,以及进入深度睡眠状态,进入深入休眠状态系统会根据黑白名单的应用进行管理,杀掉非白名单的后台进程以及网络请求;Android系统的优化是守护后台进程造成了很大困扰,线程之间守护已经是不在可靠,使用wakelock耗电过大也会是系统杀掉应用进程。下面就对我们的经历说说守护进程的。
1,从官网上可以看出google为了系统更加流畅以及优化内存,Google做了很大的处理,在手机暗屏或者睡眠状态就停止后台运行;若要保持service的常驻,需要做一些前端的活动,Notification重要属性:notification.flags = Notification.FLAG_NO_CLEAR|Notification.FLAG_ONGOING_EVENT;然后startForeground(setClass().hashCode(), notification);使得服务能挂在通知栏。
2,通过wakelock占用CPU,若一直占用CPU的话,当然这是比较耗电的,要是耗电太高的话系统会直接回收,杀死程序进程。
我是使用定时器唤醒cpu 后台服务将接收到定时任务执行未完成的任务:下面是我实现的代码
在mainfest中注册
关键代码定时任务:
publicvoidstartAlarm(Context context){ Intent intent =newIntent(context, WakeCPUAlarmReceiver.class); alarmIntent = PendingIntent.getBroadcast(context,0, intent,0); alarmMgr = (AlarmManager) context .getSystemService(Context.ALARM_SERVICE);// alarmMgr.set(AlarmManager.ELAPSED_REALTIME_WAKEUP,// 1000, alarmIntent); if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) { alarmMgr.setExactAndAllowWhileIdle( AlarmManager.ELAPSED_REALTIME_WAKEUP, SystemClock.elapsedRealtime() + chekcTime, alarmIntent); }else if(Build.VERSION.SDK_INT >= Build.VERSION_CODES.KITKAT) { alarmMgr.setExact(AlarmManager.ELAPSED_REALTIME_WAKEUP, SystemClock.elapsedRealtime() + chekcTime, alarmIntent); }else{ alarmMgr.set(AlarmManager.ELAPSED_REALTIME_WAKEUP, SystemClock.elapsedRealtime() + chekcTime, alarmIntent); } FileLogUtil.e(TAG ,"startAlarm 设置定时任务"); }
接收到定时任务:
publicclassWakeCPUAlarmReceiverextendsWakefulBroadcastReceiver{ privateAlarmManageralarmMgr; privatePendingIntentalarmIntent; privatefinallong chekcTime =30*1000; public static boolean isCheckFlag =false; privatestaticStringTAG=WakeCPUAlarmReceiver.class.getSimpleName(); @Override public void onReceive(Contextcontext,Intentintent) { // TODO Auto-generated method stub Intentservice =newIntent(context,WakecpuIntentService.class); FileLogUtil.e(TAG,"onReceive 接收定时任务"); startWakefulService(context, service); }
在service中执行需要执行的任务:
public class WakecpuIntentService extends IntentService{ private static String TAG=WakecpuIntentService.class.getSimpleName() +" :"; private NotificationManager mNotificationManager; private PowerManager.WakeLockwl; NotificationCompat.Builderbuilder; public WakecpuIntentService() { super("WakecpuIntentService"); // TODO Auto-generated constructor stub } @Override protected void onHandleIntent(Intentintent) { // TODO Auto-generated method stubBundle extras = intent.getExtras(); FileLogUtil.e(TAG,"Service接收到WakeLock定时任务。"); PollService.startService(getApplicationContext()); FileLogUtil.e(TAG,"Service接收到WakeLock定时任务在定时任务中启动轮询Service。"); // Do the work that requires your app to keep the CPU running. // Release the wake lock provided by the WakefulBroadcastReceiver. //checkScreenOff(); WakeCPUAlarmReceiver.completeWakefulIntent(intent);//释放wake WakeCPUAlarmReceiver.setCheckFlag(false); WakeCPUAlarmReceivermAlarmReceiver =newWakeCPUAlarmReceiver(); mAlarmReceiver.startAlarm(WakecpuIntentService.this); FileLogUtil.e(TAG,"Service释放wakelock后设置定时任务。"); } }
service在后台也能够打印log 保持一直执行,最重要的是不耗电也不会卡机的问题。欢迎大家一起讨论学习。 关注公众号获取更多干货