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
Related
I have a forked update, Brevent, which doesn't require Xposed, nor root, nor unlock bootloader.
You can find it here: https://forum.xda-developers.com/android/apps-games/introduce-brevent-black-prevent-root-t3559151
Prevent Running was transfered to "Shanghai Falcon Network Co., Ltd." since 2.3.3.
This module was written for my GF, and accept donations.
Address: http://repo.xposed.info/module/me.piebridge.forcestopgb
How prevent running works?
After go deep in the android source, i find it uses flag when sending broadcast, so I hijack the IntentFilter's match.
And for other action, like force stop, launch activity, exit activity, I hijack them too.
So if any package is force stopped, it won't accept any intent filter...
However, i let input method, app widget, and laucher go.
- app widget, otherwise reboot is needed to show a widget in the widget chooser.
- configuration changed, otherwise cannot change lanugage
- account, otherwise sync and account won;t work
When the activity is launched, it can receive broadcast again..
When the activity exits by back key, it won't receive intent again, this function is added to android's feature.
So if you want to keep it running, please use home key instead.
And all the feature works for system package too, but the system package must have launcher.
Otherwise, if you still force stop it, it will cause FC (I suggest you use pm disable to do so).
Latest testing version: http://piebridge.me/pr/
Change Logs
for english version: please visit: http://piebridge.me/pr/CHANGELOG.en.txt
for chinese version: please visit: http://piebridge.me/pr/CHANGELOG.txt
First.
GB users will happy.
Good Work sir !
Will test it ASAP .
so by activing this module, after i click Force stop, in GB, will be the same like Hibernating with greenify ? :laugh:
lovely thanks, i hope this can make my old ace duos come back to life thanks liudongmiao bro
liudongmiao said:
This module is written for my GF, and accept donations.
// Normally, I don't accept any donation for most little project.
Address: http://repo.xposed.info/module/me.piebridge.forcestopgb
For GB user, there is no greenify, and there is no change to back-port.
1). greenify depends system's launch control (http://developer.android.com/about/versions/android-3.1.html#launchcontrols), which introduces in 3.1
2). greenify is not opensource, also the author and i live in the same country, even in the same city, however, he doesn't open source it.
How prevent running works?
After go deep in the android source, i find it uses flag when sending broadcast, so I hijack the IntentFilter's match.
And for other action, like force stop, launch activity, exit activity, I hijack them too.
So if any package is force stopped, it won't accept any intent filter...
However, i let input method, app widget, and laucher go.
- input method, otherwise reboot is needed to show a input method in the input method chooser.
- app widget, otherwise reboot is needed to show a widget in the widget chooser.
- launcher, otherwise there is no chance to start the activiy.
- view for system's package, otherwise it will cause FC. For example, if you force stop browser, and user want to visit a link, it should receive the broadcast.
When the activity is launched, it can receive broadcast again..
When the activity exits by back key, it won't receive intent again, this function is added to android's feature.
So if you want to keep it running, please use home key instead.
And all the feature works for system package too, but the system package must have launcher.
Otherwise, if you still force stop it, it will cause FC (I suggest you use pm disable to do so).
Click to expand...
Click to collapse
Please give screenshot and your battery life before and after installing this module
Sent from my GT-N7100 using Tapatalk
Was looking for Greenify for GB from long...
Can somebody review this app? Is there any shortfall of this app in comparison with Greenify (as user, don't understand technicality )
I tried this yesterday on google play services app and it worked fine. I can't see it in running services, so i can say (but not sure for other apps) its working :good: Hatsoff @liudongmiao your GF must be very proud of u if she's a geek :silly: One question: If we stop for example hangouts app, will we receive messages as usual??
swat4samp said:
I tried this yesterday on google play services app and it worked fine. I can't see it in running services, so i can say (but not sure for other apps) its working :good: Hatsoff @liudongmiao your GF must be very proud of u if she's a geek :silly: One question: If we stop for example hangouts app, will we receive messages as usual??
Click to expand...
Click to collapse
It shouldn't receive any broadcast, and never running, so you coun't recive messages.
Can you add a UI when you can choose apps to hibernate (like Greenify) and force stop them one by one?
BTW, this mod is superb...
Sent from my Xperia E1 dual using Tapatalk
1. Love doesn't need any reason.
2. Wanna speed up 3G (not 4G LTE)?
Here it is:
http://forum.xda-developers.com/showthread.php?t=2586876
3. My blog
4. Press the thanks button if I really helped/assisted you.
???? amazing , thanks so kmmuch
Enviado desde mi HTC One mediante Tapatalk
Hi all,
i installed this fantastic module. It work partially. Problem is when i exit aplication on back key application is still running. Where i am wrong? @liudongmiao
nikola1970 said:
Hi all,
i installed this fantastic module. It work partially. Problem is when i exit aplication on back key application is still running. Where i am wrong? @liudongmiao
Click to expand...
Click to collapse
No, nothing is wrong.
When you use back key to exit the application, the application won't receive any broadcast, however, the application will be cached, so the next time you open it, it will be opened very quickly. But before you open it again, it won't receive any broadcast.
However, if you want to the process be stopped, you can force stop it.
liudongmiao said:
No, nothing is wrong.
When you use back key to exit the application, the application won't receive any broadcast, however, the application will be cached, so the next time you open it, it will be opened very quickly. But before you open it again, it won't receive any broadcast.
However, if you want to the process be stopped, you can force stop it.
Click to expand...
Click to collapse
I observed this behaviour only with play services. For other apps, its working fine. So basically there's no much diffrnce between freezing and this except for application caching right? If we stop mms, do we still receive sms? A UI would be useful to look which apps are stopped and which are not. Great work man :good: BTW xposed for gb isn't updated yet. Any reason?
swat4samp said:
I observed this behaviour only with play services. For other apps, its working fine. So basically there's no much diffrnce between freezing and this except for application caching right? If we stop mms, do we still receive sms? A UI would be useful to look which apps are stopped and which are not. Great work man :good: BTW xposed for gb isn't updated yet. Any reason?
Click to expand...
Click to collapse
I don't know what's freeze, it doesn't seem to be a android's function.
As i said in the description, it doesn't force stop any application, but prevent sending broadcast to force stopped application.
For caching, it's a feature added to android's design.
For android's native design, when you start the application, it will be removed from the stop list until you force stop again.
But for me, i think its too complex to stop it, so i catch the finish, and if it's exited by finish, it will be added to the stop list.
// but it's in the cache processing list. so if you want to force stop it. this little design is useful for me to open a application temporary.
So if you stop the mms, i don't know whether you will receive or not.
The mms should be the core services of the android, i don't think you can force stop the services...
And i didn't forbidden the open the activity from the service, otherwise, it will cause FC of the application.
As i'm very busy, and an UI will take me some time. So there is no ui currently.
However, for the list, you can open the /data/data/me.piebridge.forcestopgb/conf/forcestop.list
For the xposed and other back-ported's module, it's not updated just because i'm too busy, and sometime too lazy .
You can read the description here: http://repo.xposed.info/module/me.piebridge.forcestopgb
And if you want to know more about the tech, you can read google's documetation: http://developer.android.com/about/versions/android-3.1.html#launchcontrols
thanky you for answers @liudongmiao
when i prevent Viber from running, when i start Viber, it starts but when you tao on some conversation it gives me force close. is this know bug?
Can we remove this setting simply by editing in config list (changing to false)?
Edit: I changed gms app to false and then opened the app to check which worked fine (i can see many running process in ram) and then i checked the list and it showed only that app in list. Is it alright?
Sent from my GT-S5670 using Tapatalk 2
swat4samp said:
Can we remove this setting simply by editing in config list (changing to false)?
Edit: I changed gms app to false and then opened the app to check which worked fine (i can see many running process in ram) and then i checked the list and it showed only that app in list. Is it alright?
Sent from my GT-S5670 using Tapatalk 2
Click to expand...
Click to collapse
true or false has special meaning.
true indicates this app is in the stopped list, and no broadcast would be send to the application.
false indicates this app has been marked in the stopped list, and when use back-key to exit, it would be in the stopped list.
I will write a simple ui, after the back-porting of xposed installer (completed), xprivacy (completed), and app settings (in to do).
im following this thread closely,and i want to test somethings,but before i do so,i have some questions.
the most important one its regarding about using this module along with greenify,what settings do i have to set in order to achieve the best of both apps,and then have a better experience.
Thanks.
kalel29 said:
im following this thread closely,and i want to test somethings,but before i do so,i have some questions.
the most important one its regarding about using this module along with greenify,what settings do i have to set in order to achieve the best of both apps,and then have a better experience.
Thanks.
Click to expand...
Click to collapse
As I have no ics+ devices, so i cannot say much things.
And if you want to try, you can wait for some days, I would write a simple configuation ui this weekend.
In short, if greenify works on your device, then just use greenify. But if you find greenify doesn't work at all, then try this one.
From design, greenify depends on http://developer.android.com/about/versions/android-3.1.html#launchcontrols introduces in android 3.1, this app hacks some api to emulate the launch controls. This works on gingerbread devices, and the devices that launch controls don't work at all.
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
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:
SecureAccessibility - Accessibility services or password-on-boot encryption? Pick both!
SecureAccessibility allows you to use accessibility services while still keeping the password-on-boot screen enabled!
If your password-on-boot screen is currently disabled, you will have to reactivate it for SecureAccessibility to work.
Compatible with everything from Kitkat (4.0) all the way to Oreo (8.1)!
If you find a bug, post here or create an issue in the Github issue tracker with your logcat + Xposed logs.
NOT TESTED on heavily modified ROMS (Touchwiz, LG, EMUI, etc...)
Xposed repository link: http://repo.xposed.info/module/xyz.nulldev.secureaccess
Source code: https://github.com/null-dev/SecureAccessibility
I managed to name the thread wrong while copy and pasting. Huge derp. It's fixed now.
Wow I was waiting a module like this a while ago.
Hy, may I ask why would I compromise phone's security if I would have accessibility enabled at the same time as pattern on boot? I'm just trying to understand the problem, I hope you can explain it
Also i want to know the problem.
It looks like I was actually wrong. This module may actually improve the security of your phone!
The reason accessibility services disable the password on boot screen is so users that rely on accessibility services to input data don't get locked out. This is because accessibility services are not available early on boot until the user decrypts their phone (they are not usable while entering the boot password).
I got this explanation from here where users are petitioning Google to keep the password on boot screen while having accessibility services enabled (which is what this module does): https://code.google.com/p/android/issues/detail?id=79309
By keeping the accessibility services enabled with the password on boot screen, you get the best of both worlds, with no compromise on security.
I have removed the warning from the module descriptions.
To add to comment #6 above:
Yes, this module has zero security impact.
All it does is prevent Android from disabling the boot encryption password when you enable an accessibility service. Period.
Before I used this module, whenever I turned on an accessibility service, I had to reenable password on boot by resetting my pin, which was a chore.
Fif_ said:
To add to comment #6 above:
Yes, this module has zero security impact.
All it does is prevent Android from disabling the boot encryption password when you enable an accessibility service. Period.
Click to expand...
Click to collapse
So I won't have any issues if I have to disable xposed after making use of this module for some reason? Just worried I might lock myself out of my phone.
Silkeyway said:
So I won't have any issues if I have to disable xposed after making use of this module for some reason? Just worried I might lock myself out of my phone.
Click to expand...
Click to collapse
Yep, nothing will happen.
Great work! Thank u very much!
greetz, brockn
Now that we have a janky Xposed on Nougat, has anyone tried it?
I've looked at the code, it should work, but doesn't on Nougat, Oxygen OS 4.5.10 on OnePlus 5.
No errors in the logs related to this module.
Fif_ said:
Now that we have a janky Xposed on Nougat, has anyone tried it?
I've looked at the code, it should work, but doesn't on Nougat, Oxygen OS 4.5.10 on OnePlus 5.
No errors in the logs related to this module.
Click to expand...
Click to collapse
I've just checked it again as well and it *should* work but I can't test it. Do you get the warning that password-on-boot will be disabled when you try to enable an accessibility service?
null-dev said:
I've just checked it again as well and it *should* work but I can't test it. Do you get the warning that password-on-boot will be disabled when you try to enable an accessibility service?
Click to expand...
Click to collapse
Yes I did.
I also checked the nougat source code and I agree with you that it should work [emoji3]
Yet it doesn't. It could be OOS patching the settings manager. I'll need to decompile it one day.
Fif_ said:
Yes I did.
I also checked the nougat source code and I agree with you that it should work [emoji3]
Yet it doesn't. It could be OOS patching the settings manager. I'll need to decompile it one day.
Click to expand...
Click to collapse
The official version of Xposed for Nougat was just released and I can confirm it works on there.
null-dev said:
The official version of Xposed for Nougat was just released and I can confirm it works on there.
Click to expand...
Click to collapse
I'll try it as soon as a systemless version comes out.
Edit: It works fine with the official Rovo89 Xposed 88.1 systemless and Magisk 14.2.
:angel:
I'm using Android 9 Magisk 20 and riru sandhook, just installed apk/activated xposed and seems to work so far. My intent was to prevent accessibility from turning my tasker off. This seems to the only real solution. Thank you.
Oukitel K9
---------Update on 2017-12-10----------
I spent some time on this issue these days and made a little progress. Here is what I found:
I am using Island (com.oasisfeng.island), which is also an Oasis Feng's project, to manage some apps which ask too much permissions and do not use GCM as push serivce.
The progress listed in the quick action menu are actually installed in "island", but are also recognized as "mainland" apps. They were once installed in the "mainland" and added to the Greenify, but already been moved to "island". So Greenify could not stop an app that did not exist.
Steps to reproduce the issue:
1. Install Amap (com.autonavi.minimap) and Alipay (com.eg.android.AlipayGphone) into "mainland" and "island";
2. Add both of the four apps into Greenify;
3. Remove them from "mainland";
4. In Island app, freeze then unfreeze these two apps;
5. The quick action notification menu should look like this:
https://i.imgur.com/0weJIRj.png
As you can see, the apps that were installed in the "island" are tagged with "(in Island)", but there are also two apps, which should have already been removed from "mainland", listed in there. And "hibernate all" function would do nothing to them, because they were actually not exist.
I'm not sure it's a bug with Greenify or Island, or even both.
Temporary Fix:
1. Install the apps that can't be hibernated into "mainland";
2. Remove them from Greenify;
3. Uninstall these apps from "mainland".
-----------Original Post----------------
Device: BlackBerry PRIV (STV100-1)
System: Adroid 6.0.1
Greenify: 3.8.5
Island: 2.5.0/2.5.2
Issue
All apps that were added to Greenify were listed in the quick action notification menu, even if they were already been hibernated.
When did this issue came out?
Recent update.
What do you expect?
Is there a way to set this function to list running apps only like before?
-----------Original Post End-------------
Explorare said:
Device: BlackBerry PRIV (STV100-1)
System: Adroid 6.0.1
Greenify: 3.8.5
Issue
All apps that were added to Greenify were listed in the quick action notification menu, even if they were already been hibernated.
When did this issue came out?
Recent update.
What do you expect?
Is there a way to set this function to list running apps only like before?
Click to expand...
Click to collapse
Not seeing this; QAN working as before. Might be config/device/rom specific. Greenify 3.8.5 on Android 7.1.2 w/Xposed (official).
Davey126 said:
Not seeing this; QAN working as before. Might be config/device/rom specific. Greenify 3.8.5 on Android 7.1.2 w/Xposed (official).
Click to expand...
Click to collapse
Thanks for your reply. I have updated the post with more details. Would you like to have a try on reproducing the problem on your device? Thanks.
Explorare said:
Thanks for your reply. I have updated the post with more details. Would you like to have a try on reproducing the problem on your device? Thanks.
Click to expand...
Click to collapse
Thanks for the additional details. Island is "Early Access" with clear notations around potential instability. It's up to the developer to take note of this thread and address any issues he feels are pertinent. It looks like you have identified a workaround; hopefully that will benefit others while things get sorted.