Sony

Length of time for upgrade to reach current flagship: 147 days (41.4/60 points)

Length of time for upgrade to reach previous-gen flagship: 155 days (19.8/30 points)

Communication: Fair (6/10)

Sony effectively has a dual set of flagships with its Xperia Z3 and Xperia Z3 Compact. The company made it easy, though: Both phones got Lollipop at the same exact time, with the software hitting the unlocked models (which are sold to U.S. consumers via Sony's website) starting March 30.

The T-Mobile-connected version of the Z3 hasn't been so lucky: It's still waiting for Android 5.0 today, in mid-May, which is pretty sad. (It's listed as being in the midst of the carrier's "certification process testing" as of this writing.) The same applies to the custom Verizon variation of the device, the Xperia Z3v.

Sony's previous-gen Xperia Z2, meanwhile, started to receive Lollipop on April 7.

When it comes to communication, Sony seems to say a lot: The company posts a fair number of blogs about its plans and progress, which is a good thing. But much of the info it provides is vague and non-committal, and large gaps of time go by without any updates. Lots of devices end up being omitted from the discussion along the way, too, like the aforementioned T-Mobile Z3 and Verizon Z3v.

But communication aside, there's just no getting around the fact that for current flagship phones in particular -- ones that run close to stock Google Android software, at that -- Sony takes an astonishingly long time to get its upgrades out. It's something the company has struggled with since the start, and it continues to be a perplexing issue with its otherwise accomplished devices.

Samsung

Length of time for upgrade to reach current flagship: 91 days (47.4/60 points) for Galaxy S5; 122 days (43.2/60 points) for Galaxy Note 4

Length of time for upgrade to reach previous-gen flagship: 155 days (19.8/30 points) for Galaxy S4; 122 days (21.6/30 points) for Galaxy Note 3

Communication: Poor (0/10)

Like Sony, Samsung has two phones that are essentially equal in flagship status: the Galaxy S and the Galaxy Note. So for its score, I measured performance for both lines of devices and then averaged the figures together.

The Galaxy S5 -- the current flagship in that line at the time of Lollipop's release -- first saw Android 5.0 in the U.S. on February 2, with the Verizon model. Sprint and T-Mobile followed soon thereafter, while AT&T didn't get Lollipop to its version of the phone until the second week of April.

The Galaxy Note 4, meanwhile, got Lollipop first on Sprint starting on March 5. The AT&T model of the phone came in next, late that same month; the Verizon model's rollout began in early April; and the T-Mobile model started at the end of April.

With the previous-gen flagships, the Galaxy S4 saw Lollipop first on AT&T on April 7. The Note 3 started its Android 5.0 upgrade in the States with the T-Mo model on March 5.

(Samsung, like LG, does not offer unlocked models of its phones to consumers in the States -- which is a shame, as all of the devices experienced significantly faster rollouts internationally. But again, what we're measuring here is the soonest you could realistically get an upgrade from a manufacturer as a typical U.S. consumer.)

Interestingly, Samsung used to provide detailed info about its Android upgrade plans and the status of its rollouts, way back when -- but after it repeatedly failed to keep up with its promises (and, ahem, received a fair amount of negative publicity for the way it handled those failures), the company started an unspoken policy of saying nothing. With Lollipop, as with other recent releases, Samsung kept its customers completely in the dark about what devices it planned to upgrade, when rollouts could be expected to arrive, and how things were evolving along the way.

Motorola

Length of time for upgrade to reach current flagship: 9 days (60/60 points)

Length of time for upgrade to reach previous-gen flagship: Still waiting (0/30 points)

First, credit where credit's due: Motorola actually did ridiculously well with the first half of its Lollipop upgrade process. Its current 2014 Moto X flagship got the software a mere nine days after its release, which is pretty darn insane. That was the unlocked version of the phone, but the Verizon model wasn't far behind, with a rollout starting less than two weeks later. (The only other carrier model, AT&T's, plopped along with a rollout in late February. Yet another reminder: If you want timely upgrades, avoid buying phones from carriers whenever possible.)

That's all fine and good. But then there's the previous-gen Moto X -- the star of the KitKat upgrade show. It's somehow still waiting for its turn at 5.0 today, with no Lollipop rollouts to any models -- including the unlocked version.

Motorola has typically done a great job of communicating with customers about its upgrade progress, but once the second-gen Moto X rollout wrapped up, the manufacturer fell strangely silent. All those months, there was no official word about what the heck was going on with the first-gen Moto X rollout. Even the company's once-useful support site lists the phone as being eligible for the upgrade but provides no further info.

Just last week, a Moto product manager took to Google+ to acknowledge the delay and to vaguely blame a "lack of support" from some "partners" -- but that message came well over six months after Lollipop's release. And while who's actually at fault is anyone's guess, all that really matters is that owners of Motorola's first-gen flagship have been waiting in the dark for a very long time.

From Motorola in particular, that's incredibly disappointing.

Some closing thoughts

Not exactly an uplifting picture, eh? But let's end with a little perspective.

When Google announced Lollipop at last year's I/O conference, it did something new: It gave all of us -- not least of all the companies that manufacture Android devices -- a functional preview version of the software months ahead of its formal release. The idea was that with more advance notice, manufacturers would be able to get a head start on prepping their devices and then be able to roll out upgrades faster than they could in the past.

Yeaaaaaaah -- that didn't quite work out for everyone, did it? One possible explanation is that for all of its beautiful design and compelling features, Lollipop had plenty of problems at its launch -- some of them core issues with performance and usability. So no matter how primed they were for the software's arrival, manufacturers were greeted with an operating system that was rough around the edges and full of pesky quirks.

We can -- and should -- do better

On the one hand, we have to keep that in mind when considering the manufacturers' performance. On the other hand, all of the manufacturers started with the same software -- and their performance did vary considerably. So take from it what you will.

With Android's open nature and the level of diversity that allows, Android OS upgrades are never going to be completely consistent across all devices. That's par for the course. I've often said that Android presents you with a lot of choices, and if quick and regular upgrades are important to you, you can have them; you just have to choose a phone that delivers that type of experience.

Nexus devices continue to be the most reliable (if occasionally imperfect) options; if you were to make any comparison to iOS, they'd be the closest equivalents to iPhones in that their software is controlled and updated solely by Google. Warts and all, the end result speaks for itself.

But you know what? HTC is also looking really good lately. Its upgrades aren't as immediate as Google's, as you'd expect, but they're relatively quick -- and the company is making it clear that post-sales support is a priority it takes seriously.

As for everyone else, what can you say? Regardless of who's to blame, there's no excuse for keeping customers in the dark for months while their flagship phones sit idle. We can -- and should -- do better. That rings true for Motorola more than anyone, since we've seen how efficient and effective that company can be.

Google's 2015 I/O conference starts next week, and there's a strong chance we'll hear about the next big version of Android (Android "M") while there. Here's hoping the Lollipop upgrade experience serves as a lesson for everyone involved as to what does and doesn't work and how the process can be conducted more smoothly.

For now, I'll end with my standard closing thought: Ultimately, we can't control what manufacturers do or how much emphasis they place on timely software support. All we can do is educate ourselves on how the various companies tend to approach Android upgrades -- then decide how much that factor matters to us and make our purchasing decisions accordingly.

Being an educated consumer is the best weapon you have -- and if there's one thing I can promise, it's that I'll continue to provide all the ammo you need.

Contributing Editor JR Raphael serves up tasty morsels about the human side of technology. Hungry for more? Join him on Twitter or sign up for his weekly newsletter to get fresh tips and insight in your inbox every Friday.