Stromberg kernel passed validation, but validation failed, arrow os kernel could not be verified, tried beta and last stable updateI know that there is an issue with Magisk/Google Api right now on rooted phones. The dev is working on it (April 15). I reset my phone on Sunday and did not root it with Magisk. I uninstalled Magisk before resetting.
I'm still failing Safetynet with this error, fail (response payload validation failed).
I also get an app error with a Toyota app that I need - "The Toyota app does not support rooted devices." So minus Magisk I should not be/or test as rooted? Maybe this is triggered by the unlocked phone.
I checked on the Arrow Github page and didn't see any Magisk issues posted. Are other users having this issue.
Same with PixelExperience OSS vendor buildWaveOs switched to android 11 firmware & vendor.
Issues bellow 5% battery are also fixed
Just to be clear, you downloaded and installed app-debug.apk on top of Magisk 22.1?
Too early for that.Start using OSS vendor please
Just installed for you to try it's working or not. It's working on GAPPS version of the rom. So try flashing GAPPS one.This may be a stupid question, but I'll ask anyway:
We are using the latest nightly of ArrowOS 11 VANILLA + Magisk Stable + microG on our POCO X3 NFC phones, and I tried to install Call of Duty®: Mobile on the phone of our eldest son, but it just wont work. When started, it first shows a white pop-up with text missing, and after clicking on OK and granting required permissions it just quits or crashes.
I don't have the time to analyze this any further, but my son really wants to play that game and is quite disappointed about his new phone because of that.
Anyone any idea what the issue may be?
The problem I am experiencing triggers exactly at the moment of trying to return to the Android Auto interface on the headunit: if my phone's screen is on, then it works. If the screen is off, then Android Auto crashes and Error 11 is received.
I tried deleting caches, data, I checked battery optimization was off for Android Auto. I even formatted my device, and nothing.
I just flashed Pixel Experience and the problem is gone...
What a pity.
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.Even dev says in dec the 3rd changelog that notification led was implemented, it still doesn't work for me