Microsoft has relented after massive outrage. The company has set up a special web site where you can opt-in to preserving your current free 30GB storage.

The company recently announced it was withdrawing plans to offer unlimited storage for Office 365 customers, and worse, was reducing all free accounts to 5GB. Previously, Microsoft offered 15GB of free storage, and customers that enabled OneDrive’s mobile phone photo sync feature received another 15GB, for a total of 30GB of free storage.

Microsoft claimed the changes were sparked by PC users backing up extremely large files. OneDrive client sync allowed for large files, even DVR recordings, to be automatically stored on OneDrive. But the reduction of free plans was considered brash by many – as those plans did not cost Microsoft nearly as much, and many competitors like Box have routinely offered free 50GB plans.

At 30GB, OneDrive was one of the largest free storage solution of all the major OS/cloud platform vendors. Also Office 365 customers who had backed up terrabytes already, are being forced to reduce to 300GB of storage, or being forced to pay for storage.

This is a friendly, Internet-wide reminder that you only have about 96 hours until T-Mobile USA’s new Data Stash rules go into effect. But, you can easily opt out if you wish.

What’s Changing?

As part of offering Binge On, unlimited 480p/standard-definition streaming video, T-Mobile is capping the amount of data you can roll over each month. The limit will be 20GB.

I don’t like that, what can I do?

T-Mobile is letting people opt-out, and keep their Data Stash unlimited. You must text DATAROLL to 6255 before the 16th.

We recommend doing it well before the end of the day on the 15th (like, right now), as T-Mobile’s servers appear to run on East Coast time. So 11 PM on the 15th may be too late on the West Coast, for example.

What happens if I opt-out?

If you text DATAROLL to 6255, you will continue to be able to stash an unlimited amount of data. But you will lose Binge On’s unlimited streaming functionality.

I want to opt-out, but Binge On is currently enabled. Did I screw up?

No. You can still opt-out before the 16th. T-Mobile is letting people test drive Binge On – and automatically opting them in. If you text DATAROLL to 6255, that’s all you need to do.

What happens if I turn Binge On back on, even for a second?

Some have reported you will lose unlimited Data Stash. Even if you use Binge On for one minute. As Apple used to say in support documents “like a hoard of bees, avoid this option.”

Clarification: Others related to T-Mobile have reported that enabling Binge On (post-DATAROLL) will not kick you off unlimited stash, but will use data even at 480p streaming quality. We are trying to get confirmation from T-Mobile, like everyone else in this boat.

What happens if I sign up for T-Mobile as a new customer?

Sorry, new customers can’t opt-out after the 15th. We’re unsure what happens if you sign up today. Since there are no contracts, you may want to try and sign up in the next 72 hours, if losing unlimited Data Stash is a deal-breaker. T-Mobile has a courtesy cancellation window, so you will be able to find out without incurring much cost.

Just don’t forget to text DATAROLL to 6255 if you want to try signing up before the 16th, as an attempt to get grandfathered.

And yeah, we wrote that last sentence just to remind you to text DATAROLL to 6255 one more time. And that one too.

Um, is it lame how T-Mobile is handling this?

Somewhat, yes. T-Mobile is not informing consumers about this change, opting-in to the 20GB cap without warning… and making it a secret trick to opt-out and keep unlimited Data Stash.

That is their right, these plans are not contract plans. T-Mobile is under no obligation to let anyone keep unlimited Data Stash, as a result.

But, making the opt-out some secret that only mobile nerds know about, is pretty lame. We suspect many will find out later, that they could have opted-out, but weren’t informed of the option. As a result – they may be quite angry at T-Mobile. And they wouldn’t be wrong to feel that way.

Furthermore, the 20GB Data Stash cap may sour potential new customers from signing up. For some, T-Mobile’s Data Stash was an attractive backup Internet connection option – for using large amounts of tethering during extended hotel stays or other travel plans. For new customers at least, that won’t be an option – or at least, will be considerably limited in its efficacy.

Our take? At PhoneNews.com, we feel T-Mobile should not make this a grandfathering affair. Let people decide. Binge On, and cap Data Stash at 20GB… or Binge Off, and let the Data Stash roll.

Either way, we encourage everyone to text DATAROLL to 6255 – and lock in the option. You can always flip Binge On back on later… you just can’t go back when you do.

