05-17-2013 7:38 AM
05-17-2013 11:20 AM
The tmobile firmware update has also been ported over to the att variant of the sIII.. why does THEIR software work on YOUR device that supposedly "needs to be tested"
If only I could give 100 kudos to this post! Unfortunately, AT&T has a habit of dragging their feet when it comes to Android updates. The HTC One X just got the 4.1.1 update in the beginning of March. Although AT&T apologists will state that "AT&T must test the firmware extensively...", this is clearly a case where lack of urgency is the culprit. Every major (as well as a few minor) carrier in the U.S. has rolled out the update. Obviously, it works just fine with their networks. I do not buy the "testing" excuse.
05-17-2013 11:38 AM
In the U.S as you are aware, the carriers must first test the software before they release it because they assume responsibility if something goes wrong, not the manufacturer.
Perhaps it's high time that carriers stopped meddling in the update process (read as: infesting updates with bloatware) and allowed the manufacturers to do what they should be doing in the first place? Clearly, the carriers do not control the update process for the benefit of the consumer. They control it for their own benefit only. I've been very public on this forum, as well as several others, that my Galaxy S3 is the last carrier variant phone I ever purchase. As such, I have absolutely no reason to renew my contract with AT&T. Am I going to leave? Maybe, maybe not. However, I certainly won't be tied to them. There is no excuse for dropping the ball on a flagship device.
05-17-2013 11:59 AM
Just how long are you people going to complain about AT&T's proven track record of not releasing updates in a timely manner? Fact of the matter is, you can expect similar delays with most, if not all other carriers, and even if some random update for some random device has been pushed to everyone but us, is it really any surprise? You know what the definition of insanity is, right?
You want updates straight from Google's mouth? Get a Nexus.
You want it NOW NOW NOW? Root your device and flash it yourself. Samsung was even kind enough to make ODIN available to the public.
You're tired of being tied down by a contract? There's plenty of pay-as-you-go options out there.
Crying about matters whilst doing absolutely nothing to remedy your situation should never be an option.
05-17-2013 12:40 PM
05-17-2013 5:59 PM
05-18-2013 8:24 PM
Amen to that. With my last device, I had to unlock the bootloader, root, and flash a custom rom just so I could get it updated and remove all the bull they had preloaded on it. Now, I have a Nexus 4 that runs as smooth as butter and I don't have to wonder if it is gonna be updated.
05-18-2013 11:49 PM
Let's be honest with ourselves here and just say that ALL ROMs, whether OEM or cooked, have bugs. As for major features being left our by various chefs, you can find .apks for just about anything now, including carrier specific apps, so that's not an issue either.
Sorry, but I stand by my previous point.
05-19-2013 7:18 AM
05-19-2013 1:44 PM
No, I am suggesting you take some ownership over your situation and try to remedy something yourself, since it would seem that you're not going to be getting the official response you desire anytime soon. If that is beyond you, then that's your problem, not mine.
05-21-2013 4:54 AM
05-21-2013 10:22 AM
With the public availability of ODIN from Samsung, bricking your phone is pretty much impossible.
Also, I had never mentioned anything about installing an individual .apk to "quell a bug." What I had mention was that ALL ROMs come with bugs, either cooked or OEM. The adding of an OEM .apk would be a solution to reinstalling some native app a particular chef might have left out of a particular ROM.
You really should do more research on a subject before speaking out on it.
05-21-2013 7:59 PM
05-22-2013 11:26 AM
Yes, you had mentioned that already. My last post wasnt addressed to you. I'm sorry, I should have quoted the poster I was addressing.