Use Magisk and Magisk hide.
try flashing stock again and see if works or not, or try using a different headphone
You shd disable magisk under root options in aroma for moro to have unrooted install. Do a dirty flash of v5 to retain data, and then reinstall moro with this option to stay unrooted.
Follow thumb rule of wiping cache and dalvik and reboot system. If it continues to back to cronos and check if its an issue wuth morokernel and your app
morokernel fixed the battery percentage issue for me
press and hold power, volume down and home. your phone will boot into download mode. press volume up. then press and hold same key combination until screen turns black and then move your finger from volume down to volume up and keep pressing them till you boot into twrp. then do what you want.
i keep an eye so no worries, i keep track of new download count, if i dont respond in the thread that does not mean the rom is dead, and yes there is going to be a V7. because V6 is not my greatest work.We point out to Ananjasere that we still use this rom as a daily driver. so this rom is still used for many people and people using it ask the developer to update for security updates.
If we do not specify that we are using this rom, ananjaser may think that this rom is not used much and it is unnecessary to make a new update. This both upsets us and demotivates Ananjaser. :/
(sorry bad english, I use translate)
no specific reason, i have other newer phones, i work on many phones to contribute to the forum and the community.
it is not strange mate, without a way to consistently make this bug appear, it is near impossible to fix this bug. since the release of this firmware i faced this muting bug 2 times only, i dont have the luxury of debugging it well. so we are down to guessing and trying solutions until one sticksThe biggest bug of this Rom is the sudden ringtone sound disappearance (and all other sounds). It can fix only by rebooting. However, this bug happens unexpectedly and there is a very high risk of important call missing (it happened to me 2 times) . But the main purpose of a smartphone is to make and receive calls.
All other bugs can be tolerated.
However, without solving this problem, there is no point in the existence of this firmware. It's my personal opinion. It's strange that the firmware was published in April. It's been 5 months now and so far not a single fix.
we use the "deprecated" method, if you use twrp 3.5 it should recognize magisk.apk and let you flash it normally, if not, you can rename it to .zip and it will serve the same functionalityI think those instructions were different when you posted this, because now those instructions are how to install Magisk with stock ROM, which will overwrite FloydQ. I don't know what the recommended method is anymore.
I guess we're supposed to use the "deprecated" "no longer recommended" method of renaming the .apk to .zip and flashing it with TWRP? https://topjohnwu.github.io/Magisk/install.html#custom-recovery
i dont have time yet
We point out to Ananjasere that we still use this rom as a daily driver. so this rom is still used for many people and people using it ask the developer to update for security updates.Greetings to all, I certainly hope everyone is doing well Just dropped in for a little "update" request cleaning, and some of the not so nice replies. Please allow me to quote the rom Dev as to why he develops for so many devices:
This is the heart and soul of XDA. He does it because he wants to, not because he's being paid plain and simple. Based on that premise, asking for ETA's, updates or clever update requests, has been frowned upon for quite sometime on XDA. So, I would encourage everyone to please be respectful of all developers, and to not ask for ETA's or updates. They will come if and when the developer wants to release them since they have real lives and families as well, which of course may hinder things from time to time as we all well know. Thank you all for your cooperation, and a pleasant day to all.