Samsung Galaxy S III and Galaxy Note II Getting Android 4.2.2 in May/June? David Pena 6 April, 2013 8 Comments Android 4.2.2 might be heading to users with a Galaxy S III, and a Galaxy Note II. There is now real hard evidence of this, but recently SamMobile tweeted out that this might be happening in either May or June. No official confirmation from Samsung. Yes, there is a chance they might be wrong, but since the Galaxy S4 is coming out shortly, we all know Samsung promised to update the GS3 and Note II to get it up to where the S4 is in OS versions. SamMobile is pretty good at getting solid Samsung information too, so I guess we will see what happens in the coming months. Let us know what you guys think. Source: Android Headlines Gasopin I’m anxiously expecting this update for the GS3, but Samsung may run the same trick it did with the Vibrant and the original Galaxy Tab. Once a new model is coming out, they delay the previous model’s updates for months, and may even ‘retire’ that older model. I’m hoping David is right and the updates are released soon! rizoh66 I agree… However, I do believe that Samsung had realized their past mistakes and now follow through on their promises. I was one of those Vibrant casualties, but have since re-converted after they’ve stepped things up. I would say that this is one of the reasons behind their recent success. Jay why did Samsung Galaxy Nexus get Jelly Bean updated to 4.2.2 and a newer phone, Samsung Galaxy 3 is still at 4.1.2? http://www.androidspin.com Stormy Beach Because the Nexus is a stock Android experience device. The new versions of Android are build plain vanilla. Many people prefer this over the custom UI’s that manufacturers put into place. Like the Samsung Nature UX, TouchWix ect. It has been a plague for Android users everywhere who want the latest and greatest update. Samsung has to take the new software and code in their software to the code. then they have to test it until they solve issues and bugs. Once that is completed, the updated software is shipped off to the various carriers. Where they have to add in their bloatware, you know, the apps the carriers want to have on all of their devices. Then they test it and search for issues. If it doesn’t meet their testing and is not working correctly, they keep working to fix it. I believe it goes back to the manufacturer for final testing and approval. It is a back and forth game that keeps updates to carrier branded and custom UI style devices from getting quicker updates.