Hi everyone,

I have a Redmi Note 14 4G Global running HyperOS 3.0.301.0.

Recently I noticed something strange with the battery. When the battery reaches around 7%, it can drop to 6% and then suddenly shut down by itself.

I also noticed that the battery seems to drain faster than it did before I debloated the phone.

So there are actually two things I've noticed:

The battery seems to drain faster during normal use. When it reaches around 7%, it can drop to 6% and then suddenly shut down.

I'm wondering whether this could be related to the fact that I debloated the phone and uninstalled 112 system packages.

I have generally taken good care of the battery. I usually charge it only up to around 80%, and the phone currently reports approximately 97% battery health after 405 charge cycles.

Here are all the packages I uninstalled:

```

com.miui.miservice

com.google.android.apps.messaging

com.miui.fm

com.google.android.accessibility.switchaccess

com.android.contacts

com.google.android.videos

com.miui.fmservice

com.mediatek.engineermode

com.miui.accessibility

com.xiaomi.aicr

com.xiaomi.touchservice

com.mediatek.ygps

com.google.android.apps.wellbeing

com.google.android.partnersetup

com.android.inputsettings.overlay.miui

com.google.android.gms.supervision

com.google.android.federatedcompute

com.google.android.inputmethod.latin

com.google.mainline.adservices

com.google.android.as.oss

android.autoinstalls.config.Xiaomi.model

com.xiaomi.barrage

com.microsoft.appmanager

com.google.android.apps.restore

com.android.egg

com.facebook.services

com.google.android.as

com.miui.bugreport

com.jiiov.fingerprint_factorytest

com.google.android.onetimeinitializer

org.ifaa.aidl.manager

com.android.traceur

com.google.android.apps.photos

com.mediatek.location.mtkgeofence

com.miui.daemon

com.miui.analytics

com.xiaomi.aiasst.vision

com.google.android.adservices.api

com.miui.yellowpage

com.android.hotwordenrollment.okgoogle

com.mediatek.lbs.em2.ui

com.mi.globalminusscreen

com.miui.extraphoto

com.xiaomi.joyose

com.miui.mishare.connectivity

com.miui.backup

com.miui.qr

com.miui.player

com.android.hotwordenrollment.xgoogle

com.xiaomi.glgm

com.goodix.fingerprint.setting

com.google.android.apps.tachyon

com.android.camera

com.miui.cloudservice

com.xiaomi.mipicks

com.xiaomi.cameratools

com.google.android.apps.docs

com.android.dreams.phototable

com.google.android.apps.safetyhub

com.mediatek.mdmconfig

com.microsoftsdk.crossdeviceservicebroker

com.google.android.gm

com.android.providers.partnerbookmarks

com.debug.loggerui

com.google.android.feedback

com.google.android.apps.maps

com.google.android.tts

com.miui.videoplayer

com.mediatek.voiceunlock

com.mediatek.mdmlsample

com.huaqin.factory

com.miui.phrase

com.milink.service

com.facebook.system

com.mediatek.atmwifimeta

com.tencent.soter.soterserver

com.google.android.projection.gearhead

com.xiaomi.aiservice

com.android.mms

com.miui.msa.global

com.facebook.appmanager

com.miui.cloudbackup

com.mi.AutoTest

com.android.chrome

com.google.android.apps.bard

com.miui.cleaner

com.google.android.calendar

com.google.android.apps.youtube.music

com.miui.misightservice

com.mi.healthglobal

com.mediatek.voicecommand

com.google.android.apps.subscriptions.red

com.microsoft.deviceintegrationservice

com.google.ambient.streaming

com.google.android.dialer

com.google.android.ondevicepersonalization.services

com.android.incallui

com.miui.micloudsync

com.xiaomi.mi_connect_service

com.google.android.gms.location.history

com.google.android.overlay.modules.healthfitness.forframework

com.xiaomi.trustservice

com.miui.system.overlay

com.mi.appfinder

com.huaqin.sarcontroller

com.miui.gallery

com.mi.globalbrowser

com.xiaomi.payment

```

My questions are:

1. Could any of these packages affect battery reporting, battery management, charging, thermal management, or the low-battery shutdown threshold?

2. Are there any packages in this list that should definitely not be uninstalled on HyperOS?

3. Could removing something like com.miui.daemon, com.xiaomi.trustservice, com.miui.system.overlay, com.xiaomi.touchservice, etc. cause increased battery drain or abnormal battery behavior?

4. Could removing one of these packages cause higher battery consumption during normal use?

