Honestly samsung promised updates for the S3 so many times and they never came, yes we got a leaked copy of 4.2.2 which didn't have half of the stuff it was suppose to and was never made OTA official.
Then we get a 4.3 leaked update, which then were told the leak is the offical update, and guess what it doesnt work and half the apps promised were not there.
Ive upgrade to 4.3 (rooted) and burned through roms trying to find one that actually works properly hoping some developer had worked out samsungs mistake and patched it... sadly its not the case, so rather than downgrading back to 4.1.2 and sorting the head ache of an effs modem downgrade/restore out, im holding out hope samsung will actually pull their finger out and give us a 4.3 that works seeing as this was actually released to carriers and it started to get pushed out.
Honestly worst case they give us a stable 4.3 without all the extras from the s4 we were promised and i would be happy, but a little disappointing. If they give us the apps great, if they give us 4.4 even better, but this has to happen ASAP ie in the next week.
If they tell us they dont have the time to make 4.3 work and instead are going to release 4.4 in the first q next year im going to stop buying anymore samsung phones, recommending them to people and do everything i can to watch them burn....
Considering the S3 has the largest user base, how samsung has time and time again failed to give us updates to now finally slap is in the face with a half finished update that everyone who has flashed it have a problem that i can see is terrible.
I moved to samsung after htc stopped making phones that i wanted and instead tried to make android ishineys...
Im hoping the delay means they have decided 4.4 is a smart move and will instead bring the update release forward and forgo the awful 4.3 update, where as sadly a large part of me suspects the reason its taking so long to fix is they only have one developer working on the fix.
Pay attention samsung, your about to a very large percentage of your android userbase, make a proper statement and issue a fix... sooner rather than later..!
Sorry ran over.