Linked by Thom Holwerda on Tue 25th Sep 2012 21:14 UTC, submitted by bowkota
Thread beginning with comment 536511
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Androidpolice says most US carriers likely pushed a fix last week: http://www.androidpolice.com/2012/09/25/video-most-galaxy-s-iii-dev...
This is for S3, don't know about other models.
RE[3]: Comment by some1
by phoudoin on Wed 26th Sep 2012 12:35
in reply to "RE[2]: Comment by some1"
Androidpolice says most US carriers likely pushed a fix last week.
They didn't pushed a *fix*, but a full upgrade to Android 4.0.4 or sooner, which already include the fix.
I'll bet that they didn't even knew that the issue existed on the first place and that only this upgrade comes with the fix. May Jelly Bean was not ready to broadcast, I'm pretty sure no official fix will be available yet.





Member since:
2006-06-09
Indeed, the issue is most carrier-subsidized phones with custom ROM don't support them as they should, allowing such hole to be unfixed for months.
Unfortunatly, considering the price of a smartphone, many owners get a carrier-subsidized one...