The transition to the latest Xiaomi HyperOS 3 has brought a wave of next-gen features, but for users in Türkiye, it has also introduced a critical communication hurdle. A significant number of users report that their devices are failing to play any ringtone during incoming calls, leading to missed connections and professional disruptions. Xiaomi’s software team has officially acknowledged the issue and is currently investigating the technical breakdown.
The Breakdown: Audio Logic Failures in OS3.0.5.0
The “Silent Call” bug is specifically tied to the Global Stable build OS3.0.5.0.WNFMIXM, which is based on the new Android 16 architecture. Technically, the issue appears to be a regression in the system’s Audio Focus management. When an incoming call signal is received through the Xiaomi HyperConnect framework, the system fails to trigger the ringtone audio channel, effectively keeping the device in a “phantom silent” mode even when the volume is set to maximum.
While the exact technical trigger is still under investigation by engineers, early analysis suggests a conflict between the regional carrier settings in Türkiye and the new notification priority logic introduced in this version. Unlike previous minor glitches, this bug persists across all sound profiles, including “Regular” and “Vibrate” modes.
Affected Devices and Software Versions
This issue is currently localized to a specific firmware branch and hardware set:
-
Primary Devices:
-
Redmi Note 13 Pro (Global Model)
-
POCO M6 Pro (Global Model)
-
-
Affected Version: OS3.0.5.0.WNFMIXM
-
Operating System: Xiaomi HyperOS 3 (Android 16)
-
Region: Primarily reported by users in the Turkish market.
Current Status and Market Impact
As of March 21, 2026, Xiaomi has labeled this a “High Priority” issue. Because this bug affects a core telecommunications function, it has impacted the reliability of these mid-range powerhouses in a key market.
Currently, there is no temporary workaround (such as clearing app data or resetting sound settings) that consistently resolves the issue. Users are advised against factory resetting their devices, as the bug is baked into the system partition of this specific build and will likely persist until a new OTA (Over-the-Air) patch is deployed.
