, and

The Samsung Galaxy S III is undoubtedly one of the more popular phone launches this year, and those that have used Telstra’s 4G network have been keenly awaiting an announcement of the 4G variant of the SGS3 to arrive.

Well, await no more. Telstra have announced this morning that the Galaxy S III 4G will be available from Telstra in October — that’s right, just over a month away. At launch, it’ll run Android 4.1 Jelly Bean, with the added excitement of 4G internet speeds and a quad-core processor. All this, in just one device.

Two colours will be available initially – Titanium Gray and Onyx Black, unlike the white and blue variants that the non-4G Galaxy S III sported at its launch a couple of months back.

When you’re in the 4G coverage area, you’ll get ridiculously good speeds if you have good reception — 20mbps is not unheard of in both directions. Where 4G isn’t available, HSPA+ Dual Channel usually is, and it’s pretty fast as well.

If you’re interested in grabbing a Samsung Galaxy S III 4G on launch, let us know in the comments, and you can register your interest with Telstra to receive up to date launch information and pricing.

Source: TelstraTelstra.
Inline Feedbacks
View all comments

Ugh! But I want it today!!


Hmmm… Telstra have announced that their 4G SGS3 will be quad-core… which probably means it will have an Exynos 4412 CPU, with a separate chip for LTE. This *may* mean battery performance will suffer compared to the dual-core Qualcomm Snapdragon MSM8960 CPU version of the SGS3, which has SoC LTE – but we won’t know for sure until someone does some performance benchmarks. Of course, I’ll probably still get one, whatever the result 😉


Have been awaiting the 4G S3 as an upgrade to my 3G S2 – enjoying using the phone as a my-fi for my Nexus 7… loving Android.

Any advice, go with a Telstra plan or simply get the phone outright at Samsung directly…


Link to register interest is broken – http://www.telstra.com.au/samsung-4g

Chris Rowland (Team Ausdroid)

Sorry about that :disqus, that’s now been fixed – typo in the post 😉