OEM battery optimization saga [179644471]

Assigned

Bug

Status Update

No update yet.

Description

se...@gmail.com

created issue #1

Feb 8, 2021 05:18PM

2 years ago, I created an issue here on how certain OEMs were altering core Android components for the sake of battery optimization, while breaking basic functionality that developers rely upon (https://issuetracker.google.com/issues/122098785). Despite the issue gaining some traction and developer community support, it seems to have gone nowhere.

I am here to try and reach out to the Android team again, and request you to properly address this matter. About 7 months ago, this issue was the most voted topic in the Android 11 Reddit AMA, and we received a number less than adequate replies from the team. One of these was how Google will be updating the CDD to enforce OEMs to be transparent about their restrictions. To quote:

"We are updating the Compatibility Definition Document (CDD) for Android 11 to make sure device manufacturers are alerting users of app restrictions in a timely manner. Not only does this help educate users about what is happening to their apps, but it also allows users to override the restriction if they choose to."

Unfortunately, this seems to have fallen on deaf OEM ears. My Samsung Galaxy S10e device recently got updated to Android 11, and lo and behold, Samsung continues to run these shady practices by disabling wake-locks and broadcast messages without user or developer consent.

Attached, you will find a test app that I used to collect accelerometer data, by running a foreground service. It's a simple app that logs the timestamps of the sampled data, alongside the system time when the data was delivered. When the device is unplugged and set aside with the screen off, after 3 minutes, the app stops receiving accelerometer data. After a few minutes, I plug in the device to extract the data, and the app resumes receiving the data (80 seconds of data in a short burst), however there is a large gap in the data, plus there are intermittent out-of-order values (i.e. the timestamps are not always monotonically increasing). You can find the result attached as well.

Looking into the device logs (attached), it is clear that at the exact moment when the app stopped receiving data, the power manager service decided to "freeze" the app, disabling its wakelock. The app is "unfrozen" again after plugging the USB cable.

02-08 09:43:01.509 D/FreecessController(  979): FZ : com.example.myapplication(9793)
02-08 09:43:01.510 D/FreecessController(  979): FZ : com.example.myapplication(0), reason: LEV
02-08 09:43:01.511 E/TrafficController(  526): FREECESS
02-08 09:43:01.516 I/PowerManagerService(  979): [PWL] SetWakeLockEnableDisable uid = 10311 , disable= true
02-08 09:43:01.517 I/PowerManagerService(  979): [PWL] find out: PARTIAL_WAKE_LOCK              'com.example.myapplication:serv' DISABLED (uid=10311 pid=9793 pkg=com.example.myapplication)  disabled -> true
02-08 09:43:01.517 E/statsd  (  525): Predicate 5980654721335871649 dropping data for dimension key (10)0x2010101->10311[I] (10)0x30000->com.example.myapplication:serv[S] 
02-08 09:43:01.518 D/FreecessController(  979): disable frozen app (com.example.myapplication,10311) wakelock.
...
02-08 09:49:53.252 D/FreecessController(  979): UFZ : com.example.myapplication(9793)
02-08 09:49:53.253 D/FreecessController(  979): UFZ : com.example.myapplication(0), reason: charging
02-08 09:49:53.253 W/BtGatt.GattService( 6780): unfreezeScan() - No AppScanStats found with uid: 10311
...
02-08 09:49:53.260 D/FreecessController(  979): apply [LRs:false] to uid[10311]
02-08 09:49:53.260 W/LocationManagerService(  979): onFreezeStateChanged, uid[10311]=false
02-08 09:49:53.260 V/AlarmManager(  979): unblockMARsRestrictedAlarmsForUidPackage: uid = 10311, packageName = null
02-08 09:49:53.260 D/FreecessController(  979): send pending alarm to packageName:null, uid:10311
02-08 09:49:53.260 I/PowerManagerService(  979): [PWL] SetWakeLockEnableDisable uid = 10311 , disable= false
02-08 09:49:53.260 I/PowerManagerService(  979): [PWL] find out: PARTIAL_WAKE_LOCK              'com.example.myapplication:serv' ACQ=0 (uid=10311 pid=9793 pkg=com.example.myapplication)  disabled -> false
02-08 09:49:53.260 D/FreecessController(  979): enable frozen app (com.example.myapplication,10311) wakelock.

The only way I am able to avoid this issue is by disabling Android's battery optimization. However, as you know, this action is generally forbidden in Google Play's policy and can result in my app getting removed from Google Play.

This is just one example. I am sure the community can come up with thousands, for different OEMs.

I would like to know if Google plans to solve this long standing issue, and if so, how and when. If Google does not enforce strict policies that OEMs must abide by, and we don't see the situation improving, it will no longer be feasible for us to build products for Android.

myapplication.zip

Restricted

886 KB

Download

accel.xlsx

Restricted

269 KB

Download

logcat.gz

Restricted

383 KB

Download

Comments

ja...@google.com <ja...@google.com> #2Feb 8, 2021 08:53PM

Status: Duplicate of

122098785

Information redacted by Android Beta Feedback.

pe...@gmail.com <pe...@gmail.com> #3Feb 16, 2021 12:56PM

Thanks for reporting this issue. We have passed this to the development team and will update this issue with more information as it becomes available.

ja...@google.com <ja...@google.com> #4Feb 16, 2021 05:39PM

What

More information

Deep sleep stops working. Restart helps

Where

Build and device data

- Build Number: google/husky_beta/husky:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1

Debugging information
Usługi Google Play
com.google.android.gms
Version 250934035 (25.09.34 (260400-738842635))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699804033 (134.0.6998.40)
System App (Updated)

Network operator: Orange
SIM operator: Orange

Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit https://developer.android.com/preview/feedback#feedback-app.

pe...@gmail.com <pe...@gmail.com> #5Feb 17, 2021 10:23AM

Information redacted by Android Beta Feedback.

ja...@google.com <ja...@google.com> #6Feb 17, 2021 03:25PM

What

More information

My Pixel 8 battery lasts less than with version 15

Where

Build and device data

- Build Number: google/shiba_beta/shiba:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1

Debugging information
Servicios de Google Play
com.google.android.gms
Version 250934035 (25.09.34 (260400-738842635))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699804033 (134.0.6998.40)
System App (Updated)

Network operator: Not available
SIM operator: AT&T

sm...@gmail.com <sm...@gmail.com> #7Feb 19, 2021 04:44AM

Information redacted by Android Beta Feedback.

co...@gmail.com <co...@gmail.com> #8Feb 19, 2021 09:11AM

I was having a nightmare with my phone—its battery was draining incredibly fast, making it almost unusable. After some trial and error, I finally found a temporary solution: I disabled Google Chrome app and switched to using Firefox. So far, it’s working great. The battery is still at 85% after around 12 hours of on-and-off usage. Previously, I had to charge it every 12 hours just to keep it running through the day.

[Deleted User] <[Deleted User]> #9
Restricted
Mar 6, 2021 10:37PM

Learn More

sa...@google.com <sa...@google.com> Mar 29, 2021 07:04PM

Status: Assigned (reopened)

lb...@gmail.com <lb...@gmail.com> #10Mar 29, 2021 10:52PM

deleted

ad...@google.com <ad...@google.com> #11Mar 30, 2021 11:13AM

My google pixel 6 pro's battery lasts only for 6 to 7 hours with or without data usage...

se...@gmail.com <se...@gmail.com> #12Mar 30, 2021 11:26AM

I have the same issue in my pixel 7 after i do update yo android 16 b3

Le sam. 29 mar. 2025, 19:04, <buganizer-system@google.com> a écrit :

- Show quoted text -

br...@gmail.com <br...@gmail.com> #13Mar 31, 2021 08:09PM

I also struggle from the same issue with the battery after I updated to android 16

pe...@gmail.com <pe...@gmail.com> #14Apr 2, 2021 12:14PM

Please help us Google with some updates

se...@gmail.com <se...@gmail.com> #15Apr 5, 2021 10:21PM

My issue is not yet resolved.

On Sun, Mar 30, 2025, 12:03 AM <buganizer-system@google.com> wrote:

- Show quoted text -

se...@gmail.com <se...@gmail.com> #16Apr 5, 2021 10:23PM

What

More information

Battery is draining too fast I recorded 5 hours of screen on time for the first yesterday since I bought my pixel 8 pro

Where

Build and device data

Debugging information
Google Play services
com.google.android.gms
Version 250934035 (25.09.34 (260400-738842635))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699810833 (134.0.6998.108)
System App (Updated)

Network operator: Airtel Zambia
SIM operator: Airtel ZM

Network operator: MTN Zambia
SIM operator: MTN Zambia

ka...@gmail.com <ka...@gmail.com> #17Apr 6, 2021 07:11AM

I also face battery draining issue. Please fix it.

On Sun, Mar 30, 2025, 7:18 PM <buganizer-system@google.com> wrote:

- Show quoted text -

pe...@gmail.com <pe...@gmail.com> #18Apr 8, 2021 02:14PM

What

More information

the battery discharges extremely quickly from 35 percent and I have to plug in the charger to turn on the phone and besides the phone turns on again alone when I plug in this since the last beta 3.1 update in. And this despite the fact that I did everything to save battery (limiting apps in the background and saving energy and using wifi instead of mobile data I did everything)

When

Time and frequency

Time when bug report was triggered: Mar 30, 2025 8:16 PM GMT+01:00

Where

Build and device data

- Build Number: google/lynx_beta/lynx:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Services Google Play
com.google.android.gms
Version 251260035 (25.12.60 (260400-740938339))
System App (Updated)

Android System WebView
com.google.android.webview
Version 704902643 (135.0.7049.26)
System App (Updated)

Network operator: Orange
SIM operator: Orange

tz...@gmail.com <tz...@gmail.com> #19Apr 11, 2021 08:34AM

Information redacted by Android Beta Feedback.

ji...@google.com <ji...@google.com> #20Apr 16, 2021 01:42AM

What

More information

Very fast battery drain on pixel 6a since the last beta update.

When

Time and frequency

Time when bug report was triggered: Mar 31, 2025 5:20 PM GMT+02:00

Where

Build and device data

- Build Number: google/bluejay_beta/bluejay:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Services Google Play
com.google.android.gms
Version 251331035 (25.13.31 (260400-741637389))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Orange F
SIM operator: Orange F

se...@gmail.com <se...@gmail.com> #21Apr 16, 2021 05:43AM

Information redacted by Android Beta Feedback.

ji...@google.com <ji...@google.com> #22Apr 23, 2021 12:17AM

What

More information

Battery is draining too fast from 100% to 90% and 75% within less than an hour.

Where

Build and device data

- Build Number: google/raven_beta/raven:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 251036035 (25.10.36 (260400-739992411))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Telenor
SIM operator: Telenor

ar...@gmail.com <ar...@gmail.com> #23May 25, 2021 01:21AM

Information redacted by Android Beta Feedback.

me...@gmail.com <me...@gmail.com> #24Jun 19, 2021 09:52AM

What

More information

Phone is getting hotter and stuttery auring gaming which was running fine on 15.

When

Time and frequency

Time when bug report was triggered: Apr 1, 2025 7:57 PM GMT+05:00

Where

Build and device data

- Build Number: google/oriole_beta/oriole:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 251036035 (25.10.36 (260400-739992411))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Not available
SIM operator: Telenor

mi...@gmail.com <mi...@gmail.com> #25Jun 30, 2021 10:35AM

Comment has been deleted.

Message last modified on Jun 30, 2021 10:37AM

mi...@gmail.com <mi...@gmail.com> #26Jun 30, 2021 10:41AM

Comment has been deleted.

Message last modified on Jun 30, 2021 10:59AM

di...@gmail.com <di...@gmail.com> #27Jul 6, 2021 04:45PM

Information redacted by Android Beta Feedback.

sa...@gmail.com <sa...@gmail.com> #28Jul 31, 2021 06:51AM

What

More information

My battery drain more faster and my phone is very warm even after doing simple things like scrolling on instagram

Where

Build and device data

Debugging information
Google Play services
com.google.android.gms
Version 251036035 (25.10.36 (260400-739992411))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Not available
SIM operator: mobilis

gr...@gmail.com <gr...@gmail.com> #29Aug 2, 2021 06:09PM

Information redacted by Android Beta Feedback.

ad...@gmail.com <ad...@gmail.com> #30Aug 5, 2021 08:31AM

Everyone suffers from heat and battery damage, unfortunately, Google, help
us

Le mer. 2 avr. 2025, 00:23, <buganizer-system@google.com> a écrit :

- Show quoted text -

te...@gmail.com <te...@gmail.com> #31Dec 7, 2021 07:45PM

What

More information

The battery drain is insane after the Android 16, my battery drained about 20% with no use The always on display cuts too much power. It wasn't an issue before but it's too much right now, using pixel 7

Where

Build and device data

- Build Number: google/panther_beta/panther:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 251036035 (25.10.36 (260400-739992411))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Jazz
SIM operator: Jazz

ra...@gmail.com <ra...@gmail.com> #32Dec 12, 2021 03:08AM

Information redacted by Android Beta Feedback.

[Deleted User] <[Deleted User]> #33Feb 4, 2022 03:35PM

I have used my phone for 20 minutes and lost 10% on battery saving mode on my pixel 9 pro that can't be normal.

gr...@kochaniak.com <gr...@kochaniak.com> #34Feb 4, 2022 03:47PM

Yes battery is draining tooo fast in google pixel 6 pro

[Deleted User] <[Deleted User]> #35Feb 4, 2022 03:55PM

Thank you for reporting this issue. We have a fix rolling out in an upcoming release.

gr...@kochaniak.com <gr...@kochaniak.com> #36Feb 4, 2022 05:13PM

What

More information

A significant draining in battery percentage even not using. Wifi and GPS are on.

When

Time and frequency

Time when bug report was triggered: Apr 3, 2025 1:34 PM GMT+08:00

Where

Build and device data

- Build Number: google/raven_beta/raven:16/BP22.250221.015/13278879:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 251036035 (25.10.36 (260400-739992411))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: TM
SIM operator: TM

an...@gmail.com <an...@gmail.com> #37Feb 13, 2022 07:07PM

Information redacted by Android Beta Feedback.

lo...@gmail.com <lo...@gmail.com> #38Feb 14, 2022 11:26AM

- Build Number: google/raven_beta/raven:16/BP22.250221.013/13218340:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

I'm facing the same issue of battery drainage. When my phone was on Android 15 the battery timing was good. But when i updated it to Android 16 beta version. The battery drains fast as compared to the previous version.
Please kindly resolve this issue as soon as possible.

Debugging information
Google Play services
com.google.android.gms
Version 251036029 (25.10.36 (190400-739992411))
System App (Updated)

Android System WebView
com.google.android.webview
Version 661308831 (128.0.6613.88)
System App (Updated)

Network operator: PK-UFONE
SIM operator: Ufone

Filed by Android Beta Feedback. Version (Bundled): 2.25-betterbug.external_20220328_RC02
To learn more about our feedback process, please visit

https://developer.android.com/preview/feedback#feedback-app.

ch...@gmail.com <ch...@gmail.com> #39Feb 16, 2022 03:14PM

What

Feature request

To much issues

Where

Build and device data

- Build Number: google/lynx_beta/lynx:16/BP22.250221.015/13278879:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 251134035 (25.11.34 (260400-740024306))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Jazz
SIM operator: Jazz

ng...@gmail.com <ng...@gmail.com> #40Mar 3, 2022 04:29AM

What

More information

Battery Drain Report Issue Description Battery drains excessively overnight (10-15%) and during normal use.

Symptoms

Overnight battery drain: 10-15% loss
Quick battery drain during normal use

Device Information

Device Model: [Insert device model]
Operating System: [Insert OS version]
Battery Capacity: [Insert battery capacity]

Usage Patterns

Normal use: [Insert normal usage patterns, e.g., social media, browsing, calls, texts]
Overnight settings: [Insert overnight settings, e.g., sleep mode, Wi-Fi, Bluetooth]

Expected Battery Life

Overnight: minimal battery drain (<5%)
Normal use: reasonable battery life (>8 hours)

Actual Battery Life

Overnight: 10-15% battery drain
Normal use: quick battery drain

Troubleshooting Steps

Check for software updates
Review battery-intensive apps
Adjust power-saving settings
Consider calibration or replacement

Would you like to troubleshoot or explore potential causes?

When

Time and frequency

Time when bug report was triggered: Apr 6, 2025 6:32 PM GMT+05:30

Where

Build and device data

- Build Number: google/shiba_beta/shiba:16/BP22.250221.015/13278879:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)
- SoC Revision: Zuma B1

