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.
Related
Hi All,
I love Greenify, I used it regularly on my phone.
Unfortunately, I got a new job and my work required me to install an MDM product, Mobiliron
It will not let me access my work information unless I uninstall greenify. It detects certain applications on their list. It's a really dumb implementation, but not much I can do about it.
Is there an alternate build that I could install that anyone has that is the same application but named something different that might hopefully not flag in their application blacklist?
jbstanford said:
Hi All,
I love Greenify, I used it regularly on my phone.
Unfortunately, I got a new job and my work required me to install an MDM product, Mobiliron
It will not let me access my work information unless I uninstall greenify. It detects certain applications on their list. It's a really dumb implementation, but not much I can do about it.
Is there an alternate build that I could install that anyone has that is the same application but named something different that might hopefully not flag in their application blacklist?
Click to expand...
Click to collapse
In case you have installed Xposed, try MinMinHide.
Thanks for the option, but I need a non root option unfortunately. Greenify works fine, but because it flags on an application blacklist it conflicts
For an Android 5.x device, you can use secondary user for your work app, which won't see the apps installed in the primary user.
jbstanford said:
Hi All,
I love Greenify, I used it regularly on my phone.
Unfortunately, I got a new job and my work required me to install an MDM product, Mobiliron
It will not let me access my work information unless I uninstall greenify. It detects certain applications on their list. It's a really dumb implementation, but not much I can do about it.
Is there an alternate build that I could install that anyone has that is the same application but named something different that might hopefully not flag in their application blacklist?
Click to expand...
Click to collapse
Ine just found this here in the forums:
[APP][ROOT] Servicely - Replacement for Greenify [24 Apr 15]
http://forum.xda-developers.com/showthread.php?t=3091708
You must be rooted, but at least don't have Greenify installed.
oasisfeng said:
For an Android 5.x device, you can use secondary user for your work app, which won't see the apps installed in the primary user.
Click to expand...
Click to collapse
Mmm...didn't know that.
Like Windows different users??
Sent from my Samsung Galaxy S3 GT-i9300 using Tapatalk 4
jbstanford said:
Thanks for the option, but I need a non root option unfortunately. Greenify works fine, but because it flags on an application blacklist it conflicts
Click to expand...
Click to collapse
PIRATA! said:
Ine just found this here in the forums:
[APP][ROOT] Servicely - Replacement for Greenify [24 Apr 15]
http://forum.xda-developers.com/showthread.php?t=3091708
You must be rooted, but at least don't have Greenify installed.
Click to expand...
Click to collapse
Well, Servicely also requires root and thus is rather impracticable, I guess.
PIRATA! said:
Mmm...didn't know that.
Like Windows different users??
Click to expand...
Click to collapse
Yes, you can set up different accounts for the same device.
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
Greenify "went away" as did two apps it had hibernated, now I can't re-install them
Hi,
I recently rooted my AT&T LGv30 and installed TWRP and Magisk 1.6. I then installed Xposed via Magisk Manager and played with it a bit. I went on to install Greenify donation and enabled all the beta and aggressive stuff, as well as Xposed integration. I later discovered that Xposed breaks SafetyNet checks so I decided to remove it. When I did, Greenify "went away". I had to re-install it. It was only later that I noticed 2 other apps were missing, namely Xmeye (a security camera app notorious for consuming battery) and Spotify (here I was just playing around, but Greenify said it was using battery, so...). These were the only two apps I had added to Greenify.
I then attempt to re-install both of these apps from the Google Play store. It goes through the process of downloading, then installing, but at the end of the installation process, the Google Play button simply reverts back to "Install", as if nothing happened. The same thing happens when I try again, on either app. I can install any other app just fine.
I've run the latest Xposed uninstaller zip from recovery, but this didn't help. I do have a vague recollection of Greenify continuing to run in root + Xposed mode after Xposed had been removed, if that makes any sense. Eventually, after a subsequent re-install of Greenify (not if before or after Xposed was removed), it then walked my through the setup again, and is now running only in root mode. Yet, the problem with the two apps remains.
I'm hoping someone has a suggestion before I wipe everything and start over.
Thanks,
Daniel
Following up on my own post. I ended up installing SD Maid, which was able to show me both Spotify and Xmeye as "stopped". From the app I selected to delete both applications, which I could not do anywhere else, as they didn't show up in normal apps. My guess is that Greenify with Xposed and therefore root caused some file ownership issue that the normal utilities were not able to handle.
Daniel
DanielCeregatti said:
Following up on my own post. I ended up installing SD Maid, which was able to show me both Spotify and Xmeye as "stopped". From the app I selected to delete both applications, which I could not do anywhere else, as they didn't show up in normal apps. My guess is that Greenify with Xposed and therefore root caused some file ownership issue that the normal utilities were not able to handle.
Click to expand...
Click to collapse
Root cause likely resides elsewhere; Greenify doesn't mess with permissions.
Davey126 said:
Root cause likely resides elsewhere; Greenify doesn't mess with permissions.
Click to expand...
Click to collapse
Yet the two apps managed by Greenify stopped working. So you're saying correlation does not equal causation? Because the evidence here indicates otherwise. Just sayin'...
DanielCeregatti said:
Yet the two apps managed by Greenify stopped working. So you're saying correlation does not equal causation? Because the evidence here indicates otherwise. Just sayin'...
Click to expand...
Click to collapse
Correlation assumed but unproven. Greenify has been around a long time with a large user base. The situation you describe appears to be an outlier.
M66B, developer of the popular XPrivacy app, is closing the official support thread for the app:
https://forum.xda-developers.com/xposed/modules/xprivacy-ultimate-android-privacy-app-t2320783
This thread is meant for any existing users to communicate with each other going forward.
*** Simply "Subscribe" to this thread to keep updated ***
.
This is the best privacy manager. But I really hope that we can use it on magisk as module. I don't want Xposed.
MaXi32 said:
This is the best privacy manager. But I really hope that we can use it on magisk as module. I don't want Xposed.
Click to expand...
Click to collapse
It's not possible,magisk can't hook into code,only xposed can do that
Magisk can only change and add files
Xposed can only change and add code
You can't turn an xposed module into a magisk module and vice-versa,just because they're both called modules doesn't mean they do the same thing
Huh? XPrivacy has always relied on Xposed (hence the name). Why should it suddenly be different?
altae said:
Huh? XPrivacy has always relied on Xposed (hence the name). Why should it suddenly be different?
Click to expand...
Click to collapse
Yeah,there's no other way for xPrivacy to work without xposed's ability to hook and modify app code at runtime
How would you configure Tiktok in Xprivacy?
Hello all,
How would you configure Tiktok in Xprivacy?
Thanks.
Xposed is lob
MaXi32 said:
This is the best privacy manager. But I really hope that we can use it on magisk as module. I don't want Xposed.
Click to expand...
Click to collapse
Magisk is only a root manger application.
And its modules are nothing but replacement of system files in mirrored system partition created by magisk.
Where xposed can hook Methods and resources.
Never underestimate xposed.
It has great role in reverse engineering of application and customisation.
Badly missing Xprivacy on magisk. Was anyone able to work with Xprivacy Lua ?
Samdroid18 said:
Badly missing Xprivacy on magisk. Was anyone able to work with Xprivacy Lua ?
Click to expand...
Click to collapse
Xprivacy and Xprivacy Lua are not magisk modules.
XprivacyLua is working well on my 2 x S8. One one Oreo and the other on pie.
The one on pie needs magisk to be able to install Edxposed.
May anybody help me to make Xprivacy compatibility to deny requets of libraries (loadLibrary) on Android 7, please?
Or to make the possibility to ALLOW or DENY "Accounts" category based on PARAMETERS?
How may I refresh Xprivacy to read database again without need to reboot?
Thank you very much.
XPL Is a must have Tool
it's a shame that XPL has been discontinued. I can no longer imagine an android smartphone without xpl.
XPL deserves support.
it's a shame that XPL has been discontinued. I can no longer imagine an android smartphone without xpl.
XPL deserves support.
Is there a way to completely delete the XPL settings? unfortunately my phone does not start as long as XPL is active. have probably made too many settings.
As soon as I reactivate the module, the phone no longer starts.
deleting data does nothing.
LinoPino221 said:
it's a shame that XPL has been discontinued. I can no longer imagine an android smartphone without xpl.
XPL deserves support.
it's a shame that XPL has been discontinued. I can no longer imagine an android smartphone without xpl.
XPL deserves support.
Is there a way to completely delete the XPL settings? unfortunately my phone does not start as long as XPL is active. have probably made too many settings.
As soon as I reactivate the module, the phone no longer starts.
deleting data does nothing.
Click to expand...
Click to collapse
If you do a search for Xposed, there is a uninstall ZIP file that you can flash using recovery mode that will uninstall Xposed, which will then disable Xprivacy and your phone should be able to bootup.
JohnCody said:
If you do a search for Xposed, there is a uninstall ZIP file that you can flash using recovery mode that will uninstall Xposed, which will then disable Xprivacy and your phone should be able to bootup.
Click to expand...
Click to collapse
e phone starts as soon as i deactivate edxposed. that's working.
I just want to delete all settings and data from xprivacylua. are there any special folders?
the normal deletion of the data does nothing
LinoPino221 said:
e phone starts as soon as i deactivate edxposed. that's working.
I just want to delete all settings and data from xprivacylua. are there any special folders?
the normal deletion of the data does nothing
Click to expand...
Click to collapse
I think you should be able to disable the Xprivacy "module" from within the xposed app, then reboot. Then uninstall xprivacy like you would any other app, then reinstall the xprivacy APK and it should start with default settings.
XPrivacy was way better than XPL, I don't know why M66B would dump it. I still have it running on my Galaxy S5 with Kitkat, it's not like it needs any updating, it's fine how it is. It just needs to run heh. Anyone know how I could get it running on a recent and supported version of Android (like Oreo) and EdXposed? Is it even possible? I'd like to help to work on it.
scarlion said:
XPrivacy was way better than XPL, I don't know why M66B would dump it. I still have it running on my Galaxy S5 with Kitkat, it's not like it needs any updating, it's fine how it is. It just needs to run heh. Anyone know how I could get it running on a recent and supported version of Android (like Oreo) and EdXposed? Is it even possible? I'd like to help to work on it.
Click to expand...
Click to collapse
XPrivacy doesn't work on recent Android versions anymore due to structural changes in Android, which is the main reason why XPrivacyLua was developed.
M66B said:
XPrivacy doesn't work on recent Android versions anymore due to structural changes in Android, which is the main reason why XPrivacyLua was developed.
Click to expand...
Click to collapse
What kind of structural changes? Ain't no hill for a climber.
Also XPL doesn't run with EdXposed, so it's in a worse position than XP from my point of view. Have to stick with my ancient S5 for now.
scarlion said:
What kind of structural changes? Ain't no hill for a climber.
Click to expand...
Click to collapse
In fact many things were changed, but the main obstacles are tighter security (SELinux), how the activity manager service works and how apps are being started. Since XPrivacy is not supported anymore, I am not going to provide more details, but both the source code of XPrivacy and XPrivacyLua are on GitHub, so you can check for yourself.
scarlion said:
...
Also XPL doesn't run with EdXposed, so it's in a worse position than XP from my point of view.
...
Click to expand...
Click to collapse
Really? My impression is that XPL and EdXposed runs fine.
Is there a way to hide the battery status? I have an annoying battery Warnung in my car every time the battery is less then 50% when my Smartphone is connected with Bluetooth. I cant disable that in the car hifi settings. Or can i send fake data?