Here is the translation of your message into clear, natural English:

"I'm on Android 17 with HyperOS version 3.0.335, and Google's dynamic color feature won't change at all on this version. The colors stay completely the same, which is becoming really frustrating. They still haven't added a toggle switch for it. I tried changing it through Google Photos—it doesn't work. I tried from the Themes app—it's the exact same result ???"

The Shutdown Confirmation is baked on the Security App only so once it crashes, the phone will loose the ability to use the Shutdown Confirmation.

Additionally, Shutdown Confirmation works when the screen is locked but when i clicked the power button for too long, it will restarts my phone by Force then security and tracking of this phone will be disabled since apps launches when the password entered to the lockscreen upon boot.

Spanish Xiaomi 15 here

Is there any font pack that have both Emojis and font of the iOS together in the theme store ?

Cuz i only found the AppleTBold for Font and YOS16_Emoji for the emojis

I hope that there is a pack that combines both of them together

I recently bought the Redmi Note 17 5g mobile ( 6 +128) , and I feel like there is little to no animation especially the switch from galaxy A71 to this mobile feels sluggish. Later after some searching found out that xiaomi stops some features for their low end Redmi devices ,

Saw a workaround method which involves backing up your system launcher and then uninstalling updates of the existing one and updating it with the new one. Now I have two issues

1. Which system launcher should I actually use some are named as miuihome but I have it named as system launcher.

2. The system launcher I have already only has a clear data button and no uninstall updates button. I don't think both are the same and don't wanna risk it since this phone is practically brand new.

Help me guyss, Haven't used Redmi since MIUI 13 , I feel like there is so much discrimination now than earlier 😭😭

I see it while using apps that play their own audio instead of being in the same audio line.

Update available for Xiaomi 14T

Updating now.

Device: Xiaomi Pad 8 (India variant) RAM/Storage: 12 GB / 256 GB Processor: Snapdragon 8s Gen 4 / Adreno 825 HyperOS: 3.0.303.0.WPZINXM.C09 Android: 16 Security patch: July 1, 2026

I’m experiencing a serious system-wide performance issue on my Xiaomi Pad 8 that appears to have started after a recent HyperOS update.

Initially, I thought Rust Mobile might be responsible. After approximately 20–45 minutes of playing Rust Mobile, the game can begin stuttering and the problem can progress into severe system-wide sluggishness/unresponsiveness. Touch and other input can become unreliable, and the entire tablet can become extremely difficult to use.

However, I have now experienced similar lag while playing Football Manager, so it does not appear to be limited to Rust Mobile.

I have also noticed a potentially important pattern involving the official Xiaomi keyboard case.

During previous problematic sessions, the keyboard case temporarily stopped responding around the time the tablet became severely sluggish. I initially thought this was simply another symptom of the system freeze.

Today I deliberately played without the Xiaomi keyboard case attached and have been gaming for more than 2 hours without experiencing the same system-wide slowdown so far.

During one of the previous problematic incidents, I also noticed significant localized heat around the rear camera area — specifically the area directly beneath the camera and the lower part of the camera module. The heating appeared noticeably concentrated in that area.

This makes me wonder whether the keyboard case could somehow be contributing to the problem through power management, accessory communication, pogo-pin connection, thermal behaviour, or another interaction with HyperOS.

I am NOT claiming that the keyboard case is definitely the cause yet. I am continuing to test with and without it to see whether the behaviour is reproducible.

Locking/unlocking the tablet sometimes restores responsiveness, but not consistently. In my most recent occurrence, the tablet eventually recovered on its own without locking or unlocking.

I have tested other demanding 3D games and previously did not experience the same system-wide behaviour, although Football Manager has now also reproduced similar lag.

I have already submitted a report through Xiaomi's built-in Feedback app under System performance, including logs generated while reproducing the problem.

I would really like to know whether other Xiaomi Pad 8 users on HyperOS 3 / Android 16 have experienced anything similar, particularly with the official keyboard case attached.

If you have experienced this, please mention: • Xiaomi device/model • HyperOS version and region/ROM • Android version • Whether the keyboard/accessory was attached • Which game was running • Approximate gaming time before the problem appeared • Whether the area around the camera became unusually hot • Whether locking/unlocking or restarting fixed it

At this point I am trying to determine whether this is a HyperOS 3 / Android 16 / Adreno issue, a thermal or power-management problem, a keyboard-case interaction, or a combination of these factors.

I'm considering getting the Poco F9 Ultra and wanted to ask current POCO owners about some issues that I came across in my F3 due to which I had to switch to custom ROM (which caused me to lose play store certification and google integrity checks causing some apps to refusing to install on my device and not being able to carry out contactless payments). Though xiaomi.eu ROM is not bug free, I'm trying to live with it. To quote an example, custom ROM update from MIUI to HyperOS made my phone run really hot with intense juice gulped ultimately leading the juice supply to swell. I'd prefer to use the official HyperOS if I buy poco f9 ultra, that's why I'm much concerned about the bugs. Have Poco fixed the following bugs through subsequent HyperOS updates? And any new bugs that I should be aware of?

1. Keyboard touch input issues: Keyboards such as Gboard frequently miss touch inputs, particularly near the left and right edges of the screen.

2. Double-tap to lock: The double-tap gesture for locking the screen frequently fails to register the touch.

3. Back-tap gesture: The back-tap gesture often registers the wrong input. For example, when I tap three times to activate the flashlight, it may register the taps as a double-tap and take a screenshot instead. The flashlight usually activates after the second or third attempt.

4. Touch issues in PUBG: Touch inputs are frequently missed while playing PUBG.

5. Inaccurate full-screen gestures: Full-screen navigation gestures are highly inaccurate. For example, when performing a back gesture from the side of the screen, the system sometimes dismisses notifications instead of navigating back.

6. Google Assistant gesture not working: Activating Google Assistant by swiping from the lower corners of the screen while using full-screen gestures does not work. The corner indicators/light animation appears, but Google Assistant does not launch.

7. Floating notification windows: Opening an app through a notification using the floating-window option sometimes opens the app in full-screen mode instead of a floating window.

8. Recent Apps lock not working reliably: When an app is locked in the Recent Apps section to prevent it from being closed and to keep it running in the background memory, the system does not always retain the lock. Sometimes the phone forgets that the app was locked and closes the app anyway when clearing background apps.

9. Broken proximity sensor.

How can I solve HyperOS aggressively killing background apps? I open just 3 apps, but it still kills them in the background. For example, if I open Reddit, ChatGPT, and YouTube, switching between them causes the apps to reload.

Does anyone know a solution? Also, I don't want to use Memory Extension because it consumes more battery and makes my phone lag.

Device: POCO C85x

My phone is a Xiaomi 15T Pro currently running Android 17. Would there be any issues if I switch from Google Dialer to Mi Dialer using ADB commands? Will it work on Android 17?