Jump to content

Moto X 2014 (was "Motorola IHDT56QA1")


NateC

Recommended Posts

Just spotted on the FCC website.

 

 http://www.phonescoop.com/phones/fcc_query.php?gc=IHD&pc=T56QA1

 

(just using phonescoop.com to redirect to the appropriate FCC page)

 

This appears to be a flagship-level device since it supports LTE, NFC, WiFi on 2.4 and 5 GHz, etc.  This variant is intended for AT&T/T-Mobile based on the supported bands.

 

Device dimensions: 

   Height: 140 mm (5.51")

   Width: 72.6 mm (2.86")

   Screen diagonal: 149 mm (5.87")

 

Based on that, it's probably the rumored Moto "Shamu"?

Link to comment
Share on other sites

Just spotted on the FCC website.

 

 http://www.phonescoop.com/phones/fcc_query.php?gc=IHD&pc=T56QA1

 

(just using phonescoop.com to redirect to the appropriate FCC page)

 

This appears to be a flagship-level device since it supports LTE, NFC, WiFi on 2.4 and 5 GHz, etc.  This variant is intended for AT&T/T-Mobile based on the supported bands.

 

Device dimensions: 

   Height: 140 mm (5.51")

   Width: 72.6 mm (2.86")

   Screen diagonal: 149 mm (5.87")

 

Based on that, it's probably the rumored Moto "Shamu"?

 

I hope it isn't the new Nexus...  I would certainly hope that Sprint would get the next one, but this tells otherwise since I don't see them making more than one US variant.

Link to comment
Share on other sites

I hope it isn't the new Nexus...  I would certainly hope that Sprint would get the next one, but this tells otherwise since I don't see them making more than one US variant.

 

I'm disappointed to see that it doesn't support AT&T/T-Mobile/Sprint bands all in one device like the Nexus 5 did.  I was really hoping that would become the norm.

 

Also, the other reason I hope this isn't the basis for the new Nexus is because it's too damn big.  The Nexus 5 is already too big in my opinion, and this device is even *larger*.

  • Like 1
Link to comment
Share on other sites

This appears to be a flagship-level device since it supports LTE, NFC, WiFi on 2.4 and 5 GHz, etc.  This variant is intended for AT&T/T-Mobile based on the supported bands.

 

 

LTE Band support includes 2, 4, 5, 7, 17, and 29 so its definitely an AT&T variant. I can't find the document which details the LTE Carrier Aggregation pairs unless its under short-turn confidentiality.

Link to comment
Share on other sites

The Nexus is a perfect device for the direction that Sprint is going with Easy Pay. It is a damn good device at a reasonable price (even with the carrier markup).

 

Sent from my Nexus 7 using Tapatalk

  • Like 1
Link to comment
Share on other sites

Droid Life believes this device is the new Moto X (the AT&T variant), which would make sense...  A sliver of hope yet again.

 

Quote from Droid Life below:

 

Since many are assuming that the FCC’s measurement of 149mm across the display screen means a 5.9-inch display on the phone, I’ll have to stop you there. Keep in mind that the LG G3 has a 5.5-inch display with minimal bezel, yet it measures 146.3×74.6mm. There is no way that the new Moto X can measure 140×74.6mm, yet have a display that is .4-inches bigger than the LG G3. It’s just not possible. The FCC filing is likely just misrepresenting the situation here a bit by putting “display screen” on the image to indicate that this is the front of the phone. These measurements are for the entire phone, not just the display.

 

Link to comment
Share on other sites

Droid Life believes this device is the new Moto X (the AT&T variant), which would make sense...  A sliver of hope yet again.

 

Quote from Droid Life below:

 

Yeah, I considered that possibility as well.  It's really confusing though, because if it's *not* the display diagonal dimension, then what is it?  It can't be the chassis dimensions, because sqrt(72.6^2 + 140^2) != 149^2.  If we consider reasonable bezel sizes, it would in fact suggest that 149 mm is not the diagonal screen size.  If we consider mathematical truths, then H=140mm, W=72.6mm can't have a diagonal of 149mm, suggesting they are not chassis sizes.  So what is it?

Link to comment
Share on other sites

Yeah, I considered that possibility as well.  It's really confusing though, because if it's *not* the display diagonal dimension, then what is it?  It can't be the chassis dimensions, because sqrt(72.6^2 + 140^2) != 149^2.  If we consider reasonable bezel sizes, it would in fact suggest that 149 mm is not the diagonal screen size.  If we consider mathematical truths, then H=140mm, W=72.6mm can't have a diagonal of 149mm, suggesting they are not chassis sizes.  So what is it?

 

Just throwing out an idea...  Could be completely off, but I don't know how they specifically measure these things. 

 

What about the fact that the edges are likely curved?  The chassis diagonal will be slightly lower than the equation would say.  It's not like the original Moto X was a complete rectangle...

Link to comment
Share on other sites

Just throwing out an idea...  Could be completely off, but I don't know how they specifically measure these things. 

 

What about the fact that the edges are likely curved?  The chassis diagonal will be slightly lower than the equation would say.  It's not like the original Moto X was a complete rectangle...

 

That seems reasonable to me.  Either way it's confusing since the diagram doesn't show rounded corners:

 

5bPNz6T.png

 

 

And you are right that the device certainly won't have completely straight corners.  But it's still weird that they'd draw the dimension that way going sharp corner to sharp corner.  I think the conclusion is that we can't read too much into that diagram either way.  Whatever it is, it's much bigger than the original Moto X.

Link to comment
Share on other sites

Yeah, I considered that possibility as well.  It's really confusing though, because if it's *not* the display diagonal dimension, then what is it?  It can't be the chassis dimensions, because sqrt(72.6^2 + 140^2) != 149^2.  If we consider reasonable bezel sizes, it would in fact suggest that 149 mm is not the diagonal screen size.  If we consider mathematical truths, then H=140mm, W=72.6mm can't have a diagonal of 149mm, suggesting they are not chassis sizes.  So what is it?

 

FCC OET authorization documents show device dimensions.  They do not necessarily show screen sizes.  That is not of interest to the FCC.

 

AJ

Link to comment
Share on other sites

I'm going with Moto x+1.. Were still a few months from OET / FCC on the Nexus X/6/or wtf model you want.. The X+1 is only a week away.. So I would suspect to see a bunch of OET / FCC postings coming. 

Link to comment
Share on other sites

I'm going with Moto x+1.. Were still a few months from OET / FCC on the Nexus X/6/or wtf model you want.. The X+1 is only a week away.. So I would suspect to see a bunch of OET / FCC postings coming. 

Yeah this looks like the GSM version of the Moto X+1.  I doubt it'd be the Nexus since we're still in August!

 

Uh, guys, I am not saying that this handset is the next Nexus, but you forget history.  Last summer in late July, S4GRU staff saw a mystery LG handset uploaded to the FCC OET, then pulled back.  It reappeared permanently in the FCC OET the first week in September, and none other than S4GRU was the first to connect the dots, then break the story that the handset was the Nexus 5.

 

http://s4gru.com/index.php?/blog/1/entry-351-teaser-is-the-lg-d820-the-nexus-5/

 

We are now coming up on that same week this year, so do not be surprised if the next Nexus handset gets outed at the FCC OET soon.

 

AJ

Link to comment
Share on other sites

Uh, guys, I am not saying that this handset is the next Nexus, but you forget history.  Last summer in late July, S4GRU staff saw a mystery LG handset uploaded to the FCC OET, then pulled back.  It reappeared permanently in the FCC OET the first week in September, and none other than S4GRU was the first to connect the dots, then break the story that the handset was the Nexus 5.

 

http://s4gru.com/index.php?/blog/1/entry-351-teaser-is-the-lg-d820-the-nexus-5/

 

We are now coming up on that same week this year, so do not be surprised if the next Nexus handset gets outed at the FCC OET soon.

 

AJ

Not to argue as I agree with most your posts but your comparing two entirely different companies. Moto for the most part doesn't typically, I say that due to the fact they have posted some earlier then others, but they usually post within a month of release. That lg fiasco was bad, and they had a very similar release again the g3. Looking back at moto x for example FCC filing was July 26th'sh announcement followed weeks after and release September. Following that as a guideline I'd say we most likely will see a filing towards mid/end sept then googles announcement. But just opinion :)

Link to comment
Share on other sites

Not to argue as I agree with most your posts but your comparing two entirely different companies. Moto for the most part doesn't typically, I say that due to the fact they have posted some earlier then others, but they usually post within a month of release. That lg fiasco was bad, and they had a very similar release again the g3. Looking back at moto x for example FCC filing was July 26th'sh announcement followed weeks after and release September. Following that as a guideline I'd say we most likely will see a filing towards mid/end sept then googles announcement. But just opinion :)

 

Ah, but with the release of a Nexus device, which company wears the pants -- the OEM or Google?  As I recall, the Asus tablets, for example, hit the FCC OET months in advance.

 

AJ

Link to comment
Share on other sites

Ah, but with the release of a Nexus device, which company wears the pants -- the OEM or Google?  As I recall, the Asus tablets, for example, hit the FCC OET months in advance.

 

AJ

Well this could go into realm of typically. But not sure if this will be the case and I do remember the posting for n5 being submitted via lg and not google as they were manufacturer. Google only designs and agrees with it, the manufacturer submits the follow up.

Link to comment
Share on other sites

Well this could go into realm of typically. But not sure if this will be the case and I do remember the posting for n5 being submitted via lg and not google as they were manufacturer. Google only designs and agrees with it, the manufacturer submits the follow up.

 

Yes, the OEM is the grantee of record at the FCC OET.  But my argument is that Google runs the show as much as, if not more than the OEM.  And that is borne out when the Nexus devices end up in the hands of Google employees for real world testing months in advance.

 

AJ

Link to comment
Share on other sites

And now today the IHDT56QA2 variant was spotted.

 

LTE bands supported: 2 (1900 MHz), 4 (1700 MHz), 7 (2600 MHz), 13 (700 MHz)

CDMA, GSM, and UMTS: 850 MHz and 1900 MHz

 

This one could be for Verizon?

  • Like 1
Link to comment
Share on other sites

And now today the IHDT56QA2 variant was spotted.

 

LTE bands supported: 2 (1900 MHz), 4 (1700 MHz), 7 (2600 MHz), 13 (700 MHz)

CDMA, GSM, and UMTS: 850 MHz and 1900 MHz

 

This one could be for Verizon?

Canada.

 

Sent from my Nexus 5 using Tapatalk

Link to comment
Share on other sites

Canada.

 

Sent from my Nexus 5 using Tapatalk

 

Ah.  I noticed the Bell/Rogers band 7 support, but I figured maybe they just included that in there for roaming/compatibility purposes.  I also didn't think they'd do the Canadian version before Sprint/Verizon/T-Mobile, but I don't really know.

Link to comment
Share on other sites

And now today the IHDT56QA2 variant was spotted.

 

LTE bands supported: 2 (1900 MHz), 4 (1700 MHz), 7 (2600 MHz), 13 (700 MHz)

CDMA, GSM, and UMTS: 850 MHz and 1900 MHz

 

This one could be for Verizon?

Canada.

 

You both could be correct.  Canada is small potatoes, so its operators generally do not get their own handset variants.  Rather, they get piggybacked on a US operator variant.  But this handset does not appear to support SVLTE, making it unlikely to be headed to VZW, despite the boutique band 13 capability.

 

AJ

Link to comment
Share on other sites

You both could be correct.  Canada is small potatoes, so its operators generally do not get their own handset variants.  Rather, they get piggybacked on a US operator variant.  But this handset does not appear to support SVLTE, making it unlikely to be headed to VZW, despite the boutique band 13 capability.

 

AJ

 

Good point with SVLTE. That leaves the couple million non-Big 3 Canadian mobile providers holding 700 MHz C1 blocks. Maybe later re-certification is possible too.

Edited by atomic50
Link to comment
Share on other sites

According to the spec, the Sprint Moto X (2014) should be model XT1092 with specs below:

 

GSM/GPRS/EDGE (850, 900, 1800, 1900 MHz);

UMTS/HSPA+ (850, 900, 1700 (AWS), 1900, 2100 MHz);

CDMA (850/1900 MHz);

4G LTE (02, 04, 05, 12, 17, 25, 26, 41)

 

It appears it will work on all major US carriers except Verizon similar to the Nexus 5!

  • Like 12
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • large.unreadcontent.png.6ef00db54e758d06

  • gallery_1_23_9202.png

  • Posts

    • Since this is kind of the general chat thread, I have to share this humorous story (at least it is to me): Since around February/March of this year, my S22U has been an absolute pain to charge. USB-C cables would immediately fall out and it progressively got worse and worse until it often took me a number of minutes to get the angle of the cable juuuussst right to get charging to occur at all (not exaggerating). The connection was so weak that even walking heavily could cause the cable to disconnect. I tried cleaning out the port with a stable, a paperclip, etc. Some dust/lint/dirt came out but the connection didn't improve one bit. Needless to say, this was a MONSTER headache and had me hating this phone. I just didn't have the finances right now for a replacement.  Which brings us to the night before last. I am angry as hell because I had spent five minutes trying to get this phone to charge and failed. I am looking in the port and I notice it doesn't look right. The walls look rough and, using a staple, the back and walls feel REALLY rough and very hard. I get some lint/dust out with the staple and it improves charging in the sense I can get it to charge but it doesn't remove any of the hard stuff. It's late and it's charging, so that's enough for now. I decide it's time to see if that hard stuff is part of the connector or not. More aggressive methods are needed! I work in a biochem lab and we have a lot of different sizes of disposable needles available. So, yesterday morning, while in the lab I grab a few different sizes of needles between 26AWG and 31 AWG. When I got home, I got to work and start probing the connector with the 26 AWG and 31 AWG needle. The stuff feels extremely hard, almost like it was part of the connector, but a bit does break off. Under examination of the bit, it's almost sandy with dust/lint embedded in it. It's not part of the connector but instead some sort of rock-hard crap! That's when I remember that I had done some rock hounding at the end of last year and in January. This involved lots of digging in very sandy/dusty soils; soils which bare more than a passing resemblance to the crap in the connector. We have our answer, this debris is basically compacted/cemented rock dust. Over time, moisture in the area combined with the compression from inserting the USB-C connector had turned it into cement. I start going nuts chiseling away at it with the 26 AWG needle. After about 5-10 minutes of constant chiseling and scraping with the 26AWG and 31AWG needles, I see the first signs of metal at the back of the connector. So it is metal around the outsides! Another 5 minutes of work and I have scraped away pretty much all of the crap in the connector. A few finishing passes with the 31AWG needle, a blast of compressed air, and it is time to see if this helped any. I plug my regular USB-C cable and holy crap it clicks into place; it hasn't done that since February! I pick up the phone and the cable has actually latched! The connector works pretty much like it did over a year ago, it's almost like having a brand new phone!
    • That's odd, they are usually almost lock step with TMO. I forgot to mention this also includes the September Security Update.
    • 417.55 MB September security update just downloaded here for S24+ unlocked   Edit:  after Sept security update install, checked and found a 13MB GP System update as well.  Still showing August 1st there however. 
    • T-Mobile is selling the rest of the 3.45GHz spectrum to Columbia Capital.  
    • Still nothing for my AT&T and Visible phones.
  • Recently Browsing

    • No registered users viewing this page.
×
×
  • Create New...