Thursday, 30 May 2019

The latest Galaxy S10 update gets pulled after causing devices to freeze

If your phone is affected, turning off Wi-Fi may help resolve some of the issues.

What you need to know

  • After many users have reported issues, update XXU1ASE5 for the Galaxy S10 models has been pulled.
  • Issues include the phone or apps freezing, an unresponsive power button, and the fingerprint sensor not responding.
  • Some report that disabling Wi-Fi can help but a factory reset does not.

Recently, Samsung released the XXU1ASE5 firmware update including the May security patches and big improvements to the camera for the Galaxy S10, S10+ and S10e. Within days, however, users began reporting issues on Reddit and XDA about several major bugs with the update. As a result, it has now been pulled.

Some users experienced third-party apps freezing, while others said the entire phone would freeze and require a restart to start working again. Other issues include the power button becoming unresponsive and the in-display fingerprint sensor not working.

The problems appear to be all over the place, with users experiencing different symptoms on every device or with different apps. According to a few posts, disabling the Wi-Fi can help resolve some of the issues, but it's not a permanent fix.

Many times after an update causes problems, resetting or wiping the device can help clear things up. Unfortunately, users are reporting that this is not the case with the latest Samsung update.

While the buggy update has been pulled, there has been no statement from Samsung on the cause of the problems or when they will be fixed. For now, users who updated early are left waiting for a patch, while users without the update can breathe a sigh of relief as they wait for the issues to be resolved.

Get More Galaxy S10

Samsung Galaxy S10

Galaxy S10 From $899 at Amazon Galaxy S10+ From $1149 at Amazon Galaxy S10e From $749 at Amazon



from Android Central - Android Forums, News, Reviews, Help and Android Wallpapers http://bit.ly/30SmDuT
via IFTTT

0 comments: