4 ms·

I wonder if Google's own apps are exempt from adaptive battery? I continue to have problems with Google's apps soaking my phone's battery. Reset the phone, and

by cmurf 8y ago

I wonder if Google's own apps are exempt from adaptive battery? I continue to have problems with Google's apps soaking my phone's battery. Reset the phone, and I get 6 days of standby (this is LineageOS). Install Google apps, and it's now 4 hours. Wakelock detector says the apps Inbox, Google, and Google Contacts are the top offenders with dozens of wakes keeping the phone awake between 40% and 99% of the time. Super irritating.

izacus 8y ago
That wakelock detector is probably showing wrong data (especially on newer API levels). Can you try something more advanced like Battery Historian (in dev tools) to see what's waking up the CPU? (And no, Google apps are beholden to all power saving restrictions like other apps - Play Services being the exception because it services functionality that must work at all times.)
- cmurf 8y ago
  Battery Historian isn't really helping pin this down. CPU is running the whole time over night, ~5%/hr drain doing nothing. Kernel only uptime has hundreds of events per minute with reason "unknown". Userspace wakelocks total less than 16s every 20 minutes with no app I recognize named (Babel_ConcService is the top offender). Top app is blank as is Long waklocks and Screen. Doze is "light" all night. Kernel Wakesources: Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count 0 | event1 | 17m59s340ms | 23457.57 | 3h2m57.557s | 238578 1 | event5 | 17m32s350ms | 23463.47 | 2h58m23.053s | 238638 2 | alarmtimer | 1m47s350ms | 53.59 | 18m11.818s | 545 3 | wlan | 45s341ms | 58.99 | 7m41.149s | 600 4 | bluetooth_timer | 23s642ms | 194.68 | 4m0.462s | 1980 No idea what event1 and event5 are, but that seems excessive. Kernel Wakeup Reasons: Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count | Show Count vs Time 0 | unknown | 57m26s285ms | 11789.25 | 9h44m10.852s | 119904 | App Wakeup Alarms: Ranking | Name | Uid | Frequency (count/hr) | Count 0 | GOOGLE_SERVICES | 10033 | 60.66 | 617 1 | com.android.providers.calendar | 10004 | 0.20 | 2 60 wakeup alarms per hour? Excessive anytime but absurd for night time. Time Spent In Each App State: Name | Uid | Top / Hr | Foreground Service / Hr | Top Sleeping / Hr | Foreground / Hr | Background / Hr | Cached / Hr GOOGLE_SERVICES | 10033 | 7s202ms | 59m52s311ms | 0ms | 486ms | 0ms | 0ms bbc.mobile.news.ww | 10109 | 5s312ms | 0ms | 0ms | 0ms | 762ms | 16m48s169ms net.sourceforge.opencamera | 10097 | 5s71ms | 0ms | 0ms | 0ms | 0ms | 59m54s209ms com.google.android.tts | 10072 | 4s910ms | 88ms | 0ms | 0ms | 0ms | 59m54s200ms com.cyanogenmod.trebuchet | 10026 | 3s247ms | 0ms | 59m44s851ms | 0ms | 0ms | 11s900ms Foreground service per hour? Anyway, battery life goes to about 4 days standby if I put the phone in airplane mode. Or if I reset the phone and then on next boot I don't enter my Google account info. I have one bugreport where the discharge rate varied between 15% and 40% per hour, but there's no battery data due to overflow (?) looks like I'm only getting 3-4 hours of detailed data after a reboot.
  - izacus 8y ago
    Hmmm... if I remember correctly the concservice thing is supposed to come from the Hangouts app. Unless you have Fi, can you try disabling it?
    - cmurf 8y ago
      I've uninstalled Hangouts Dialer and Hangouts, reset stats and rebooted, left the phone untouched since. No change in discharge rate, it's still around 4-6% per hour. The top user wake lock offender is NlpWakeLock now, but it lasts just a second, but happens every 10-15 minutes. Still event1 and event5 listed as wakesources with tens of thousands of counts per hour each. And still kernel wakeup reason "unknown" 12000+ counts per hour and 58m per hour duration (the entire 3h46m the phone was left since booting until capturing the bugreport). The big gripe I have is in fact not the battery loss. It's the lack of tools that reliably pin the blame on the cause of the problem. So now I have to once again F around with uninstalling apps one by one to find out whodunnit and past experience tells me it will be a Google app or service with no recourse for getting the problem fixed. It's really an irritating platform. Edit: And the WLD app shows the phone is "awake" 99% of the time. But if I put it in airplane mode, or wipe it and don't put it in airplane mode, it'll be awake 1% of the time (this is being left alone untouched for 1-4 hours).
      - izacus 8y ago
        Yeah, honestly this looks like there's something wrong with the actual phone (not software) - those "event" sources tend to come from kernel interrupts and those issues tend to happen when a sensor or something related malfunctions. Just a guess tho.
        cmurf 8y ago
        Except doesn't happen after a reset. Doesn't happen when in airplane mode. Happens only after I restore apps. Something is busy doing something when there's network access, and I suspect the 15% to 40% drains are when wifi goes down for whatever reason and I'm left with a really crummy weak mobile signal, which I know drains phone batteries fast just by the nature of having to compensate for weak signal.
