Hi!
I've recently installed Riru Edxposed on my Poco f2 pro. It worked fine until after a day, the Modules started to deactivate themselves. I'd manually activate them again, but after rebooting, they're deactivated again.. Can anyone tell me why this problem occurs? I can't use the modules at all, if they keep deactivating, obviously!!
Any help is appreciated!
Having the same issue it happens randomly all the time for me. I am on a mi 11 running riru exposed.
Ianb1 said:
Having the same issue it happens randomly all the time for me. I am on a mi 11 running riru exposed.
Click to expand...
Click to collapse
I'm on mi 11 too! Glad to know, I'm not the only one.
If you lock the exposed manager app in the recents window and do not swipe it away the modulars stay active. This is 100% not a solution and only a temporary fix. I hope this helps in the meantime.
Thank you very much! It might not be a permanent solution, but it's a big help!!
Related
Hey Guys,
I have seen some Custom-ROMs with Screen Off NFC Options but I like CM11S and would like to ask if there is any way to make this possible in CM11S as well.
Thanks in advance
Install Xposed and NFC LockScreenOff Enabler.
repo.xposed.info/module/de.robv.android.xposed.installer
repo.xposed.info/module/pk.qwerty12.nfclockscreenoffenabler
mudkip908 said:
Install Xposed and NFC LockScreenOff Enabler.
repo.xposed.info/module/de.robv.android.xposed.installer
repo.xposed.info/module/pk.qwerty12.nfclockscreenoffenabler
Click to expand...
Click to collapse
I did it several weeks ago but id didn't work properly for me in my OPO.
It works fine for some time, maybe some hours, but then the NFC doesn't work at all, even with the screen on.
I had to turn the NFC off and on again to start reading nfc tags again.
Does it work properly in his OPO to someone here in the forum?
I'm using it since day 1 on my OPO (a bit more than a month ago), and never had any issue with it
Do yo set it up with screen off or with screen locked?
Screen off for me
bud77 said:
Screen off for me
Click to expand...
Click to collapse
thanks. I have installed it again. I will try it again for some time.
capdcanoa said:
thanks. I have installed it again. I will try it again for some time.
Click to expand...
Click to collapse
Your issues might also be ROM related
If you still get errors, try a clean install and reinstall the module
Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.
Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually
RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones
RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk
So I'm fighting with this all night I found this
https://www.xda-developers.com/oneplus-7-pro-oxygenos-9-5-gravitybox-root/
Updated : so the exposed work now what module I need to have to change status bar ?
Install Gravitybox apk, activate xposed module and reboot.
JJay666 said:
Install Gravitybox apk, activate xposed module and reboot.
Click to expand...
Click to collapse
Confirmed work take me 3 hour i have wrong module installed in exposed and got bootloop and removing my root too when I was active gravity box and restart phone. First time was doing this noob time :cyclops: thank you
siuraczewski said:
Confirmed work take me 3 hour i have wrong module installed in exposed and got bootloop and removing my root too when I was active gravity box and restart phone. First time was doing this noob time :cyclops: thank you
Click to expand...
Click to collapse
Btw any recommendations module's for try it in first time use ?
siuraczewski said:
Btw any recommendations module's for try it in first time use ?
Click to expand...
Click to collapse
Besides GravityBox ? Im not sure. It depends on what you want. I personally no longer use any of it.
JJay666 said:
Besides GravityBox ? Im not sure. It depends on what you want. I personally no longer use any of it.
Click to expand...
Click to collapse
How you change status bar text color i don't see option in gravity box?
siuraczewski said:
How you change status bar text color i don't see option in gravity box?
Click to expand...
Click to collapse
You can't in current pie version
Is GravityBox actually working for anyone? When I installed/enabled the Xposed module my phone went into a boot loop. Not too bad to recover from, but I don't really want to try it again unless someone can confirm it works on their OP7P. If it's working for you, which version/where did you install it from?
terlynn4 said:
Is GravityBox actually working for anyone? When I installed/enabled the Xposed module my phone went into a boot loop. Not too bad to recover from, but I don't really want to try it again unless someone can confirm it works on their OP7P. If it's working for you, which version/where did you install it from?
Click to expand...
Click to collapse
Working fine for me.
tech_head said:
Working fine for me.
Click to expand...
Click to collapse
Same here.
everything work well
9.5.7 GM21AA GM1917
Everything work well
Modules in Magic
-Riru Core
-Riru EdXposed
-substratum
apk gravity box
Why do you need substratum?
HottieLinus said:
Why do you need substratum?
Click to expand...
Click to collapse
For themes, Substratum will install a magisk module if it finds it.
siuraczewski said:
everything work well
9.5.8 GM21AA GM19170 didn't disable enything before Update.
Everything work well
Modules in Magic
-Riru Core
-Riru EdXposed
-substratum
apk gravity box
Click to expand...
Click to collapse
-viper
-YouTube vience
cant get lockscreen rotate to work in gravitybox. really the only think I installed it for.
does anyone know of a volume button reorientation module until we get custom roms with it?
I really want to install Gravity Box on my phone but last time I did on my 6T, the exposed interferes with the Snapchat and I was banned for a day. Has anyone found work around for Snapchat with exposed installed? If yes, please let me know. Thanks.
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
harshparmar said:
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
Click to expand...
Click to collapse
I cleared cache in twrp and mine starting working again
Ultraman666 said:
I cleared cache in twrp and mine starting working again
Click to expand...
Click to collapse
I also wiped dalvik cache but same error exists...
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
but I am not using call recorder module...
I am using cloudflare dns and xXx no limit module only
I think xxx hast it inclueded? Try deactivating magisk modules?
harshparmar said:
Both Sim Cards are not being detected.
When I open SIM settings it shows, "com.android.phone keeps stopping".
I am using oxygen OS 10.3.0
with xXx No limits 9.5.
Other than that, I have magisk 20.2, edxposed 4.5.3, riru core 19.6, edxposed yahfa v4491.
The same issue also came the previous month when I was using oxygen OS 10.0.2 with xXx No limit 9.4.
I have noticed that it happens when the phone is switched off an then turned ON.
I have tried many things and searched everywhere but didn't find a solution other than full data wipe.
please help!!!
Click to expand...
Click to collapse
This happened to me and after disabling all Magisk modules and rebooting I got it to recognize the SIM card again. I did dirty flash the ROM during this process with modules activated, but it didn't fix the issue until I deactivated all modules and rebooted. I think it was an issue with xXx, but when I installed xXx after detecting the SIM again I didn't have any issues.....
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
god damn me that was it...it was driving me nuts. thank you!!
6nchris said:
I Had the same problem after updating to 10.0.3! I Had also magisk and call Recorder enabler module installed. Found Out IT was call recorders fault. When i disabled the Module everything was finde. After i updated the call enabler module everything worked again.
Click to expand...
Click to collapse
That worked for me, thanks!
The OnePlus helpdesk was making a ticket to send the phone to recovery
I'm using a OnePlus 5. I also had the same problem after an OS update. The OnePlus Native Call Recording Magisk module was indeed the culprit!
Usually, I uninstall Magisk before an OS update. I got lazy and skipped this time. Oh, yeah, now I remember... Random time-wasting stuff like this happens half the time if I skip Magisk uninstall! Lesson learned.
I was able to use the Call Recording module again by uninstalling and then reinstalling Magisk.
After installing magisk on the phone using the boot.img patch method, the camera app crashes. Flashing the stock boot.img file fixes it though. I also noticed that the phone takes longer to boot now.
Never mind, it was a module that was causing the problem
Entity_909 said:
Never mind, it was a module that was causing the problem
Click to expand...
Click to collapse
Which module it is? Actually I am running AOSP 13 in my xiaomi phone and recently its camera is crashing. I have installed multiple modules lately.
The Rysul said:
Which module it is? Actually I am running AOSP 13 in my xiaomi phone and recently its camera is crashing. I have installed multiple modules lately.
Click to expand...
Click to collapse
I think the problem is that the module I installed actually changed the device model, so it showed up as another phone. This caused the camera app to crash