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.
Related
SuperUser won't allow me to allow an app root access, any app I try, SuperSU, Hotspot shield, anything. In the past it worked just fine allowing Titanium and still works for apps I have already allowed, but it won't let me hit the allow button when an app asks for root access. No matter what I keep tapping it and nothing happens, either I tap cancel or it times out. And I am on CyanogenMod 11 nightlies.
This doesn't help your issue but don't use hotspot shield it logs what you do.
Willielikesmonkeys said:
SuperUser won't allow me to allow an app root access, any app I try, SuperSU, Hotspot shield, anything. In the past it worked just fine allowing Titanium and still works for apps I have already allowed, but it won't let me hit the allow button when an app asks for root access. No matter what I keep tapping it and nothing happens, either I tap cancel or it times out. And I am on CyanogenMod 11 nightlies.
Click to expand...
Click to collapse
There is some app overlaying on the screen and superuser is strict about.
Most likely is lux unless they fixed it recently. Try uninstalling that and any other apps that affect the display.
crpalmer said:
There is some app overlaying on the screen and superuser is strict about.
Most likely is lux unless they fixed it recently. Try uninstalling that and any other apps that affect the display.
Click to expand...
Click to collapse
Thank you!!!!
This worked. How did you find this out?
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.
Since I rooted my phone I would sometimes, about once every two weeks get a root request from the phone application. I'd deny it, it was very occasional and I honestly didn't mind.
Two days ago, the System UI application started to request root, which I also denied and let it go. The thing is that it started to request it VERY frequently, to the point that it's flooding Super SU logs (~1 request per second), it would crash Super SU's logs. I tried upgrading to the pro version to see if the logs would show something else but it just show the many attempts but nothing else to go on with.
I'm running stock 4.4.2, 3.23.401.1 and the biggest mod is Xposed with Sense 6 Toolbox and AppsOps Xposed. I've been using those for quite some time so I doubt that's the problem.
Normally I'd just let this go but, it's starting to worry me for a bit, but this is the first phone that I owned that has system apps prompting for root access. And I'm quite sure this is impacting battery life.
What can I do to investigate why it's requesting root and what to do to stop it? Giving it the green light even though it's a system app is not a good idea, right?
Thank you.
Bumping this as I am having the same issue.
Why don't you want to give SystemUI SU permission? Doesn't it HAVE to have it to allow Xposed Framework to work properly? I'm mystified.
Alright I just bought the donation package for Greenify (latest) but the auto-hibernate option is gone now. I tried to disable every module, reinstall root, reinstall greenify, clear cache, edit the settings (Security and accessibility) but still no luck. I don't have the yellow message that shows up when something is wrong with the auto-hibernation. All I can see is "will hibernate in minutes after screen is off" but the apps are still working in stand by and aren't hibernated. The only way that the apps are hibernated is using the Hibernate + Lock screen shortcut.
@DavidMKD:
You are using it in root or boost mode? Does Supersu show Greenify in its logs?
Update/reinstall Supersu.
tnsmani said:
@DavidMKD:
You are using it in root or boost mode? Does Supersu show Greenify in its logs?
Update/reinstall Supersu.
Click to expand...
Click to collapse
Boost mode. Yes it's shown and as I stated in the OP i did reinstall SU
DavidMKD said:
Boost mode. Yes it's shown and as I stated in the OP i did reinstall SU
Click to expand...
Click to collapse
You are running Supersu and not SuperUser? Normally this happens if granting root permission is somehow ****ed up. So are you sure Greenify was specifically granted root priveleges?
How long did you wait after screen off to check? Sometimes it takes 3 to 5 minutes for autohibernation.
tnsmani said:
You are running Supersu and not SuperUser? Normally this happens if granting root permission is somehow ****ed up. So are you sure Greenify was specifically granted root priveleges?
How long did you wait after screen off to check? Sometimes it takes 3 to 5 minutes for autohibernation.
Click to expand...
Click to collapse
That was one of my questions here how long does it take and why isn't instant like the shortcut that the app has. It's SuperSU and i was just removing and flashing and what not so that's not the problem. Stamina mode is disable every other module is disable but still doesn't hibernate as it should. I even set the default permission in SuperSU to granted without pompit
DavidMKD said:
That was one of my questions here how long does it take and why isn't instant like the shortcut that the app has.
Click to expand...
Click to collapse
It is intentionally set to hibernate after a short delay so that if you had second thoughts after screen off and wanted to work on an app already running, it won't consume much battery or time. Atleast this is what the Dev said earlier.
I have no other ideas for your issue, sorry.
We have some Note 4X Phones in use. Generally, we are satisfied. But this daily and recurrent notification, which is showing in the status bar (in the drop down notifications), is not acceptable.
Of course, we have disabled all settings in the Updater App, which are possible for disabling.
As long as the 8.5.8.0 is not as good as the 8.2.10.0, and as long the 8.5.8.0 has bugs, we are not able to update. Therefore it is no solution to do what the Updater want to do. Also all solutions which require a rooting are not practicable, because due security reasons, rooting is not allowed.
Try this, go to settings>apps>Updater>Show notification and disable all possible
xire68 said:
Try this, go to settings>apps>Updater>Show notification and disable all possible
Click to expand...
Click to collapse
Sorry, but as I wrote above: "...Of course, we have disabled all settings in the Updater App, which are possible for disabling..."
mi_eu said:
Sorry, but as I wrote above: "...Of course, we have disabled all settings in the Updater App, which are possible for disabling..."
Click to expand...
Click to collapse
Ah ok sorry I did not read, then try disabling the data network momentarily, then in the update settings, deselect auto update, then go to the applications and empty the updater cache.
Sorry for my bad english.
read carefully disable notification from setting app
shamsud said:
read carefully disable notification from setting app
Click to expand...
Click to collapse
?
ALL Buttons and Switches in "Settings>Notification and Status bar>App: "Settings">" are disabled. Except the first one setting "Show Notifications", because this one is not selectable (it is faded out).
xire68 said:
Ah ok sorry I did not read, then try disabling the data network momentarily, then in the update settings, deselect auto update, then go to the applications and empty the updater cache.
Click to expand...
Click to collapse
Thank you very much for your help.
Unfortunately, I have already disabled "auto updates" in the "Updater App". But this was no improvement.
In the meantime I've tried a second setting, but also without success:
I'm here: Security App - > Data Usage - > Restrict Data Usage - > System. Here I've disabled the "Updater App".
But all Apps here are listed in the column "Mobile". Now, this means, the disabling only works during a mobile data connection. Therefore, the disabling will not valid during a WLAN session.
The second indication is, that in the following path: "Security App - > Data Usage - > Restrict Data Usage" there exists not only the menu "System". The second selectable menu here is "Installed". Under the menu "Installed" there are listed many apps. And here are exists two different columns. One column is called "WLAN", the other column is called "Mobile". And all apps are listed in both columns. The reason is that the users have the choice to restrict data either for "WLAN" or for "Mobile".
But the bad thing is that in the menu "System" there only exists the column "Mobile".
Now, how can I restrict the data for the Security App also for a WLAN connection?
But as I described above, anyway this solution also doesn't work - if anything, than only with a mobile connection.
But principally, the aim isn't to restrict data, the goal is how to avoid the notification of that stupid "Updater App"?
Has anyone a working solution for me?
mi_eu said:
Thank you very much for your help.
Unfortunately, I have already disabled "auto updates" in the "Updater App". But this was no improvement.
In the meantime I've tried a second setting, but also without success:
I'm here: Security App - > Data Usage - > Restrict Data Usage - > System. Here I've disabled the "Updater App".
But all Apps here are listed in the column "Mobile". Now, this means, the disabling only works during a mobile data connection. Therefore, the disabling will not valid during a WLAN session.
The second indication is, that in the following path: "Security App - > Data Usage - > Restrict Data Usage" there exists not only the menu "System". The second selectable menu here is "Installed". Under the menu "Installed" there are listed many apps. And here are exists two different columns. One column is called "WLAN", the other column is called "Mobile". And all apps are listed in both columns. The reason is that the users have the choice to restrict data either for "WLAN" or for "Mobile".
But the bad thing is that in the menu "System" there only exists the column "Mobile".
Now, how can I restrict the data for the Security App also for a WLAN connection?
But as I described above, anyway this solution also doesn't work - if anything, than only with a mobile connection.
But principally, the aim isn't to restrict data, the goal is how to avoid the notification of that stupid "Updater App"?
Has anyone a working solution for me?
Click to expand...
Click to collapse
Were you able to find any solution? I am facing this exact issue and it's really infuriating
Force stop the app and dismiss the notification
And don't open the update settings again
You could try disabling the Updater application with ADB.
Get ADB & fastboot here from XDA from this link, install it on a computer.
Then, enable Developer options. Go to Settings -> About device and tap MIUI version a few times until it says they've been enabled.
Now go to Settings -> Additional Settings -> Developer options and enable USB debugging.
Connect the phone to the computer, type 'adb devices' without the quotation marks and make sure the phone is detected. The phone will pop up a notice to confirm you trust the computer.
Now, type 'pm uninstall -k --user 0 com.android.updater' without the quotation marks. This will disable the built-in Updater app, removing any notifications coming from it.
This does not require root.
Just use Titanium Backup and freeze Updater app.
It will not show anything until you run it manually, or you restart phone.
Muzam said:
Force stop the app and dismiss the notification
And don't open the update settings again
Click to expand...
Click to collapse
This is the best solution, it helped me.
You can map your back button with long press to force close any app. If you mapped it, just open updater and long press the back button. It will close updater app and dismiss its notification. It will only come up again if you manually open the Updater app again and search for updates.
Also its not necessary to map the nav keys
Just hold the app window from recent apps view to get app info and hit force close button at bottom.
any one tried xezrunner's solution? any good? I hate this notification crap that mi has foisted on all of us.
k3lcior said:
Just use Titanium Backup and freeze Updater app.
It will not show anything until you run it manually, or you restart phone.
Click to expand...
Click to collapse
On my phone, the 3Gb Global Version, some MiUi app can't be frozen, including updater.apk (MiUi 9.2.1.0).
Coming back to this topic, I made a backup of the aforementioned apk with Titanium. Would it be safe to uninstall it completely or should I go the ADB route? I'm asking because the case happened to me once with another phone where the system wouldn't be the same despite the backup-restore by Titanium.
d8v8n8 said:
On my phone, the 3Gb Global Version, some MiUi app can't be frozen, including updater.apk (MiUi 9.2.1.0).
Coming back to this topic, I made a backup of the aforementioned apk with Titanium. Would it be safe to uninstall it completely or should I go the ADB route? I'm asking because the case happened to me once with another phone where the system wouldn't be the same despite the backup-restore by Titanium.
Click to expand...
Click to collapse
You could uninstall but make sure to backup it first in case you run into some issues, personally i'd just freeze it. (it will appear as uninstalled until phone restart)
k3lcior said:
You could uninstall but make sure to backup it first in case you run into some issues, personally i'd just freeze it. (it will appear as uninstalled until phone restart)
Click to expand...
Click to collapse
When I click freeze in Titanium, nothing happens, the app isn't marked as frozen and stays available. I tried to freeze with other apps as well but always ended up with the same unsuccessful result.
d8v8n8 said:
When I click freeze in Titanium, nothing happens, the app isn't marked as frozen and stays available. I tried to freeze with other apps as well but always ended up with the same unsuccessful result.
Click to expand...
Click to collapse
It wont run unless you run it yourself which unfreezes it. Dont tell me it doesn't work because i do it all the time and no updates show up.
d8v8n8 said:
When I click freeze in Titanium, nothing happens, the app isn't marked as frozen and stays available. I tried to freeze with other apps as well but always ended up with the same unsuccessful result.
Click to expand...
Click to collapse
correct me if im worng, titanium backup freezing function only works if you have paid version.
Maybe you don't have that.
try it with some other app like Lucky Patcher, that app isn't primarily for freezing aplication but it have option under tools to freeze packages. Just be careful to not play around with other tools if don't know what it used for.
xezrunner said:
You could try disabling the Updater application with ADB.
Get ADB & fastboot here from XDA from this link, install it on a computer.
Then, enable Developer options. Go to Settings -> About device and tap MIUI version a few times until it says they've been enabled.
Now go to Settings -> Additional Settings -> Developer options and enable USB debugging.
Connect the phone to the computer, type 'adb devices' without the quotation marks and make sure the phone is detected. The phone will pop up a notice to confirm you trust the computer.
Now, type 'pm uninstall -k --user 0 com.android.updater' without the quotation marks. This will disable the built-in Updater app, removing any notifications coming from it.
This does not require root.
Click to expand...
Click to collapse
Sorry if it were out of topic, but I'm wondering whether it is possible or not to edit the build.prop (for gcam} through adb on non UBL and non ROOT Redmi Note 4