Database Develop

Lag on Roooted Global 7.1.19 MIUI

Hi I'm having this issue consistently ever since nougat based ROMs are released for Mi5
Whenever i root the nougat based miui ROM, it boots fine but after some time it starts stuttering/lagging so much that one becomes totally inoperable.
I have tried various ways but no success.
I have tried with SuperSU 2.78, 2.79, 2.79SR3 and also eu roms n China global as well but the results are same.
I have also tried wiping the whole internal partition to remove device encryption but the lag don't go away.
When dirty flash the ROM again from twrp, Everything comes back to normal.
Not sure if anybody else is facing the same issue or probably know the solution.
Cheers!

Did you already tried stable version 8.1.9.0 rom from xiaomi.eu that's based 7.0 too..?, coz before..i'm using that rom for a month i think...and doesn't found any lag..even already rooting with supersu 2.79.
Please make sure..this time not just a wiping..but do a format system, data and cache as ext4 from official twrp 3.0.2-3 before flasing

JJeamy said:
Did you already tried stable version 8.1.9.0 rom from xiaomi.eu that's based 7.0 too..?, coz before..i'm using that rom for a month i think...and doesn't found any lag..even already rooting with supersu 2.79.
Please make sure..this time not just a wiping..but do a format system, data and cache as ext4 from official twrp 3.0.2-3 before flasing
Click to expand...
Click to collapse
Let me try formatting system also, but i don't think that would help much

after flashing suhide the lag is back again, looks like suhide issue

chhapil said:
after flashing suhide the lag is back again, looks like suhide issue
Click to expand...
Click to collapse
Yup..i think compatibility suhide is causing that lag..coz i'm never tried that before..but with just standard supersu..all running normally in mine..

JJeamy said:
Yup..i think compatibility suhide is causing that lag..coz i'm never tried that before..but with just standard supersu..all running normally in mine..
Click to expand...
Click to collapse
Just to confirm my doubt, can you try flashig suhide? its very easy uninstall as well. it just adds a script to su partition.
it will help me report the issue in suhide thread.
thanks for your support

chhapil said:
Just to confirm my doubt, can you try flashig suhide? its very easy uninstall as well. it just adds a script to su partition.
it will help me report the issue in suhide thread.
thanks for your support
Click to expand...
Click to collapse
I can't test it that now..coz now mine currently back using 8.1.3.0 that's based 6.0, to test raw format of camera coz in 7.0 doesn't work before.. so the result will be different from yours..

JJeamy said:
I can't test it that now..coz now mine currently back using 8.1.3.0 that's based 6.0, to test raw format of camera coz in 7.0 doesn't work before.. so the result will be different from yours..
Click to expand...
Click to collapse
Np, let me know if you switch back N again

chhapil said:
Np, let me know if you switch back N again
Click to expand...
Click to collapse
Will testing it later..and letting know the result to you..

Installed the new Magisk 11, everything smooth as butter now.
magisk hide works fine!

[Rant -- sorry] SystemUI has stopped happens way too often...

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.

Samsung S5 Plus Magisk above v12 boot loop stuck on boot logo

Hi all when flashing any version above v12 on to my phone it gets stuck at the boot logo I am using Lineageos latest version of typing this but if I use v12 its fine but dont pass the CTS and stuff
I have tried to fully uninstall the magisk and reinstall it on the newer version and nothing can anyone help please

I have also fully reinstalled the ROM with formatting everything and it still don't boot

Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?

ldeveraux said:
Your bootloader must be unlocked to flash LOS on the S5, right? I have the same setup as you and running no issues at all. Are you flashing the zip after flashing the ROM?
Click to expand...
Click to collapse
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on the first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.

Jet45 said:
The Samsung galaxy S5 plus (g901F) is different from Samsung galaxy S5 (g900) si magisk work on second one but on thé first one magisk v13 never worked and it's confirmed at the lineage OS side. I'm on this case too so I confirm the issue.
Click to expand...
Click to collapse
So glad someone eles has the same problem and I'm not on my own it just seems weird how the v12 works it don't pass but all loads fine. Let hope they find why and fix it.

Flash your stock bootloader then try flashing magisk

I'm using the stock bootload not changed my bootloader
If it was the bootloader why foes v12 work fine?

No request to have any information about this ?
What do the devs need (other than time of course) to try a troubleshooting ?
How to get this logs/boot image and logs ?

Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.