Debugging information
Google Play services
com.google.android.gms
Version 251036035 (25.10.36 (260400-739992411))
System App (Updated)

Android System WebView
com.google.android.webview
Version 710300443 (136.0.7103.4)
System App (Updated)

Network operator: BSNL MOBILE
SIM operator: BSNL MOBILE

br...@xovation.com <br...@xovation.com> #41Mar 6, 2022 06:43PM

Information redacted by Android Beta Feedback.

gr...@kochaniak.com <gr...@kochaniak.com> #42Mar 6, 2022 07:29PM

Le téléphone chauffe avec les données mobiles

to...@gmail.com <to...@gmail.com> #43Mar 19, 2022 03:15PM

What

More information

Descarga muy rápido

Where

Build and device data

Debugging information
Servicios de Google Play
com.google.android.gms
Version 250934035 (25.09.34 (260400-738842635))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Cubacel
SIM operator: Cubacel

ad...@google.com <ad...@google.com> #44Mar 30, 2022 04:11PM

Information redacted by Android Beta Feedback.

ad...@google.com <ad...@google.com> #45Apr 6, 2022 01:14PM

What

More information

Sigue drenando batería, al principio de la actualización pareció mejorar, pero a vuelto a gastar mucho la batería en mi Google pixel 8

Where

