[Android General] marcel18feh:
I think I can say ... everyone here knows the native google services app, right? Well, this app performs structural operations on the system, plus functionalities. All this, however, in the background, and sometimes (with or without mobile data). In fact, every operation of this app is performed without such data, but, on the other hand, with the data attached, then [it] may come to consume. Several brands from manufacturers such as Samsung, LG, Sony etc ... allow the user to restrict the use of mobile data in the background of some apps (natives or not, which consume a lot of franchise or not). And these manufacturers allow two types of restrictions in the background. A: general, aiming not to exceed the limit of data used of the franchise, two: specific, whereby the user manually restricts or de-restricts the apps that are or are not consuming data (internet). Now, one thing needs to be said, depending on the version of android, of course, the place where the user can restrict apps from consuming rem background may be different. So to use a standard reference - in my understanding - I will use Samsung as a manufacturer reference, and the Android versions between 4.1 and below 5.0, aiming as I said, on average. It should be noted that in every app (native) can be made such a restriction. Of some native apps (not counting offlines, for entertainment), they depend on all the stability of the operating system, and not only, but they do not use any mobile data, even when connected. Returning to stick with google services, you need to expose two of your own characteristics. [It] does not use any data in the foreground (since it can not be accessed internally, since it has no icon in the application grid), and the second is that [it] uses data in the background (regardless if you are inside the play store "downloading something" and, or if automatic notification update synchronization is disabled).*The problem is that if the user restricts the background data consumption (specific form) of the play store app, for example, if he [user] decides to re-enable such consumption of the app referred to, it will do so without any problems. It is only the user (after accessing it internally, and spending a few kb / s of data browsing "in the store") to go to the mobile data consumption meter on your device and the list with the most consumed internet apps, click on top of the app you want the restriction (in this case, the play store) and choose this option. However, if the same restriction for the google services app happens the opposite. The primary constraint becomes irreversible! At least, that's what I said, I'm not in this forum, maybe someone points out an effective deal. Anyway, let's see why this [reported] is given. Remember the explanation, where he said: just spend a few kb / s, for this consumption to appear in the meter of consumption, and be clicking on top of such app? I was referring to the play store, I made it clear ... or not? Well, since google services does not use anything in the foreground, it will be impossible to make [such an app] appear on the referenced meter. This implies the possibility of reactivating consumption in the background (if restricted), not only referring to google services, but all apps that do not consume anything in the foreground.