This is interesting enough to deserve a separate post:
Under Lollipop I found that Google Play Services was using a LOT of data on a regular basis, so I had restricted its background data and that solved the problem. (I had to reenable it temporarily to actually use the Play Store app but that was easy enough.) We just got the Marshmallow upgrade, and it appears that Google caught onto this solution and found a way to prevent it!
It's not obvious at first, but Play Services no longer even appears on the app listing under Data, so there's nothing to tap on and restrict. The app is still present of course, and it does show up on the Battery list where you can see that it uses a fair amount of power too -- there's even a figure there for data usage, but you can't do anything with it. And of course Play Services can't be battery-optimized either, so now it can just do whatever it wants with your phone at any time.
How do you suppose Google would explain this neat little sleight-of-hand?
Under Lollipop I found that Google Play Services was using a LOT of data on a regular basis, so I had restricted its background data and that solved the problem. (I had to reenable it temporarily to actually use the Play Store app but that was easy enough.) We just got the Marshmallow upgrade, and it appears that Google caught onto this solution and found a way to prevent it!
It's not obvious at first, but Play Services no longer even appears on the app listing under Data, so there's nothing to tap on and restrict. The app is still present of course, and it does show up on the Battery list where you can see that it uses a fair amount of power too -- there's even a figure there for data usage, but you can't do anything with it. And of course Play Services can't be battery-optimized either, so now it can just do whatever it wants with your phone at any time.
How do you suppose Google would explain this neat little sleight-of-hand?