2 ms·
That's location, not execution. Effectively Google is preventing 3rd party apps from running persistently in the background by limiting location (because that's
by dcow 9y ago
That's location, not execution. Effectively Google is preventing 3rd party apps from running persistently in the background by limiting location (because that's how some apps would "cheat"--you could get around a user explicitly stopping your app if you registered for background location updates, similar scenario on iOS until they added the extra status bar informing the user when apps are using background location). Because play services can run persistently (how do you think GCM works) it doesn't really affect their stuff.
But it's good to see Google closing that gap because it's one of the ways naughty apps would piss in the pool for everyone else. And it's one of the criticisms a lot of people had against Google's upper hand.
- Ajedi32 9y agoAh, fair point. I looked into it further, and I believe you're correct that Play Services is currently excluded from the background execution limits (but not location limits) in Oreo. That's not an arbitrary exception on Google's part though; the reason it's excluded is because Play Services targets Marshmallow, not Oreo, and the new background execution restrictions are currently only enforced for apps targeting Oreo (though there's a switch in settings to manually enforce them for individual apps, and you can flip that switch for Play Services if you want).
- dcow 9y agoI'm curious how they'll handle GCM. Maybe it will get registered as a VOIP or messaging app meaning the system will not remove its Services.