Motorola explains the delay in updating the OG Moto X to Android 5.0

posted by Alan F. / Feb 10, 2015, 5:33 AM

Motorola explains the delay in updating the OG Moto X to Android 5.0

Those with the OG Motorola Moto X must feel like they are in a nightmare. Handsets all over the place, including models considered to be lower in the Moto pecking order like the Motorola Moto G and Motorola Moto E, have received or are in the process of soon receiving the update. And yes, the second generation Moto X has already been "Lollipopped."

So what is it about the OG Moto X that has prevented its owners from enjoying the latest and greatest Android build? A tweet sent out by Motorola Support on Monday in response to an inquiry, revealed that it is the chipset that is the culprit. While the second generation Moto X is driven by a quad-core Snapdragon 801 CPU, the OG model has an older dual-core Snapdragon S4 Pro processor under the hood.

The tweet says that the OG Motorola Moto X will get "L" (Android 5.0), but it is taking more effort on Motorola's part. There is no word from Motorola on when the update will be ready, but the important thing is that the manufacturer did say that it will eventually arrive. Obviously this is tough on those who own the device, but sitting around and stewing about it won't get you anything but an ulcer.You can decide to wait, try to catch a sympathetic ear from someone at Motorola or your carrier, or dig deep into your wallet to buy a new phone.

Motorola explains why the OG Moto X is stuck at Android 4.4.4 for now

source: @MotorolaSupport via STJSGadgets

Related phones

View Full specs

PhoneArena Rating:

8.5

Read Full Review

User Rating:

9.4

Based on 26 Reviews

Display 4.7" 720 x 1280 pixels

Camera 10 MP / 2 MP front

Processor Qualcomm Snapdragon S4 Pro, Dual-core, 1700 MHz

Storage 16 GB

Battery 2200 mAh(13h talk time)

FEATURED VIDEO

Options

40 Comments

1. Zomer

Posts: 361; Member since: May 31, 2013

In other words: the chips sucks and we are trying to make the most of it.

posted on Feb 10, 2015, 5:34 AM 1

2. Sniggly

Posts: 7305; Member since: Dec 05, 2009

It doesn't *suck,* since there are phones with equivalent or better chipsets that can run L just fine. There's probably just weird issues with the architecture that other chips don't have. It's not like Motorola would have known there would be such issues when they built the OG X, since it was long before Lollipop was finalized.

posted on Feb 10, 2015, 5:38 AM 3

9. sgodsell

Posts: 7464; Member since: Mar 16, 2013

If the dual core snapdragon 200 running at 1.2 GHz is able to run lollipop, then the dual core Snapdragon S4 pro running at 1.7 Ghz will be able to run lollipop as well. Its as simple as that. Just give it more time. Besides its really only been this year that lollipop is starting to move into more devices. It wasn't 2014 that saw the lollipop updates come (excluding Nexus and Android Wear devices).

posted on Feb 10, 2015, 7:02 AM 0

10. Sniggly

Posts: 7305; Member since: Dec 05, 2009

It's not about the speed, like I said. Likely has to do with the specific architecture of the chip, not to mention Motorola's modifications to it.

posted on Feb 10, 2015, 7:53 AM 0

19. Mxyzptlk unregistered

Excuses excuses.

posted on Feb 10, 2015, 9:56 AM 0

31. Scott93274

Posts: 6040; Member since: Aug 06, 2013

What's Apple's excuse for not fixing their instant messaging software? As far as I can tell, it still sending consumer's texts to a "black hole" when they switch platforms? This has been an issue for such a long time and their incompetence is inexcusable.

posted on Feb 10, 2015, 1:11 PM 1

33. Mxyzptlk unregistered

There's no excuse for it to not be fixed. Your point? Oh wait that was a straw man.

posted on Feb 10, 2015, 3:17 PM 2

36. 14545

Posts: 1835; Member since: Nov 22, 2011

What are you talking about? They are *updating it*, it's just taking longer because they have to massage the code more. Or they could just do like apple and release a bug ridden horrible POS of an OS.

posted on Feb 10, 2015, 3:26 PM 0

40. sgodsell

Posts: 7464; Member since: Mar 16, 2013

I think it has to do with Motorola's X8 computing system with the S4 pro CPU. The new Moto X doesn't have Motorola's X8 computing system.

posted on Feb 10, 2015, 6:07 PM 0

27. JC557

Posts: 1921; Member since: Dec 07, 2011

Yup, the HTC One M7 is getting Lollipop soon if it hasn't been already (I think some already received the update) and the Galaxy S4 should be seeing it in the coming months as well. The Snapdragon 600 is basically a Quad core S4 Pro. Maybe the HTC Droid DNA will get L later this year... hmmm... What this article fails to mention is that it's not off the shelf SnapDragon Pro, it's Moto's custom design around that SoC and is called X8. I had to get better detailing from PocketNow.

posted on Feb 10, 2015, 12:43 PM 0

15. kaikuheadhunterz

Posts: 1157; Member since: Jul 18, 2013

No, it means Qualcomm sucks for not providing drivers for Lollipop for this chipset