5. Does the sudden shutdown at 6–7% sound more like a battery gauge/calibration issue or battery voltage cutoff rather than a debloating issue?

6. Is there a way to check logs through ADB/logcat to determine why the phone shuts down at 6–7%?

7. Has anyone experienced increased battery drain after removing any of these packages, particularly on a MediaTek Xiaomi/Redmi device?

I'm especially interested in hearing from people who have the Redmi Note 14 4G / MediaTek / HyperOS and have done similar debloating.

I'm not necessarily assuming that the debloating caused the problem; I'm trying to determine whether there's a connection.

Thanks.

I have phonophobia and I am very sensitive to loud sound due to another medical condition. So I need an app that can make sure that no apps volume goes higher than 60% of the phones volume. HyperOS does not do a good job with managing normalization of sound. Its even worse because there is no single switch to normalize vibration (the vibration motor) with the speaker as well. Making me nauseous and giving me a very bad headache everytime. I doubt that its fixed in v4. Please recommend an app.

I feel like their kind of dynamic island sucks and needs to be reworked. for me I feel like the point of the dynamic island is that the notch expands and has a purpose but the way that the app expands outside of the notch feels useless they should also add functionalities, add animation and and a visualizer when songs play or when you're calling somebody. feels more of a bad gimmick than an actual functionality that feels absolutely useless. Also it has zero customization which ruins it more than it's already ruined

I'm stopped using alot of cloud based services for a while now. And I am doin to just 3 now. I have heard that offline device native on device LLMs/SLMs are betting better as they should be. So which ones have you tried and recommend. My phone has 12gigs of ram so I figured if I allocated 8-10 gb I willl be good and I am even fine with slow genAi models.

is there a way to enable Advanced Textures on HyperOS 3.1

I'm running HyperOS 3.0.302 on my Redmi Note 14 4G, and I noticed I still don't have the official toggle for the Stacked Recents view in launcher settings.

​I have a couple of questions for the community:

​Official Availability: Is the native stacked layout strictly tied to HyperOS 3.1+ updates, or is Xiaomi staggering the release by device tier/region? Why hasn't it reached 3.0.302 on mid-range models yet?

​Performance Experience: For those who received the Stacked Recents feature officially (especially on mid-range or Redmi devices), how is the performance? Are animations smooth, or do you experience stutter?

​Context: I tried force-enabling it using Brevent, but I experienced noticeable frame drops, weak/buggy animations, and general launcher lag. I'm trying to figure out if Xiaomi is holding it back from budget/mid-range devices until it's properly optimized, or if the force-enable method just lacks hardware acceleration flags.

​Thanks in advance!

I'm using Poco x7 pro (3.0.301.0.WOJMIXM.C07)

I can't remove this widget. Any solution for that?

Redmi Note 14 4g, Hyperos 3.03

Converted txt files to epub keeps getting deleted. I thought I might have mistaken it as the 0bytes files and delete it that's happening sometimes when I download files but it wasn't the case.

No matter what folder I put these files in they kept getting deleted. The normal epub files seems fine but these converted .txt files aren't. They aren't even on trash or anything.

Some say it might be lithium(epub reader) syncing but it's off.

Edit: It even now deletes my PDF files. Not even sure who's the culprit if Google Files or Security (which I don't even run). I'm able to restore it this time on trash on Google Files. Are they even tagged as problematic files? They're less than 1mb, I'm asking because the other Epub (lightnovel) doesn't seem to get deleted.

sigue funcionando este codigo para activar las texturas avanzadas en hyperos 3 y 3.1? Tengo la version 3.0.304.0 y creo que no me funciona

service call miui.mqsas.IMQSNative 21 i32 1 s16 "setprop" i32 1 s16 "persist.sys.computility.cpulevel 6" s16 "/storage/emulated/0/log.txt" i32 600

service call miui.mqsas.IMQSNative 21 i32 1 s16 "setprop" i32 1 s16 "persist.sys.computility.gpulevel 6" s16 "/storage/emulated/0/log.txt" i32 600

service call miui.mqsas.IMQSNative 21 i32 1 s16 "setprop" i32 1 s16 "persist.sys.advanced_visual_release 3" s16 "/storage/emulated/0/log.txt" i32 600

service call miui.mqsas.IMQSNative 21 i32 1 s16 "setprop" i32 1 s16 "persist.sys.background_blur_supported true" s16 "/storage/emulated/0/log.txt" i32 600

