[已解決] 820s的耗電問題

820s2015-9-18 09:46

使用上不算耗電, 但令我介意的是它的喚醒機制似乎還有待加強.

一個晚上耗電量是15%, 貼部分 bugreport內容, 請問是否正常, 是否可以從設定來避免.

底下是bugreport 擷取, 還需要看甚麼請指教, 謝謝.

  Time on battery: 14h 21m 51s 48ms (99.6%) realtime, 12h 37m 3s 84ms (87.4%) uptime

  Time on battery screen off: 13h 50m 32s 196ms (95.9%) realtime, 12h 5m 44s 232ms (83.8%) uptime

  Total run time: 14h 25m 41s 859ms realtime, 12h 40m 53s 895ms uptime

  Start clock time: 2015-09-18-07-15-05

  Screen on: 31m 18s 852ms (3.6%) 7x, Interactive: 31m 17s 806ms (3.6%)


  Total full wakelock time: 6m 22s 244ms

  Total partial wakelock time: 41m 28s 868ms

......
  All partial wake locks:

  Wake lock u0a18 NlpCollectorWakeLock: 28m 2s 328ms (663 times) realtime

  Wake lock u0a65 NlpWakeLock: 2m 27s 245ms (684 times) realtime

  Wake lock u0a18 NlpWakeLock: 2m 20s 788ms (2805 times) realtime

  Wake lock 1000 ConnectivityService: 1m 3s 979ms (8 times) realtime

  Wake lock u0a18 ContextManagerWakeLock: 54s 994ms (1819 times) realtime

  Wake lock u0a65 EntriesRefresh_wakelock: 53s 192ms (24 times) realtime

  Wake lock 1000 BatteryServiceUpdateStats_3: 44s 730ms (17030 times) realtime



14個小時的歷史紀錄就發現BatteryServiceUpdateStats_3, 一直不斷喚醒.
也發現一些停用的app, 如chrome, kid, fitness 除了停用, 同步也關掉了, 但還是有喚醒動作


  Wake lock u0a18 *sync*/com.google.android.gms.kids.common.sync/com.google/*****: 42ms (1 times) realtime


  Wake lock u0a78 wake:com.android.chrome/org.chromium.content.browser.BackgroundSyncLauncherService: 15ms (3 times) realtime





除了內建程式, 共安裝了line, JPTT, 中華電信客服, 就這樣, 但自裝的程式也只看到line 喚醒了13次


  Wake lock u0a136 jp.naver.line.android: 2s 993ms (13 times) realtime
本文章最後由( 尼爾 )於 2015-9-24 18:50 編輯

• 標籤
• 820s