yesterday i tried to flash this rom, coming from 12.5.1 global miui. I was not able to boot the gapps variant of the rom, however i was able to boot vanilla variant, here are the steps i followed, can someone help me identify the issue why gapps variant did not boot or was i too quick to assume its stuck?
then i went back to recovery and flashed firmware+vanilla+gapps>format data>yes>reboot>boot within a minute.
Does the gapps variant take this much time to first boot as compared to vanilla? or did i miss something?
thanks for confirming that it takes longer time to first boot with 'gapps included version'.yes the "GAPPS included, version" does take a lot of more time for the 1st boot, I don't remember if it was more than 10 minutes , but it took yes.
you don't have to flash every time the firmware from XIAOMI (do you use global , European or the Indian version?)
I guess you download the correct version of ArrowOS, I mean the Official one , and not the Experiments?
and personaly I don't use the "add more zip" option in TWRP, it seems every time something goes wrong. After I install something with TWRP, I then reboot to TWRP again, and istall the second .zip
(which GAPPS version do you use? OpenGapps, FlameGapps, NikGapps?)
I tried changing the absolute volume setting but it does not change anything... Still, thanks for the idea, mate...about Bluetooth: try to go to developer settings and enable the setting (in English): disable absolute volume
about alarm clock: it seems that after an update from Google, there are a few problems with google clock, many people around the world , never woke up to go for work!!! I don't use it , so I can not be sure, I always use another clock from PlayStore.
It looks OK with last update 18/9
I have a similar problem that I reported yesterday on GitLab.
So can you comment on my GitLab post as well ?
Maybe the developers will notice it sooner
i had the same problem a couple times, the only solution i found was to reboot the phone with the otg inserted, it works but in the past builds it was recognized as otg, now it recognizes it as if I had connected my phone to a pc
How do I cancel and disable forced encryption? I'm experiencing the same issue. In my case, I flash the DFE zip after the rom every update, but TWRP always asks for a password.
• November security patch
• Hotspot WPA3 Settings
• base: PixelPropsUtils: Update redfin fp to SP1A.211105.003
• Update translations from community
• For Quicksilver Kernel changelog see this (https://github.com/ghostrider-reborn/android_kernel_xiaomi_surya/commits/staging/LA.UM.9.x)
• Misc fixes and upstream changes
Ouch! I don't really look forward to a clean flash, it's my daily driver and some secure apps don't really like it (they think it's a different device), but I might try it sometime in the near future.
There's a thread for arrow 12
To everyone, please STOP this misconception about having the need to flash magisk in order to pass safety net. Do read the OP I've clearly mentioned there's no need of a magisk or modules for safety net. Device is certified and passes safety net out of the box without need of any modifications.Mission Impossible in all custom ROMs !
1. Safetynet check the bootloader status and will automatically fail if magisk is not installed (Magisk Hide ON must be applied for this) !
2. Furthermore, now you have to install the safetynet-fix module to make your banking apps working !
3. Finally, you must hide Magisk Manager.apk with a random name too (Magisk Settings)