Database Develop

Disabling Device Administrators triggers Apps getting activated again

Update (28. Sep. 2014):
Did some more research on that matter for I found this really annoying. Deactivated Apps shall remain deactivated, even more so for as long as we don't have root yet.
Figured finally out (reproducible) that it's Disabling Device Administrators to trigger (some) Apps to get activated again.
Steps to reproduce:
Goto Settings -> Apps -> All
Deactivate e.g. Chrome, Google+, Hangouts, File Commander, Gmail, Maps, Play Store, Sony Select or Video Unlimited (so it's not only the GAPPS coming back).
Check the App Drawer, all the above should no longer be visible.
Goto Settings -> Security -> Device Administrators: Disable a Device Admin (BTW: Enabling does not re-activate Apps, only deactivation!)
Check the App Drawer again and find all of the above deactivated Apps have re-appeared.
This works in 23.0.A.2.98 (customized DE) as well as 23.0.A.2.105 (customized UK).
Sony: please fix this asap.
Devs: please, please give us root. The phone is worth it
Original assumption (OUTDATED):
Noticed a strange behaviour in builds 23.0.A.2.98 (customized DE) and builds 23.0.A.2.105 (customized UK) w.r.t. deactivated Apps getting automatically re-activated after changing language settings.
Started off with 23.0.A.2.98 (customized DE) on my phone and deactivated e.g. Chrome, Google Play Store, Google Play Services and some other Apps. Now, as I wanted to make some screenshots in English, I changed language settings from German to English. That moment Chrome, Google Play Services and otheres (but not all of them) got automatically re-activated and also (re-)appeared in the App drawer. Changing the phone back to German did not help as still some Apps keep getting re-activated after say a re-start of the phone.
Then, installed 23.0.A.2.105 (customized UK), immediately set it to German during first boot, deactivated same apps as before and guess what... same here.
It looks as if whenever you set your phone to use a language different to the one for which the build was localized for this problems shows.
Can anyone please try and confirm?

This explains this reactivating of Apps. I was trying to deactivate Admin for the Sony Enterprise something. It re-activates automatically and reactivates some of the disabled apps. Not all though...
Very anoying. Especially that Sony gives themselves admin rights again after I deactivated it.... hmmm.

msm1111 said:
Very anoying. Especially that Sony gives themselves admin rights again after I deactivated it.... hmmm.
Click to expand...
Click to collapse
Happy to see (well, kind of, for it shouldn't be present in the first place) that finally someone has been able to reproduce the bug.
In order to get rid of admins "Sony Enterprise API" and "Sony My Xperia" do the following:
Download ADB and store it somewhere on you PC.
Enable USB debugging on the phone and connect it to your PC.
Open a command window and navigate to where you stored ADB.
Type "adb shell" at the prompt, hit ENTER and and the prompt changes to "[email protected]:/ $"
To block "Sony Enterprise API", issue command: "pm block com.sonymobile.enterprise.service"
To block "Sony My Xperia", issue command: "pm block com.sonymobile.mx.android"
While we are at that (though not an Admin, yet annoying), to block "What's New", issue command: "block com.sonymobile.advancedwidget.entrance".
The result of the block commands should look like "Package %PACKAGE_NAME% new blocked state: true. If still "false", you have to deactivate the corresponding admin in the settings first and re-issue the command again.
Only thing I have not been able to figure out yet is how to remove/block admin "Configuration Agent" but that one does not turn on itself (like the "Sony Enterprise API" does).

sxtester said:
Only thing I have not been able to figure out yet is how to remove/block admin "Configuration Agent" but that one does not turn on itself (like the "Sony Enterprise API" does).
Click to expand...
Click to collapse
Ah, thank you!
Configuration agent is: pm block com.sonymobile.deviceconfigtool

Wonderful, that removed my last (unwanted) one.

Thanks. I'll try it on Sunday! Is this enterprise stuff actually good for something? Or just tracking.

msm1111 said:
Thanks. I'll try it on Sunday! Is this enterprise stuff actually good for something? Or just tracking.
Click to expand...
Click to collapse
This is mainly for policy enforcement on mobiles given to employees by their company.
Check this for more info: http://developer.sonymobile.com/201...-work-with-our-sdk-and-become-a-sony-partner/

Just a quick note to say thanks to the guys who wrote this one up. I managed to follow the instructions and get rid of the whats new icon ive lost a bit of my touch though as this is not for those who don't know what sdk is.
pm block com.sonymobile.enterprise.service with this one I was getting: "False" without knowing how to change it to "true"

sxtester,
Thanks! It worked! I got rid of this stuff. I needed some attemps and reboots in between.
For "com.sonymobile.enterprise.service" you need to first disable admin and block "com.sonymobile.mx.android", reboot, then disable admin for the enterpriseAPI, block, reboot. Now its gone
I also successfully blocked "com.sonymobile.advancedwidget.entrance", "com.sony.smallapp.launcher" and "com.sony.smallapp.app.widget"
As I am not so familiar in adb, may I ask what is the difference between blocking and disabling (I guess its the same disable I can do in Settings/Apps)? I realized the blocked packages do not show up in the "pm list packages" anymore. Disabled ones do. Is there a list to see what was blocked? Thanks.

Btw I can also confirm that the OP is correct. When I first disabled Sony enterprise most or all of my disabled apps were re enabled.

Every thing worked great, thanks for help!

Thank you!!! Worked great Z3

PM BLOCK commands don't work...
I tried what was suggested above, but after I entered my ADB SHELL, the PM BLOCK command didn't work. I used the latest ADB that was installed on my system, but the only command that seems relevant to this was: PM DISABLE. I used that with the packages mentioned but they didn't get disabled. I had to disable them manually again after rebooting.

m0b1f0n3 said:
I tried what was suggested above, but after I entered my ADB SHELL, the PM BLOCK command didn't work. I used the latest ADB that was installed on my system, but the only command that seems relevant to this was: PM DISABLE. I used that with the packages mentioned but they didn't get disabled. I had to disable them manually again after rebooting.
Click to expand...
Click to collapse
As you didn't specify the version of ADB, try the following:
Download EasyRoot Tool from http://forum.xda-developers.com/showthread.php?t=2784900
Don't run the tool itself, it won't work on the Z3/Z3C! However, it contains a very slim ADB version 1.0.31 which worked for me.
Unpack the ZIP to a directory of your choice.
Open a CMD Window and navigate to %YOUR_FOLDER%\EasyRootTool v12.3\files
Connect you phone and issue the PM block commans as described above.

PM BLOCK commands still don't work...
sxtester,
Thanks for your response. I tried all sorts of ADB versions (1.0.25) including the one you suggested. I had no luck. Once I issued any of the commands above, I got the message: "Error: unknown command 'block'". I am not sure what more I can do at this point.
Any ideas?

m0b1f0n3 said:
sxtester,
Thanks for your response. I tried all sorts of ADB versions (1.0.25) including the one you suggested. I had no luck. Once I issued any of the commands above, I got the message: "Error: unknown command 'block'". I am not sure what more I can do at this point.
Any ideas?
Click to expand...
Click to collapse
I used "hide" command and it worked like a charm, i.e.: pm hide com.sony...
Hope it will help.

[MOD] Nougat_PlayStore_Rom_Addon_ADB_Install

Must Be on Nougat Rom!!!
I recommend Starting on freshly wiped rom but. This requires Package Disabler Pro Be Installed.
PlayStoreNougatMods.zip
Extract zip
Enable Usb Debugging
Disable Verify apps over USB
Enable all disabled apps
Plug phone into computer watch phone screen accept usb debugging key for computer
Run Install_PlayStore_Rom.bat
Follow Instruction On Cmd Screen
Once Install Is All Done
Select Pixel For Home Launcher
Open Settings/Application/Default Application under Calling Select Phone
Open Language and Input
Open Virtual Keyboards and click manage keyboards and turn on GBoard keyboard
Open Developer Options
Set Window Animation scale to .05x
Set Transition Animation scale to .05x
Set Animation Duration scale to .05x
Open settings goto accessibility
Enable all the servicesexcept talkback unless you want it
In settings open applications
Open applications manager
Goto menu select speciall access
In Phone Administrators enable all except android device manager unless you want that
Now click back button and open Draw over other apps and enable all
Click back button and open Modify system settings enable all
Click back button and open Notification access enable all
Open Rom Control and Everything Installed will be accessed there
Features
Pixel Dialer V8 With working Video Calling
Pixel Contacts
Google Camera
AOSP Browser
Google Messenger
Google Clock
Google Calculator
Call Recording Via BoldBeast
Rom Control Mods
DNS66 Ad Blocking
Status Bar Mod
Torchlight With Volume Buttons
Access To IMS Settings And Advanced Calling
Keylight Duration Settings
Battery Bar +
Status Bar Internet Speed
Recent Bar In Notification Panel
Button Remapping Via AIO Gestures
Volume Button Music Skip
Fingerprint Gesters
Led Control Via Light Flow App
Volume Panel Mod

View attachment 4048810View attachment 4048811View attachment 4048812View attachment 4048813View attachment 4048820View attachment 4048821

Will this work on the nougat stock beta ROM? Since that's the only option for Verizon users at this point for nougat? Also do we have to root? It's under my assumption that there isn't root yet available for the stock nougat for Verizon... Looks awesome and excited to try this out and what options are soon to come for Verizon users because of this. Gives me hope for a nougat stock experience for Verizon s7 Edge users! Thanks again
Sent from my SM-G935V using Tapatalk

jonesj198 said:
Will this work on the nougat stock beta ROM? Since that's the only option for Verizon users at this point for nougat? Also do we have to root? It's under my assumption that there isn't root yet available for the stock nougat for Verizon... Looks awesome and excited to try this out and what options are soon to come for Verizon users because of this. Gives me hope for a nougat stock experience for Verizon s7 Edge users! Thanks again
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Inquiring minds want to know

I guess you havent seen this thread https://forum.xda-developers.com/ve...din-stock-nougat-firmware-s7-edge-to-t3558313
It will work on stock beta 2 but I have the official tmobile nougat firmware working on our phones. Only thing that doesnt work is wifi calling and Visual Voice Mail but Volte and Video calling work. So you might want to look into that

Just tried this and it did not work. The xml script for package disabler didn't do anything and once it got to the part where the device should reboot, it never did. Please help or advise?
Sent from my SM-G935V using Tapatalk

jonesj198 said:
Just tried this and it did not work. The xml script for package disabler didn't do anything and once it got to the part where the device should reboot, it never did. Please help or advise?
Click to expand...
Click to collapse
Did you accept the adb key when prompted did it install anything

Here is the package disabler pro import script. You can also just istall all of the apks manually if you have to
View attachment PlayStore.zip

I was never prompted to install an adb key... When does that happen? I click on the .Bat file, it finds my device. Then start following prompts
Sent from my SM-G935V using Tapatalk

jonesj198 said:
I was never prompted to install an adb key... When does that happen? I click on the .Bat file, it finds my device. Then start following prompts
Click to expand...
Click to collapse
When you first start bat file does it show device as unauthorized

jrkruse said:
When you first start bat file does it show device as unauthorized
Click to expand...
Click to collapse
No it shows three lines of text. One is the device ID I think, one says device is recognised, and then something else. Nothing about not being unauthorized, unavailable, not found or anything like that. It sees the device just fine.
Sent from my SM-G935V using Tapatalk
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
It doesn't need root right? Can you possibly post screen shots of the setup steps so we can compare screens and I'll try to post images of mine as well. Thanks for the help id love to get this working and try it out. Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Sent from my SM-G935V using Tapatalk

jonesj198 said:
No it shows three lines of text. One is the device ID I think, one says device is recognised, and then something else. Nothing about not being unauthorized, unavailable, not found or anything like that. It sees the device just fine.
Sent from my SM-G935V using Tapatalk
---------- Post added at 08:19 PM ---------- Previous post was at 08:18 PM ----------
It doesn't need root right? Can you possibly post screen shots of the setup steps so we can compare screens and I'll try to post images of mine as well. Thanks for the help id love to get this working and try it out. Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Click to expand...
Click to collapse
Here if you dont have those numbers before device its not recognized

Is usb debugging enabled and verify apps over usb disabled

Did you accept debugging key. If this never came up. In developer settings click revoke usb debugging the unplug and replug your phone into computet. If the below screen still doesnt come up start the bat file then it will pop up. Accept key close bat then reopen and start process

jonesj198 said:
Installing all the apks one by one just doesn't seem to be the same as what the OP describes
Click to expand...
Click to collapse
Installing apps manually will work just fine. Then just copy the playstore.xml file from the zip of it I posted and import it with pacage disabler pro it should disable 126 packages

stud

Enabling any of the apps in accessibility says this error "*app* does not support the current system language. The text-to-speech language will be set to to null, but this might cause unexpected behavior. When i click turn on settings crashes and it doesn't enable.

CyanideHD said:
Enabling any of the apps in accessibility says this error "*app* does not support the current system language. The text-to-speech language will be set to to null, but this might cause unexpected behavior. When i click turn on settings crashes and it doesn't enable.
Click to expand...
Click to collapse
What build is your rom. Beta 2?

jrkruse said:
What build is your rom. Beta 2?
Click to expand...
Click to collapse
TMobile nougat.

CyanideHD said:
TMobile nougat.
Click to expand...
Click to collapse
If you have the rom control app open it under useful apps and open samsung info and tell me your csc version

Data dis/enable

Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.

Tmobilefan906 said:
Ok. I am running magisk....made shell cmd task of data on and off...they work....but why when I click "use root", it says device doesn't appear rooted. Could magisk be the culprit? Thanks.
Click to expand...
Click to collapse
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Code:
/sbin/su -c "svc data enable"

axxbat said:
Tasker cannot detect root with MagiskSU. If you attempt to select the Use Root option, you get a toast: "Error, you device doesn't appear to be rooted." However, as mentioned here, if you preface a Run Shell command with /sbin/su -c, Magisk Manager will prompt to allow Tasker root access and your command will work.
Click to expand...
Click to collapse
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.

Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas

Tmobilefan906 said:
Yes. I know the commands for it. Lol. The task still works when I click the play arrow button in task window, it just says no root when I click use root.
Click to expand...
Click to collapse
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?

axxbat said:
Didn't mean to offend will give a try a Magisk-enabled ROM today and hope will be back with ideas
Click to expand...
Click to collapse
u didn't offend me at all

axxbat said:
Well. Original position:
- Used RR April 16, 2017 nightly build as fresh install
- recovered Tasker from TiB backup
- created new task
- to avoid cheating assumptions created Tasker's task shortcut to run the task.
Video link is below. Pay attention to LTE symbol in the beginning of the vid. Task's goal was to disable it. The task was run via desktop shortcut
https://drive.google.com/file/d/0B8jDZdXO_06aMW5GYVJIRjBfemM/view?usp=drivesdk
Arrgh.just saw - LTE link run down before the task run - Tasker spotted my homecells and tried to setup WiFi connection (but no WLAN settings were restored). Nevertheless, it changes nothing - Task call via shortcut didn't call any root complaints, did it?
P.S. no offences again. In the cast i've intentionally shown Magisk's superuser tab to demonstrate nothing but two apps had root access. But after restore Tasker asked for 'su' perms (baloon), and was granted. Maybe, skipped 'su' perms for Tasker is Your headache?
Click to expand...
Click to collapse
What u mean skipped su perms?

Tmobilefan906 said:
What u mean skipped su perms?
Click to expand...
Click to collapse
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?

axxbat said:
1:48 request dialog
Sorry for late reply. Could it be so that Tasker was asking for root permission, but was not granted? Also, guess, You've checked that Tasker is in Device Administrators?
Upd. Stupid assumption. You've said , the task works when running on its own, from Tasker, but pops up the warning, when 'Use root' is checked... Not a big specialist in Magisk, but, haven't You use something like 'Hide root from apps' or alike in Magisk?
Click to expand...
Click to collapse
I guess I'm not too worried about it. As long as the task works, I'm fine with it. Haha

how to open Magisk after it's hidden?

I outsourced rooting my device. Now I need access to Magisk to change the settings for the monitoring software I need to install. How do I open the Magisk app after it's been hidden? TIA!!!

It's in your app drawer, named "Manager".

gamoses said:
I outsourced rooting my device. Now I need access to Magisk to change the settings for the monitoring software I need to install. How do I open the Magisk app after it's been hidden? TIA!!!
Click to expand...
Click to collapse
Just run the app "Magisk Manager" or "Manager" (with the Magisk icon) that is on your app drawer.
Don't you have it? Well, then you don't have a proper installation of Magisk, at least the Manager is lacking. Download it (the apk) and install. Then open it and see if everything is fine or not. Check main Magisk release thread for links.

Thank you so much for replying! Magisk Manager is not in my app drawer, but it *is* listed in the device settings as an installed app. I just can't figure out how to open it. I assumed that app had also been hidden somehow. Advice?

Whoever you outsourced it to have done something that's not standard. Ask them...

Bummer. They'll probably charge me again. Thanks for your help, though!!!

gamoses said:
Bummer. They'll probably charge me again. Thanks for your help, though!!!
Click to expand...
Click to collapse
By the sound of it, they've messed up. So if I were you I would demand they fix things free of charge.

Didgeridoohan said:
By the sound of it, they've messed up. So if I were you I would demand they fix things free of charge.
Click to expand...
Click to collapse
Yeah, that didn't work. So I'm again trying to DIY...
Your wonderful guide says:
Unhiding the Magisk Manager
Go to the Manager settings and choose "Restore Magisk Manager".
Click to expand...
Click to collapse
But I can't do that because "Manager" is not in my app drawer.
You also have:
Starting MagiskHide manually
MagiskHide is enabled by default and should start automatically on boot. If it isn’t working, try toggling MagiskHide off and on in the Manager settings. If MagiskHide just won't start when toggling it in the Magisk Manager (check the Magisk log, it might have started but the Manager doesn't reflect it), try starting it manually. This can be done in a terminal emulator (as su) by executing the following command:
su
magiskhide --disable
magiskhide --enable
Click to expand...
Click to collapse
So I downloaded a terminal emulator and ran this command, but got this error message: su: unrecognized option '--disable'
Any more tips before I lose more money? Should I just try and reinstall Magisk completely? Having watched the tech guy do it the first time, I'm not sure I'm completely up for the task. Would it be easier after it's already been successful? Should this be straightforward, or am I better off handing over my wallet?
THANK YOU so much!!!

gamoses said:
Yeah, that didn't work. So I'm again trying to DIY...
Your wonderful guide says:
But I can't do that because "Manager" is not in my app drawer.
Click to expand...
Click to collapse
I'm curious... What happens when you want to grant superuser access to an app? Do you get the prompt to accept or deny?
I'm also curious what Magisk version you actually have installed. What's the result if you run this command in the terminal emulator:
Code:
magisk
You also have:
So I downloaded a terminal emulator and ran this command, but got this error message: su: unrecognized option '--disable'
Click to expand...
Click to collapse
You need to run the three commands separately, not all together.
Any more tips before I lose more money? Should I just try and reinstall Magisk completely? Having watched the tech guy do it the first time, I'm not sure I'm completely up for the task. Would it be easier after it's already been successful? Should this be straightforward, or am I better off handing over my wallet?
THANK YOU so much!!!
Click to expand...
Click to collapse
My first tip is to not trust your "tech" guy... From what you've described here it doesn't at all sound like he knows what he's doing.
Secondly, I would try to install the Manager and see what happens. Download the apk from here (that's the current version of Manager v7.2.0) and install that. If that works you're golden, if it doesn't report back...

I'm curious... What happens when you want to grant superuser access to an app? Do you get the prompt to accept or deny?
Click to expand...
Click to collapse
I don't know what this means or how to do that.
I'm also curious what Magisk version you actually have installed. What's the result if you run this command in the terminal emulator:
Click to expand...
Click to collapse
19.1
Secondly, I would try to install the Manager and see what happens. Download the apk from here (that's the current version of Manager v7.2.0) and install that. If that works you're golden, if it doesn't report back...
Click to expand...
Click to collapse
So I downloaded and installed this apk. I think. All that's necessary to do that is just click on it while on the phone, right? It said it was updating my previously installed Magisk Manager, so I assume it worked. But both immediately and after a reset, there is still nothing new in the app drawer. It still shows in my phone settings->apps, but that's it.
I've attached a log from my results in the terminal emulator regarding magisk and magiskhide. I'm sure I'm doing something wrong.

What launcher do you have? Sounds like the guy just his it from showing up the app drawer?
Sent from my MI 6 using Tapatalk

I was about to kick myself if it was that easy. Just installed Nova to check, and still no Manager app.
So should I just try to reinstall Magisk completely? Do I need to uninstall first? Is it as simple as opening the .apk on the device?

Hi, I have the same problem, did you find a solution?

Question Access denied popup

I'm using a rooted S21 Ultra. I'm on stock android.
It's been rooted for 1.5 years and there were no issues. A couple of months ago the attached popup started to appear. I press ok and it goes away. This can happen between once every 2-3 days to a couple times a day.
There were no significant changes on the device when this started, so I have no idea what caused this to appear.
On my searches I read that it could be the Samsung Health app, so I I installed it, but that didn't help. I guess it's another Samsung app? But which?
Right now I'm running A13, but this started a couple of months back when I was running A12. The upgrade didn't change that.
Any leads on this?

sagybp said:
There were no significant changes on the device when this started, so I have no idea what caused this to appear.
Click to expand...
Click to collapse
Yes there were, you rooted your phone. That's a "significant change".
sagybp said:
On my searches I read that it could be the Samsung Health app, so I I installed it, but that didn't help. I guess it's another Samsung app? But which?
Click to expand...
Click to collapse
A number of Samsung apps will check for root/Knox status, and since Knox is hardware based (i.e. trip it once, and it's tripped forever), even if you return to complete stock, these apps won't work.
It's mainly the apps whose data security heavily depends on the phone's root status (even if it's currently unrooted, it's been 'compromised'), so Samsung Health, Secure Folder, etc. are the main culprits for such a message. However it's possible that Samsung added a system-level check that causes the pop-up.

fonix232 said:
Yes there were, you rooted your phone. That's a "significant change".
Click to expand...
Click to collapse
I will clarify again. My phone was rooted for about 16 months before this message showed up. It's been rooted 1.5 years and the message is here for 2 months. This is what I meant when I said no significant changes before the message appeared.

I have the same problem when I first bought the phone, I rooted it, then I unrooted it, but because knox was triggered, android 12 was not coming out, so it started to appear after I made the CSC change. android 13 e upgrade

Someone had a discussion on this link last month, so I wrote it, but no one answered.
How to fix "Access denied" screen randomly appearing on rooted devices
A couple of days ago my S21 Ultra running G998BXXS5CVIF automatically opened an "Access denied" screen. It was impossible to show which app cause it as it disappeared once you got to the app switcher menu. Access denied Unauthorized changes...
forum.xda-developers.com

For rooted
Delete System/priv-app/DigitalKey + uninstall update
OR
Execute this from terminal
Code:
adb shell
su
pm hide com.samsung.android.dkey
For unrooted
You can try disable appears on top permission for digital key app

The phone is not rooted, is there a non-rooted solution? @dr.ketan ?

Can you explain in more detail what programs should be used to do what you wrote?

musakamis said:
The phone is not rooted, is there a non-rooted solution? @dr.ketan ?
Click to expand...
Click to collapse
Edited above
In case that doesn't work try this with adb shell on PC
Code:
pm uninstall com.samsung.android.dkey

musakamis said:
Can you explain in more detail what programs should be used to do what you wrote?
Click to expand...
Click to collapse
For permission you don't need third party app
Open settings - apps - enable show system app - search Digital Key and disable show on top permission

Settings / apps / private access / show on top / Samsung wallet digital key is it correct? Dear @dr.ketan

B I got results by following this way, I recommend it.

dr.ketan said:
For permission you don't need third party app
Open settings - apps - enable show system app - search Digital Key and disable show on top permission
Click to expand...
Click to collapse
I can't see the digital key app. I'm on android 13 and don't see enable show system app option. thanks your help will be appreciated

musakamis said:
B I got results by following this way, I recommend it.
Click to expand...
Click to collapse
which method did you follow?

Settings/apps/private access/Samsung wallet digital/tap to disable show on top access denied window won't pop up again

musakamis said:
Settings / apps / private access / tap on Samsung wallet digital turn off show on top access denied window won't open again
Click to expand...
Click to collapse
I don't see private access in apps only private share?

senin için video çektim ama yükleyemem özelden atarım tamam

musakamis said:
senin için video çektim ama yükleyemem özelden atarım tamam
Click to expand...
Click to collapse
cheers