待机异常尿崩求屌大的大神帮看下吧持续几个月了证据齐全_BUG反馈_MIUI论坛 -
Powered by Discuz! Archiver
待机异常尿崩求屌大的大神帮看下吧持续几个月了证据齐全
具体如下：
Statistics since last charge:
System starts: 0, currently on battery: true
Time on battery: 9h 16m 5s 796ms (100.0%) realtime, 1h 34m 1s 606ms (16.9%) uptime
Time on battery screen off: 8h 19m 24s 335ms (89.8%) realtime, 37m 20s 143ms (6.7%) uptime
Total run time: 9h 16m 5s 763ms realtime, 1h 34m 1s 573ms uptime
Battery time remaining: 3d 5h 31m 35s 812ms
Start clock time: -06-03-00
Screen on: 56m 41s 461ms (10.2%) 19x, Interactive: 56m 38s 876ms (10.2%)
Screen brightnesses:
& & dark 1m 7s 572ms (2.0%)
& & dim 20m 7s 400ms (35.5%)
& & medium 35m 26s 489ms (62.5%)
Total full wakelock time: 1m 5s 408ms
Total partial wakelock time: 7m 4s 358ms
Mobile total received: 0B, sent: 0B (packets received 0, sent 0)
Phone signal levels:
& & great 15s 87ms (0.0%) 5x
& & excellent 9h 15m 50s 709ms (100.0%) 5x
Signal scanning time: 0ms
Radio types:
& & none 9h 16m 5s 796ms (100.0%) 0x
Mobile radio active time: 0ms (0.0%) 0x
Wi-Fi total received: 76.45MB, sent: 8.94MB (packets received 70452, sent 120167)
Wifi on: 9h 16m 5s 796ms (100.0%), Wifi running: 9h 16m 5s 796ms (100.0%)
Wifi states: (no activity)
Wifi supplicant states:
& & completed 9h 16m 5s 796ms (100.0%) 0x
Wifi signal levels:
& & level(2) 6s 37ms (0.0%) 2x
& & level(3) 37m 2s 895ms (6.7%) 33x
& & level(4) 8h 38m 56s 864ms (93.3%) 32x
WiFi Idle time: 0ms (--%)
WiFi Rx time:& &0ms (--%)
WiFi Tx time:& &0ms (--%)
WiFi Power drain: 0mAh
Bluetooth Idle time: 0ms (--%)
Bluetooth Rx time:& &0ms (--%)
Bluetooth Tx time:& &0ms (--%)
Bluetooth Power drain: 0mAh
Device battery use since last full charge
& & Amount discharged (lower bound): 10
& & Amount discharged (upper bound): 11
& & Amount discharged while screen on: 7
& & Amount discharged while screen off: 4
这是唤醒：
All kernel wake locks:
Kernel Wake lock alarmtimer: 10m 16s 437ms (309 times) realtime
Kernel Wake lock PowerManagerService.WakeLocks: 7m 3s 55ms (1308 times) realtime
Kernel Wake lock fpc_ttw_wl: 4m 25s 987ms (18 times) realtime
Kernel Wake lock & &: 4m 9s 439ms (7121 times) realtime
Kernel Wake lock qcom_rx_wakelock: 2m 28s 254ms (3023 times) realtime
Kernel Wake lock NETLINK& &: 1m 23s 371ms (7983 times) realtime
Kernel Wake lock wlan& && &: 55s 191ms (76 times) realtime
Kernel Wake lock PowerManagerService.Broadcasts: 16s 156ms (37 times) realtime
Kernel Wake lock PowerManagerService.Display: 6s 78ms (19 times) realtime
Kernel Wake lock radio-interface: 2s 613ms (13 times) realtime
Kernel Wake lock qcril& && & : 901ms (66 times) realtime
Kernel Wake lock sensor_ind: 800ms (27 times) realtime
Kernel Wake lock ipc0000004c_rild: 644ms (101 times) realtime
Kernel Wake lock qpnp_fg_memaccess: 560ms (931 times) realtime
Kernel Wake lock event0& && &: 433ms (7 times) realtime
Kernel Wake lock qpnp_fg_update_sram: 376ms (76 times) realtime
Kernel Wake lock SensorService_wakelock: 298ms (24 times) realtime
Kernel Wake lock KeyEvents& &: 288ms (77 times) realtime
Kernel Wake lock ipc_rild: 224ms (6 times) realtime
Kernel Wake lock qpnp_fg_update_temp: 181ms (223 times) realtime
Kernel Wake lock ipc000000bd_sensors.qcom: 85ms (51 times) realtime
Kernel Wake lock eventpoll& &: 82ms (13196 times) realtime
Kernel Wake lock ipc0000004f_rild: 73ms (2 times) realtime
Kernel Wake lock qpnp_fg_gain_comp: 41ms (5 times) realtime
Kernel Wake lock ipc000000ce_sensors.qcom: 31ms (226 times) realtime
Kernel Wake lock ipc0000005e_rild: 23ms (104 times) realtime
Kernel Wake lock battery& &: 21ms (5 times) realtime
Kernel Wake lock HVDCPD_WL& &: 15ms (5 times) realtime
Kernel Wake lock modem_IPCRTR: 14ms (351 times) realtime
Kernel Wake lock ipc0000004a_rild: 5ms (19 times) realtime
Kernel Wake lock ipc0000005f_rild: 4ms (19 times) realtime
Kernel Wake lock qpnp-rtc-ffffffc078dad800: 4ms (9 times) realtime
Kernel Wake lock ipc000000cc_FLP Service Cal: 3ms (31 times) realtime
Kernel Wake lock bms& && && &: 3ms (5 times) realtime
Kernel Wake lock ipc_rild: 3ms (19 times) realtime
Kernel Wake lock adsp_IPCRTR : 3ms (66 times) realtime
Kernel Wake lock ipc_rild: 3ms (20 times) realtime
Kernel Wake lock ipc_rild: 1ms (15 times) realtime
Kernel Wake lock ipc_time_daemon: 1ms (2 times) realtime
Kernel Wake lock binder& && &: 1ms (2 times) realtime
Kernel Wake lock ipc_sensors.qcom: 1ms (2 times) realtime
All partial wake locks:
Wake lock u0a111 WakerLock:m 29s 761ms (213 times) realtime
Wake lock u0a111 WakerLock:m 10s 732ms (437 times) realtime
Wake lock u0a111 WakerLock:: 1m 7s 239ms (216 times) realtime
Wake lock u0a111 WakerLock:s 601ms (177 times) realtime
Wake lock u0a111 WakerLock:: 23s 65ms (101 times) realtime
Wake lock 1000 *alarm*: 23s 46ms (515 times) realtime
Wake lock 1013 AudioMix: 19s 146ms (14 times) realtime
Wake lock u0a111 WakerLock:: 18s 101ms (64 times) realtime
Wake lock u0a111 *alarm*: 14s 702ms (109 times) realtime
Wake lock u0a22 MMS PushReceiver: 9s 878ms (2 times) realtime
Wake lock u0a150 *alarm*: 7s 706ms (488 times) realtime
Wake lock 1000 show keyguard: 6s 911ms (10 times) realtime
Wake lock 1001 yy.nmob.voip.serviceStart: 6s 158ms (101 times) realtime
Wake lock u0a111 WakerLock:: 5s 570ms (32 times) realtime
Wake lock u0a40 *sync*/sms/com.xiaomi/: 5s 37ms (4 times) realtime
Wake lock u0a22 StartingAlertService: 3s 750ms (5 times) realtime
Wake lock u0a2 *alarm*: 3s 9ms (1 times) realtime
Wake lock 1000 com.miui.bugreport.service.BugreportGenerateService: 2s 219ms (1 times) realtime
Wake lock u0a29 *alarm*: 2s 52ms (19 times) realtime
Wake lock u0a115 *alarm*: 1s 989ms (77 times) realtime
Wake lock 1001 GsmInboundSmsHandler: 1s 934ms (4 times) realtime
Wake lock 1000 AudioMix: 1s 907ms (8 times) realtime
Wake lock 1001 RILJ: 1s 618ms (138 times) realtime
Wake lock u0a76 *alarm*: 1s 385ms (101 times) realtime
Wake lock 1000 RingtonePlayer: 1s 244ms (14 times) realtime
Wake lock u0a47 *alarm*: 1s 127ms (1 times) realtime
Wake lock u0a41 AlarmClock: 940ms (2 times) realtime
Wake lock 1000 WifiSuspend: 624ms (19 times) realtime
Wake lock 1000 SyncLoopWakeLock: 618ms (26 times) realtime
Wake lock u0a22 *vibrator*: 618ms (2 times) realtime
Wake lock 1001 *alarm*: 611ms (81 times) realtime
Wake lock 1000 NetworkStats: 598ms (16 times) realtime
Wake lock u0a41 *vibrator*: 580ms (1 times) realtime
Wake lock u0a76 *vibrator*: 510ms (2 times) realtime
Wake lock u0a41 *alarm*: 507ms (1 times) realtime
Wake lock 1000 ActivityManager-Sleep: 482ms (10 times) realtime
Wake lock u0a156 *alarm*: 461ms (10 times) realtime
Wake lock u0a9 StartingAlertService: 378ms (2 times) realtime
Wake lock u0a111 WakerLock:: 376ms (2 times) realtime
Wake lock u0a102 *alarm*: 343ms (34 times) realtime
Wake lock 1000 *vibrator*: 190ms (8 times) realtime
Wake lock 1000 SyncManagerHandleSyncAlarm: 144ms (8 times) realtime
Wake lock 1001 QcrilMsgTunnelSocket: 124ms (9 times) realtime
Wake lock u0a2 ScheduleNextAlarmWakeLock: 97ms (1 times) realtime
Wake lock 1001 ServiceStateTracker: 82ms (9 times) realtime
Wake lock 1000 LocationManagerService: 62ms (9 times) realtime
Wake lock 1000 PhoneWindowManager.mPowerKeyWakeLock: 57ms (3 times) realtime
Wake lock u0a102 LocationManagerService: 45ms (7 times) realtime
Wake lock u0a31 LocationManagerService: 17ms (9 times) realtime
Wake lock u0a53 *alarm*: 8ms (2 times) realtime
All wakeup reasons:
Wakeup reason unknown: 10m 0s 21ms (2051 times) realtime
Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 4m 22s 439ms (308 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: qcom_rx_wakelock : 26s 121ms (83 times) realtime
Wakeup reason Abort:Pending Wakeup Sources:
: 13s 229ms (70 times) realtime
Wakeup reason Abort:Last active Wakeup Source: qcom_rx_wakelock: 18s 420ms (59 times) realtime
Wakeup reason Abort:Last active Wakeup Source: qpnp_fg_update_temp: 19s 235ms (51 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: PowerManagerService.WakeLocks : 18s 441ms (43 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: NETLINK NETLINK : 6s 576ms (20 times) realtime
Wakeup reason Abort:Last active Wakeup Source: eventpoll: 6s 829ms (17 times) realtime
Wakeup reason Abort:Last active Wakeup Source: qpnp_fg_update_sram: 3s 348ms (9 times) realtime
Wakeup reason Abort:Last active Wakeup Source: ipc000000ce_sensors.qcom: 1s 998ms (5 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: NETLINK : 2s 762ms (5 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: qcom_rx_wakelock NETLINK NETLINK : 957ms (4 times) realtime
Wakeup reason Abort:?u????p;?u????0;?u???????? device failed: 410ms (2 times) realtime
Wakeup reason Abort:p;?u????p;?u????0;?u???????? device failed to power down: 769ms (2 times) realtime
Wakeup reason Abort:Last active Wakeup Source: KeyEvents: 768ms (2 times) realtime
Wakeup reason Abort:Last active Wakeup Source: PowerManagerService.WakeLocks: 506ms (1 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: qpnp_fg_update_sram qpnp_fg_memaccess : 397ms (1 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: qcom_rx_wakelock PowerManagerService.WakeLocksrealtime
Wakeup reason Abort:Pending Wakeup Sources:
NETLINK NETLINKrealtime
Wakeup reason Abort:Pending Wakeup Sources: ipc000000bd_sensors.qcomrealtime
Wakeup reason Abort:Pending Wakeup Sources: wlanrealtime
Wakeup reason Abort:Pending Wakeup Sources: qpnp_fg_update_temp qpnp_fg_memaccessrealtime
到底是什么在后台疯狂唤醒耗电？
谁看得懂????
拆了kill 发表于
谁看得懂????
稳定版不能root所以专业软件查看不了唤醒只能看log但这个log都是应用代号不能确定是那个应用所以需要大神计算代号对应的程序不然只能刷开发板root自己查看真的麻烦。。。
版主管理大神在哪里，真心求解!
菜鸟没看懂，抱歉了
笨蛋不懂哭
这串东西差点把我这个小白吓尿了
有设备没法挂起, 在占着耗电:Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 4m 22s 439ms (308 times) realtime
发现待机耗电跟sensors.qcom相关, 只要它出现在batterystats里就异常耗电!
并且batterystats报告&Wakeup reason Abort&:All wakeup reasons:
Wakeup reason Abort:Last active Wakeup Source: ipc_sensors.qcom: 6h 24m 33s 257ms (91014 times) realtime
Wakeup reason unknown: 17m 26s 480ms (1695 times) realtime
Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 12m 37s 541ms (350 times) realtime
Wakeup reason Abort:Last active Wakeup Source: qpnp_fg_update_temp: 2m 12s 738ms (349 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: bam_dmux_wakelock : 4m 12s 839ms (280 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: qcom_rx_wakelock : 1m 11s 203ms (277 times) realtime
Wakeup reason Abort:Last active Wakeup Source: SensorService_wakelock: 2m 35s 118ms (271 times) realtime
Wakeup reason Abort:Last active Wakeup Source: ipc000000bf_sensors.qcom: 47s 261ms (152 times) realtime
Wakeup reason Abort:Last active Wakeup Source: qcom_rx_wakelock: 37s 518ms (121 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: PowerManagerService.WakeLocks : 27s 805ms (105 times) realtime
Wakeup reason Abort:Last active Wakeup Source: qpnp_fg_update_sram: 42s 626ms (103 times) realtime伴随大量的:...
& && &+16h19m43s140ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m43s393ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m43s647ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m43s900ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m44s152ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m44s406ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m44s658ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m44s912ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m45s165ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m45s419ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m45s672ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m45s928ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m46s185ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m46s437ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
& && &+16h19m46s691ms (2) 064 wake_reason=0:&Abort:Last active Wakeup Source: ipc_sensors.qcom&
ipc_sensors.qcom貌似是距离感应器.
于是我关闭了设置里的&防误触模式&, 发现&Wakeup reason Abort:Last active Wakeup Source: ipc_sensors.qcom&只剩一点儿了(可能跟接打电话贴脸关屏有关).
待机耗电接近正常!
但还是有少量的&Wakeup reason Abort&, 继续研究中...
MAPGPS 发表于
ipc_sensors.qcom貌似是距离感应器.
于是我关闭了设置里的&防误触模式&, 发现&Wakeup reason Abort ...
还关闭了WiFi, 开4G。这是昨晚待机电流图，最低5mA, 耗电才3%。
看来之前晚上待机耗电15%跟距离感应器和WiFi设备有关。
查看完整版本:一周以前刷的miui，总体不错，反应耗电的进来看看_酷派大神f1吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：54,142贴子：
一周以前刷的miui，总体不错，反应耗电的进来看看收藏
你们认为什么样才是省电啊，玩大型游戏手机发热楼主表示默认，但是酷派的确垃圾要死
票牛教你如何买到热门、便宜、真实的演出门票！
哪里垃圾？
登录百度帐号推荐应用
为兴趣而生，贴吧更懂你。或在线时间51 小时
版本V8.0.8.0.MAACNDH
积分 133, 距离下一级还需 67 积分
积分 133, 距离下一级还需 67 积分
机型小米手机5
MIUI版本V8.0.8.0.MAACNDH
来自网页版
大家好，我用的是魅族mx四核自从刷了小米系统后耗电情况非常严重跟本都不知道为什么？在晚上十二点钟前我把电充满后就把手机调到飞行模式，然后睡觉。到了第二天早上九点多的时候就发现手机已经耗去了10%多的电，有时更离普的是早上一起床只剩40%多电令我十分无奈，请各路的大神指点一下我该如何做比较省电，还是我电池问题呢？
遇到的人越多，MIUI开发组会越关注
分享到微信朋友圈
打开微信，点击底部的“发现”，使用 “扫一扫” 即可将网页分享到我的朋友圈。
经验187 米
在线时间20 小时
版本3.11.29
积分 211, 距离下一级还需 289 积分
积分 211, 距离下一级还需 289 积分
机型魅族MX2
签到次数18
MIUI版本3.11.29
来自网页版
个人感觉比flyme省电& &&&mx2
经验19002 米
威望116 米
在线时间1834 小时
版本V8.0.5.0.LXKCNDG
我想我该走了
机型小米手机4c
签到次数179
MIUI版本V8.0.5.0.LXKCNDG
来自网页版
楼主你好。请你进入recovery主菜单选择工具 然后进行电池信息初始化看看。
在线时间51 小时
版本V8.0.8.0.MAACNDH
积分 133, 距离下一级还需 67 积分
积分 133, 距离下一级还需 67 积分
机型小米手机5
MIUI版本V8.0.8.0.MAACNDH
来自网页版
好的，我试试吧，谢谢
在线时间51 小时
版本V8.0.8.0.MAACNDH
积分 133, 距离下一级还需 67 积分
积分 133, 距离下一级还需 67 积分
机型小米手机5
MIUI版本V8.0.8.0.MAACNDH
来自网页版
可惜我不是
在线时间51 小时
版本V8.0.8.0.MAACNDH
积分 133, 距离下一级还需 67 积分
积分 133, 距离下一级还需 67 积分
机型小米手机5
MIUI版本V8.0.8.0.MAACNDH
来自网页版
好像没有什么变的？
经验19002 米
威望116 米
在线时间1834 小时
版本V8.0.5.0.LXKCNDG
我想我该走了
机型小米手机4c
签到次数179
MIUI版本V8.0.5.0.LXKCNDG
来自网页版
你现在一直都是这样
经验1114 米
在线时间208 小时
积分 1530, 距离下一级还需 470 积分
积分 1530, 距离下一级还需 470 积分
机型OPPO Find7
签到次数44
MIUI版本6.7.7
通过手机发布
点设置 应用 把你不用自启的软件点开！拉到最下面！把自启关闭！就好了！省电！
在线时间51 小时
版本V8.0.8.0.MAACNDH
积分 133, 距离下一级还需 67 积分
积分 133, 距离下一级还需 67 积分
机型小米手机5
MIUI版本V8.0.8.0.MAACNDH
来自网页版
之前已经这样设置了，现在还是这样耗电，晚上12点钟电量99%的，到第二天11点只剩60%多
在线时间16 小时
版本3.6.14
积分 99, 距离下一级还需 101 积分
积分 99, 距离下一级还需 101 积分
机型魅族MX2
MIUI版本3.6.14
来自网页版
桔村块饼V 发表于
回复 lizhaozhao 的帖子
之前已经这样设置了，现在还是这样耗电，晚上12点钟电量99%的，到第二天11点只剩6 ...
我的也是这样，我还以为是个案呢，我的掉电特夸张，7小时能掉电35%以上，待机要比FLYME要耗电10倍以上，这样怎么让人活啊
MIUI 3000万
MIUI 3000万发烧友纪念勋章
MIUI 2000万
MIUI 2000万发烧友纪念勋章
1000万用户纪念勋章
MIUI1000万用户纪念勋章
MIUI 7纪念勋章
MIUI五周年
MIUI五周年纪念勋章
MIUI三周年
MIUI三周年纪念勋章
百万壁纸评审纪念勋章
已关注微信
已关注极客秀微信
关注腾讯微博
已关注腾讯微博
关注新浪微博
已关注新浪微博
发烧友俱乐部
发烧友俱乐部
Copyright (C) 2016 MIUI
京ICP备号 | 京公网安备34号 | 京ICP证110507号【MIUI小吐槽】系统耗电_miui吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：1,628,112贴子：
【MIUI小吐槽】系统耗电收藏
最近升级两次，系统耗电量大了很多，谁知道咋回事？？
票牛教你如何买到热门、便宜、真实的演出门票！
红包助手关掉
自动亮度关了
我一直是最高亮度，是系统耗电不是屏幕
最近很多人都这样
我不知道。
我也是这样，妈的，很快没电，系统有病
登录百度帐号推荐应用
为兴趣而生，贴吧更懂你。或【miui】求助大神_miui吧_百度贴吧
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&签到排名：今日本吧第个签到，本吧因你更精彩，明天继续来努力！
本吧签到人数：0成为超级会员，使用一键签到本月漏签0次！成为超级会员，赠送8张补签卡连续签到：天&&累计签到：天超级会员单次开通12个月以上，赠送连续签到卡3张
关注：1,628,112贴子：
【miui】求助大神收藏
我的联通版小米3
刷的开发版
但是现在显示无法连接到相机
清除数据和重启电话
有哪位大神知道该怎么解决吗
上海张学友、王菲演唱会一站式购票!票品安全且真票!立即订购!
楼上正解，如果解决不了问题，速度去找小米客服，别拖。当然，拖一拖问题也不大，小米肯定要把你的机器弄好。如果你15天内去找小米，小米直接给你换新的。如果你15天后去找小米，小米会先给你修，修不好的话，才给你换。
你是怎么刷的开发版？
登录百度帐号推荐应用
为兴趣而生，贴吧更懂你。或}