The Samsung Gear S2 brought a lot of new features to the Tizen smartwatch implementation of HERE Maps. Most notably, and long asked for, is the ability to do driving navigation autonomously from the watch. The original Gear S could do offline maps, and autonomous navigation, but curiously it would only do that for mass transit (autonomously) and walking directions (when paired with a Samsung phone)… it does not provide navigation for driving your own car, even when paired to a phone.

With the Gear S having the same Tizen app compatibility range as the Gear S2, and some preferring the curved/larger screen of the original Gear S, many wanted to know if HERE was going to update the Gear S version of the app.

Sadly, the answer is no. HERE today confirmed to PhoneNews.com that driving directions, and all the HERE Maps enhancements in the Gear S2 version, will remain exclusive to the Gear S2. “Driving directions will only be available for the Gear S2…” was the brief statement that HERE provided to us on the subject.

The Gear S is now available in refurbished form for as little as $150, complete with unlocked 3G radio and GPS. But without app providers maintaining support, Gear S owners may be in for an isolated existence.

Android’s fragmentation framework provides more traditional support for older devices, by making it simple for older Android System versions to be supported with newer app upgrades. It appears that Tizen may not have the same kind of backwards compatibility, despite its rootings in the Qt framework.

This may not completely be HERE’s fault, however. HERE Maps is a system app, and can only be updated with a Gear S firmware update. Considering the costs of updating firmware (including carrier approval, needed on the Gear S on all four carriers), Samsung may not be interested in subjecting an updated HERE Map app to carriers for scrutiny – particularly on a device that they no longer sell.

This bad news comes as Samsung is racing to improve adoption for the Gear S2. It was revealed this week that Samsung may be working to implement iOS support, similar to Android Wear for iOS. The Gear S2, unlike the Gear S, already works with non-Samsung Android phones natively.

Canon is offering the PowerShot SX400 IS for $49.99 with free shipping and a free soft case. While refurbished, Canon backs it with a one year warranty.

This is an excellent low-cost high-zoom shooter with 30x optical zoom, 720P HD Video and SD memory card support. Only downside is that like most Canons, it requires an external AC adapter. Alternatives like the Nikon L-series use AA batteries, but haven’t been sold for this cheap ever.

This is a great camera for your glovebox as it provides very long battery life without recharging, and is perfect for grabbing that last-minute shot… or for when someone backs into your rear bumper. Because, nothing is worse than having a dead phone and being rear-ended at the same time. Been there, done that.

We pick back up with coverage before our re-launch in 2016. New look, new domain, new people writing new news.

RingPlus has launched yet another new “Future” plan, in their effort to test out high-capacity free/freemium plans.

The new plan, Future 9.0, is open to all for new device activations and lines of service. It is not currently open to existing RingPlus subscribers, unless they activate a completely new device that has not been used on RingPlus in the past 30 days.

Future 9.0 differs from past plans slightly. It features 1,500 minutes and 1,500 text messages… but only 500MB of 4G LTE-capable data. That’s 500 extra minutes and texts, but 500MB less than previous Future plans.

It appears RingPlus is testing to see if the reduction in data is still enough to woo over customers from rival FreedomPop. FreedomPop offers 200 minutes and 500MB of data per month on their standard BYOD plan, with a $19.99/month unlimited minute plan, and a $2.50/month add-on option that bypasses VoIP for Sprint CDMA voice coverage.

RingPlus differs from FreedomPop in that it does not require VoIP, instead using Sprint CDMA with RingPlus handling VoIP traffic on their backend – instead of the device itself. This means RingPlus can use nearly every CDMA and/or LTE phone that Sprint has sold this century.

Also, like past Future plans, the plan is not totally free – it requires a minimum account balance of $5, which will auto-refill from your credit card to cover any overage costs.

No word on how many device activations RingPlus will allow, but if you want one, you should activate at https://ringplus.net as soon as possible.

The Sprint Freemium MVNO typically offers “truly” free data plans ranging from 100 to 300MB. Additional free plans, like this one, require a one-time deposit of $5, followed by mandatory overage reloads – so if you go over on talk/text/data, your credit card will be directly billed.

This “Future 8.0” plan, is the eighth time they’ve offered this very coveted free plan. As with each of the seven times in the past, there’s a catch…

The Future 8.0 edition is only open to people bringing in a Nexus or iPhone device, such as from another carrier. A user will sign up at https://store.ringplus.netbeginning at 12 PM Pacific, later today. You will enter the IMEI/MEID of your Nexus 5, Nexus 6, or iPhone 5c, 5s, 6, 6 Plus, 6S, or 6S Plus. Sprint-branded/sold iPhone and Nexus devices are also included in the offering.

