Related
I have an AT&T Galaxy Note running official ICS - stock and rooted. I have SuperUser from ChainsDD.
These past few weeks, I have been seeing the message "shell has been granted superuser permission" in random manner. When it does, the message will keep showing up until I reboot the phone. SuperUser log will also the same messages...hundreds of them!
I couldn't pinpoint the reason it happening, but I see a bit of a pattern --> it happens when I tried to switch program quickly. Example:
1). Open up Dead Trigger game. Load a game and when it starts, quickly hit the Android back button and exit the game. The above message shows up.
2). Open GMail app. While the app is "loading" the list of message, I received a "Twitter" notification. From notification bar open the Twitter message to open the Plume Twitter app. The above message shows up.
I tried to uninstall apps that requires root one-by-one but the problem still exists. These apps are:
- AdFree
- AutoStarts
- BetterBatteryStats
- File Manager
- GameCIH
- Quick Boot
- Sixaxis Controller
- SuperUser
- Titanium Backup
- Wifi Tether (3 entries in SuperUser app)
- Wireless Tether (2 entries in SuperUser app)
- avast! Mobile Security
Not only the message is annoying, but it slows down the phone.
Can anyone tell me how to fix this?
The shell goes active every time any app starts, that has been given super user permissions..
You can turn off the SU "toast" notifications from within the SU application ....g
gregsarg said:
The shell goes active every time any app starts, that has been given super user permissions..
You can turn off the SU "toast" notifications from within the SU application ....g
Click to expand...
Click to collapse
I am aware about the "toast" notification, especially if I started an app like, say, File Manager that requires Root Access.
However, I don't think it's normal for the "shell" message to shows up EVERY 2-4 SECONDS. Even if I turned off "toast" notifications, the SuperUser log shows that same message and it slows down the phone.
Does your rooted phone shows that message in the SuperUser log files? I have HUNDREDS of them in a span of 1 minute. I am just trying to see if the above behavior is normal, but I think it is not because this does not happen to my past phone (Thunderbolt, Motorola Triumph, Galaxy S2) and tablets (Transformer, Galaxy Tab 7.0 Plus and Nexus 7).
lanwarrior said:
I am aware about the "toast" notification, especially if I started an app like, say, File Manager that requires Root Access.
However, I don't think it's normal for the "shell" message to shows up EVERY 2-4 SECONDS. Even if I turned off "toast" notifications, the SuperUser log shows that same message and it slows down the phone.
Does your rooted phone shows that message in the SuperUser log files? I have HUNDREDS of them in a span of 1 minute. I am just trying to see if the above behavior is normal, but I think it is not because this does not happen to my past phone (Thunderbolt, Motorola Triumph, Galaxy S2) and tablets (Transformer, Galaxy Tab 7.0 Plus and Nexus 7).
Click to expand...
Click to collapse
I think what the op meant here was:
Thanks for the quick response. I understand the "Toast" notifications, but that's not exactly what I am referring to. Here is a more detailed explanation of what is happening. [ insert description here] . Hope this better explains my problem and helps you to help me resolve this issue.
Thanks again.
lanwarrior said:
I am aware about the "toast" notification, especially if I started an app like, say, File Manager that requires Root Access.
However, I don't think it's normal for the "shell" message to shows up EVERY 2-4 SECONDS. Even if I turned off "toast" notifications, the SuperUser log shows that same message and it slows down the phone.
Does your rooted phone shows that message in the SuperUser log files? I have HUNDREDS of them in a span of 1 minute. I am just trying to see if the above behavior is normal, but I think it is not because this does not happen to my past phone (Thunderbolt, Motorola Triumph, Galaxy S2) and tablets (Transformer, Galaxy Tab 7.0 Plus and Nexus 7).
Click to expand...
Click to collapse
No...the device behavior is not normal...
I do get the notifications every so often, especially after a reboot, but never 1000's of times a day...
Try uninstalling super user, and install "Super SU instead.....
then go to your recovery, and wipe your caches, dalvik included...
After the reboot, your normal apps may require you to give them SU permissions again, but i'm thinking with the new app, it may fix your issue with the phone..
If not, you may have some sort of data corruption going on, and will need a fresh start...or, you have a rogue app thats kicking your azz....
also try an app monitor of some sort, to see if you get any apps that open/close non-stop....
And on a personal note, I understand you are frustrated.....And I get that...
And I'm only trying to help you....g
gregsarg said:
No...the device behavior is not normal...
I do get the notifications every so often, especially after a reboot, but never 1000's of times a day...
Try uninstalling super user, and install "Super SU instead.....
Click to expand...
Click to collapse
Since I already have SuperUser, do I install SuperSU first and then uninstall SuperUser?
gregsarg said:
And on a personal note, I understand you are frustrated.....And I get that...
And I'm only trying to help you....g
Click to expand...
Click to collapse
No worries, I was trying to provide more context of my problem in the 2nd post. Appreciate the help.
You should uninstall your superuser app first, then clear caches .
Then after reboot, install super SU..and reboot again.
This method will allow the device to see the SU app, and will prompt you for any interaction it may need ....g
shell granted su - result of Bug Report
See this thread HERE
-JR-
Turn off USB Debug in settings/developer options. That'll fix it.
--rk
jazzruby said:
See this thread HERE
-JR-
Click to expand...
Click to collapse
True...but that does not explain the bug report being initialized, or what triggered the event....
Disabling of USB debugging will shut down about 75% of the devices ability to interact with root apps and ADB operability.....
While it will stop the error from occuring, it wont fix the problem...
It may be simply a bad flash, with errors....we may never know....g
lanwarrior said:
I... Open GMail app.
Click to expand...
Click to collapse
I have the Mail.com app (probably the same rebranded as is for GMX.net) on my Galaxy S2 tab. It often hangs/freezes and being a helpfull guy I use the submit report feature. Immediately after this I also go in to the "shell has been granted superuser permission" cycle until phone restart. The battery goes into turbo drain if I don't restart PDQ & phone gets hot.
I've disabled USB debugging now too, and I'm hoping that this is the end of that nonsense.
So has anyone found the culprit of this, or a better solution to disabling 'usb debugging'? How was your experience with switching to SuperSU? I have a Note that constantly toasts the same shell stuff. My friend has a Note also with the issue. It slows the phone to a crawl, and drains battery until reboot.
Check your system for bugmailer.sh and rename it with a .bak extension.
[ /system/bin/bugmailer.sh ]
-JR-
JVogler said:
So has anyone found the culprit of this, or a better solution to disabling 'usb debugging'? How was your experience with switching to SuperSU? I have a Note that constantly toasts the same shell stuff. My friend has a Note also with the issue. It slows the phone to a crawl, and drains battery until reboot.
Click to expand...
Click to collapse
I switched to SuperSU and the problem goes away. Wohoo!
I disabled SuperUser from Application Settings and then installed SuperSU.
lanwarrior said:
I switched to SuperSU and the problem goes away. Wohoo!
I disabled SuperUser from Application Settings and then installed SuperSU.
Click to expand...
Click to collapse
So, I lost root access doing things in this order. Everything is working fine now, although it's only been a few minutes. I couldn't uninstall Superuser, the closest I could get, was uninstall updates, and then disable [It would be nice for superuser to show up TiBu, but it's not recognized at all]. Downloaded SuperSU, but it refused to open and froze my phone with each try. Ran 'root checker' and didn't have root access anymore since superuser was disabled. Had to enable superuser again, update it...give SuperSU root access via superuser, then SuperSU was able to gain control of my root access, and then I uninstalled updates, and then disabled superuser.
So it seems from my experience, that you have to leave your previous app for root access enabled long enough to grant the new app access to take over it's job.
So if anyone else is deciding to switch over, I'll save you a headache by making sure you leave Superuser enabled until you get SuperSU up and running.
Hopefully I've seen the last of these persistent 'shell notifications'
JVogler said:
So, I lost root access doing things in this order. Everything is working fine now, although it's only been a few minutes. I couldn't uninstall Superuser, the closest I could get, was uninstall updates, and then disable [It would be nice for superuser to show up TiBu, but it's not recognized at all]. Downloaded SuperSU, but it refused to open and froze my phone with each try. Ran 'root checker' and didn't have root access anymore since superuser was disabled. Had to enable superuser again, update it...give SuperSU root access via superuser, then SuperSU was able to gain control of my root access, and then I uninstalled updates, and then disabled superuser.
So it seems from my experience, that you have to leave your previous app for root access enabled long enough to grant the new app access to take over it's job.
So if anyone else is deciding to switch over, I'll save you a headache by making sure you leave Superuser enabled until you get SuperSU up and running.
Hopefully I've seen the last of these persistent 'shell notifications'
Click to expand...
Click to collapse
That's interesting. I didn't uninstall SuperUser, just disabled it so my thought this will not remove root. Maybe this has to do on how I rooted my phone.
Hey there. I just received my M8 yesterday. Really loving it. I have a feeling it won't sell well, which is really too bad. I have run across a few issues, though, and I wanted to list them here to see if anyone else experienced the same thing and also post my fixes/workarounds for what I did encounter.
Out of the Box, the first thing I did was unlock the bootloader and root. I rooted for two reasons: To block ads and tether free. I really don't care about custom roms or anything else. However, I ran into issues almost immediately, similar to my challenges with the M7.
Adblock - Adaway simply will not work because it can't write the hosts file. I tried sim linking to a different folder, but that also failed. Adfree worked for a while, but then quit. Both apps rebooted my phone spontaneoulsy when I ran them. Adblock Plus kind of works, but will also ocasionally stop and even block all of my internet. Workaround - I flashed a zip of an adaway host from June through TWRP. Ads are now blocked, but obviously it's an outdated hosts file.
Fitbit - I realize that I may be unique here, but I have been using a Fitbit for a long time. When I tried to set it up, the phone wouldn't let me log in (java error), then when I went back to the app, I was logged in, but my Fitbit One did not show up under devices. I tried to add it twice and it went through the whole process, but never actually showed up. Later, I went back into the Fitbit app and it was just magically there. Something is definitely up with the newest Fitbit app, at least on the M8, but all is working now.
Gsam - I want to see my screen-on time, but I can't seem to get Gsam to work correctly. Everything just says "updating". I tried uninstalling and reinstalling. When I installed the root helper, it rebooted my phone because it couldn't write to the system.
Tethering - I currently can not find a solution for tethering that works. I froze tether check with Titanium Backup and now toggling hotspot does nothing. With the M7, we had to flash a modified apk.
That's kind of it for now. If anyone has a better solution for ad blocking, I'm all ears. Also, anyone who comes up with a solution to tethering will be my personal hero.
Hi all
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
thx
This same problem,
S III, rom > http://forum.xda-developers.com/galaxy-s3/development/rom-archidroid-v2-4-6-power-hands-t2354859
Xposed framework installed
Greenify is device administrator
I have full version
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
If I may make a suggestion?
I started getting the same error message (it started right after I paid for the app). After reading "thousands" of pages I think I may have hit on the answer. Greenify is in "boost" mode, that somehow, even though it uses xposed framework, doesn't need root. So I checked supersu and greenify wasn't listed. Then I changed to "root" method and greenified an app, then supersu asked to allow greenify, thereby now having it listed again in supersu.
I then changed it back to "boost" and so far haven't had that error. Coincidently, Greenify seemed to work ok anyway even with that error.,
edit: well that blows, I started to get the error message again, so disregard what I wrote above. Maybe a fix is coming, or I'll live with manually starting auto-hibernation.
tnsmani said:
Please read the FAQ in post #2 in the main thread. Both of you may be having root issues.
Click to expand...
Click to collapse
No, I check this 3 times ...
colin p > nothing, still this same problem
anyone has ideas, what else, I can do ?
Just to add additional info, this auto-hibernation error only started after I bought the Donation Package. I don't know if it's something to do with the additional options or not. Before I bought the program, auto-hibernation worked fine.
I have a Nexus 4 (rooted with towel-root) and SuperSu and of course the Xposed framework. I uninstalled/re-installed Greenify, as well as the Donation Package and still the error pops up the first time I open Greenify. I then have to manually start auto- hibernation and it works ok after that, at least it "seems" to as everything is under the hibernated section.
After I re-installed, SuperSu asked to allow Greenify root access, so it is properly listed. I would imagine that if a significant few of us have the issue, a future update will address the error problem.
I would like to try to enable Greenify as root mode. Will the message appear?
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
This is not a definite fix, though in some weird circumstances, it might work
TechnoSparks said:
I would like to try to enable Greenify as root mode. Will the message appear?
The message appears in either root or boost mode on the first time the program is opened after a boot up.
If it isn't I would then disable the Greenify module in Xposed, then reboot (no soft reboot, just to be sure), enable module, reboot again, and then select boost mode within Greenify. Then make a last reboot. Then inspect the problem.
Tried your suggestion and still get the "auto-hibernation has stopped" error.
This is not a definite fix, though in some weird circumstances, it might work
Click to expand...
Click to collapse
Unfortunately, no dice. Still get that error, thanks anyway.
By George...
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
colin p said:
Well after a lot of screwing around, I think (at least for my circumstances) I "may" of found the answer. Because the error said something like "auto hibernation service is being blocked by 3rd party tool or system settings (ex.stamina mode in sony devi es. autostart manager in MIUI) Please whitelist greenify for automatic hibernation to work", I uninstalled Donkey Guard and Cydia Substrate (they were installed a couple of days before I got the pro version of Greenify, even though there was no problem with them before I got the paid version of Greenify), but still got the error. Ruling out program issues, this time I actually shut down my phone (no reboot or soft reboot) and on opening Greenify, no error. Since I was using the reboot toggle in "Notification Toggle", I tried rebooting through xposed (not soft reboot) and this time, no error. Tried again with Notification toggle and got the error.
So, at least for me, I think I may have solved the issue.....for now.
BTW thanks TechnoSparks as you gave me something to work with.
Click to expand...
Click to collapse
No problem mate. If it really works for a long time, it might be good to report here as I may take your method as a suggestion to other people facing the same problem as well. :good:
romdroid. said:
I am using a Samsung Galaxy Note 2 4.3 stock rooted and I am having some issues with greenify. Everytime I start the app to see if it working I get this message: "Auto-hibernation service is stopped" The problem is that I am not using a 3rd-party tool or any other mode as energy saving mode on my note 2 and I still get this message. What should I do to fix it?
Click to expand...
Click to collapse
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
I had not got this message for quite a long time, but after updating to beta 2, the first time I rebooted and opened Greenify, I got this message. Afterwards, for the whole of today, I haven't got it.
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
gorilla p said:
Everything is working great for me.
Make sure you have SuperSu (latest)
Also after installing Greenify, set it as a device administrator.
Settings>security>device administrators>select Greenify.
Enable accessability as well (settings>accessibility>Greenify>Enable.
I have these enabled and have no issues.
Sent from my Nexus 4
Click to expand...
Click to collapse
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
tnsmani said:
You are right. After my last post, I found that Greenify was not enabled in Accessibility settings.
After every update, the Accessibility setting has to be re-enabled. Why?
Click to expand...
Click to collapse
for me i have to enable it in accessibility after every restart of the phone ....
Anyone found a solution to this? I am getting the same error.
oasisfeng said:
Can anyone confirm whether it was fixed in 2.4.4 beta 1 or beta 2?
Click to expand...
Click to collapse
HI Oasis - just to reply that I am still getting Auto-hibernation stopped with Greenify v2.5.1
Basically after a while auto-hibernate just seems to stop. I have all my apps waiting to be hibernated even after a few hours of screen off. I do not get the 3rd party message saying auto-hibernation is stopped. I have Accessibilty on and have given Greenify Device Administration rights.
I will get the 3rd party message if I force close Greenify or if I reboot. In those cases Accessibility will have turned itself off. After turning Accessibility back on, the message disappears but I still have apps waiting to be hibernated after seveal hours of screen-off.
After every reboot, I find that Greenify does not seem to ask SuperSU for root access. Even though I've granted Greenify automatic access,the log files for SuperSU never show Greenify as either being granted or denied rights. I know that Greenify is meant to ask for those rights when the screen is off. I guess it might be another app is locking the device when the screen is off before Greenify can ask for access. I've tried removing Device Admin privileges for other apps and remove PIN unlocks but this does not seem to help.
The only way I have managed to get Greenify running again is to uninstall and reinstall, which seems to be the only way when the screen is on that I can get it to request root access via SuperSU. This does mean I cannot use the Xposed installer options, because I would first need to reinstall Greenify, grant it root access via SuperSU, then enable the XPosed module, then reboot. But after reboot SuperSU access seems to be withdrawn and I can't get it to request root unless I uninstall and reinstall.
I'm sure I'm missing something but I'm not sure what. I am not sure if there is a way of forcing Greenify to request SuperSU access even when the screen is on without having to reinstall.
I am rooted with SuperSU 2.4 and Xposed installer, HTC One on Viper 7.02 ROM, Greenify 2.5.1 with donation package.
EDIT: I've found that I can get Greenify to ask for Root Access through Xposed if I first degreenify Facebook, re-greenify Facebook, launch another app which wakes up Facebook (eg Agoda) and then request Greenify to cut-off the wake-up. Seems to be working.
EDIT2: Alas, still having problems. Usually nothing auto-hibernates after charging the phone. Yesterday it was working fine, today I unplugged, started some apps, closed the phone and went for breakfast. 1.5 hours later the apps were still waiting to hibernate. Am completely lost on what to do next.
Dronak said:
I seem to have this same problem, but I don't think it's easily repeatable, which makes it hard to narrow down a possible cause. I have a Samsung Galaxy Note 3 running Android 4.4.4 but it's not rooted, so the other posts here (which I think all involve root) don't seem to apply in my case. Is there a possible known cause and/or solution for this problem of auto-hibernation stopping on unrooted devices? Thanks for your help!
Click to expand...
Click to collapse
I occasionally get this message, generally after an update to Greenify, but just tap on the message and continue on with my day. After exhaustive (I'm rather OCD) research, the general consensus is to forget about it as it is just Greenify's way of letting you know that the auto-hibernation has stopped and needs to be restarted. I have gone without tapping on that message and the service still starts up all by itself.
My advice is to open Greenify after an update (updates have slowed considerably anyway) and just tap on the message and it will be good to go until the next update.
Thanks for the response. I have been tapping on the message when I notice it, but it still seems to appear without updates to Greenify. I've tried checking a little more, though probably not as exhaustively as you did, and I suspect that there's some kind of conflict with Tasker. One of the main things I do with Tasker is alternate between "home" and "work" modes, part of which involves using a screen lock for "work" and turning it off for "home". It seems like when things are working fine at home, I go to work making it switch to work mode, and return home at the end of the day going back into home mode, Greenify complains. Since Greenify only works without a screen lock in non-root mode, I'm guessing this switching may be affecting thing, but I'm not completely sure. I guess I just have to live with it. One thing I've tried doing to mitigate the problem is add a Greenify hibernate action to my Tasker profile for turning mobile data off when the screen goes off. I'm not sure how well it's working, because at work I normally hibernate manually and at home I often don't worry about it, but even if it's not working, I think I get a placebo effect of thinking it's doing *something* so I'm less concerned about checking to see if Greenify has stopped auto-hibernating.
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
peste19 said:
So i have my tmobile edge for a couple of days now and im not really impressed with the battery life so i installed greenify however its not showing me all the bloatware that came preinstalled, anyone else having these issues?
Click to expand...
Click to collapse
Do you have experimental mode enabled? I think you need the donation pack as well as root to greenify system apps.
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Has anyone noticed some improvements using greenify with s6?
peste19 said:
didnt know about that, i tried going to experimental features and you are right donation package is needed however it says xposed is needed also, is xposed compatible with s6 edge? afraid of installing stuff to brick my device. I was trying to avoid rooting it for now since i see alot of people are bricking their devices, waiting for a fix.
Click to expand...
Click to collapse
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
isangelous said:
You don't need Xposed to greenify system apps. There are some other features in the experimental section that it enables, but you don't need them. (And you are right that xposed is not compatible with the edge).
However, if you are not rooted the System freezing doesn't work very well in my experience. It freezes them but they often start running again on their own. Thus you wind up with it trying to close them all down each time you turn off the phone. You might be better off disabling what apps you can manually instead.
Overall I didn't find Greenify to be great when not rooted - sometimes it gets stuck pressing the keys to force close the apps. The best way I found was to use tasker to trigger the hibernation when the phone has been idle for ~10minutes, but it was still a bit iffy.
It will probably be good enough to get you by for now if you think you will root later, but I am not sure I would bother if you probably won't ever root.
Click to expand...
Click to collapse
how did you use tasker to enable the hibernation? i am a bit new at this
peste19 said:
how did you use tasker to enable the hibernation? i am a bit new at this
Click to expand...
Click to collapse
I just had a look but unfortunately I don't have the profile anymore to export it for you.
Doing it from scratch would be a bit daunting if you have never used Tasker before.
You basically need to:
1. Set a variable for the display state (ie, on, off and unlocked). %DisplayState
2. Have a task for the screen unlock which sets a variable %NeedToGreenify or similar.
3. Have a task for the when screen off event triggers and %NeedToGreenify is set. This task waits 10 minutes. Then check if the screen is still off - this is what %DisplayState is for (Stop if it is not). Clear %NeedToGreenify. Trigger Hibernate (Greenify is a 3rd Party Plugin). Wait 30 seconds. Turn the screen off "SecureSettings - LockDevice".
I think I may have also used SecureSettings to keep the screen on while the process is running. You will also need to set the task options to "abort existing task" if it is already running.
I think this is how it worked, but it was a while ago :/
Hi all!
I have been tinkering with Magisk etc lately and was wondering about something. If I install a random apk that I find somewhere, grant it superuser, use it a bit, and then decide I'm not convinced it's safe, does going back and denying superuser effectively disable it and prevent it from taking any actions?
Shoruk3n said:
Hi all!
I have been tinkering with Magisk etc lately and was wondering about something. If I install a random apk that I find somewhere, grant it superuser, use it a bit, and then decide I'm not convinced it's safe, does going back and denying superuser effectively disable it and prevent it from taking any actions?
Click to expand...
Click to collapse
All the actions performed by it earlier will not be affected but it will not be allowed to carry any activity further!