-
Notifications
You must be signed in to change notification settings - Fork 776
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
2019-07-16:Service如何进行保活? #98
Comments
保活不了,死球了 |
做保活的都死球了,比如我 |
评论我笑出猪叫 百度了下 思路无非是两种 |
利用系统广播拉活 |
|
1.设置Service优先级,setForground(true) |
第二种保证不了系统回收 |
诱导用户添加白名单 |
保活基本实现不了了,pass |
现在系统只要一键清理掉应用 服务也会被清掉而且无法自启动 除非加入白名单 |
1:跟各大系统厂商建立合作关系,把App加入系统内存清理的白名单 2:白色保活 用startForeground()启动前台服务,这是官方提供的后台保活方式,不足的就是通知栏会常驻一条通知,像360的状态栏。 3:灰色保活 开启前台Service,开启另一个Service将通知栏移除,其oom_adj值还是没变的,这样用户就察觉不到app在后台保活。 4:黑色保活 1 像素activity保活方案,监听息屏事件,在息屏时启动个一像素的activity,提升自身优先级; 1)、用startForeground()启动前台服务 前台Service,使用startForeground这个Service尽量要轻,不要占用过多的系统资源,否则系统在资源紧张时,照样会将其杀死。 DaemonService.java 可以参考下面的 |
No description provided.
The text was updated successfully, but these errors were encountered: