[/e/OS Project] 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 have an

audio issue

follow FAQ #6 instead.

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

if you have magisk installed:
adb shell
su
setenforce permissive

When " usb debugging root" is enabled in developer settings:
adb root
adb shell
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 your issue is not solved with selinux permissive click here to proceed:

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

logcat GUIDE

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 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.

Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.

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

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

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 /e/ builds?

Yes. With your help! What you can do? Test and report EVEN SUCCESS in this thread.

Q #4: Is there an /e/ specific FAQ?

Sure:

FAQ: click

Forum: click

HOWTOs: click (a great resource for all your first questions)

Q #5: 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 audio issue and cancel the logcat from step 2 before hanging up!

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

Q #6: I'm scared about that microG , I don't want to expose my phone so is this /e/ version a security risk?

First of all you need a lot of trust installing ANY custom ROM. A developer can do nasty things right? Besides that yes microG allowing to let apps act like as they are another app, also known as signature spoofing. This CAN be a good and a bad thing. Read on why my builds are different:

In general the microG patch is an all or nothing. A ROM which supports microG (i.e. signature spoofing) have that feature enabled, always.

The difference in my /e/ builds is that I am using the "restricted" option of signature spoofing so as long as you trust me you are as safe as without microG.

Q #7: What is the difference between CUSTOM and UNOFFICIAL builds?

UNOFFICIAL is like pure /e/ - untouched. This is the base for OFFICIAL builds (coming soon)

CUSTOM:

removed: /e/ Apps (read here why)

added: AuroraStore, F-Droid, F-Droid xtra repos (manual enable required), DNS66 (adblock w/o root), Omega Launcher (as alternative Launcher)

Q #8: Banking not working? Your app <fill-in-appname> does not work because root is detected?

So you wanna install and use a banking app or any other which is trying to detect root? The following might help you out:

https://xdaforums.com/t/rom-unoffic...ty-lock-your-bootloader.4290485/post-85164931

--> See FAQ 8 there!Yes that FAQ was written for a oneplus device but is generic for every device and model.

.-