4.4.2?

[kwalla]

Interesting.. I just got the OTA update, but it clearly said 4.4.2. It was about 50mbs -- installing as I type.

I never got 4.4.1 -- hope that doesn't matter!

Edit: added a screenshot post update. It is 4.4.2.

K

 

[codesplice]

Doesn't look like anything too exciting (but you know I'm about to flash that sucker anyway).

Deets: Sprint Says The Nexus 5 Is Getting An Update To KOT49H Today, But What Happened To KOT49E? [Update: KOT49E May Have Been Pulled]

Enhancements/Fixes
- Fix for clearing the VM Indicator
- Fix for delivery of the VM Indicator
- Various additional software fixes
- Security enhancements

Download:
http://android.clients.google.com/p....signed-occam-KOT49H-from-KOT49E.0ec632f5.zip (from 4.4.1)
http://android.clients.google.com/p....signed-occam-KOT49H-from-KRT16S.4f6d2fc7.zip (from 4.4)

 

[xploPR]

I also got the notification now but i can't flash it, because my recovery is cwm, last time i tried 4.4.1 it didn't let me, it aborted the OTA. so i had to wait for a flashable zip.

 

[codesplice]

I also got the notification now but i can't flash it, because my recovery is cwm, last time i tried 4.4.1 it didn't let me, it aborted the OTA. so i had to wait for a flashable zip.

CWM should be able to flash it - the catch being that any file systems that the patch updates (most likely /system, possibly the radio firmware as well) have to be unmolested. So no root, no hybrid radios, no LTE, etc.

That said, I'm in the process of reflashing the 4.4 factory image so I can then do the KRT16S -> KOT49H update.

 

[lion7718]

I also got the notification now but i can't flash it, because my recovery is cwm, last time i tried 4.4.1 it didn't let me, it aborted the OTA. so i had to wait for a flashable zip.

The OTA update worked for me with TWRP from 4.4.1 to 4.4.2...
I thought it might fail also, but it didn't.
4.4.2 was 1.8MB on my N4.

 

[Dolmangar]

Received it tonight as well. So far Widget Locker is totally messed up now, haven't noticed anything else. It was only partially messed up with the previous update.

 

[lunatic59]

I flashed it with CWM, but with each update I lose root and recovery and have to reflash each. :dontknow:

 

[jhawkkw]

I flashed it with CWM, but with each update I lose root and recovery and have to reflash each. :dontknow:

SuperSU pro survived root when I took the update on my Nexus 7, but it does seem to break it in every other case.

 

[codesplice]

I flashed it with CWM, but with each update I lose root and recovery and have to reflash each. :dontknow:

That's normal. Anytime you flash an ota update, the system partition gets overwritten (which is where root lives). The recovery gets overwritten as well because it effectively bootstraps itself.

 

[andruoid]

Just received 4.4.2 (KOT49H) OTA as well, installing as we speak. So far i have had zero issues with 4.4 and battery life is great

 

[John Bean]

I just ran the OTA too and it worked fine - eventually. It was by far the slowest update I'd seen - excluding the original 4.3 to 4.4 that never ended and broke my phone.

When I started the 4.4.2 OTA the battery was at 85% (I checked) and when it finished the phone was warm to the touch and the battery was at 53%, so don't take this OTA unless the battery is well charged.

This OTA seems to be doing a lot of work; maybe Google have learned something from the unacceptable failure rates of recent OTAs... Maybe.

 

[bjacks12]

I just ran the OTA too and it worked fine - eventually. It was by far the slowest update I'd seen - excluding the original 4.3 to 4.4 that never ended and broke my phone.

When I started the 4.4.2 OTA the battery was at 85% (I checked) and when it finished the phone was warm to the touch and the battery was at 53%, so don't take this OTA unless the battery is well charged.

This OTA seems to be doing a lot of work; maybe Google have learned something from the unacceptable failure rates of recent OTAs... Maybe.

Did you go straight from 4.4 to 4.4.2 or did you get 4.4.1 first?

 

[lunatic59]

It's just a theory, but I think if you are using ART instead of Dalvik it takes much longer to update the apps after and OTA.

 

[jhonb]

Mine upgraded from 4.4 to 4.42 in about 5 minutes. 1% or 2% drop in battery

 

[bjacks12]

It's just a theory, but I think if you are using ART instead of Dalvik it takes much longer to update the apps after and OTA.

Based on my experiencing on updating from 4.3 -> 4.4 KRT16O-> enabling art -> KRT16S -> KOT49E, I would have to say you are correct. Just deciding now if I want to sideload 4.4.2 or actually wait and try a regular OTA for once.

 

[SiempreTuna]

Still no sign of 4.4.1 or 4.4.2 here

 

[John Bean]

It's just a theory, but I think if you are using ART instead of Dalvik it takes much longer to update the apps after and OTA.

That sounds plausible. I had not updated to 4.2.1 and was complete stock with locked bootloader but I had switched to ART.

The "optimizing apps" phase took forever, so slow that I though it had crashed at one point. That's what seems to have taken up most of the time and battery.

PS: This morning I am seeing noticeable performance improvements in a couple of apps I use regularly, mainly in the general responsiveness. Whatever it was "optimizing" for half an hour seems to have had a good result

 

[lunatic59]

I think the long time it takes to optimize apps after an update when using ART is a small price to pay for the significant performance enhancements. I'd do a comparison by restoring a 4.4.1 nandroid, using Dalvik and timing the update to 4.4.2, but I'm too lazy.

 

[bjacks12]

Just got the OTA notification, letting it install right now. I'm on ART, so it should take a while.

This is the only time, excep for the 4.3 update, that I have done an OTA. The phone came with 4.2.2 on it, OTA'd to 4.3, but then I flashed system images for KRT16O and KRT16S, then sideloaded the update for 4.4.1.

 

[codesplice]

I got the OTA last night after I somehow managed to break everything. Ended up with a full wipe, flashed the KRT16S image, and received the KOT49H OTA while I was redownloading apps from the Play Store.

Pretty sure that's also the first time I've ever actually received an OTA instead of sideloading it.

 

[jhawkkw]

4.4.2 factory images are out, so there's another way to update now if you don't want to wait for the ota or use adb.

 

[codesplice]

4.4.2 factory images are out, so there's another way to update now if you don't want to wait for the ota or use adb.

Well, sort-of. Still getting 404 errors when I try to download from https://dl.google.com/dl/android/aosp/occam-kot49h-factory-2006f418.tgz

 

[John Bean]

Interestingly I just got the OTA for my Nexus 7 (2012) which is rooted and has several disabled "system" apps which would have broken all previous OTAs. My experience of this OTA on the N4 was that it seemed to be doing a lot more checking than previous OTAs so just to see what happened I ran it without enabling the disabled apps or removing root.

It ran perfectly.

It broke root of course but other than that it was fine - and quick, confirming the ART/Dalvik differences in OTA timing.

Nice one Google

 

[2prevail]

I got the 4.4.2 OTA today and it was only 1.8 mbs. I installed it and everything went perfect, it only took awhile to optimize the apps because I am using ART as my runtime. 4.4.2 is great

 

[bjacks12]

It's running great. I remembered halfway through the update that I had disabled the stock messaging app, but no problems arose.