Recycool said:
Managed to get it working, but did a clean install and lost it, first time I got it working I was at 19-07-2017 build with magisk manager 5.1.1 and magisk 12, with magisk folder mount and magisk ext SD access modules installed, then upgraded to 26-07-2017 build through official update from settings, and after installation I rebooted the phone into recovery and installed magisk 13.3 (as you know when updating we lose magisk root) and it worked.
Then did a clean install of 26-07 build (thinking it will work) but nope.
Click to expand...
Click to collapse
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?

Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.

Recycool said:
I tried to do that again but I couldn't. As said:
In was on 19-07-2017 build with magisk 12 sdk and magisk manager 5.1.1 app, had magisk folder mount 0.8.5 and SD card access module, then on 26.07.2017 I received the weekly update, after update I rebooted the phone into recovery and instead of magisk 12 sdk I installed magisk 13.3 (for testing) and it worked. I tried doing that again but didn't worked so I don't know what to say lol.
Click to expand...
Click to collapse
So I'll try to reproduce it at my side with that you've said, it may be a walktrough . Two brains to work on it may succeed

Jet45 said:
Hi ! Can you make a little synthetic how to ? I'd like to try it on my S5 plus (g901F) It may be a walkthrough wating any response from magisk team ?
Click to expand...
Click to collapse
I posted a logging of the problem on the main support thread, let's see what happens
https://forum.xda-developers.com/ap...sal-systemless-t3432382/page1765#post73249492

cross the fingers (I hope that you say like that in English)

Fingers crossed they sort it. Would love yo be able to use magisk again

Does anyone here have this issue on a stock ROM or is it just Lineage OS? From the log that was posted in the main support thread it looks like the Magisk installation was successful, but the system hangs on this one line before it can fully boot. I'm not qualified to read more than that out of the log though...
There's been some code added to GitHub in the last few days. Have anyone tried the latest unofficial snapshot? There was a new one built yesterday: https://forum.xda-developers.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

Hi we got anymore news on this I have tried the latest beta one and it still gets stuck at booting.

It seems there is nothing to expect from nor magisk team neither lineage team. Nobody seem want to work on this really specific problem.

Uninstalled a system app after I rooted my phone. How do I fix this?

Hey,
I am a Xiaomi Redmi 4A user. Over the past few days, I unlocked its bootloader, installed twrp. I then flashed AOSP Extended and rooted my phone by flashing SuperSU.
Today, I used the in built system device uninstaller and I uninstalled the android stock Calendar app, thinking the Google Calendar app from the play store is better and it would work. Now, I see something like 'com.android.providers.Calendar' has stopped every once in a while.
Is there any viable solution to this error that regularly keeps popping up? I do not want to flash the ROM again/factory reset/root my phone again or something like that.
Any help would be greatly appreciated. Thanks!

Try flashing Oreo gapps it may fix it just clean cache and dalvink before flashing

rseragon said:
Try flashing Oreo gapps it may fix it just clean cache and dalvink before flashing
Click to expand...
Click to collapse
Sure, it worked all right. Thanks!

mobileenthusiast said:
Sure, it worked all right. Thanks!
Click to expand...
Click to collapse
No problem bro

Front camera doesn't popup in custom ROM (only Cosmic OS tested)

Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!

S.N.A.P said:
Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!
Click to expand...
Click to collapse
Front Camera just works fine except you don't mess with the sensors while downgrading. For a flawless experience either stick to Q or P.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
Front Camera just works fine except you don't mess with the sensors while downgrading. For a flawless experience either stick to Q or P.
Click to expand...
Click to collapse
well the custom ROM is Pie-based and I'm pretty sure I didn't do anything related to sensors
anyway thanks for your answer

S.N.A.P said:
well the custom ROM is Pie-based and I'm pretty sure I didn't do anything related to sensors
anyway thanks for your answer
Click to expand...
Click to collapse
Jumping b/w Q and P roms does break the sensors.
Sent from my Redmi K20 Pro using Tapatalk

S.N.A.P said:
Hi guys
I'm quite new to the K20 Pro. Last night, my friend asked me to install some custom AOSP ROMs for him. I chose Cosmic OS first since it just got updated recently. Installed and booted up just fine, BUT here's the problem :
- First boot up and installed GCam : front camera pops up fine
- Installed 81Hz mod and Immensity kernel : still pops up fine
- Some Magisk modules like NFS, Viper4android v2.7, Google dialer framework : still pops up fine
- Substratum app and apply Liv Dark theme : front camera STUCKS after a reboot, can't even use the Motor Control app to get it pop up again
So I thought the problem lies in the Substratum and the theme but uninstalling those didn't help, EVEN clean flashing the ROM again. Changing to MIUI 11 EU rom, front camera works fine again.
If anyone knows whether the problem is in the ROM itself or conflict with the modules/theme/mod/kernel or it's a common issues in custom AOSP ROMs then please let me know asap, I'll be very appreciated.
THANK YOU !!!!!!
Click to expand...
Click to collapse
Hey, how good is the fingerprint sensor with this rom? And also can you try watching a YouTube
To see how stable the audio is.

