Search results

Not sure if this is the correct thread for this, but I just noticed that the category for Redmi Note 12 is labeled with only "sunstone". It is missing "tapas" and "topaz", which represent the much larger part of users for that device group. I'm not sure who exactly is responsible for forum...

Your model is tapas - there is no NFC.

I'm encountering a similar behavior as the people before; I don't see much parallels to what you linked. There isn't a traditional "crash" and also not only when installing. What im encountering: When (re)booting, it first takes a long time on MI-Logo, then restarts the boot from scratch. On...

For me it's in "settings>battery>charging options" and working perfectly... What device do you have?

Had the same issue on my 14 Pro a few patches ago. I think it can be fixed by using the volume up button while assistant is trying to use sound. It should appear a new sound channel for digital assistants which for some reason is muted by default.

https://xiaomidriver.com/

I'm too lazy to double check for HOS 2.0, but it was definitely working on 1.0 CN before switching to EU and stopped working after switching.

That's why you buy android devices. Just download the APK form apkpure or any other APK mirror.

Doesn't sound like too bad of an idea. Why don't u do it?

First of all, read rules 1 and 2 of this thread. Aside from that: the latest firmware available for public package download is 2.0.104.0. which is the same that xiaomi.eu released a couple weeks ago.

It just got launched, and as the ROMs also just went public, the xm.eu version will probably be published within the next days-weeks, depending on how busy the devs are. Anyways: read rules 1 and 2 of this thread please.

This is a forum for xiaomi.eu custom ROM for Xiaomi Smartphones. Either head to Mi General section or try again on official Mi forum. http://new.c.mi.com/global/

The question is, if we swap the stock recovery in the installer package with twrp file before installation, could this lead to any problems while/after installing?

Interesting, thanks for the heads-up. Anyways, I still wonder why we don't just include the A15 twrp as recovery.img then. Simply because it's slightly more work and not 100% necessary or is there another reason?

You will definitely need a PC with fastboot. For some reason (nobody here understands), the devs no longer include twrp in the ROM. This means, we either have to reflash twrp manually after each update, or (if you don't need twrp for other things) you just use fastboot for every update. ...or...

Not really... It seems to me it only happens sometimes after using a PD charger instead of original one, and its usually fixed by performing a reboot. Still don't know the actual reason why it happens tho...

Its normal that it remains on quick charging. The charging mode option only decides if it uses normal PowerDelivery ("Quick charging"), or Xiaomis turbo charging ("120W MAX"). Usually, if it doesn't use 120W mode, it means that it detects the cable to not be compatible with 6A. Have you tried...

Did you set charging mode to "Top speed"?

Yes, you can just update without wipe. If you are using LSPosed, you should uninstall it and install this one instead. It's a modified fork by JingMatrix because main release LSPosed doesn't support Android 15 and would break your whole Zygisk functionality.

Have you tried installing the app using ADB with a PC? This way, it is possible to bypass things like target SDK lock, maybe it works in this case aswell.