You will then be offered a RingPlus SIM (UCCID, in Sprint speak), for $25. Add in another $10 for the required minimum account balance, and for $35 you can convert your Nexus or iPhone device into a truly-free every-month Sprint phone.

Oh, and you’re required to tweet or post on Facebook with the #ringplus after signing up – based on the “honor system” in their words.

RingPlus, as we’ve mentioned in greater detail in the past, is valued because of their broad compatibility with most Sprint 3G and 4G phones, dating all the way back to the Sony Ericsson T608 and other 2003-era phones – all the way up to 4G LTE phones of today.

Roaming is also available, but you must link a checking account for direct billing to opt-in.

Normally, users can bring their own device, and you still can get a free plan. Even more-basic devices like the $39.99 Sprint Prepaid Moto E (available at Best Buy) can use 4G LTE data on RingPlus’s standard-trim plans.

And, likewise, if you don’t need that much talk, text, and data, you can purchase your own blank Sprint UCCID for around $20 at any Sprint corporate retail store, and then log on to RingPlus.net and activate it on a free plan.

For those that miss out, fear not. It appears RingPlus is racking up quite a large amount of cash from these $10 minimum account balances – it’s quite likely they will continue to offer the Future plan to current customers (as they have done in the past, already).

Google spent thousands promoting the launch-day coup of a Sanrio official Hello Kitty, Android Wear tie-in. Now that watch face has vanished.

One of the major features of Android Wear 5.1 that puts it above Apple Watch, and its watchOS 2, is that (since launch) their watch faces have been user-customizable. Anyone can create their own custom watch face, and submit it to the Google Play Store.

Apple today, in comparison, only allows pre-defined watch faces, including a tie-in with Disney. Disney previously had exclusive product tie-ins with Nokia in the 1990s that are credited for helping make Nokia (at the time) the world’s largest phone maker.

It’s not clear why the watch face has been removed. Neither Google nor Sanrio has even acknowledged the removal. However, it may come down to cost. With millions downloading the free watch face, Sanrio may have had a change of heart with offering it for free. Most Hello Kitty mobile wares, outside of fremium games, have had at least a $.99 charge tied to them.

It’s also possible the free watch face was bought and paid for by Google, and now that the launch festivities have ended, Sanrio may offer the watch face later as a paid download.

Apple offers a similar ability for existing downloaders to continue to use some apps that have been taken off the App Store. However, that is not always the case. It is up to the app publisher. In some rare circumstances, Apple and others like Amazon have even gone as far as to remove an app completely – even for those that bought and paid for that.

The Sanrio mystery is a great example of why sideloading and the ability to physically back up app purchases is important. While Google is still offering the app available for download (to existing/grandfathered users), that isn’t always the case. By being able to sideload apps – and back them up physically – users can ensure that a product going dark online… doesn’t mean the users can no longer enjoy them.

Google has inferred something troubling about the new Nexus 5X and 6P – they don’t seem to support Qualcomm QuickCharge technology. Despite the fact that QuickCharge 2.0 and 3.0 are compatible with the new USB-C port, the new Nexus Snapdragon 808 & 810 devices will only charge at standard USB speeds.

In this article, we dive deep on Qualcomm, and Intel/USB-IF’s rival accelerated charging standards… and why Google likely cut a corner here.

What is Qualcomm QuickCharge Technology?

In a nutshell, QuickCharge is a tool that Qualcomm uses to push more power over USB lines, than the USB specification allows.

The tactic is not new. Apple pioneered it, and got away without reprisal from the USB Implementation Forum. Apple has used the USB-IF to punish others (ahem, Palm), but this time – they got through without reprimand. Thankfully, it’s a good thing. It has helped prevent USB from needing auxiliary charging ports.

When you plug an iPad into its USB wall charger, or an iPhone into a Macintosh computer – something special happens. The charger and mobile device perform a hardware handshake, by phasing their voltage regulation in a rhythmic manner. This variance is statistically impossible to occur otherwise, and validates that the two devices can supply and receive amperage higher than what the USB specification allows.

HP followed suit with its webOS TouchPad, then Samsung did the same… and now Qualcomm has standardized the practice across multiple device makers, with one single standard. Since most high-end mobile devices today use Qualcomm SoC’s, it was logical for Qualcomm to provide the standard.

