Search results

Okay, I understood and it's understandable.. and I stick with my above mentioned solutions then.. I'm disabling it for like 2 years now already but I feel I don't experience any side-effect (other than the fact that my apps which I want to run.. just are running - which is nice). Anyway, thanks...

Thanks and sorry for the code tags. Probably it worth a try to make some test builds and setting persist.sys.periodic.enable to false. Since /system is not RW anymore build time is the time to change it (: It's kind of an annoying feature.. isn't it? Even though memory management of MIUI can be...

Hi Everyone.. So I hope this is a bug and not a feature.. Xiaomi Redmi Note 9 Pro (joyeuse) && Android 12 && MIUI 13 xiaomi.eu_multi_HMNote9ProEU_V13.0.2.0.SJZMIXM_v13-12-fastboot This issue is persistent since ages, really. I can't really tell when I figured this out (like 2 years ago) but...

Are you sure that the recovery image you are trying to use is exactly for your device?

I think you probably simply disabled "Allow window-level blur" in Developers options and thats why you don't see blur. No need for any module. I don't know about any that can solve this for you.

Thanks but big no-no, I'm not into ports. Edit: you can laugh all the way but ports aren't made for that device so hw control problems are always expected (NFC for instance). I know that lots of phones are sharing almost the same hw (and thats how and why the miatoll tree has been created) but...

Joyeuse has no chinese variant, therefore there's no chinese ROM for this device.. that's why Xiaomi.EU uses the MIXM Global ROM as base ROM. Plus chinese ROMs lack GApps.

Of course you can flash the FBEv1 zip from the FBEv2 version, just use a USB OTG pendrive or a microSD or whatever.:emoji_thumbsup:

Guess you flashed the FBEv2 version of OFox (R11.1_4_A12_FBEv2.zip) but MIUI is using FBEv1 (R11.1_3_A12_FBEv1.zip is the latest) so I suggest you to flash the latest FBEv1.

How unfortunate that the ROM built today is still fastboot, even though we already have stable FBEv1 TWRP/OrangeFox.. but such is life :D Happy new year!

Did you mess with MIUI optimization? All your sympthoms are matching with the state when it is forced to be off..

What is your fastboot.exe version? When did you update your fastboot last time? I suspect that it's old for your phone.

Yes, indeed it means Joyeuse users can only update to MIUI 13 of Android 12 via fastboot because at the moment when the mentioned ROM has been released there was't a TWRP or custom recovery that was considered stable enough to be used for installing MIUI V13 Android 12 ROM and that's why there's...

That's because the Note 9 Pro (Joyeuse) still has no stable TWRP or any custom recovery that supports Android 12 and MIUI V13 and thus the actual update that the updater is referring to is actually a fastboot ROM -which you said more or less: no recovery ROM- and can't be installed nor verified...

Hi. As I mentioned the actual unit in my hands is running on Xiaomi.EU V13.0.1.0 which is Android 12 and unfortunately I can't check it on Android 11 at the moment. Never the less I tried the TWRP build you posted with the ROM this phone runs on and it does not work, not even asking for PIN /...

Indeed I started with an Android 11 build, one of the first Xiaomi.EU builds and upgraded from build to build to the latest one and yes, indeed at the very moment my /data has the same data as before (I will explain why I emphasise this). But! When I formated /data for testing and started the...

Thank you for your time and effort to look into this. I'm using the Xiaomi.EU Android 12 MIUI V13.0.1.0.SJZMIXM for my Joyeuse. The interesting (to me) is the fact that the log says that metadata decryption failed - even though there aren't any files in /metadata/vold/metadata_encryption and...

Thank you. Is the source is open? I have this problem with OrangeFox - guess you solved it? I hope..! Edit: nope, it fails exactly the same way.. Full log attached. I don't know whether it's important or not but /metadata/vold/metadata_encryption is empty for me..

I can save you some time and labour, I'm already done with this -> same OFox issue and -of course- it is still FBEv1, I documented it here. Please read my posts there back and forth for some pages.

That has nothing to do with the original question / situation. OFox has a separate build for ROMs using FBEv1 and FBEv2, this is the root cause. Of course moving to a custom ROM with FBEv2 after a format is not a problem, but you can't "upgrade" a ROM that used FBEv1 to use FBEv2 wituout formating.