If you have an AT&T Galaxy S5, you should be getting an OTA notification shortly for a nearly-500MB update, which includes exciting new features like not Lollipop. The software brings an upgrade to Android 4.4.4 (from 4.4.2), AT&T voice over LTE (AKA HD Voice), and some new bloatware that AT&T would like you to please use.
Here's the full changelog.
AT&T released a software update for the Samsung Galaxy S 5 (SM-G900A) on February 3, 2015.
Republic Wireless' hybrid WiFi-cellular calling system requires a number of changes to the firmware of phones, so updates tend to take a little longer. Case in point, The Moto G and Moto E are about to get Android 4.4.4 on Republic, but the Moto X is delayed a bit longer.
The HTC One M8 on AT&T is getting an update starting today, and it makes a few significant changes. What it doesn't do is bring Lollipop to the device—it's 4.4.4. The wait for Lollipop shall continue, I'm afraid.
Update, January 11th, 2015: Verizon has issued another update alert for the Galaxy Note 4.4.4. This one also updates the phone to 4.4.4 and includes the same changelog, but for some reason the build number is changed to N900VVRUDNK1. Whether or not there was a problem with the original rollout, we can't say, but it appears to be continuing.
No, it's not Android 5.0. There, we've got that over with.
Raise your hand if you like carrier apps added to your phone. Anyone. Go ahead, don't be shy. Well if you don't, here's a great example of why companies like AT&T should leave the software alone. An over-the-air update to 4.4.4 for the carrier-customized version of the Galaxy Note 3 was sent out on November 28th, then unceremoniously pulled. A previous message on the support page explained why:
Update: The software update for Samsung Galaxy Note 3 (SMN900A) is temporarily on hold, effective November 28, 2014.
Sony hasn't always been the best at updating its phones, but the company does have a commitment to AOSP unlike most others. It contributes a lot of code to Android, and developers are encouraged to tinker with unlocked devices. In fact, Sony has just announced support for AOSP on the Xperia E3 and Xperia T3, meaning all Qualcomm-based phones from 2014 can run pure Android with very little hassle.
Remember last night, when we were excited about the Galaxy S5 getting its Android 5.0 update already, at least in Poland? That was nice. Let's try to hang on to that warm, comforting feeling while we face this cold fact: a combination of lowered expectations for non-flagship devices and good old US carrier apathy means many Android owners won't be so lucky. For example, the Galaxy S4 Zoom on AT&T is just now getting its update to Android 4.4, more than a year after the release of both KitKat and the phone itself.
Huawei took a lot of heat when it told North American customers a few weeks ago that the Ascend Mate2 would not be getting the promised KitKat update. The original post was removed after the comments got ugly, and now Huawei is backtracking. After "reassessing" the decision to cancel KitKat on the Mate2, Huawei will go all the way to Lollipop, but not until some time in the first half of 2015.
If you're the owner of a Samsung Galaxy Note 3 for AT&T, you should be getting your Android 4.4.4 OTA update starting today. This will bring you up from Android 4.4.2, and Samsung has packed in a few extras with this 459MB OTA, as well. Namely: Kid mode, SideSync 3.0, Knox 2.0, virtual tour mode in the camera app, and some updated AT&T bloatware.
The Uber app has been added to the list of things-AT&T-won't-let-you-uninstall, and I imagine there are a boatload of bug-fixes and the standard exploit patches you would expect in an OTA of this magnitude.
When it comes to software development, there are two very distinct camps on the subject of tools: those who prefer to keep it simple with just a text editor and a compiler, and then those who go straight for a fully-featured IDE with all the bells and whistles. For more than a decade, the undisputed champion of IDEs is Microsoft with its assorted versions of Visual Studio. Having come from years of work on Visual Studio, nothing pained me more than the first (several) times I started up Eclipse.