By default, QuickCharge 2.0 provides up to 18W of power, through two alternate amperage/voltage combinations. The preferable rate is 9V, 2A – but it can also charge similarly using 12V and 1.5A.

Google did, at least at one point, embrace QuickCharge 2.0. The Motorola Nexus 6 was one of the first devices to support QuickCharge 2.0.

But now there’s USB-C. And that makes things more… interesting.

USB-C And The Growing Charging Web

Intel created USB, and it wasn’t going to sit idle as PCs, phones, and tablets converged. It has its own return-fire against QuickCharge.

The world’s largest chipmaker comes from the PC universe, where laptops and 2-in-1’s routinely require dozens of watts of power. So, USB-C had to provide something more than just 15W to do everything Intel wanted from it.

USB-C by default, adopts USB 3.1’s enhanced power delivery specification. A standard USB-C cable can handle up to 5 volts, 3 amps of power, for 15W of total power delivery. This is the same as what USB 2.0 and 3.0 devices could deliver – provided the manufacturer overcharged the cable. An ASUS Transformer Book T100 for example, comes with a 5V, 3A charger… but the charger notes clearly not to use it with other devices, because it is not USB certified (it supplies too much power, as 2.1A is the USB 2.0 cap).

Alongside USB-C, there’s the all-new (optional) USB Power Delivery standard. Think of it as QuickCharge on steroids. It’s a new feature of the USB-C specification, that supports up to 100W of charging power, in a USB-C cable. The USB PD function, as it’s called, requires using the active switching cable options of the USB-C port that extends functionality to new technologies; Thunderbolt and DisplayPort Alternate Mode.

Neither of the new Nexus devices benefit from USB PD (they don’t need it), but they do embrace USB-C’s native 15W charging. The first USB PD-enabled USB-C device, is Apple’s 12-inch Retina MacBook. The laptop benefits from being able to charge, and supply power to other devices, at up to 100W from a single USB-C cable.

USB PD also supports daisy chaining. For example, you can have a MacBook plugged into the wall via a USB PD wall charger. And, that MacBook can then be plugged into a USB-C hub, that also gets power from the MacBook… and passes that power onto a Nexus 5X. The Nexus 5X, MacBook, and the USB-C hub, all pull down maximum power – up to 100W – from the a single USB-C AC adapter.

Frustration Remains

Now that you are briefed on USB-C and QuickCharge… hence the question – why don’t the Nexus 5X and 6P support QuickCharge? The Snapdragon 808 and 810 both are flagships for QuickCharge 2.0.

Qualcomm has been adamant that Google didn’t need to take this step. QuickCharge 2.0 and 3.0 both support functioning over USB-C, just as it performs over older versions. You can use a USB-A to USB-C cable, plugged into a QC adapter. This is particularly nice during the USB-C transition, because, you were supposed to be able to keep your QC 2.0 charging gear – even while picking up (or rather, upgrading to) USB-C phones and tablets.

To give another example that might further clarify, take the OnePlus 2. The OnePlus 2 uses a USB-C port and a Snapdragon 810. It supports QuickCharge 2.0 while using older chargers, when connecting a USB-A to USB-C cable. Also, it charges at 15W using standard-fare USB-C chargers too. This is how Qualcomm envisioned the transition – letting people charge at full speed using either their older QuickCharge 2.0 chargers (with a new cable) or with new USB-C pure chargers.

So, we frustratingly, can’t get a clear answer from Google as to why LG or Huawei couldn’t, or weren’t allowed to use QuickCharge standard formally in the Nexus 5X or 6P.

The most likely scenario is that Google instructed LG and Huawei to remove the authentication chip needed for QuickCharge 2.0. Unlike QuickCharge 3.0 and USB PD, QC 2.0 requires a physical chip in the device’s charging circuit – to enable the necessary hardware handshake.

It is nice to remind people that neither Intel nor Qualcomm created this situation, and they are happy to support both their optimized charging standards (QC for Qualcomm and PD for Intel), and both at least USB-C’s baseline 15W charging.

This could boil down to marketing dollars. Google may have declined to engage in the QuickCharge requirements to post advertising stickers, and also possibly pay extra certification costs to Qualcomm, to license the QuickCharge standard. Intel and the USB-IF, do not charge any fee to use USB-C Power Delivery, though cable and manufacturing costs may increase if you need 16-100W of power.

But even that isn’t enough of an explanation. Qualcomm says the standard is open and royalty-free, provided certification is met. The QuickCharge support cost should be negligible… a few cents for a charging circuit.

