I, like a number of users, have encountered the awful android OS data drain which has taken a crappy 1.6GB of data this month.
There's been a lot of thoughts and theories and whilst I don't claim to know the exact reasoning I'd like to share my solution nonetheless.
If you have background data turned on but have selected any number of apps to be restricted individually, this error occurs. I've no idea why but the android OS starts becoming a data hog when this mix of settings is in place.
So if you're having a data drain caused by android OS then make sure all your apps have background data enabled or you'll end up using more data than you need. It's ridiculous as it completely undermines the point of the feature. I've seen some users claim that apps instead are logged as pushing data through the OS if restricted via background, but it's really unclear if that's true. Either way this will give you a proper reading so at least you know what data is being used by what app rather than the ambiguous android OS.
There's been a lot of thoughts and theories and whilst I don't claim to know the exact reasoning I'd like to share my solution nonetheless.
If you have background data turned on but have selected any number of apps to be restricted individually, this error occurs. I've no idea why but the android OS starts becoming a data hog when this mix of settings is in place.
So if you're having a data drain caused by android OS then make sure all your apps have background data enabled or you'll end up using more data than you need. It's ridiculous as it completely undermines the point of the feature. I've seen some users claim that apps instead are logged as pushing data through the OS if restricted via background, but it's really unclear if that's true. Either way this will give you a proper reading so at least you know what data is being used by what app rather than the ambiguous android OS.