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 have a rooted note 5 n920c im running lineage os and rooted with magisk 15.3 my apps keeps force closing
Like when im swiping through instagram stories or whatsapp stories or when im going through facebook news feed it happens after a while of using like if i use my phone for like half an hour and it stays when i go to recovery twrp i fix context it works fine i dont know if that fixes it or just the reboot fixes it i have used all the custom aosp roms this problem for me is in all of the roms i have used dr ketan rom but it works fine
Please help
Usually that happens when your magisk installation is dirty/broken. Try flashing magisk.
If all else fails, flash in this order, rom, kernel, magisk. Very important to flash magisk after the kernel.
Turbine1991 said:
Usually that happens when your magisk installation is dirty/broken. Try flashing magisk.
If all else fails, flash in this order, rom, kernel, magisk. Very important to flash magisk after the kernel.
Click to expand...
Click to collapse
Thank you very much will try this right away and tell u the results im using lineage os and the forum had another root file and didnt include magisk i installed magisk from its manager does not installing magisk will fix this? And do i have to clean install the rom now?
Update: i Have clean installed the rom and kernel gapps everything but still i have the same problem i get force closes on multiple apps like facebook whatsapp youtube instagram the force closes happen when i use the apps like with too fast of speed like if i scroll throught instagram stories too fast or i scroll throught facebook news feed very fast please help thanks in advance ps im using lineage os and opengapps no root or xposed installed
I finally rooted my K50a40 and the device is running on official MM 6.0 S327_160517_ROW. Ever since the update last year, there has been a problem in the volume on the speakers.
Sound is loud for only about a second and starts to fade and gets almost inaudible even with the volume at max. I can barely hear even with the phone right in my hand. Rarely the volume doesn't fade and it works fine, totally on luck.
Pausing the video or audio and playing again makes the sound loud again for a second but fades again in the same pattern.
I tried everything from disabling the Dolby, using custom equalizers and music players, clearing app data for dolby and media storage, even hard reset. The problem still persists.
I tried MTK Engineering mode for the audio tweaks but that didn't help either.
The sound in headphones works just fine, dolby works too.
I rooted my phone with SuperSU/ TWRP and have installed Xposed libraries in hopes for a solution.
Please help.
Spartame said:
I finally rooted my K50a40 and the device is running on official MM 6.0 S327_160517_ROW. Ever since the update last year, there has been a problem in the volume on the speakers.
Sound is loud for only about a second and starts to fade and gets almost inaudible even with the volume at max. I can barely hear even with the phone right in my hand. Rarely the volume doesn't fade and it works fine, totally on luck.
Pausing the video or audio and playing again makes the sound loud again for a second but fades again in the same pattern.
I tried everything from disabling the Dolby, using custom equalizers and music players, clearing app data for dolby and media storage, even hard reset. The problem still persists.
I tried MTK Engineering mode for the audio tweaks but that didn't help either.
The sound in headphones works just fine, dolby works too.
I rooted my phone with SuperSU/ TWRP and have installed Xposed libraries in hopes for a solution.
Please help.
Click to expand...
Click to collapse
Install a different ROM the nougat ROMs are really good i would suggest RR official if you like customizations or lineage from danielhk if you like a good stable ROM with low levels of customization or you could try going on needrom.com and look for a rom there dot os is fine but idk if they are stable
Now here are the steps for the rr and the most roms i mentioned if the steps are not included in the thread read the thread carefully before installing a ROM don't reboot
-Now go to twrp i latest is always best but you could use danielhks twrp it's good too
-Press install search for the rom file it should be a .zip and let it install
-Now flash gapps (Our phone is arm64 and for nougat roms it's 7.1 gapps flash pico)
-And let it install don't reboot
-And now flash MAGISK it's better than supersu then reboot
-Now when you boot you set up the rom flash the venom kernel it's on xda it's the best
-And now if you want to use apps like snapchat you can't unless you flash the magisk module safety net fix it's an old module so search it up on google
-And then you're set up and don't use xposed on ROMs it's not very stable and makes the ROMs lag
And also don't use Oreo roms they are not stable too
Hi,
Now they fixed the fingerprint in the ç27 update. I rooted my x2pro again with Magisk 20.4 So far so good.
Now I really wanted my viper4android Android back, but I get a bootloop when activating the driver.
I tried the aml patch but no luck so far.
Anybody tried this with success?
Luckily it's easy to undo the install in TWRP.
Just run the zip file and it would uninstall v4a.
Hellsblade said:
Hi,
Now they fixed the fingerprint in the ç27 update. I rooted my x2pro again with Magisk 20.4 So far so good.
Now I really wanted my viper4android Android back, but I get a bootloop when activating the driver.
I tried the aml patch but no luck so far.
Anybody tried this with success?
Luckily it's easy to undo the install in TWRP.
Just run the zip file and it would uninstall v4a.
Click to expand...
Click to collapse
I managed to get v4a working again after hours trying different methods
Install magisk
Get the aml and v4a rootless zip version here https://zackptg5.com/android.php not from magisk repo
First install AML through magisk install complete don't reboot now got recovery install v4a rootless zip when install complete reboot
After that install v4a apk xda labs version https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Now you have working v4a c 27 update
Wow great.
It works again. I'm what they call a happy camper ?
NB: My setup picture for my Sony WF1000 in ears. I use an old studer.irs for convolver. 2 ms deferential sound. Balance a little to left for compensation and viper clarity natural...
Thanks for helping me out.
Good evening, you can tell me how I update my realme x2pro to c27 and the rooted, I'm on the c11 rooted version and twrp installed, I did not want to update it to Android 10 not to lose the fingerprint, but now that they are fixed the problem on c27 I would like to update it. If there's someone who can help me and give me a link to a tutorial, I haven't found here on xda a tutorial that explains the root and installation of twrp. Thank you
---------- Post added at 01:45 AM ---------- Previous post was at 01:44 AM ----------
Hellsblade said:
Hi,
Now they fixed the fingerprint in the ç27 update. I rooted my x2pro again with Magisk 20.4 So far so good.
Now I really wanted my viper4android Android back, but I get a bootloop when activating the driver.
I tried the aml patch but no luck so far.
Anybody tried this with success?
Luckily it's easy to undo the install in TWRP.
Just run the zip file and it would uninstall v4a.
Click to expand...
Click to collapse
Good evening, you can tell me how I update my realme x2pro to c27 and the rooted, I'm on the c11 rooted version and twrp installed, I did not want to update it to Android 10 not to lose the fingerprint, but now that they are fixed the problem on c27 I would like to update it. If there's someone who can help me and give me a link to a tutorial, I haven't found here on xda a tutorial that explains the root and installation of twrp. Thank you
Aze0077 said:
I managed to get v4a working again after hours trying different methods
Install magisk
Get the aml and v4a rootless zip version here https://zackptg5.com/android.php not from magisk repo
First install AML through magisk install complete don't reboot now got recovery install v4a rootless zip when install complete reboot
After that install v4a apk xda labs version https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Now you have working v4a c 27 update
Click to expand...
Click to collapse
This should not disable stock dolby atmos options right?
adsubzero said:
This should not disable stock dolby atmos options right?
Click to expand...
Click to collapse
No it doesn't, but I turn it off anyway because it's adding a bit too much for my liking.
Hellsblade said:
No it doesn't, but I turn it off anyway because it's adding a bit too much for my liking.
Click to expand...
Click to collapse
Ah yeah I mean I like to use the movie preset when playing though speakers, so that's great.
Do you guys have any issues with system sounds and ringtone? If I'm not using a convolver it's fine, but with convolver active there are unusual sound glitches and audio pops.
adsubzero said:
Do you guys have any issues with system sounds and ringtone? If I'm not using a convolver it's fine, but with convolver active there are unusual sound glitches and audio pops.
Click to expand...
Click to collapse
No problems with system sounds here.
I'm using convolver with studer -1db irs.And output gain on minus 6.
Hellsblade said:
No problems with system sounds here.
I'm using convolver with studer -1db irs.And output gain on minus 6.
Click to expand...
Click to collapse
Could you please go into sound settings and then change the media volume slider so it plays that short sound? Nothing weird happens for you?
adsubzero said:
Could you please go into sound settings and then change the media volume slider so it plays that short sound? Nothing weird happens for you?
Click to expand...
Click to collapse
Yep there is always a bit of lag before the driver kick's in when playing media audio. Also when you start playing music. I don't think there's a solution for that.
I think I just got used ?
Hellsblade said:
Yep there is always a bit of lag before the driver kick's in when playing media audio. Also when you start playing music. I don't think there's a solution for that.
I think I just got used ?
Click to expand...
Click to collapse
Ah yes that's the thing, but the problem is when receiving notifications from different apps.
For instance I get a notification from Viber and there's a slight pop, but then I receive a notification from Facebook and first it plays the remaining sound from Viber then from FB and it sounds really messed up.
It's sad if there's no solution, but I guess I'll keep investigating.
Though I don't think there's no solution, since this always worked fine for me, previously on Nexus 6P, LG V30 and HTC 10.
Btw, my suggestion for the SRS_1_1_Normal_stereo.irs convolver.
Edit the EQ to something like -2dB for the bass freq and -4dB for 4KHz, the rest is up to you.
It gives incredible deep bass and better bass response to the speakers.
Edit: the partial solution for the mentioned issue is to enable attach audio effects option in V4A. I'm not sure if it works for every audio player, but it works with Poweramp. What it does is it disables V4A processing for everything but the music player. The drawback to this is when I'm listening to something in Poweramp and want to play something eg. on YouTube, there is no sound at first. It works okay when I stop/close poweramp. For my usage this is kind of fine I guess, so I thought I would share.
hello everyone and thanks for the explanation everything works correctly now
I don't know if it only happens to me or if it is normal, when I close the multitasking v4a application it stops working, I tried turning it into a system application but the same thing happens, can you help me with that question?
Aze0077 said:
I managed to get v4a working again after hours trying different methods
Install magisk
Get the aml and v4a rootless zip version here https://zackptg5.com/android.php not from magisk repo
First install AML through magisk install complete don't reboot now got recovery install v4a rootless zip when install complete reboot
After that install v4a apk xda labs version https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Now you have working v4a c 27 update
Click to expand...
Click to collapse
why i cant find xda version apk anywhere ? other versions doesnt work
peymanbeyraghi said:
why i cant find xda version apk anywhere ? other versions doesnt work
Click to expand...
Click to collapse
https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
thanks , i have fixed it , i forget to install selinux on magisk . after that all versions works fine .
Aze0077 said:
I managed to get v4a working again after hours trying different methods
Install magisk
Get the aml and v4a rootless zip version here https://zackptg5.com/android.php not from magisk repo
First install AML through magisk install complete don't reboot now got recovery install v4a rootless zip when install complete reboot
After that install v4a apk xda labs version https://labs.xda-developers.com/store/app/com.pittvandewitt.viperfx
Now you have working v4a c 27 update
Click to expand...
Click to collapse
Hey, I have used this method previously to install V4A, but I can't get it working anymore. After trying out custom ROMs, I've gone back to clean RUI 1.0 C38, and following the same steps the V4A doesn't work. Has anyone found a reliable way to install V4A?