Score representation looks kinda unfair and misleading about dont-kill-my-app HOT 1 CLOSED

Many thanks for your feedback. In fact we are getting surprisingly many support request from angry people who's alarms or background services do not work and after a lot of effort on debugging we find out that they simply turned the background restrictions ON - not even knowing why.

So the question is should there be an option to break normal functionality off apps in the first place. Even when this option would be all RED and users will be warned "only press this when you know what you are doing" still users will keep enabling it. Maybe it should be called "Break the app's core functionality" - because this is exactly what it is doing.

IMHO this option is unnecessary and evil. After all you can always uninstall the app if it is consuming too much battery. Nowadays for any app category there are dozen alternatives - you can choose the best app which does not consume unnecessary resources.

Most user do not even know what background processes mean and even for me as programmer is hard to assume what features of an app would be broken and what would keep work if I would enable such option.

So IMHO this option should not exists in the system. Why did Google implement it? Maybe because they still try somehow standardize the battery management on Android and they hope this option will keep more vendors from modifying the OS? But as in the other cases as with doze mode this won't be the case IMHO..

from dont-kill-my-app.