Magisk v 20.2 - Fingerprint auth double step - Magisk

Hey there, community !
I've noticed that since last update, whenever Magisk prompts for su authorization I have to press "grant" button and then touch the fingerprint to authenticate. I would like to got back to just touch the fingerprint for authorization.
I've already reinstalled Magisk, double checked configuration, cleaned up dalvik/art cache but the 'problem' persists.
TLDR;
What I want:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What I've got:
Thanks you all !
EDIT: Wondering if it is an Android 10 "feature" rather than a magisk 'bug'

If I remember correctly, that's caused by the Magisk Manager supporting Google's new biometric authentication API (Pixel 4 face unlock) and not something that can be changed.

Penaa said:
Hey there, community !
I've noticed that since last update, whenever Magisk prompts for su authorization I have to press "grant" button and then touch the fingerprint to authenticate. I would like to got back to just touch the fingerprint for authorization.
I've already reinstalled Magisk, double checked configuration, cleaned up dalvik/art cache but the 'problem' persists.
TLDR;
What I want:
What I've got:
Thanks you all !
EDIT: Wondering if it is an Android 10 "feature" rather than a magisk 'bug'
Click to expand...
Click to collapse
They're using the new API for Biometrics. It's not actually an Android 10 feature, but just a new API... It also looked like that on older versions such as Pie (older versions than Pie aren't tested yet.)

yashinodon said:
They're using the new API for Biometrics. It's not actually an Android 10 feature, but just a new API... It also looked like that on older versions such as Pie (older versions than Pie aren't tested yet.)
Click to expand...
Click to collapse
By 'they' you mean Android or Magisk ?
Thanks for the answer !

Related

Viper4Android on Oreo 8.1 Roms

Hi All,
I've been able to successfully install Viper on several Oreo Roms - it works fine for internal speaker and wired headphones. However as soon as I connect my Bluetooth Headphones (Sony MDR1000X) the driver state changes to Abnormal and Viper stops processing - meaning I don't get Viper goodness through my Bluetooth headphones.
I've tried every which way to install Viper, various APK's, Flashable Zips, all available in Magisk, ARISE sound system, etc..
The same occurs across all Oreo Roms. Works fine on Nougat Roms...
Any ideas? Anyone else see the same behaviour?
Thanks
Paul
How did you installed V4A on Oreo 8.1? I'm running LOS 15.1 on Mi6 I can't figured it out how to install it. Classic I/O error...
I have this exact same problem, have you found any solution to this yet?

			
				
The only Oreo ROM I was able to get this working on was the MIUI Oreo. I no longer own the Mix, moved to a Note 8. Hope you guys get to the bottom of this!
Using Mi6 with LineageOS 15.1. Perfectly running was at first build but now ( running 3th build ) it gives I/O error still can't able to solve...
Chandler Muriel Bing said:
Using Mi6 with LineageOS 15.1. Perfectly running was at first build but now ( running 3th build ) it gives I/O error still can't able to solve...
Click to expand...
Click to collapse
SOLVED! Just ROOT your device with latest Magisk (using v16 now), open Magisk menu tap downloads and type "viper4android" and then download and install "ViPER4Android FX for Magisk v15" module. Now you are good to go!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Magisk Hide

Magisk Hide doesn't seem to be working when it comes to my automobile's app, Uconnect. I'm rooted and now the Uconnect app states that I'm using an unsupported device. It worked before rooting.View attachment magisk_log_20181022_153305.log
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
tried clearing apps data?
kamilmirza said:
tried clearing apps data?
Click to expand...
Click to collapse
Yes. I even uninstalled, then reinstalled the Uconnect app.
destiple said:
Yes. I even uninstalled, then reinstalled the Uconnect app.
Click to expand...
Click to collapse
THIS great module might help :fingers-crossed:
Destiple, can you confirm whether MagiskHide Props Config, which kamilmirza referred you to, worked?
Alternately, did you find another solution to get Uconnect working?
If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).
Didgeridoohan said:
If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).
Click to expand...
Click to collapse
That's very good to know. I'm nervous about running a Canary build on my normal phone, but I'll see if I can find a spare to test it on.
Will the new MagiskHide be on the next Magisk update, or is it several versions away from being in the stable build?
Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.
Coop9 said:
Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.
Click to expand...
Click to collapse
Good to know! I tried it - hiding the manager by itself wasn't enough. But once I added Uconnect to the apps being hidden, *then* the app finally loaded.
Of course, upon trying to log in, the app immediately crashes. Would that have anything to do with it being added to the MagiskHide list?

Camera stop working