Build and device data

Debugging information
Servicios de Google Play
com.google.android.gms
Version 251134035 (25.11.34 (260400-740024306))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: O2
SIM operator: O2

em...@gmail.com <em...@gmail.com> #46Apr 9, 2022 04:02PM

Information redacted by Android Beta Feedback.

ad...@google.com <ad...@google.com> #47Apr 13, 2022 10:13AM

في الاثنين، ٧ أبريل ٢٠٢٥، ١٢:٥٢ ص <buganizer-system@google.com> كتب:

- Show quoted text -

ad...@google.com <ad...@google.com> #48Apr 20, 2022 03:03PM

What

More information

Battery Stuck e no possibility to update

Where

Build and device data

- Build Number: google/panther_beta/panther:Baklava/BP22.250124.009/13034193:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play Services
com.google.android.gms
Version 251134035 (25.11.34 (260400-740024306))
System App (Updated)

Android System WebView
com.google.android.webview
Version 704903733 (135.0.7049.37)
System App (Updated)

Network operator: TIM
SIM operator: TIM

ad...@google.com <ad...@google.com> #49Apr 27, 2022 10:30AM

Information redacted by Android Beta Feedback.

gm...@gmail.com <gm...@gmail.com> #50Apr 27, 2022 12:53PM

- Build Number: google/cheetah_beta/cheetah:16/BP22.250221.015/13278879:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