machiavelli1024 8y ago
That ML pipeline ain’t gonna feed itself, y’know?

by cmurf 8y ago

izacus 8y ago

That wakelock detector is probably showing wrong data (especially on newer API levels). Can you try something more advanced like Battery Historian (in dev tools) to see what's waking up the CPU? (And no, Google apps are beholden to all power saving restrictions like other apps - Play Services being the exception because it services functionality that must work at all times.)

cmurf 8y ago
Battery Historian isn't really helping pin this down. CPU is running the whole time over night, ~5%/hr drain doing nothing. Kernel only uptime has hundreds of events per minute with reason "unknown". Userspace wakelocks total less than 16s every 20 minutes with no app I recognize named (Babel_ConcService is the top offender). Top app is blank as is Long waklocks and Screen. Doze is "light" all night. Kernel Wakesources: Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count 0 | event1 | 17m59s340ms | 23457.57 | 3h2m57.557s | 238578 1 | event5 | 17m32s350ms | 23463.47 | 2h58m23.053s | 238638 2 | alarmtimer | 1m47s350ms | 53.59 | 18m11.818s | 545 3 | wlan | 45s341ms | 58.99 | 7m41.149s | 600 4 | bluetooth_timer | 23s642ms | 194.68 | 4m0.462s | 1980 No idea what event1 and event5 are, but that seems excessive. Kernel Wakeup Reasons: Ranking | Name | Duration / Hr | Count / Hr | Total Duration | Total Count | Show Count vs Time 0 | unknown | 57m26s285ms | 11789.25 | 9h44m10.852s | 119904 | App Wakeup Alarms: Ranking | Name | Uid | Frequency (count/hr) | Count 0 | GOOGLE_SERVICES | 10033 | 60.66 | 617 1 | com.android.providers.calendar | 10004 | 0.20 | 2 60 wakeup alarms per hour? Excessive anytime but absurd for night time. Time Spent In Each App State: Name | Uid | Top / Hr | Foreground Service / Hr | Top Sleeping / Hr | Foreground / Hr | Background / Hr | Cached / Hr GOOGLE_SERVICES | 10033 | 7s202ms | 59m52s311ms | 0ms | 486ms | 0ms | 0ms bbc.mobile.news.ww | 10109 | 5s312ms | 0ms | 0ms | 0ms | 762ms | 16m48s169ms net.sourceforge.opencamera | 10097 | 5s71ms | 0ms | 0ms | 0ms | 0ms | 59m54s209ms com.google.android.tts | 10072 | 4s910ms | 88ms | 0ms | 0ms | 0ms | 59m54s200ms com.cyanogenmod.trebuchet | 10026 | 3s247ms | 0ms | 59m44s851ms | 0ms | 0ms | 11s900ms Foreground service per hour? Anyway, battery life goes to about 4 days standby if I put the phone in airplane mode. Or if I reset the phone and then on next boot I don't enter my Google account info. I have one bugreport where the discharge rate varied between 15% and 40% per hour, but there's no battery data due to overflow (?) looks like I'm only getting 3-4 hours of detailed data after a reboot.
- izacus 8y ago
  Hmmm... if I remember correctly the concservice thing is supposed to come from the Hangouts app. Unless you have Fi, can you try disabling it?
  - cmurf 8y ago
    I've uninstalled Hangouts Dialer and Hangouts, reset stats and rebooted, left the phone untouched since. No change in discharge rate, it's still around 4-6% per hour. The top user wake lock offender is NlpWakeLock now, but it lasts just a second, but happens every 10-15 minutes. Still event1 and event5 listed as wakesources with tens of thousands of counts per hour each. And still kernel wakeup reason "unknown" 12000+ counts per hour and 58m per hour duration (the entire 3h46m the phone was left since booting until capturing the bugreport). The big gripe I have is in fact not the battery loss. It's the lack of tools that reliably pin the blame on the cause of the problem. So now I have to once again F around with uninstalling apps one by one to find out whodunnit and past experience tells me it will be a Google app or service with no recourse for getting the problem fixed. It's really an irritating platform. Edit: And the WLD app shows the phone is "awake" 99% of the time. But if I put it in airplane mode, or wipe it and don't put it in airplane mode, it'll be awake 1% of the time (this is being left alone untouched for 1-4 hours).
    - izacus 8y ago
      Yeah, honestly this looks like there's something wrong with the actual phone (not software) - those "event" sources tend to come from kernel interrupts and those issues tend to happen when a sensor or something related malfunctions. Just a guess tho.
      - cmurf 8y ago
        Except doesn't happen after a reset. Doesn't happen when in airplane mode. Happens only after I restore apps. Something is busy doing something when there's network access, and I suspect the 15% to 40% drains are when wifi goes down for whatever reason and I'm left with a really crummy weak mobile signal, which I know drains phone batteries fast just by the nature of having to compensate for weak signal.

machiavelli1024 8y ago

That ML pipeline ain’t gonna feed itself, y’know?