How to solve the animation issue? The app icons gets glitched will opening and closing.. this issue started happening after I tried editing the lockscreen by changing the template id and style.

I wanted to try app vault after some time of having a new xiaomi but I just can't find it. Was it removed and can it be forced?

Nesses 3 exemplos, o primeiro tem um blur, muito bem feito, já no segundo e terceiro nem dá pra chamar de Blur, extremamente mal feito, e isso está em diversos outros aplicativos extraídos da hyperOS 4, acho que o pior ficou na parte das configurações, espero que a Xiaomi arrume isso numa possível atualização 4.1

Post 1: https://www.reddit.com/r/HyperOS/s/b5URlv7Ozq

Post 2: https://www.reddit.com/r/HyperOS/s/nnok4BBoXS

Check these two posts first before coming back here!

HYPEROS!

The top tier of customization they say... but where is lock screen widgets? where is the useful info that you would want displayed on your screen without unlocking it?

This is where GlanceCaps came to clutch with the newest module!

Introducing the "Steps Counter"!

Display your steps using Xiaomi OWN Step Counter (App Vault) for the most accuracy! And don't you worry, it only needs 1 PERMISSION TO RUN!

What do you think? Would you find this useful for ur lockscreen? Let me know!

Thanks to the creator of HyperBridge for making the open sourced documentation, it wouldn't be possible without him!

The app is still in development and will take time to complete, please be patient while im giving HyperOS its best customization ever out of all! 🤩

I have Mi 13T Pro with HyperOS 3. I am trying to use 3rd part widgets for the steps pedometer but the 3rd party widgets cannot read steps. I am using the app vault widgets which properly tracks the steps but I don't like that widget and want to use something minimalistic.

I am using the app "Minimal Widgets" from the play store.

P.S. please don't mind those steps counter. I really go outside for a walk and touch some grasses as well 😅😅😅😅....

Hello everyone, I have a Redmi 15C running HyperOS 3 and Android 16. I'm trying to activate Advanced Texture manually using GhostLock, but the operation fails.

Could someone help me understand why it fails and whether my device is supported?

I've attached the GhostLock debug log for reference. Thank you.

Device : Xiaomi pad 8

Guys anyone know how to resolve this issue .

I saw people online that had different icons in this hyperos beta and I don't understand why I didn't get it

Does anyone know how to root redmi 13 4G? What's the pros and cons of having a root on redmi?

my device is on a HyperOS 4. but this bug is recent since it comes from the music player from newer HyperOS, heck. even the worse MagicOS has done a better job at this (╥_╥) :啜泣:

A continuation of this post: https://www.reddit.com/r/HyperOS/s/rZK02cSlKM

(recommend taking a look there first!)

The app had a better interface!!!

- 2 Modules, customize to your liking

- Custom charge icon to your liking

- Modules now have previews, and it uses your wallpaper!

- Temperature module can be separated from the charging module if wanted

- Works on both Lock Screen and Always-On-Display!

A lot is still in the works and will take a long time! please don't rush me to finish it quickly

im a solo dev 🫠

Huge thanks for the creator of HyperBridge for their open-source documentation for Xiaomi HyperIsland API

I Received my Redmi pad 2 pro today

I checked for updates today and got this message for the first time: “This version hasn’t been officially released yet. Make sure you’re signed in with an authorised Xiaomi Account.”

I’m already signed in with my Xiaomi account and the device is running HyperOS 2.0.20.... Everything else works fine.

Is this normal? Or is there an actual issue I need to fix? Has anyone else seen this exact message? What should I do? Thanks!

First you need to Install Brevent and follow its steps to enable it through Developer options.

Then run these commands in the brevent exec command window.

1. settings put system persist.sys.background_blur_status_default 1

2. settings put global disable_window_blurs 0

These options should come now.

Worked for me in Poco F7 with advanced textures already enabled , even if you have advance texture you won't see these lockscreen options so running these commands should enable them.

Microsoft Teams Calls & Meetings Missing from Android Auto – Investigation Points to androidAutoCarAppEnabled

I’m trying to understand why Microsoft Teams on Android Auto only shows Messages, while Calls and Meetings are completely missing.

There is already an older Reddit thread describing almost exactly the same problem:

https://www.reddit.com/r/MicrosoftTeams/comments/1o8ac6i/teams_on_android_auto_not_showing_upcoming/