I am facing very less screen on time on Pixel 7 pro. Just using Facebook, messenger, Instagram.

Debugging information
Google Play services
com.google.android.gms
Version 251432035 (25.14.32 (260400-744072750))
System App (Updated)

Android System WebView
com.google.android.webview
Version 699813533 (134.0.6998.135)
System App (Updated)

Network operator: Airtel
SIM operator: airtel

Filed by Android Beta Feedback. Version (Updated): 2.46-betterbug.external_20241023_RC01 (DOGFOOD)
To learn more about our feedback process, please visit

https://developer.android.com/preview/feedback#feedback-app.

uf...@gmail.com <uf...@gmail.com> #51Apr 27, 2022 01:03PM

What

More information

I'm having the same problem with this on my Pixel 8a I have to use extreme battery saver just to make it one day with enough battery.

Where

Build and device data

- Build Number: google/akita_beta/akita:16/BP22.250221.015/13278879:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Google Play services
com.google.android.gms
Version 251361035 (25.13.61 (260400-743672900))
System App (Updated)

Android System WebView
com.google.android.webview
Version 710300443 (136.0.7103.4)
System App (Updated)

Network operator: T-Mobile
SIM operator: T-Mobile

vi...@google.com <vi...@google.com> #52Apr 29, 2022 11:33AM

Information redacted by Android Beta Feedback.

gm...@gmail.com <gm...@gmail.com> #53Apr 29, 2022 04:24PM

To simplify reproducing the issue, I've run DontKillMyApp benchmark on our Redmi 6A (MIUI 11, Android 9), got "60%" result (see screenshot) and retrieved the bug report.

Screenshot_20220429_190455.png

Restricted

63 KB

View

Download

vi...@google.com <vi...@google.com> #54May 2, 2022 12:03PM

Re-comment#53, thanks for the above information. Could you please share a bugreport after reproducing the issue with MultiPassme and a screenrecord of the bug for reference (if possible).

va...@gmail.com <va...@gmail.com> #58May 5, 2022 09:27PM

Gracias lo entiendo

to...@gmail.com <to...@gmail.com> #59May 6, 2022 02:39AM

