Related
I apologize if creating a new thread was wrong but this issue is a big one. Developers must notice this.
Greenify is undoubtedly one of most amazing apps that exist. thus such issues are frustrating.
Greenify was smart enough to not put running foreground apps (music players, maps or any app in use) to put into hibernation. it used to say "not hibernating xyz" .
I am on CM12.1 20150820 nightly. Using greenify 2.7beta5 . rooted. (no xposed)
Greenify was working just fine till i was on Cm version 20150811.
Basically it is unusable now. Either you don't use Greenify or keep the display on forever.
Please fix this guys . It was a greaaaaaaaaaaaaaaaat feature.
I do not know whether this is related to recent CM updates, but I am also running Greenify on CyanogenMod 12.1 (20150816 nightly) and Greenify is hibernating Spotify while it is playing (despite it's ongoing event notification). If I remember correctly, previously Spotify was not hibernated while playing in background (however I am not 100% sure). Both Greenify latest stable and latest beta versions have this issue (I was running stable and then updated to beta while trying to resolve this issue). Can anyone else confirm this?
Could @oasisfeng look at this?
Probably we should continue discussion in this thread.
2.7 Beta 6 is rolling out with a new implementation to detect foreground app via the app usage stats permission.
But unfortunately, this new implementation can only detect foreground app, but not background app with on-going notification. The latter will be supported in a future version, due to its implementation complexity.
oasisfeng said:
2.7 Beta 6 is rolling out with a new implementation to detect foreground app via the app usage stats permission.
But unfortunately, this new implementation can only detect foreground app, but not background app with on-going notification. The latter will be supported in a future version, due to its implementation complexity.
Click to expand...
Click to collapse
Music player still hibernating altough playing music :/
Hope you find a workaround...
oasisfeng said:
2.7 Beta 6 is rolling out with a new implementation to detect foreground app via the app usage stats permission.
But unfortunately, this new implementation can only detect foreground app, but not background app with on-going notification. The latter will be supported in a future version, due to its implementation complexity.
Click to expand...
Click to collapse
Thanks! Have you identified changes in CM creating this problem? CM guys are great, but sometimes they make bugs too! Once my Jelly Bean 4.x Airplane Mode Helper (btw working on Lollipop as well) got broken by a change in CyanogenMod/android_frameworks_base. I informed authors of the change about side effects (broken APIs) of that change and they got fixed pretty soon.
If the Greenify breaking API changes were introduced by CyanogenMod (and not by Google), then IMHO @oasisfeng should inform CyanogenMod team about the fact they have broken API compatibility with native Android, and most likely CM will fix the broken APIs. I think best way to do it is by writing comments in CyanogenMod's Gerrit to the breaking patch sets.
DavisNT said:
Thanks! Have you identified changes in CM creating this problem? CM guys are great, but sometimes they make bugs too! Once my Jelly Bean 4.x Airplane Mode Helper (btw working on Lollipop as well) got broken by a change in CyanogenMod/android_frameworks_base. I informed authors of the change about side effects (broken APIs) of that change and they got fixed pretty soon.
If the Greenify breaking API changes were introduced by CyanogenMod (and not by Google), then IMHO @oasisfeng should inform CyanogenMod team about the fact they have broken API compatibility with native Android, and most likely CM will fix the broken APIs. I think best way to do it is by writing comments in CyanogenMod's Gerrit to the breaking patch sets.
Click to expand...
Click to collapse
Unfortunately, it's an upstream change in AOSP made by Google. So I bet we have little chance arguing that change.
oasisfeng said:
Unfortunately, it's an upstream change in AOSP made by Google. So I bet we have little chance arguing that change.
Click to expand...
Click to collapse
Thanks! I know from discussion on Google+ about the CyanogenMod 12.1 Change 105861 that is comming from AOSP and has broken Greenify.
Could you please try adding
Code:
<uses-permission android:name="android.permission.INTERACT_ACROSS_USERS_FULL" />
to the manifest of next beta? Then I could do
Code:
pm grant com.oasisfeng.greenify android.permission.INTERACT_ACROSS_USERS_FULL
as root, test Greenify and report back to you whether this has resolved the issue.
Permission name INTERACT_ACROSS_USERS_FULL comes from Change 105861, file ActivityManagerService.java line 12547 (in Patch Set 1). Looks like either INTERACT_ACROSS_USERS_FULL or REAL_GET_TASKS permission is required.
Update! Sorry! Looks like nor android.permission.INTERACT_ACROSS_USERS_FULL, nor android.permission.REAL_GET_TASKS can be granted by pm grant.
@oasisfeng May be getActiveNotifications() from NotificationListenerService could help detecting applications having ongoing event notifications (by checking isOngoing() and getPackageName() of returned notifications)?
Hope this issue gets fixed :/
@oasisfeng
Any news?
I have exactly the same problem with greenify and cm12.1 (on latest nightly). Effectively removes all the benefits of greenify and turns it into a liability when it shuts down apps I'm relying on. Obviously I am not complaining about the dev as it isn't their fault at all, but it is really annoying.
iamnotkurtcobain said:
@oasisfeng
Any news?
Click to expand...
Click to collapse
The issue has been fixed in version 2.7 beta 8.
Many thanks to @oasisfeng for quick solution!
not working yureka cm 12.1..lollipop 5.1.1 not rooted.. any solution?
This Module removes Ads from Appy Geek using the Xposed Framework.
Its current capabilities are limited to removing fullscreen Ads shown when the App is started. Remove list Ads planned, but I can't give an ETA.
Tested on
Android 4.4.4
Xposed v54
Android 5.0.2
Xposed v71
Android 5.1.1
Xposed v72
...
Xposed v75
Source Code at GitHub
Download from Xposed Repo
Please tell me, if it works for you.
reserved
Seems to work on my Sony Xperia ZR 5.1.1. Haven't encountered an adds in Appy Geek so far.
Great work!
Great module Works flawlessly so far on my HTC One M7 (GPE 5.1 - LMY4701.H10 / Framework 75)
Any project for News Republic? The app seems pretty similar
Yes, a really good module!! I'd love to see more from News Republic (especially AppyGamer)
Keep working on it :good:
Granted, I did not realize that there are other apps by News Republic. I suppose it is possible to expand this module to this apps.
I'll take care of it. Stay tuned.
XPrivacyLua
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy).
Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data instead of real data.
Features:
Simple to use
Manage any user or system app
Extensible
Multi-user support
Free and open source
See here for all details, including installation instructions and download link.
Please read the frequently asked questions before asking a question.
This XDA thread is about using the latest version of XPrivacyLua. Off topic comments are allowed as long they are related to XPrivacyLua and are in the general interest of the followers of this thread, but anything not related to privacy is not allowed.
If XPrivacyLua doesn't work and/or when "module not running or updated" is shown, this is almost always caused by an Xposed problem.
Discussions about purchases are not allowed here, please contact me via here instead.
XPrivacyLua is being maintained and community supported, but new features won't be added anymore.
Custom hook definitions will always be part of XPrivacyLua, but there will be community support only. This means that I won't respond to questions about defining custom hooks anymore. See this thread for the reasons.
If you value your privacy, please consider to support this project with a donation or by purchasing pro features.
M66B said:
XPrivacyLua is not a permission manager, but a privacy manager. XPrivacyLua doesn't block things and doesn't revoke permissions, but does replace real data by fake data. This means you can grant Android permissions to an app and still let XPrivacyLua prevent the app from seeing privacy sensitive data. Revoking permissions can result in an app refusing to work and/or to crash. However, replacing real by fake data generally doesn't let an app crash.
Currently restrictions are quite crude because they mostly replace real data by no data. For example restricting the contacts app from getting contacts will result in an empty contact list. In the near future it might be made possible to select the data an app may see, for example just one group of contacts.
Click to expand...
Click to collapse
About feature requests and bug reports:
M66B said:
The goal is to have a tool that can properly protect the privacy of many in the near future. However, it isn't paid work, so I do whatever I like whenever I like it.
You can request features in this XDA forum. I will read them, but I will not respond to them and they might or might not be implemented. If I know for sure something will not be implemented, I will let you know.
You can report any problem you have here. There will be no issue tracker on GitHub.
Click to expand...
Click to collapse
M66B said:
For now I have decided to not implement restrictions that are useful to prevent tracking only. There are simply too many data items that can be used for tracking and it would take too much time to develop restrictions for all these data items.
The basic idea is to restrict only things that 'define' you, so which contacts you have, where you are, which apps you use, etc.
Click to expand...
Click to collapse
Namnodorel said:
Maybe we can widen the definition of things that the core of XPL covers to "What defines you, and what can be used to spie on you"? This would include camera/audio, but not tracking.
Click to expand...
Click to collapse
M66B said:
XPrivacyLua is pretty feature complete and will be maintained and supported and when there is a need new hook definitions will be added to better protect your privacy. For the rest this FAQ applies:
https://github.com/M66B/XPrivacyLua/blob/master/FAQ.md#FAQ4
As said before, development will also depend on Xposed development, which is just minimal unfortunately.
Click to expand...
Click to collapse
XDA thanks and donations are appreciated.
XPrivacyLua is supported with Xposed only. There is no support for VirtualXposed and TaiChi.
Even if old Xprivacy isn't supported on nougat, is it possible to keep it with new Lua too until Lua grow up? Or it is not recommended ?
Thank you
Orphee said:
Even if old Xprivacy isn't supported on nougat, is it possible to keep it with new Lua too until Lua grow up? Or it is not recommended ?
Thank you
Click to expand...
Click to collapse
Noooo! First post and it is asking about using Xprivacy on Nougat? That must be demotivating to the dev! It has been told too many times in the xprivacy thread that it is not recommended to use it on Nougat and above all IT IS NOT SUPPORTED!
Sorry for using capitals but let's hope everyone sees it and this thread stays on new Lua topic.
Greetings.
Wow, I was just scrolling through some stuff, stumbled into your repo for XPrivacy/Lua and couldn't believe what I saw! M66B is developing a new app as a replacement for XPrivacy... Thank you so much, you've totally made my day and pobably quite some time into the future as well! I'll definetely also buy/donate for this version as soon as I get to use it.
Just some technical questions:
Looks like you are going more modular with this new app, and you mentioned something about downloading additional (user-made) hooks. You also said you'd keep it much more simple this time to avoid high maintenance etc. Could these external hooks then allow to get the complexity back? I totally understand your motivation, but in-depth restricting of app permissions was something I really liked about the old XPrivacy, and if some user-made hooks would make that possible I'd use them. But they'd also need the ability to add new UI elements, and not just "This hook is about the method XY, execute this code before/after to block it and this code to enable it" for that to be possible.
Orphee said:
Even if old Xprivacy isn't supported on nougat, is it possible to keep it with new Lua too until Lua grow up? Or it is not recommended ?
Click to expand...
Click to collapse
I have just added a FAQ that answers this question:
https://github.com/M66B/XPrivacyLua/blob/master/FAQ.md
m66b said:
i have just added a faq that answers this question:
https://github.com/m66b/xprivacylua/blob/master/faq.md
Click to expand...
Click to collapse
5vp4096549363413x
Namnodorel said:
Wow, I was just scrolling through some stuff, stumbled into your repo for XPrivacy/Lua and couldn't believe what I saw! M66B is developing a new app as a replacement for XPrivacy... Thank you so much, you've totally made my day and pobably quite some time into the future as well! I'll definetely also buy/donate for this version as soon as I get to use it.
Just some technical questions:
Looks like you are going more modular with this new app, and you mentioned something about downloading additional (user-made) hooks. You also said you'd keep it much more simple this time to avoid high maintenance etc. Could these external hooks then allow to get the complexity back? I totally understand your motivation, but in-depth restricting of app permissions was something I really liked about the old XPrivacy, and if some user-made hooks would make that possible I'd use them. But they'd also need the ability to add new UI elements, and not just "This hook is about the method XY, execute this code before/after to block it and this code to enable it" for that to be possible.
Click to expand...
Click to collapse
For now I will concentrate on fixing bugs and building restrictions, which is of course the most important of all. Restrictions are indeed defined and written in Lua. Currently all restrictions are built-in, but later I might add a manager, so you can manage your own definitions. There might even be a repository, which could even contain definition for things not privacy related.
You can find the current definitions here (hooks.json contains the definitions).
Just donated. More to follow along the way. Thank you!!
blackhawk_LA said:
Noooo! First post and it is asking about using Xprivacy on Nougat? That must be demotivating to the dev! It has been told too many times in the xprivacy thread that it is not recommended to use it on Nougat and above all IT IS NOT SUPPORTED!
Sorry for using capitals but let's hope everyone sees it and this thread stays on new Lua topic.
Greetings.
Click to expand...
Click to collapse
"XPrivacyLua is supported on Android 6 Marshmallow and later" you're either lying or it's a misstatement on the repo.
Also can somehow explain to me (I just switched to Android), what Lua is (if not a programming language)?
OgreTactic said:
"XPrivacyLua is supported on Android 6 Marshmallow and later" you're either lying or it's a misstatement on the repo.
Click to expand...
Click to collapse
I don't see why that is a lie or misstatement, so, could you please explain why you think it is?
Edit: I have changed the wording of the opening post a bit, so it is clearer that "Android 6 Marshmallow and later" applies to XPrivacyLua and not to XPrivacy, assuming this is what you meant.
OgreTactic said:
Also can somehow explain to me (I just switched to Android), what Lua is (if not a programming language)?
Click to expand...
Click to collapse
See this comment.
OgreTactic said:
"XPrivacyLua is supported on Android 6 Marshmallow and later" you're either lying or it's a misstatement on the repo.
Also can somehow explain to me (I just switched to Android), what Lua is (if not a programming language)?
Click to expand...
Click to collapse
Some people...
Glad to see Xposed Module development is still alive!
Thx a lot for building and developing this app.
After I've selected some apps I get an error:
XLua.Main:android.os.DeadObjectException:Transaction failed on small parcel; remote process probably died
Things that I would appreciate in future releases:
- More restriction-types like: Network connection, Telephone number/sim-operator, Serialnumber, installed apps/services, accounts
- Is it possible to hide disabled apps from the list?
- Is it possible to decide when an app will request for example the location to allow or deny the request?
th4_c0r3 said:
Thx a lot for building and developing this app.
After I've selected some apps I get an error:
XLua.Main:android.os.DeadObjectException:Transaction failed on small parcel; remote process probably died
Click to expand...
Click to collapse
Can you please capture a logcat? If not, the problem might be visible in the Xposed log as well.
Edit: where exactly do you see this error?
th4_c0r3 said:
Things that I would appreciate in future releases:
- More restriction-types like: Network connection, Telephone number/sim-operator, Serialnumber, installed apps/services, accounts
- Is it possible to hide disabled apps from the list?
- Is it possible to decide when an app will request for example the location to allow or deny the request?
Click to expand...
Click to collapse
Disabled apps are hidden from the list by default.
First: thanks for the release and minimal UI of this app.
Just one request if it is possible. Would it be possible when you start ironing out the features to include a randomisation to some privacy information. Like my main coordinates for GPS are 33N 112W. If the app could randomise the rest so the app knows my general location but not accurately as 1m?
Edit: a good reason for this is for apps like speedtest.net. it grabs GPS to find a close server. When I restrict, closes server is in NY. I don't mind if it knows I live in AZ, heck, XDA knows I live here, but knowing my exact location is bothering.
M66B said:
Can you please capture a logcat? If not, the problem might be visible in the Xposed log as well.
Edit: where exactly do you see this error?
Click to expand...
Click to collapse
The error occurs every second time I open the app and it's shown in the bottom of the app. In the Xposed log there isn't a XLua-Error.
I've sent you the logcat via email.
M66B said:
For now I will concentrate on fixing bugs and building restrictions, which is of course the most important of all. Restrictions are indeed defined and written in Lua. Currently all restrictions are built-in, but later I might add a manager, so you can manage your own definitions. There might even be a repository, which could even contain definition for things not privacy related.
Click to expand...
Click to collapse
Thank you for your answer, but I'm still kinda missing what I wanted to know: Could hooks potentially add custom UI and/or save data? I'd imagine something like saving a list of contacts and when an app requests the contact list selecting this specific list to be returned.
Namnodorel said:
Thank you for your answer, but I'm still kinda missing what I wanted to know: Could hooks potentially add custom UI and/or save data? I'd imagine something like saving a list of contacts and when an app requests the contact list selecting this specific list to be returned.
Click to expand...
Click to collapse
Yes, that would be possible. When there is a need, I will add APIs that can be used in Lua to save data in a structured way into the XPrivacyLua database, so anyone wanting to develop a new hook definition doesn't have to worry about how to do this. In fact this has already been prepared.
M66B said:
I don't see why that is a lie or misstatement, so, could you please explain why you think it is?
Edit: I have changed the wording of the opening post a bit, so it is clearer that "Android 6 Marshmallow and later" applies to XPrivacyLua and not to XPrivacy, assuming this is what you meant.
See this comment.
Click to expand...
Click to collapse
Oh okay, thanks. So I can't use the current XPrivacy (on the PlayStore) on Nougat S8? I hope I can if not, I'll wait for the XPrivacy L.
It's crazy that Android forces privacy breaching (violation is an accurate word use) "services", processes and apps at it's core. If I were to learn to use Android enough is it possible to prevent it, like it's the case on iPhone, well in appareances because when you jailbreak it you can see all the processes, but it's clearly not in completely forcing this violation of your data, be it just with the permission management that NO apps can require or force on you to run, which to me absolutely crazy that it's the case on Android.
OgreTactic said:
Oh okay, thanks. So I can't use the current XPrivacy (on the PlayStore) on Nougat S8? I hope I can if not, I'll wait for the XPrivacy L.
It's crazy that Android forces privacy breaching (violation is an accurate word use) "services", processes and apps at it's core. If I were to learn to use Android enough is it possible to prevent it, like it's the case on iPhone, well in appareances because when you jailbreak it you can see all the processes, but it's clearly not in completely forcing this violation of your data, be it just with the permission management that NO apps can require or force on you to run, which to me absolutely crazy that it's the case on Android.
Click to expand...
Click to collapse
As M66B said in the Xprivacy Thread:
M66B said:
An absolute privacy fix is turning your device off. XPrivacy is an best effort attempt to fix the most important privacy problems, like exposing your location and contacts.
Click to expand...
Click to collapse
What you could do, at least that's what I do, is to disable services (look for DisableService in PlayStore) and/or restrict as much as possible via the privacy settings (depending on ROM). For example I deny Google services the location rights and only switch them on when needed.
Also there are possibilities to run your phone without any Google services at all. Search for MicroG.
But you have to understand, that using an Android device is going to violate privacy in one form or another. Same goes with Windows and Apple devices...
I don't like it at all but that's just what the world has become. If you want to use Google Services you kinda have to accept that you can't (at least not with simple fixes) protect your whole privacy. It sucks, but that's just what it is...
I don't know if this is the right place to post this thread but I can't see any feature request thread anywhere.
So as the title says, I would like to request a feature that is similiar to Smart Hibernation, except that it will avoid Dozing the phone if it detects any notification of application(s) added to its list.
Of course there should be an extra menu to add Smart Doze list. This way I don't have to disable Aggressive Doze everytime I cast something. I keep losing connection with Aggresive Doze on when I cast Youtube / other apps to Chromecast. Only disabling Aggressive Doze fixes it. (Yes I did put Youtube on doze white list)
Probably Smart Doze is not the right name but you get the point I'm using android 6.0.1 Galaxy Note 4
Thanks in advance!
Off topic : I think should we have a feature request thread? That way oasisfeng can read all the feature requests in one thread
threetwotwo said:
...I would like to request a feature that is similiar to Smart Hibernation, except that it will avoid Dozing the phone if it detects any notification of application(s) added to its list....
Click to expand...
Click to collapse
Assuming that I've correctly understood your addressed requirement, and my assumption might be wrong that would void everything coming behind, the requested feature/function is already available as one of the Xposed-based features; and actually working perfectly.
I'm well aware that not everybody wants to use Xposed for some reasons beyond the scope of the Greenify forum but I think it's simply that way that you can't get lots of functionalities if you're unrooted, you receive more power if rooted, but for some functionalities you ultimately require the Xposed framework.
Oswald Boelcke said:
Assuming that I've correctly understood your addressed requirement, and my assumption might be wrong that would void everything coming behind, the requested feature/function is already available as one of the Xposed-based features; and actually working perfectly.
I'm well aware that not everybody wants to use Xposed for some reasons beyond the scope of the Greenify forum but I think it's simply that way that you can't get lots of functionalities if you're unrooted, you receive more power if rooted, but for some functionalities you ultimately require the Xposed framework.
Click to expand...
Click to collapse
I guess you misunderstood? Let me rephrase my experience in points.
- My chromecast keeps disconnecting from my phone if I cast Youtube / other apps after a few minutes when screen is off
- Already put all casting apps to doze whitelist
- Can be fixed by setting Aggresive Doze off but I want to keep it on
threetwotwo said:
I guess you misunderstood? Let me rephrase my experience in points.
- My chromecast keeps disconnecting from my phone if I cast Youtube / other apps after a few minutes when screen is off
- Already put all casting apps to doze whitelist
- Can be fixed by setting Aggresive Doze off but I want to keep it on
Click to expand...
Click to collapse
Aggressive doze generally does not yield significant power savings relative to standard doze. Switch it off and profit.
threetwotwo said:
I guess you misunderstood? Let me rephrase my experience in points.
- My chromecast keeps disconnecting from my phone if I cast Youtube / other apps after a few minutes when screen is off
- Already put all casting apps to doze whitelist
- Can be fixed by setting Aggresive Doze off but I want to keep it on
Click to expand...
Click to collapse
I apologise; it's correct I clearly misunderstood. Lacking own experiences with chromecast or other casting apps and the apps not being part of my portfolio, I'm unable to test myself. Just imagine its utilisation, I currently don't understand why to greenify chromecast and the others at all. At least I didn't do that with applications I want them to run even if the screen is off like OsmAnd+, my mapping and navigation app for hiking and biking,and 15 (just counted them) others for various reasons. On average, I get a battery drainage of 0.5 - 0.7%/h, which is absolutely satisfying to me under special consideration that my devices is running and doing its job as advertised and required by me under all conditions. I never tried but personally doubt that I'd gain a lower drainage if I greenify the aformentioned applications.
Davey126 said:
Aggressive doze generally does not yield significant power savings relative to standard doze. Switch it off and profit.
Click to expand...
Click to collapse
On android 7.0+ maybe but on 6.0 Aggresive doze really helps a lot.
Oswald Boelcke said:
I apologise; it's correct I clearly misunderstood. Lacking own experiences with chromecast or other casting apps and the apps not being part of my portfolio, I'm unable to test myself. Just imagine its utilisation, I currently don't understand why to greenify chromecast and the others at all. At least I didn't do that with applications I want them to run even if the screen is off like OsmAnd+, my mapping and navigation app for hiking and biking,and 15 (just counted them) others for various reasons. On average, I get a battery drainage of 0.5 - 0.7%/h, which is absolutely satisfying to me under special consideration that my devices is running and doing its job as advertised and required by me under all conditions. I never tried but personally doubt that I'd gain a lower drainage if I greenify the aformentioned applications.
Click to expand...
Click to collapse
Nope, I don't greenify those apps either, I only greenify stubborn apps I got in my phone there are a few but I need them.
delete
threetwotwo said:
On android 7.0+ maybe but on 6.0 Aggresive doze really helps a lot.
Click to expand...
Click to collapse
Doze on the go (Xposed section) is the setting you want on Android 6 which is the default on Android 7.x and above. If Aggressive Doze is helping "a lot" then something else is happening under the covers. Whether it is worth pursuing is up to you.
Davey126 said:
Doze on the go (Xposed section) is the setting you want on Android 6 which is the default on Android 7.x and above. If Aggressive Doze is helping "a lot" then something else is happening under the covers. Whether it is worth pursuing is up to you.
Click to expand...
Click to collapse
Of course, but this does not relate to what I am suggesting / feature request.
threetwotwo said:
Of course, but this does not relate to what I am suggesting / feature request.
Click to expand...
Click to collapse
Smart doze isn't needed IMO; you have a specialized situation on an EOL Android base. Would rather see the developer focus on other progressive functionality.
Greenify isn't a 'doze tweaker' - nor should it become one. Plenty of other largely ineffective apps/modules/tools apps in that crowded space.
I'll step out of the ring now and allow your request to progress on its own merits.
Since M66B decided to discontinue support for XPrivacyLua and the official thread was closed I'm starting this unofficial thread to continue discussing the module.
It currently works up to android 13 with LSPosed.
Source code can be found at the author's github https://github.com/M66B/XPrivacyLua
FAQ https://github.com/M66B/XPrivacyLua/blob/master/FAQ.md
Please read the original thread as it contains a lot of useful information https://forum.xda-developers.com/t/...-android-privacy-manager-unsupported.3730663/
Disclaimer: I am not the developer of the module. I'm a long time user of XPrivacy/XPrivacyLua who wants to keep using it on future android versions. All credits for this module go to the developer and the people who made the custom hooks.
Best module to date
Thank you for creating new thread for XPL user.
is there a trick to get new apps automatically checked on lsposed? Otherwise, the option that new apps take all rights during installation does not work.
Conan179 said:
is there a trick to get new apps automatically checked on lsposed? Otherwise, the option that new apps take all rights during installation does not work.
Click to expand...
Click to collapse
Not with LSPosed but according to this post you can do it with tasker. I think there's also an LSPosed fork that does it too.
[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
XPrivacyLua Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy). Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data...
forum.xda-developers.com
mythos_ said:
I think there's also an LSPosed fork that does it too.
Click to expand...
Click to collapse
There is, it's this LSPosed_mod.
I still haven't tried it myself though.
heinhuiz said:
There is, it's this LSPosed_mod.
I still haven't tried it myself though.
Click to expand...
Click to collapse
Yes, since v1.8.5 according the mod changelog:
now user can choose if set automatic add new installed packages to module
fix add column automatic_add when exist
Click to expand...
Click to collapse
@Oswald Boelcke the thread is about XPrivacyLua or about LSPosed ?
Lol
VD171 said:
@Oswald Boelcke the thread is about XPrivacyLua or about LSPosed ?
Lol
Click to expand...
Click to collapse
Hello and good morning, @VD171
I guess you need to address the OP @mythos_ with this question but as far as I understand it's about the Xposed module XPrivacyLua by @M66B and not about LSPosed. If my assumption is correct it's on the OP to decide if LSPosed related questions and contributions are off-topic (OT) or not. A moderator will never get involved to that unless a threadowner (and only the owner) reports something as OT.
Regards
Oswald Boelcke
Senior Moderator
The main focus should be on XPL but since LSPosed is needed to run XPL, I see nothing wrong with discussing it here.
QoL things like how to auto-add new apps to LSPosed are fine. Of course if people want a more in depth discussion (e.g. bugs, new features, etc.) they should post in the LSPosed threads as the developers don't read this.
VD171 said:
@Oswald Boelcke the thread is about XPrivacyLua or about LSPosed ?
Lol
Click to expand...
Click to collapse
Really? Wow...smh
exist an active fork of this app ?
xerves78 said:
exist an active fork of this app ?
Click to expand...
Click to collapse
According to github there is a whole bunch of people who forked it in the past month. How active they will be in the future and (more importantly) how much you can trust them is another issue.
when this project was abandoned by m66b did he opensource the "pro" app?
and is the code available now for free to be built from source?
or is there a link to the last version?
i hope someone keeps working on this, as privacy is more and more important the more stuff is kept on our phones.
nutzfreelance said:
when this project was abandoned by m66b did he opensource the "pro" app?
and is the code available now for free to be built from source?
or is there a link to the last version?
i hope someone keeps working on this, as privacy is more and more important the more stuff is kept on our phones.
Click to expand...
Click to collapse
[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
XPrivacyLua Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy). Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data...
forum.xda-developers.com
(...) The pro companion app won't be open-sourced. If somebody wants to continue the project, (s)he can prove being a worthy developer by developing a new pro companion app, which can be done in at most a few days. As already offered, another developer can ask for the source code after a significant contribution to the source code as well.
Click to expand...
Click to collapse
I've already reported to @M66B about "MEW wallet" app which can't be restricted (tested on A10) to access camera (not sure is it was photo or video - app is handling QR codes) at https://forum.xda-developers.com/t/...acy-manager-unsupported.3730663/post-87416749.
Now I've installed LineageOS 20 (A13) and noticed default Camera app (which is new "Aperture" Lineage app) also can't be restricted to BOTH video and photo (but microphone restriction works okay and result in recording video without sound).
Looks like there are some new API to be restricted… so, @M66B, maybe you can update XPrivacyLua a bit to fix this? Or at least give some hint for someone who might wanna fork it?
mythos_ said:
Not with LSPosed but according to this post you can do it with tasker. I think there's also an LSPosed fork that does it too.
[CLOSED][APP][XPOSED][6.0+] XPrivacyLua - Android privacy manager [UNSUPPORTED]
XPrivacyLua Really simple to use privacy manager for Android 6.0 Marshmallow and later (successor of XPrivacy). Revoking Android permissions from apps often let apps crash or malfunction. XPrivacyLua solves this by feeding apps fake data...
forum.xda-developers.com
Click to expand...
Click to collapse
I've checked both Tasker methods to update LSPosed.
First one (UI automation) didn't work because there are no "LSPosed Manager" app (it's now started only as a widget, and I don't found a way in Tasker to start widget), so this unlikely can be fixed at all.
Second one (database editing) might work… but to me it looks unsafe: each time new app is installed it does kill `lspd` (LSPosed daemon, I suppose) after editing database for 1 second and then restarts it. I think this might result in allowing app apps to bypass XPrivacyLua restictions within that 1 second. No idea how to test this.
Also I've tried to replace original LSPosed with modified version https://github.com/mywalkb/LSPosed_mod - it works like a charm: installed as drop-in replacement over original one, keeps all configuration of original one after reboot and provide new UI to automatically add new apps to XPrivacyLua module! To me it looks like main and only actual way to continue using XPrivacyLua for now.
mythos_ said:
The main focus should be on XPL but since LSPosed is needed to run XPL, I see nothing wrong with discussing it here.
QoL things like how to auto-add new apps to LSPosed are fine. Of course if people want a more in depth discussion (e.g. bugs, new features, etc.) they should post in the LSPosed threads as the developers don't read this.
Click to expand...
Click to collapse
You might want to add that info to the OP of this thread in order to avoid any further confusion in the future
Cheers
powerman.asdf said:
I've already reported to @M66B about "MEW wallet" app which can't be restricted (tested on A10) to access camera (not sure is it was photo or video - app is handling QR codes) at https://forum.xda-developers.com/t/...acy-manager-unsupported.3730663/post-87416749.
Now I've installed LineageOS 20 (A13) and noticed default Camera app (which is new "Aperture" Lineage app) also can't be restricted to BOTH video and photo (but microphone restriction works okay and result in recording video without sound).
Looks like there are some new API to be restricted… so, @M66B, maybe you can update XPrivacyLua a bit to fix this? Or at least give some hint for someone who might wanna fork it?
Click to expand...
Click to collapse
@M66B won't care with that.
You should do what you want by yourself or wait and hope to someone else release that.
powerman.asdf said:
I've checked both Tasker methods to update LSPosed.
First one (UI automation) didn't work because there are no "LSPosed Manager" app (it's now started only as a widget, and I don't found a way in Tasker to start widget), so this unlikely can be fixed at all.
Second one (database editing) might work… but to me it looks unsafe: each time new app is installed it does kill `lspd` (LSPosed daemon, I suppose) after editing database for 1 second and then restarts it. I think this might result in allowing app apps to bypass XPrivacyLua restictions within that 1 second. No idea how to test this.
Also I've tried to replace original LSPosed with modified version https://github.com/mywalkb/LSPosed_mod - it works like a charm: installed as drop-in replacement over original one, keeps all configuration of original one after reboot and provide new UI to automatically add new apps to XPrivacyLua module! To me it looks like main and only actual way to continue using XPrivacyLua for now.
Click to expand...
Click to collapse
"auto-add" is a waste of time.
LSPosed is developed for avoiding something like "all-add" or "auto-add".
Since you are talking about something that is contrary to the official release, LSPosed developers will never read and care to the thread.
mythos_ said:
According to github there is a whole bunch of people who forked it in the past month. How active they will be in the future and (more importantly) how much you can trust them is another issue.
Click to expand...
Click to collapse
how / where can i find the forks on github ?