Related
Install and run Exploit apk to get root:
Install XposedInstaller-ICS_JB-rc2.apk, follow instructions on post.
Install XposedMultiWindow.apk.
Open the Xposed Installer app (installed in step 2). Click 'Modules', then check 'xMulti Window Mod', and reboot. (activates the run-time patch allowing all apps to be multiwindow compatible).
BTW, there are more cool Xposed modules (like call recording, per-app dpi, and no 100% battery notification) you can download here. Xposedframework eliminates the need for stock rom chefs imho.
Amazing
h0tw1r3 said:
Install and run Exploit apk to get root:
Install XposedInstaller-ICS_JB-rc2.apk, follow instructions on post.
Install XposedMultiWindow.apk.
Install MultiWindow Control app (allows you to customize available apps).
Open the Xposed Installer app (installed in step 2). Click 'Modules', then check 'xMulti Window Mod', and reboot. (activates the run-time patch allowing all apps to be multiwindow compatible).
BTW, there are more cool Xposed modules (like call recording, per-app dpi, and no 100% battery notification) you can download here. Xposedframework eliminates the need for stock rom chefs imho.
Click to expand...
Click to collapse
Thanks so much this is brilliant!! :good:
So if I installed the new stock deodexed rooted Rom from teshxx (which has the new Tmo multi window update) I can still use the above method to add multiple apps to multiwindow?
britchris1 said:
So if I installed the new stock deodexed rooted Rom from teshxx (which has the new Tmo multi window update) I can still use the above method to add multiple apps to multiwindow?
Click to expand...
Click to collapse
Yes, you can use xposed with any rom.
Thanks for this just found this tool today I didnt want to go through the trouble of custom roms so glad we could get this done with just root! One question tho anyway to change it so every able doesnt show on the big multiview app aftee clicking edit I have a bunch of apps and it lags when scrolling.
Thanks again!
♥Galaxy Note ll
How do I know if the multi-window works? I followed all these steps, but what I got is exactly the same as before. Where is the multi-window and how to call it out? Tried long press the return button but nothing happened. Or it does not work for T-mobile device?
I have completed the installation and have to admit that this made my night. Huge props to the person who developed this. Installing on my partners note 2 as well. Looking forward to seeing what else xposed comesbup with
Sent from my SGH-T889 using Tapatalk 2
Kuime said:
How do I know if the multi-window works? I followed all these steps, but what I got is exactly the same as before. Where is the multi-window and how to call it out? Tried long press the return button but nothing happened. Or it does not work for T-mobile device?
Click to expand...
Click to collapse
Did you do the T-mobile update from yesterday? If so toggle multi window on in Settings--->Display. If you've done that then hold down your back button for a couple seconds the multi window should pop up at the left. You can hold back to hide it again.
Kuime said:
How do I know if the multi-window works? I followed all these steps, but what I got is exactly the same as before. Where is the multi-window and how to call it out? Tried long press the return button but nothing happened. Or it does not work for T-mobile device?
Click to expand...
Click to collapse
Updated the subject. As the post above states, you need to be running the newest update.
This situation is an excellent example of why the xposed framework is such a great way to mod.
Had this been a standard flash patch, you would likely have force closes, or worse a soft brick.
With xposed, those problems are a thing of the past. If it can't hook the mod in, nothing happens (just as you are seeing). Hopefully in a future release there will be some indicator if a mod cant be hooked in.
Nevermind... got it working. F'n awesome, thank you!
Thank you for posting this mod. This made my day - I like keeping my phones with stock rom for as long as I can for stability sakes, and this mod is just what I needed.
Are there any draw backs to this mod? I was reading the original Exploit apk post and some are talking about a green camera screen.
dkb218 said:
Are there any draw backs to this mod? I was reading the original Exploit apk post and some are talking about a green camera screen.
Click to expand...
Click to collapse
If you just root through the app you'll be fine. The green camera screen happens when you check the boxes to actually disable the exploit.
nmw407 said:
If you just root through the app you'll be fine. The green camera screen happens when you check the boxes to actually disable the exploit.
Click to expand...
Click to collapse
Thanks for the reply. Fastest root job I've ever done.
kodochax said:
Thanks for this just found this tool today I didnt want to go through the trouble of custom roms so glad we could get this done with just root! One question tho anyway to change it so every able doesnt show on the big multiview app aftee clicking edit I have a bunch of apps and it lags when scrolling.
Thanks again!
♥Galaxy Note ll
Click to expand...
Click to collapse
Can someone please answer this? I don't want to get this mod and have every single app of mine show up on the multi window list, I just want a certain selection of apps
edit: nevermind, I installed it and you get to choose the apps to add to the list if anyone is wondering. They don't all just show up on the bar, you get a list of yours app and you edit the bar to choose what you want to add
Maybe you misunderstood him? All apps will only show when you click on edit. From that edit screen, you can then drag specific apps over to the multiview bar. After you're done editing, only apps you dragged over will show on the bar.
So two different things here: edit screen and the bar itself.
Hello everyone.
One question on this root process, can we install and use overclock applications such as SetCPU and TunerPro?
And if we had to, can the process be reversed and go back to stock unroot Note II?
Thank you.
maniep said:
Hello everyone.
One question on this root process, can we install and use overclock applications such as SetCPU and TunerPro?
And if we had to, can the process be reversed and go back to stock unroot Note II?
Thank you.
Click to expand...
Click to collapse
1. Yes, once you're rooted, you can use apps that request root like SetCPU, Titanium Backup, AdAway, etc.
2. Yes, if you're on stock rom and recovery, you just go to SuperSu > Settings > Full Unroot.
Wow thanks that's the fastest root i have done. ALSO easy to be on Stock rom and have multi Window with every single app. Much thanks
from my Galaxy Note 2 using Tapatalk 2
Nellyinda803 said:
Wow thanks that's the fastest root i have done. ALSO easy to be on Stock rom and have multi Window with every single app. Much thanks
from my Galaxy Note 2 using Tapatalk 2
Click to expand...
Click to collapse
you guys are lucky . my phone lagged like crazy buttons wernt responding . I unrooted and un installed all the xposed stuff.
nmw407 said:
1. Yes, once you're rooted, you can use apps that request root like SetCPU, Titanium Backup, AdAway, etc.
2. Yes, if you're on stock rom and recovery, you just go to SuperSu > Settings > Full Unroot.
Click to expand...
Click to collapse
Remember to uncheck the disable exploit boxes before unrooting, or you won't be able to re-root using the exploit.
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:
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.
I rooted my phone using the odexed method here: http://forum.xda-developers.com/note-4-sprint/development/rom-t3185274
The Wi-Fi calling option has disappeared and I haven't been able to find a solution while searching XDA. I have an Airvana at home but it requires that I switch from LTE/CDMA to CDMA network and reboot so I would like to try Wi-Fi calling. Is there something I can flash that will restore Wi-Fi calling?
Thanks!
Wi-Fi Calling
pholt33 said:
I rooted my phone using the odexed method here: http://forum.xda-developers.com/note-4-sprint/development/rom-t3185274
The Wi-Fi calling option has disappeared and I haven't been able to find a solution while searching XDA. I have an Airvana at home but it requires that I switch from LTE/CDMA to CDMA network and reboot so I would like to try Wi-Fi calling. Is there something I can flash that will restore Wi-Fi calling?
Thanks!
Click to expand...
Click to collapse
Do you by chance have xposed installed?....if not then just reinstall ROM again, this wont change anything except for getting rid of xposed and sound mods, if you even have those, but reinstalling rom will make it reappear again without changing anything, besides those mods.
So by having xposed installed you lose Wi-Fi calling?
Sent from my SM-N910P using Tapatalk
You must have installed Wanam Xposed module prior to the update of 1.2.2? (Wanam Module, not Wanam Xposed framework.)
Prior to the update, Wanam module was causing csc issues with default to missed calls rather than all calls in call log. Also causing Wi-Fi calling to drop out of Settings.
The update fixes that but doesn't reverse the existing issues prior to that. The fix is to go to make sure you've updated the module, goto /system/csc folder and verify you have both feature.xml and feature.xml.bak If so, delete feature.xml and rename the .bak as feature.xml and make one change in Wanam module to generate the new feature.xml correctly. Reboot and that should be fixed.
For sacs ROM, some have also reported Wi-Fi calling volume issues at max volume. Drop by one click of in-call volume to fix that. Odd but confirmed by multiple users.
Sent from my SM-N910P using Tapatalk
samep said:
You must have installed Wanam Xposed module prior to the update of 1.2.2? (Wanam Module, not Wanam Xposed framework.)
Prior to the update, Wanam module was causing csc issues with default to missed calls rather than all calls in call log. Also causing Wi-Fi calling to drop out of Settings.
The update fixes that but doesn't reverse the existing issues prior to that. The fix is to go to make sure you've updated the module, goto /system/csc folder and verify you have both feature.xml and feature.xml.bak If so, delete feature.xml and rename the .bak as feature.xml and make one change in Wanam module to generate the new feature.xml correctly. Reboot and that should be fixed.
For sacs ROM, some have also reported Wi-Fi calling volume issues at max volume. Drop by one click of in-call volume to fix that. Odd but confirmed by multiple users.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Excellent.
I did have xposed and wanam installed. I uninstalled them, deleted them from my Titanium backup history, ran a new backup, then did a hard reset using the link from my original post. I haven't restored anything from the backup yet but still no WiFi calling option in the settings. The WFC Settings and WiFi Calling apps are listed in the application manager but no way to open them.
What should i do now?
I would factory reset if I were you.
Sent from my SM-N910P using Tapatalk
pholt33 said:
I did have xposed and wanam installed. I uninstalled them, deleted them from my Titanium backup history, ran a new backup, then did a hard reset using the link from my original post. I haven't restored anything from the backup yet but still no WiFi calling option in the settings. The WFC Settings and WiFi Calling apps are listed in the application manager but no way to open them.
What should i do now?
Click to expand...
Click to collapse
See my post above. You should still have a /system/csc/feature xml.bak
If so, delete the original and remove the .bak extension which is the original. Reboot.
Unless you flash the ROM again, I don't see this fixing itself by the means you have taken. Factory reset wouldn't do that either.
That said, a clean install with Xposed module 1.2.2 or higher shouldn't induce the Wi-Fi calling dropping out of settings any longer. I think I'd avoid restoring old settings to Xposed module until you have normal function, then backup those settings to restore later.
Sent from my SM-N910P using Tapatalk
samep said:
See my post above. You should still have a /system/csc/feature xml.bak
If so, delete the original and remove the .bak extension which is the original. Reboot.
Click to expand...
Click to collapse
Just did that. No change.
pholt33 said:
Just did that. No change.
Click to expand...
Click to collapse
Clean install the ROM again. If it includes Xposed make sure you update Xposed module prior to setting it up.
Sent from my SM-N910P using Tapatalk
samep said:
Clean install the ROM again. If it includes Xposed make sure you update Xposed module prior to setting it up.
Click to expand...
Click to collapse
I've uninstalled all things Xposed, so Ill start from scratch.
After talking with samep some more, he suggested this...
Can you check your /system/csc/feature.xml for this line:
<CscFeature_Common_Sprint_Vowifi>true</CscFeature_Common_Sprint_Vowifi>
If it's not there, add it, save it and reboot.
Click to expand...
Click to collapse
That fixed it for me!
samep said:
You must have installed Wanam Xposed module prior to the update of 1.2.2? (Wanam Module, not Wanam Xposed framework.)
Prior to the update, Wanam module was causing csc issues with default to missed calls rather than all calls in call log. Also causing Wi-Fi calling to drop out of Settings.
The update fixes that but doesn't reverse the existing issues prior to that. The fix is to go to make sure you've updated the module, goto /system/csc folder and verify you have both feature.xml and feature.xml.bak If so, delete feature.xml and rename the .bak as feature.xml and make one change in Wanam module to generate the new feature.xml correctly. Reboot and that should be fixed.
For sacs ROM, some have also reported Wi-Fi calling volume issues at max volume. Drop by one click of in-call volume to fix that. Odd but confirmed by multiple users.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
this worked like a charm ... thank you
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