4G data下待机10小时平均电流53.16mA(不能超过20)

最新推荐文章于 2024-08-13 22:00:10 发布

法迪

最新推荐文章于 2024-08-13 22:00:10 发布

阅读量559

点赞数

分类专栏：功耗异常分析文章标签： android java apache

本文链接：https://blog.csdn.net/su749520/article/details/122442888

版权

功耗异常分析专栏收录该内容

103 篇文章 30 订阅

订阅专栏

本功耗Bug存在2个问题：

1. 呼吸灯功耗优化，目前代码已经提交；

2. 应用自启动管控策略优化；

待机测试中存在被kill 的应用，后台又自启动的现象, 帮忙看下SmartManagerv8.3.3.1.0609.0 是否已经优化

或一起交流下优化策略

具体现象，反馈如下：

一、息屏待机时间段：03-05 09:53:08 至 03-05 19:58:10存在后台又自启动现象：

// 03-05 10:10:29 被SmartManager pid 4810 （com.fadi.onetouchbooster）进行省电查杀

48,377: 03-05 10:10:29.288 1120 1739 I ActivityManager: Force stopping com.ss.android.article.news appid=10170 user=0: from pid 4810 （com.fadi.onetouchbooster）

//但是 03-05 10:38:50 存在后台又自启动的现象，具体如下：

55,355: 03-05 10:38:50.169 1120 1146 I ActivityManager: Start proc 32752:com.ss.android.article.news:push/u0a170 for broadcast com.ss.android.article.news/com.baidu.android.pushservice.RegistrationReceiver

55,440: 03-05 10:38:50.829 1120 1146 I ActivityManager: Start proc 415:com.ss.android.article.news/u0a170 for content provider com.ss.android.article.news/com.ss.android.common.util.MultiProcessSharedProvider

二、息屏待机时间段：03-05 09:53:08 至 03-05 19:58:10存在关联唤醒现象：

// 03-05 10:25:30 被SmartManager pid 4810 （com.fadi.onetouchbooster）进行省电查杀

53,356: 03-05 10:25:30.981 1120 5205 I ActivityManager: Force stopping com.netease.newsreader.activity appid=10165 user=0: from pid 4810 （com.fadi.onetouchbooster）

//但是 03-05 10:38:50 存在后台又自启动的现象，具体如下：

59,921: 03-05 11:27:51.559 1120 1146 I ActivityManager: Start proc 1880:com.netease.newsreader.activity:sync/u0a165 for service com.netease.newsreader.activity/com.netease.nr.biz.account.SyncService

59,968: 03-05 11:27:51.782 1120 1146 I ActivityManager: Start proc 1937:com.netease.newsreader.activity/u0a165 for content provider com.netease.newsreader.activity/com.netease.nr.biz.account.FeedProvider

三、除了上述，查看待机测试中，存在“关键字ActivityManager: Start proc” 32 次被调用

启动的应用:百度地图、淘宝、腾讯视频、今日头条、百度云盘、消消乐、网易新闻、微信

PS：例如推送组件 com.baidu.android.pushservice，会唤醒百度本身和com.ss.android.article.news应用，这里可能需要单独再埋点才可以准确看到链式唤醒的行为

应用的后台运行，会导致呼吸灯被调用，应用本身的行为会触发唤醒锁(关键字PowerManagerService: acquireWakeLockInternal)，导致系统待机中产生台阶电流，个别应用的联网行为（关键字System.out: [socket] connection）导致台阶波形面积变大，总体拉高平均电流

PS：息屏待机时间段：03-05 09:53:08 至 03-05 19:58:10

40,103: 03-05 09:53:08.753 3175 3175 D StandbyModeManager: onReceive action: android.intent.action.SCREEN_OFF

97,775: 03-05 19:58:10.819 3175 3175 D StandbyModeManager: onReceive action: android.intent.action.SCREEN_ON

息屏待机后台应用启动情况

存在被kill 的应用，后台被关联唤醒

一、息屏待机时间段：03-05 09:53:08 至 03-05 19:58:10存在关联唤醒现象：

// 03-05 10:10:29 被SmartManager kill，

48,377: 03-05 10:10:29.288 1120 1739 I ActivityManager: Force stopping com.ss.android.article.news appid=10170 user=0: from pid 4810 （com.fadi.onetouchbooster）

//但是 03-05 10:38:50 存在被关联唤醒的现象，怀疑是 content provider 唤醒导致的启动

二、息屏待机时间段：03-05 09:53:08 至 03-05 19:58:10存在关联唤醒现象：