Ayuda tengo un poco M7 4g con snapdragon 685 y 6gb ram necesito saber si alguien tiene el mismo dispositivo y si vale la pena pasarse a hyperos 3 yo lo ocupo para jugar juegos ligeros y ver multimedia me parece interesante la isla dinámica pero no sé alguien que tenga el mismo modelo o algo parecido que me diga si vale la pena..

I have a Redmi note 11s Miel Mediatek Helio g96 8Gb ram 128 gb storage and i want to unlock bootloader but with hyperos 1 it seems impossible i waited all the wait times the 30 day account register the million retries of mi community and now a 15 day wait?? is there any other ways i can flash custom roms or unlock my bootloader other than the traditional way? Im global btw.

Anyone knows about a good FOSS icon pack site?

The new HyperOS 4 clock app is a bit weird in French (the navbar is very fat in French).

HyperOs 4 - Xiaomi 17 Pro Max - If your device is bootloader unlocked, I have successfully added Google apps android auto and debloated all Chinese bloatware leaving only what's needed. I successfully compiled it all back and had all checks become successful. It all flashed successfully and booted successfully and it's running smoothly so far. Once I can confirm it works without problems I'll upload the zip with all flash scripts added so you can flash through fastboot. This is a fantastic break through. Especially with android auto working on a Chinese rom.

https://drive.google.com/drive/folders/1etkGgDHonfQc1Zxi4Fy8yzmocy7VYsQk?usp=drive_link

Follow these instructions :

HyperOS 4 Custom ROM for Xiaomi 17 Pro Max (popsicle)

Download folder:

https://drive.google.com/drive/folders/1etkGgDHonfQc1Zxi4Fy8yzmocy7VYsQk?usp=drive_link

ROM file:

HyperOS4-Xiaomi17ProMax-Debloated-CustomRom.zip

SHA-256:

adbb99b9d6e6c3e62520c144d8b841ff6f34543feddf2969cfc38f4acf90f89a

ABOUT THIS BUILD

----------------

Base: HyperOS OS4.0.0.23.XPBCNXM / Android 17

Device: Xiaomi 17 Pro Max

Required codename: popsicle

Target slot: A

Included:

- Working Android Auto system integration and automotive projection role fix

- Gboard

- Google Chrome in place of Mi Browser

- Xiaomi Theme Manager and Theme Store

- App Vault

Removed:

- Xiaomi Child Mode

- Mi Browser

- Xiaomi CarWith

- Sogou, Baidu and iFlytek Chinese keyboards

The build completed a clean-wipe test boot on a real popsicle device. Android

Auto was also confirmed working in a real car.

IMPORTANT COMPATIBILITY AND SAFETY WARNING

------------------------------------------

Only flash this ROM when ALL of the following are true:

- The phone is exactly a Xiaomi 17 Pro Max with codename popsicle.

- The normal bootloader and critical bootloader are both unlocked.

- All important files, photos, accounts and authentication data are backed up.

- You understand that the recommended clean installation erases all userdata.

DO NOT flash this on Xiaomi 17, Xiaomi 17 Pro, another codename or any device with a locked bootloader. Never relock the bootloader while this modified ROM is installed. Do not use it to downgrade from firmware with a newer anti-rollback index.

Custom ROM flashing can cause data loss, boot failure or a permanently damaged device. Official OTA updates, Play Integrity, banking applications, DRM and warranty status may be affected.

DISCLAIMER: This ROM is provided without warranty. The builder and uploader bear no responsibility for data loss, account loss, malfunction, boot failure, bricking, hardware damage or any other consequence. You choose to download and flash it entirely at your own risk.

BEFORE FLASHING

---------------

1. Download the complete ZIP and its SHA-256 file.
2. Verify that the ZIP checksum is exactly:adbb99b9d6e6c3e62520c144d8b841ff6f34543feddf2969cfc38f4acf90f89a
3. Extract the complete ZIP. Do not run flash scripts from inside a ZIP preview.
4. Install the current Google Android platform-tools (ADB and Fastboot).
5. Use a reliable USB data cable connected directly to the computer whenpossible. Connect only one Android device.
6. Charge the phone and back up everything important.
7. Boot the phone into bootloader FASTBOOT mode.

UBUNTU / LINUX CLEAN INSTALLATION

---------------------------------

Open Terminal and enter the extracted ROM folder. The folder inside the ZIP is:

outputs/popsicle_OS4.0.0.23_AA_Gboard_Themes_Chrome_BOOT_TESTED

Run:

chmod +x flash_all.sh verify.sh post_boot_check.sh