posted on Feb 10, 2015, 9:05 AM 0

18. Mxyzptlk unregistered

I called it. They pulled this stunt with the Atrix phones. Lol that's what they get for using an old outdated chip. I have a feeling the 2014 model will suffer the same fate eventually.

posted on Feb 10, 2015, 9:55 AM 0

22. roldefol

Posts: 4744; Member since: Jan 28, 2011

That's ridiculous, and you've already been proven wrong about the 2014 model. Also, it's only been a few months since Lollipop arrived. Yes, I would like to continue to receive upgrades, but I'd rather they be done right. And I would buy another Motorola based on my current device and their track record since 2012.

posted on Feb 10, 2015, 10:15 AM 0

24. Mxyzptlk unregistered

How's it ridiculous? Motorola screwed up by using a custom chip and now they're having issues getting the phone updated.

posted on Feb 10, 2015, 10:57 AM 0

25. roldefol

Posts: 4744; Member since: Jan 28, 2011

Because they didn't screw up. They took a calculated risk. They wanted to innovate with always-on capabilities, and no stock chipset would do what they needed to. So now they're having more trouble updating it, but I believe they will get the job done right.

posted on Feb 10, 2015, 11:27 AM 0

29. Mxyzptlk unregistered

Yeah but look at what that risk caused. They didn't learn the last time they used a custom chipset. Android and custom chipset do not mix well together.

posted on Feb 10, 2015, 12:55 PM 0

32. roldefol

Posts: 4744; Member since: Jan 28, 2011

What did that risk cause? An upgrade delay? How is that anything newsworthy in the Android world? They made a good product. We, the actual users, aren't complaining.

posted on Feb 10, 2015, 2:28 PM 0

34. Mxyzptlk unregistered

Could have been a good product. There's too many mistakes for it to be.

posted on Feb 10, 2015, 3:18 PM 0

39. roldefol

Posts: 4744; Member since: Jan 28, 2011

Moto's biggest mistake with the 2013 X was pricing. The hardware fit the software fit the size... but not the price. If they were able to get their hands on a 5" FHD screen at the time, they could have commanded a premium for it. But since they needed SAMOLED for Active Notifications (which I still think are brilliant), they were stuck with Sammy's 720p S-stripe from 2012. They made the most of what they were able to source.

posted on Feb 10, 2015, 4:22 PM 0

37. 14545

Posts: 1835; Member since: Nov 22, 2011

Having issues, and not updating it are two different things. They are still updating it, unlike with the Atrix, it's just taking them longer. Note: I thought the X8 was a decent idea, but clearly not the best. At least they are trying to fix it.

posted on Feb 10, 2015, 3:28 PM 0

3. mahebn26

Posts: 5; Member since: Jan 08, 2015

Even Nexus 7 runs on S4 Pro. The difference is in the number of cores

posted on Feb 10, 2015, 5:39 AM 1

8. UglyFrank

Posts: 2194; Member since: Jan 23, 2014

*S600

posted on Feb 10, 2015, 6:59 AM 1

12. Predator1701

Posts: 130; Member since: Oct 28, 2014

What do you mean S600 the Nexus 7 second gen. runs on Snapdragon S4 pro clocked at 1,5 Ghz.

posted on Feb 10, 2015, 8:05 AM 0

35. UglyFrank

Posts: 2194; Member since: Jan 23, 2014

S600 under clocked and branded as an S4 Pro

posted on Feb 10, 2015, 3:18 PM 0

4. Sniggly

Posts: 7305; Member since: Dec 05, 2009

I'm really hoping this doesn't turn into another Atrix issue, because that was much the same problem: new update (Ice Cream Sandwich) was hampered by issues with the chip's architecture (Tegra 2). That of course ended with the Atrix never being updated to ICS at all, which of course gave tons of ammo to Mxy at the time. In fact, I'm pretty sure that's when Mxy really became a regular poster on this site.

posted on Feb 10, 2015, 5:40 AM 0

20. Mxyzptlk unregistered

Oh it's exactly like the Atrix incident. Motorola screws up again by using a custom chip that ends causing issues for updates. Lol I called it.

posted on Feb 10, 2015, 9:58 AM 0

23. roldefol

Posts: 4744; Member since: Jan 28, 2011

The Atrix was a screw-up. Ditto the Bionic announcement/delay/cancelation/redesign. But that was four years ago now. Releasing a buggy mess would be a screw up. A delay so that the end product works properly is the exact opposite.

posted on Feb 10, 2015, 10:21 AM 0

30. Sniggly

Posts: 7305; Member since: Dec 05, 2009

The Tegra 2 wasn't custom. It was the exact same chip used in many devices, and at the time Nvidia was enough of a trusted name with their GPUs several manufacturers, not just Motorola, jumped for their debut chipset. So no, not exactly the same, and Lollipop is still coming to the 2013 X. Just not as fast as Motorola hoped obviously.

posted on Feb 10, 2015, 1:03 PM 0

21. Mxyzptlk unregistered

And nice of you to call me out. Of course I'm going to run with this.