FCC clears T-Mobile's iPhone 5 for AWS bandwidths
Coming on the heels of T-Mobile's "Uncarrier" event, the U.S. Federal Communications Commission published its report of the new A1428 iPhone 5 model bound for the carrier's network, complete with Advanced Wireless Services support.
FCC test photo of T-Mobile's iPhone 5. | Source: FCC
First spotted by Engadget, the FCC report details the T-Mobile iPhone 5, including RF exposure and performance. Photos of the device are also found in the document, though the handset is cosmetically unchanged from current iterations.
It was reported earlier on Tuesday that, while still bearing the A1428 model number as the AT&T version, T-Mobile's iPhone 5 will support HSPA+ on AWS bandwidths, a feature not activated in Apple's existing handsets. The smartphone supposedly come modified straight from the factory, meaning AT&T iPhone 5 owners are unable to activate AWS capabilities with a firmware update.
However, once the phone launches on T-Mobile's network on April 12, Apple is said to be replacing the older A1428 with the new AWS-supporting model.
T-Mobile is the last of the "Big Four" U.S. wireless telecoms to become an Apple partner carrier, and will feature the handset as a flagship LTE smartphone for its new 4G network. As part of a no-subsidy pricing scheme, the 16GB iPhone 5 will be sold for a $99 up-front fee, with the remaining price spread out over 20 additional monthly payments of $20.
The iPhone 5 goes on sale on April 12 in T-Mobile's retail stores, while preorders kick off on April 5.
FCC test photo of T-Mobile's iPhone 5. | Source: FCC
First spotted by Engadget, the FCC report details the T-Mobile iPhone 5, including RF exposure and performance. Photos of the device are also found in the document, though the handset is cosmetically unchanged from current iterations.
It was reported earlier on Tuesday that, while still bearing the A1428 model number as the AT&T version, T-Mobile's iPhone 5 will support HSPA+ on AWS bandwidths, a feature not activated in Apple's existing handsets. The smartphone supposedly come modified straight from the factory, meaning AT&T iPhone 5 owners are unable to activate AWS capabilities with a firmware update.
However, once the phone launches on T-Mobile's network on April 12, Apple is said to be replacing the older A1428 with the new AWS-supporting model.
T-Mobile is the last of the "Big Four" U.S. wireless telecoms to become an Apple partner carrier, and will feature the handset as a flagship LTE smartphone for its new 4G network. As part of a no-subsidy pricing scheme, the 16GB iPhone 5 will be sold for a $99 up-front fee, with the remaining price spread out over 20 additional monthly payments of $20.
The iPhone 5 goes on sale on April 12 in T-Mobile's retail stores, while preorders kick off on April 5.
Comments
Doubtful. As the article says, these models bare the same number as the current AT&T version, only with AWS spectrum support enabled on the SoC. Otherwise it is physically and numerically identical.
Quote:
Originally Posted by Cash907
Doubtful. As the article says, these models bare the same number as the current AT&T version, only with AWS spectrum support enabled on the SoC. Otherwise it is physically and numerically identical.
I think the original poster is referring to the "Spring release of new iPhone" rumors being the grain of truth for the T-Mobile modded iPhone and all the redesign rumors added to that rumor are fiction.
I read drblank's comment the same way Cash907 did and agree with his reply.
FCC filings make it clear there are NO hardware changes at all for AWS support. This is purely a firmware trigger. That being the case, why is Apple not going to simply expose the bands on existing phones through an OS update? Sort of smells.
https://apps.fcc.gov/oetcf/eas/reports/ViewExhibitReport.cfm?mode=Exhibits&RequestTimeout=500&calledFromFrame=N&application_id=593719&fcc_id=BCG-E2599A
C2PC Cover Letter
Quote:
This is to request a Class II Permissive Change for FCC ID: BCG-E2599A originally
granted on 09/12/2012.
The change filed under this application is:
Change #1 – Adding UMTS Band IV (1700 MHz)
The addition of this UMTS band does not require any hardware changes to the approved
device. There is no increase in the output power rating on this additional UMTS band and
the Equipment Class remains the same. There are no other changes to the device.
Remember the $2.99 charge to upgrade the WiFi firmware to support 802.11n. It may simply be a similar situation here where Apple doesn't want to deal having to charge some modicum amount for the upgrade that few if none will use or the backlash from being accused of nickel-and-diming their most loyal* customers. Since there is no HW change it's possible that JB community will be able to offer a solution to add it to the other A1428 models.
* That always cracks me up.
Originally Posted by Tulkas
This is purely a firmware trigger. That being the case, why is Apple not going to simply expose the bands on existing phones through an OS update?
The smartphone supposedly come modified straight from the factory, meaning AT&T iPhone 5 owners are unable to activate AWS capabilities with a firmware update.
It sounds the same as how a manually unlocked iPhone will NEVER be the same as a factory unlocked one.
Quote:
Originally Posted by SolipsismX
Remember the $2.99 charge to upgrade the WiFi firmware to support 802.11n. It may simply be a similar situation here where Apple doesn't want to deal having to charge some modicum amount for the upgrade that few if none will use or the backlash from being accused of nickel-and-diming their most loyal* customers. Since there is no HW change it's possible that JB community will be able to offer a solution to add it to the other A1428 models.
* That always cracks me up.
Yeah, I remember that. Was driven by a specific accounting method, wasn't it? I thought they have moved away from that that required charging for new features (i.e. when they had to charge iPod owners but not iPhone owners for the same update, or something like that). If they have changed accounting practices, then they wouldn't have to charge anything to enable it on existing units.
Maybe AWS requires flashing a chipset that can only be written to once. That would make both statements true, that no hardware changed and that it can't be pushed to existing devices.