Unfortunately, unless Google is willing to speak more on the subject – or even better, try to work around this in baseband firmware – we may never know why Google chose to opt-out of QuickCharge 2.0. It doesn’t make sense to us.

While it is possible that Google is still supporting QuickCharge 2.0, albeit, unofficially – we won’t be able to confirm until the devices ship. It just isn’t very likely.

Who This Hurts

Ironically, those that bought Nexus 6’s last time around, are likely to be the ones worst impacted by Google’s move to not include the QuickCharge 2.0 support.

Arguably, Google may have felt that extra effort to support QuickCharge 2.0 on a marketing basis, was not needed, since USB-C provides 15W of power natively. Though this does dramatically impact consumers (like myself) who already own a series of QuickCharge 2.0 gear that predates USB-C. I already own a QuickCharge 2.0 portable charger (10,000 mAh), as well as two AC adapters, and two car adapters. Now, with Google’s move, all of those will likely throttle down to USB 2.0 (5V, 2A) speeds.

Qualcomm’s original vision was that I would simply have to buy a couple of USB-A to USB-C cables, and all my QuickCharge 2.0 gear would keep charging at 15W… even that expensive 10,000 mAh portable charger. It was a standard built to be future proof. But, that required Google to opt-in on its new devices… which it didn’t.

By blocking, or at least, not implementing QuickCharge 2.0 on the new Nexus devices, Google is forcing consumers like me to purchase all new, USB-C aware chargers. The thing is, there’s no benefit had QuickCharge 2.0 been implemented, both standards charge at 15W. This means people like me just blew upwards of $100 on QC 2.0 chargers, and now have to blow $200 on cutting-edge USB-C aware 15W portable chargers and AC/DC adapters. It’s a waste. A gigantic waste of money, time, effort, and e-waste.

One Last Time

Thankfully, while this is yet another costly technology/hardware migration, it likely will be the last one. The USB-IF has caught up with the demands of modern technology, and USB-C, USB Power Delivery, and QuickCharge 3.0, all appear to act together in harmony. With consumers focused on devices that last for very long periods, rather than consuming high-wattages of power, it’s unlikely we’ll need to buy new chargers again… for a much longer time to come.

Full Disclosure: I run an Android-enabled startup that enhances Intel technologies. I’m also a distinguished developer with Intel. Intel didn’t ask me to write this article.

You may have noticed that the Moto X Pure Edition, Nexus 5X, and Nexus 6P all lack LTE Band 12. And, they do lack the band indeed… temporarily.

Considering the Nexus 6, a year ago, broke ground on supporting Band 12, there has to be another reason for the frequency being absent from these high-end devices.

As we mentioned in our last breaking article the real reason for T-Mobile demanding compliant VoLTE stacks on all devices bearing LTE Band 12. The reason is a planned VoLTE-only roaming agreement with US Cellular (read the exclusive here), one aimed at giving T-Mobile vastly superior voice and data coverage in rural markets, virtually overnight.

The only catch being, you must have an LTE Band 12 phone, and you must have a rock-solid VoLTE implementation that can cross carriers, for all voice phone calls. Oh, and E911 too… since a significant portion of T-Mobile’s rural map will actually consist of VoLTE-only roaming on US Cellular.

Android is very close to that, but not quite. Google has been working tirelessly to satisfy each carrier’s demands in the standard AOSP stack. For example, Verizon HD Voice 1.0 (their early VoLTE stack) for Nexus 6 phones. This is different from most Android Lollipop phones, which use an alternative app entirely when facilitating such calls.

Since Android Marshmallow will improve this, and it is launching with the Nexus 5X & 6P, it was not possible to achieve T-Mobile VoLTE certification – simultaneous with building new hardware, and a new generation of Android at the same time.

The gameplan here is pretty clear. Google will ship the LG Nexus 5X & Huawei Nexus 6P with Marshmallow, and then begin the work to certify their VoLTE with T-Mobile. This will almost certainly require an Android System update, and that update will unlock Band 12 simultaneously with VoLTE.

T-Mobile has confirmed that Wi-Fi calling will automatically enable itself, once a Nexus 5X or 6P is registered on the network, and that the carrier plans to sell both devices… indicating that T-Mobile is continuing its strong relationship with Google.

On the contrary, both AT&T and Verizon have indicated they do not intend to sell the Nexus 5X and 6P. This step back comes after a tumultuous relationship on both carriers with the Nexus 6 – which took nearly six months after launch, to ship on Verizon.

