Thank you, I installed NGcam 7.4 again and got the recommended config to work. Now I'm completely happy with this rom, nice work.
Same problem here, works somtetimes for up to a few few minutes after screen is off then stops working, and since these OSS Builds random reboots occur sometimes (never happened with last pre oss 20210503), but sine I´m selling this phone I don´t bother anymore.
You have to flash Miui 12.0.1 before flashing Arrow OS because both have to be on the same Android version... If you don't, then your phone will be in bootloop for sure...Hi all,
Quick question, can I flash Arrow OS, coming from MIUI, without updating MIUI to the latest version available?
Right now I have MIUI 12.0.9 Global on Android 10. The latest version available is 12.0.1 on Android 11. I just don't want to upgrade because I'm afraid of Xiaomi adding ARB to Android 11.
ARB is for Anti Rollback. Basically once you update you cannot go back to the previous version. Flashing a previous version with a lower ARB number will brick your phone. Reason why I want to avoid upgrading.
Poco doesn't have ARB, I could go back to previous versions of MIUI without problems.
I got the same message today, even though I'm using 20210601 build.
Alright, I think I got it working. I had Magisk Hide for Google apps and banking already activated. I hadn't hidden the manager yet though.
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)
I'm aware of the notification led issue, its interlinked to an sepolicy denial from vendor which is quite tricky to address it while we're using the prebuilt/stock vendor. For now you can assume it as a trade off for enforcing builds. I'm working on a fix, once we start a full transition towards an OSS vendor these issues will be more convenient to be addressed.