// 03-05 10:25:30 被SmartManager kill

53,356: 03-05 10:25:30.981 1120 5205 I ActivityManager: Force stopping com.netease.newsreader.activity appid=10165 user=0: from pid 4810 （com.fadi.onetouchbooster）

//但是 03-05 10:38:50 存在被关联唤醒的现象，怀疑是 content provider 唤醒导致的启动

59,921: 03-05 11:27:51.559 1120 1146 I ActivityManager: Start proc 1880:com.netease.newsreader.activity:sync/u0a165 for service com.netease.newsreader.activity/com.netease.nr.biz.account.SyncService

40,301: 03-05 09:53:15.731 1120 1146 I ActivityManager: Start proc 30482:com.baidu.BaiduMap:bdservice_v1/u0a152 for broadcast com.baidu.BaiduMap/com.baidu.android.pushservice.PushServiceReceiver

41,421: 03-05 09:54:16.648 1120 1146 I ActivityManager: Start proc 30613:com.taobao.taobao:channel/u0a168 for broadcast com.taobao.taobao/com.taobao.accs.EventReceiver

41,600: 03-05 09:54:17.264 1120 1146 I ActivityManager: Start proc 30636:com.youku.phone:channel/u0a176 for broadcast com.youku.phone/com.taobao.accs.EventReceiver

41,752: 03-05 09:54:17.708 1120 1146 I ActivityManager: Start proc 30656:com.baidu.netdisk:bdservice_v1/u0a153 for broadcast com.baidu.netdisk/com.baidu.android.pushservice.RegistrationReceiver

41,883: 03-05 09:54:17.835 1120 1146 I ActivityManager: Start proc 30677:com.happyelements.AndroidAnimal:bdservice_v1/u0a175 for broadcast com.happyelements.AndroidAnimal/com.baidu.android.pushservice.RegistrationReceiver

42,003: 03-05 09:54:18.252 1120 1146 I ActivityManager: Start proc 30725:com.android.chrome:sandboxed_process0/u0i14 for webview_service com.netease.newsreader.activity/org.chromium.content.app.SandboxedProcessService0

45,021: 03-05 10:09:34.187 1120 1146 I ActivityManager: Start proc 31324:com.ss.android.article.news:push/u0a170 for service com.ss.android.article.news/com.ss.android.account.AccountSyncService

45,099: 03-05 10:09:35.147 1120 1146 I ActivityManager: Start proc 31359:com.ss.android.article.news/u0a170 for content provider com.ss.android.article.news/com.ss.android.common.util.MultiProcessSharedProvider

45,161: 03-05 10:09:35.535 1120 1146 I ActivityManager: Start proc 31411:com.android.chrome:sandboxed_process0/u0i15 for webview_service com.ss.android.article.news/org.chromium.content.app.SandboxedProcessService0

45,668: 03-05 10:09:36.067 1120 1146 I ActivityManager: Start proc 31475:com.ss.android.article.news:pushservice/u0a170 for service com.ss.android.article.news/com.xiaomi.push.service.XMPushService

48,863: 03-05 10:15:47.138 1120 1146 I ActivityManager: Start proc 31750:com.baidu.netdisk:bdservice_v1/u0a153 for service com.baidu.netdisk/com.baidu.userexperience.UserExperienceService

49,349: 03-05 10:16:46.350 1120 1146 I ActivityManager: Start proc 31813:com.netease.newsreader.activity:sync/u0a165 for service com.netease.newsreader.activity/com.netease.nr.biz.account.SyncService

49,937: 03-05 10:24:35.326 1120 1146 I ActivityManager: Start proc 31982:com.ss.android.article.news:push/u0a170 for service com.ss.android.article.news/com.ss.android.account.AccountSyncService

50,019: 03-05 10:24:35.963 1120 1146 I ActivityManager: Start proc 32022:com.ss.android.article.news/u0a170 for content provider com.ss.android.article.news/com.ss.android.common.util.MultiProcessSharedProvider

50,092: 03-05 10:24:49.340 1120 1146 I ActivityManager: Start proc 32078:com.android.chrome:sandboxed_process0/u0i16 for webview_service com.ss.android.article.news/org.chromium.content.app.SandboxedProcessService0

50,563: 03-05 10:24:49.800 1120 1146 I ActivityManager: Start proc 32142:com.ss.android.article.news:pushservice/u0a170 for service com.ss.android.article.news/com.xiaomi.push.service.XMPushService

