#LTE DISCOVERY PRO UPDATE#
#LTE DISCOVERY PRO ANDROID#
#LTE DISCOVERY PRO PRO#
#LTE DISCOVERY PRO FREE#

It has LTE bands 2, 3, 4, 5, 7, 17, so I am lucky it has all the AT&T bands (2, 4, 5, 17). Actually, I own two and am running them both on AT&T network. 5.2', 1440p, Snapdragon 805, 3GB RAM, 64GB storage, Qi wireless charging, Turbo charging. I have the Moto XT1225, which is the 'international' version of the Verizon Droid Turbo XT1254, and is basically the 5.2' version of the Moto Nexus 6. I use AT&T GoPhone, which only has native AT&T service, not roaming.

They need to know specific bands being used in their area. IF there is one, please point me in that direction!Ī lot of people use prepaid carriers and BYOD. SUGGESTION: Have you ever considered creating a crowd sourced LTE bands coverage display map? For all carriers, but especially for AT&T.

#LTE DISCOVERY PRO PRO#

I use LTE Discovery app and I have the Pro Edition. I'm going to tinker around with some settings and hopefully it should be corrected in the next release.

#LTE DISCOVERY PRO UPDATE#

I'm sure this will probably fix itself whenever Google and Asus decide to get the Lollipop update out there.Hmmm well the SNR is likely an API restriction that we can't get around, but I think we should be able to correct the band identification. Truthfully, I wouldn't worry about this as I think the latest radio is getting confused because of Verizon's multi-band LTE. On every radio except the current one, the network identifies properly as 'Verizon Wireless' and LTE Discovery shows the band I'm connected to, but still shows the SNR as 'N/A.' I did a little more digging and it actually appears to be a radio issue. I'm sure this will probably fix itself whenever Google and Asus decide to get the Lollipop update out there.

#LTE DISCOVERY PRO ANDROID#

However, on the latest radio (which has appeared on every firmware since 4.4.2/KVT49L and is the one with 'official' support for Verizon), the network identifier from Android shows 311480 (MCC-MNC of Verizon's LTE network) and LTE Discovery does not even show a line for 'band,' plus the SNR shows 'N/A.' Attached is a screenshot. Hmmm there are a few API's we use that some phone manufacturers choose to not permit which cause issues like what you are describing, but I'd be pretty shocked if this were the case on a Nexus device (even if it is a tablet).Ĭould you post a screenshot of the signals page for me to take a quick look at?I did a little more digging and it actually appears to be a radio issue. It shows LTE signal strength properly but doesn't show the band and the SNR just says 'N/A.' Obviously the Nexus 7 is a bit unique when it comes to Verizon since it has no CDMA support and relies purely on the fact that VZW's network is pretty much 100% LTE at this point.Īlso, for what it's worth, Signal Check Pro seems to have the same problem. There appears to be issues with the Nexus 7 LTE (2013), or at least when there's a Verizon SIM in it. If you like it I'd recommend supporting him as a dev and purchasing the pro version. Just look for SignalCheckLite in the Google Play Store. He makes another great signal utility you might enjoy. If you want an alternative check out SignalCheck by BlueLineComputing (MikeJeep). (Actually if you wouldn't mind, could you just go ahead an email me your logs and I'll look over them for inconsistencies?)

#LTE DISCOVERY PRO FREE#

If you find out for sure otherwise though feel free to send us a debug email in app and we can look into it. In all my testing, AT&T band detection is probably one of the most reliable so I'd hazard to guess you are probably always on Band 17 lol. An AT&T Moto X is actually one of the devices we use to develop LTE Discovery on.

Lte discovery pro