Jump to content

Google Nexus 6 by Motorola Users Thread


WiWavelength

Recommended Posts

How in the world would an engineering screen indicate if "carrier aggregation was around"? Are you using the Nexus 6 on Sprint? It does not support band 41 carrier aggregation.

 

AJ

Also there is a way to see if you have carrier aggregation I have seen it before on the internet
Link to comment
Share on other sites

Also there is a way to see if you have carrier aggregation I have seen it before on the internet

 

Not relevant.  Not on the Nexus 6.  Remember which thread this is.

 

AJ

Link to comment
Share on other sites

the CA bands in the specs section add up to Verizon and At&t bands. I have no indication if it is able to do this but there is no proof that it can't either.

 

VZW does not do carrier aggregation -- its band 13 infrastructure is too old. And I have seen no indication that the Nexus 6 supports carrier aggregation at all, not even for AT&T.

 

AJ

  • Like 1
Link to comment
Share on other sites

 

 

That is true.  I had forgotten that the Google Play specs do make mention of LTE FDD carrier aggregation capabilities.  The FCC OET filing, however, does not.

 

And, despite your pipe dream to the contrary, VZW is not currently doing carrier aggregation.  Its infrastructure does not support it.

 

Now, fix your quote.  Do NOT put your text in my quote box.

 

AJ

  • Like 2
Link to comment
Share on other sites

That is true. I had forgotten that the Google Play specs do make mention of LTE FDD carrier aggregation capabilities. The FCC OET filing, however, does not.

 

And, despite your pipe dream to the contrary, VZW is not currently doing carrier aggregation. Its infrastructure does not support it.

 

Now, fix your quote. Do NOT put your text in my quote box.

 

AJ

I figured Verizon wouldn't work my hope is solely for At&t.
Link to comment
Share on other sites

Does anybody know how to remove the keyboard icon at the bottom of the screen when I'm using Swype?  I keep hitting it with my thumb accidentally.

Link to comment
Share on other sites

I figured Verizon wouldn't work my hope is solely for At&t.

 

It looks like the Nexus 6 actually does technically support carrier aggregation for Verizon and AT&T bands.

 

http://www.extremetech.com/extreme/192101-nexus-6-the-best-android-smartphone-for-wireless-and-lte-connectivity

 

This doesn't necessarily mean you'll actually get carrier aggregation on Verizon (in part, for the reasons already mentioned) but technically, the Nexus 6 supports carrier aggregation on Verizon and AT&T.

  • Like 1
Link to comment
Share on other sites

Is anyone having issues with ambient display? Mine worked for a bit and now it's not working at all.

Sent from my Nexus 5 using Tapatalk

At least your screen didn't die the first day making it a very expensive paper weight. Lol. But luckily this one I have now works great!

 

The front speakers are soooooo awesome sounding!

Link to comment
Share on other sites

SIAP, but is WiFI calling isn't presently baked into the N6, but will be in the future right? (believe TMO has said its coming in 2015). 

 

In theory,  wouldn't it logically follow that it could also be coming to the N5 around the same time? 

 

TIA.

Link to comment
Share on other sites

for those interested in the encrypted vs non-encrypted argument

 

 

Wowsers!

Link to comment
Share on other sites

 

So if I purchaed my n6 with a 2 year contract already say on the 19th does that mean I can call up sprint about this and I will get it since its within the 14 days?

Link to comment
Share on other sites

Anyone have any luck getting to the engineering screens or field test mode yet?

Link to comment
Share on other sites

Still nothing, even with the apk in the system folder.

 

Yeah thats a bummer.  Well i guess lets give it some time and see if anyone figures it out!  perhaps we should all fund a call to action on this.  Put out a bounty and see if anyone can access it.

Link to comment
Share on other sites

