Listen to this Post
Introduction: A Promising Update Turns Into a Frustrating Surprise
Samsung’s One UI 8.5 update was expected to refine performance, improve stability, and enhance the Galaxy ecosystem experience across supported devices. Instead, a troubling issue has emerged among some AT&T users in the United States, where a core feature—video calling through the native Phone app—has reportedly stopped functioning correctly. While the problem does not appear to be widespread across all carriers or devices, it has triggered confusion among Galaxy S23, S24, S25, and select Galaxy A series users. The situation raises questions about carrier-level compatibility, firmware integration, and how deeply telecom partnerships can impact even basic smartphone functions.
the Issue: One UI 8.5 Video Calling Bug on AT&T Galaxy Devices
Samsung recently began rolling out the stable One UI 8.5 update to eligible Galaxy smartphones worldwide, with carrier partners like AT&T distributing the firmware in the United States shortly after.
Soon after installation, some AT&T Galaxy users began reporting a critical issue affecting video calls made through the default Samsung Phone app.
The problem appears to be isolated specifically to native video calling, while third-party applications such as Google Meet continue to function normally without disruption.
Affected users include owners of Galaxy S23, Galaxy S24, and Galaxy S25 series devices, as well as select Galaxy A models, suggesting the issue is not limited to a single hardware generation.
Interestingly, the bug does not appear consistent across all users, even those on the same carrier or in the same location, indicating a potentially complex underlying cause.
When attempting a video call through the Phone app, users are reportedly met with a “video declined” error message, preventing the call from connecting.
The issue occurs both when calling other Android devices and when receiving video call attempts from them.
Despite this, alternative communication platforms such as Google Meet remain unaffected, confirming that the camera and network systems are still functional.
This narrows the problem down to the native Phone app’s video calling integration within One UI 8.5.
At this stage, it remains unclear whether the root cause originates from Samsung’s firmware update or AT&T’s carrier-side configuration changes.
No similar widespread reports have been confirmed from unlocked Galaxy devices or users on other carriers, which further complicates diagnosis.
Samsung and AT&T have not yet issued an official explanation, leaving users waiting for clarification and a potential fix.
The inconsistency of the issue suggests it may involve server-side provisioning, regional carrier settings, or a software handshake failure introduced in the latest update.
For now, affected users are advised to rely on third-party apps until a resolution is deployed.
What Undercode Say:
Carrier-Controlled Ecosystems Are Becoming a Hidden Weak Point
Modern smartphones are no longer purely software-hardware devices; they are deeply integrated with carrier infrastructures. The AT&T-specific nature of this bug highlights how carrier customization layers can introduce instability after major updates. Even if Samsung’s core firmware is stable, carrier modifications can silently break essential features like native video calling.
One UI 8.5 May Have Altered Video Call Protocol Handling
The timing of the issue strongly suggests that One UI 8.5 introduced changes in how video call signaling or authentication is processed within the Phone app. If even small protocol mismatches occur between Samsung’s updated system and AT&T’s network configuration, the result can be complete feature failure despite normal device operation elsewhere.
Inconsistency Across Users Suggests Server-Side or Provisioning Errors
The fact that some users in the same environment experience the bug while others do not points toward backend provisioning inconsistencies rather than a universal software defect. Carrier feature flags, regional network settings, or account-level configurations could be triggering the “video declined” response unpredictably.
Third-Party Apps Working Fine Narrows the Root Cause
Since apps like Google Meet function normally, the issue is unlikely to be hardware-related or a general camera/system failure. Instead, it isolates the problem to Samsung’s native communication stack, which relies more heavily on carrier integration than independent applications do.
Potential Misalignment Between Samsung and AT&T Update Rollouts
Firmware updates and carrier configurations often roll out on slightly different timelines. A mismatch between Samsung’s One UI 8.5 deployment and AT&T’s backend readiness could easily produce feature-level breakdowns like this, especially for services embedded directly into the Phone app.
User Trust Risk for Native Communication Features
When basic features like video calling fail after an update, users tend to shift toward third-party platforms permanently. This incident could accelerate a gradual erosion of trust in native Samsung communication tools if not resolved quickly and transparently.
Lack of Immediate Transparency Worsens Perception
The absence of an official statement from either Samsung or AT&T increases uncertainty. In modern software ecosystems, delays in communication often amplify user frustration more than the issue itself, especially when essential features are affected.
Broader Implications for Future One UI Carrier Partnerships
If carrier-specific bugs continue to appear with major One UI releases, Samsung may need to reconsider how deeply carrier customizations are integrated into core communication features. A more modular approach could reduce dependency risks in future updates.
Fact Checker Results 🔍
✔ Verified Update Rollout
Samsung has begun rolling out One UI 8.5 to eligible Galaxy devices, including carrier distribution in the U.S.
✔ Confirmed Issue Scope
Reports indicate AT&T users across multiple Galaxy models are experiencing video calling failures in the Phone app.
✔ Unconfirmed Root Cause
No official confirmation yet from Samsung or AT&T regarding whether the issue originates from firmware or carrier configuration.
Prediction 📊
The issue is likely to be resolved through a carrier-side patch or a minor One UI hotfix rather than a full system overhaul.
Samsung and AT&T will probably coordinate a rapid compatibility update once internal testing confirms the root cause.
If the problem is indeed provisioning-related, fixes may roll out gradually over the next update cycle rather than instantly.
🕵️📝Let’s dive deep and fact‑check.
References:
Reported By: www.sammobile.com
Extra Source Hub (Possible Sources for article):
https://www.pinterest.com
Wikipedia
OpenAi & Undercode AI
Image Source:
Unsplash
Undercode AI DI v2
Bing
🔐JOIN OUR CYBER WORLD [ CVE News • HackMonitor • UndercodeNews ]
📢 Follow UndercodeNews & Stay Tuned:
𝕏 formerly Twitter 🐦 | @ Threads | 🔗 Linkedin | 🦋BlueSky | 🐘Mastodon
