Is everyone receiving the upgrade to 4.4.2?

What is the risk of trying this method? I have done this before on previous updates with no issues but I have seen posts about downfalls. I still don't have it in Tallahassee but I haven't had any issues with 4.4 so I'm willing to wait for it to appear.

The risk isn't with force closing Google services framework, the risk is with clearing the cache for the Google services framework. It essentially creates a new device ID for your device so Google Play and many other apps will likely see your device as a new one rather than the existing one that it is. That's at the very least, the article below by a Google engineer suggests other bad things can happen behind-the-scenes that are not necessarily visible to you.
Google Engineer Dan Morrill Sheds Some Light On The Nexus OTA Process, Urges You To Never Clear Google Service Framework Data
 
i guess there's a lesson about patience (which i'm sure i will continue to ignore...); got the update today (12th), and all is well (so far...)
 
I tried the force stop trick a couple of times and nothing happened. When I got home this afternoon the notice was on my 2012 Nexus 7. All is good so far, I have no idea what is supposed to be different after this update, I wasn't having any problems before it.
 
My nexus 7 (2012) USA got the ota 4.4.2 update yesterday - took a long time to load. Everything seems to be running faster and smoothly, but the battery continues to run down faster than it did with jelly bean 4.3.
 
Got the OTA today and installed without issues and everything seems to be working fine. I'm in Charleston, WV.

Posted via Android Central App
 
Got it in my notification area. Not installed yet.
Waiting for MX Player update for this app dose not work on 4.4.2.

Regards!

SLo
 

Forum statistics

Threads
955,708
Messages
6,965,562
Members
3,163,365
Latest member
msdonna