26
Dec
HTC-One-M7

HTC is pulling back the curtain a bit to give us a peek at what goes into a device update. Not only that, but it has broken out the different versions of the HTC One with individual KitKat statuses and a big infographic explaining the process.

HTC

The HTC One comes in three basic types – the carrier version, unlocked/developer edition, and the Google Play Edition device. Of course, it's the carrier version of the HTC One at Sprint, AT&T, Verizon, and T-Mobile still waiting on KitKat. These phones are in the integration phase, which includes HTC Sense additions and carrier modifications. The unlocked phones still get HTC Sense, but no carrier stuff. No surprise they're done. The infographic illustrates how the GPE phone just cruises around most of the roadblocks too.

The page also lists statuses for some other devices like the HTC One Max and Droid DNA. HTC doesn't seem as concerned with these ones for some reason. The whole infographic would be bonkers to post here – it's over 10,000 pixels tall. So you can hit the link below for the full thing.

[HTC Update Status, Infographic]

Ryan Whitwam
Ryan is a tech/science writer, skeptic, lover of all things electronic, and Android fan. In his spare time he reads golden-age sci-fi and sleeps, but rarely at the same time. His wife tolerates him as few would.

  • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

    I love that HTC did this. It's not like we didn't know the carriers were
    responsible for the lion's share of the delay, but it's a much more powerful
    message to see exactly how far behind they are.

    It's too bad there isn't an actual tracker built into the site with dates for
    each status update. Perhaps somebody will take the time to put one together as a
    separate project. I hope the other devices join the list with their own status
    updates.

    • mustbepbs

      But what does this say for Motorola and the Moto X? Every time I see articles about updates and blame and carriers I always go back to Motorola pushing 4.4 to their newest devices in a short period of time. I mean, the Moto X got it on Verizon of all places before some Nexus devices! Granted, their skin is nothing compared to Sense or TW/OptimusUI.

      No matter what perspective you look at, the OEMs are mostly at fault for update timeframes.

      • Brad

        Yeah, I'm pretty sure the OEMs just slap the same APK on every phone regardless of versions..

        • Cory

          Nope.

          • Mitchman

            Now who's being daft? That's clearly sarcasm from Brad.

      • blix247

        The speed with which the moto x update made it on to a Verizon phone changed my perception of who is at fault for updates taking forever. People's perceptions and expectations of update speed has been changed by Motorola, and other manufacturers will either meet those expectations or prepare to receive the brunt of customer dissatisfaction.

      • http://www.androidpolice.com/author/cody-toombs/ Cody Toombs

        I'm not doubting Motorola can keep this up, but there haven't been enough updates to start calling this a pattern. I suspect the speed with which Verizon took care of the Moto X update may have been prompted by other factors, perhaps a critical security issue.

        I think a big factor in this equation comes from how much bloatware the carriers want to put on each handset. HTC is typically a bit more permissive about including carrier software because there are associated kickbacks, so it's pretty plausible that the process is taking longer when there are more apps requiring integration and testing. Motorola is pretty flush with Google's money, so it's not allowing the same quantity of addons.

        • mustbepbs

          But you just proved my point: the OEMs are causing the delays with things like bloatware and overbearing skins.

          And what about the DROID Ultra/Maxx/Mini? They just got 4.4 last week. There's too much evidence to prove that OEMs have the most power when it comes to OTA updates.

          • Guest

            Actually, he just shot your point down. Or better yet, the VERIZON Samsung Galaxy Nexus did.

            Your point has been rendered moot by that one device.

          • mustbepbs

            How did he shoot my point down, and where did he mention anything about a Verizon Galaxy Nexus and what does that have to do with Motorola?

            I'm confused. The Verizon Galaxy Nexus just proves my point even further in that Samsung may have held things up. Not only that, but it was plagued by the OMAP processor, so the chip manufacturer may have played a role here as we know TI is out of the mobile processing game.

          • dozi

            just stop... it was a Nexus so Google writes the code for it... Im sure they delivered the code to Verizon and Verizon held it up.. the whole Motorola thing and Google thing is pretty fishy since theyre the same company and im pretty sure Moto got some kind of head start.. Plus those custom skins is how OEMS compete and differentiate their devices from the pack.. Moto just decided to do all its OEM modifications under the hood as opposed to on the surface.. its 100% the carriers and its ridiculous for you to argue that..

          • telco

            if VERIZON did hold the update that is due to testing. after a EOM hands the codes to the carrier it is the responsibility of the carrier to check if the codes provided will have no SHOW STOPPERS or in layman's term is compatible to the network. having said that.. its not a carrier's fault if the codes that were written by EOMs does not work properly w/ the system network since carriers provide full network infos to EOM just like when verizon approached RIM back then to ask for an iphone killer.

          • Guest

            He didn't mention the Verizon Galaxy Nexus. I did. And that's my point. Just look at that one device. It's a Nexus. All others were updated, on all other carriers, save for the one on Verizon.

            This renders your point, that it's the OEM's holding back updates, moot.

            Really? You seem to be completely not getting the fact that it was updated everywhere else but for that one carrier. Either Samsung loves everyone else or Verizon is just a dick. My money is on the latter. You're glaring inability to PROPERLY lay blame where it should would be almost cute if it wasn't completely stupid and wrong.

          • Cory

            The Verizon Galaxy's Nexus delays were made by Verizon. Look at the god damn facts. Unlocked editions get the update weeks and months sometimes before the carrier branded. The unlocked HTC One got 4.3 in September. The carrier branded, all but Verizon got it in October. Verizon just got it a couple of weeks ago. It is all the carriers. Any one who has been around Android knows it is the carriers. Anyone who knows anything knows it is the carriers Trying to say otherwise makes you look daft. .Are you seriously this daft?

          • telco

            am a fandroid since galaxy S2

          • telco

            its mainly w/ EOM. carriers does not have access to actual codes for any software or firmware update. and if telco's do have access they will be sued if the edit and released the codes w/out EOM's knowledge thus loosing THE RIGHT TO SELL the EOM's product

          • dozie

            he disproved your point...

          • Justin W

            I think bloatware is correct, but HTC updated it's unlocked One within a few days of the Moto X receiving the update on Verizon, so in reality, it is the carrier's fault here, not HTC's. Their software was clearly ready for deployment, but they had to modify the software to fit the carrier's requirements, which caused the delay.

          • Cory

            Learn the definition of bloatware.

            I would have a skin than stock. Stock suck.

            No. A ll the evidence shows that it is the carriers.

          • telco

            this is from the current telco am working on. its mostly public. i can't go on releasing FOR COMPANY ONLY INFO.

            here's the link: http://crowdsupport.telstra.com.au/t5/Device-Updates/Device-Updates-Important-Info-amp-Terminology/td-p/63944

            its basically the same w/ other carriers

            Device Updates – Important Info & Terminology

            [ Edited ]

            Options

            on

            ‎09-08-2012

            01:20 PM

            - last edited on

            ‎23-08-2013

            04:27 PM

            by

            Yannick

            What information is in these posts?

            The information posted in this forum covers updates for mobile
            handsets and tablets as well as any pertinent updates to Telstra ranged
            data products (e.g 4G hotspots, USB modems etc).

            By default only the “significant” updates will be captured here.
            Telstra tests and approves a lot of updates (97 device updates were
            tested and approved in financial year 2011/2012) and not all of these
            are of relevance to a significant number of customers. If details of a
            specific update are missing then please let us know via a post in this
            forum and we will where possible include it in the regular updates.

            How often will the information be updated?

            The information will be updated on a fortnightly basis. A new thread
            will be started for each fortnight updates. If there are significant
            changes to status that need to be urgently communicated then this will
            happen as soon as practical.

            What is the process for testing updates?

            The overall process is quite simple. It is made up of a number of steps:

            The device manufacturer (also referred to as the “OEM” or “Original
            Equipment Manufacturer”) will notify Telstra of an upcoming update. In
            some cases Telstra will request an update as a matter of priority to
            address an issue identified “in the field”.

            Once an update is identified then the submission dates for the update will be determined.

            Telstra and the OEM will jointly assess the scope of the update and
            agree on a testing approach. This will generally result in either a 1 or
            2 cycle test approach being agreed. (see the section “How long does the testing take?” for more details on this aspect)

            If there are any “showstopper” issues found during the round(s) of
            testing then the OEM will be asked to resolved those issues and submit a
            new version for testing.

            Once all “Showstopper” issues have been rectified Telstra issues an “Approval” for the update

            Once the update is approved the OEM will deploy the update to end
            customers. The update may be deployed “Over The Air” (sometimes called
            “FOTA” or “Firmware Over The Air”), via side load from a specific sync
            software on a PC or Mac (e.g. via the Zune client for Windows Phone
            7.5), via a service centre or a combination of all three methods.

            How long does the testing take?

            This depends on the scope of the update. In general minor updates are
            only scheduled for one round of testing. Major updates are usually
            scheduled for two rounds of testing but this is somewhat flexible.

            Changes in "minor point" versions of the OS - e.g. from Android ICS
            4.0.3 to Android ICS 4.0.4 are generally designated as "minor" updates.

            Changes in major versions of the OS - e.g. from Android Gingerbread
            2.3 to Android ICS 4.0 are generally designated as "major" updates.

            If multiple rounds of testing are required then the gap between them
            is usually 2 weeks from the end of Telstra testing although this can
            vary depending on the processes that that the device manufacturer uses.

            In the vast majority of cases a Telstra test round takes no more than 2 weeks

            What about historical information?

            Details of historical updates will be kept in the “Device updates - archive” thread. Once an update has been “deployed” for a few weeks it will be moved to the archive thread.

            What modifications does Telstra itself make to the firmware of devices?

            The short answer – none. Telstra itself does not modify the firmware
            of devices at all – we have no access to it nor the necessary skill set
            to “cut code”.

            What Telstra does do through its testing process is identify issues
            such as software bugs, non compliance to industry standards, non
            compliance to regulatory standards, sub-optimal performance on the
            network, user experience issues, interworking issues with the Telstra
            network etc. to the device manufacturer.

            The device manufacturer will then rectify the issues identified and
            release a new version of the firmware (and sometime hardware) for
            Telstra testing. Once all of the “showstopper” issues are resolved then
            the update is “Approved” by Telstra for release to customers.

            Explanations of column headings in updates table

            See below for further information on the column headings used in the firmware update table.

            Status:

            The current phase the update is in. These include:

            Waiting for initial vendor submission:
            A
            commitment has been made by the device vendor to supply the update and
            Telstra are waiting for the test submission. Where specific timings have
            been supplied then these will be provided.

            First round testing:
            Update is in its first
            round of Telstra testing. Minor updates only require one round of
            testing. A Telstra test round generally takes 2 weeks. The planned
            number of test rounds is shown in the Expected test rounds column.

            Waiting for second FW submission:
            Vendor is working on providing the second version of the update for Telstra testing.

            Second round testing:
            Update is in its second
            round of Telstra testing. Major updates generally have 2 rounds of
            testing scheduled. A Telstra test round generally takes 2 weeks. The
            planned number of test rounds is shown in the Expected test rounds
            column.

            Waiting for additional FW submission:
            Vendor is working on providing an additional version of the update for Telstra testing.

            Third or greater round of testing:
            Updates
            generally are planned for up to 2 rounds of testing. If further rounds
            are required due to unplanned circumstances then this will be reflected
            by this phase status.

            Approved by Telstra - waiting for deployment by vendor:
            The update has been tested and approved by Telstra and is waiting for deployment by the device or OS vendor.

            Now available:
            Update is available to customers.

            Expected test rounds

            The number of planned test rounds for this update. In general minor
            updates are only scheduled for one round of testing. Major updates are
            usually scheduled for two rounds of testing but this is somewhat
            flexible.

            Changes in "minor point" versions of the OS - e.g. from Android ICS
            4.0.3 to Android ICS 4.0.4 are generally designated as "minor" updates.

            Changes in major versions of the OS - e.g. from Android Gingerbread
            2.3 to Android ICS 4.0 are generally designated as "major" updates.

            Expected approval date

            The date that Telstra expects to issue the formal "Approval" for the
            update. This is the precursor to the release of the update to customers.

            Expected customer availability date

            The update is expected to be available for customer download by this date.

            EDITED: Device updates will now go out fortnightly instead of weekly

            Device Updates – Important Info & Terminology

      • KingofPing

        Easy: Motorola is Google.

        Now refer back to graphic above.

        :) (smart-arse answer, I know, but there's just enough truth to it...)

        Now the fact that Google somehow got VZW to move faster on the X than the Galaxy Nexus...well, that's something to talk about.

        • mustbepbs

          If we are to believe that Google doesn't have a special relationship with Moto with their devices (like they said), then that doesn't mean anything to me.

          I'm going based on facts and evidence here, not speculation.

          • KingofPing

            "If we are to believe"

            "I'm going based on facts"

            ...just putting those two lines a bit closer together for you to consider.

            The fact is that Google owns Motorola. There's no speculation there. While they can *say* that doesn't affect anything, well, just look at how quickly the Moto X got updated.

            ...almost like it was a Nexus. :)

            (My first response was not intended to start an argument, I was just stating my own personal conclusions drawn from, as you state, facts and evidence. A billion users will come to a billion differing conclusions based on the same facts/evidence. )

            I do admit though, the avatar and the last line of your post is just so...perfectly Tuvok. Well played..

          • mustbepbs

            Thanks for taking my words out of context, because I said "If we are to believe" and "(like they said)", as in, if we are to believe what they said.

            Anyway, Google provides the same stuff to all the OEMs, and what they choose to do with it is up to them.

          • KingofPing

            I'll drop it. Wasn't kidding about not wanting to start an argument.

            Hope ya had a good Christmas. Best wished for the New year. :)

          • Cory

            If you believe Google doesn't have a special relationship with Moto on its devices you are delusional. Look at Moto pre google and Moto after Google. If you don't think Google has its hand in it influencing it you are stupid

            If you were going on facts you would realise everything you say is wrong.

      • Cory

        It is all the carriers. Moto and Google made back room deals to get the Moto X updates out quickly.

        • Serge

          Proof?

          • Cory

            Proof? Okay HTC One Unlocked got 4.3 in September. HTC One Sprint AT&T and T-Mobile got it in October. Verizon just got it like a week ago. HTC One Unlocked got 4.4 last month. GNEX got Jelly Bean months after the unlocked because Verizon delayed the update. Need I go on? And Moto confirmed they made deals. Look it up.

          • telco

            kindly refer to this : http://crowdsupport.telstra.com.au/t5/Device-Updates/Device-Updates-Important-Info-amp-Terminology/td-p/63944

            telco's does not have the codes nor do they write one. if they are given one then they need to run a test first to see if the codes are compatible to the network system/frame

          • squiddy20

            Yeahhhh, that link is specific to Australian carrier Telstra. They're talking about Verizon/Sprint, which are US only carriers. Not to mention that Telstra is a GSM/LTE carrier while Sprint and Verizon are CDMA/LTE. Good try though.

          • telco

            and even if its the EOMs the one responsible for the delay that would be for a reason.

            would you rush an order of fried chicken if you know its still half cook and bloody ?

            would you rather face an angry customer ?
            or would you rather have your business on the verge of closure for serving raw and bloody chicken and possible food poisoning?

            same w/ EOM. yes they can realease an update sooner but no promise that its bug free. they just want to make sure you will not have any issues moving forward like loosing contacts and infos

          • Cory

            The carrier is responsible for the dealys. See the HTC One unlocked got the 4.3 upadate in September. The Sprint AT&T and T-Mobile HTC One got it in October. Verizon did not. Look at 4.4. Unlocked HTC One already got it. Carrier editions. Nope. Look at the Galaxy Nexus. A Google phone, The Jelly Bean update was delayed months by Verizon. Anyone who says it's not the carrier is clearly daft and has not done the research.

          • squiddy20

            1. For god sakes, it's "OEM" (Original Equipment Manufacturer) not "EOM".
            2. I assume Sprint and Verizon got the Galaxy Nexus 4.3 update from Google at the same time. Sprint has had the update available since about October 31, months after the unlocked/international models got the update sometime in July. While true that you can go to Google's Android binaries page and download the necessary files to update the Verizon Gnex to 4.3, Verizon itself still has yet to push the update OTA. If Sprint can do it in a somewhat timely manner (if you call 3 months after the fact for an update to a Nexus phone "timely"), so can Verizon. There is no excuse.

          • telco

            would you care to know the reason why they have not pushed the OTA?

          • squiddy20

            I can only assume it's because they don't feel like pushing the update for some unfathomable reason. Sprint got the update out. There's no reason for Verizon not to have as well. As far as I know, besides specific frequencies, Sprint and Verizon use virtually the same radio tech (CDMA/LTE). Sprint also got the update for 4.2 out before Verizon.
            Not to mention that, maybe a month or so after Google released the 4.3 source code, there was news (or maybe just rumor) of the update being pushed out to the Verizon Gnex, but was (very) quickly halted and no one was told why.
            In any event, the issue is not with the "EOMs" as you claimed earlier, as Sprint has had the update out for 2 months. The problem is with Verizon, which has a long history of taking an unusually long time to update their phones (Moto X notwithstanding).

          • telco

            it is from OEMs. a carrier will not released an update if it will not work properly. they have a lot of customer's to protect and to keep compared from OEMs. and carrier's dont have the same systems and equipments even if they are basically using same type of technology(3g,4g) they also have different softwares to keep their network running. so one carrier may release an update earlier than the other.

          • Me

            For GOD'S SAKE it's "For God's Sake", not "For God Sakes"

  • Brad

    Gonna gripe and say what a sloppy way to display this info haha... anyway, neat to see it...

    • Brendan Dillon

      Yeah, not a great graphic.

      • Brad

        Just hard to follow...

  • Owen Finn

    Imagine how much time/money would be saved if they all just ran vanilla Android!

    • Brad

      that'd be my dream

    • enoch861

      That would make every phone more or less then same.. which, in turn, would make everything boring.
      These skins make the phone what it is and that's what defines Android.

  • maniel

    now I'm wondering how they justify there is no newer than 4.2.2 android for HTC One X (endeavoru), it's last year's flagship, there are BSPs for Tegra 3 (2012 Nexus 7), Samsung already released 4.3 for their 2012 phones;/

    • kekkojoker90

      tegra 3?

      • blumpkinator

        yes, the international version of the H0x [endeavoru] used a tegra 3 and had GSM/HSPA+ connectivity. The American version [evita] used a qualcomm chip and had GSM/HSPA+/LTE connectivity.

    • mustbepbs

      The part where it says they determine if it can run Sense or not. That's where they get you.

      • maniel

        yeah, nice excuse to not make at least .5 update, i would be happy with Sense 5.5;-)

        • mustbepbs

          Whatever they can do to get you to upgrade. Although to enthusiasts and hobbyists, it's counter productive because we give them the collective "fuc* you" when they don't update devices that can clearly handle it.

          • Joris Griffioen

            Yep, if I check out another HTC I'll go in with the predefined con of "not going to recieve updates". Maybe that's harsh, but HTCs current attitude towards updates seems to be a flagship-only affair. So when they release a new one, tough cookies.

            They're quick right now, but we'll see how the One fares when the "Two" comes out..

          • Cael

            They'll be back on their take forever schedule to update previous models and then place the blame on everyone but themselves.

    • AOSPrevails

      Samsung released 4.3 for their 2012 phones so that they can be used with Galaxy Gear(they hope to enhance Galaxy Gear sales that way), HTC have no such financial motivation.

    • Cory

      Yeah and Samsung had to pull the update to fix it and people are still complaining it messed their phones up.

      Also there is very little difference in 4.2 and 4.3

  • cy_n_ic

    Pixel height is over 10,000!!!

    • telco

      you mean density?

      • squiddy20

        No, he meant height. It was even stated right in the article "The whole infographic would be bonkers to post here – it's over 10,000 pixels tall" Seriously, did you even read the article and infographic?
        Also, it is a reference to DBZ.
        Good try though.

  • KingofPing

    Looks like they are preparing for the inevitable carrier delays past the "promised" end of January timeline.

    I am taking this as pretty damning evidence that at least one if not multiple carriers will not have their 4.4 out by the deadline as HTC is already rushing to make sure their excuses are out there.

    Don't get me wrong; I own an HTC One. I love it. Best phone I've ever had, bar none, and HTC has stood behind it firmer than any other manufacturer of any other device excluding Google themselves (that includes wholly-owned subsidiaries).

    It is what it is, though. Just because I am a fan doesn't make me blind to the reality that HTC doesn't have a big enough stick to force US carriers to bend to their will....and this just sounds like the beginning of a...

    "Well, we showed you how it's done. We did our part. It's not our fault. Really."

    • Cory

      Wrong again. They are not prepping for any kind of delay.

      • KingofPing

        Oh.

        Well.

        Obviously you know better. I mean, you just said it. Right there. On the Internet.

        It must be true.../smh

      • Cael

        Tell that to the Droid DNA

        • Cory

          Blame Verizon. The international version of the DNA got the update. Do some research.

          • Cael

            I guess Verizon also sends out HTC's tweets then too. I guess Verizon is also why HTC is going down the toilet. LETS BLAME VERIZON FOR EVERYTHING. Maybe HTC shouldn't make crap phones that it won't support because no one buys their crap phones. HTC One 2 = DOA. Yup that's Verizon's fault.

          • Aaron Davis

            Yes, I would love to blame Verizon for for everything:

            Being the cause of the spectrum shortage that everyone is complaining about, because VZW sits on a huge pile of spectrum that they hoarded and then never used.

            Blocking all non-VZW GPS apps, and then charging a monthly fee to use the pre-installed VZW-approved GPS app

            Blocking 3rd-party ringtone services and forcing everyone to buy ringtones though the VZW store instead (back when people cared about ringtones)

            Charging high ETFs that aren't pro-rated, while having contracts that magically extend themselves whenever you make even a tiny change to your plan

            Not allowing the Nexus 5 on their network despite full compatibility.

            Continuing to charge customers extra each month to subsidize a smartphone that has already been paid off.

            Delaying software updates simply because they don't include VZW-owned apps, or have the VZW logo plastered everywhere.

          • Cael

            >_>
            The point of my post is...Verizon is not at fault for HTC's crap.

          • Aaron Davis

            Verizon is certianly at fault for the updates for the Verizon version taking longer than the unlocked and play versions. I can't see how you could blame HTC for this.

            If Verizon wanted to avoid this problem, all they would have to do is stop being complete control freaks and just accept the HTC One the way HTC designed it, without demanding that every app on the phone be Verizon-branded

            If it was left up to Verizon and at&t, you wouldn't even be allowed to buy a phone, you would be forced to rent it from them (just like the old Ma Bell that they both descended from)

  • LjHe80

    The one thing they forgot in this infographic is a planned leak and let consumers test for bugs.

    • Joris Griffioen

      Except that doesn't happen. They release the tested build to a small batch of consumers, see if it works well, sometimes it doesn't and they have to do fixes.

      There are millions of possible permutations of data and usage patterns, nevermind network quirks and all that. You can't test them all in a "lab" environment, you cannot expect to release software that works perfectly 100% of the cases unless it is very, very simple software.

      Releasing to a smaller userbase at first just ensures that they don't screw everybody if something's up. Sure it sucks for that group of users when something is up, but if that software was released to everybody ... they'd still be part of that group. So it doesn't change their situation at all.

  • MotoXYZ

    It's like a Domino's Pizza tracker for HTC. Joe is testing the code..Joe is baking the code..Your update is ready!

    • Simon Belmont

      Now you just have to make a special request to put an awesome wallpaper of your choice into your build of the KitKat ROM. Kind of like how you see people request drawings on the pizza box.

      Here you go: http://25.media.tumblr.com/tumblr_m5olqvGpZ31qhlepco1_500.jpg .

      • MotoXYZ

        Lol..yup that would work..

  • Taleim

    Hmm still think I'm missing something. I know this varies by region, but my unlocked one happens to get ota after all the carriers in Australia have approved update. No one has been able to tell me why this, including htc Australia. Cid 039. Have to think carriers are interfering with unlocked updates, or htc Australia are lazy. If this was true, I should get ota at least a few weeks before carrier versions. Anyone?

  • drcmda

    It's a lie, although i love the presentation. They have an obvious benefit when they delay updates as far as they possibly can, and so does the carrier. Updates make devices better, faster, last longer - do you really want this when you are about to drop yet another marginal hardware offering which half of your customers will skip because new runtime tweaks in 4.4.x make the old devices run just as good?

    And this is where i hope vendors come to their senses and realize they don't have to screw over their customers. Motorola can do it, so can they. Drop your skin, respect the platform design, deploy your extras as apps and modules like Moto and Facebook do. Handle updates fast and differentiate with your hardware while you leave software in the hands of those that know and care, Google.

    I think hell will freeze over before they would even consider it, though---

    • mustbepbs

      I totally agree, but Sense 5 isn't NEARLY as bad as Sense used to be, it's actually kind of nice. If OEMs just contained their skins to launchers, that would be sweet.

      • maniel

        yeah, sense 5 is nice, comparing to TouchWiz for example, i hate it, every time is play with my friend's Note 3 and have to use Settings i feel like using gingerbread;-)

        • Crispin Swickard

          Its looked about the same since around the eclair days. I don't know how even Samsung isn't tired of looking at it by now..

          • Danny Davis

            About as lackluster as iOS

          • Crispin Swickard

            Given Samsung's history with Apple maybe now they will finally switch over to a more modern design with the next flagship Galaxy. I am however, not holding my breath.

        • AOSPrevails

          It is not just Sense 5 & Touch Wiz, it is things like the two button set up on HTC phones or the menu button on samsung phones that are contributing to android fragmentation.

          • Kokusho

            Please... Android can handle 2 or 3 buttons... android was thought from the groundup to work on anything with any input device.

          • Cory

            That is a moronic statement

        • telco

          makes sense :)

      • Cory

        No. I would rather have skin.

  • Adam Goldberg

    I don't see my EVO 4gltE status there. WTF HTC?!?!?!

  • Bazar6

    This is great to see from the OEM, now we need the Service Providers (VZW, AT&T, etc) to get a status page rolling too... you'd be able to see exactly where it's stuck (and who to point fingers at for the longer delay)

    • Joris Griffioen

      They're going to roll out a page that shows their own slowness?

      • Mitchman

        Rollout the page and never update it. That's why they'd do.

  • Simon Belmont

    This is cool. At least HTC is trying to inject some transparency into the process.

    I have to give them props for that. If they get KitKat out by the end of January, I'll be wholly impressed (as I was with Android 4.3).

    • Joris Griffioen

      They are only fast now because they've relayed all their resources there. All older phones are not recieving updates. The HOX is still on 4.2.2 and could easily run 4.4 (or at least 4.3)

      Just wait till the next flashship comes out, they'll drop quick One updates like a stone.

  • garyniger69

    Nappa: Vegeta, what does the scouter say about the number of pixels?
    Vegeta: IT'S OVER NINE THOUSAND!!!!1!111
    Nappa: WHAT? NINE THOUSAND???

  • supremekizzle

    The lesson here is buy devices in the order of:

    1) Google play edition
    2) Unlocked
    3) Carrier

    • Cory

      A GPE is a waste. Unlocked all the way.

      • blumpkinator

        why stop there; unlocked is a waste. Get a used ATT version, then sim unlock for $3. Then S-off and do a full GPE conversion. All the goodness of being unlocked and having GPE without the pricetag.

        • Cory

          Because GPE is stupid. And I cannot stand stock

          • Thomas’

            You sure are in the majority here, sir.

    • Mitchman

      Unless you are on Verizon...

  • Marcell Lévai

    Moto X anyone? Instead of an infographic of updates ;)

    • Cory

      HTC One is better

      • Cael

        HTC One sucks that why it didn't save HTC.

        • Mitchman

          HTC One - front facing speakers and aluminum build awesome. Everything else bland.

        • Cory

          If it sucks is that why it got rave reviews? Is that why it won more awards than any other phone? Is that why it has been awarded the phone of the year? Is that why on Phone Dog's viewer rankings it has been #1 since launch? Yeah that sounds like a phone that sucks.

          Also it has done a lot to save HTC. It has put them on the long road of recovery.

          • Cael

            Reviews don't matter. Sales matter. God can say the HTC One is the best phone around but if it doesn't sale then its a flop, it sucks.
            IIRC HTC had a red third quarter. How the hell did it save them?
            HTC doesn't know how to make a thin, lightweight, small bezeled, big battery, great camera phone that still looks good. Until then, they suck. Half way doesn't cut it.
            Money talks, your BS can surely walk. Or is HTC paying you?

          • Cory

            HTC One has sold quite a lot. It is daft fools like you who don't know a good phone.

            Thin, the HTC One is ravor thin, And very light. Has a small bezel. An amazing battery. 15+ hours moderate use. 9 hours heavy use. That camera on the one is the best on any Android phone around. HTC One. Rated by the people as Smartphone of the Year on Phonedog's official smartphone rankings.

            How much is Sammy paying you?

            You are clearly an uneducated twat.

          • Cael

            LMAO. YOU are. Samsung isn't paying me anything. I never once said anything about Samsung. I don't own any Samsung phones and I never will. I hate how Touchwiz is. I hate the physical button. I don't care for their phones. Only thing I like is the SD card slot and the fact that they will update their flagships and provide variety.

            HTC One: 5.41 x 2.69 x 0.37 inches
            S4: 5.38 x 2.75 x 0.31 inches
            G2: 5.45 x 2.79 x 0.35 inches
            Moto X: 5.09 x 2.57 x 0.41 inches
            Yeah the HTC One is pretty big for a 4.7 inch phone. The G2 has a bigger battery and its THINNER than the One. For poops and giggles, the Droid MAXX with a 3500 mah battery is 0.33 inches thin.
            And that 4 MP is crap. That is a fact. That's the biggest thing people don't like. You can read (I hope). Go read how many people are disappointed at the rumors that the One 2 will have the same crap camera.
            HTC is the next Blackberry. Just late to the party.

          • Cory

            Thanks got point out you are a paid trolling twat.

            You are a fool.

            Wrong. The Ultrapixel camera has got rave reviews. You haven't done much research at all.

            You are a twat who has no idea what they are talking about. I feel sorry for you.

  • Michael Pahl

    "What about my country! Soon backanswer!"

  • dm

    Other HTC smartphone update status is not exist, I suppose HTC only have 1 product? HTC One, where is the same level of detail status update for "Other"? hell they even list software for HTC one X wrong, its not Android 4.1 sense 4, its 4.2.2 Sense 5, so many effort putting together infographics can't even put all normal facts straight.

  • mrjayviper

    Is this HTC's way of saying why it's OS updates is slower than Apple's?

  • Dandamudi Mohan Krishna

    The infographics are good but still doesn't explain why for unlocked devices in UK get update 1 month ahead of the unlocked device in India..

  • http://www.vrdwellersblog.com/ Miles Reiter

    This is cool, but at the same time, and I really don't want to place the blame entirely on either the OEM or the Carriers, but I've seen random developers build a stable ROM in their free time faster than most of even the fastest official updates come out. Bit annoying.

    • Thomas’

      Because random developer use nightly builds and early adopter for testing w/o the worries of any certification.

    • FritoDorito

      A ROM doesn't even begin to compare to official software. I've yet to use a custom ROM on any of my phones (2 of which have been Nexuses) that was nearly as stable as a stock ROM. Hell, I've yet to use a ROM that doesn't at least recommend a full wipe of all user data and both caches. Not to mention that checklist of bugs every ROM has.

      -Camera Force Closes when taking a Photo Sphere.
      -MMS doesn't work
      -Notification light occasionally blinks "Heil Hitler!" in morse code
      -Phone crashes if the Calendar app is opened on the third Tuesday of November within 30 feet of a 32" Vizio TV

      ROMs aren't designed for widespread consumer use. They're designed for people who understand the risks to install themselves, which is extremely small compared to the number of casual users. That's not even mentioning the many testing and verification processes that developers don't have to go through. There's also the fact that most developers are only dealing with one phone, and usually one variant of the phone at that. Manufacturers have an entire lineup that needs to be put through this process.

      • http://www.vrdwellersblog.com/ Miles Reiter

        And I've rarely used a stock ROM that's as stable as the custom ones I use.
        My point is more that if single developers do what they do in their free time so well it's really kind of sad that big corporations with so many more resources can't roll out updates faster, and support older devices for longer. I also have issues with how long certification and verification processes take. It would be different if that actually resulted in totally bug free software but we all know that's never the case.

        P.S, I thoroughly enjoyed those creative bugs.

  • nvillaco

    The HTC Update Status Page is wrong about the DNA though... It says it's on android 4.2, sense 4 but its actually on android 4.2 with Sense 5... Small error but it's there.

    • Cael

      HTC could care less about that phone. lbr

      • nvillaco

        Ya, it's a shame cause it really was an incredible phone for it's release date. I'm still using it (although waiting on a bamboo Moto X in the mail) and it still hangs with the current flagships. The thing that kept it so underrated was the fact it was only on one carrier, Verizon.

  • John McNichol

    Everytime HTC do an update no video apps work, google movies and youtube mostly but also the video feature in sky news... then they release a smaller update to fix it, then a big update again and now the same video issue is back, still waiting for the smaller update now. HTC sort yourselves out!

  • CerealFTW

    I don't care if the spec wars are over, step 4 is reason enough for me not to buy a Moto x. the processor is still great, but not new enough to be getting updates as long as the S800 imo. I'm never buying a device that doesn't have the latest processor again. roms are pretty buggy too if the chipset maker doesn't put out drivers

  • http://byazrov.ru/ Russian Photographer

    if my HTC phone is not updated I don' care whose fault it is. I just don't buy HTC next time. Though HTC One is amazing and It means I might buy HTC again.

  • Nex

    Let's see their infographic about why the Galaxy S4 has a bigger removable battery, SD slot and yet still 1.4mm slimmer than the One.

  • asadf

    still doesn't explain why newer devices (with the same hardware as some older ones) came out with an updated android version and the older devices (with the same hardware) left without updates.