为什么是 foreground ? 默认启动的 Service 是被标记为 background,当前运行的 Activity 一般被标记为 foreground,也就是说你给 Service 设置了 foreground 那么他就和正在运行的 Activity 类似优先级得到了一定的提高。当让这并不能保证你得 Service 永远不被杀掉,只是提高了他的优先级。
有一个方法可以给你更清晰的演示,进入 $SDK/tools 运行命令
复制内容到剪贴板
代码:
# adb shell dumpsys activity|grep oom_adj
Running Norm Proc # 6: oom_adj= 0 ProcessRecord{43635cf0 12689:com.roiding.netraffic/10028}
Running Norm Proc # 5: oom_adj= 7 ProcessRecord{436feda0 12729:com.android.browser/10006}
Running Norm Proc # 4: oom_adj= 8 ProcessRecord{4367e838 12761:android.process.acore/10016}
Running Norm Proc # 3: oom_adj= 8 ProcessRecord{43691cd8 12754:com.google.process.gapps/10000}
Running PERS Proc # 1: oom_adj=-12 ProcessRecord{43506750 5941:com.android.phone/1001}
Running PERS Proc # 0: oom_adj=-100 ProcessRecord{4348fde0 5908:system/1000}
返 回的一大堆东西,观察 oom_adj 的值,如果是大于 8 一般就是属于 backgroud 随时可能被干掉,数值越小证明优先级越高,被干掉的时间越晚。你看phone的程序是 -12 说明电话就是电话,其他什么都干了了,也的能接电话对吧。另外还有一个 -100 的,更邪乎因为是 system 如果他也完蛋了,你得系统也就挂了。
在miui中,对LMK进行了改造,如果直接输入上述命令,打印不出任何信息,所以直接输入adb shell dumpsys activity,然后再输出信息中找running process一段,如下所示。MIUI已将数字表示的oom_adj转换成了字符串形式,如vis, core, sys, bak, svc等。如果是第三方开发的程序,最高级别只能到svc(started service)
Running processes (most recent first):
Proc # 0: adj=bak /B 40692a78 330:com.android.bluetooth/10002 (started-bg-services)
Proc # 1: adj=vis /F 40b161c8 250:com.google.process.gapps/10016 (service)
com.google.android.location/.NetworkLocationService<=Proc{40a10520 130:system/1000}
Proc # 2: adj=fore /F 40b67408 251:android.process.acore/10000 (provider)
com.android.providers.contacts/.ContactsProvider2<=Proc{40b02b98 215:com.android.phone/1001}
PERS # 3: adj=core /F 40b02b98 215:com.android.phone/1001 (fixed)
Proc # 4: adj=vis /F 40aeea30 308:com.iflytek.inputmethod/10049 (service)
com.iflytek.inputmethod/.FlyIME<=Proc{40a10520 130:system/1000}
PERS # 5: adj=sys /F 40a10520 130:system/1000 (fixed)
Proc # 6: adj=fore /F 40b42348 223:com.android.launcher/10020 (top-activity)
PERS # 7: adj=core /F 40ab02c0 197:com.android.systemui/1000 (fixed)
Proc # 8: adj=svc /B 40c3dc48 774:com.tencent.mm:push/10041 (started-services)
Proc # 9: adj=bak /B 40bd0c98 957:com.qihoo360.mobilesafe/10048 (bg-empty)
Proc #10: adj=bak+1/B 40a58fd8 949:com.moji.mjweather/10047 (bg-empty)
Proc #11: adj=svc /B 40af5480 552:com.snda.wifilocating/10071 (started-services)
Proc #12: adj=fore /F 406c0060 478:com.android.mms/10025 (user-specified-apps)
Proc #13: adj=bak+1/B 40ceabf8 783:com.ijinshan.kbatterydoctor/10067 (bg-empty)
Proc #14: adj=bak+2/B 40e3f970 3054:com.android.gallery/10014 (bg-empty)
Proc #15: adj=bak+2/B 40eeaf50 3089:com.miui.uac/10032 (bg-empty)
Proc #16: adj=svc /B 40e783b0 3071:com.sds.android.process.ttpod.support/10045 (started-services)
Proc #17: adj=bak+3/B 40e51cc8 3063:com.sds.android.process.ttpod/10045 (bg-empty)
Proc #18: adj=bak+3/B 40ef9570 2554:android.process.media/10011 (bg-empty)
Proc #19: adj=svc /B 40e006c8 2472:com.mobinweaver.game.defense/10076 (started-services)
Proc #20: adj=bak+4/B 40dfe9f0 2592:com.sina.weibo/10068 (bg-empty)
Proc #21: adj=bak+4/B 40ef7018 2583:com.renren.mobile.android/10073 (bg-empty)
Proc #22: adj=bak+5/B 40edc878 2574:com.android.updater/1030 (bg-empty)
Proc #23: adj=bak+5/B 40e7bec8 2564:com.google.android.gm/10015 (bg-empty)
Proc #24: adj=bak+6/B 40ea9768 2546:com.miui.backup/10001 (bg-empty)
Proc #25: adj=bak+6/B 40df3bf8 2745:net.cactii.flash2/10034 (bg-empty)
Proc #26: adj=bak+7/B 40a9b6a8 2762:qsbk.app/10054 (started-bg-services)
Proc #27: adj=svc /B 40bbc290 405:factory.widgets.ThreeDDigitalWeatherClock/10066 (started-services)