This is a ridiculously inappropriate and unprofessional way to handle and deal with a rule that Android itself has implemented. 2-2.5 YEARS LATER It's being investigated?! Whoa!! If that doesn't show the apathetic nature of the people that make the rules. Good for the enforcement but hey you all can do as you please so we'll just investigate a known, obvious and fixable problem. This is lunacy at its full blown grandeur. Throttle my phone to help you all look good, while other developers are harshly ignored. Nice show of quality and integrity. Just saying.

vi...@google.com <vi...@google.com> #60May 9, 2022 11:35AM

Re-

comment#53

: Could you please share the information requested in

comment#54

to proceed further.

gm...@gmail.com <gm...@gmail.com> #61May 9, 2022 10:04PM

Sure. Here is the bug report from Xiaomi Redmi Note 7 (MIUI 12.5, Android 10). Our app was killed multiple times, the last two cases are on May 9 at 19:42 and 22:56 (GMT+3).

I didn't make a screen record, because there seems to be nothing to record: our foreground notification is shown, but after a while (sometimes 15 minutes, sometimes about an hour) it's just gone.

We have a plain foreground service, no wakelocks. All energy saving settings are on default values.

vi...@google.com <vi...@google.com> #62May 11, 2022 09:56AM

We’ve shared this with our product and engineering teams and will continue to provide updates as more information becomes available.

ba...@gmail.com <ba...@gmail.com> #63May 15, 2022 04:08PM

10 t0 android 12 software update my phone

ha...@gmail.com <ha...@gmail.com> #64Jun 3, 2022 06:22PM

8.0 android software update my phone

ge...@gmail.com <ge...@gmail.com> #65Jul 29, 2022 06:30PM

Wow, y'all I knew so eone was in my account and I have been on Google for 2 years and ... BAM... TODAY I GOT SMART AND FOUND THE ANDROID STUDIO AND THIS ON THE GOOGLE CLOUD! IM VERY MAD AND GOOGLE YOU NEED TO DO SOMETHING ABOUT IT!!! NOW

te...@gmail.com <te...@gmail.com> #66Jul 30, 2022 12:09AM

Thank you very much.

Jeff

Jeffrey Polansky
13 Dorlyn Rd
Albany, NY 12205

TechValleyJeff@gmail.com
518-779-6625

On Fri, Jul 29, 2022, 2:31 PM <buganizer-system@google.com> wrote:

- Show quoted text -

[Deleted User] <[Deleted User]> #67Sep 11, 2022 08:59AM

I have created a related topic about background execution on Samsungs compared with pixel with evidence and the sample app. Maybe it would be helpful.
Here is a link: https://issuetracker.google.com/issues/245355414

vi...@google.com <vi...@google.com> #68Nov 10, 2022 09:31PM

We shared the issue with Xiaomi but it was not reproducible. Could you please share the exact reproduction steps with us and if it's possible, share with us whether it can be replicated on an Android 10+ devices.

vi...@google.com <vi...@google.com> #69Nov 11, 2022 10:21PM

In addition to the above comment,

If the issue is reproducible, please share a bugreport for further investigation.
Can you please check if the issue can be solved by setting the App Info > Battery Saver option to No Restrictions?

sa...@google.com <sa...@google.com> #70Nov 19, 2022 03:04AM

Please provide the requested information to proceed further.

tz...@gmail.com <tz...@gmail.com> #71Nov 27, 2022 12:21PM

Just info:

In some cases this battery optimization causing the DeadSystemException. Especially on Samsung, Android 10.

I get multiple reports from a foreground service

Non-fatal Exception: java.lang.RuntimeException: android.os.DeadSystemException
       at android.app.ApplicationPackageManager.queryIntentActivitiesAsUser(ApplicationPackageManager.java:1271)
       at android.app.ApplicationPackageManager.queryIntentActivities(ApplicationPackageManager.java:1234)

So basically the system is running, the app is running, but it sees the system as dead. I stopped getting this exception after the user disabled battery optimization as described here https://dontkillmyapp.com/

vi...@google.com <vi...@google.com> #72Nov 28, 2022 09:56PM

Re-comment#71, could you please share a bugreport with us for further investigation.

tz...@gmail.com <tz...@gmail.com> #73Nov 29, 2022 02:40PM

I can't. It happened on user's phone

vi...@google.com <vi...@google.com> #74Dec 7, 2022 04:50PM

Other affected users who are still experiencing the issue are also welcome to share the information requested in comments #68 and #69 for further investigation.

kr...@gmail.com <kr...@gmail.com> #75Dec 7, 2022 08:34PM

You there us an obvious problem. To continue dragging your developer feet and keep "asking for information" you're proving how lowley you find this problem to be. You have an entire team that can easily reproduce, recreate and duplicate this battery optimization issue yet 3-4 years later it is in the "investigation" pile (which is the cold case file of you all don't prioritize this issue). What be abuse the public at large trusts you it's not really a problem? I swore by Samsung, their research team and all around device well being production. Since Covid and we all see the lawsuits, heart attacks and privacy violations rolling forth and you people at Samsung are continuing to violate privacy, your own rules and propagate shanigans as normal. This is a horrendous showing for the 2nd largest mobile phone producer on the market. I am and will continue to follow this travesty of an operating system only good for the government to keep track of and lock down the population while real issues are blatantly discarded.

vi...@google.com <vi...@google.com> #76Dec 14, 2022 11:46PM

We couldn't replicate the issue, as mentioned in comment#68 and comment#69. However, we're still looking to investigate this further with a new bug report. Requesting the users who are still experiencing the issue can share a new bugreport captured on the latest build.

vi...@google.com <vi...@google.com> #77Dec 22, 2022 03:28PM

