IssueTracker

Which app are you using? Please share its Play Store link. Also mention the steps to be followed for reproducing the issue with the given app.

Can you share a bug report, after reproducing the issue ?

Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)

Android bug report
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report  file to this issue.

Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.

NOTE: Please upload the files to Google Drive and share the folder to android-bugreport@google.com, then share the link here.

With all due respect, I do not have additional data to share. I can only point you to one of many complaints already made regarding this issue:

* https://www.theverge.com/2018/7/25/17614014/vlc-blacklisting-recent-huawei-devices-negative-app-reviews
* https://twitter.com/videolan/status/1022354204025860097

Global developer

Why are you fuck tards in my account. I’m sick of it. Did you get a good look at all my nude photos, as well as my children’s photos. Stop going through my private information. Especially my photos of my children, when they were just little babies and were nude. You make me sick. Apple   Google. Suddenlink. Sprint. And the rest of you sick perverts. Stay off my 9 year olds phone. Sickening

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

We have CTS that OEMs pass in order to ensure compatibility, we are not sure if this request is for better CTS or just a complaint that aggressive battery management breaks some apps' core functionalities.

What use cases you want supported without having to get white-listed from battery optimizations?

This is a request for a better CTS to ensure OS core functionality is not selectively broken out of the box. If users chooses to limit certain functionality (running in the background, requesting locations, etc.), they can do so from the OEM's battery optimization settings. But having it disabled by default for a newly installed app reflects poorly on the app and the developer. Additionally, exclusive whitelisting of popular apps is poor practice and should be reprimanded by Google. There must be a policy ensuring that all apps are treated equally.

Here are some use cases that are not possible today without explicit whitelisting (tested on Huawei P20 Lite running Android 8):
* Receiving a geofence exit from Google Play Services (the broadcast is dropped since it is proxied via Huawei's powerginie manager).
* Requesting sensor data using a foreground service (wakelocks are proxied as well and released upon screen off).
* Receiving activity transition events from Google Play Services (again, broadcasts are dropped).
* Requesting location fixes via Google Play Services by running a foreground service (wakelock and broadcast issues).

Huawei uses powerginie to proxy all broadcasts and wakelocks through its service as soon the screen goes off, and selectively permits apps based on package name whitelisting, app type (email, instant messaging, clock), network connectivity, etc.

For example: Huawei uses a launch mode for apps, by default automatically handled by Huawei. The default automatic launch mode prevents starting in the background (as foreground service), disables the working of the AlarmManager. Basic functionally correctly present in an app according to the Android specifications won't work without an explicit action of the end user to set the launch mode to manual and allow starting in the background, running in the background and starting other apps in the background (the last one for accessing another app service).

It is impossible to explain to all app users on Huawei (or other phone models with similar agressive background killing behavior) to manually set the launch mode. Apps that respect the latest Android rules for doze and background processes, won't work correctly. This has nothing to do with the white-listing from battery optimizations. Even that white-listing won't work if the launch mode isn't set correctly.

The main point is not that some apps' core functionality is broken, the main point is that Android functionality isn't working as described in the specifications if the end user doesn't arrange certain settings manually.

For Huawei this applies to the devices with Android 8 and Android 9.

Someone has made a site that documents all of the transgressions of various OEMs:

https://dontkillmyapp.com/

For example, some Nokia devices kill every background process and cancel all AlarmManager alarms after screen has been off for 20 minutes, even if that process runs as foreground service. This includes apps like alarm clocks, which is really bad (it prevents 3rd party alarm clocks from even waking you up in the morning). I think that things like this should definitely not pass the CTS.