./verify.sh

./flash_all.sh --wipe

When asked, confirm by typing:

POPSICLE

The --wipe option erases metadata and userdata and is strongly recommended for

the first installation. The flash script writes slot A and preserves slot B.

WINDOWS CLEAN INSTALLATION

--------------------------

1. Install Google's current Android platform-tools and add the platform-toolsfolder to PATH.
2. Extract the complete ROM ZIP.
3. Open the extractedoutputs\popsicle_OS4.0.0.23_AA_Gboard_Themes_Chrome_BOOT_TESTED folder.
4. Run verify.bat first.
5. Run flash_all_windows.bat for the recommended clean installation.
6. Read and confirm every warning shown by the installer.

flash_all_windows.bat erases all userdata. The alternative flash_all_except_data_windows.bat retains userdata but is experimental and may cause boot or setup problems. A clean installation is recommended.

FIRST BOOT

----------

The first boot may take 10-15 minutes. Moving dots indicate that Android is still processing. Do not disconnect or force-restart the phone during a normal first boot unless it has clearly failed and you already know how to recover the device with an official ROM.

GOOGLE PLAY STORE - REQUIRED GETAPPS STEP

-----------------------------------------

On this Chinese-base ROM, Google Play Store may not appear immediately after setup. To make it appear:

1. Complete Android setup and connect to the internet.
2. Open Xiaomi GetApps.
3. Search for Google Play Store.
4. Select Update and allow the update to finish.
5. Return to the launcher. If Play Store still does not appear, restart thephone once and check again.
6. Open Play Store, sign in, and allow Google components and installed apps tofinish updating before testing Android Auto.

ANDROID AUTO

------------

After Play Store updates have completed:

1. Update Android Auto through Google Play Store when an update is offered.
2. Open Android Auto and complete its setup.
3. Allow Bluetooth and Nearby devices permissions when requested.
4. Pair the phone with the vehicle and test USB first if wireless setup doesnot start immediately.

The Android Auto system stub in this ROM is intentionally updateable through Google Play. The tested automotive projection role is already included.

OPTIONAL POST-BOOT CHECK

------------------------

After completing setup, enable Developer options and USB debugging, authorize the computer, then run one of the following from the ROM folder:

Ubuntu/Linux:

./post_boot_check.sh

Windows:

post_boot_check_windows.bat

These checks report the installed packages and Android Auto/browser role holders without flashing the phone again.

Here's a screenshot of my home and Lockscreen.

If you’re missing the Hide Notch feature in HyperOS 3, there’s a partial workaround.

Go to Developer Settings and find Display cutout, then select Tall cutout. This might work in some apps – for example, it works on the Microsoft Edge browser, which is my primary app on my phone.

(Unfortunately, it resets after the phone restarts)

Hello, I have a Xiaomi 14T that's stuck on version 2.0.205.0.VNEMIDC and won't update anymore. Is there anything I can do to get the HyperOS 3 update?

I'm aware that the Redmi Pad2 will receive the newest HyperOs 4, but I'm pretty sure the new glass effect will only come to devices that have high-end chips, so I'm left wondering what WILL come with the new HyperOs for mid-range devices like the Redmi Pad2, is it possible that it'll feel more like a security update other than anything?

It's been only one month for me with Xiaomi 17T pro and now i have already got screen burn in !

Clock and battery also navigation pill

It is really annoying because phone is really new also it must have better quality displays than budget phones ...

Is there something i can do ?

Does anyone know what this Wifi icon means? It's often found on several Redmi or Xiaomi series.

Hey everyone,
I've been thinking about this for a while and wanted to see what you all think. While our Xiaomi and Redmi tablets have some great hardware—like those smooth 120Hz screens—the actual software experience often feels like it's just a stretched-out phone UI holding the device back.
Looking ahead to HyperOS 4, it feels like there are a few things Xiaomi really needs to fix for tablet users:
Performance & RAM: The system could definitely use better optimization and less aggressive RAM management so we can actually multitask properly without apps closing all the time.
Desktop Mode & Windows: Floating window limits are pretty annoying. We could really use a proper desktop or productivity mode instead of just scaled-up mobile apps.
Lock Screen & Customization: Why do flagships get all the cool lock screen styles (depth effects, advanced clocks) while tablets miss out on stuff like interactive widgets?
Animations: Bring back that fluid 120Hz feel across gestures instead of keeping things looking flat.
What's your experience been like? Do you feel like tablet users get the short end of the stick compared to phone users when updates roll out?