The Samsung Galaxy S3 has been with us for a while now and has sold millions of units around the world, and over the last couple of months the handset has been the centre of attention with regards to the latest Android update for the device. Samsung first pushed the Android Jelly Bean update out at the end of September with it first hitting the UK in the following month, but there is still no sign of the Android Jelly Bean update for the Orange or T-Mobile Samsung Galaxy S3, which remains a mystery to why there has been no sight of it yet.
In the UK the likes of Three and O2 were among the first carriers to get the Jelly Bean update out to its customers, which was then followed by unlocked versions of the smartphone to start receiving the updated operating system. Fast forward to now around two months later and owners of the device on Orange and T-Mobile still have no official news from the carrier about the availability of the new firmware.
Looking on various support forums there are many frustrated customers with many contacting their carrier asking for information on when the Jelly Bean update will be released. Some have been told by T-Mobile that it would arrive by early December, but obviously this has come and gone, and on contacting the company again were told they have no idea when the new software will arrive.
Customers of the two carriers that are now part of the EE Company will be wondering when they will ever see the update, and this is at a time when customers of US carrier Verizon can expect to see Android Jelly Bean in the next couple of days.
Samsung has recently begun rolling out another Jelly Bean update in the form of 4.1.2 to unlocked versions of the handset, and it was previously expected that Android 4.2 would hit the Samsung Galaxy S3 early next year.
We have heard of some customers of Orange that have received the update already but these claims can’t be confirmed, and there are many more that are saying they have yet to see any update. Some users are wondering if the delay may have something to do with the merger of T-Mobile and Orange to form EE, and many angry customers have said that they will be leaving the carrier once their contract is finished.Some have decided to use a custom ROM to get hold of the Jelly Bean firmware, but this should only be done if you are confident in such things, and this can invalidate your warranty for the handset.
Samsung Galaxy S3 Jelly Bean rollout for T-Mobile USA.
It seems strange to some of you that the Samsung Galaxy S3 has yet to see the Jelly Bean update rollout in North America. However, we’re happy to report that T-Mobile are now pushing the update, so you’re advised to check now via your Samsung Kies software to see if you have it yet. While this is great news for those with the Galaxy S III on T-Mobile USA, it’s a little disappointing for those on other carriers such as AT&T, as they still have to play the waiting game.
While it’s easy to put the blame on the likes of Samsung to get Jelly Bean later than other devices, more often than not it’s down to the carriers in the US, which is the case this time. What we do find strange is that T-Mobile USA did not even make an announcement that they would be making the Android 4.1 Jelly Bean available, instead it just appeared – but who’s complaining? Although it’s now showing on their support page.
What has surprised us the most though is when Samsung suggested that Jelly Bean would not be made available for the Galaxy S3 until 2013, which did seem a little strange when you consider that these handsets has seen the update some time ago in other countries; although we did explain the reason for this above.
The Galaxy S3 receiving Android 4.1.1 Jelly Bean is good in one respect and negative in another because while this is a new version for the handset, it’s not the latest version of Android as 4.2 is. We reported a few days ago that AT&T should also be getting 4.1.1 JB for the Galaxy S3 any day now, so maybe it will appear out of the blue just like T-Mobile.
Speaking of Jelly Bean it looks as though the Motorola Xoom and the Nexus S will not be receiving update 4.2 and will have to stick with 4.1.2. Does seem strange that such old devices received JB long before the newer Galaxy S3, and we all know that these older devices have been struggling to run Jelly Bean.
0 comments:
Post a Comment