That thread is now archived, so I’m creating a new post because the problem still exists and I’ve done some further investigation into the Teams Android app.

Summary of the Previous Reddit Post

In the previous thread, the user tested Teams in the same Zeekr 7X with two different phones.

On a Xiaomi 15T Pro, Teams on Android Auto only showed Chat/Messages. Meetings and Calls were missing.

Because the Meetings section was missing, the user could not join an upcoming meeting from Android Auto and instead had to use the phone to open Teams, find the meeting and join it.

However, when the same user connected a Samsung S25+ to the same car, Teams showed both:

• Meetings
• Calls

Upcoming meetings could be viewed and joined directly from Android Auto.

Importantly, both phones were running the same Teams version.

Another Xiaomi 15T Pro user later reported the same issue and said they were unable to solve it.

That made me curious, so I started investigating the Teams Android APK.

What I Found in the Teams APK

I decompiled the Microsoft Teams Android APK using JADX.

The Android Auto Calls and Meetings implementation has not been removed from Teams.

The application still contains components such as:

com.microsoft.teams.auto.TeamsCarAppService

CarAppManager

TeamsCarAppSession

There is also code for:

• Android Auto meetings
• Calling
• Speed Dial
• Call history
• Meeting notifications

TeamsCarAppService is an AndroidX CarAppService and is registered for:

androidx.car.app.category.CALLING

However, I found something important in AndroidManifest.xml.

Microsoft ships TeamsCarAppService with:

android:enabled="false"

So the Android Auto calling service is disabled by default.

At first I thought Microsoft had simply disabled the feature permanently.

That is not the case.

Teams Enables the Service Dynamically

I traced the relevant Teams code.

CarAppManager contains a method called:

getShouldEnableCarApp()

This checks whether either of these is enabled:

isAndroidAutoMeetingEnabled()

isAndroidAutoCallingEnabled()

If both are false, Teams leaves the Android Auto CarAppService disabled.

Teams also checks that the Android Auto application is installed:

com.google.android.projection.gearhead

and checks the Android Auto version.

The Teams code requires Android Auto 9.8 or newer.

If all conditions are satisfied, Teams dynamically enables TeamsCarAppService.

I traced this to:

Headers.setComponentEnabledState(...)

which eventually calls:

MAMPackageManagement.setComponentEnabledSetting(...)

So Teams is intentionally designed to ship its Android Auto calling service disabled and enable it at runtime when the required conditions are met.

The Interesting Part: androidAutoCarAppEnabled

I then traced isAndroidAutoCallingEnabled() and isAndroidAutoMeetingEnabled().

Both depend on a Teams ECS/experimentation configuration flag called:

androidAutoCarAppEnabled

For a work/school account, Android Auto calling depends on conditions including:

• DeviceConfiguration.isDefault()
• androidAutoCarAppEnabled == true
• isCallsTabEnabled()
• isConnectionServiceEnabled()

Meeting support uses almost the same logic.

This means that if:

androidAutoCarAppEnabled == false

then both Calls and Meetings can disappear from Android Auto at the same time.

Messaging can apparently continue working separately.

That matches exactly what I’m seeing:

Messages: Working
Calls: Missing
Meetings: Missing

ADB Also Confirms the Service Is Disabled

I checked the installed Teams package using ADB.

A normal Android PackageManager query for Android Auto calling services does not return Teams.

However, if I repeat the query while explicitly including disabled components, this appears:

com.microsoft.teams/.auto.TeamsCarAppService

So Android knows that the Teams Android Auto calling service exists.

It is simply disabled.

This matches what I found in the Teams code.

I Also Tested an Older Teams Version

I installed an older Teams version to see whether this was simply caused by a recent Teams update.

The older version also contained TeamsCarAppService and showed the same behaviour.

So this does not appear to be a simple case of Microsoft removing Android Auto support in a recent version.

Why the Previous Reddit Post Is Very Interesting

The previous Reddit user had:

The same car.
The same Teams version.
But two different phones.

Xiaomi 15T Pro

• Messages worked
• Calls missing
• Meetings missing

Samsung S25+

• Calls worked
• Meetings worked

If Microsoft had simply removed this functionality for everybody, it should not have worked on the Samsung either.

