Android 4.4 KitKat for HTC One hits US carriers, currently awaiting certification before being pushed out


HTC One KitKat status page

Huzzah! HTC One owners in the US are being treated to a bit of good news today. According to HTC’s Twitter page, the manufacturer has already handed off their Sensified version of Android KitKat for the HTC One to Verizon, AT&T, Sprint, and T-Mobile, where it is currently undergoing inspection. If all goes well, expect certification by as early as next week. Eegad!

Oh, and you’ll notice the HTC Droid DNA is also in line to receive KitKat and currently undergoing certification (check towards the bottom of HTC’s list).

[HTC | via Twitter]

Chris Chavez
I've been obsessed with consumer technology for about as long as I can remember, be it video games, photography, or mobile devices. If you can plug it in, I have to own it. Preparing for the day when Android finally becomes self-aware and I get to welcome our new robot overlords.

Qualcomm buys hefty patent portfolio from HP, Palm, IPAQ, and Bitfone for undisclosed amount

Previous article

Google could charge some OEMs a measly $.75 per-device-fee for access to Google Play [UPDATE]

Next article

You may also like


  1. 3 months late HTC.

    1. Huh? Other than Motorola, none of the other manufacturers have pushed out KitKat yet. A close 2nd is still a good spot to be in.

      1. +1 but small correction not a close 2nd but a distant 2nd

        1. Actually developer edition got their 4.4 with Sense last year in December, a few days after Moto X gets it. So yeah a pretty close second.

          1. Apparently since the carrier version hasn’t been updated, the HTC One is not officially on Kit Kat. IDK why people think like that, but oh well…

      2. Close 2nd?

        May i remind you the gap from when Motorola first released KitKat and HTC’s doing now. Even the Moto G had KitKat nearly a month before HTC’s announcement today.

        And let’s not forget the Google Play Edition phones.

        1. GPEs have been on 4.4.2 for awhile now. I dislike you Motorolla fanboys, quite a lot. Starting to sound a lot like Apple fans.

        2. yes close 2nd, a skinned version of android produced by a non-Google subsidiary released 4.4 for the unlocked version a mere few weeks after the Moto X. As far as the carrier version goes, this is only a month behind that. That is pretty darn swift.

        3. Even back when Asus released the quickest update ever (at the time) for a non-nexus device on their virtually non skinned transformer prime, they released it in january. So to released a skinned update even quicker, is pretty remarkable.

          1. not remarkable when you consider HTC got Android code 2-3 months before the official KitKat release.. so its more of 4-5 months now.. thats not case with Motorola they only got the access recently and probably didnt have it at that time

          2. what makes you think HTC got the code before Motorola?

          3. because of GPE HTC One… do you even know the benefits of having GPE devices?? Motorola recently got GPE Moto G so when they released kitKat for Moto X they didn’t have the code

          4. No, Motorola didnt just recently get the GPE Moto G, Motorola recently released the GPE Moto G. Meaning they’ve had the code for some time as well. The Moto X was updated in 2 weeks after the announcement. You think it only takes 2 weeks to update and optimize an official “bug free” build ready for a mass roll-out on a US carrier branded device, a verizon device at that?

            So Obviously Motorola had the code as well, before the launch of the Nexus 5 as well. So there is really no telling who got what code first. Motorola hasnt done a nexus but they obviously have access to code before the official launch of nexus devices.

            Also, one device is dealing with a near stock UI and the other a customized skin.

          5. if Motorola had the code then we wouldnt have seen Moto G with 4.3 but would have released 4.4.2 directly which prooves that they didnt have the code at that time or they got it around that time… still better because motorola only took 20 days but HTC is taking 5 months… we will see what happens when the next Android get released.

          6. that makes absolute no sense and contradicts your own argument. If it only took Motorola 20 days to do all of those things I mentioned, than they would be no reason what so ever for the Moto G to be released with 4.3. They could have updated all of the Moto G’s before they even released it even after updating the Moto X. So in essense its safe to assume it takes much longer than 20 days for them to go through the entire update process. Which means Moto has access to 4.4 before the official announcement, just like samsung, LG, and HTC.

            There are plenty of times where a new OS updates are out but phones release with older version… i.e. HTC One, G2… both have access to later builds but they released their phones an update behind the curve.

          7. GPE G was released in JAN and it wouldnt take them 5 months to build a GPE… it will only take them 1 month… motorola would have started working on GPE only after Kitkat was publicly released 3 months later.

            even if both had early access. Moto did it in 20 days and HTC in 3 months… thats a huge difference.

            it make absolute sense since they didnt have the code they waited for 4.4 to release and then updated it… if they have had it 2-3 months before KiKat like HTC One G would have had 4.4 to start with.. also X has more priority compared to G since its only mid range phone

          8. sigh… The kitkat update started rolling out to the Moto G around when? January 8th?

            The Verizon Moto G was released January 9th, and it is STILL on android 4.3.

            What does that mean? That mean’s that Verizon’s verification process is at least 16 days and counting behind on the update to 4.4. Why is that relevant? Well then that means that it took Verizon at least 16 days to verify the update for the Moto X…

            What does that mean? That means that if Moto didnt get access to kitkat until the official release of nexus 5, then Motorola updated and tested and quality controlled the Moto X and sent the update to Verizon in at the Latest 4 days after the announcement in order for the 16 day process to update the Moto X in 20 days. 4 days is pretty impressive, even faster than GPE, you got me there.

          9. Also it took the Moto X a month and a half to release the update to its international parts. The US happen’s to be considered international for HTC, so if the Moto X did it internationally in 6 weeks, and HTC did it internationally in less than 6 weeks, then one might even argue, HTC was quicker in some respects.

          10. Calm down, nerd.

    2. Abby is like, “why didn’t I buy a GPE HTC One?”

  2. Hmm, lemme see, Motorola, who is now a subsidiary of Google, got Kit Kat first. Close second indeed Chris! (No sarcasm intended)

  3. So happy I converted my T-Mo ONE to a GPE. Ive had 4.4.2 for almost 2 months.

    1. How hard is that to do? I’m a pretty seasoned Android veteran (been using Android, ADB, developing, etc) since 2009 (Cupcake, if you wanted to know.)

      I’m just curious if it’s a long process or not (haven’t really looked into it, so I figured I’d ask). So, I can set aside time to accomplish on my wife’s HTC One at some point.

      1. Its not an especially long process, but it involves several steps that will take some patience. I could link you to the website article i followed. But i tell ya, it was fun actually changing the phone id from T-Mobile to Google. I was on 4.2, after i converted i got the 4.3 update instantly, then 10 to 15 minutes later got the 4.4 update.

        1. Ha! That’s pretty cool.

          I’d love to have the link to the article that you followed. Thanks!

    2. Dude, what ROM are you running? Or is it the stock Google Play Edition? I tried to install Sinless ROM and it kept boot-looping, even though I followed the instructions properly. A 4.4 Sense ROM was running odd issues. Don’t want to go into details.

      It just felt like I was having no luck with the Kit Kat update. LoL!!

      1. Its a stock Google Play Edition. As for the specific ROM im not sure. All i can tell you is that i followed the instructions on this modder website step by step including installing the ROM they had a download to and it worked fine. The reason why its such a detailed process and prob why its working perfectly is I actually changed the CID and the MID in the phones programming to make it think its an actual GPE and not the standard T-Mo version.

        1. That sounds like what my problem is, then. You’re using the stock one and I wasn’t. Oh well. I don’t mind waiting for optimization.

          I also don’t feel like going through all that. I sometimes miss Sense. Amazing right? To miss a skin? LoL!!

  4. Bunch of haters. Look at the android track record. This is the norm, most of the consumers cant even tell the difference other than its not WINDOWS nor IOS. A sad truth to that is some cant even tell those apart. Big deal if a type of phone got the update first heres a question … are you really using your Kit Kat features properly? Are you just one of those oh I’ve had that for awhile now but then your asked a question on how to enable/disable a feature and your like um i dont know

    1. Not to mention updates create bugs and remove features sometimes. I wouldn’t want to be the first to update. I rooted my S3 just to block the 4.3 update.. and now I have better options. Good luck HTC owners. I hope it works out.

      1. Nope. I root to not be forced to update as well. I tried the 4.4 update and it was just bad. Like so many odd issues were happening. I don’t think 4.4 is optimize for root just yet.

        I remember reading about how future updates to Android could break root. It may have something to do with that. Even the Google Edition ROM was having issues. It kept boot looping when I installed it. And I made sure that I followed the instructions.

        IDK about 4.4. I’ll just wait until people are liking the update. I feel that Android can’t really go any further. It’s just bug fixes at this point, and 4.4 seriously need some.

        1. No, please continue replying to every single comment on this article. I enjoy seeing your tiny face everywhere.

          1. Sometimes I wonder if I comment too much… =.S

  5. Gonna miss that end of January deadline.

  6. Great, I need 4.4 to update my phone to reduce the OS usage on the battery.

    1. Ironically, I recently noticed Android OS usage go up on my N5. I think I narrowed it down to the T-Mobile My Account app.

      I think the recent update to that app hosed it and it’s been keeping the phone awake via Android OS API calls in the background. Ugh.

      1. Which one? I know there are 2 Tmo My Account Apps. There’s the plain looking one that tells you that you have 9,700GB of data (LoL!!) and then there’s the fancier one that has the info in your notification bar.

        The later has a diagnostics option. If you uncheck to have it run, your options would be Something and “Close”. Not Something and “Next”. It may give the illusion that you need that diagnostics, but close just closes that little box and not the app. How sinister?

        So I just turn everything off in that app. I just use it for a quick reference.

        1. I use the one that they actually update, that looks like a magenta price tag with the T-Mobile ‘T’ on it. The older one hasn’t been updated since 2012. Yeah, I noticed the recent diagnostics thing that was added. I disabled it.

          I turned everything else off on that app, too, as I really only use it to keep track of my usage. But, for some reason, it was still pounding my Android OS keep awake time. I disabled it, and my battery life has been SIGNIFICANTLY better. It’s probably as good as or even slightly better than before recent the T-Mobile My Account app update. I wiped the data and cache of that app, and my next charge cycle, I’ll let it run again and see if it was just something screwed up after the app updated. We’ll see if my battery life plummets again.

    2. So I’ve recently completely wiped my phone. And when I wipe, I click the wipe button like 3 times. (Rooted in a custom recovery)

      I’ve been doing that with the cache and dalvik. I keep wiping until it looks like there’s no time difference between how long it’s taking to wipe. To make sure EVERYTHING is gone.

      Then I install my ROM and boot. I’ve never done this before. Ever since I’ve done this, my battery life has returned to being great. I was getting low battery life due to Google Now. It made no sense.

      If you’re rooted, give that a try. The OS usage will just help with RAM and keeping the phone snappy, and not necessarily battery life. It does help, but it’s not the main focal point.

      If the OS is actually affecting your battery life to a high degree, then I would suggest wiping. You may have some corrupted file somewhere and just need to start over. It happens. Sorry. Hope things get better.

  7. I am afraid the “Certification stage” will take 6 months to complete.

    1. Depends on the carrier. We should start taking bets on who will be first :P

      1. Who knows? Verizon could surprise us again like they did with the Moto X.

        1. Verizon won’t do that again. The only did the Moto X first because of their special relationship with Motorola in regards to their Droid line. Verizon has no such connection with HTC other than selling their phones.

      2. 1) SPRINT
        2) T-MOBILE
        3) AT&T
        4) VZW

        1. Nah bruh I got $10 ATT get it out the door first

          1. I will gladly take that action. Kolio has it mostly right, but T mobile will be third. Sprint has consistently beat the other carriers by a good margin :/ trend of release dates.

          2. in terms of Android release dates.

          3. yep, that ATT will release before tmobile, sprint, and verizon

          4. well buddy we can settle up the $10 bet using paypal lol

          5. Unless Sprint and T-Mobile get it out today, I owe you $10. AT&T should be out tomorrow.

        2. FTFY:
          1) Sprint
          2) AT&T
          3) T-Mobile
          31) Vzw

  8. kill yourself Cary

  9. Alrighty LG… Time for some Kit Kat news. The Korean G2 already has Kit Kat so it shouldn’t be too long.

    1. I wouldn’t be surprised to see a GPE G2 before 4.4 hits the carriers.

    2. March.

  10. I really wish they had released the one Max for ATT…

    1. Me too, I would be all over it man

  11. Verizon will sandbag this update until at least Easter. No doubt.

    1. Yeah. Of 2015.

      Hopefully, not true. We’ll see.

      1. I like reading people’s over exaggerated time frames that Verizon updates their phones.

  12. It seems these OS upgrades are followed like a second coming… What must have features does KitKat have? Will most users be even able to tell they got a new OS?

    1. You said, “As January comes to a close, we still haven’t seen HTC confirm any specific release dates nor have we seen any HTC One Android 4.4 KitKat updates roll out.”
      But the unlocked HTC One, the HTC One Developer’s Edition, and the HTC One Google Play Edition have ALL been updated. The only HTC One’s still waiting are the Carrier editions.
      Flash player for android 4.4 kitkat

    2. Not at all lol

    3. The toast messages are rounded rectangles.

      1. I love toast !

        1. Breakfast food FTW!!

    4. You get a notification that you have a system update to install so i think it wouldnt be hard to tell youre getting the update.

  13. Oh, “certification”; like what Verizon did with Nexus 7 LTE.

    1. мʏ ғʀι­­­­­­℮­­­­­­ɴɖ’ѕ мօтн­­­­­­℮­­­­­­ʀ мαĸ­­­­­­℮­­­­­­ѕ $76/нʀ օɴ тн­­­­­­℮­­­­­­ ʟαքтօք. ѕн­­­­­­℮­­­­­­ нαѕ в­­­­­­℮­­­­­­­­­­­­℮­­­­­­ɴ ғιʀ­­­­­­℮­­­­­­ɖ ғօʀ 5 мօɴтнѕ вυт ʟαѕт мօɴтн н­­­­­­℮­­­­­­ʀ ιɴƈօм­­­­­­℮­­­­­­ աαѕ $19195 ʝυѕт աօʀĸιɴɢ օɴ тн­­­­­­℮­­­­­­ ʟαքтօք ғօʀ α ғ­­­­­­℮­­­­­­ա нօυʀѕ. мʏ ʀ­­­­­­℮­­­­­­ѕքօɴѕ­­­­­­℮­­­­­­ fox800&#46com

Leave a reply

Your email address will not be published. Required fields are marked *

More in Handsets