

Samsung Pauses One UI 7 Rollout Worldwide (theverge.com) 9
Samsung has paused the global rollout of its One UI 7 update after a serious bug was reported that prevented some Galaxy S24 owners from unlocking their phones. The Verge reports: While the complaints seem to have specifically come from South Korean owners of Galaxy S24 series handsets, Samsung has played it safe and paused the rollout across all models worldwide. While some users will have already downloaded the update to One UI 7, using the app CheckFirm we've confirmed that the update is no longer listed on Samsung's servers as the latest firmware version across several Galaxy devices, with older patches appearing instead. Samsung hasn't confirmed the pause in the rollout, nor plans to issue a fix for users who have already downloaded the One UI 7 update. We've reached out to the company for comment.
How about ... (Score:2)
...stopping the update Galaxywide? /bad bun
Re: How about ... (Score:2)
I setup a new S24 Ultra on apr 10th (Score:2)
Fortunately, it only updated to the latest OneUI 6.1 . Dodged a bullet. But I wonder who is doing the QA at Samsung. Not being able to unlock your phone is pretty bad.
Re: (Score:2)
Is Samsung a hot company again? (Score:2)
Android app development (Score:2)
I'm doing Android development at work and have a couple of test devices that are on Samsung's upgrade list. I was looking forward to having Android 15 hardware to play with. Then Samsung went dark so I bought a cheap Brand X Android 15 tablet from Amazon. It does what I need to do.
...laura
#GSOD for all ? (Score:2)
Lots of missing information in the "article" (Score:2)
The issue appears to have been limited to a small number of Exynos based phones, so it wasn't all of them, it wasn't most of them, but there were enough to make Samsung pause the update until the scope of the problem could be identified. Now, it could be that there is an app or a type of app that is causing the problem, so yes, it's critical, but wouldn't affect those not using the app(s) that cause the problem in the first place. For those who have carrier locked versions, we already get to wait for upd