54,203: 03-05 10:33:55.913 1120 1146 I ActivityManager: Start proc 32517:com.baidu.BaiduMap:bdservice_v1/u0a152 for broadcast com.baidu.BaiduMap/com.baidu.android.pushservice.PushServiceReceiver

54,757: 03-05 10:38:48.085 1120 1146 I ActivityManager: Start proc 32620:com.taobao.taobao:channel/u0a168 for broadcast com.taobao.taobao/com.taobao.accs.EventReceiver

54,956: 03-05 10:38:48.723 1120 1146 I ActivityManager: Start proc 32644:com.youku.phone:phone_monitor/u0a176 for broadcast com.youku.phone/cn.com.iresearch.phonemonitor.library.receiver.NetWorkChangeReceiver

54,990: 03-05 10:38:48.932 1120 1146 I ActivityManager: Start proc 32660:com.youku.phone:channel/u0a176 for broadcast com.youku.phone/com.taobao.accs.EventReceiver

55,017: 03-05 10:38:49.144 1120 1146 I ActivityManager: Start proc 32675:com.youku.phone/u0a176 for broadcast com.youku.phone/com.taobao.orange.receiver.OrangeReceiver

55,098: 03-05 10:38:49.459 1120 1146 I ActivityManager: Start proc 32694:com.baidu.netdisk:bdservice_v1/u0a153 for broadcast com.baidu.netdisk/com.baidu.android.pushservice.RegistrationReceiver

55,234: 03-05 10:38:49.601 1120 1146 I ActivityManager: Start proc 32713:com.happyelements.AndroidAnimal:bdservice_v1/u0a175 for broadcast com.happyelements.AndroidAnimal/com.baidu.android.pushservice.RegistrationReceiver

55,510: 03-05 10:38:51.229 1120 1146 I ActivityManager: Start proc 575:com.android.chrome:sandboxed_process0/u0i17 for webview_service com.ss.android.article.news/org.chromium.content.app.SandboxedProcessService0

55,991: 03-05 10:38:51.696 1120 1146 I ActivityManager: Start proc 750:com.ss.android.article.news:pushservice/u0a170 for service com.ss.android.article.news/com.xiaomi.push.service.XMPushService

59,921: 03-05 11:27:51.559 1120 1146 I ActivityManager: Start proc 1880:com.netease.newsreader.activity:sync/u0a165 for service com.netease.newsreader.activity/com.netease.nr.biz.account.SyncService

60,014: 03-05 11:27:52.035 1120 1146 I ActivityManager: Start proc 1984:com.netease.newsreader.activity:core/u0a165 for service com.netease.newsreader.activity/com.netease.nimlib.service.NimService

60,097: 03-05 11:27:52.250 1120 1146 I ActivityManager: Start proc 2057:com.netease.newsreader.activity:pushservice/u0a165 for service com.netease.newsreader.activity/com.netease.nr.biz.push.newpush.service.PushGTCoreService

60,212: 03-05 11:27:52.343 1120 1146 I ActivityManager: Start proc 2130:com.netease.pomelo.news.push.messageservice_V1/u0a165 for service com.netease.newsreader.activity/com.netease.pushservice.core.PushServiceNews_V1

63,455: 03-05 11:51:51.223 1120 1146 I ActivityManager: Start proc 2707:com.baidu.netdisk:bdservice_v1/u0a153 for service com.baidu.netdisk/com.baidu.userexperience.UserExperienceService

78,866: 03-05 17:08:43.489 1120 1146 I ActivityManager: Start proc 5555:com.baidu.netdisk:bdservice_v1/u0a153 for service com.baidu.netdisk/com.baidu.userexperience.UserExperienceService

81,338: 03-05 17:08:53.313 1120 1146 I ActivityManager: Start proc 5765:com.facebook.appmanager/u0a138 for broadcast com.facebook.appmanager/com.facebook.oxygen.appmanager.scheduler.SchedulerReceiver

81,398: 03-05 17:08:53.750 1120 1146 I ActivityManager: Start proc 5795:com.android.providers.calendar/u0a65 for broadcast com.android.providers.calendar/.CalendarProviderBroadcastReceiver

82,781: 03-05 17:26:41.515 1120 1146 I ActivityManager: Start proc 6100:com.tencent.mm/u0a174 for broadcast com.tencent.mm/.booter.NotifyReceiver

83,243: 03-05 17:28:23.882 1120 1146 I ActivityManager: Start proc 6331:com.tencent.mm:tools/u0a174 for broadcast com.tencent.mm/.booter.MMReceivers$ToolsProcessReceiver

