u/Hot-Lengthiness193

I'm using KernelSU with temporary root on my Redmi Note 14 4G (HyperOS 3 / Android 16), and my bootloader is locked. I want to know which modules are safe to use in this setup.

• Which modules actually work with temporary root access?

• Which modules should I avoid because they could cause bootloops or brick my device?

• Are there any anti-bootloop or anti-brick modules that can help recover from a bad module?

• Are there any Xiaomi-specific modules that work well with HyperOS?

I'd especially like to hear from people who have used temporary root access with KernelSU on Xiaomi devices. Which modules worked for you, and which ones caused problems or aren't worth installing?

Thanks!

First off, there’s a problem: you won’t be able to set a screen lock/home wallpaper from Gallery (Xiaomi’s default gallery app), or at least that’s what happened to me on my Redmi Note 14 4G. But I was able to fix it by installing other gallery apps, such as Fossify Gallery, Iris Gallery, etc.

Can it be reverted? Yes. There are two ways:

1. Take a screenshot of constant_template_editor_info and miui_15_default_lockscreen_info (in case you also edit this one) before changing style and templateid, so you know what your default clock style was. On my Redmi Note 14 4G, they were style:21 and templateid:classic_max.

2. Go to Settings > Personalization and set your default clock style. This will change constant_template_editor_info to your default style. Although that doesn’t change miui_15_default_lockscreen_info, it’s no problem: you can change it to the style from constant_template_editor_info, or if you don’t want to change it, that’s fine too; you’ll still have your default clock style.

First, try editing constant_template_editor_info and lock your phone to see if it has already been applied. If it hasn’t been applied, restart your phone. And if it still hasn’t been applied, edit miui_15_default_lockscreen_info and restart your phone.

There’s a problem, and it’s that you won’t be able to set a home screen/lock screen wallpaper from Gallery (Xiaomi’s default gallery app), or at least that’s what happened on my Redmi Note 14 4G, but I was able to fix it by installing other gallery apps like Fossify Gallery, Iris Gallery, etc.

How to enable the large clock on unsupported devices

Test device: Redmi Note 14 4G Global (HyperOS 3.0.303.0 / Android 16)

After testing on my Redmi Note 14 4G, I managed to change and customize the lock screen clock style (as shown in the images).

Requirements and preliminary steps

1. Download and install Shizuku and Settings Database Editor (using the Shizuku fork developed by Thedjchi is recommended).

2. Grant the necessary permissions so that Settings Database Editor can use Shizuku.

Procedure

1. Open Settings Database Editor, tap the search bar, and enter the term templateid.

2. Select the option constant_template_editor_info to edit it.

Recommendation: I suggest taking a prior screenshot of the current values (style and templateid) to have a backup in case you want to return to the original design.

3. Modify the templateid and style parameters using the values from any of the options available in the shared images.

4. Restart your device.

Troubleshooting (If the previous step did not work)

If the previous change does not take effect on its own (as happened to me on my Redmi Note 14 4G), do the following:

1. Find the entry miui_15_default_lockscreen_info within the same app.

2. Also modify its default values so they match the ones you chose.

Practical example:

· My original values in constant_template_editor_info were style:21 and templateId:classic_max.

· I changed them to style:2 and templateId:oversize_b, and restarted the phone (at this point the change still did not apply).

· Without reverting those changes, I went to miui_15_default_lockscreen_info (whose default values were also style:21 and templateId:classic_max) and replaced them with style:2 and templateId:oversize_b.

· Finally, I restarted the device again and the large clock began working correctly.

### How to enable the large clock on unsupported devices

**Test device:** Redmi Note 14 4G Global (HyperOS 3.0.303.0 / Android 16)

After running tests on my Redmi Note 14 4G, I managed to change and customize the lock screen clock style (as shown in the images).

#### Requirements and prerequisites

1. Download and install **Shizuku** and **Settings Database Editor** (it is recommended to use the Shizuku fork developed by Thedjchi).

2. Grant the necessary permissions for **Settings Database Editor** to use Shizuku.

#### Procedure

1. Open **Settings Database Editor**, tap the search bar, and enter the term `templateid`.

2. Select the **`constant_template_editor_info`** option to edit it.

> **Recommendation:** I suggest taking a screenshot of the current values (`style` and `templateid`) beforehand to have a backup in case you want to revert to the original design.

3. Modify the `templateid` and `style` parameters using the values from one of the available options shown in the shared images.

4. Restart your device.

#### Troubleshooting (If the previous step did not work)

In case the previous change does not take effect on its own (as happened to me on my Redmi Note 14 4G), do the following:

1. Search for the **`miui_15_default_lockscreen_info`** registry within the same app.

2. Also modify its default values to match the ones you chose.

> **Practical example:**

> * My original values in `constant_template_editor_info` were `style:21` and `templateId:classic_max`.

> * I changed them to `style:2` and `templateId:oversize_b`, and restarted the phone (at this point the change still hadn't applied).

> * Without reverting those changes, I went to `miui_15_default_lockscreen_info` (whose default values were also `style:21` and `templateId:classic_max`) and replaced them with `style:2` and `templateId:oversize_b`.

> * Finally, I restarted the device again and the large clock started working correctly.

Android Developer Verifier has now arrived on the Redmi Note 14 4G Global.

Not sure how I feel about this, especially considering the changes coming with Android 17.

Has anyone else on the Global variant received it yet? Is this part of the HyperOS rollout, or is Google rolling it out separately?

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.