So, no surprise here then - Samsung is aiming, apparently, to push the Android 4.1 Jelly Bean update out to Samsung Galaxy S III owners very soon - with August or September mooted, according to Sammobile.
It's great news considering the Galaxy S III is doing so well in the sales stakes - reports out at the weekend claimed that the flagship Samsung handset has passed 10m sales since launch two months ago.
And there'll be lots of eager beaver S III owners (the ones not brave enough to root and install custom FW) who are waiting for this to hit, and until now have only had the vague prediction of a Q4 rollout to go on.
What's more, the slightly older - but still, frankly, very competent - Galaxy S II also looks in line for the update. Although this could take a little longer, the site reckons testing with the new Android update has proven successful in early stages.
I will be awaiting the update with real anticipation. Probably more so than many others. Here's why. Regular Mobotniks will know I wrote an article recently about my disappointment with the Galaxy S III which I'd patiently queued up for on launch day. Its implementation of the MTP Protocol made it completely incompatible with what I needed to do in terms of syncing music and the phone ended up on AV Forums.
Well, since then, a workaround was found and I excitedly threw the iPhone on AV Forums too, going back to an S III which I am now totally in love with. I've been syncing music left right and centre for weeks and loving every second. Big thanks to iSyncr, by the way, who found that workaround!
Until last week.
Kies told me there was an update for the S III, so I hurriedly downloaded and installed it. Battery life is improved, yes. But what it gives with one hand, Samsung takes away with the other.
It has now completely frozen out any form of connection with a Mac via cable other than Kies. Which means even the Android File Transfer app which many used as a workaround doesn't work. Quite simply, the only thing your Galaxy S III will now do when connected to a Mac is charge.
Samsung are aware of the issue - but let's face it: Mac users are hardly a priority. We only account for about 0.00001% of users. Hardly worth rushing an update out for.
But at least, hopefully, in Jelly Bean, they may rectify it once and for all. Here's to crossing fingers. And hoping they don't remove some other key functionality.
your below me wuahahahahaha 
