Home

Share this Story

Moto X Camera Update to Build 139.14.1 Arriving on Sprint Model Too

moto x sprint update

On Monday, Motorola began pushing an update to the T-Mobile Moto X that dramatically improved the camera, but also fixed a few important bugs in Touchless Control, voice call audio, and Migrate (full changelog). Again, the star was the camera update, which we have highlighted in a series of comparison photos that can be seen here. That update is now to be rolling out to the Sprint model as well. 

According to a couple of our readers, an update to build 139.14.1 popped up on their Moto X variants this morning. Sure enough, Motorola has posted a changelog for us which does indeed show that this is the same update as the T-Mo update from earlier in the week:

Screen Shot 2013-09-25 at 7.30.44 AM

To check for the update, head into Settings>About phone>System updates.

Cheers Ari and Stephen!

  • Pat

    I really hope this makes it to the Droid Maxx.

  • Sean Bello

    Does anybody know where I can get the AT&T factory image from? I’ve been looking on XDA and Google, but on Google I just get pics of the factory where Moto Xs are being made lol…ugh.

  • Paul Hansen

    I’m curious how quickly these updates roll out to the rest of the Droid 2013 lineup since they’re all basically the same device.

  • Louis

    I like the Moto X but only reason why I went with the DROID MAXX was that battery life and wireless charging, hope if/when verizon decides to let this camera upgrade happen it rolls over to the DROID line.

  • http://www.thepapermail.com/ Jacob Penderworth

    I had a major issue with Driving Mode’s reading text messages and callers when it wasn’t on. Hopefully this comes to Verizon very soon.

  • hatboysam

    I want this badly on my Droid Maxx … any chance that ever happens?

    • guesswhat

      soon! expect in couple of weeks..mid october i would say

      • hatboysam

        Why do you say that?

  • Turb0wned

    Good for Motorola.. Showing promise for updates.

  • JBartcaps

    Remember that one time when it landed on the Verizon? Yeah neither do i

  • http://www.unappreciatedscholars.com/ Steven Shreve

    Since they’re running essentially the same software/hardware, any chance we see this on the Droid MAXX too?

    • Sharrief Ibn Kamal Shabazz

      There is definitely a chance…

  • MyNexusCameraKindaSux

    Updates to improve cameras!!!?!?
    Can the guy that does this at Motorola call over to the Nexus department to see if they can start doing this too?

    • Turb0wned

      LOL very true.. God my Nexus 4 and GNEX take terrible pics…

  • maratu

    Yea this has convinced me to get off Verizon. I’m done. Returning my new motox tomorrow, going with tmobile. Ordering gsm variant now.

    • guesswhat

      verizon will get it in couple of weeks ..

  • NickA

    T-Mobile – Check
    Sprint – Check
    AT&T and Verizon – Crickets.

    I’m actually surprised AT&T didn’t get this first, kind of like they got MotoMaker first.

    • ThomasNeidhart

      Maybe tradeoff for them getting MotoMaker first…

  • moelsen8

    i really wish the dev editions would come back in stock on moto’s site. i officially want this phone as of monday.. shortly after they went out of stock.

  • AxemRed

    It will be interesting to see how long it takes AT&T and Verizon to get these updates. There aren’t that many phones that are identical on all carriers like this. I’ll start complaining to Verizon about a week after AT&T gets theirs I think… ;)

    • Justtyn Hutcheson

      To which the reply will be “Our testing process is the most rigorous in the industry to ensure the reliability and security that Verizon prides itself upon”. Implying that T-Mobile, Sprint, and AT&T’s testing is worthless, of course.

  • Adam Truelove

    Coming to your Verizon Moto X just in time for Android 4.3 in June 2014!!

  • Jordan Pfingsten

    People need to pull the .apk for all of us….

    PLEASE!

    • zurginator

      APKs don’t touch firmware, so it wouldn’t do you much good.

  • Jack3D

    Just a reminder to anyone who is using JCase’s PwnMyMoto root exploits…DO NOT INSTALL THESE UPDATES!!!

    It closes one of the exploits used in that method, breaking root and I would not hold out hope of getting it back…

    • Lucky Armpit

      Link, please? Would love to read more about that. If that’s true, I’ll have to decide which is more important… root, or bug fixes.

    • thomas

      is there anyway stop the OTA

  • Clay Wilson

    Woah this fixes all the problems I had with my moto x. I don’t even care about 4.3, as long as I get key lime pay fairly quickly(which is unlikely considering Im on Verizon)

    • Justtyn Hutcheson

      They have been less than forthcoming about anything for the Moto X beyond “working on another update”, but it seems like they are planning to roll out updates on a fairly regular basis, so I have hope. Mainly that 4.4 will take the carrier out of the update equation unless the radio firmware is touched.

      • zurginator

        Wait there is a rumor that 4.4 takes the carriers out of the equation? How does that work?

        • Justtyn Hutcheson

          Not a rumor so much as rampant, unsubstantiated speculation. The wording from their naming graphic, their slow yet steady removal of their major platform-driving services from the OS to the Play Store, and the rise of Google Play Services as an app that has complete and utter control over nearly every part of your device points towards a much better update scheme, where Google can push framework and system-level updates through the Play Store, and the only things that would require an OTA update is kernel and radio firmware.

    • Adam Truelove

      Hahahahaha, the Verizon version won’t get anything past whatever it’s on now for at least another 6 months, and when it does get an update it’ll still be 2 versions behind.

    • Ben Cammarata

      *kit kat brah

      • Clay Wilson

        Ha yeah I’m just so used to saying Key Lime Pie

      • Sharrief Ibn Kamal Shabazz

        You sir are an idiot.

        :)

        • ThomasNeidhart

          It’s, “You, Sir, are an idiot.” Now, let’s talk about why you feel the need to be so rude? You wouldn’t say that obnoxious remark in person, so don’t say it on the net.

        • Anon

          Eh. Why is he an idiot when he is correct? Ironic..

        • Sharrief Ibn Kamal Shabazz

          Calm down guys, we’re friends IRL :)

    • pamelabutler88

      What
      Marcus replied I am in shock that any one able to get paid $6824 in 4 weeks
      on the computer. have you read this site link..www.Pro67.ℂom

    • Anon

      Wait, so you actually received the OTA update that fixes these issues? That’s making me rethink canceling my Verizon contract for the Nexus 5!

  • TheDrunkenClam

    Still no 4.3.
    Surely I’m not the only person who thinks this is inexcusable. Phone should have launched with 4.3.

    • zurginator

      You do realize 4.3 shipped only like a month before the Moto X right? The X would have already been under full production. I don’t think it’s even remotely realistic to expect an OEM to move that fast, Google owned or not.

      • Adam Truelove

        Just because we’ve come to expect slow updates doesn’t make it acceptable.

        • zurginator

          There is a point which is unreasonable though. I think OEMs should spend at least a week testing updates (because bricking phones and breaking things is not cool), so that would give them 3 weeks to build out a stable update, and bake in their features; assuming they ran in to zero complications on their first run, they could push the update out in a month. Yeah not going to happen.

          • Justtyn Hutcheson

            They can push a stable minor update in ~3-4 weeks, as we see here. For OS updates, it would move to 4-6 weeks, possibly as many as 8 if you are talking a jump like 2.3->4.0. However, that build then goes to the carrier, whose testing takes 4-6 weeks on its own, possibly more depending on the complexity of the update and definitely affected by their own internal testing priority queue.

            So, to me a reasonable time frame is: X.x or X.x.x update, 4-6 weeks from code release to handset for an unlocked device, 6-10 weeks for carrier versions. For an X.0 or a major under-the-hood X.x (like 4.0 to 4.1 was), I would say 6-8 weeks for an unlocked handset, and 8-12 weeks for a carrier model.

            However, maintenance and security updates should be rolling out at least on a quarterly basis, if not monthly. That is definitely one area that Android OEMs must become more focused on in the future.

          • LionStone

            “…and definitely affected by their own internal testing priority queue.”
            Aka- injecting bloatware :-)

    • Justtyn Hutcheson

      ….Sure, a device that launched a week after the code was made publicly available should have it at launch…. 3 weeks is barely enough time to get the code working properly, let alone certified and pushed through the carrier update process.

    • Steve Ballmer

      You’re nuts.

    • kixofmyg0t

      After using 4.3 on my Nexus 7, no thanks. You can keep that bug ridden mess to yourself. I’d rather stay at 4.2.2.

      • Justtyn Hutcheson

        Most of the X.x versions are pretty buggy. While I love the Nexus program, I actually prefer to let someone like Motorola take their time and squash bugs before it is on my daily driver. I get a stable device that works as-advertised, which is exactly what I purchased it as. Any updates that improve or add functionality are great.

        • Paul Hansen

          Some of the big streaming apps aren’t compatible with 4.3 as well. HBO/Cinemax are quick examples. I’ll have mixed emotions about updating if these aren’t updated yet when 4.3 does arrive.

          • Justtyn Hutcheson

            The same applies to any software that isn’t sourced to developers early, and makes the delays better for the customer in the end. I’ve always seen the Nexus line as a development tool and reference platform that just happens to be sold to consumers.

          • Paul Hansen

            Agreed. As much as I love the nexus in principle, it’s not exactly the best product for consumers as a practical item. While I understand this, John Smith on the street is just going to be pissed that his app doesn’t work and isn’t going to care why.

  • Justtyn Hutcheson

    o.o Motorola, dafuq are you paying these guys to get these out so quick??

    Whatever it is, double it for Verizon, I wantz that update next week :-D

    • JoshGroff

      T-Mobile, for better or worse, has generally been fast in rolling out updates. (Often times only a few days/weeks behind the international variants) Same for Sprint, the G-Nex comes to mind as the perfect example.

      • Justtyn Hutcheson

        I know, and I still don’t expect the AT&T and Verizon updates to surface officially for the next 2-4 weeks, but dang it a man can dream!

        And I surely hope we don’t end up using the GNex as an example of support for the Moto X. /shudder, and my sympathies to those brave (poor?) souls who actually wait for an OTA on that device.

      • http://www.droid-life.com Kellex B

        Also keep in mind that T-Mobile doesn’t care about the Moto X. Only way to get it currently is through Motorola’s site, so Moto can essentially do what they want with it heh.

        • Justtyn Hutcheson

          They will probably care a lot more once Moto Maker opens up but until then, there’s really no reason for them to. Besides, the T-Mobile version is pretty much identical to the GSM Developer Edition isn’t it, just with one less LTE Band?

          • Turb0wned

            Besides the storage.

        • EC8CH

          I wish that when Verizon doesn’t care about a phone it would mean the same thing :-(