We’ve already heard from Verizon, Sprint, T-Mobile and US Cellular about their own Galaxy S3, and now it’s AT&T’s turn to throw some light on one of their own. Not to be left lagging too much behind, or rather distancing itself from the bagful of announcements from all carriers to make appropriate space, AT&T has finally announcement their deal of Galaxy S3.
Unsurprisingly, the AT&T Galaxy S3 features the same 1.5GHz dual-core snapdragon processor as the other 4 carriers in US, along with the 2GB RAM. AT&T has planned to make available its Galaxy S3 on pre-order on and from June 6, and has priced it $199 for the 16GB version and that’s it – no 32GB version of Galaxy S3 here. That is of course, with a two-year contract obligation.
Some good news though, since Galaxy S3 does have expandable storage, AT&T is selling the 16GB version with a 16GB micro sdcard with an additional cost of $39. Not bad, right?
It seems that forgoing the 32GB version is just a little price of the deal which will allow AT&T to sell a Red Galaxy S3 too, along with the universal white and pebble blue (or metallic blue now) Galaxy S3.
The hardware remains same as that of international Galaxy S3, i9300, and the only change there is in the form of AT&T’s logo on the back side. It remains to be seen whether the carrier will be selling the Galaxy S3 pre-installed with its own apps or not, since Samsung has been really dictating some terms to the carriers and thus we hope for a no-bloatware Galaxy S3 from AT&T, which isn’t easy.
Other specifications of AT&T Galaxy S3 include:
- Android 4.0 Ice Cream Sandwich
- 4.8 inch Super AMOLED HD display with a resolution of 1280 x 720 pixels, around 312 PPI
- 8 MP camera at back and 2 MP camera in the front
- 8.6mm thin
- Supports AT&T’s LTE and HSPA networks
- Samsung apps and features come pre-installed, like S Voice, S Stay Smart eye tracking, S Suggest, 50 GB Dropbox storage, etc.
If you are at AT&T, does the red Galaxy S3 sounds exciting to you? Enough to sacrifice a 32GB model for its exclusivity (so far it seems)?
Discussion