To proceed further, requesting the affected users to check the issue on Android 10+ device and if reproducible, please share a bugreport along with the reproduction steps for further investigation. Thanks.

ad...@google.com <ad...@google.com> Jan 11, 2023 04:38PM

Assigned to vi...@google.com.

ni...@gmail.com <ni...@gmail.com> #78Jan 15, 2023 08:21PM

<script
src="

https://www.paypal.com/sdk/js?client-id=AcoTUknyBfVR3uO3GmGovEfQeQ8YGjmSyprB5h0jafMLU5YaxPT7mmTiPFUckQcv4DvESLQ6n1pTSY5g&currency=EUR&components=messages"
data-namespace="PayPalSDK">
</script>nicolaevalentinciubotaru@gmail.com

vi...@google.com <vi...@google.com> #79Jan 25, 2023 04:00PM

In order to move forward, we need the impacted users to check the problem on an Android 10+ smartphone, and if it's repeatable, we need them to submit a bug report with the necessary reproduction instructions. Thanks.

fl...@gmail.com <fl...@gmail.com> #80Jan 25, 2023 05:18PM

How about YOU check the problem and try and reproduce it?? We've submitted exactly how to do that and it's a very common issue Android users are facing on many many smartphones out there.

vi...@google.com <vi...@google.com> #81Jan 30, 2023 03:44PM

Re-comment#80, As stated in comments #68 and #69, we were unable to reproduce the issue. If you are able to replicate then please share a bug report with us.

In addition, please check if the issue can be solved by setting the App Info > Battery Saver option to No Restrictions.

tz...@gmail.com <tz...@gmail.com> #82Jan 30, 2023 03:58PM

Two years you're unable to get a dozen of OEM phones and run a full scale test? This is ridiculous. We should sue you.

fl...@gmail.com <fl...@gmail.com> #83Jan 30, 2023 05:37PM

That's the problem though, the standard Android behavior should be to not kill "foreground" apps while running in the background. But OEMs are making the default to kill them, which is against Android guidelines. You shouldn't have to go change any "battery saver" options. It should be opt-in not opt-out.

ba...@gmail.com <ba...@gmail.com> #84Jan 30, 2023 06:08PM

I've been working on Android for 10+ years, and Android development has gotten so much better in recent years, across the board. Everything is getting better all the time, and I'm so grateful for it.

But this. This issue is still a thorn in my side. I would argue it is _the_ thorn in my side. In my personal and professional projects. You don't need someone to submit a repro case. Buy a Samsung, Huawei, OnePlus, or Xiamoi device. And use it. Or read forums. Or just ask any developer.

I wish Android banned manufacturers from adding custom background restrictions or killing background processes, and that this ban was enforced by the CTS. It makes Android look bad. App developers get blamed for this behavior because users don't know what is causing it, and the behavior varies not only by manufacturer, but by Android version. Every time a manufacturer updates their devices, e.g. from Android 12 -> 13, they change their bespoke battery saving behavior, it breaks our apps, and then we get 1-star ratings and annoyed support emails. It shouldn't be our job to educate users about their manufacturer's garbage customizations, but that is what the majority of my support e-mails are about.

fa...@hotmail.com <fa...@hotmail.com> #85Jan 31, 2023 11:52AM

Yes

ul...@antavi.ch <ul...@antavi.ch> #86Feb 1, 2023 01:20PM

Finally I found this thread.

This is a problem and yet no workaround, no solution that is just mediocre is offered? I got 100.000 users sitting on my neck because of non-standard approaches to app states that basically lead to non-deterministic behavior.

That hurts users and developers.

Example: How can I keep an app running as a foreground service asking every 10min for a location?
Is that possible across *all* Android OEMs? Yes or no.

fa...@hotmail.com <fa...@hotmail.com> #87Feb 2, 2023 07:00AM

ch...@gmail.com <ch...@gmail.com> #88Feb 11, 2023 12:29AM

https://issuetracker.google.com/issues/179644471#comment44: Instead of asking developers to submit reproducible test cases to replicate, how about Google actively FIELD test the issues with the affected Android mobiled devices released by OEMs like Samsung, Huawei, etc (See

https://dontkillmyapp.com/ for more info). Asking developers to submit reproducible test cases for your LAB testing is just shirking your responsibility by passing the hard-to-do bucket to someone else.

The reason I'm not submitting any more technical info to Google's IssueTracker is NOTHING EVER GET FIXED, period! It's pointless for myself- or any other developers for that matter- to submit anything to Google to fix since we already can guess Google's responses:

- "Working as intended"; or
- "Obsolete"; or
- "Sorry, we weren't able to replicate the technical issue on our end", and so on, and so on!...

Your LAB testing to replicate Android issues is NOT THE SAME as FIELD testing the same issues on active Android mobile devices circulating in the production Android ecosystem. So, of course, you will NEVER be able to replicate the issue- that much is obvious.

If Google really want Android to thrive, then first scrap and rebuild your CTS acceptance testing procedure and actively enforce whatever "standards" you need towards OEMs regarding Android- clearly, your CTS procedure is NOT WORKING AS INTENDED! Do it not, then you're just wasting developers' times with your careless unethical approach. Sure, my words may sting a bit, but someone needs to speak up about Google's business practices that is destroying a promising open(?) mobile operating system build on top of Linux.

Regards,
C.

re...@gmail.com <re...@gmail.com> #89Feb 24, 2023 02:24PM

Folow