After last update to v22, my camera stop working. Magisk is just partylu installed iI think. App is installed, but when I try install using recovery option, after reboot there is no change in App. Safety net test return fail. Help me with this camera, I really need it.
Camera detect if safetynet is failed? That's new
ineedroot69 said:
Camera detect if safetynet is failed? That's new
Click to expand...
Click to collapse
Both issues arose after the Magisk update.
Your phone is Google pixel or nexus?
NO, Xiaomi Mi Mix 3.
Any ideas? Where is developer?
by stop working does camera app shows stop working error or just complete black when open?
It was showing "unable to connect to the camera" when I launched the camera app. After rebooting the phone, it got into a bootloop and TWRP is asking me for the password to decrypt my files.
Now phone is dead thanks to the "new Magisk v22".
how many battery percentage you have when opening the camera app??
Almost full battery. The new Magisk seems to be corrupting permission on the system partition.
have you tried "clear data" on camera app?
Yes, I tried when the phone worked and it didn't help. After rebooting, the phone only boots to TWRP and asks me for the decryption password.
have you given the camera app the camera permission?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes. It seems the problem is not with the camera, but with Magisk.
Awhqt do you mean by "After rebooting, the phone only boots to TWRP "?
Yes, it now only boots in TWRP and asks for the decryption password. Magisk installation corrupted system files.
then your problem is not camera but bootloop?
1. I updated Magisk to v22.
2. Problem with SafetyNet has appeared
3. The camera has stopped working
4. After rebooting, the phone goes into bootloop and only boots in TWRP asking for some password.
ohh I understand you keep saying camera so I thought camera is just broken but your on bootloop how did you install magisk via magisk_patched.img??

Question System UI isn't responding - after December update

Rooted Pixel7 here.
After the December update, I randomly get:
"system UI isn't responding"
Do you also have this problem without root?
Installed magisk modules:
LSPosed
volte-properties for pixel6
universal safety net fix
Systemless hosts
Call recorder skvalex
AOSP mods
Does anyone know where the problem is?
I was also getting random SystemUI crashes until I updated AOSPMods.
Unless you are on the latest canary builds (178+ I believe), you may see issues like this. There were lots of changes in the December feature drop that broke AOSPMod for many users.
Well thank you. And what version of AOSP mods do you have?
I can't update.
ekeppel said:
I was also getting random SystemUI crashes until I updated AOSPMods.
Unless you are on the latest canary builds (178+ I believe), you may see issues like this. There were lots of changes in the December feature drop that broke AOSPMod for many users.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm on canary build 186, which is the latest as of this post. Just open the AOSPMods app, hit the 3-dot menu in the upper right, select App Updates, then select the Canary update channel / full package, and finally hit Update. After the update, you will be prompted to reboot.
NOT COMPATIBLE WITH Android 13 Dec 2022 (Feature drop 2022), or AOSP 13 R18 or Later
Right. The version you have installed has issues with the December update. You should see the AOSPMod app in your apps list though all the same, and it should open just fine. It's just that many features are broken. Once you get into the app, you can change over to the Canary channel and get the working version.
Edit: By the way, even though it says it's not compatible when you're on the canary branch on Github, the latest builds are in fact compatible. These updates were just rolled out over the past couple of days.
Thank you for your help and your time.
I updated it successfully.
Great! Hopefully, that was the source of your SystemUI crashes. ;-)

Hotel app Marriott detects Magisk and root

Please see discussion already at
https://www.reddit.com/r/Magisk/comments/yf8gyu
Security message when running an app
Hello I installed the Marriott app this morning, and when I go to run it, i get that security message along the bottom third of the screen, and the app shuts down. What is causing that?
forum.xda-developers.com
Calling on the broader community to look at this, as I only start to have this today. I have also tried HuskyDG's Magisk Delta which is said to have brought back MagiskHide, but I failed. Thanks
try this https://forum.xda-developers.com/t/guide-howto-use-banking-apps-on-your-rooted-device.4530801/
supermansaga said:
Please see discussion already at
https://www.reddit.com/r/Magisk/comments/yf8gyu
Security message when running an app
Hello I installed the Marriott app this morning, and when I go to run it, i get that security message along the bottom third of the screen, and the app shuts down. What is causing that?
forum.xda-developers.com
Calling on the broader community to look at this, as I only start to have this today. I have also tried HuskyDG's Magisk Delta which is said to have brought back MagiskHide, but I failed. Thanks
Click to expand...
Click to collapse
Thanks. It does seem to work, except I didn't perform these following steps mentioned. Maybe they are not applicable to the latest 3.1.1 version on GitHub instead of play store? Also don't think I truly understand how to use template. Finally, there is a popup to ask me to uninstall Magisk? Probably not a good idea.
Under the Preference head, tap on Select hide methods -> Check API requests, Intent queries, ID detections -> Tap OK
Under the Template config head, tap on 0 additional apps invisible -> Check Magisk, LSPosed and HMA
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lelakon666 said:
try this https://forum.xda-developers.com/t/guide-howto-use-banking-apps-on-your-rooted-device.4530801/
Click to expand...
Click to collapse
It worked several times but has since been busted. Maybe I didn't set it up correctly?
I heard Magisk Delta by HuskyDG could hide it from detection. Has anyone been brave enough to try? Well, I tried and it didn't work. I tried the whitelist mode by leaving Marriott out of the SuList and many other banking apps too. But it still detects root. Marriott app version 10.13.1. Older version say 10.12.0 and below should survive.
marriott’s new version 10.15.0 appears to have fixed the over-detection issue. Shamiko is now 0.7.1. not sure if relevant

Categories

Resources