Reasons why Samsung phones slow down after upgrading the operating system

 

Google’s latest Play System update causes some Galaxy phones to slow down. But luckily the solution is very simple.

Google released the May 2024 Play System update for Android smartphones at the end of April. Besides the usual stability improvements, the update also introduced Cross-Device Services, which helps with video calling on Google. Meet between devices seamlessly.

The company also introduced the ability to share passwords with family members in Google Password Manager.

However, the May 2024 Play System update caused unintended consequences on some Samsung Galaxy devices, causing them to run slowly and take a long time to launch applications.

This issue affects the Galaxy S23 and some other Galaxy phones. Samsung acknowledged the problem on the user support forum and suggested a simple workaround while the team tries to fix the problem.

Company staff said that some users will find their Samsung Galaxy smartphone running slowly if used for a long time, especially after installing the latest Google Play System update. You can restart your phone to temporarily resolve the issue until a fix is ​​released.

According to Android Police, installing the Google Play System update forces users to reboot their Android phones. In this case, Samsung advises them to restart after a few hours if they feel the smartphone is running slowly and taking a long time to open applications.

If you haven’t installed it yet, you can temporarily not download the May 2024 Play System update on your Galaxy series phone to avoid unexpected issues.

In fact, this is the second problem Samsung users have encountered in less than a week. Previously, many people continuously complained when the Messages application crashed earlier this week, caused by a Google Meet update.

Previously, at the end of March, the One UI 6.1 update caused touch screen problems on the Galaxy S23 series. Many people believe that Samsung’s new firmware is the culprit. However, the real cause turned out to be an error in the Google Discover feed, and Google eventually had to update it with a fix.