Yeah I been playing with it for a few days now trying to force start it, playing with permissions. No good. So there must be new commands or an additional program that sprint has that needs to be loaded (apk) to use there DMsprint app thats in the system folder. A big concern, looking at this sprint DM service, not saying its not on n5 or other devices, its looking and controlling insane permissions.. 

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

    • On Reddit, someone asked (skeptically) if the US Cellular buyout would result in better service.  I'd been pondering this very issue, and decided to cross-post my response here: I've been pondering the question in the title and I've come to the conclusion that the answer is that it's possible. Hear me out. Unlike some of the small carriers that work exclusively with one larger carrier, all three major carriers roam on US Cellular today in at least some areas, so far as I know. If that network ceases to exist, then the carriers would presumably want to recover those areas of lost service by building out natively. Thus, people in those areas who may only have service from US Cellular or from US Cellular and one other may gain competition from other carriers backfilling that loss. How likely is it? I'm not sure. But it's definitely feasible. Most notably, AT&T did their big roaming deal with US Cellular in support of FirstNet in places where they lacked native coverage. They can't just lose a huge chunk of coverage whole still making FirstNet happy; I suspect they'll have to build out and recover at least some of that area, if not most of it. So it'd be indirect, but I could imagine it. - Trip
    • Historically, T-Mobile has been the only carrier contracting with Crown Castle Solutions, at least in Brooklyn. I did a quick count of the ~35 nodes currently marked as "installed" and everything mapped appears to be T-Mobile. However, they have a macro sector pointed directly at this site and seem to continue relying on the older-style DAS nodes. Additionally, there's another Crown Castle Solutions node approved for construction just around the corner, well within range of their macro. I wouldn’t be surprised to see Verizon using a new vendor for their mmWave build, especially since the macro site directly behind this node lacks mmWave/CBRS deployment (limited to LTE plus C-Band). However, opting for a multi-carrier solution here seems unlikely unless another carrier has actually joined the build. This node is equidistant (about five blocks) between two AT&T macro sites, and there are no oDAS nodes deployed nearby. Although I'm not currently mapping AT&T, based on CellMapper, it appears to be right on cell edge for both sites. Regardless, it appears that whoever is deploying is planning for a significant build. There are eight Crown Castle Solutions nodes approved for construction in a 12-block by 2-block area.
    • Starlink (1900mhz) for T-Mobile, AST SpaceMobile (700mhz and 850mhz) for AT&T, GlobalStar (unknown frequency) for Apple, Iridium (unknown frequency) for Samsung, and AST SpaceMobile (850mhz) for Verizon only work on frequency bands the carrier has licensed nationwide.  These systems broadcast and listen on multiple frequencies at the same time in areas much wider than normal cellular market license areas.  They would struggle with only broadcasting certain frequencies only in certain markets so instead they require a nationwide license.  With the antennas that are included on the satellites, they have range of cellular band frequencies they support and can have different frequencies with different providers in each supported country.  The cellular bands in use are typically 5mhz x 5mhz bands (37.5mbps total for the entire cell) or smaller so they do not have a lot of data bandwidth for the satellite band covering a very large plot of land with potentially millions of customers in a single large cellular satellite cell.  I have heard that each of Starlink's cells sharing that bandwidth will cover 75 or more miles. Satellite cellular connectivity will be set to the lowest priority connection just before SOS service on supported mobile devices and is made available nationwide in supported countries.  The mobile device rules pushed by the provider decide when and where the device is allowed to connect to the satellite service and what services can be provided over that connection.  The satellite has a weak receiving antenna and is moving very quickly so any significant obstructions above your mobile device antenna could cause it not to work.  All the cellular satellite services are starting with texting only and some of them like Apple's solution only support a predefined set of text messages.  Eventually it is expected that a limited number of simultaneous voice calls (VoLTE) will run on these per satellite cell.  Any spare data will then be available as an extremely slow LTE data connection as it could potentially be shared by millions of people.  Satellite data from the way these are currently configured will likely never work well enough to use unless you are in a very remote location.
    • T-Mobile owns the PCS G-block across the contiguous U.S. so they can just use that spectrum to broadcast direct to cell. Ideally your phone would only connect to it in areas where there isn't any terrestrial service available.
  • Recently Browsing

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