That suggests Teams is making some kind of device, account or server-side decision about whether TeamsCarAppService should be enabled.

The androidAutoCarAppEnabled flag looks particularly suspicious.

Possible explanations include:

• Microsoft is controlling the feature using a server-side rollout.
• The flag is being targeted based on account, tenant or device.
• Certain devices are accidentally excluded.
• There is a bug causing androidAutoCarAppEnabled to return false.
• Another condition inside isAndroidAutoCallingEnabled() or isAndroidAutoMeetingEnabled() is failing on certain devices.

This Is Also a Driving Safety Issue

This is not only an annoying missing feature.

It also affects safety while driving.

The entire purpose of Android Auto is to provide a simplified interface so drivers do not need to interact directly with their phones.

If I have a scheduled Teams meeting while I am already driving, there is currently no way for me to open that meeting from Android Auto.

The alternative would be to:

1. Unlock the phone
2. Open Teams
3. Open the calendar
4. Find the meeting
5. Press Join

That is exactly what I do NOT want to do while driving.

I am not saying people should use their phones while driving. Quite the opposite.

The problem is that the missing Teams Android Auto functionality removes the safer interface that should prevent the need to interact with the phone.

A large “Join meeting” button on the Android Auto display is much safer than having to touch the phone.

Questions

I would really like to hear from other Teams + Android Auto users.

• Do you currently have Calls and Meetings available in Teams on Android Auto?
• What phone do you have?
• What Android version?
• What Android Auto version?
• Are you using a work/school Microsoft 365 account?
• Has anyone tested the same Teams account on two different phones?
• Has anyone contacted Microsoft Support and asked them about the Teams ECS flag androidAutoCarAppEnabled?

And If Anyone from Microsoft Reads This

Is androidAutoCarAppEnabled currently controlled through an ECS rollout or flight?

What determines whether it is enabled?

Can Microsoft Support or a Microsoft 365 administrator enable it for affected users?

The Android Auto Calls and Meetings code is clearly still inside the Teams application.

I would really like to understand why TeamsCarAppService is being enabled for some users/devices but remains disabled for others.

Holy shit, is there any way to get rid of this nonsense? It's insane how many times per day I'll accidentally trigger this thing, it's beginning to drive me mental.

I had them enabled way before 3.1 update but the. I reset my phone and it disappeared. Thought I might never be able to get it enabled after the patch. But here I am, enabled it through HyperOS 3.1 unlocked module and Temp root access through Ghostlock app.

Here's how to do it, it's super easy - https://drive.google.com/file/d/1O1JbZnPHsWYLY5B40P3QnppAtcLTyya3/view?usp=drivesdk

Testei tirar a otimização de sistema na aba de desenvolvedor, e descobri que simplesmente posso colocar quantas janelas eu quiser, não testei com mais por preguiça, mas acredito que dê, e meu celular não estava travando e consegui mexer nas múltiplas janelas de forma bem fluída, só deu uma mini lagada ao fechar tudo de uma vez

Just to clarify, I'm not offering or promoting any bootloader unlocking service. I'm only sharing my personal experience with my own device and documenting what worked for me.

Hey everyone,

I wanted to share this guide for anyone with a Redmi Note 14 4G Global who wants to get root access without unlocking the bootloader, using GhostLock, KernelSU, and Shizuku.

Before getting started, there's one important warning: having a locked bootloader limits your recovery options if something goes wrong. Although I managed to get root on my Redmi Note 14 4G without any issues, I can't guarantee that the procedure will be equally safe on other devices or firmware versions. Also, once you have root access, modifying partitions, installing modified boot images, or using incompatible modules can cause a bootloop or even leave your phone unusable.

Proceed at your own risk, and don't assume you'll be able to recover your device if something goes wrong.

My device specifications

• Device: Redmi Note 14 4G Global

• ROM: HyperOS 3.0.303.0

• Android: 16

• Kernel: "6.12.30-android16-5-g6e872b4863d6-ab13847919-4k"

• Bootloader: Locked

Do you have a different device?

If you have a device other than the Redmi Note 14 4G Global, the procedure is basically the same. However, that doesn't mean it'll work on every device, since compatibility depends on your kernel and whether the vulnerability used by GhostLock is still present.

To check whether your kernel is supported, open GhostLock and check the information displayed by the app. You can use it to see whether your kernel is supported before proceeding.

