South Korean mobile phone maker Samsung is gearing up for the release of Android 4.2.1 Jelly Bean for its Galaxy S III smartphone, and has already started to test the update, it seems.
The company has sent the new firmware to testers out there, and one of them has already brought it online, for more users to enjoy it.
Featuring version number I9300XXUFMB3, the new software is still a testing flavor, which means that those who are considering installing it on their smartphones might bump into various issues with it.
Furthermore, the guys over at SamMobile, who grabbed the necessary dumped files from XDA-Developers, note that the repackaged ROM should not be installed via Kies, and that installing it will also increase the binary counter on devices.
Furthermore, it will also change the status of the handset to “modified.” The firmware comes without a modem, so users will continue to use the existing one.
The news site also notes that this Android 4.2.1 JOP40D pre-release firmware appears to be running very well on the Galaxy S III.
Some of the main changes that the firmware arrives on devices with will include:
- Improved Ripple effect on Lockscreen
- New Android 4.2.1 Lockscreen with widgets
- Daydream (Settings>Display)
- New Additions in Notification Center
- Notifications are more actionable
- Voice Command (Let’s you control various parts of the phone using voice commands)
To install the software, users will have to download the packaged file, fire up Odin (which has been included in the download), restart the handset in download mode (Press and hold Home + Power + Volume down buttons), connect it to the PC, and then flash the I9300XXUFMB3_I9300OJKFMB3_HOME.tar.md5 file (it should be added to PDA in Odin).
Provided that there are issues with the device following the installation, one should simply enter recovery and perform a wipe/factory reset (which will erase all data on the device).
Those of you interested in trying the new firmware on their Galaxy S III smartphones will do so at their own risk. You are, however, advised to wait for the official update to be pushed out (which might not happen until Galaxy S IV is made official next month).