https://drive.google.com/file/d/1WhyvUDfzafNEQebnQCVPM6xPxEwEnGAn/view?usp=drive_web (20221211_010150.mp4)

vi...@google.com <vi...@google.com> #90Feb 24, 2023 06:10PM

Re-

comment#89

: Please grant permission to access the gdrive link provided in

comment#89

. You may share the folder with android-bugreport@google.com, then share the link here. If you can share the bugreport along with the video, it would be really appreciated.

vi...@google.com <vi...@google.com> #91Mar 15, 2023 05:27PM

The drive link provided in comment#89 is still not accessible.

ye...@gmail.com <ye...@gmail.com> #92Mar 16, 2023 03:52PM

It's really anoyone. I tought making an alarm will be impossible on iOS and easy on Android but finally because of that I have 100% coverage on iOS and random pourcentage of succes for Android because my app get killed by those "optimisation" thing... 😭

ja...@gmail.com <ja...@gmail.com> #93Mar 20, 2023 03:35PM

Pienso que esta bien

ne...@gmail.com <ne...@gmail.com> #94Mar 25, 2023 01:07AM

Is it possible that are restricting, because some background process or how you call it, are just way to invade the privacy?
and now you are complaining with google because it doesn't allow it? is this the case?

mi...@gmail.com <mi...@gmail.com> #95Apr 2, 2023 04:10AM

Android beta decypt

ti...@gmail.com <ti...@gmail.com> #96May 5, 2023 02:27PM

Per comment https://issuetracker.google.com/issues/179644471#comment69 I have shared a bug report with android-bugreport@google.com and included some additional observations.

We do NOT see the issue when we disable battery optimization. Battery Optimization freezing an active VPN while it is in the background is problematic.

https://drive.google.com/drive/folders/1raYBwR0FzR6SHMZ5gQFgyV0x142Gs3ao?usp=sharing

[Deleted User] <[Deleted User]> #97May 13, 2023 09:34AM

دانلود بهترین های پورنو

[Deleted User] <[Deleted User]> #98May 13, 2023 09:38AM

عشق واقعی💞

fa...@hotmail.com <fa...@hotmail.com> #99May 26, 2023 11:57PM

👨‍💻

le...@gmail.com <le...@gmail.com> #100Jul 1, 2023 11:24AM

Включити провокацію.автоматично.

si...@gmail.com <si...@gmail.com> #101Aug 9, 2023 02:12PM

01425706919400

be...@gmail.com <be...@gmail.com> #102Aug 9, 2023 04:36PM

This isn't actually a software bug, it's Google failing to enforce their own OEM policies. Maybe we do need to talk to their legal team.

pu...@gmail.com <pu...@gmail.com> #103Oct 10, 2023 08:51AM

What's tragic is that some manufacturers are breaking Android as it is documented with their clever 'save the battery' customization. This should have been addressed like 10 years ago with a hammer to prevent them from doing that but here we are... It results in broken app, angry users and developers, and the existence of dontkillmyapp which is just band aid and not even 100% complete.

co...@gmail.com <co...@gmail.com> #104Nov 9, 2023 12:50AM

I'm so unbelievably sick of my apps not working when I need them to. I'm tired of getting notifications for YouTube livestreams half an hour late, I'm tired of my tile trackers notifying me that I forgot my keys or wallet halfway across town instead of just a few feet away, and I'm tired of receiving vital emails and texts hours late.

[Deleted User] <[Deleted User]> #105Nov 28, 2023 03:00PM

I've encountered the same problem with Bluetooth battery optimisation.

Message last modified on Nov 28, 2023 03:05PM

ma...@gmail.com <ma...@gmail.com> #106Dec 29, 2023 12:03AM

Kiero que funcione

aa...@gmail.com <aa...@gmail.com> #107Jan 24, 2024 03:06PM

fa...@gmail.com <fa...@gmail.com> #108Apr 20, 2024 11:16PM

تل

fa...@gmail.com <fa...@gmail.com> #109Apr 20, 2024 11:18PM

fawaz4449@gmail.com

de...@gmail.com <de...@gmail.com> #110Apr 20, 2024 11:19PM

tobby

On Sat, Apr 20, 2024, 7:18 PM <buganizer-system@google.com> wrote:

- Show quoted text -

co...@gmail.com <co...@gmail.com> #111May 1, 2024 09:43PM

hakkınızda savcılık suc duyurusu verildi

ro...@gmail.com <ro...@gmail.com> #112May 13, 2024 12:34PM

af...@gmail.com <af...@gmail.com> #113May 26, 2024 07:52AM

I love the blatant ignorance or incompetence of the android team

Over 3 years later and this issue still exists.

I run an S21FE with android 14 and despite ensuring I've given all of the accessible options to exclude the app I need from battery saving methods Samsung continues to break functionality and as such I am unable to gather and process valuable information.

This issue was less prevalent with my previous LG devices.

Android team needs to tell OEMs either allow users to exempt any app of their choosing from any task killing/battery saving methods of we choose or revoke any and all licenses to that OEM to use Android

I'm sick of being dictated as to what I can do with my device by a manufacture when it has the inherent capability.

Wake up team or watch us all tell android to GF itself.

I will be suspending all Android development going forward with my partners until this issue is fixed.

si...@gmail.com <si...@gmail.com> #114Jul 26, 2024 11:34AM

@sintayew Gashaw

jo...@gmail.com <jo...@gmail.com> #115Aug 19, 2024 09:02AM

vida

pl...@gmail.com <pl...@gmail.com> #116Aug 25, 2024 01:40PM

Untitled project