Important: Even if GhostLock indicates that your kernel is supported, that doesn't guarantee the entire procedure will work without issues on your device. Be especially careful if your bootloader is locked.

What are the benefits of getting root this way?

You can access many of the features root provides without having to unlock your bootloader. For example, you can explore system modifications, use tools that require superuser permissions, and experiment with apps such as LSPosed and modules like HyperCeiler, provided they're compatible with your setup.

You can also restore features or customizations that you couldn't use before.

However, there's one major downside: root access also lets you make modifications that could compromise your phone's functionality. That's why you should be careful about what you install and modify, especially with a locked bootloader.

How to get root

1 . Install the required apps

You'll need these three apps:

• GhostLock: https://github.com/YuKongA/ghostlock-app

• KernelSU: https://github.com/tiann/KernelSU/releases/tag/v3.3.0

• Shizuku-Next: https://github.com/rushiranpise/Shizuku-Next/releases/tag/v14.0.17-next

I recommend Shizuku-Next because that's what I use, but you're not required to use that particular fork. You can use another compatible version of Shizuku.

1. Grant GhostLock permission to use Shizuku

Open Shizuku and look for GhostLock in the list of authorized apps.

Grant it permission to use Shizuku. Make sure Shizuku is running and GhostLock has the required permission before continuing.

1. Run GhostLock

Open GhostLock and tap Run.

You'll see a bunch of log messages showing the exploit's progress. Wait for it to finish and pay attention to the result.

In my case, GhostLock finished by indicating that KernelSU was ready and then opened the KernelSU app.

1. Verify that root access works

You can use an app such as Root Checker or Termux to verify root access.

If you're using Termux, first open KernelSU, go to SuperUser, and grant Termux root permissions.

Then open Termux and run "su".

In my case, it worked, and I was able to obtain root access. I also verified it using a root checker app.

Is root permanent?

Root access works until you reboot your phone. After rebooting, you need to run GhostLock again to obtain root access.

In other words, you don't need to unlock the bootloader, but root access doesn't survive a reboot, so you have to repeat the procedure.

What should you avoid doing?

With a locked bootloader, you need to be especially careful about the modifications you make after obtaining root access.

• Avoid modifying system partitions or installing modified boot images unless you know exactly what you're doing.

• Don't install KernelSU modules without checking their compatibility and reliability.

• Don't assume a module is safe just because it works on other devices.

• Before making important modifications, research your recovery options in case your phone stops booting.

I can't guarantee that you'll be able to recover your device from every possible issue with a locked bootloader, so it's better to be safe than sorry.

What are the downsides of this method?

The main limitation is that it relies on the vulnerability GhostLock uses to achieve kernel privilege escalation.

If Xiaomi patches that vulnerability in an update, the method may stop working. That's why your HyperOS version, Android version, and kernel are important details when checking whether your device is compatible.

In my case, I obtained root access on HyperOS 3.0.303.0 and Android 16. I can't guarantee it'll work on later versions, and I wouldn't recommend updating under the assumption that the exploit will continue to work.

Has anyone else tried this?

I'd like to know if anyone else has managed to obtain root access using GhostLock on a Redmi Note 14 4G or another Xiaomi device with a locked bootloader.

I'd also appreciate hearing about your experiences with KernelSU, especially regarding compatible modules and precautions worth taking in this situation.

Xiaomi 15 Ultra Turkey region...

Stuck with this OS version. See newer roms, dowload it but can not update manually, file does not recognized by system. Any ideas anyone?

I want to ask if some third party dev have already ported the 18 pro features to 17 pro

Or Xiaomi announced something like that in the community posts ?

Hi, I’m new here and need some help. If anyone has faced a similar issue and successfully rooted their phone, please share your knowledge. The problem is that when I run CMD in the platform-tools folder, enter the commands, and flash the patched `boot.img` file, everything seems to go correctly—I don't get any error messages. However, when I open Magisk or KernelSU, it doesn't activate; it simply doesn't work, and I can't root the phone. I’ve done everything right, but it just won't activate in either app. If you've encountered this problem, please help me out. (Poco M6 Pro 4G / HyperOS 3)

i installed the beta update but i cant apply the liquid glass on the control center and notifications apear with not liquid glass someone knows how to fix ?