I recently updated my module's xposed code, and now sometimes get stuck at boot when I updated the Xposed module before, although I didn't touch the Main class.
I released it yesterday, and now several users report the same issue. I and the users were able to fix the bootstuck by wiping dalvik cache, for some it worked instantly, but I had to wipe it several time to get it to boot again.
Now I am not sure if my module is the cause, because I don't see any errors, it sometimes just works, and although it first seemed so, the app isn't always the last Xposed module which gets loaded, thus not definitely the reason for the bootstuck.
UPDATE: Found the issue. It seems that referencing other package classes which are not part listed in xposed_init cause this bootloop. @rovo89, is this fixable?
"Note that this is still an alpha version and for Lollipop on ARMv7+ devices only.
Please install it only if you're willing to take the risk of boot loops. Just because it's working fine and stable for me doesn't mean it will work for everyone the same way."
Rovo mentioned this was to be expected.
Sorry I'm not much of help. :/ My guess is that results vary from devices.
MisterCoolBeans said:
"Note that this is still an alpha version and for Lollipop on ARMv7+ devices only.
Please install it only if you're willing to take the risk of boot loops. Just because it's working fine and stable for me doesn't mean it will work for everyone the same way."
Rovo mentioned this was to be expected.
Sorry I'm not much of help. :/ My guess is that results vary from devices.
Click to expand...
Click to collapse
Well, of course I know. But if @rovo89 and @romracer as well as @C3C076 aren't knowing about, they cannot fix.
I tried using just xposed frakework installed, without any modules and still got this bug. Weird.
delete
Since Magisk 11 released and even now with 12, rebooting feels like a roll of the dice between flashing something or installing a module. I don't have any real development experience, but had tried building a module or two and troubleshooting another in the past few weeks, which resulted in eventually booting to the error SystemUI has stopped... This has happened several times in a day even. Now today, I push the April security update, install Magisk 12, and slowly start piecing my setup together 1 by one to make sure everything works properly. Then suddenly another SystemUI has stopped error... Only way to fix it is to restore from TWRP or factory reset. A timely process. Flashing zips in TWRP in the past hasn't resulted in this for me ever... That's going back to the Donut days on my Samsung Moment, LG Optimus, HTC One M7, and now my Nexus 6. I really want to love Magisk, but its very frustrating to get so far then to have to restore and start again.
Is it something I'm doing wrong? Is there a better way to resolve this when it occurs? Is there a way to avoid this error? Is this even a Magisk issue and the fact it hasn't happened before is a matter of luck? I don't even know what's causing it...
Use MagiskMount to mount magisk.img to /magisk and delete the installed module
duxishere said:
Use MagiskMount to mount magisk.img to /magisk and delete the installed module
Click to expand...
Click to collapse
Yes, I do that. That's not even the problem. It's when I finally boot after installing something or removing a module, SystemUI stops and I can't do anything.
Hm... I did notice this issue a couple of times on my Nexus 6 as well. It did happen a few times when installing modules that weren't quite compatible or otherwise had issues (I was experimenting and it was never quite reproducible), but mainly when trying to do a TWRP backup or restore (completely reproducible, 100% of the times). I figured it was my device acting up and never really connected it with Magisk.
I'm going to do some further testing...
gk1984 said:
Yes, I do that. That's not even the problem. It's when I finally boot after installing something or removing a module, SystemUI stops and I can't do anything.
Click to expand...
Click to collapse
Exactly my problem too. Im using redmi note 3 with lineage os and rr. The problem sam like this. Please tag me if you find the solution.
batmi said:
Exactly my problem too. Im using redmi note 3 with lineage os and rr. The problem sam like this. Please tag me if you find the solution.
Click to expand...
Click to collapse
I concluded it's a module I was using. Actually, the module I tried writing myself. Stopped using, no more issues. Well, at least not yet.
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!
What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
I have Resurrectionremix and Magisk 14.3
No any lag on my phone.
Tapatalk - Xiaomi Mi6
You need to list what modules you're using.
BIGWORM said:
You need to list what modules you're using.
Click to expand...
Click to collapse
I only flash the ROM, GApps and Magisk without any additional flashable ZIPs.
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
yung40oz84 said:
Honestly that doesn't sound like Magisk. I've ran Magisk on literally probably 20 ROMs between Angler and Pixel XL and never Magisk caused lag... Did u try a different rom? Just curious, or maybe it's some incompatibility with that specific rom and magisk
Click to expand...
Click to collapse
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
irfanfadilah said:
I tried several ROMs that based on LOS and all same, maybe it's caused by LOS base that used in those ROMs. And since you say so, probably it's not an issue in Magisk, but the ROM itself.
I'll try Magisk again later when some ROM's builds available for my device.
-
I think my questions has been answered (it's appear not issue in Magisk side) and this thread can be closed.
Click to expand...
Click to collapse
Ya I was gonna say cause I use all AOSP and CAF based
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Danilo-Sanchez said:
I had this issue with Lineage 14.1 and AEX before.
Now I don't have this issue anymore.
What I do is:
- Wipe everything
- Install ROM
- Install GApps
- Reboot and finish Setup Wizard (then I install some or all apps that I use)
- Reboot to TWRP and flash Magisk.
The first time I reboot after flashing Magisk it's still a little slower than normal. Then I reboot one more time and never faced this anymore.
Now I do this everytime I make a clean install and everytime it works.
Click to expand...
Click to collapse
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
Yes.
Try it and let me know if this also fix the problem for you.
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
dragos281993 said:
Yes, Magisk is the thing that's causing lag and stutter. My Nexus 5X is also barely responding to any commands if I flash Magisk right after a ROM clean installation. If you flash only the ROM, then you can finish setting up the device without much stutter or hiccups in performance.
If, after a clean installation (or after installing Magisk - didn't try this though) you use the phone without Magisk for a bit, maybe install some apps, etc, you'll see that everything is nice and smooth.
Now, you can check the smoothness without Magisk and with Magisk installed like this:
- Without Magisk: Update 'Google App' to the latest version then try to open the side panel from the latest Pixel Launcher. You'll see that opening/closing it is nice and smooth, and scrolling up and down is also smooth.
- With Magisk installed (without using any modules): The moment the phone turns on, at first, things might seem OK. First wait for the phone to settle down after the reboot for a few minutes. Then try opening the side panel. You'll see some stutter while dragging that panel to the right, maybe not huge, but it's there. Scrolling up and down is also stuttery. At first I thought it was because of the latest version of Google App, or the new cards design, or even the images in there, but that wasn't the issue. Then I thought maybe the launcher was somehow influencing Google App's performance, but that wasn't either the issue.
AND it was like I completely forgot about SuperSU and didn't even think of trying it in order to see how things were.
I even rebased my ROM in the hope that I'd find the culprit, and still nothing. Nothing weird appeared in any logs, which was so annoying. And a few hours ago, after finishing up cleaning up my sources (for other reasons), I compiled a fresh new build, and it crossed my mind to try SuperSU, just for the hell of it, and BOOM ! No more lag and stutter. The phone is snappy and responsive again.
I'll try to contact the dude behind Magisk and see what he has to say, or leave a comment in his thread.
The thing is, those with more recent phones, like the Pixels or any other phones than are more powerful than mine, might not notice what I described above, but there should be some stutter there, no matter how small, maybe in other scenarios as well.
The thing is, Magisk kinda slowly took the place of Xposed, at least that's what it looks like to me, and I personally don't like that but that's how things are, I suppose. All those modules or at least one of them WILL cause issues sooner or later, just like on Xposed.
But in the end, yes, it's Magisk what's destroying your phone's performance and nothing else. So if you're not really in the need to have your phone pass SafetyNet, and want to have your phone snappy and lag-free, use SuperSU, at least until things get better on Magisk.
Click to expand...
Click to collapse
I'm glad I'm not the only one experienced this issue, that's mean it's not entirely user fault. Maybe you're right, on more high-spec phones they won't really notice the lags/stutters.
Looking forward to the news/updates regarding this issue.
irfanfadilah said:
So don't flash Magisk along with the ROM?
Instead finish Wizard Setup first and back to TWRP to flash Magisk. I'll try this if the issue still persist. Many Thanks
Click to expand...
Click to collapse
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Camandros said:
I don't mean to necrobump, but did it work? I have an LG G4 (H815) and suffered the same issue. Like you, I only flashed magisk right after flashing the ROM (LG nougat).
Thanks
Click to expand...
Click to collapse
I haven't got the chance to try it.
Currently I'm using SuperSU to root my device.
I tried installing magisk on my currently in use ROM, i.e., a long time after flashing it, and although it got less laggy, there still was a heavy lag impact in some applications. Maybe it has less impact on lineage or on lighter ROMs? I'm using official LG nougat.
I'm using Mi 6 in Xiaomi.eu rom
YES, magisk causing laggy.
Same here
Mi5, tested on MIUI 9 and 10
Without Magisk everything was great and after flashing Magisk, the phone got laggy!
I have the same problem with my LG G6
interesting, first I thought that emmc will be broken. because the problem is the same (lag). but after i replace emmc, all back is fine. I just think emmc is broken because it is often flashing rom.
ChessPiece said:
What I did:
- Wipe all (clean install).
- Flash latest Official MoKee ROM (Nougat).
- Flash latest GApps.
- Flash latest Magisk.
- Reboot.
After finished the Wizard Setup and before doing anything, my phone got very laggy, open menu, open Settings, etc.
Then I clean install again like the steps above, but this time using SuperSU, and everything normal, so I stick with SuperSU for now.
My questions, what is the cause of the lags? Is it known bug in Magisk, the ROM itself (not compatible), or GApps? I also heard ResurrectionRemix had the same problem after installing Magisk, so many people revert back to SuperSU.
Thanks,
Click to expand...
Click to collapse
what magisk version 16.0 or beta? magisk can't make the phone lag but kernel or something in ROM may interrupt try to change kernel or flash the lastest Gapps