I've got the following modules installed: Nottach Xposed, Wanam Xposed, XBlast Tools.
Each provides something unique that the rest don't have. The issue I'm having is that when I open up one of the modules, it loads it's settings and overwrites the other modules. Here is a sample scenario:
1) Open first module, set the number of signal bars to 6.
2) Open second module, but don't touch the default of 4 signal bars and change the color of the seekbar or something.
3) Restart.
4) The 4 bars overwrites the 6.
I know these conflicts arise with the territory when using multiple modules that have the same options for one setting. My question is, is there any possible way I can track the changes a module makes, and create a script from it that gets applied whenever I boot up my phone. Is that even possible?
It would be nice to have one script that can unify all the changes the modules make. I'm assuming it would have to be an Xposed module itself since the changes are made at startup. Anyone have any suggestions or tips I may find useful?
xdapowerapps said:
I've got the following modules installed: Nottach Xposed, Wanam Xposed, XBlast Tools.
Each provides something unique that the rest don't have. The issue I'm having is that when I open up one of the modules, it loads it's settings and overwrites the other modules. Here is a sample scenario:
1) Open first module, set the number of signal bars to 6.
2) Open second module, but don't touch the default of 4 signal bars and change the color of the seekbar or something.
3) Restart.
4) The 4 bars overwrites the 6.
I know these conflicts arise with the territory when using multiple modules that have the same options for one setting. My question is, is there any possible way I can track the changes a module makes, and create a script from it that gets applied whenever I boot up my phone. Is that even possible?
It would be nice to have one script that can unify all the changes the modules make. I'm assuming it would have to be an Xposed module itself since the changes are made at startup. Anyone have any suggestions or tips I may find useful?
Click to expand...
Click to collapse
Multiple Xposed modules is one of the best way to get your phone
all messed up... My suggestion is stick with you favorite module.
Good luck!
Misterjunky said:
Multiple Xposed modules is one of the best way to get your phone
all messed up... My suggestion is stick with you favorite module.
Good luck!
Click to expand...
Click to collapse
Well, it's a pain in the ass for the first time setup, but once everything is set, I don't have to touch it again which is plus. But if I decide to make one little change, things reset and I have to start again. Sigh. Wish all the All-in-One modules had the "On-Off" switch so they don't make any changes until you enable it and apply. Wishful thinking. :crying:
re: Xposed Modules
xdapowerapps said:
Well, it's a pain in the ass for the first time setup, but once everything is set, I don't have to touch it again which is plus. But if I decide to make one little change, things reset and I have to start again. Sigh. Wish all the All-in-One modules had the "On-Off" switch so they don't make any changes until you enable it and apply. Wishful thinking. :crying:
Click to expand...
Click to collapse
There is something else which could be done by the Xposed DEVS
to upgrade the app to make it a whole lot easier for all the users.
All the modules should create a log with time/date stamp along with the specific
changes made to the options and settings in the modules in a format which even
a noob or novice could read and fully understand all the details in the log.
Another thing which could be done to make things easier is to have a SAVE/RESTORE
option in all the modules just like like the better launchers have.
Misterjunky said:
There is something else which could be done by the Xposed DEVS
to upgrade the app to make it a whole lot easier for all the users.
All the modules should create a log with time/date stamp along with the specific
changes made to the options and settings in the modules in a format which even
a noob or novice could read and fully understand all the details in the log.
Click to expand...
Click to collapse
Agreed, that would be great to have on hand. Great idea. :highfive:
Related
I can no longer hold home to get to the task manager. Holding down home does nothing now and I can't figure out why or what I could have done to cause this. Restarting doesn't fix it. Anyone know how I can restore this function without reflashing? The last thing I did was install Xposed Framework with modules 'App Settings 0.4' and 'xMulti Window Mod 1.3' so I'm thinking that's what caused it but I'm not sure why.
ROM: Tweaked 2.4.1
Kernel: Stock
Your best bet is to try and disable the new modules in xposed. Or disable xposed all together Then reboot..... also there's nO need to post in multiple threads. Patience
Sent from my SGH-T889 using Tapatalk 4
deeznutz1977 said:
Your best bet is to try and disable the new modules in xposed. Or disable xposed all together Then reboot..... also there's nO need to post in multiple threads. Patience
Click to expand...
Click to collapse
Disabled the two modules and rebooted. That fixed it. Re-enabled them, rebooted, problem came back. Double checked and the modules are configured as instructed. Everything on my phone seems fine and working great except this one little issue and it's an annoying one. I don't want to give up this MOD so there must be a way to isolate this but I must admit I'm lost.
So I have a rooted Note 4 with stock ROM, and I recently installed Wanam Xposed. After installing this I have noticed that when I open the Phone App and go to Logs, it always defaults to missed calls, where before installing Wanam it defaulted to All Calls. Anyone know how to fix this? I cannot find the setting in Wanam that caused this (or if it even is Wanam), nor can I find any other setting for this.
http://forum.xda-developers.com/showthread.php?p=58365213
Since you already have wanam, just delete the highlighted line in the /system/csc/feature.xml and reboot.
samep said:
http://forum.xda-developers.com/showthread.php?p=58365213
Since you already have wanam, just delete the highlighted line in the /system/csc/feature.xml
Click to expand...
Click to collapse
Beautiful, thanks!!!
DrSeussFreak said:
Beautiful, thanks!!!
Click to expand...
Click to collapse
You're welcome. If you have to redo stock, upgrade to custom Rom or if/when we're fortunate to get Xposed for lollipop, remove the line before activating wanam. If not before, then after. Ideally, the primary file is the target for developers as I explained in the original post; avoids users breaking it with wanam but still functional for non-wanam users.
Sprint choose to be unique; this fixes that so wanam works as intended.
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
Seqrch plays tore there is tons of apps
Sent from my SAMSUNG-SM-N910T using XDA Free mobile app
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
If you are rooted use a file manager with an editor that has root capability (like File Manager HD) and go to /system. Make a backup copy of build.prop and then edit it to change the value of ro.sf.lcd_density from 480 to something lower, like 450, 400, or 360. I tried the latter and it worked. However the appearance of some native apps like phone or camera may become funky. IF you want everything to look normal you will have to install Xposed and do some stuff like this: http://forum.xda-developers.com/showthread.php?t=2507369
Be careful not to go too low with this value. People usually don't go below 320 because the phone may not reboot afterwards. Below 360 things are not even visible, at least for me.
najoor said:
If you are rooted use a file manager with an editor that has root capability (like File Manager HD) and go to /system. Make a backup copy of build.prop and then edit it to change the value of ro.sf.lcd_density from 480 to something lower, like 450, 400, or 360. I tried the latter and it worked. However the appearance of some native apps like phone or camera may become funky. IF you want everything to look normal you will have to install Xposed and do some stuff like this: http://forum.xda-developers.com/showthread.php?t=2507369
Be careful not to go too low with this value. People usually don't go below 320 because the phone may not reboot afterwards. Below 360 things are not even visible, at least for me.
Click to expand...
Click to collapse
Ok Thanks
ROADKING17 said:
Any way to change the Dpi on lollipop without using app settings since xposed does not work for touchwhiz
Click to expand...
Click to collapse
Before you attempt to use the guide that najoor suggested, be sure to backup your ENTIRE ROM and not just the build.prop file. Installing Xposed on many Note 3's and any TW devices for that matter, ends in disaster. Many are left in an infinite bootloop, causing you to need to wipe everything and reinstall your ROM.
ludeawakening said:
Before you attempt to use the guide that najoor suggested, be sure to backup your ENTIRE ROM and not just the build.prop file. Installing Xposed on many Note 3's and any TW devices for that matter, ends in disaster. Many are left in an infinite bootloop, causing you to need to wipe everything and reinstall your ROM.
Click to expand...
Click to collapse
I concur. I personally don't like Xposed anymore. It was fun the first few times I used it and then I realized it tends to be chaotic in the way it changes the system. In general any tool/software that changes things in an irreversible way without the user's explicit knowledge is in my opinion poorly written. I remember that when I had an ATT note 3 on Android 4.3 I rooted it and installed Xposed and some of its modules and was very content with myself. But then when the time came to upgrade to 4.4.2 the phone refused to do so because it saw my system as "altered in an unauthorized way". I unrooted it to no avail. I uninstalled Xposed and all its modules, once before and once after unrooting to no avail. Finally I sat down and started looking at the system files and Xposed had changed so many things without my knowledge that tracing all of them and reversing them took me forever. I had the luxury of using Safestrap back then to do trial and error but since there is no such thing for lollipop, if you don't have a custom recovery and you mess up, you will need to flash the ROM from scratch and lose your data in the process.
najoor said:
I concur. I personally don't like Xposed anymore. It was fun the first few times I used it and then I realized it tends to be chaotic in the way it changes the system. In general any tool/software that changes things in an irreversible way without the user's explicit knowledge is in my opinion poorly written. I remember that when I had an ATT note 3 on Android 4.3 I rooted it and installed Xposed and some of its modules and was very content with myself. But then when the time came to upgrade to 4.4.2 the phone refused to do so because it saw my system as "altered in an unauthorized way". I unrooted it to no avail. I uninstalled Xposed and all its modules, once before and once after unrooting to no avail. Finally I sat down and started looking at the system files and Xposed had changes so many things without my knowledge that tracing all of them and reversing them took me forever. I had the luxury of using Safestrap back then to do trial and error but since there is no such thing for lollipop, if you don't have a custom recovery and you mess up, you will need to flash the ROM from scratch and lose your data in the process.
Click to expand...
Click to collapse
I've never used Xposed and I never will, but I also have the resources and the knowledge to just change the stuff in the framework and SystemUI myself.
If I'm helping anyone upgrade their system, the first thing I ask is if they've installed Xposed or running a ROM that has it pre-installed. If they say yes I recommend them just starting over from scratch with OEM firmware, which is easy to do on any brand phone. You have Odin for Samsung, RSD Lite for Motorola, and fastboot for HTC to achieve this.
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
cescman said:
Changes made to gravity box, such as battery icon, long press defaults, and pretty much everything else, don't survive after a reboot. It works on the old nexus 5 running Android 6.0. Is it a problem of 6.0.1, or a problem of nexus 5x?
Click to expand...
Click to collapse
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
cescman said:
Thanks. I just checked that on the xposed forum, and people have various other issues as well on 6.0.1. Hopefully my previous small donation can give rovo an extra dose of coffee or beer, as a boost to his coding.
And I am using standard root method as well. Other modules that I used seems to be working fine. GB is working fine too, just that the changes don't survive a reboot
Click to expand...
Click to collapse
Then it's strange. There must be something different about our devices and the way they are set up. I haven't come across any of these issues whether on N5X or N5. My setup is:
- stock 6.0.1
- modified boot.img which allows SuperSU to work (found in Rooting guide thread in 5X forum)
- xposed framework v78
- GravityBox 6.0.2 (the only module I have installed)
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
cescman said:
I am on stock 6.0.1, and I guess the same modified boot image
SuperSU 2.5.2
Xposed framework v78 sdk23 64 bit
Gravity box 6.0.2
I have tried a few times, and I can confirm that all the changes I made disappear after a reboot.
Click to expand...
Click to collapse
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
C3C076 said:
It's a problem of the xposed framework and is probably related to how SeLinux policy is set.
There may be a difference related to root method: standard vs. systemless.
I use standard on my N5X without GB issues mentioned.
Rovo knows about these issues but has no solution yet.
Click to expand...
Click to collapse
C3C076 said:
Seems to be identical. Regarding SuperSU, I flashed BETA-SuperSU-v2.52.zip.
Click to expand...
Click to collapse
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
cescman said:
All the same. And I flashed via twrp 2.8.7.2
I am not sure but I guess it may be more difficult to solve this problem when it is not reproducible using the exact same setup?
Click to expand...
Click to collapse
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
C3C076 said:
Maybe worth checking how file permissions look like at filesystem level.
Attached screenshot with list of contents of these folders:
/data/data/com.ceco.marshmallow.gravitybox
and
/data/data/com.ceco.marshmallow.gravitybox/shared_prefs
Click to expand...
Click to collapse
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
cescman said:
My shared_prefs permission is rwx------
Just changed to rwxrwx--x as in your picture
and... reboot....
yes!!! problem solved!!!
Thank you.
Click to expand...
Click to collapse
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
C3C076 said:
Thanks for info. Now to only know what causes different permission sets.
Did you do something like "fix permissions" via recovery in the past?
Anyway, I'll try to think about checking and adjusting permissions of this folder at startup.
Although, it might be a little too late since access is necessary far earlier before device is fully booted but at least it would fix the permissions for the next reboot.
Click to expand...
Click to collapse
No, I didn't click fix permissions in recovery, although, as I now remember, installing xposed wasn't that smooth. After installation, I got some error messages saying some services is forced to stop, and I needed several reboots, and the system needed to optimise apps each time before the phone is boot up normally at the end
deleted
Hi there, uh... I will directly to question
I downloaded Quick Reboot from XDA labs apps, and it has many useful options to every user who likes to flash stuffs and do anything with their phone, so, I'd like to know if is there any way to get rid of that stock power off menu and add some new options like reboot to recovery, fastboot and others WITHOUT USING THINGS THAT BREAKS SAFETYNET SUCH AS XPOSED... See attached pictures to understand better please.
Thanks in advance for any answer!
Not as far as I know. You'd need to modify the system app that's controlling that. So either you are able to get that app, decompile it, change it and recompile it without errors and get it to install... Or you use XPosed. I don't think there is a way with tools like Magisk
Artim_96 said:
Not as far as I know. You'd need to modify the system app that's controlling that. So either you are able to get that app, decompile it, change it and recompile it without errors and get it to install... Or you use XPosed. I don't think there is a way with tools like Magisk
Click to expand...
Click to collapse
Hmm, okay, thanks
I thought someone could do that with magisk like they do to systemize apps and etc
xdaVTU said:
Hmm, okay, thanks
I thought someone could do that with magisk like they do to systemize apps and etc
Click to expand...
Click to collapse
Like I said, if you can get that app and modify it successfully no problem. But to make sense as a Magisk module that would need to work at least on every close-to-AOSP ROM and I don't think that's possible. Maybe I'm wrong and there actually is an easier method but then I'd be surprised that I don't know if it since I would like to have that too