pl...@gmail.com <pl...@gmail.com> #117Aug 25, 2024 01:41PM

Untitled project

ni...@gmail.com <ni...@gmail.com> #118Sep 3, 2024 11:57AM

This is killing my ability to use my new tablet for art. My files are constantly being corrupted by the app sleeping during automates.

lo...@gmail.com <lo...@gmail.com> #119Sep 3, 2024 12:19PM

You might want to use AtomicFile or SQLite + frequent saves (e.g. after each action) to be shutdown resilient.

ma...@gmail.com <ma...@gmail.com> #120Jan 29, 2025 09:53PM

Any updates on this? This issue still exists nearly 4 YEARS later!!

in...@gmail.com <in...@gmail.com> #121Mar 1, 2025 03:50PM

Comment has been deleted.

Message last modified on Mar 1, 2025 03:51PM

ro...@gmail.com <ro...@gmail.com> #122Mar 1, 2025 03:52PM

I'm not a developer, not even close. I'm a user. I will never leave a bad review for apps anymore after reading this if it relates to crashes or failed notifications. What I will do, as my own tiny protest, is to submit AS MANY bug reports as I can, ideally hundreds per day if I'm bored, just to inundate android with garbage. I cannot believe Google and Android let Samsung do whatever they want, violate policies, etc. Android, you are trash for letting these type of bugs exist for half a decade and just keep asking for information. You have the information. You are wasting everybody's time and taking food off developers tables because their apps don't work because of your negligence. I was always a steadfast Android fanboy, but I don't think I'm going to buy an android for my next device, and I will be suggesting to anyone who listens that they do the same. I hope you and your uncaring company have the day you deserve, every day. Kindly choke on the money you earn. Good day, and goodbye. 🖕

Issue 179644471

Description

Issue summary

Comments

ja...@google.com <ja...@google.com> #2Feb 8, 2021 08:53PM

pe...@gmail.com <pe...@gmail.com> #3Feb 16, 2021 12:56PM

ja...@google.com <ja...@google.com> #4Feb 16, 2021 05:39PM

What

More information

Where

Build and device data

pe...@gmail.com <pe...@gmail.com> #5Feb 17, 2021 10:23AM

ja...@google.com <ja...@google.com> #6Feb 17, 2021 03:25PM

What

More information

Where

Build and device data

sm...@gmail.com <sm...@gmail.com> #7Feb 19, 2021 04:44AM

co...@gmail.com <co...@gmail.com> #8Feb 19, 2021 09:11AM

[Deleted User] <[Deleted User]> #9 Restricted Mar 6, 2021 10:37PM

sa...@google.com <sa...@google.com> Mar 29, 2021 07:04PM

lb...@gmail.com <lb...@gmail.com> #10Mar 29, 2021 10:52PM

ad...@google.com <ad...@google.com> #11Mar 30, 2021 11:13AM

se...@gmail.com <se...@gmail.com> #12Mar 30, 2021 11:26AM

br...@gmail.com <br...@gmail.com> #13Mar 31, 2021 08:09PM

pe...@gmail.com <pe...@gmail.com> #14Apr 2, 2021 12:14PM

se...@gmail.com <se...@gmail.com> #15Apr 5, 2021 10:21PM

se...@gmail.com <se...@gmail.com> #16Apr 5, 2021 10:23PM

What

More information

Where

Build and device data

ka...@gmail.com <ka...@gmail.com> #17Apr 6, 2021 07:11AM

pe...@gmail.com <pe...@gmail.com> #18Apr 8, 2021 02:14PM

What

More information

When

Time and frequency

Where

Build and device data

tz...@gmail.com <tz...@gmail.com> #19Apr 11, 2021 08:34AM

ji...@google.com <ji...@google.com> #20Apr 16, 2021 01:42AM

What

More information

When

Time and frequency

Where

Build and device data

se...@gmail.com <se...@gmail.com> #21Apr 16, 2021 05:43AM

ji...@google.com <ji...@google.com> #22Apr 23, 2021 12:17AM

What

More information

Where

Build and device data

ar...@gmail.com <ar...@gmail.com> #23May 25, 2021 01:21AM

me...@gmail.com <me...@gmail.com> #24Jun 19, 2021 09:52AM

What

More information

When

Time and frequency

Where

Build and device data

mi...@gmail.com <mi...@gmail.com> #25Jun 30, 2021 10:35AM

mi...@gmail.com <mi...@gmail.com> #26Jun 30, 2021 10:41AM

di...@gmail.com <di...@gmail.com> #27Jul 6, 2021 04:45PM

sa...@gmail.com <sa...@gmail.com> #28Jul 31, 2021 06:51AM

What

More information

Where

Build and device data

gr...@gmail.com <gr...@gmail.com> #29Aug 2, 2021 06:09PM

ad...@gmail.com <ad...@gmail.com> #30Aug 5, 2021 08:31AM

te...@gmail.com <te...@gmail.com> #31Dec 7, 2021 07:45PM

What

More information

Where

Build and device data

ra...@gmail.com <ra...@gmail.com> #32Dec 12, 2021 03:08AM

[Deleted User] <[Deleted User]> #33Feb 4, 2022 03:35PM

gr...@kochaniak.com <gr...@kochaniak.com> #34Feb 4, 2022 03:47PM

[Deleted User] <[Deleted User]> #9
Restricted
Mar 6, 2021 10:37PM

ta...@gmail.com <ta...@gmail.com> #55
Restricted+
May 3, 2022 08:42PM