android service 防杀_防止Android服务被操作系统杀死

bd96500e110b49cbb3cd949968f18be7.png

I have created a service that is returning START_STICKY at the onStartCommand. However, after sometime, I notice that my app has been killed by the OS.

Is there any method/piece of code that I can use to prevent the app from being killed by the OS? I know this may not fall under the best practices.

Or is there some other method that we can use like repeatedly check if the app is running, and to start the app if it is not?

Your insight on this is very much appreciated.

Cheers

解决方案

You cannot prevent your process from being killed. If OS decide to kill your processes you will be killed. Period.

The START_STICKY will not do any magic os other answer incorrectly tells - docs about that value say:

If this service's process is killed while it is started (after

returning from onStartCommand(Intent, int, int)), then leave it in the

started state but don't retain this delivered intent. Later the system

will try to re-create the service. Because it is in the started state,

it will guarantee to call onStartCommand(Intent, int, int) after

creating the new service instance; if there are not any pending start

commands to be delivered to the service, it will be called with a null

intent object, so you must take care to check for this.

  • 0
    点赞
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论

“相关推荐”对你有帮助么?

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值