Furthermore, Nexus devices have run afoul of AT&T and Verizon’s ban on bootloader unlocks, even when the devices prominently alert the user that the bootloader has been disabled. PhoneNews.com has recommended (for years) that customers on AT&T and Verizon only use Nexus (or other carrier-free) devices, to protest this move. With the Nexus 5X returning Nexus phones to the sub-$400 price range, this is a viable recommendation once again.

US Cellular has been teasing LTE roaming for ages, but they’ve been extremely quiet on who. New evidence, and sources, point to T-Mobile.

In late July, US Cellular announced that LTE roaming would initiate within “60 to 90 days” – but still wouldn’t say which carrier, at the time. US Cellular is the fifth largest carrier today, focusing on rural footprints, but has maintained a strong national coverage network via roaming agreements with Sprint and Verizon for CDMA 3G coverage.

And Sprint and Verizon jointly have benefitted from having free roaming on US Cellular – often times, if you’re wondering why your phone drops to 1x or EV-DO coverage out in rural areas, it’s because you’re actually roaming on US Cellular. So how does T-Mobile fit into all this?

T-Mobile is a GSM/UMTS carrier, so US Cellular roaming on 3G is not going to happen. There is however one thing that T-Mobile and US Cellular devices do agree on, and that’s LTE Band 12.

LTE Band 12 is what has powered T-Mobile’s resurgence in rural coverage areas. If somehow happen to have T-Mobile today, and you live in a rural market, it’s pretty essential that you get a phone that supports LTE Band 12. There aren’t many today, but that will change… to the point, we suspect, that T-Mobile will begin offering customers in rural zip codes free (or discounted) phone upgrades to Band 12 devices.

T-Mobile was rumored to be working with US Cellular, but implementation was a real concern. The two carriers are vastly different in configuration.

Moto E Was the Dead Giveaway

Awhile back, we (more than just) noted that T-Mobile was blamed by Motorola for a firmware update that revoked LTE Band 12 from the Moto E. This really isn’t legal behavior in the opinions of many – removing features from a device retroactively, after purchase, can get a company in hot water.

At the time T-Mobile (through Motorola, oddly) claimed that only T-Mobile devices can use Band 12 if they support VoLTE. We noted at the time this didn’t make a lot of sense – as there are various other scenarios that can cause LTE-only coverage, and VoLTE devices aren’t required there.

So we wondered what was so important about Band 12, that T-Mobile would require VoLTE to use it? Sources at T-Mobile have confirmed that it will be a roaming pact with US Cellular.

It also explains the LTE Band 12 redaction on Moto E. Without VoLTE on the second-gen Moto E, the phone would be constantly roaming for free on a (typically, stronger) US Cellular signal in rural markets, unable to make voice calls.

VoLTE Bridges the Platform Gap

By using LTE Band 12 for roaming, with compatible VoLTE stacks on both sides, T-Mobile and US Cellular can offer cross-carrier roaming, despite the CDMA-GSM platform divide.

This is an even bigger win for US Cellular customers. Customers with a VoLTE Band 12 phone on US Cellular, can now enjoy the coverage of nearly every network in America… save for AT&T.

A US Cellular VoLTE phone, if this deal is implemented, will be able to access US Cellular domestic coverage, free roaming on Sprint and Verizon CDMA networks, as well as voice and data on T-Mobile Band 4 and Band 12.

This is a major coup for both T-Mobile and US Cellular. It ensures T-Mobile phones will work vastly better in rural markets, and it ensures US Cellular phones will enjoy 4G LTE speeds in metropolitan markets.

This doesn’t leave Sprint and Verizon out in the cold, however. Sprint has begun adding LTE Band 12 to its devices, and Verizon has begun to see Band 12 phones trickle in as well.

The major difference there may be cost – it appears the T-Mobile/US Cellular alignment is a relatively fair trade, possibly to the point that money may not be changing hands. But, US Cellular, Sprint, and Verizon may be in a less cozy position than they once were – as a result. This could result in higher roaming rates for Sprint and Verizon to offer rural LTE coverage, for customers traveling on those networks.

However until a cross-carrier VoLTE solution is implemented in device firmware, it’s questionable if today’s Sprint and Verizon phones (aside from a select few like Google’s Nexus 6 and iPhone 6) will be able to utilize US Cellular VoLTE. For most Android devices (aside from T-Mobile and US Cellular VoLTE devices), cross-carrier roaming VoLTE will begin in the Android Marshmallow era.