AT&T Samsung phones can’t make video calls after one ui 8.5 update

At a glance:

• Samsung devices on AT&T report "video declined" errors after installing One UI 8.5.
• The problem is limited to the native Phone app; Google Meet calls still work.
• Affected models include Galaxy S25, S24 series, S23 series and several A‑series phones.

What happened

Samsung has been rolling out the stable One UI 8.5 update over the past few weeks. The update has already reached flagship devices such as the Galaxy S25, the S24 series and the S23 series, as well as a range of mid‑range A‑series phones. Shortly after the rollout, users on AT&T’s network began reporting that video calls initiated from the native Phone app fail with a "video declined" error. The issue appears regardless of which party initiates the call – whether the Samsung handset dials out or receives an incoming video call.

Scope of the glitch

User reports collected by Android Authority and cited via PiunikaWeb indicate that the error is reproducible on multiple device generations. Specifically, the following models have been mentioned:

• Galaxy S25
• Galaxy S24 series (S24, S24+, S24 Ultra)
• Galaxy S23 series (S23, S23+, S23 Ultra)
• Various Galaxy A‑series phones (exact SKUs not disclosed) The bug seems confined to calls placed through the Phone app; third‑party video platforms such as Google Meet continue to function normally, suggesting the problem lies in the integration between the carrier’s IMS stack and Samsung’s native video‑calling implementation.

Why the blame game is heating up

AT&T has told affected users that the root cause is a Samsung‑side software defect, while Samsung’s support channels have pushed back, stating that the issue originates from AT&T’s network configuration. One user even claimed that One UI 8.5 removed the camera permission from the Phone app, preventing the app from accessing the front‑facing camera during a call. The same user noted that the permission cannot be manually restored, leaving the device effectively blind for native video calls.

Potential technical cause

One plausible explanation is a mismatch in the IMS (IP Multimedia Subsystem) signaling parameters after the One UI 8.5 update. Samsung’s update may have altered how the Phone app requests video streams, while AT&T’s carrier profile has not been updated to recognize the new request format. Another theory points to a regression in Android’s permission handling that inadvertently revokes camera access for system‑level apps on certain carrier‑specific builds.

What users can do now

At the moment, there is no official fix from either party. Users have tried work‑arounds such as:

1. Switching to a third‑party video‑calling app (e.g., Google Meet, Zoom) for video conversations.
2. Rolling back to the previous One UI version, if a factory image is available.
3. Contacting AT&T support to request a carrier settings refresh, though results have been mixed. Because the bug is tied to the native Phone app, these temporary measures do not restore the original video‑calling experience.

Outlook and next steps

Both Samsung and AT&T have been contacted for comment, and industry observers expect a patch to be released within the next few weeks. Historically, carrier‑specific bugs of this nature have been resolved through OTA carrier‑settings updates or a follow‑up One UI patch that restores the missing permission and aligns IMS signaling. Users should keep an eye on official Samsung release notes and AT&T’s network‑maintenance announcements for the forthcoming fix.