> This reads like a comment written by someone not aware of the depth of the problem.

> Oh please.

> Or you don't understand that?

What I understand is that your posts have wandered between being dismissive, condescending, and argumentative. I've ignored that to this point, but since you've been insisted on being consistently so in 3 messages straight, I'm calling you on it.

If you have a point other than being argumentative, it's not well made.

You're complaining that my replies have nothing to do with the original point... then typing up a screed about my tone?

Especially after starting your initial reply to me with

>I have absolutely no idea what any of this has to do with my original point or my reply.

Do you know what dismissive means?

-

If I come across as dismissive it's because you really don't seem to know what you're talking about, and if anything this attempt to deflect from the fact just cements that.

Me telling you that your comment comes across as being written by someone not aware of the depth of the problem is exactly what it sounds like, you said things that strongly implied you were not aware of the deeper background to this post.

If you choose to take it as a personal slight, be my guest.

-

Likewise if you're going to play the "music players can be crypto miners" card I'm going to be dismissive of that too, it's a lazy attempt to distract from the problem.

Of course apps can be bad actors. Jumping to the most fear-mongery example possible is just that... fear mongering.

For every app mining cryptocurrency, there's 10 more that are just poorly behaved in respect to battery life.

Trying to act like OEM's attempts to lock down background apps should be dictated by the former rather than the latter is something I'll gladly dismiss. It's nonsense.

So you’re saying OEMs take no efforts to optimize for battery life. That’s kind of an extreme position to take. We know they are working on battery life because updates have extended battery life in deployed assets.

What? No? Where did I say "OEMs take no efforts to optimize for battery life"? Usually you try and be subtle about a strawman, no?

I said overbearing app killers aren't optimizing for battery life.

Do you think that's the only knob for battery life? I'm currently working on an unreleased Android device at our company, the number of knobs we have to turn for battery life is insane. Throttling behavior, optimizing existing services, screen off behavior, etc.

App killers don't work, again, that's why vanilla Android devices consistently top battery life charts. Forcing apps to start up more often, breaking user functionality, it's not a real solution.

Android already has built-in management of background services and has had it for half a decade: (https://developer.android.com/training/monitoring-device-sta...)

The defaults scope of background processing is already very tight on Android, breaking that already limited scope for little to negative gain isn't helping anyone but themselves.