Sukhi said:
Jumping b/w Q and P roms does break the sensors.
Click to expand...
Click to collapse
oh
I was from MIUI china stable 10.3.17 Pie, so it's just Pie-MIUI to Pie-AOSP
Does it break the sensors too ???

m1chb3ltr3 said:
Hey, how good is the fingerprint sensor with this rom? And also can you try watching a YouTube
To see how stable the audio is.
Click to expand...
Click to collapse
audio works as it should, completely normal
fingerprint works fine too

S.N.A.P said:
oh
I was from MIUI china stable 10.3.17 Pie, so it's just Pie-MIUI to Pie-AOSP
Does it break the sensors too ???
Click to expand...
Click to collapse
Nope ! I thought you came back from MIUI 11. If you're jumping within Pie, it's not a problem. There should be no other reason why the Cam won't Pop-up other than the Camera sensor fail. Did you wipe Vendor?.
Sent from my Mi A3 using Tapatalk

Sukhi said:
Nope ! I thought you came back from MIUI 11. If you're jumping within Pie, it's not a problem. There should be no other reason why the Cam won't Pop-up other than the Camera sensor fail. Did you wipe Vendor?.
Click to expand...
Click to collapse
(S.N.A.P here, just my other account)
Yes, I did wiped Vendor
At first I used TWRP 3.3.1-15 by Mauro, 5 wipe and flashing Vendor 10.3.17 + Rom + Gapps but failed at the vendor so I switched to LRTeam TWRP. This time only 4 wipe since there's no Vendor option. Flashing was ok and the phone booted up
And then everything went like the first post

75_TZ said:
(S.N.A.P here, just my other account)
Yes, I did wiped Vendor
At first I used TWRP 3.3.1-15 by Mauro, 5 wipe and flashing Vendor 10.3.17 + Rom + Gapps but failed at the vendor so I switched to LRTeam TWRP. This time only 4 wipe since there's no Vendor option. Flashing was ok and the phone booted up
And then everything went like the first post
Click to expand...
Click to collapse
Never ever touch vendor again. It's the set of drivers for your device. Go back flash the complete MIUI stock Pie rom and then continue with the Cosmic flash w/o any system/vendor wipes. Data,Cache,Dalvik wipes should be more than enough.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
Never ever touch vendor again. It's the set of drivers for your device. Go back flash the complete MIUI stock Pie rom and then continue with the Cosmic flash w/o any system/vendor wipes. Data,Cache,Dalvik wipes should be more than enough.
Click to expand...
Click to collapse
OH
My fault
Just check back some tutorials of some custom ROMs, only wipe system, data, cache, dalvik cache, no Vendor wipe needed
No wonder when I flashed MIUI 11 EU rom, popup cam works fine again
Thank you so much
I'll try again and see if it works

75_TZ said:
OH
My fault
Just check back some tutorials of some custom ROMs, only wipe system, data, cache, dalvik cache, no Vendor wipe needed
No wonder when I flashed MIUI 11 EU rom, popup cam works fine again
Thank you so much
I'll try again and see if it works
Click to expand...
Click to collapse
People are just copy pasting tutorials from old devices which have dedicated System, Recovery, Vendor etc partions and and wiping one of these won't crash the device. K20P is a system as a root device and wiping system wipes of everything except vendor. Moreover, wiping System isn't required at all as most of the roms these days have System wipe scripts already baked in and would wipe the system irrespective of whether you wipe it or not. There's no real added advantage of wiping system before you flash the rom. System wipes should only be done occassionally whenever you have really messed up something or getting FC's.
Sent from my Redmi K20 Pro using Tapatalk

Sukhi said:
People are just copy pasting tutorials from old devices which have dedicated System, Recovery, Vendor etc partions and and wiping one of these won't crash the device. K20P is a system as a root device and wiping system wipes of everything except vendor. Moreover, wiping System isn't required at all as most of the roms these days have System wipe scripts already baked in and would wipe the system irrespective of whether you wipe it or not. There's no real added advantage of wiping system before you flash the rom. System wipes should only be done occassionally whenever you have really messed up something or getting FC's.
Click to expand...
Click to collapse
OH :fingers-crossed:
That's a great tip
I'm very appreciated
Thank you :highfive: