Saturday, December 12, 2015

HTC Marshmallow-update leak offers a peek at who’s getting what, when

Unknown


HTC knows that its users crave the latest system software, and so far the company’s been keeping ahead of the pack when it comes to embracing Android 6.0 Marshmallow. Not only has the One A9 launched with Marshmallow under the hood, but the manufacturer isn’t wasting any time in making Marshmallow updates available for existing hardware, with distribution for the One M8 already underway. Of course, HTC’s got a lot more hardware than just these two phones; what does the Marshmallow situation look like for the rest of the family? A new leak attempts to shed some light on the situation, offering a detailed breakdown of update plans for over a dozen HTC handsets.
The data contained in this leak appears to align with both what we’ve seen so far and have heard from official sources, with the One M9 ready to see Marshmallow land a little later this month. We also get some insight into handsets that may be skipping Android 6.0 altogether and moving right along to the new Android 6.0.1 – largely Desire phones and Asia’s Butterfly models.
Unsurprisingly, the One M7 won’t be joining us at the Marshmallow table, and future updates aren’t yet confirmed for even some newer models; the One M8 may have Android 6.0, but whether or not it will keep moving up to 6.0.1 is supposedly still under evaluation.
Dual-SIM models of the listed phones should share the same access to updates, but may lag a few months behind single-SIM editions.
The source notes that while this chart should reflect HTC’s current plans, not all of the decisions it represents are necessarily final, and we could see the company change its mind about updates for one or more of these phones.
htc-marshmallow-leak
Source: LlabTooFeR
Via: The Droid Guy

About the Author

Unknown / Author & Editor

I generally blog between 5:30 A.M. and 7 A.M. I will from time to time add something during the day, but for the most part blogging is an early morning activity for me.

0 comments:

Post a Comment