[Samsung Galaxy Tab A series ROMs, Kernels, Recover] steadfasterX:
Frequently Asked Questions (FAQ)

Q #01: I want to report an issue. What is the proper way to do so?

I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!

If you encountered a

kernel panic

follow FAQ #6 in this post instead.

If you have issues with "just" the

boot process

follow FAQ #7 for a very easy way to grab the boot logs.

if you have an

audio issue

follow FAQ #10 instead.

If your issue is not listed there click here to proceed:

If your issue is not listed there follow the directions here briefly and I may can fix it.

Often selinux can cause issues so try that at very first:

adb shell
su
(or "adb root" when enabled in developer settings)
setenforce permissive

Try again and if the issue is gone when in permissive mode:

provide me a logcat as described

here -> on step 3 I need the SELINUX log (option D)

If that does not solve your issue follow the logcat GUIDE to provide a valid log depending on what your issue is.

Ensure you have done a

full

CLEAN install before doing so (refer to FAQ #2 for what that means).

Warning: NO SUPPORT when:

- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)

- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)

If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.

Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.

I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.

Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.

so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..

Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?

A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:

1) regular

2) full - when you (still) encounter issues

Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.

A

regular clean

install can be done like this:

WIPE -> Advanced -> select: System + Cache

Flash the ROM

reflash root addon/magisk if you want root

reflash opengapps if you want to use Google crap

A

full clean

install needs 2 steps more then the regular:

follow the steps for regular clean

go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)

REBOOT -> Recovery

Flash the ROM

reflash root addon/magisk if you want root

reflash opengapps if you want to use Google crap

It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.

Q #03: Are there any plans or a chance of official LOS builds?

no.

Q #04: Google Play shows that my device is not "certified" - how can I fix that?

First of all you must be on the latest build.

If your issue persists click here to proceed:

The second thing is you must not be rooted by the LOS root addon (afaik). Magisk has its own protections to ensure you stay certified but I hadn't the time to test the LOS root-addon.

You also need to know that google play remembers your devices last state so if you are on the latest build and still having that issue do this and it will be certified again:

android settings -> apps -> find play store -> clear data (yes data, not cache) -> reboot -> open play store -> wait 2..5 minutes -> check certified state again

Q #5: A life without Google?! Read here how:

A life without Google ? Is that possible ? ...and why you should consider it ?

So why? That's easy to answer and if those are worth it depends totally on your personal needs:

1) BATTERY. Google services are draining a LOT of your battery, so to get the most out of your battery you should abandon Google gapps

2) PRIVACY. Almost all Google apps phoning home to Google! You don't care about that? You really should. You have nothing to hide? Oh dear believe me you have no idea how much of your private data you do NOT want to share. Keep also in mind that you give your private data not to a company only , there are always humans behind and what they do.. You do not believe me? Read on

BREAKING NEWS:

You can go on with the following steps or simply head-over to /e/ OS which is LOS but completely Google-Free + microG fully working pre-installed:

check it out here!

Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:

Do the following steps:

1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone

2) Then perform the following (all one command)

On Linux:

On windows:

3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!

4) Share the logcat output from the console screen using paste.omnirom.org