This seems simple enough and I though a quick search would set me straight, but I can't seem to find the answer to this.
Is there a way to prevent data access for individual apps? (both WiFi and 3/4G)
Essentially, I'm trying to block internet access for certain apps while the rest on the device is connected.
I'm running CM10.2 on a GS3.
Thanks in advance.
fua1 said:
This seems simple enough and I though a quick search would set me straight, but I can't seem to find the answer to this.
Is there a way to prevent data access for individual apps? (both WiFi and 3/4G)
Essentially, I'm trying to block internet access for certain apps while the rest on the device is connected.
I'm running CM10.2 on a GS3.
Thanks in advance.
Click to expand...
Click to collapse
You'll need to install the Xposed framework from here http://forum.xda-developers.com/show...php?p=24267797
After you have it installed, reboot so that the framework applies.
Then grab Xprivacy from here, http://forum.xda-developers.com/showthread.php?t=2320783
Install Xprivacy then go back to the framework, it is installed as an app, select modules, enable Xprivacy, reboot the phone.
After your phone is done rebooting, open Xprivacy from the app drawer, it may ask for root, allow it, Find your app, Disable it's data connectivity, Annnnnnd profit? Cheers!
Critical Detox said:
You'll need to install the Xposed framework from here http://forum.xda-developers.com/show...php?p=24267797
After you have it installed, reboot so that the framework applies.
Then grab Xprivacy from here, http://forum.xda-developers.com/showthread.php?t=2320783
Install Xprivacy then go back to the framework, it is installed as an app, select modules, enable Xprivacy, reboot the phone.
After your phone is done rebooting, open Xprivacy from the app drawer, it may ask for root, allow it, Find your app, Disable it's data connectivity, Annnnnnd profit? Cheers!
Click to expand...
Click to collapse
Profit, you say? Straight to phase three, eh?
I was really hoping there'd be a setting somewhere I'm just not aware of. Didn't wanna have to mess with frameworks and such
Thanks for the help.
Just grab a firewall app. This way you can prevent what ever app you want from getting access. Xposed can cause issues depending on your set up.
Bat cave One
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.
It's actually working when it comes to manually hibernating the apps but it won't automatically hibernate apps when on sleep no matter how long it was. Any workaround for this or is there something that I've missed? It was working fine when I was still on my rooted KK.
My phone is Xperia z3 Compact (D5833).
dane_xperia said:
It's actually working when it comes to manually hibernating the apps but it won't automatically hibernate apps when on sleep no matter how long it was. Any workaround for this or is there something that I've missed? It was working fine when I was still on my rooted KK.
My phone is Xperia z3 Compact (D5833).
Click to expand...
Click to collapse
I also sometimes have this but only with system apps. Third party apps have no issue.
From observing the SuperSU logs, I find that Greenify fired and closed the apps but when you open Greenify, they will be shown as running the whole time. May be it is an issue with how they are reported when you open Greenify.
I am running Greenify in Boost mode with official Xposed and donation pack on 5.0.1 in a Nexus 4.
tnsmani said:
I also sometimes have this but only with system apps. Third party apps have no issue.
From observing the SuperSU logs, I find that Greenify fired and closed the apps but when you open Greenify, they will be shown as running the whole time. May be it is an issue with how they are reported when you open Greenify.
I am running Greenify in Boost mode with official Xposed and donation pack on 5.0.1 in a Nexus 4.
Click to expand...
Click to collapse
Well in my case, I opened Clash of clans, closed it, then put my phone to sleep for 30mins. I did not remove it from the running services tab/ nor did I hibernate it. I went back to see if it was hibernated automatically but it wasn't and I also checked SuperSU, it did not show anything with regards to greenify.
Hi all,
I'm using my S7e with nougat and there is no xposed yet here.
Can someone share how it works this app without using xposed mode? Is this still being so useful in Nougat and without xposed?
Thanks!
yamwt said:
Hi all,
I'm using my S7e with nougat and there is no xposed yet here.
Can someone share how it works this app without using xposed mode? Is this still being so useful in Nougat and without xposed?
Thanks!
Click to expand...
Click to collapse
Install recent builds as a system app to enable 'privilaged' mode which yields functionality similar to Boost + Xposed. Great for Nougat.
Davey126 said:
Install recent builds as a system app to enable 'privilaged' mode which yields functionality similar to Boost + Xposed. Great for Nougat.
Click to expand...
Click to collapse
I just enabled this on my device and under Mode it does say it's in root+privileged mode, but I can't seem to enable any of the Xposed options. am I missing something?
dimm0k said:
I just enabled this on my device and under Mode it does say it's in root+privileged mode, but I can't seem to enable any of the Xposed options. am I missing something?
Click to expand...
Click to collapse
I also converted it as a system app through TiBU but the mode stays as "rooted" perhaps because I am on Nougat.
And Xposed options can not be enabled. I think that it functions as rooted but in a better fashion. But I don't see any difference in performance between normal installation and as a system app.
EDIT: After reading on another thread that TiBU places Greenify apk in /system/app instead of /system/priv-app, I checked and found that indeed the apk was in app instead of priv-app. So used TWRP to move the apk to priv-app and rebooted. Now Greenify is functioning in root+privileged mode. Let me check the performance. (Of course still no Xposed features).
tnsmani said:
I also converted it as a system app through TiBU but the mode stays as "rooted" perhaps because I am on Nougat.
And Xposed options can not be enabled. I think that it functions as rooted but in a better fashion. But I don't see any difference in performance between normal installation and as a system app.
EDIT: After reading on another thread that TiBU places Greenify apk in /system/app instead of /system/priv-app, I checked and found that indeed the apk was in app instead of priv-app. So used TWRP to move the apk to priv-app and rebooted. Now Greenify is functioning in root+privileged mode. Let me check the performance. (Of course still no Xposed features).
Click to expand...
Click to collapse
ahh, thanks for the confirm... I haven't really noticed anything different either since the change, but let me know if you do. I was hoping privileged mode would give some of the Xposed options, but thanks for confirming
dimm0k said:
I just enabled this on my device and under Mode it does say it's in root+privileged mode, but I can't seem to enable any of the Xposed options. am I missing something?
Click to expand...
Click to collapse
tnsmani said:
I also converted it as a system app through TiBU but the mode stays as "rooted" perhaps because I am on Nougat.
And Xposed options can not be enabled. I think that it functions as rooted but in a better fashion. But I don't see any difference in performance between normal installation and as a system app.
EDIT: After reading on another thread that TiBU places Greenify apk in /system/app instead of /system/priv-app, I checked and found that indeed the apk was in app instead of priv-app. So used TWRP to move the apk to priv-app and rebooted. Now Greenify is functioning in root+privileged mode. Let me check the performance. (Of course still no Xposed features).
Click to expand...
Click to collapse
Curious if you have Xposed functionality on any non-nougat ROMs associated with the Google account being used (ie: paid upgrade)?
Davey126 said:
Curious if you have Xposed functionality on any non-nougat ROMs associated with the Google account being used (ie: paid upgrade)?
Click to expand...
Click to collapse
if I understand correctly, I had a non-Nougat phone prior to this current phone that has Xposed and has Greenify donation key installed on it... why do you ask? that phone is no longer alive/used anymore
dimm0k said:
if I understand correctly, I had a non-Nougat phone prior to this current phone that has Xposed and has Greenify donation key installed on it... why do you ask? that phone is no longer alive/used anymore
Click to expand...
Click to collapse
Sorry - didn't phrase question well. Was asking if you had the paid version of Greenify (donation key). Was hoping that might explain lack of access to Xposed functionality when running in privileged mode.
Davey126 said:
Sorry - didn't phrase question well. Was asking if you had the paid version of Greenify (donation key). Was hoping that might explain lack of access to Xposed functionality when running in privileged mode.
Click to expand...
Click to collapse
ahh, yes, I do have the donation key installed...
Davey126 said:
Sorry - didn't phrase question well. Was asking if you had the paid version of Greenify (donation key). Was hoping that might explain lack of access to Xposed functionality when running in privileged mode.
Click to expand...
Click to collapse
Yes, I also have the donation package installed. Are you running Nougat? Do you get the Xposed options?
Though on opening Greenify I don't find any difference, I find that the phone sleeps better and the drain during idle has come down after moving Greenify to priv-apps.
tnsmani said:
Yes, I also have the donation package installed. Are you running Nougat? Do you get the Xposed options?
Though on opening Greenify I don't find any difference, I find that the phone sleeps better and the drain during idle has come down after moving Greenify to priv-apps.
Click to expand...
Click to collapse
Well - I speak in half truths. Nougat is installed on a test device. Migrated Greenify to a system app a few weeks ago. Verified it was running in 'Root + Privileged' mode and quickly checked access to Xposed-based features which popped up as expected. But (a huge but...) never attempted to enable any as it was a test device and didn't immediately need the extended functionality. You can guess the rest...can't enable any of the Xposed options...just like everyone else. I hang my head in shame for not throughly testing.
Small positive: Privileged works similarly to Boost w.r.t the speed of hibernation. Probably some other goodies too. Not ready to jump over to Nougat in my daily driver due to other Xposed dependencies. So really not in a good position to give Privileged mode a through assessment.
The Greenify app (root mode) identified a particular Broadcast Receiver, the "PackageMonitorReceiver$RegisteredReceiver", that wakes up the Play Store whenever certain apps are booted on certain occasions. I applied the cutoff, but the Play Store still pops up in Greenify every time I start up my VPN app, not only ignoring the cutoff but apparently ignoring the fact that the app has been run multiple times (the Intents are package_added, package_removed, package_changed, package_first_launch, and external_applications_(un)available; I'm not sure which one it might be reacting to).
I do not even have to activate the VPN service for this to occur, only launch the app. For other apps, the Play Store will run in the background on the first bootup but will stop afterwards. Both brand new apps and this VPN app will still cause the Play Store to reenable its Receiver service (which I disabled in MyAndroidTools only to see it reactivate itself each time I use another app) and ignore Greenify's path cutoff despite the cutoff still being active and recognized within the client: Greenify shows that the VPN app is what woke the Play Store up and that the wakeup path has already been cut off. This may not be a Greenify "problem" but it might be worth mentioning that the cutoff isn't being honored.
animeme said:
The Greenify app (root mode) identified a particular Broadcast Receiver, the "PackageMonitorReceiver$RegisteredReceiver", that wakes up the Play Store whenever certain apps are booted on certain occasions. I applied the cutoff, but the Play Store still pops up in Greenify every time I start up my VPN app, not only ignoring the cutoff but apparently ignoring the fact that the app has been run multiple times (the Intents are package_added, package_removed, package_changed, package_first_launch, and external_applications_(un)available; I'm not sure which one it might be reacting to).
I do not even have to activate the VPN service for this to occur, only launch the app. For other apps, the Play Store will run in the background on the first bootup but will stop afterwards. Both brand new apps and this VPN app will still cause the Play Store to reenable its Receiver service (which I disabled in MyAndroidTools only to see it reactivate itself each time I use another app) and ignore Greenify's path cutoff despite the cutoff still being active and recognized within the client: Greenify shows that the VPN app is what woke the Play Store up and that the wakeup path has already been cut off. This may not be a Greenify "problem" but it might be worth mentioning that the cutoff isn't being honored.
Click to expand...
Click to collapse
If you have Xposed Framework installed try the MyAndroidTools module which attempts to address this behavior.
Davey126 said:
If you have Xposed Framework installed try the MyAndroidTools module which attempts to address this behavior.
Click to expand...
Click to collapse
Don't have Xposed, unfortunately. If possible, I'd like to avoid it anyway
animeme said:
Don't have Xposed, unfortunately. If possible, I'd like to avoid it anyway
Click to expand...
Click to collapse
Understand, but recognize w/o Xposed you loose access to more advanced tools and methods - including those utilized by Greenify that are not entirely contained to user selectable Xposed features.
Davey126 said:
Understand, but recognize w/o Xposed you loose access to more advanced tools and methods - including those utilized by Greenify that are not entirely contained to user selectable Xposed features.
Click to expand...
Click to collapse
Yea, it seems Deep Hibernation was required. Unfortunate since I had just gotten safetynet working with microg. Oh well, thanks for the bad news :silly: