- 6 Oct 2016
- 10,503
- 322
Xiaomi disabled some animations/effects on low-end GPU devices for performance.Hi guys so I updated my sapphire to hyper os 2.2 eu and the CC animation is totally gone, can y'all explain me why it happened?
Xiaomi disabled some animations/effects on low-end GPU devices for performance.Hi guys so I updated my sapphire to hyper os 2.2 eu and the CC animation is totally gone, can y'all explain me why it happened?
Glad it's disabled after 2.2Xiaomi disabled some animations/effects on low-end GPU devices for performance.
Outside of America it's spelled "Personalisation" the "z" is an American English thing. Might be an option to set American English as system language, but that's how it's spelled.Hi there, I wanted to report this typo in settings. It reads "Personalisation" instead of "Personalization"
I attached screenshots below.
Yes, yes, I'm aware of that, that's why I'm reporting, my device language is English (United States), as you can see, it's spelled "Personalisation" in the list, but once you enter the menu, the header reads "Personalization", I mean, there should not be two different strings for the same word in EN_US.Outside of America it's spelled "Personalisation" the "z" is an American English thing. Might be an option to set American English as system language, but that's how it's spelled.
English translation is provided by Xiaomi.Yes, yes, I'm aware of that, that's why I'm reporting, my device language is English (United States), as you can see, it's spelled "Personalisation" in the list, but once you enter the menu, the header reads "Personalization", I mean, there should not be two different strings for the same word in EN_US.
go on install, switch to image and then flash the img to the recovery partitionSmall heads up for houji users going through TWRP for updates.
It might just be me, but this time the option "flash current TWRP" didn't work.
Maybe a hick up on my side, but would advice to flash the actual image to be sure.
I know, but I didnt have the image on my device as I always use the native TWRP option.go on install, switch to image and then flash the img to the recovery partition
yep sadly had the same issue....I know, but I didnt have the image on my device as I always use the native TWRP option.
So if I would have been traveling (without a laptop) I wouldn't be able to get root after rebooting.
So that why I'm just giving a heads up to prevent others getting into such issues.
I had a computer nearby so was up and running again in a few moments.
Dont think they will ever.yep sadly had the same issue....
i hope they will be able to put that recovery into the rom as standard
Just to confirm that 2-step verification by SMS doesn't work on the latest Aurora 2.0.2090. SMS messages from Google aren't being received. I receive SMS messages from friends and messaging seems to be working fine. 2FA was working before installing Xiaomi.eu, and it works on my other phone with the same SIM card. Sorry to say, but this prevents me from using this ROM because I need 2FA for work.I installed the ROM successfully on the 14 Ultra. It seems working fine, but one issue appeared. I can't receive 2-step verification SMS from Google. I receive SMSs from friends and messaging seems to be working fine. Does anyone else have such experience? Also, I'm not sure if installing modem firmware from the latest global version may solve the issue, as I receive SMSs and maybe the issue is somehow related to Google...
If I remember well, the update without recovery was broken for people not using HyperOS 2 previously.In my opinion better would be to have no recovery in the "update" file.
Let people keep what they have.
But they have their reasons I guess.
And I'm not going to complain, as I'm happy with all other.
That makes sense, although it would than be an option to stop this from now on and make a clear message for people coming from A14 to first flash an earlier A15 version.If I remember well, the update without recovery was broken for people not using HyperOS 2 previously.
Found it :
![]()
HyperOS 2.0 - HyperOS 2.0 STABLE RELEASE
Hello, has anyone experienced issues with the new OS version 2.0.9.0VNBCNXM released for the Xiaomi 14 Pro (Shennong)? Inviato dal mio 23116PN5BC utilizzando Tapatalk The only issue I've noticed so far with version 2.0.9.0VNBCNXM on the Xiaomi 14 Pro is the WiFi signal, which seems a bit unstable.xiaomi.eu
Tenker
![]()
Supported Devices
The devices we choose to support are entirely at our own discretion, and will change according to various circumstances. Generally speaking, we only support devices with all of the following characteristics: Is a standard phone (not a foldable/flip or a tablet). Is powered by a Qualcomm...xiaomi.eu
![]()
Community-funded MediaTek Support
We have launched a community-funded initiative to support select MediaTek Dimensity devices. The details are in the "About" section of the Patreon page: https://www.patreon.com/xiaomieu/aboutxiaomi.eu
Hello,
Is there no image available for Xiaomi 14T Pro, or have I overlooked something?
Thank you
No, having a fully bootable ROM "out of the box" is a must, having TWRP is a user choice.That makes sense, although it would than be an option to stop this from now on and make a clear message for people coming from A14 to first flash an earlier A15 version.
I assume there are now more people updating who use TWRP than there are people still coming from A14.
Anyway, again, for me no problem, just that I recommended before to use "flash current TWRP" and this time (maybe just once) if wasn't working.
Flashing "something else" would still be your ROM.No, having a fully bootable ROM "out of the box" is a must, having TWRP is a user choice.
Forcing people to flash something else before flashing our ROM just because some users use TWRP is not acceptable.
"A version without recovery inside" means uploading 2 separate ZIPs. SourceForge will not be happy about that.Flashing "something else" would still be your ROM.
But I see what you mean and don't disagree actually.
Maybe in an ideal world, let the updater app download a version without recovery inside.
But I see the extra work that would mean for you guys.
Google has own, that's the bottom line. There are solutions but these are not cut and dry. You need to research and nothing is guaranteed. Keyboxes are banned left and right by big G so even Strong integrity is short lived and needs constant attentionHello,
I'm delighted with the Xiaomi.eu project. I've been supporting it since 2019 and will continue to do so for as long as necessary, but I believe we, as users, need information...
I'd simply like to know if a solution is being sought for the payment module or, on the contrary, if Google has won.
I'm in no rush for it to be resolved, but I would like you to be honest with users.
I repeat, I'm delighted with the project and am not interested in switching to any other ROM.
Thank you for your work.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation