Database Develop

Does not function on phones with Toybox - BLU STUDIO XL 2

Thank you for all you hard work, I have been a user for many releases prior and love that your software has always been "there and working well". So why only speak up when I have a problem, so for that I apologize.
I have managed to obtain a version of Xposed (Systemless) ported for Magisk installed on my phone (SDK 23) and while Magisk lists Xposed in its installed module list with a check box saying it is active, the Xposed menu shows the green notification area that says it is working, when I install XprivacyLua, and while after the installation of XprivacyLUa, in the Modules section of Xposed there is a check box showing that XprivacyLua is installed and active, the problem is that the Xprivacy app thinks it is not loaded. I sent trace logs captured via adb to the Xprivacy developer and he says that Xposed believes the XprivacyLua app is not installed (even though all indications are that it is active).
Someone who knows more about this than me stated my problem was likely with Toybox being on the phone and something about symlinks where he gave another suggestion about loading Busybox and then following with loading a BusyBox binary zip package via TWRP. All this does is render me not able to access MagiskManager any longer.
Do you know anything about such an issue and how I might get around it? I am saddened that using this valuable tool is being made so difficult from all the new hardware changes. I normally stick with age old phones, but accidents happen, the old one's cracked and my new one won't seem to work with Xposed.
Thanks!
BLU STUDIO XL 2 16/2G
MT6737
ARMv7 Processor rev4 (V71)
armv71

Is there anyone who can help me with my issue? I have poor eyesight and need a larger phone like the BLU, plus as often as I drop phones I cannot afford to buy the fancy, expensive and popular gaming models that everyone seems to purchase.
I am willing to do what ever it takes to resolve the issue, including running traces, submitting file structure maps or anything the developer needs to address the issue with Toybox or whatever the problem that is causing XprivacyLua not to be enabled by Xposed.
Thank you again.

Donphillipe said:
Is there anyone who can help me with my issue? I have poor eyesight and need a larger phone like the BLU, plus as often as I drop phones I cannot afford to buy the fancy, expensive and popular gaming models that everyone seems to purchase.
I am willing to do what ever it takes to resolve the issue, including running traces, submitting file structure maps or anything the developer needs to address the issue with Toybox or whatever the problem that is causing XprivacyLua not to be enabled by Xposed.
Thank you again.
Click to expand...
Click to collapse
What about making system run in permissive mode?
have you tried?
I have not "jumped" from superSU to majisk so my method is to use superSU.
I have a recovery install package that sets file in place to make permissive and force superSU to install systemless.
you can give a try.
the updater-script prints out a message it was made for "blu tank xtreme pro" but it is fine for other phones too. I made it for/ with other dev who wanted to have one step to make root and permissive.
I do not know how will respond to majisk, so better off to try ununstall that first, and start fresh.

[Xposed] (Security) Disable Quick Settings Pulldown on Lock Screen

This is just a simple Xposed module that disables pulling down the notification shade / quick settings tiles while on the lock screen (but doesn't break media player controls on lock screen). Only tested on Pixel 4 and Pixel 4 XL on Android 10 (more on this later).
Background: This has always been an annoying aspect of Android for me, and it's dumb from a security standpoint. Being able to pull down the quick settings tiles on a locked phone is dumb. Why hasn't Android natively built this in yet? Using this and Gravity Box to disable power menu on lock screen makes me feel a lot better in the event my phone ever gets lost or stolen. It's dumb that anyone can steal your phone and immediately toggle your settings (turn off WiFi, Mobile Data, toggle Airplane Mode, etc) and/or turn the phone off... I've been spoiled for years by the OG HTC devs (particularly LeeDroid and Team Venom) and their ROMs with these features baked in, so it's back to using Xposed to fill that gap for me and my wife, lol. Anyway, I pair these mods along with the Lockwatch app from Play Store and it gives me more peace of mind. Hey, anything to increase the chances of recovering a lost or stolen phone, am I right?
Credits / Technical Details: This module is based off of char101's published Xposed Repo module, and all credits and thanks should go to him. This is the first app / APK I've compiled so it was a nice learning experience, but it was all based off of his source and I really just needed to remove a few lines of code to get it to work properly with our phones. His mod worked fine and disabled the quick settings pull down on the lock screen, as intended. The problem was that it would also prevent media player controls from functioning (and I would assume other possible functions as well). To fix this, I just removed DISABLE2_NOTIFICATION_SHADE references from the code, leaving DISABLE2_NONE and DISABLE2_QUICK_SETTINGS untouched. The mod still works perfectly as intended. Only tested on Pixel 4 / 4 XL on Android 10. I'm sure it would work on other devices as well.
I really just did this on a whim for me and my wife's own phones and wasn't planning on sharing it, but I figure other people may have also wanted this for their P4's as well, so enjoy. Again, all thanks go to @char101!
Installation:
- Download .APK file attached to this post.
* If you have char101's original module installed already, I would highly recommend uninstalling it first.
- It's an Xposed module. Install the APK and enable in your Xposed Manager.
- Reboot and test.
Based on: https://repo.xposed.info/module/com.github.char101.qslock
Source for modified module: https://github.com/i5lee8bit/xposed-qslock-P4mod

thanks for this!!! any difference between this one and the one posted on the XL forums?

vdevl said:
thanks for this!!! any difference between this one and the one posted on the XL forums?
Click to expand...
Click to collapse
Nope, they are exactly the same. I have a 4 XL and got my wife the regular 4, and so I've been posting on both forums to share some of my findings on both devices. I just figured most 4-only owners probably won't be checking the 4 XL forums, and since this mod worked perfectly on my wife's phone I wanted to share with both communities. Glad to help though!
PS: Please try to refrain from quoting the entire OP, it makes the thread kind of cluttered. Just for future reference. =)

