Available now on Verizon, T-Mobile, Sprint, and AT&T.
Android Oreo has been rolling out to unlocked models of the Galaxy S8 and S8+ since February 22 after Samsung fixed a bug with its initial build, but there's been no word as to when U.S. carriers would begin updating their versions of the phone. Thankfully, that's starting to change.
Verizon
Verizon recently updated its official support page for the Galaxy S8, indicating that Oreo started being pushed to the phone on March 15, 2018. The build number for the S8 is G950USQU2CRB9, whereas the one for the S8+ is G955USQU2CRB9.
Similar to what we've seen for past updates, Oreo adds picture-in-picture, the Autofill API, and much more to the S8/S8+. This changes the Samsung Experience to v9.0, and it also adds the February 2018 security patch. I'm not sure why we didn't get the more recent March patch, but I digress.
T-Mobile
Just a day after Verizon started pushing Oreo to the Galaxy S8, T-Mobile was quick to follow in its footsteps. We've received multiple tips from our readers (thanks to everyone who let us know!) that T-Mobile is now updating the S8 and S8+ to Oreo, and with it comes version 9 of the Samsung Experience and the February 2018 security patch.
Sprint
Sprint has updated the Galaxy to 8.0 Oreo, and it comes with all the same features we've seen from the Verizon and T-Mobile updates.
Along with upgrading the Samsung Experience to v9.0, Oreo also adds the February 2018 security patch to the S8.
AT&T
Finally, AT&T is the last of the big four U.S. carriers to update the Galaxy S8 to Android 8.0 Oreo.
Although it should go without saying, I'll run through what's included one last time. In addition to Oreo, this update also brings Samsung Experience v9.0 and adds — you guessed it — the February 2018 security patch.
If you've got a Galaxy S8 or S8+ on Verizon, have you gotten the Oreo update yet?
Samsung Galaxy S8 and S8+
Updated 3/20/18: Added AT&T to the list!
from Android Central - Android Forums, News, Reviews, Help and Android Wallpapers http://ift.tt/2pkhF90
via IFTTT
No comments:
Post a Comment