Hello,
I'm new to modding and stuff but after I flashed EdXposed (the SandHook Alpha version) apps like settings, camera, facebook services or something like "android.process.acore" keeps crashing randomly. Especially after booting. Why? Will it help if I flash Canary version? Or maybe I should stay on Alpha but flash the YAHFA one? I'm really clueless and don't know what's happening.
Same issue persisting
I am also facing same time of problem...have your problem solved?
Related
Booting is very slow, lags.
Tasker, LMT launcher, Lucky Patcher apps are activated 5 minutes after the boot, and they do not work properly!
I have tried to uninstall all the modules under Xposed, start it alone, reinstall Xposed again, change version with last beta.
On my Galaxy Note 4 n910f rom Stock Original ver. NK5 with root permissions everything is ok before I have actived exposed.
Does anyone know the reason?
Thanks in advance!
I have issues like yours, some times is just one module that conflicts your system or frame work, sometimes I got "UI STOPED WORKING" Other times, boot loops, or lags, I have fixed restoring system in recovery from a previous backup, disabling xposed, disabling modules, and enabling one by one until finding the culprit, so far I found some settings in certain modules causing me trouble, not the entire module, I think it depends upon your device, rom, and combination of modules and settings , so you could try by elimination, as I did, I found the conflicts in xblast, xinstaller, swipeback, battery xthemer, xprivacy, donkeyguard, good luck
Install XSecureStorage from the modules list and see if that helps, let us know the outcome.
So I've had this bug for a while and I've always thought it was a bug in CM14.1 since I had it come about when I switched both my Nexus 7 2013 and OnePlus One over to the CM14.1 nightlies but after talking to a few people they told me they don't have this problem. I decided to do some testing and upon uninstalling Magisk the bug seemed to not occur anymore on either my Tablet or my Phone. At one point I went through and installed everything one at a time on the Magisk 10 12/29 build oddly enough I didn't experience the bug on that even with all my normal modules installed. As soon as I reverted to Magisk 9 or a newer build of Magisk 10 (I'm currently on 01/01/17 after getting it to work by clearing my cache) the YouTube bug came back. I haven't been able to replicate not having the bug while magisk is installed a second time even with the same build however.
Now I'm wanting to know how many if any of you are also experiencing this same issue and if so what device, rom, and Magisk version are you on and what modules are you using? I really want to solve this issue without having to stop using Magisk because I need it for several things currently.
Link_of_Hyrule said:
So I've had this bug for a while and I've always thought it was a bug in CM14.1 since I had it come about when I switched both my Nexus 7 2013 and OnePlus One over to the CM14.1 nightlies but after talking to a few people they told me they don't have this problem. I decided to do some testing and upon uninstalling Magisk the bug seemed to not occur anymore on either my Tablet or my Phone. At one point I went through and installed everything one at a time on the Magisk 10 12/29 build oddly enough I didn't experience the bug on that even with all my normal modules installed. As soon as I reverted to Magisk 9 or a newer build of Magisk 10 (I'm currently on 01/01/17 after getting it to work by clearing my cache) the YouTube bug came back. I haven't been able to replicate not having the bug while magisk is installed a second time even with the same build however.
Now I'm wanting to know how many if any of you are also experiencing this same issue and if so what device, rom, and Magisk version are you on and what modules are you using? I really want to solve this issue without having to stop using Magisk because I need it for several things currently.
Click to expand...
Click to collapse
I have this... But it only happens after a lot of uptime... And only once in a great while
I chalk it up to running a custom ROM... And it is fixed with a reboot...
I get it with and without magisk
rignfool said:
I have this... But it only happens after a lot of uptime... And only once in a great while
I chalk it up to running a custom ROM... And it is fixed with a reboot...
I get it with and without magisk
Click to expand...
Click to collapse
For me it can't be up time because it occurs even between reboots on y nexus 7 and OnePlus One. I did seem to get it to well on u OnePlus one with the newest build some how but couldn't seem to replicate that on my Nexus 7. It must be a combination of things causing it ugh. If I could just disable 60fps and keep 720p/1080p that would be fine even. Just 480p looks like crap.
Hello again XDA!
So this has become much more frustrating that I thought it would. My phone normally operates fine, just a couple minor software issues here and there, latest issue being my alarm not going off, tried disabling amplify in xposed as the issue only occurs if the phone has been idle for the night, figured maybe amplify might be blocking the wakelock or something. Just thought I'd share in case the module could be the root cause of both issues.
The issue I'd really like to ask about has to do with booting. As I said, the phone generally runs fine, but any time I reboot(or my phone dies) I have to wipe the dalvik in TWRP or else android just hangs on bootup indefinitely. Not only is this always a slow process(generally 15 mins of downtime) but it drains about 30% battery in the process. Just wondering if anyone has had this issue and fixed it without wiping and reinstalling a rom from the ground up.
Currently running latest ICE Lollipop build 7.1.3, elementalX 22.4-sense kernel, and latest firmware, 4.19 I believe. Xposed running with just a handful of modules (greenify, snapprefs, xblast, youtube adaway, sense toolbox). I have tried using stock kernel and uninstalling xposed framework and apk to no avail. What does work is a clean install of the same rom with the same basic setup, but I didn't want to have to reconfigure everything if I didn't have to, so I restored my backup in the meantime.
I can't get a logcat ATM, maybe tomorrow after work if I have some time. I'm also not 100% sure how to grab one anymore since its been years since I last posted one, but would be happy to provide one soon.
cheers!
Hello, I have the following problem, the operating system and the Greenify application worked very well on Magisk v22.1, but after updating to v23.0, there are problems, the operating system itself on the phone is slow and in the Greenify application, I am dissatisfied with this update v23.0 .
Please help what can be done about it.
My HTC U11, Stock ROM.
Greetings.
Noticed this on my Pixel 3 running stock as well. I would have to restart the phone several times to get it running.
GrandAdmiral said:
Noticed this on my Pixel 3 running stock as well. I would have to restart the phone several times to get it running.
Click to expand...
Click to collapse
I understand it turns out there is a problem with this v23.0 update, I wonder who else has a problem with it, besides us.
I'm not seeing any similar issues on v23 (and haven't on the canary releases leading up to it either). That doesn't mean there isn't a possible issue though...
Have you guys checked your modules if there's a possible culprit there?
Didgeridoohan said:
I'm not seeing any similar issues on v23 (and haven't on the canary releases leading up to it either). That doesn't mean there isn't a possible issue though...
Have you guys checked your modules if there's a possible culprit there?
Click to expand...
Click to collapse
I only have these modules and they were on v22.1, they did not cause any problems like this v23.0.
That the modules worked fine in earlier releases doesn't necessarily mean that they work on current/future release...
You need to do some troubleshooting if you're interested in getting to the bottom of this.
Disable modules to figure out if it's one of those. Disable MagiskHide to see if it's connected to that. Etc...
Didgeridoohan said:
That the modules worked fine in earlier releases doesn't necessarily mean that they work on current/future release...
You need to do some troubleshooting if you're interested in getting to the bottom of this.
Disable modules to figure out if it's one of those. Disable MagiskHide to see if it's connected to that. Etc...
Click to expand...
Click to collapse
It may be that the module may not work properly on this v23.0.
Okay, I will follow your suggestion on what to do with it, I'll check it out and let you know.
From the very beginning, MagiskHide is turned off.
MagiskHide off, module turned off, Riru, Riru - Edxposed, phone restart, phone working, fast as it was on v.22.1, probably something is wrong with these modules.
Sounds like EdXposed is causing some issues then... You might want to check the Xposed forums and/or EdXposed Github issues to see if there's some mention of similar problems there.
Didgeridoohan said:
Sounds like EdXposed is causing some issues then... You might want to check the Xposed forums and/or EdXposed Github issues to see if there's some mention of similar problems there.
Click to expand...
Click to collapse
I will check the forums, maybe I will come across something, and if not, I will also write a post there, maybe a new update of these modules will fix something.
Thanks for your interest in the topic.
hello!
just joined this super cool community as I am experiencing some issue since I've update my Mi 11 Ultra to v.12.5.6. A few days after the new firmare, I've woken up to a notification from Google Pay that my phone was rooted. Indeed, my safetyNet check now fails. Let me tell you, my Magisk has been working flawlessly up till the update.
I have noticed 2 weird things:
- all other apps do work except GPay
- there something weird in the Magisk UI because there is little to none settings and all my modules seem to have disappeared and there isn't seem to be a way to get them back.
Posting some pictures.
Has anyone else had the same issue?
thanks folks
Seems to me that Magisk got uninstalled ("Installed: N/A").
I suggest to put the phone in fastboot mode and reflash the Magisk patched boot.img again.
I've had the same thing on my POCO F3, with latest MIUI 12.5.x.
Thank you! Yes that's very strange. I'll try that and will let you know. It would just be annoying if it's something that needs to be done at ever update