Samsung GT-i9023 hits FCC: a new version of the Nexus S with Android 2.4?
FCC filings have a curious tendency to launch us into far-reaching bouts of speculation, but hear us out — we think we're onto something here. A Samsung phone with model number GT-i9023 just passed the FCC with AWS 3G — T-Mobile's band.
Context & Ripple Effects
The Nexus S has been leaking in stages since fall 2010: PC Magazine rounded up 'Nexus Two' details in October, and Best Buy's November listing confirmed the Nexus S was real and bound for T-Mobile before launch. Now a Samsung model number nobody has seen retail-side, the GT-i9023, has cleared the FCC with AWS 3G — precisely the band T-Mobile uses.
That timing matters because T-Mobile's 4G story is moving fast: its current 4G handsets top out at 14.4 Mbps while the Samsung Vibrant Plus is slated as the carrier's first phone above 21 Mbps. Engadget's read — flagged explicitly as speculation, not fact — is that this filing points to a Nexus S revision running Android 2.4, which would be the first sign of an update to Google's flagship line.
First-order effects
- Samsung now has a T-Mobile-band Nexus S variant certified by the FCC, giving it a shelf-ready SKU whether or not Google ships a software update alongside it.
- The Android 2.4 claim remains exactly what it was in the filing chatter — a rumor attached to a certification — so Google's actual next Nexus move is still undisclosed.
Second-order effects
- If the GT-i9023 ships with updated software, T-Mobile gets a stock-Android flagship to position against its own faster Vibrant Plus lineup rather than ceding the high-speed tier to TouchWiz hardware.
- Rival carriers watching the Nexus program will note that band-specific variants are how Google's 'open' phone reaches each network — pressuring Google to certify multiple radios per generation or lose carrier shelf space.
Third-order effects
- The pattern taking shape is FCC filings doubling as the industry's unofficial product roadmap: certifications surface hardware weeks before any announcement, and every Nexus generation now forks by carrier band.
- For the Nexus program specifically, the structural tension is between Google's single-stock-device ideal and the multi-carrier reality that keeps producing variants like this one — a fork that grows harder to manage as each U.S. network demands its own radios.
The trend: Google's Nexus hardware is becoming a multi-carrier platform whose existence is revealed through FCC certifications before Google says anything, with band variants multiplying per U.S. network.