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
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Kov8 said:
I had the Nook HD+ running CyanogenMod for a few years.
I changed nothing, but lately it stopped working, complaining about Trebuchet, so I changed the launcher and it worked again, but giving occasional errors about an app not starting.
In the last few days it also started sporadically rebooting itself. Plunging it in did not seem to change anything. Lowering the max CPU speed from 1.5GHz to 1.1 did not help.
Now, it would not start at all – it would always get stuck at the circling CyanogenMod boot screen. It would still shut down using a long press.
I can start the rescue fine, with no unwanted reboots.
I do have a small amount of data there that I would like to be able to take out, if possible.
I don't care for any specific OS version/mod.
What do you think is the cause of this issue?
How can I fix this? Can I get the Data out?
Click to expand...
Click to collapse
Hi Kov8.
I was running CM 11.1 for ovation and experienced the same thing. My solution was to install a newer version.
To save your data, set up an SD card (be sure you have enough extra room for your data) with the TWRP 3.0.1-0 version here:
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
Load TWRP and look for the File Manager. I think it's under "Advanced." You can use that to copy or move your data to the SD card.
After that, consider upgrading to AOSP or LNOS. I can install AOSP without much difficulty, but LNOS doesn't go well. More on that in a later post.
If you need more detailed information, look at this post and download the pdf at the end of the first post:
https://forum.xda-developers.com/nook-hd/general/install-cyanogenmod-12-1-barnes-noble-t3211119
Kov8 said:
Btw, in the years it was working, it did have an issue of sometimes restarting instead of shutting down.
I never knew if it was a fault with my device or the with latest CM.
Click to expand...
Click to collapse
Yes. I've been reading that all the recent ROMs do that.
The solution is to do a standard shutdown followed by a hard shutdown (by holding the power button for 8 seconds).
I suspect that going straight for the hard shutdown caused some file system errors that made installing new ROMs very difficult.
I'm OK now, though.
Thanks for the detailed reply! I will try.
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Kov8 said:
The link for TWRP does not work. Can I install the latest, 3.2.1.0?
Click to expand...
Click to collapse
That's funny. I just downloaded two copies from that link.
For version 3.2.1-0, it sounds like you're looking at the version from the team win website. I haven't tested that one thoroughly, but I have tried out their version 3.1.1-0. It works pretty well. It gave me some minor error messages here and there, but if I just repeated what resulted in the error, it generally went through on the second attempt without an error.
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Kov8 said:
The link worked for me later. I managed to change to TWRP 3.0.1-0 only after removing the version identifier from the zip file. I later easily upgraded TWRP to the newest.
I also upgraded to the latest AOSP from the same source, without deleting, as I couldn't get the data from one app. I then installed ARM 7.1 pico gapps. Some apps kept crashing, but removing and reinstalling seems to have fixed that.
The only problem, is that now shut down never works, and restart always takes me to recovery. So I just hard shutdown there.
Click to expand...
Click to collapse
Mind telling how you managed to update twrp from 3.0 1 to the latest? I successfully installed 3.0.1 to my nook hd+, then flashed 3.2.1 img to recovery, now the device stuck at boot.
I simply downloaded to img file from their website (for ovation, my device), placed on the micro-sd, and installed it from TWRP itself. As simple as that.
Are you sure that you got the correct version for your device?
I also always verify the integrity of roms after writing them to a card. I've seen bad cards.
Hello! Today I decided I would give Xposed another chance (I tried installing it through Magisk before, resulted in bootloop). After installing it through TWRP, my phone got stuck in a bootloop. I tried using the Xposed Uninstaller. Didn't work. I tried entering Safe Mode. Didn't work. I tried resetting my phone in TWRP. Also didn't work. How can I get rid of it? Please help, I just want to uninstall Xposed so I can use my phone again). Thanks!
Ovidiu05 said:
Hello! Today I decided I would give Xposed another chance (I tried installing it through Magisk before, resulted in bootloop). After installing it through TWRP, my phone got stuck in a bootloop. I tried using the Xposed Uninstaller. Didn't work. I tried entering Safe Mode. Didn't work. I tried resetting my phone in TWRP. Also didn't work. How can I get rid of it? Please help, I just want to uninstall Xposed so I can use my phone again). Thanks!
Click to expand...
Click to collapse
I guess the only way to revert this is to flash the stock firmware over with Mi Tools.
I'm saying this as a layman, because I'm still studying before doing any dangerous experiments with my mido.
But I've read a few minutes ago that there are specific ports of Xposed for mido. Maybe you should try those. I don't have the links right now, but if you dig up in the forums, you'll probably find what you are looking for.
Those videos on YT also helps, but they're not 100% guarantee that will work at all. You should proceed by reading a lot before tinkering with this stuff, you know.
It's my 1st attempt as well, so I just hope I do everything right to do not result in something like you had. ?