Reporting Bugs
- DO NOT Report bugs if you're running a custom kernel or you installed Xposed
- Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
- Include your firmware versions in reports.
- Mention any and all Magisk modules you might be using along with the Magisk version
- If it is a random reboot, grab dmesg . (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
- If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
FREQUENTLY ASKED QUESTIONS:
<< Can I Dirty Flash over the previous Unofficial Build?
>> Yes you can!
<< Will AOSiP Become Official?
>> Fingers Crossed!
// CAUTION /// WARNING //
Some Information about ROMs / Builds with Encryption working:
The thing about encryption is that sometimes it can be a total jerk. So, pay attention to what is written below.
This may or may not happen to you! Consider this a Precaution!
If you're on an encrypted version do keep in mind that the next time you change the ROM, please remove your phone password/pattern/pin or whatever the lock is!
It is advised to do so because there is a possibility that if you haven't done that before flashing a new ROM, the boot screen will be followed by asking a password, and 90% of the time it doesn't work as expected!
Once that happens, you'd have to "Format Data" to boot into the new ROM.
Cheers everyone! Happy Flashing
