قالب وردپرس درنا توس
Home / Technology / Oreo seems to cause problems for Samsung Galaxy A3 (2017)

Oreo seems to cause problems for Samsung Galaxy A3 (2017)



After updating the handset to Android 8.0 Oreo, new reports of potential problems with the 2017 Samsung Galaxy A3 issue have come to light. This is based on comments from the Samsung Community Forum, with users of the budget-friendly device pointing to issues ranging from bootloops to freezing the operating system. In fact, some users describe their newly upgraded smartphones as "unusable" because of these issues and problems with battery usage. These are obviously problems for those who use the device daily, but the underlying cause is much more difficult to determine. In some cases, the problem arises when users try to connect to a Wi-Fi network and reportedly only in certain networks in Europe – namely Eduroam Wi-Fi networks. Other users report frequent app crashes and a maximum battery life of just a few hours.

Perhaps it's even worse that a complete device reset, including a factory reset, does not seem to mitigate any of the seemingly negative effects coming from the firmware update. So it's quite possible that the company will eventually stop the rollout while identifying and fixing the bugs that cause problems. In the meantime, the issues do not seem to be too different from previous problems that Samsung and some other companies had with their Oreo updates. Android 8.0 has changed quite a few Android optimizations in terms of operating system management and battery power. These changes have been made by OEMs trying to get updates quickly because most Android manufacturers use their own software on the operating system and need further tweaks and changes.

Samsung still has to answer officially, but the moderators ask for more details from someone who has problems after the update. Given this, it's a good idea for users who have not yet received and installed the update to stick to it. As mentioned above, Samsung was relatively quick to stop updates and check the firmware for errors. Once these have been sorted out, the new firmware should be issued in a short time.


Source link