You probably don't know this, but thankfully the super snoops over at Android Police spotted this one early. The most recent updates to Google Play Services – the driving force behind pretty much everything Google does on your Android – has a sneaky and potentially dangerous change to Device Administrators: namely, that it disables Android Device Manager as a Device Administrator, meaning you cannot access that service's remote lock and wipe feature. So if your phone gets stolen you can't do anything about it.
Why on earth Google would make this change without letting users know is absolutely beyond me, especially considering the overwhelmingly positive response Android Device Manager received when it wielded the power to lock or wipe your phone in the event of it being stolen. In a crazy twist of logic, Google seems to have decided that users wouldn't mind having that function turned off without their knowledge.
Fortunately it's a simple enough thing to fix, once you know it is a problem. So please, read this article, get ADM working on your device again, and then spread the word so everyone you know is aware of this change and can take the necessary steps to protect themselves (again). It's actually quite jarring to know the peace of mind I've enjoyed since I enabled ADM to lock or wipe my device has been a sham since the last update. The change affects the Google Play Services update with version numbers 4.0.31 and the previous one 4.0.30.
To fix it, just go into your Settings and then Apps. Scroll down to Google Play Services and check your update number. If you have one of the affected updates then you'll need to go back to Settings and into Security to find your list of Device Administrators. You may then notice that Android Device Manager is no longer enabled, meaning if your phone is stolen and you try to use ADM to remote lock or wipe your device, you'll get absolutely nowhere. So tick that box, curse Google for their stupidity and tweet this article, share it, write a FB status update, yell out to your neighbor and fix it on your girlfriend's phone, because someone needs to be looking out for us, and it certainly doesn't seem to be Google.
The good news is not everyone is affected, even if they have one of the GPS updates responsible. I did, and, to my horror, ADM was indeed disabled as a Device Administrator. So please make sure you are protected and that everyone you know who is using ADM as a security contingency plan knows about this problem. If you have a previous version of GPS, keep an eye on future updates because this change may affect you when the update does arrive on your device.
Do you have one of the affected updates? Did you have to re-enable Android Device Manager as a Device Administrator?