Samsung’s Update Mistake—No Fix For Galaxy S25 And S24 Phones

InnovationCybersecuritySamsung’s Update Mistake—No Fix For Galaxy S25 And S24 PhonesByZak Doffman,Contributor.Forbes contributors publish independent expert analyses and insights. Zak Doffman writes about cybersecurity, surveillance and privacy.Follow AuthorApr 29, 2026, 01:48am EDT--:-- / --:--This voice experience is generated by AI. Learn more.This voice experience is generated by AI. Learn more.Is your Samsung affected?AFP via Getty ImagesIf you have a Galaxy S25 or S24 phone, you may have a serious problem. Samsung’s must recent security update has reportedly left owners of these recent flagships with a daily nightmare as batteries drain rapidly and devices start to overheat. Samsung users are not alone, with Google’s Pixel owners also reporting “severe” battery drain after the moist recent security update. Given that, one might assume this is a generic Android problem, but it seems it may not be linked.Is your Samsung affected?AFP via Getty ImagesAndroid Authority reports that most Galaxy S25 and S24 users may be affected — at least according to its own reader survey. “The exact cause of the issue is still unknown,” the website says, “but it requires immediate attention from Samsung. The company has yet to acknowledge the issue, leaving users without a fix.”It’s not yet clear what has caused these latest issues, with Meta apps flagged as one potential cause. But the other culprit could be Samsung’s own Knox Matrix platform, which provides Apple-like security across the Samsung ecosystem. This has recently been enhanced, and so could be a logical source of such issues. if (!window.cnxel) { window.cnxel = {}; window.cnxel.cmd = []; var iframe = document.createElement('iframe'); iframe.style.display = 'none'; iframe.onload = function() { var iframeDoc = iframe.contentWindow.document; var script = iframeDoc.createElement('script'); script.src = '//cd.elements.video/player.js?cid=62cec241-7d09-4462-afc2-f72f8d8ef40a'; script.setAttribute('defer', '1'); script.setAt...