Thanks.
This means small firmware-only packages to update vendor and driver stuff and so on.Thanks.
What does that mean under "Requirements"?
° Make sure you've latest Stable firmware flashed before flashing the ROM.
Can I installed it without losing data or getting problem? i'm using paranoid androidThis means small firmware-only packages to update vendor and driver stuff and so on.
For Spes: https://xiaomifirmwareupdater.com/firmware/spes/stable/V13.0.12.0.SGCMIXM/
For SpesN:
https://xiaomifirmwareupdater.com/firmware/spesn/stable/V13.0.6.0.SGKEUXM/
Can be flashed separately and updated at any time. Just download and flash in recovery. You can also flash spes fw in spesn and vice versa. But there's a chance that nfc doesn't work, then simply use the other one (just for those with spesn reading this).
Never had problems like this while using the corresponding firmware for my device. Flashing the wrong firmware (eg from other redmi like note 11S etc.), on the other hand, will most likely hardbrick your phone. Luckily spes and spesn are cross-compatible with each other's firmware. So a little caution while searching should be given. And yes, simply flash in recovery if you think your fw is outdated or doesn't match with the ROM's setup recommendations. CheersCan I installed it without losing data or getting problem? i'm using paranoid android
A full stock(ish) miui always contains the corresponding firmware. So yes, correct. It's more important for rom users to have an eye on the fw recommendations. But if you choose to flash a rom, then you already know the state of your fw version.My Redmi Note 11 NFC has MIUI-V13.0.6.0.SGKEUXM. So it should also have this firmware version below:
https://xiaomifirmwareupdater.com/firmware/spesn/stable/V13.0.6.0.SGKEUXM/
Correct?
So no need to update my firmware, right?
on a side note, this seems to happen to every AOSP roms for this device. Not sure why this is happening
is there any temporary solution to fix AOD? like magisk or somethingon a side note, this seems to happen to every AOSP roms for this device. Not sure why this is happening
If I had to guess it's probably because there's a hook in the display driver somewhere for a low-power state meant for AOD that AOSP doesn't know about. That might change now that they're beginning to release kernel sources, but I could be wrong.on a side note, this seems to happen to every AOSP roms for this device. Not sure why this is happening
yesDoes fast charging and unlimited google photos backup work with this rom?
Thanks
Very good. MIUI Android 11 used ~6-7%/hour on normal usage for me and this is with battery saver turned on at all times. Updated to MIUI Android 12 and it drained even more battery.How is the energy efficiency compared to original MIUI OS?
Are there comparable battery saving modes?
I need this phone for work and need good battery life.
Both of them, may be fast charging a bit slower than stock but don't worryIt has both unlimited google photo backup and fast charging or just one of them?
Thank you so muchBoth of them, may be fast charging a bit slower than stock but don't worry
Yes, you can use paranoid update like otaAnother question
Can i update this rom like i can update miui, without going into recovery and flashing it all over again. And without losing data.
Also how can i install this rom without bricking the device? Please tell me if there is a video tutorial.
Thanks
First of all, bug reporting here is for stable releases. Second, it's a known bug related to the custom kernel the build's using. No workaround actually.
PA? Most likely, next year. By the way, it is considered rude here in the forum to ask for ETA (estimated time of arrival).
Funny, I skipped Stable 3 for the upcoming beta releases what seem to explain that I never got the gps issue. On the latest beta (from Dev's sourceforge folder) Chrome even plays videos again.Apparently there are 3 known bugs right now:
However, the latest update also brought the stock MIUI camera which is great. Apart from that, everything else is superb as I previously commented. Battery, etc. everything s great.
- GPS not working
- Video not working on Chromium >113
- Issues with screenshot on on some apps in work profile
I've been dirty flashing since early beta and had no problem with GPS however (even in Stable 3), only after I clean flashed into Stable 3 that I get the bug.