Samsung Galaxy Note 2 Android 4.3 Jelly Bean update release still faces setbacks even after weeks it first began rolling out to the American carriers. In October 2013, Samsung announced its plan to roll out Android 4.3 Jelly Bean updates to the Samsung Galaxy S3, Galaxy S4 and Galaxy Note 2.
It was expected that the company began with the Galaxy S4 before moving to the Galaxy Note 2 and the Galaxy S3. By December 2013, U.S carriers had finished all Android 4.3 updates and their features to three of these devices. However, while everything is now settled in the U.S., there are updates that still face setbacks in some parts of the world.
Australian carrier Telstra has been the only carrier in the world that is very communicative with its customers. Telstra, which finally rolled out the Galaxy S4 Android 4.3 Jelly Bean update earlier this week, still has to roll out the Galaxy S3 Android 4.3 Jelly Bean update. Like French carrier SFR, Telstra has been dealing with Galaxy Note 2 Android 4.3 update issues.
The Galaxy Note 2 Android 4.3 update was supposed to arrive in November 2013 but Samsung's update submission was delayed for some unknown reasons. Telstra said it's targeting Dec. 23, 2013 and after complaints from its customers, particularly those with Galaxy Gear, Telstra finally announced its new update schedule and unfortunately, it's not good news.
Telstra didn't give a specific date and instead tagged a "To Be Confirmed" (TBC) label to its Galaxy Note 2 Android 4.3 update release date. It's basically up in the air right now. This is a setback that Telstra customers probably did not envision when their carrier announced Dec. 23 target release.
Although customers welcome it, this is one of the dangers of giving specific release dates beforehand. Customer expectations are set and if expectations are not met, it leads to disappointment. That's exactly what we see from Telstra customers.
Telstra is not alone. Several carriers have yet to roll out Android 4.3, including SFR, which announced that it developed problems during testing.
To contact the editor, e-mail: