• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

4.4.2?

The Google 404 page is amusing though.

Reminds me of a beta BIOS I was testing way back when that had an "otherwise" in the list of known errors that output "Something funny just happened" to the console and executed a processor HALT. I think I prefer Google's take on the same situation :-)

PS: the same beta BIOS had the ubiquitous "press any key to continue" appended to almost all known errors, including the one that said "Error: missing keyboard"...
 
John Bean said:
The Google 404 page is amusing though.

Reminds me of a beta BIOS I was testing way back when that had an "otherwise" in the list of known errors that output "Something funny just happened" to the console and executed a processor HALT. I think I prefer Google's take on the same situation :-)
Click to expand...

I love the title: Error 404 (Not Found)!!1
 
codesplice said:
I love the title: Error 404 (Not Found)!!1
Click to expand...

Nobody wins at the Internet like Google.


4.4.2 seems to be running OK. I can't give an honest battery life test because my day-to-day use has been extremely inconsistent, especially now that I've started playing Deer Hunter 2014 extensively and also because my home internet has been down since Sunday, so I've been using my phone's 4G as my primary internet connection rather than my laptop.
 
Finally got 4.4.2 this side of the pond :D

Download was somewhere around 52MB. The upgrade ran fairly quickly and painlessly - way, way quicker than 4.3 -> 4.4.

Haven't found any differences at all - but then, I guess it was just a bugfix release.
 
Im still waiting for it on my N4. Had the N10 update a few days ago.

On a side note, Nova Launcher has the new clear bottom buttons which looks good :)
 
Got 4.4.2 on my Nexus 7 last night and the Exchange problem is FIXED!!! Trying to force it now on my N4.

** Just forced the OTA on my N4 via the Google Services Framework trick. Downloaded and installing.

**** Installed and Exchange problem on my N4 is now fixed. Thank you Google.
 
john30308 said:
Got 4.4.2 on my Nexus 7 last night and the Exchange problem is FIXED!!! Trying to force it now on my N4.

**** Just forced the OTA on my N4 via the Google Services Framework trick. Downloaded and installing.
Click to expand...

Good result on the N7, but I hope you haven't made problems for yourself by using that "trick" - it is not recommended by insiders within the development team for all sorts of reasons. But you may be lucky, let's hope :-)

If you couldn't wait for the OTA a better option would have been to download the appropriate zip and sideload it rather than (potentially) messing up other bits of the system.
 
John Bean said:
Good result on the N7, but I hope you haven't made problems for yourself by using that "trick" - it is not recommended by insiders within the development team for all sorts of reasons. But you may be lucky, let's hope :-)

If you couldn't wait for the OTA a better option would have been to download the appropriate zip and sideload it rather than (potentially) messing up other bits of the system.
Click to expand...

Really? I hadn't heard that. I've used it for just about every update... :)

Seriously, what kind of problems can it cause? Just curious.

BTW, keeping fingers crossed, but all appears well with the 4.4.2 update on my N4, and Exchange is working properly again.
 
Here's the quote from Dan Morrill of Google:
Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)

How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.

Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.

All of this can be avoided by just doing an 'adb sideload' if you are impatient.
Click to expand...

Source
 
john30308 said:
Really? I hadn't heard that. I've used it for just about every update... :)

Seriously, what kind of problems can it cause? Just curious.

BTW, keeping fingers crossed, but all appears well with the 4.4.2 update on my N4, and Exchange is working properly again.
Click to expand...

Google Engineer Dan Morrill Sheds Some Light On The Nexus OTA Process, Urges You To Never Clear Google Service Framework Data

From Dan Morrill:
Doing this changes the primary ID by which Google knows your device. As far as the servers are concerned, the device was basically factory reset. There are many downstream effects of this, but a big one is that this invalidates the tokens used by any app that uses GCM (which is nearly all the Google apps, and a ton of third-party apps.)
How apps react to GCM IDs changing varies by app. With Play Store you have to log out and log back in, I think Gmail usually handles it transparently eventually but won't get new mail notifications for a while, etc. Some apps you may have to clear data on to recover. All apps will simply stop getting GCM push-messages, until they get a new GCM ID; some do this frequently, others rarely, and some apps use the GCM ID as an ID on their own servers (as it is opaque and basically random), so other things besides push messages may not work.
Nothing bursts into flames, but it makes a ton of nuisances on the device, including some that can look pretty mysterious. Your mileage will vary depending on what apps you use.
All of this can be avoided by just doing an 'adb sideload' if you are impatient.
Click to expand...
 
You must log in or register to reply here.
Back
Top Bottom