thanks much dude! gonna try edxposed with this module for 1st time after kitkat days. Miss those easy android days.
Appreciate the effort youre putting for sharing mods and patched boot imgs. Cool guy

i5lee8bit said:
This is just a simple Xposed module that disables pulling down the notification shade / quick settings tiles while on the lock screen (but doesn't break media player controls on lock screen). Only tested on Pixel 4 and Pixel 4 XL on Android 10 (more on this later).
Background: This has always been an annoying aspect of Android for me, and it's dumb from a security standpoint. Being able to pull down the quick settings tiles on a locked phone is dumb. Why hasn't Android natively built this in yet? Using this and Gravity Box to disable power menu on lock screen makes me feel a lot better in the event my phone ever gets lost or stolen. It's dumb that anyone can steal your phone and immediately toggle your settings (turn off WiFi, Mobile Data, toggle Airplane Mode, etc) and/or turn the phone off... I've been spoiled for years by the OG HTC devs (particularly LeeDroid and Team Venom) and their ROMs with these features baked in, so it's back to using Xposed to fill that gap for me and my wife, lol. Anyway, I pair these mods along with the Lockwatch app from Play Store and it gives me more peace of mind. Hey, anything to increase the chances of recovering a lost or stolen phone, am I right?
Credits / Technical Details: This module is based off of char101's published Xposed Repo module, and all credits and thanks should go to him. This is the first app / APK I've compiled so it was a nice learning experience, but it was all based off of his source and I really just needed to remove a few lines of code to get it to work properly with our phones. His mod worked fine and disabled the quick settings pull down on the lock screen, as intended. The problem was that it would also prevent media player controls from functioning (and I would assume other possible functions as well). To fix this, I just removed DISABLE2_NOTIFICATION_SHADE references from the code, leaving DISABLE2_NONE and DISABLE2_QUICK_SETTINGS untouched. The mod still works perfectly as intended. Only tested on Pixel 4 / 4 XL on Android 10. I'm sure it would work on other devices as well.
I really just did this on a whim for me and my wife's own phones and wasn't planning on sharing it, but I figure other people may have also wanted this for their P4's as well, so enjoy. Again, all thanks go to @char101!
Installation:
- Download .APK file attached to this post.
* If you have char101's original module installed already, I would highly recommend uninstalling it first.
- It's an Xposed module. Install the APK and enable in your Xposed Manager.
- Reboot and test.
Based on: https://repo.xposed.info/module/com.github.char101.qslock
Source for modified module: https://github.com/i5lee8bit/xposed-qslock-P4mod
Click to expand...
Click to collapse
thanks, mate, it's working perfectly on poco f3 android 12.1 lineageOS

Thank you so much for sharing this!!!!!!!

i5lee8bit said:
Nope, they are exactly the same. I have a 4 XL and got my wife the regular 4, and so I've been posting on both forums to share some of my findings on both devices. I just figured most 4-only owners probably won't be checking the 4 XL forums, and since this mod worked perfectly on my wife's phone I wanted to share with both communities. Glad to help though!
PS: Please try to refrain from quoting the entire OP, it makes the thread kind of cluttered. Just for future reference. =)
Click to expand...
Click to collapse
are you able to update the app to work with android 13. Am using a pixel 6 and the app doesnt work

v.konvict said:
are you able to update the app to work with android 13. Am using a pixel 6 and the app doesnt work
Click to expand...
Click to collapse
I was able to modify the code to run in android 13, see my reply at https://forum.xda-developers.com/t/...n-on-lock-screen.4076593/page-2#post-88165351

com.adobe.ims.accountaccess (Adobe Account Access) seems to detect Magisk, even while hidden.

