Bug Hello, I had instal greenify beta 3 and buy the donation version, I have a Samsung S5 ( G900F) with Android 4.4.2,I had instal wsm tools, it is the xposed , when I want to enable experimental settings the application said me to buy the donation version who is installed...
I'm getting this too now... help! Not sure when it started happening, but definitely with the latest beta! Samsung Galaxy S4 with 4.4.2
---------- Post added at 08:55 PM ---------- Previous post was at 08:44 PM ----------
@oasisfeng this is happening even though I purchased both Greenify and donation package from Google Play... a long time ago!
There is nothing wrong with beta3. It is working alright for me.
Check if you have Lucky Patcher.
If not, uncheck Greenify from Device Administrator and Xposed and uninstall both Greenify and donation pack.
Reboot. First install donation pack, then Greenify and enable in Device Administrator, Accessibility and Xposed and reboot.
It should work now.
it works with lucky patcher !
Damage to crack an application that I bought !
a quick update !
The problem is Lucky Patcher. Open it > tools > disable 2nd and 3rd options. Close it. Now Greenify will work fine with donation package
konqueror said:
The problem is Lucky Patcher. Open it > tools > disable 2nd and 3rd options. Close it. Now Greenify will work fine with donation package
Click to expand...
Click to collapse
That's the solution thanks man !
No change to get donation working. I unchecked and uninstalled both for more then one times and after reboot, checked in xposed and reboot, after that starting greenify and it says "Thank you for donation...". In "About Greenify" it says "Thank you for your donation". But if I want to set experimental features, there is an issue "donation couldnt be verified check your connection or try later".
I have no lucky patcher and I tried definitely with (working) WLAN and mobile connection (all other Apps have access to internet)...
Have v2.5.beta4 (also on 2 other devices with no problems)...
Did you cut off the links of Playstore for IAP?
Paid apps check the payment status with Playstore every time the paid features are invoked. It seems that Greenify is not able to do that check in your case. It may be a problem with your Playstore if you had meddled with it before.
To cross check, try accessing the paid feature of any other app you have. If you get the same result, then you have a broken Playstore.
tnsmani said:
Did you cut off the links of Playstore for IAP?
.
Click to expand...
Click to collapse
Yes, you were right. I had cut off IAP from PlayStore, cause my Launcher starts it all the time... :good:
After restoring IAP to PlayStore, Greenify Donation Check works fine ... Thanks for the help!
Bogeyof said:
Yes, you were right. I had cut off IAP from PlayStore, cause my Launcher starts it all the time... :good:
After restoring IAP to PlayStore, Greenify Donation Check works fine ... Thanks for the help!
Click to expand...
Click to collapse
Good to hear.
Instead of cutting off the link, try to greenify the Playstore ignoring its state so that it will run only when the screen is on.
tnsmani said:
There is nothing wrong with beta3. It is working alright for me.
Check if you have Lucky Patcher.
If not, uncheck Greenify from Device Administrator and Xposed and uninstall both Greenify and donation pack.
Reboot. First install donation pack, then Greenify and enable in Device Administrator, Accessibility and Xposed and reboot.
It should work now.
Click to expand...
Click to collapse
the problem is that i bought it from amazon app store. and it does not provide any donation package app.
Bogeyof said:
No change to get donation working. I unchecked and uninstalled both for more then one times and after reboot, checked in xposed and reboot, after that starting greenify and it says "Thank you for donation...". In "About Greenify" it says "Thank you for your donation". But if I want to set experimental features, there is an issue "donation couldnt be verified check your connection or try later".
I have no lucky patcher and I tried definitely with (working) WLAN and mobile connection (all other Apps have access to internet)...
Have v2.5.beta4 (also on 2 other devices with no problems)...
Click to expand...
Click to collapse
hi, new to this thread -
ends up i had lucky patcher installed (backed up/restored from many old nandroids = also decided that it was time to pay the dev's BTW!) so removed it and was able to get my Donation Package working, to a certain point - don't have any widgets such as my "greenify now" button. i haven't messed with google play or such, any hints?
not sure what AIP is? Thought I was android literate but not sure now:
Did you cut off the links of Playstore for IAP?
Click to expand...
Click to collapse
.
Yes, you were right. I had cut off IAP from PlayStore, cause my Launcher starts it all the time...
After restoring IAP to PlayStore, Greenify Donation Check works fine ... Thanks for the help
Click to expand...
Click to collapse
The dev has not replied to me concerning this so looking for help: BTW running HyperDrive RLS19, GS4, MK2, etc.
Lucky has been removed, rebooted, and will never be used again for now (not necessarily against it for trial use, but am against it for continued use - just my personal opinion, the same for pc use).
EDIT: yeah, I F'ed up. Searched for a shortcut instead of a widget and found the "hybernate now" button. Just happy I was able to fix the Experimental features issue... and in the long run only from your help/reading the thread. I just love xda.
thanks.
mkoyskip said:
not sure what AIP is? Thought I was android literate but not sure now:
Click to expand...
Click to collapse
Not AIP.
IAP=in app billing
Related
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.
I am just wondering if anyone else is having problems with notifications disappearing upon hibernation with xposed 5.1. I have everything set right in experimental settings, I've been using this so for years so I know how to set it properly☺. Just wondering if I am the only one because I am about to loose my mind!! I've tried everything, installing uninstalling downgrading upgrading, I've spent hours on it, just thought I'd ask before giving up. Running in boost mode with donation package. Thanks
Sent from my GT-P5110 using Tapatalk
Shepguessed said:
I am just wondering if anyone else is having problems with notifications disappearing upon hibernation with xposed 5.1.
Sent from my GT-P5110 using Tapatalk
Click to expand...
Click to collapse
Try the Xposed version of the GB Dev available in the super alpha Xposed thread. Also use beta 3 of Greenify with that. This combination is reported to be working.
Another alternative is to disable deep hibernation in Greenify.
tnsmani said:
Try the Xposed version of the GB Dev available in the super alpha Xposed thread. Also use beta 3 of Greenify with that. This combination is reported to be working.
Another alternative is to disable deep hibernation in Greenify.
Click to expand...
Click to collapse
I am guessing he's using that version of Xposed. But yeah this problem is there.
ottomanrage said:
I am guessing he's using that version of Xposed. But yeah this problem is there.
Click to expand...
Click to collapse
Yes I have tried every possible combo, litterally spent hours on it. I am just wondering if it is my problem only or are other people having this problem? I would love to know!
Sent from my GT-P5110 using Tapatalk
Hi guys. I'm on the same boat.
CM12.1, Greenify 2.6.2b5, xposed super alpha and no notifications kept after auto-hibernate for whatsapp, hangouts and skype.
I've only installed xposed again, and greenify module etc, and notifications only affect Facebook, but just noticed by just noticed that they're snoozing too.
I have the same issue, notifications come in, but then they disappear. I have all the required options checked, using alpha 4 xposed + b5 greenify.
Yes, i have this too. All notifications are gone after re-greenify.
---------- Post added at 07:01 PM ---------- Previous post was at 06:38 PM ----------
I may have accidentally found a solution. deleted beta 5(back up in titanium backup first) , reboot, reinstalled beta 4, reboot, restore beta 5. seems to be working for me now. not quite sure why.
davtse said:
I may have accidentally found a solution. deleted beta 5(back up in titanium backup first) , reboot, reinstalled beta 4, reboot, restore beta 5. seems to be working for me now. not quite sure why.
Click to expand...
Click to collapse
Did you activate the xposed module after b4 installation? When you restored b5 using TiBu, did you choose app, data or app+data? For me, your solution doesn't work.
christiano88 said:
Did you activate the xposed module after b4 installation? When you restored b5 using TiBu, did you choose app, data or app+data? For me, your solution doesn't work.
Click to expand...
Click to collapse
yes activated after b4 installation. after that i just restored app+data for b5. alternatively try to enable notification access for greenify as well. might have been a step i missed but its still working for me.
davtse said:
yes activated after b4 installation. after that i just restored app+data for b5. alternatively try to enable notification access for greenify as well. might have been a step i missed but its still working for me.
Click to expand...
Click to collapse
I do not have Greenify under Notification access.
christiano88 said:
I do not have Greenify under Notification access.
Click to expand...
Click to collapse
weird... i do though. see attached picture. i'm on 5.1.1 slimpop
Beta 6 is up, it doesn't address this issue. I tried reinstalling from scratch, greenify appeared in notification access, but as soon as I activated "Keep notifications" (root non-limited one) under greenify, it disappeared from the notification access. @davtse can you please post a screenshot of your greenify settings?
L.E.: I've pretty much figured it out after reinstalling greenify multiple times and trying with different settings. This is what happens:
- Activating the xposed module makes the "Keep notifications (Limited)" disappear from Greenify options, so I went on and activated it before activating the xposed module and restarting the phone. Also make sure to activate Greenify under notification access option in phone settings.
- Even if "Keep notifications (Limited)" doesn't show anymore, if you managed to activate it before activating the xposed module, it will be kept active.
- If you activate "Keep notifications" (the non-limited one), it will cancel the Limited one, and it won't work, and it also makes Greenify disappear from the notification access menu.
These are my findings.
The good part is that I made it work this way, but the notification light goes away when the app is hibernated with a pending notification. At least, the notification stays.
christiano88 said:
Beta 6 is up, it doesn't address this issue. I tried reinstalling from scratch, greenify appeared in notification access, but as soon as I activated "Keep notifications" (root non-limited one) under greenify, it disappeared from the notification access. @davtse can you please post a screenshot of your greenify settings?
L.E.: I've pretty much figured it out after reinstalling greenify multiple times and trying with different settings. This is what happens:
- Activating the xposed module makes the "Keep notifications (Limited)" disappear from Greenify options, so I went on and activated it before activating the xposed module and restarting the phone. Also make sure to activate Greenify under notification access option in phone settings.
- Even if "Keep notifications (Limited)" doesn't show anymore, if you managed to activate it before activating the xposed module, it will be kept active.
- If you activate "Keep notifications" (the non-limited one), it will cancel the Limited one, and it won't work, and it also makes Greenify disappear from the notification access menu.
These are my findings.
The good part is that I made it work this way, but the notification light goes away when the app is hibernated with a pending notification. At least, the notification stays.
Click to expand...
Click to collapse
Glad to know that i am not alone in this I'll try your method and let you know. I don't know if there are many users in our case but in case @oasisfeng you decide to investigate on it please let us know if we can help with some kind of log or anything else. (keeping notifications after hibernation is a major feature i think)
PS : Irrelevant to the problem, but could somebody tell me difference between the root and beast mode in greenify ? (did some research on it but did not see a clear answer)
Edit : Unfortunately that did not go well at 100%, i mean that for example when i got a messenger message, the app can not go to hibernation but for facebook's notifications (e.g. friend request) after hibernation the notification goes away ... Keeping notifications is one of the best features in Greenify IMO so being broken make me :crying:
mbmb8989 said:
Edit : Unfortunately that did not go well at 100%, i mean that for example when i got a messenger message, the app can not go to hibernation but for facebook's notifications (e.g. friend request) after hibernation the notification goes away ... Keeping notifications is one of the best features in Greenify IMO so being broken make me :crying:
Click to expand...
Click to collapse
Are you sure you did exactly this?
- after installing latest version of Greenify, DO NOT REBOOT, go to settings and activate only "Do not remove notifications (Limited)".
- activate "Greenify" in Notification access from phone settings
- activate the xposed module and reboot the phone
- activate "GCM push for greenified apps".
christiano88 said:
Are you sure you did exactly this?
- after installing latest version of Greenify, DO NOT REBOOT, go to settings and activate only "Do not remove notifications (Limited)".
- activate "Greenify" in Notification access from phone settings
- activate the xposed module and reboot the phone
- activate "GCM push for greenified apps".
Click to expand...
Click to collapse
Actually, i did reboot before activating the xposed module
Just to clarify :
- In the third step, i just activate the xposed module (so i shouldn't activate any greenify feature ?) and reboot the phone ?
- In the fourth step, i activate "GCM push for greenified apps" only or among the other features ?
- Do you recommand Deep Hibernation or should i leave it off for now ?
- Concerning greenify mode, what would be more efficient in our case Boost or Root ?
Thanks again and sorry for being a pain in the arse :laugh: :laugh:
I will try again regarding your next answer and let you know how it went
Yes, you only have to activate the module. No, you can activate other features, for example, I have Deep Hibernation enabled (even though it causes some issues with accounts, and making some apps ask to re-login everytime you use them). So, I don't really recommend Deep Hibernation as it is right now, wait for more updates with fixes for it. Instead, you can check Greenify regularly to cut-off wake paths, which gets you close to having deep hibernation enabled.
Boost is the best tehnically, but I am on Root mode (personal choice).
christiano88 said:
Yes, you only have to activate the module. No, you can activate other features, for example, I have Deep Hibernation enabled (even though it causes some issues with accounts, and making some apps ask to re-login everytime you use them). So, I don't really recommend Deep Hibernation as it is right now, wait for more updates with fixes for it. Instead, you can check Greenify regularly to cut-off wake paths, which gets you close to having deep hibernation enabled.
Boost is the best tehnically, but I am on Root mode (personal choice).
Click to expand...
Click to collapse
Unfortunately that did not work :crying: I will try to go back to a previous stable version ? one you'd recommend ?
mbmb8989 said:
Unfortunately that did not work :crying: I will try to go back to a previous stable version ? one you'd recommend ?
Click to expand...
Click to collapse
Try one more time without activating other modules, just go by my steps only. If it still doesn't work, try same method with beta 5.
christiano88 said:
Try one more time without activating other modules, just go by my steps only. If it still doesn't work, try same method with beta 5.
Click to expand...
Click to collapse
I did try it with beta 3 and it worked but the notification icon is not the original one after hibernating the original app (and its the same custom icon for every app that has a pending notification and goes into hibernation).
I will try it with the beta 5. I hope that op is aware of it
Are we the only ones with this issue :crying:
This module prevents components from trying to enable themselves.
---------------------------------
We can use MyAndroidTools or MyAndroidTools Pro (you can find them in the Google Play) to disable components(service,broadcast receiver,activity,content provider).
But any app can enable their own component through an open api (setComponentEnabledSetting).
This module just prevent it.
The icon comes from Uchiha Shisui's Mangekyō Sharingan.
1. Log:record all the components that use "setComponentEnabledSetting" to enable themselves,not matter whether it is checked in the blacklist.
2. BlackList settings:select the app you want to block,then save.
--------------------------------------------
//the main source code:
Code:
XposedHelpers.findAndHookMethod("android.app.ApplicationPackageManager",
loadPackageParam.classLoader,
"setComponentEnabledSetting",
ComponentName.class, int.class, int.class,
new XC_MethodHook() {
@Override
protected void beforeHookedMethod(MethodHookParam param) throws Throwable {
if (((int) param.args[1]) == PackageManager.COMPONENT_ENABLED_STATE_ENABLED) {
param.args[1]=PackageManager.COMPONENT_ENABLED_STATE_DISABLED;
}
}
});
I love your app !!! What version do I need to be on for this to work ?
Would be nice if you explained more info in your thread ? What exactly does this do that the app already doesn't ?
does MyAndroidTools 1.2.8.7 apk need to be installed first and then this Xposed Module 0.1?
how exactly does this work? please explain in detail and also the installation procedure.
I agree with m0han. The module doesn't provide us with a user interface. So when activated through Xposed, what exactly is it doing? Do we need to download the apk from the app store? More clarification is needed before I activate this module. Thanks.
wangqi060934 said:
This module prevent components from trying to enable themselves.
Click to expand...
Click to collapse
Awesome, thank you!
Finally something to stop K9-Mail and Google Play store from starting at boot
Would you consider making the Xposed module or even MyAndroidTools open source? Xposed modules and root apps are scary and releasing the source would increase trust immensely.
I bought the pro version and I would actually buy it again or donate for an open source version. Your app and XPrivacy (open source ) make a very nice couple on any phone :laugh:
@wangqi060934, it is very cool and higly anticipated feature. Thank you!
But how does it work? How does it distinct components disabled by me with MyAndroidTools and components disabled by host app itself? And, by the way, can such components be visually distinguished in MyAndroidTools's GUI?
I don't know the nature of this facts but some apps (e.g. Gmail) indeed have services which are disabled without any manual intrusion.
Kind regards!
There is a beta2 now. I already have MyAndroidTools 0.9.8.6 installed from Play Store. I downloaded the beta through Xposed and installed it as we usually do for Xposed modules, enabled it in Xposed and rebooted.
If we go to XPOSED>modules and click on My AndroidTools, we are asked to activate the module. When we click OK, it goes back to the modules screen and if once again clicked, the UI appears. We have Log, Blacklist and Settings options at top left.
The blacklist menu gives options of third party apps and system apps and when you choose one, the apps are listed with a checkbox against their names. Till now I have experimented. After this comes the conjecture.
If we choose one or more of the apps and click the save button at top right, then that app is prevented from enabling itself unless we invoke that app ourselves. This is my understanding. I have not attempted it. I am afraid as 1. I am not an expert 2. there is no info about what this module actually does 3. it is an Xposed module 4. I won't have my laptop for some more time (in case something happens).
The settings option has only one option to show a toast when a blocking happens. The log is a log.
So if somebody else is brave enough to experiment further or if the OP explains things, I would be happy.
EDIT:
The app also appears in the app drawer and clicking it has the same effect as from Xposed.
if you do a search on xda theres more info on this app when you find it try the tenshi_xp settings.
v0.2 is not working for me, it always show me that the Module is not active even though I can see in Xposed Log it's loaded.
xk0niR said:
v0.2 is not working for me, it always show me that the Module is not active.
Click to expand...
Click to collapse
Same here.
(CM12.1 at SGS4mini I9192)
xk0niR said:
v0.2 is not working for me, it always show me that the Module is not active even though I can see in Xposed Log it's loaded.
Click to expand...
Click to collapse
There seems to be an issue with the UI. I also get the popup that the app is not active and asking me to activate it. If I activate it, the UI closes. The workaround I found is to open it from recents. Then the UI stays and you can play with it.
---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------
Kirrrr said:
Same here.
(CM12.1 at SGS4mini I9192)
Click to expand...
Click to collapse
...
wangqi060934 said:
This module prevent components from trying to enable themselves.
Click to expand...
Click to collapse
The module block massenger to connect to the network
Envoyé de mon SM-N910F en utilisant Tapatalk
Version 0.3 seems to work again.
I was wondering about the purpose of a blacklist. When I disable a service for an app with MyAndroidTools, I do not want that app to re-enable said service. Essentially this means that all apps should be activated in the blacklist in the Xposed module?
There is a version 0.6 now. Further the Dev has also furnished more info on the app in the first post.
When we reboot after enabling the app in Xposed and open the app, the log populates and shows the components which have been enabled through 'setComponentEnabledSetting'. We can then long press the component which we want to disable and choose 'blacklist'. It is then shown as blacklisted. The 'blacklist settings' shows the third party apps installed on the phone which can be selected and saved for blocking.
So find any component or third party apps which you want to block and do so. When something is chosen for blocking and it tries to enable itself, it is blocked and an entry appears in the log with its name and the time of its blocking.
If anyone finds any further info, please post the same so that we can learn.
---------- Post added at 01:52 PM ---------- Previous post was at 01:48 PM ----------
daniel_m said:
Version 0.3 seems to work again.
I was wondering about the purpose of a blacklist. When I disable a service for an app with MyAndroidTools, I do not want that app to re-enable said service. Essentially this means that all apps should be activated in the blacklist in the Xposed module?
Click to expand...
Click to collapse
No. You check the log and if you find the blocked app/component shown as started, then you add it to the blacklist.
As the Dev explains in the first post, not all disabled apps/components enable themselves. Only a few do so. You find them from the log and block them. Not all.
tnsmani said:
No. You check the log and if you find the blocked app/component shown as started, then you add it to the blacklist.
As the Dev explains in the first post, not all disabled apps/components enable themselves. Only a few do so. You find them from the log and block them. Not all.
Click to expand...
Click to collapse
Yes, I noticed. Of the 200 apps installed on my phone, only K9-Mail and Google Play Store try to re-enable some services.
The question is, does blacklisting impact performance? If not, one could simply blacklist all apps and not care about checking the log. On my ancient Sony Xperia Mini Pro, blacklisting all apps did not seem to slow down the phone noticeably.
Installed it and it worked perfectly; however I had to uninstall the module since it caused, sometimes, a bootloop. It didn't happened all the time and if I accessed to the recovery and rebooted the phone after a forced shutdown, phone booted correctly. I'm almost sure it's the module fault because since I uninstalled it the phone is working smoothly, anyway I don't know how to provide a log in order to help.
I have a Oneplus One running custom CM12.1 by Sultanxda.
Bino92 said:
Installed it and it worked perfectly; however I had to uninstall the module since it caused, sometimes, a bootloop. It didn't happened all the time and if I accessed to the recovery and rebooted the phone after a forced shutdown, phone booted correctly. I'm almost sure it's the module fault because since I uninstalled it the phone is working smoothly, anyway I don't know how to provide a log in order to help.
I have a Oneplus One running custom CM12.1 by Sultanxda.
Click to expand...
Click to collapse
Try the next version 0.7
Module fc since last version
Sent from my SM-G920F using XDA-Developers mobile app
FC on blacklist menu and still bootloop, with and without system app selection...
Bino92 said:
FC on blacklist menu and still bootloop, with and without system app selection...
Click to expand...
Click to collapse
Was also suffering with alot of bootloop, couldn't work out what app it was. Glad I found your comment
i recently updated my meizu m2 to flyme 5.1.8.0G
it has a feature that it stop all the apps that are not being used every 3 minutes .
but the problem is dat i want some apps not to be cleaned like VPN apps that works in background, It had a option to whitelist apps , But it does not work , So please suggest me some solution or some other app that can control which apps to clean and which to keep.
I am also interested in know such kind of app.
ravishru1414 said:
i recently updated my meizu m2 to flyme 5.1.8.0G
it has a feature that it stop all the apps that are not being used every 3 minutes .
but the problem is dat i want some apps not to be cleaned like VPN apps that works in background, It had a option to whitelist apps , But it does not work , So please suggest me some solution or some other app that can control which apps to clean and which to keep.
Click to expand...
Click to collapse
PulseMedicalApp said:
I am also interested in know such kind of app.
Click to expand...
Click to collapse
Hello and welcome to XDA Q&A section of the Forum.
If you have the XPosed framework installed you can downlaod and install a module called "Greenify". It lets you force close apps after not using them and put them into a mode called "hibernation". This module also has a feature that lets you pick the apps you don't want hibernating.
Hope that solves your issue and hit "thanks" if I did
RAZERZDAHACKER said:
Hello and welcome to XDA Q&A section of the Forum.
If you have the XPosed framework installed you can downlaod and install a module called "Greenify". It lets you force close apps after not using them and put them into a mode called "hibernation". This module also has a feature that lets you pick the apps you don't want hibernating.
Hope that solves your issue and hit "thanks" if I did
Click to expand...
Click to collapse
But i think it requires root, and i dont want to void warranty.
And i installed greenify app but it only does hibernation , does nt has any option to prevent some apps from auto clearing
ravishru1414 said:
But i think it requires root, and i dont want to void warranty.
And i installed greenify app but it only does hibernation , does nt has any option to prevent some apps from auto clearing
Click to expand...
Click to collapse
Hello again!
Well, I am sorry to hear that, I have now no clue how to fix it. Hopefully, you'll do it
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.