, and

Samsung Logo

Samsung has halted rollout of an Android 4.3 upgrade for the Galaxy S III in light of users experiencing issues after installing the update.

According to a post on SamMobile, a spokesperson for Samsung Mobile UK made the following statement:

โ€œAs we are currently investigating the reported issues with Galaxy S3 4.3 Jelly Bean update, the upgrading service has been temporarily suspended. We are committed to providing customers with the best possible mobile experience, and will ensure to resume the upgrading service at the earliest possibility.โ€

SamMobile goes on to state that users have been experiencing the following issues:

  • Wake up lag (Sometimes it takes a few seconds to wake the device from standby and sometimes a few minutes)
  • Random Freezing
  • Huge battery drain
  • Bluetooth Audio issues during playback in car
  • Stuttering music playback with stock Samsung music app
  • Device freezes as soon a call is received (Black screen issue)
  • Poor RAM management (very difficult to multitask)
  • Wi-Fi issues

The update – identified as I9300XXUGMG9 – has been pulled from OTA and Samsung’s KIES service. No ETA has been given when for the rollout will resume, although it seems likely Samsung will need to create a new version of the update.

This only addd to the frustration of Galaxy S III owners, who’ve been stuck on Android 4.1.2 since mid-2012. Earlier this year we heard that the Galaxy S III and Galaxy Note II would bypass Android 4.2, which was the latest Android version available at the time.

The problem may not just be isolated to the Galaxy S III update, either – Android Police is also reporting that the Android 4.3 update for the Galaxy S4 has been pulled from at least one US carrier.

Have you installed Samsung’s Android 4.3 update on your Galaxy S III? Have you experienced any issues with it? Let us know in the comments.

Source: SamMobileAndroid Police.
Via: Android Authority.
10 Comments
newest
oldest
Inline Feedbacks
View all comments
Festivus Oz

A little of a side track. I bought the I9505 from Logan and have not received the update. Can anyone confirm I’d they have received it in Australia. Local or overseas stock. Not on Kies either.

Does anyone know where I can go to figure out the roll out schedule?

Andrew

Experienced all of those issues with my SIII after the 4.3 upgrade and had to go back to CM10.1. Made the phone almost unusable.

Nick

After using Galaxy I, I gave Samsung a second Chance (Thankfully skipped SGS II) and got Galaxy III and almost fell in love with the phone. SGS III was without any doubt the best smart phone of that time which was over and above all iPhones, HTCs and Nexus at that time. I could not justify upgrade to S4. I still love my SGS III very much but got tired of waiting for updates. i was planning to buy S5 but 4.3 update disaster was the tipping point. I don’t think Samsung is learning from their mistakes. Their Touchwiz getting… Read more ยป

maatsby

xda is your friend

Grumpigeek

Samsung need to get their act together. Making us wait nearly 18 months for an update from 4.1.2 is incredibly poor customer service.

Then to add insult to injury, they stuff it up.

Amos S

Huh! I only received the 4.1.2 update to my Vodafone SGS II two nights ago, it could be worse mate ๐Ÿ™‚
(Then yesterday I got my Nexus 5, which I didn’t expect until December, yay!)

phantomsofthedesert

i am experiencing these problems as well on my GT-I9300, GT-I9300T both work fine but mainly the wakeup lag is my major bug. so if this is the case what are our options if I want to use Samsung rom. I had a good copy of 4.2.2 but unable to locate it. I re downloaded it but there is and issue with modem. everything else works good. or do I download 4.1.2 ops

anonymous

Go with Omega V51 then turn off ZRAM using Trickster Mod.

Problem goes away. Otherwise get Yank555 kernel

Peter Verwey

I have experienced all of these issues with the stock 4.1.2 on my SIII, so bad that I recently did a factory reset, which has thankfully helped a bit. I am not convinced this is just a 4.3 problem.

Alex

I run CM 10.2 and have these same issues…. conspiracy!