H! So I am actually unsure where to post this..
Here's hoping you can figure something out and not be mad at me if this is the wrong place to post this.
Initially, i was going to post this as a Bug report on Github. However, I figured this was not correct.
Technically speaking this also isn't really an issue with magisk itself, more that adobe might have found a way to circumvent magisk anti detection methods.
In short: The App "Adobe Account Access" (com.adobe.ims.accountaccess on the play store: https://play.google.com/store/apps/details?id=com.adobe.ims.accountaccess) seems to have found a way to detect magisk and/or root, even though root detection is hidden in magisk.
The App just displays a prompt, saying "Device not supported. Sorry, your phone is not supported for Adobe Account Access.", even though the device used should be supported.
I checked with adobe community support on whether my Phone is supported or not and according to them, it should indeed be supported: https://community.adobe.com/t5/acco...-access-app-device-not-supported/m-p/11696613
I suspect they have found a way to get around all magisk anti detection methods and i would be grateful if someone would be kind enough to check if there is a workaround or if magisk's detection prevention needs an update.
Unfortunately, i don't have much more to say other than that..
There aren't any magisk log entries that would indicate something went wrong (only entries mentioning the app are"i" loglevel, one coming from hide_list_add and one coming from proc_monitor).
I could not find anything out of the ordinary in the logcat, although i suppose i could be more thorough with my search.
My technical/general info would be:
Magisk Version used: 22.0 (22000) (18)
SafetyNet integrity: Both basicIntegrity AND ctsProfile = pass; evalType = BASIC
ROM used: OxygenOS 10.0.11.GM21BA
Android version: 10
Device name: OnePlus 7 Pro
"Adobe Account Access" App version: 1.6
+++ Please feel free to ask for any additional info in case I missed it +++
Thanks in advance for any productive suggestion!

When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list, and with the Magisk app unhidden.

Didgeridoohan said:
When does it display this "device not supported" message? I tested just now and could log in and set everything up without even adding the app to the Hide list.
Click to expand...
Click to collapse
Oh? That is peculiar.. Damn, that implies an issue somewhere else i reckon ://
It displays it immediately after launching the app. The very first screen..
What phone and which OS (/ROM) are you using? Might just be that my phone is genuinely not supported and the folks over at the adobe community forum lied when saying my phone should be compatible..
Also, which android version are you on if you don't mind me asking?

You don't have any modules installed? No edxposed or lsposed, or magisk modules?
Have you tried root detection apps like Root Beer Fresh to see if indeed the app is unable to detect root? If you try any such app, remember to add it to the Magisk Hide list beforehand, otherwise the app will clearly detect root.

It's a OnePlus 3T with Android 9 ArrowOS. As stated above, it could very well be a module, like EdXposed. Or a root app, or a file or folder on your device, or something completely different.
It's not detecting Magisk at least, that's for sure...
General root hiding tips:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

@Barrel Titor
Samsung Galaxy S7 Custom 9.0 Pie, Magisk 22 root with random name, application without hiding works fine.

Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.

Barrel Titor said:
Hi all!
First of all: Apologies! I meant to respond sooner to this, but work has kept me occupied and the one time I actually was available, XDA Forums went down into maintenance mode..
Secondly: Sorry for maybe jumping the gun here a bit!
It does look like I should have tested this issue a bit more! I am definitely going to keep on trying to fix this on my own using the resources and methods you have suggested!
I have tested com.adobe.ims.accountaccess on my sisters unrooted OnePlus Nord.. It works fine there, which is really confusing. None of the other apps I am using show this sort of issue :c Not even my banking app!
@mario0318 Thanks for your suggestion! I know it is good practice to remove/disable all your modules. However, none of the modules I have currently installed are particularly large and they certainly do not modify much compared to what is possible. I am going to attach a list to this response, however I am also going to try disabling them one by one and see if I can find the culprit! Unfortunately, I will not be able to disable the "Google Dialer Framework" module, since it causes the device to bootloop if the google dialer app is still present.
Here is a list of all the modules I have installed and enabled at the moment:
Spoiler
App Systemizer (Terminal Emulator)
Busybox for Android NDK
Google Dialer Framework
Looki75 Product Sans font
Systemless Hosts
ViPER4ANDROID FX
Honourable mentions (these modules are completely DISABLED):
Spoiler
Riru
Riru - EdXposed
However, please note again that SafetyNet seems to be INTACT, with "basicIntegrity" and "ctsProfile" still passing and "evalType" being "BASIC".
In any case. Thanks to everyone for their contribution! I really appreciate any suggestion!
Edit: @mario0318 right after I posted this message, I went ahead and gave "RootbeerFresh" a shot. It does not detect root when it is hidden from it. This makes my leading theory to be that the app truly does not support OnePlus 7 Pro devices. Wouldn't know why it doesn't support this model in particular though. Until I either unroot or find someone with the same device, willing to install Adobe Account Access, i can't say for sure though.
Click to expand...
Click to collapse
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.

mario0318 said:
So upon Google searching "oneplus 7 pro adobe account access" it appears to be a common problem.
Click to expand...
Click to collapse
I cannot find any results using this search term on google other than my own post on the adobe community forums.. This one: https://community.adobe.com/t5/acco...access-app-device-not-supported/td-p/11695914

@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?

Barrel Titor said:
@mario0318 do you happen to know a way to somehow "pretend" to the app that i am in fact using a different phone? Something that would allow me to make the app believe it is running on a different device?
Click to expand...
Click to collapse
Well, the well known magisk module MHPC or Magisk Hide Props Config comes to mind. You can change device fingerprints and maybe also give the Device Simulation feature a go, or custom edit any range of configurable props.
You could do so without the module editing the build.props yourself. Or if you stick with edxposed and deal with not having magisk manager's hide enabled, perhaps any of the device spoofers on the xposed repo could fool the app. Or Sudohide if you set Adobe app to hide from any and all apps that are root relevant. May also consider removing directories in your internal and removable storage for things like TWRP or PBRP, Titanium Backup, xposes, etc, you know, things that a simple media scan looking for any sign of root apps might pick up.
But for now, I'd give MHPC a try and change device fingerprint and maybe enable device simulation if simple fingerprint change doesn't work.

I'm having the same issue on a rooted OnePlus 8T

Same for me on op7 pro. Hiding with somiko but Adobe still not working. Nor could I bypass square, it notes root when it pairs Bluetooth

Question Magisk/Root procedure for 5a 5G?

Hey all,
I purchased my new 5a after seeing various headlines about how the Google Dialer would allow you to opt in to automatic call recording. That's incredibly helpful for my job, and a major reason why I've kept my OnePlus 6 for the past few years, but now the battery is barely getting through half the day.
It looks like Google is restricting auto calls to outside the US, which sucks because I live in a one-party consent state and always ask for permission to record.
Magisk could be the answer since it has a few modules for other Pixels to get auto call recording. However, do we know if we can apply the same method for Magisking the 5 to the 5a? I figure it may carry over because these two devices are so similar in specs and software, but I'd like to make sure before getting into the process.

Yes, you can. See screenshot of my rooted 5a. I have the JP version but there's no reason why it shouldn't work on the US version too.

Ehikes said:
Hey all,
I purchased my new 5a after seeing various headlines about how the Google Dialer would allow you to opt in to automatic call recording. That's incredibly helpful for my job, and a major reason why I've kept my OnePlus 6 for the past few years, but now the battery is barely getting through half the day.
It looks like Google is restricting auto calls to outside the US, which sucks because I live in a one-party consent state and always ask for permission to record.
Magisk could be the answer since it has a few modules for other Pixels to get auto call recording. However, do we know if we can apply the same method for Magisking the 5 to the 5a? I figure it may carry over because these two devices are so similar in specs and software, but I'd like to make sure before getting into the process.
Click to expand...
Click to collapse
Go to Settings -> About Phone. At the bottom is your build number. Go to https://developers.google.com/android/images and download the image that matches your version, probably .007.
Extract boot.img from it and adb push it to /sdcard. Have magisk patch that and save it. adb pull that patched boot.img and make sure you have OEM Unlock enabled in Developer Options. After confirming that, reboot to fastboot and run 'fastboot flashing unlock'. This will likely wipe your phone. Once that's done, reboot back into fastboot and run 'fastboot flash boot <local path to patched boot.img>' Now you have magisk installed. You can also install LSPosed and XPrivacyLua if you want to tinker with that or the Universal SafetyNet Fix at: https://github.com/kdrag0n/safetynet-fix/releases. Just download 1.2.0 and adb push it to your phone and have magisk install it.

himom said:
Go to Settings -> About Phone. At the bottom is your build number. Go to https://developers.google.com/android/images and download the image that matches your version, probably .007.
Extract boot.img from it and adb push it to /sdcard. Have magisk patch that and save it. adb pull that patched boot.img and make sure you have OEM Unlock enabled in Developer Options. After confirming that, reboot to fastboot and run 'fastboot flashing unlock'. This will likely wipe your phone. Once that's done, reboot back into fastboot and run 'fastboot flash boot <local path to patched boot.img>' Now you have magisk installed. You can also install LSPosed and XPrivacyLua if you want to tinker with that or the Universal SafetyNet Fix at: https://github.com/kdrag0n/safetynet-fix/releases. Just download 1.2.0 and adb push it to your phone and have magisk install it.
Click to expand...
Click to collapse
So I actually did this a couple days ago with the universal safetynet fix. Ipassed safetynet on magisk but googlepay doesnt work. Does googlepay work for you?

exile1ck said:
So I actually did this a couple days ago with the universal safetynet fix. Ipassed safetynet on magisk but googlepay doesnt work. Does googlepay work for you?
Click to expand...
Click to collapse
I haven't had a chance to try it yet. I have the card added but I've yet to pay with it. Maybe later today I'll give it a whirl.

It doesn't look like there are valid device fingerprints for the 5a yet in MagiskHide Props Config, so I'm not sure how you're able to pass basic ctsProfile checks.
I've rooted and have installed the universal safetynet fix, but until there is a 5a fingerprint, I'm not sure how I can pass safetynet.

nsoult said:
It doesn't look like there are valid device fingerprints for the 5a yet in MagiskHide Props Config, so I'm not sure how you're able to pass basic ctsProfile checks.
I've rooted and have installed the universal safetynet fix, but until there is a 5a fingerprint, I'm not sure how I can pass safetynet.
Click to expand...
Click to collapse
isnt the magiskhide project coming to an end though?

exile1ck said:
isnt the magiskhide project coming to an end though?
Click to expand...
Click to collapse
yes. There will be another program that comes along. The main dev for Magisk got hired by google, so...

I have a Pixel 2 XL. It's rooted on Android 10 still. I never even upgraded to Android 11 because by the time it came out I was already sick of dealing with the rooting updates. I don't care what anybody here says it's always a pain in the ass. It takes 3 to 4 hours to get everything set back up right after rooting. The time to back up everything before you start has to be considered. And when things go wrong you spend a whole weekend making them right. I don't have time for it anymore.
I most enjoy my EX kernels ability that allows me to sweep to sleep the display. I love this because it's handy and makes it so my screen off button (power button) is basically never used. It never fails this way. This means I never have to tear my phone apart to replace mechanical components.
I enjoy adaway. I enjoy YouTube vanced. I enjoy viper for Android. I enjoy substratum. I enjoy button mapper. I really, really enjoy Tulsa divers pixel launcher mods that allow me to make the buttons on the screen smaller to give me more screen real estate, but I think that hasn't been available since Android 11. You can no longer modify button icons from what I understand. I don't know if this is still true. I know there are rootless versions of substratum and the YouTube advanced, but when I last read about them years ago they were limited as compared to the root versions.
I leaned towards root being basically worthless, not worth the time, and more of a pain in the ass for a basic user who's not a developer. If I get the Pixel 5a or the Pixel 6 is rooting still worth it in 2021? Are there any rootless versions of the things I've mentioned here that would satisfy all my likes and needs I've mentioned here on Android 12 on a Pixel 5A or Pixel 6?

in case anyone cares, magiskhide props config module was updated recently and I was able to use it to force basic attuestation, so my 5a is now passing safetynet checks.

Schroeder09 said:
I have a Pixel 2 XL. It's rooted on Android 10 still. I never even upgraded to Android 11 because by the time it came out I was already sick of dealing with the rooting updates. I don't care what anybody here says it's always a pain in the ass. It takes 3 to 4 hours to get everything set back up right after rooting. The time to back up everything before you start has to be considered. And when things go wrong you spend a whole weekend making them right. I don't have time for it anymore.
I most enjoy my EX kernels ability that allows me to sweep to sleep the display. I love this because it's handy and makes it so my screen off button (power button) is basically never used. It never fails this way. This means I never have to tear my phone apart to replace mechanical components.
I enjoy adaway. I enjoy YouTube vanced. I enjoy viper for Android. I enjoy substratum. I enjoy button mapper. I really, really enjoy Tulsa divers pixel launcher mods that allow me to make the buttons on the screen smaller to give me more screen real estate, but I think that hasn't been available since Android 11. You can no longer modify button icons from what I understand. I don't know if this is still true. I know there are rootless versions of substratum and the YouTube advanced, but when I last read about them years ago they were limited as compared to the root versions.
I leaned towards root being basically worthless, not worth the time, and more of a pain in the ass for a basic user who's not a developer. If I get the Pixel 5a or the Pixel 6 is rooting still worth it in 2021? Are there any rootless versions of the things I've mentioned here that would satisfy all my likes and needs I've mentioned here on Android 12 on a Pixel 5A or Pixel 6?
Click to expand...
Click to collapse
I cannot live without YouTube Vanced or Viper4Android, and I have found no alternative. Magisk rooting is pretty easy though, so I don't think it's that much of a hassle.
nsoult said:
in case anyone cares, magiskhide props config module was updated recently and I was able to use it to force basic attuestation, so my 5a is now passing safetynet checks.
Click to expand...
Click to collapse
Wow holy you're right it is super recent, thanks for the update.

Schroeder09 said:
I have a Pixel 2 XL. It's rooted on Android 10 still. I never even upgraded to Android 11 because by the time it came out I was already sick of dealing with the rooting updates. I don't care what anybody here says it's always a pain in the ass. It takes 3 to 4 hours to get everything set back up right after rooting. The time to back up everything before you start has to be considered. And when things go wrong you spend a whole weekend making them right. I don't have time for it anymore.
I most enjoy my EX kernels ability that allows me to sweep to sleep the display. I love this because it's handy and makes it so my screen off button (power button) is basically never used. It never fails this way. This means I never have to tear my phone apart to replace mechanical components.
I enjoy adaway. I enjoy YouTube vanced. I enjoy viper for Android. I enjoy substratum. I enjoy button mapper. I really, really enjoy Tulsa divers pixel launcher mods that allow me to make the buttons on the screen smaller to give me more screen real estate, but I think that hasn't been available since Android 11. You can no longer modify button icons from what I understand. I don't know if this is still true. I know there are rootless versions of substratum and the YouTube advanced, but when I last read about them years ago they were limited as compared to the root versions.
I leaned towards root being basically worthless, not worth the time, and more of a pain in the ass for a basic user who's not a developer. If I get the Pixel 5a or the Pixel 6 is rooting still worth it in 2021? Are there any rootless versions of the things I've mentioned here that would satisfy all my likes and needs I've mentioned here on Android 12 on a Pixel 5A or Pixel 6?
Click to expand...
Click to collapse
My portfolio of root 'enjoys' differs a bit by overall ROI sentiment around rooting is similar. I stopped after Pie and never looked back. Much of what previously required root can now be accomplished via other means. I do miss being master of my gizmos but there are bigger fish to fry in the world of worries.

Adblock?

peikojose said:
Adblock?
Click to expand...
Click to collapse
This is a non-root version of AdAway I take it?

Schroeder09 said:
This is a non-root version of AdAway I take it?
Click to expand...
Click to collapse
Most "adblocking" programs are standalone, in the case of android, Adblock has its own browser. Some other browsers that do that are like Brave. However they obviously only work within the application, AdAway does hosts file level blocking so it works throughout the entire OS, so this worked really pleasantly for me from those stupid pop-up ads or the ones that take up quarter of the screen on some apps.

liberatorx3 said:
Most "adblocking" programs are standalone, in the case of android, Adblock has its own browser. Some other browsers that do that are like Brave. However they obviously only work within the application, AdAway does hosts file level blocking so it works throughout the entire OS, so this worked really pleasantly for me from those stupid pop-up ads or the ones that take up quarter of the screen on some apps.
Click to expand...
Click to collapse
I never realized brave blocked ads. It's the browser I use. I thought it just blocked third party tracking cookies or something that happen in the background. The ads I notice that are blocked are the broken link ads blocked by AdAway.
When i started rooting I got AdAway just because of the hype and mentions I saw all the time. I didn't see what the big deal was but figured since I was rooted I might as well get all the benefits for the hard work. I have bought in at this point. Going to some sites on my work phone is a real pain. The bombardment of ads is NUTS. Some sites are unusable. This isn't a problem on my rooted p2xl with AdAway.
My camera just failed though. When I replaced it and the battery a couple nights ago I cracked the screen. It isn't shattered beyond use or anything. In fact I don't think most would even notice unless I pointed it out. I still think I'm going to be going to the 5a or p6 pro based on the reviews that I start to see after a couple months' use for each of these two variants.
If someone could figure out a smooth way to do updates and stay rooted without having to hook up to a PC and spend 3 hours doing it id never think about leaving root. It's a PITA though.

Schroeder09 said:
I never realized brave blocked ads. It's the browser I use. I thought it just blocked third party tracking cookies or something that happen in the background. The ads I notice that are blocked are the broken link ads blocked by AdAway.
When i started rooting I got AdAway just because of the hype and mentions I saw all the time. I didn't see what the big deal was but figured since I was rooted I might as well get all the benefits for the hard work. I have bought in at this point. Going to some sites on my work phone is a real pain. The bombardment of ads is NUTS. Some sites are unusable. This isn't a problem on my rooted p2xl with AdAway.
My camera just failed though. When I replaced it and the battery a couple nights ago I cracked the screen. It isn't shattered beyond use or anything. In fact I don't think most would even notice unless I pointed it out. I still think I'm going to be going to the 5a or p6 pro based on the reviews that I start to see after a couple months' use for each of these two variants.
If someone could figure out a smooth way to do updates and stay rooted without having to hook up to a PC and spend 3 hours doing it id never think about leaving root. It's a PITA though.
Click to expand...
Click to collapse
Do you root with Magisk? It's definitely a lot easier now. https://topjohnwu.github.io/Magisk/ota.html
Doing updates and staying rooted was a PITA for me too, I ended up just never updating haha. In fact, my P2 is still running some old custom 9.1 version.

liberatorx3 said:
Do you root with Magisk? It's definitely a lot easier now. https://topjohnwu.github.io/Magisk/ota.html
Doing updates and staying rooted was a PITA for me too, I ended up just never updating haha. In fact, my P2 is still running some old custom 9.1 version.
Click to expand...
Click to collapse
Yes. I use magisk, and that's exactly what I did. I have yet to (never will on this phone anymore) update to android 11 because I KNEW such a big OS change would leave my phone broken for days. One of the big things I like on my phone is Tulsa divers modified button bar icons and making the bar a lot smaller, so it uses less screen real estate. When 11 came out I read that the icons couldn't be modified. Not sure if that's correct. It's been too long. Regardless, I just stopped updating because of the potential for a bad couple days, and even when things went well I never wanted to spend the 3-4 hrs to back the phone up and get everything just like it was before after booting back up into the new update.
It's easier to update and root now than it was when I had to download the update, open it, remove "-w" from the flashall.bat file, flash twrp, flash magisk, and then re-install all the modules or the ones that were messed up or inactive from the update?

This is my process, ymmv:
I keep my os, etc stock. I run mostly the latest updates, however, there have been times I have skipped a few monthlies.
step 1: go to google's developers site to download the latest factory image.
step 2: unzip, extract boot.img, adb push it to my phone
step 3: edit either the .bat file or the .sh file depending on whether I'm using windows or wsl2, remove the -w
step 4: reboot into fastboot, execute .bat or .sh
step 5: reboot, open magisk, patch boot.img that I pushed in step 2, adb pull patched boot to computer
step 6: reboot into fastboot, run `fastboot flash boot [patched image file name]`, repeat command for boot_a or boot_b
step 7: reboot, verify in magisk that root is ok
pretty simple, I think, and only takes like 10 minutes of my time. I don't see it as burdensome, but I'm not sure how the future it going to look - the steps described above was my process for my old pixel 4xl, so with magisk's developer working for google now, I'm not sure this will continue to be as easy if I want to continue to keep safetynet checks working on my pixel 5a.

Schroeder09 said:
Yes. I use magisk, and that's exactly what I did. I have yet to (never will on this phone anymore) update to android 11 because I KNEW such a big OS change would leave my phone broken for days. One of the big things I like on my phone is Tulsa divers modified button bar icons and making the bar a lot smaller, so it uses less screen real estate. When 11 came out I read that the icons couldn't be modified. Not sure if that's correct. It's been too long. Regardless, I just stopped updating because of the potential for a bad couple days, and even when things went well I never wanted to spend the 3-4 hrs to back the phone up and get everything just like it was before after booting back up into the new update.
It's easier to update and root now than it was when I had to download the update, open it, remove "-w" from the flashall.bat file, flash twrp, flash magisk, and then re-install all the modules or the ones that were messed up or inactive from the update?
Click to expand...
Click to collapse
Are you talking about these navbar Icons? I converted them to vector files and they still work for me (i'm on Android 12-Pixel 4XL). I'm probably going to get one of the Pixel 6 phones. I was going to hold out until the punch hole camera went instead to "under the screen" but my Pixel 3XL died and I no longer have a backup phone.

New Xposed API Proposal

We are now working on the new Xposed API, which allows modules to get / set scope, to get framework info, and to store configs across apps without the embarrassing New-XSharedPreferences interface. The API library will be released to GitHub/libxposed and maven central after it is ready.
Now we are considering removal of resources hook in the incoming new API, so we need to know whether it is still needed or unreplaceable for some modules.
About why we want to remove this API: Resources hook is very hard to maintain and is even not fully supported now under some frameworks (e.g. Taichi). So even if we keep it, it will be maintain-only.
Old modules can still use this feature. We are just considering remove it in the new API.
You can vote at the LSPosed Telegram group or write your opinion here. Also we are glad to hear your suggestions about the new API.

@AndroidX @siavash79 @Dark_Eyes_ @firefds @David B. @Quinny899 @wanam
Just mentioning you guys since you're all active here on XDA. Please see the first post.
Regards,
shadowstep
Senior Moderator

Dr-TSNG said:
We are now working on the new Xposed API, which allows modules to get / set scope, to get framework info, and to store configs across apps without the embarrassing New-XSharedPreferences interface. The API library will be released to GitHub/libxposed and maven central after it is ready.
Now we are considering removal of resources hook in the incoming new API, so we need to know whether it is still needed or unreplaceable for some modules.
About why we want to remove this API: Resources hook is very hard to maintain and is even not fully supported now under some frameworks (e.g. Taichi). So even if we keep it, it will be maintain-only.
Old modules can still use this feature. We are just considering remove it in the new API.
You can vote at the LSPosed Telegram group or write your opinion here. Also we are glad to hear your suggestions about the new API.
Click to expand...
Click to collapse
Thanks for getting opinions
1. Xshared preferences interface overhaul is good news since it was always unstable for me. I personally switched to remote preferences API for AOSPMods
2. When going to systemUI and framework, it's sometimes very difficult and complicated to change some variable values through Xposed, specially with R8 code optimizations which dramatically limit the points we can hook into code.
There are two workarounds I know of, being Xposed resource hooking that can be also dynamic in runtime, or overlays, which being static, still limit the way we can change resources dramatically.
So, I'd really suggest keeping it in the API

siavash79 said:
2. When going to systemUI and framework, it's sometimes very difficult and complicated to change some variable values through Xposed, specially with R8 code optimizations which dramatically limit the points we can hook into code.
Click to expand...
Click to collapse
For R8 code optimizations, we introduced a new API to parse dex file, which allows modules to find methods/fields more accurately.
Anyway if we finally decide to keep resources hook API, do you have any suggestions on keeping/adding/removing specific methods of it or refine it to a more modern interface?

Perfect news.
About resource hooking, few things to note are that: it can't differentiate between different resource files, for example normal values vs landscape or dark/light values. It would be great if there's a way to push different values to different resource files.
Also, there are more limitations when talking about special resources such as themes. As an example, in AOSPMods, one of the reasons it's a magisk module instead of being a normal APK is that overlay files have to be used in cases that need modification of theme resources and that can't be done via resource hooking.
I personally love to get a more complete/flexible resource hooking API, but I completely understand if that's too much to ask. So even keeping it as currently is would be good enough

Thank you @shadowstep for bringing this to my attention!
Dr-TSNG said:
We are now working on the new Xposed API, which allows modules to get / set scope, to get framework info, and to store configs across apps without the embarrassing New-XSharedPreferences interface. The API library will be released to GitHub/libxposed and maven central after it is ready.
Click to expand...
Click to collapse
That's wonderful news, although I do not quite understand what you have against the new XSharedPreferences interface. I use it in my modules, and I've never had any issues with it.
Dr-TSNG said:
Now we are considering removal of resources hook in the incoming new API, so we need to know whether it is still needed or unreplaceable for some modules.
About why we want to remove this API: Resources hook is very hard to maintain and is even not fully supported now under some frameworks (e.g. Taichi). So even if we keep it, it will be maintain-only.
Old modules can still use this feature. We are just considering remove it in the new API.
Click to expand...
Click to collapse
I am not currently using the resources hook in any of my modules, so removing it would not impact me, but even so, I'm not a fan of the suggestion to get rid of it completely. I think that at the very least, it should be kept as maintain-only. It is unfortunate that it does not work with Taichi, but given that Taichi isn't a true Xposed implementation, I'm not sure that it's worth worrying about.

This looks great, I've been waiting for it since the initial issue talking about it. Prefs are always a pain to handle, and while the "new" method worked, I always preferred to use a Content Provider, which was nerfed in Android 12.
Really like the idea of setting the scope, it would be beneficial to the Xposed part of DarQ, the only suggestion I have is to make sure it includes some sort of "am I enabled?" check - currently I use self hooks (literally the module hooking itself and changing a method returning false to true) to verify it's enabled, but it doesn't seem to be foolproof as people sometimes still complain it doesn't work.

Quinny899 said:
the only suggestion I have is to make sure it includes some sort of "am I enabled?" check
Click to expand...
Click to collapse
Of course does, and the module app can get more info about the the Xposed state like it's under which framework and which version, and whether it is rootless or not without self-hooking.
You can view the detail here.

@shadowstep Thanks for the head up.
Glad to see a new api to manage configs across apps, shared prefs has been always painful to handle even with the new-xshared prefs.
I would suggest having an api to get the version name of scope's package, I'm aware of some workarounds that help get the version name, but it's not a reliable solution on the latest Android versions, this information is needed for logging/debugging purposes.
@Dr-TSNG thanks and keep up the good work.

@Dr-TSNG Thanks for new api I was wating for this api from more then 1 year coz when I build my first module (Android Faker) its was really pain in ass coz of Xsharedpreference after some research I found better solution which was remote preference but Quinny899 mention in Github issue that its not work in android 11 so after that I move to new Xsharedpreference which was introduce by lsposed team and its working great but its still create issue in some devices so I think it will be a better solution if we get it soon and I am not sure about resources hook coz I don't use it before .

The problem with xshared preferences is that if the apk is a system app it won't work for some reason. Only works on user apps

siavash79 said:
The problem with xshared preferences is that if the apk is a system app it won't work for some reason. Only works on user apps
Click to expand...
Click to collapse
Interesting. I use XSharedPreferences in a System Framework hook and haven't had any issues with it.

David B. said:
Interesting. I use XSharedPreferences in a System Framework hook and haven't had any issues with it.
Click to expand...
Click to collapse
Is your module installed as APK or as magisk module?
Try mounting it to system through magisk and preferences will stop working

siavash79 said:
Is your module installed as APK or as magisk module?
Try mounting it to system through magisk and preferences will stop working
Click to expand...
Click to collapse
It's installed as an APK. I misunderstood what you had said earlier. I thought you meant that the hook doesn't work when you try to use it on system APKs. I didn't realize that you meant that it doesn't work when the module is itself a system APK.

siavash79​Yeah I agree with this and in my testing if you set target sdk 23 its doesn't matter if its as system app or user its work without any issues but its not worth coz it have some other issues

Thank you for accepting the API invokeSpecial() !
Add invokeSpecial · libxposed/[email protected]
Fix #2
github.com
Implement invoke special and new instance special · LSPosed/[email protected]
LSPosed Framework. Contribute to LSPosed/LSPosed development by creating an account on GitHub.
github.com
Looking forward to the new API release.
Happy Chinese New Year!

I just want to see @M66B happy again

Somewhat unrelated, but is there any chance of seeing original Xprivacy return or compatibility? I think it's a lot better than Lua

lawrencee said:
Somewhat unrelated, but is there any chance of seeing original Xprivacy return or compatibility? I think it's a lot better than Lua
Click to expand...
Click to collapse
No. Xprivacy will never "return".
XPrivacyLua is the best ever