83,343: 03-05 17:28:25.475 1120 1146 I ActivityManager: Start proc 6406:com.tencent.mm:sandbox/u0a174 for service com.tencent.mm/.service.ProcessService$SandBoxProcessService

83,593: 03-05 17:34:31.602 1120 1146 I ActivityManager: Start proc 6538:com.tencent.mm:sandbox/u0a174 for service com.tencent.mm/.service.ProcessService$SandBoxProcessService

83,849: 03-05 17:37:12.596 1120 1146 I ActivityManager: Start proc 6625:com.baidu.netdisk:bdservice_v1/u0a153 for service com.baidu.netdisk/com.baidu.userexperience.UserExperienceService

84,371: 03-05 17:45:33.407 1120 1146 I ActivityManager: Start proc 6738:com.tencent.mobileqq/u0a166 for content provider com.tencent.mobileqq/com.tencent.mqq.shared_file_accessor.ContentProviderImpl

93,442: 03-05 18:02:22.123 1120 1146 I ActivityManager: Start proc 7352:com.tencent.mm/u0a174 for service com.tencent.mm/.plugin.wepkg.ipc.WepkgMainProcessService

息屏前应用查杀情况

息屏待机时间段：03-05 09:53:08 至 03-05 19:58:10

暗屏期间 SmartManager一共查杀了如下应用com.ss.android.article.news和com.netease.newsreader

48,377: 03-05 10:10:29.288 1120 1739 I ActivityManager: Force stopping com.ss.android.article.news appid=10170 user=0: from pid 4810 （com.fadi.onetouchbooster）

53,356: 03-05 10:25:30.981 1120 5205 I ActivityManager: Force stopping com.netease.newsreader.activity appid=10165 user=0: from pid 4810 （com.fadi.onetouchbooster）

48,377: 03-05 10:10:29.288 1120 1739 I ActivityManager: Force stopping com.ss.android.article.news appid=10170 user=0: from pid 4810

48,405: 03-05 10:10:29.316 1120 1739 I ActivityManager: Force stopping service ServiceRecord{e536239 u0 com.ss.android.article.news/com.taobao.accs.ChannelService}

48,406: 03-05 10:10:29.316 1120 1739 I ActivityManager: Force stopping service ServiceRecord{3ac9121 u0 com.ss.android.article.news/com.xiaomi.push.service.XMPushService}

48,407: 03-05 10:10:29.316 1120 1739 I ActivityManager: Force stopping service ServiceRecord{8826f7a u0 com.ss.android.article.news/com.ss.android.message.NotifyService}

53,317: 03-05 10:25:30.919 1120 5205 I ActivityManager: Force stopping com.ss.android.article.news appid=10170 user=0: from pid 4810

53,343: 03-05 10:25:30.946 1120 5205 I ActivityManager: Force stopping service ServiceRecord{c372783 u0 com.ss.android.article.news/com.taobao.accs.ChannelService}

53,344: 03-05 10:25:30.947 1120 5205 I ActivityManager: Force stopping service ServiceRecord{c9c40f u0 com.ss.android.article.news/com.xiaomi.push.service.XMPushService}

53,345: 03-05 10:25:30.947 1120 5205 I ActivityManager: Force stopping service ServiceRecord{6bbf970 u0 com.ss.android.article.news/com.ss.android.message.NotifyService}

53,346: 03-05 10:25:30.954 1120 9937 I ActivityManager: Force stopping com.ss.android.article.news appid=10170 user=0: from pid 4810

53,356: 03-05 10:25:30.981 1120 5205 I ActivityManager: Force stopping com.netease.newsreader.activity appid=10165 user=0: from pid 4810

53,391: 03-05 10:25:31.025 1120 5205 I ActivityManager: Force stopping service ServiceRecord{84e42b8 u0 com.netease.newsreader.activity/com.netease.nimlib.service.NimService$Aux}

53,392: 03-05 10:25:31.025 1120 5205 I ActivityManager: Force stopping service ServiceRecord{d1b25ea u0 com.netease.newsreader.activity/com.netease.pushservice.core.PushServiceNews_V1}

53,393: 03-05 10:25:31.025 1120 5205 I ActivityManager: Force stopping service ServiceRecord{5a9778d u0 com.netease.newsreader.activity/com.netease.nr.biz.push.newpush.service.PushGTCoreService}

53,394: 03-05 10:25:31.029 1120 7341 I ActivityManager: Force stopping com.netease.newsreader.activity appid=10165 user=0: from pid 4810