When you go around flashing ROMs, you have to expect that things might occasionally go wrong. The previous milestone build of CyanogenMod 11 seemed fine at first, but then Google released the 4.4.3 update. Devices that were eligible (Nexus phones, for example) started producing update notifications, which shouldn't happen on a custom ROM. This was more troublesome than a notification that wouldn't go away, though.
There should be no doubt, Google is getting ready to make a lot of announcements at I/O. If we've learned anything from past experiences, Google starts packing its apps full of surprises in the weeks leading up to the big show. The latest update to Play Services started rolling out yesterday and it has grown by a whopping 4 MB, almost 30% larger than the previous version. There's obviously a lot of stuff to look at, so let's just jump right in.
Every so often, something shows up in the Android Police tip box that seems just a little too wild to be true. Such was the case with the information that led us to publish this story. After all, if someone simply claimed that Google was forcing device OEMs to use up-to-date software in order to get access to Google Mobile Services, you'd probably find such an allegation dubious at best. Even if they included moderately convincing evidence that this was the case.
You might not have noticed, but a fresh version of Google Play Services started silently rolling out a few days ago. Google I/O came and went without an Android version bump because Google wanted to send a message: Google Play Services is the single most important APK on your device. It was recently used to roll out Google Play Games, cloud app data storage, and the fused location provider.