[ROM][UNOFFICIAL][P][F500,LS991,H81x,US991,VS986] /e/ OS | BYE Google, HELLO Privacy!

Search This thread

nubla

Senior Member
Sep 7, 2020
63
20
NOTE:
Unfortunately you have to disable selinux before OTA flashing will work (I promise .. one day.. OTA will just work lol).
follow FAQ #1 to find the guide on how to disable selinux (follow just that then start the OTA).
Where is that FAQ? Maybe I'm blind but even Ctrl-F didn't find any instructions on disabling selinux.

If I understood correctly, the required steps to upgrade for UsU'd devices is:
1. Follow the workaround from here.
1. apply OTA and watch briefly after pressing INSTALL
2. as soon as the device shuts down: take out the battery
3. power on and let it boot -> TWRP will pop-up and the OTA will be
applied.

2. Then update recovery to the latest, eg. TWRP 3.5 Preview 258 https://leech.binbash.rocks:8008/TWRP/g4/

Is that correct?

I can't wait to test Phonesky (in-)app purchase support! :D
 

tullyp

Member
Oct 9, 2011
24
8
On vs986, I downloaded new OTA update, /e/OS 1.0-20210119, but when hit install get "install error". To try this I uninstalled magisk and have latest 258 twrp. I need magisk to use auto dialer rilvoicefix so I'm reinstalling magisk. OTA is more work than just reflashing for me so where is the e/ update stored so can I just flash it?
@tullyp
 

nubla

Senior Member
Sep 7, 2020
63
20
Where is that FAQ? Maybe I'm blind but even Ctrl-F didn't find any instructions on disabling selinux.

If I understood correctly, the required steps to upgrade for UsU'd devices is:
1. Follow the workaround from here.


2. Then update recovery to the latest, eg. TWRP 3.5 Preview 258 https://leech.binbash.rocks:8008/TWRP/g4/

Is that correct?

I can't wait to test Phonesky (in-)app purchase support! :D
I got adventurous and tried updating to /e/ 1.0-20210119 without disabling selinux. The workaround worked, and the updated system booted even with TWRP 3.4.0 preview 230. No boot loops. I updated it to 3.5.0_9 preview 258 anyway.

As for changes:
- There is a slight difference in appearance, with the colors appearing more saturated (eg. the blue system fonts in settings).
- There is an allow/deny dialog that keeps coming up sometimes with only a cloud notification symbol/icon, but no explanation of what it is requesting to allow or deny. Confusing.
- I don't notice Phonesky / patched Google Play Store available? :( Did I miss something or was this discussed option not included?
 

Tribux

Member
Feb 3, 2016
43
5
Thanks for new update :) I didn't read it propeerly before and had to flash everything from the begining :D Now I disabled selinux with adb..
TWRP updated
One question after update should I do some cleaning fromTWRP or use it right away?
 

nubla

Senior Member
Sep 7, 2020
63
20
You probably found or warkaround but here is the FAQ :) :
FAQ #01 SELinux disable
Aha, it's in the FAQ of a different ROM :LOL: Thanks for finding it!


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

PS. What issues did you have with the upgrade without disabling selinux? I didn't disable it and so far my upgrade appears to be just fine.
 

LouMinartey

Member
Jan 20, 2020
23
7
No SIM card detected after OTA from 15 Dec 20 build to 19 Jan 21 - Non USU'd H815 on 20p modem, OTA performed by SHRP

EDIT: Flashed Modem, no fix

EDIT2: Clean flashed build 20210120, no fix

EDIT3: Clean flashed build 20201215, SIM card detected. Phone working again
 
Last edited:

tullyp

Member
Oct 9, 2011
24
8
Verizon vs986, flashed just system first of 20210120, no SIM detected. flashed back to previous system 20201215, got service. Then tried full clean flash. No SIM detected. No service. Flash back to previous version 20201215. Get service again.
@tullyp
 
Last edited:

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
As written in my TG groups (you really sbould join) the 20210120 build is buggy.

20210121 works as it should

selinux permissive is needed only during the process of OTA flashing and will not be needed anymore once flashed the latest build .

Enjoy..
 

nubla

Senior Member
Sep 7, 2020
63
20
As written in my TG groups (you really sbould join) the 20210120 build is buggy.

20210121 works as it should

selinux permissive is needed only during the process of OTA flashing and will not be needed anymore once flashed the latest build .

Enjoy..
Wait, buggy builds are being pushed to OTA?? o_O

I'm currently on 20210119, but I use it without a SIM, so I can't confirm others' issues with that.

I don't have Telegram and don't want to be forced to join just to use /e/...
 

tullyp

Member
Oct 9, 2011
24
8
As written in my TG groups (you really sbould join) the 20210120 build is buggy.

20210121 works as it should

selinux permissive is needed only during the process of OTA flashing and will not be needed anymore once flashed the latest build .

Enjoy..
I did join, that's where I saw 20210120
 

Tribux

Member
Feb 3, 2016
43
5
Aha, it's in the FAQ of a different ROM :LOL: Thanks for finding it!




PS. What issues did you have with the upgrade without disabling selinux? I didn't disable it and so far my upgrade appears to be just fine.
It just did not want to go through, showed me warning sign and messeage on top task bar "installation error", that's why i thought that I should disable selinux and after that while phone connected to PC, it worked for me from OTA, kind of because it went to twrp and autoinstalled..

As written in my TG groups (you really sbould join) the 20210120 build is buggy.

20210121 works as it should

selinux permissive is needed only during the process of OTA flashing and will not be needed anymore once flashed the latest build .

Enjoy..
Thanks for info. I will check out the group ;)
 
Last edited:
  • Like
Reactions: nubla

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
Wait, buggy builds are being pushed to OTA?? o_O

I'm currently on 20210119, but I use it without a SIM, so I can't confirm others' issues with that.

I don't have Telegram and don't want to be forced to join just to use /e/...
Well first of all I am not LG. I'm doing this alone and do not have a team of testers who verify everything is working after every build. Second the whole process of Building and pushing out to OTA is fully automated so there's always a VERY rare chance that something is going wrong here when an issue occurs during the build process. That was the case with that build version.

To be crystal clear bigger changes like the latest ones regarding the RIL stack have been tested before I pushed it out of course. But my tests are done on a single build always not on the build during the automated build process. The chance that they differ is very rare but it exists.

You're not forced to join. Absolutely not. It is just an offer and you are totally free to take it or leave it. It's just that important information and change logs are pushed there only (or at least more early).

if you don't want to join I would recommend to wait at least one week before doing an OTA. usually that is enough to let other users find bigger issues and so let me make a new build or removing it from the OTA server.
 
  • Like
Reactions: LouMinartey

nubla

Senior Member
Sep 7, 2020
63
20
if you don't want to join I would recommend to wait at least one week before doing an OTA.
Ok, that works. It would be nice to see changelogs here too, but I get that it's annoying to keep info synchronized in multiple places. It's cool that the build is fully automated.

Could you perhaps just let me know if/when the (in-)app purchase support patched Phonesky makes it into a build? The inability to use one important app (OBDLink) that requires that support is the only thing holding me back from full enjoyment of the setup.

Otherwise, I'm super happy with the LG G4 and your /e/ builds. 👌🥂 Thanks for continuing to support it.
 
  • Like
Reactions: steadfasterX

LouMinartey

Member
Jan 20, 2020
23
7
These things happen, always gonna get the odd bad egg. I could've just restored a backup but I wanted to make sure I hadn't FUBAR'd it myself and a little troubleshooting goes a long way. Thanks for keeping my zombie-ass half-dead-CPU G4 alive, it overheats itself to pieces on most other roms if I don't disable some cores (Thanks, Google)
 

llarr

Member
Dec 2, 2020
5
2
On latest - 21 January update, did notice this behaviour on earlier versions though.

I have noticed something odd and could use some advice narrowing it down. Basically if I turn the wifi on at 8am - 8.30am in the morning (GMT) and then leave the phone to idle, there's maybe a 50% or more chance there will be excess battery drain to the tune of 6.5% battery per hour.

Never had this issue when turning the wifi on in middle of the day or the evening or leaving the wifi on overnight and then throughout the next day.

Looking at battery stats it seems to be phantom drain that isn't associated with anything in particularly, but it does stop as soon as I turn wifi off.

The phone stats claim the cpu is in deep sleep during this. I wonder if there is some sort of update check scheduler. Maybe my phone goes crazy renegotiating its wifi connection for some reason under these specific circumstances. Any tips, basically my work around is to try to remember to check the phone after 20-30mins and if it has dropped 2-3% while idle then toggle the wifi and that tends to fix it. Very odd.
 

steadfasterX

Recognized Developer
Nov 13, 2013
5,678
15,000
On latest - 21 January update, did notice this behaviour on earlier versions though.

I have noticed something odd and could use some advice narrowing it down. Basically if I turn the wifi on at 8am - 8.30am in the morning (GMT) and then leave the phone to idle, there's maybe a 50% or more chance there will be excess battery drain to the tune of 6.5% battery per hour.

Never had this issue when turning the wifi on in middle of the day or the evening or leaving the wifi on overnight and then throughout the next day.

Looking at battery stats it seems to be phantom drain that isn't associated with anything in particularly, but it does stop as soon as I turn wifi off.

The phone stats claim the cpu is in deep sleep during this. I wonder if there is some sort of update check scheduler. Maybe my phone goes crazy renegotiating its wifi connection for some reason under these specific circumstances. Any tips, basically my work around is to try to remember to check the phone after 20-30mins and if it has dropped 2-3% while idle then toggle the wifi and that tends to fix it. Very odd.
well I think u know the answer. we need to take a look into the log when that happens (FAQ #1). When that happens again follow "Specific Issue", let it run for a while and then turn off wifi (logcat still running but note the exact time) and turn it on again, then let it run again for a a while.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    What is eSpeak (com.reecedunn.espeak, v1.48.15.20) and is it a default app in the /e/ build?

    I happened to notice eSpeak in my installed apps list in Aurora Store after upgrading that to v4. I don't recall seeing it before, and it is installed as a system app, so I could not uninstall it.
    its is a TTS (text-to-speech) engine and yes its included in /e/
    2
    New release! 🥳

    .. in progress (keep an eye on my TG Automation channel)

    As mentioned I do not provide changelogs besides from my TG Automation channel anymore but this one is important so I drop a note here, too.

    first of all I've changed the versioning back to /e/ standards. I've used "v1-0" in the past as I thought that will happen soon (lol) and as its used by them as the most recent branch names (e.g. v1-q). To get a better understanding of which exact version you get (and be able to identify the matching official /e/ changelogs) I will use what they use (atm of writing: v0.16). Due to this versioning change the newest update will not popup as an OTA so you have to boot to TWRP and flash it manually.

    second: I have changed the signing keys (actually one of my build scripts deleted them by accident). Because of the version scheme change this does not matter at all for you as OTA does not work anyways.

    the next & last major one: I have enabled UNOFFICIAL builds again. The reason is I am planning OFFICIAL builds. I personally like to have F-Droid, Aurora and so on already included in the ROM so I will continue doing CUSTOM builds including OTA support as well. The major diff is that some apps will be included in the ROM and "Apps" will be removed. Other then that will be identical. Until we reach the OFFICIAL state I will provide CUSTOM + UNOFFICIAL builds.

    This build contains a ton of fixes & enhancements made by @aoleary so I hope I didn't broke anything while merging his changes ;)
    oh ya and some little changes from my site regarding charging led (led blinks green when charging and goes solid green when fully charged) :D and some other tweaks here & there

    Installation instructions:
    • follow the FAQ to do at least a regular clean flash correctly. If you encounter any issues do a full clean flash.
    2
    It's fantastic to see so much development effort for such an old but still wonderful device. Thank you all! Can't wait to try it out.
    1
    v4 is not "just" a complete UI re-write but also the backend (how apps are accessed) has totally changed. This results in often having login issues from my experience. From what I heard by others it happens more often when using anonymous (i.e not using your google account). other then that it works fine so far. a disadvantage of their new approach is e.g. in v3 you can spoof your country and get apps which are country-specific. due to their major change in the backend this does not work anymore thats why some / many? apps are missing..
    The extent of the changes is why I'm surprised/happy that it's working after updating manually.

    I had no problems with anonymous login except once when the token server was down for a bit.

    The lack of geo-restricted apps in V4 was a result of increased privacy protection, but due to popular demand, the functionality has been restored, though still disabled by default: https://forum.xda-developers.com/t/...t-march-20-2021.3739733/page-78#post-84739245
    1
    These are AWESOME news !!! :D
    But I thought going official was out of the question. Has anything happened regarding this, and if so, what ? Care to share your thoughts ? ;)
    yes it was but now it will be possible ;) its in progress already (but depend on them atm). and no there is no ETA ;)
  • 29
    e-color.png

    brought to you by the
    eFoundation-1-400x61.png


    Code:
    /*
    * I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
    * Please do some research if you have any concerns about features included in the products you find here before flashing it!
    * YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
    * Your warranty will be void if you tamper with any part of your device / software.
    * Same statement for XDA.
    */

    ****
    These builds are for all G4 models: official unlocked and UsU'd devices
    ****

    UsU? http://bit.do/unlockg4


    About /e/
    /e/ is an a mobile ecosystem (ROM + onlines services) that:

    • is open source
    • is pro-privacy
    • is compatible with most existing Android applications
    • cares about usability
    • is as far as possible freed from shackles by Google and OEMs
    • already exists!
    It’s the alternative to the Apple/Google duopoly on the smartphone.

    ... so again and just to be clear: /e/ is not just a ROM, it is more a complete privacy ecosystem and consists of:
    • an installable mobile operating system for smartphones, which is forked from Android and strongly “ungoogled”
    • a set of sorted and improved default open source applications
    • various online services that are linked to the mobile operating system, such as: a meta search engine for the web, drive (with synchronization), mail, calendar, notes, tasks.


    Features

    • Based on LineageOS so a very stable base
    • microG fully pre-installed with Signature Spoofing in restricted mode!
    • All features described on the /e/ page: What is e
    • All features and fixes of my LOS 16 builds.
    • Finally I had the time to setup an own OTA server.. so my builds come with full OTA update support :)
      ... you know that thing which informs you that a new update is there and where you just click to download + install ;)


    Difference from pure /e/ or: why are the builds CUSTOM?

    • The /e/ app store has been removed completely (read the FAQ why I did this drastic change)
    • AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
    • F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
    • Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)

    The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
    This is according to the rules /e/ defined.


    Known issues:

    Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
    So back up regularly and frequently!

    1. Check the current issues at the github tracker (feel free to help, provide logs etc!)
    2. If you find a bug not listed, follow the instructions here and provide me with the logs: FAQ #1


    Requirements
    • Your device need to be unlocked either officially (h815 international or h811) or by UsU
    • Your bootloader stack should be on lastest MM version for your model. That is e.g. 20p for the H815 models or 20x for H811.
      So.. NO SUPPORT ON LOWER bootloader stacks then the latest MM version for your model
      ... and NO SUPPORT for the BETA v29A as well!!
      -> for your convenience I have created TWRP flashable files for that !!!! (click)
      Of course ensure you just use files for your model, your ARB and UsU'd or not. If unsure ask.
    • in particular that means this thread is for:
      F500, H810, H811, H812, H815 (official unlocked or UsU'd), H819 , LS991, US991, VS986
    • Latest TWRP - PREVIEW build: click or SHRP build: click
    • Do a full Nandroid backup before doing anything!


    Installation
    1. This single very first step is for UsU'd devices only (SKIP when you have an official unlocked model):
      If you have ever flashed the UsU baseband package: Clean flash the modem partition from your backup in TWRP.
      If you do not know if you ever flashed it simply re-flash your modem partition again and you can be sure. This can't do any harm.
      If you have no backup:
      - TWRP flashable MM modems (N will not work)
    2. Ensure your bootloader is current! You will have issues if you are not on the latest bootloader stack. Read the above Requirements topic to find a link to TWRP flashable files.
    3. Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
    4. Flash /e/
    5. Optional (if you want root): Flash Magisk
    6. Flashing OpenGapps ????? NO No no! you don't want that on a google-free phone! /e/ contains everything you need to live without Google! So flashing OpenGapps on /e/ is like using a bit more secure LOS but that's not the point of /e/. Either try without or go with LOS (imho).
    7. Boot it (will take a bit on first boot!!! be patient!)
    8. Enjoy the most easy way to have a privacy focused and google-free phone!


    Download

    Get your builds from my leech server (new installs or re-installs)
    http://leech.binbash.rocks:8008/e-os/pie/

    If you have /e/ installed already and just want to update to a newer release:
    Android settings -> Updater (yes my builds have OTA support!)

    Note:
    1. Builds are updated as soon as possible. There is no build cycle.
    2. Information pertaining to your device is displayed accordingly.
    3. The current build is the latest for your device.


    Changelogs

    • search results from this thread: click


    Support
    Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
    and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here


    Credits
    • LineageOS (the base of /e/)
    • The /e/ foundation and all related devs making this experience possible!
    • The Suicide-Squirrel team (ThePiGuy, kessaras, steadfasterX)
    • aoleary
    • and more..


    Sources

    XDA:DevDB Information
    g4_eos-pie_custom, ROM for the LG G4

    Contributors
    steadfasterX
    Source Code: https://gitlab.e.foundation/e

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: latest MM firmware for your model !
    Based On: Lineage OS

    Version Information
    Status:
    Beta

    Created 2020-08-03
    Last Updated 2020-11-20
    11
    faq

    Frequently Asked Questions (FAQ)

    Q #0: Why is the /e/ App store not included??? It is GREAT!
    Mainly due to security and privacy concerns. Wth? I thought /e/ is secure and privacy focused? Yes it is but.. read on:

    First of all the App store itself has no security or privacy issues. It is opensource and I see no issues with the app itself!
    ... the most important point for a smartphone is the availability of apps. I mean having a secure device which respects your privacy is great but it will have no chance to win when you cannot get easily apps on it.
    ... and the most dangerous part for a smartphone is installing apps because here is where Malware can easily step in! So whatever you do never install APK files from a website directly unless you can be 100% safe it is trustworthy.

    It is all about trust again and when you look in the sources of the /e/ Apps store you find it connects to: cleanapk.org.
    /e/ makes that not a secret though as you can read here.
    So who is behind that cleanapk.org? Why is /e/ trusting them? While reading through the /e/ forums I found that this page hosts (as far as we know) apps mirrored from apkpure + fdroid.
    .. and it's completely unclear who hosts that site and where is behind it. On the other site /e/ (Gael, the founder as well) states clearly they are not in any relation to that site. "They just using their api".

    here some facts:

    • you cannot get the owner by a whois request
    • They have a info page here which just roughly describes where the apps are coming from and how
    • There is no detailed privacy statement or even an info if they keep your data GDPR compliant or not
    • No way for devs to get their apps removed or updated

    The /e/ foundation clearly states they have no relationship to that repository of apps but some things are interesting aren't they:


    During that mentioned discussion and after pointing Gael to that - the welcome message suddenly changed to what it is today..
    The full topic where even Gael is talking (not that friendly) is: here

    TL;DR:
    /e/ is providing apps (the most used way to get infected by malware) by an API which is at least questionable.
    I do not say /e/ is doing questionable things and as said before the /e/ ROM is 100% trustworthy (otherwise I would not do any builds for it) but that cleanapk.org site is truly another story.
    An interesting quote of Gael can make one read between the lines (I marked the interesting ones bold and cursive):
    Some users have reported that they are using Aurora, [...] (context: we will never integrate this) because it’s infriging the play store terms of services.
    For this, we have to use indirect mechanisms, that don’t infrige the play store TOS, and therefore, we are using a service that is not officially part of the /e/ project, and which is called cleanapk.org
    On the long run, we other plans with partners, to offer something more transparent, but it’s too soon to talk about this.
    Of course /e/ needs to ensure that what they are doing is 100% legal and offering an app repository like cleanapk.org is not.
    My personal assumption is that /e/ is offering that repo - indirectly so not officially by the e.foundation itself.
    A relation between is for sure nothing they want to have public as this would cause legal questions.

    So the last question is:
    Q: Why do I consider AuroraStore "better" then using cleanapk.org and so removed the /e/ apps store and adding AuroraStore instead?
    A: Because I definitively know where the apps are coming from when using Aurora instead of /e/. Not just the app itself is OSS (like the /e/ one) the apps are coming directly from the play store instead of an unknown source.


    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:

    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 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.
    Pro-Tip: set magisk to 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 Factory Reset and let it do its job
    • 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 this in progress (as of April 2021) and so should happen somewhen in 2021


    Q #04: Will this ROM support / pass SafetyNet?
    When you install Magisk you can hide and so yes you might be able to pass SafetyNet. Which can change every day though because even when that might work atm you should note the following:
    Magisk has its own protections to ensure you pass safetynet but this is something which will change one day and there is no known method yet to workaround that.


    Q #05: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
    TLDR;
    There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
    Details:
    we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
    the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
    the big cluster will run ONLY when it is NEEDED - i.e. high load.
    so when you look closer: those are not DISABLED they are IDLE which is a big difference.



    Q #06: I get a kernel panic or green/purple/blue screen how to grab logs for this?
    When you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM and so erase the needed logs):
    1) reboot (without taking out the battery!) to either TWRP/SHRP or (if you have root access) to your ROM
    2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
    If you don't have a pc near you can do it directly from the device as well:

    Enable the terminal app in developer options or download any
    Open the terminal app.

    su
    cd /sdcard/Download
    tar czf pstore.tgz /sys/fs/pstore

    Attach pstore.tgz to your post.

    It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.

    Developers note:
    convert PMSG log (requires a linux system):
    Code:
    tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 | sed 's/TENS\s/\n/g' > readable-pmsg.txt


    Q #07a: I get a kernel panic on boot or having other boot issues but the pstore log are empty! What should I do?
    Q #07b: How can I provide a clean boot log?


    Since a while there is a very easy way to provide debug logs for the boot process. Before my convenient logging you had to follow FAQ #1 to grab them and it was a bit of PITA for some users.
    So here you go for a much easier way:

    1. boot Android
    2. once booted : reboot to TWRP/SHRP
    3. when you have a bootloop instead: take the battery out just before the bootloop occurs, or better press the key combo to get into TWRP all the time to eventually get there directly
    4. once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
    5. open a terminal on your PC and type:
      Code:
      adb pull /cache/debug/boot_lc_crash.txt
      adb pull /cache/debug/boot_lc_full.txt
      adb pull /cache/debug/boot_lc_kernel.txt
    6. paste one by one to a paste service like https://del.dog/ , https://paste.systemli.org/ or https://paste.omnirom.org/



    Q #8: upgrade your bootloader stack only?! Read here how:
    Check the OP of this thread which has TWRP flashable files linked.


    Q #9: Is there an /e/ specific FAQ?
    Sure:

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


    Q #10: 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:
      adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"

      On windows:
      adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "

    • 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


    Q #11: 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 #12: I have graphic glitches / issues, what can I do?
    My builds using skiaGL instead of OpenGL since a while. skia is the new and faster renderer coming with pie by default but it can cause graphic glitches in some applications and/or situations.
    Is there any fix for skiaGL coming? No, details here .
    To check if your current ROM version is using skiaGL do this:

    Code:
    adb shell getprop debug.hwui.renderer
    If you get an empty result it means skiaGL is active.
    If for any reason you wanna go back and enforce OpenGL you can do so by

    temporary (immediately activated):
    Code:
    adb root (must be enabled in dev options)
    adb shell setprop debug.hwui.renderer opengl

    or make that change persistent:
    Code:
    boot TWRP
    backup system
    mount system
    adb shell
    echo "debug.hwui.renderer=opengl" >> /system/build.prop
    sync
    reboot


    .-
    5
    BREAKING NEWS
    I've decided to create a Telegram group for all stuff around Android : here
    and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here

    New builds are cooking...

    I have added a test in my jenkins build process to ensure that the unified device tree is working as it should.
    Unifying our device tree makes it much easier to maintain and to add other not-yet added models - while it comes with the risk something goes wrong when it comes to blobs.

    Nevertheless:
    I would highly recommend doing the following (I have done that in my manual builds but you get it from jenkins - so there is a tiny little chance of bad luck .. ):

    Pre-Cautions | Flashing instructions

    1. Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
    2. Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
    3. Flash LOS - DO NOT choose to reboot afterwards - stay in TWRP.
    4. TWRP menu: "Mount" --> choose "System"
    5. From a terminal execute:
      Code:
      adb shell md5sum /system/etc/firmware/venus.mbn
    6. Compare the value (last 4 characters is fully enough) with these:
      If you flash:
      h815, f500, h818, h819 it should be: d1f6fe863643b1e8d1e597762474928c
      h810, h811, h812, ls991, us991, vs986 it should be: 78e5cf520d0de4a413ef1cfa7bbbe713
      WARNING: If that checksum is NOT as it should be: DO NOT PANIC! simply FLASH the PREVIOUS LOS version BEFORE booting!. This will ensure you will not blow a fuse.
      While the above test should be considered safe: If you are unsure about this procedure: WAIT before flashing until someone (or I) had done the above quick test from the builds jenkins is providing at my leech server.
    7. Whenever an error occurs while flashing in TWRP (e.g "E1001: Failed to update system image.Updater process ended with ERROR: 7")
      or if the above checksum does not match:
      provide the recovery.log (FAQ #4 A)!!
      ... then flash the previous LOS version to get back to life - without harming your device.
    8. if instead (as we all expect) all went well and you had opengapps before - ensure you reflash gapps

    Cooking order & LIVE cooking view

    • H815
    • H811
    • H815 UsU
    • VS986
    • H812
    • H810

    Live - View:


    Noteworthy Changes:

    Flashing method: "REGULAR CLEAN FLASH" is REQUIRED!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    (See the FAQ #2 of the LOS thread how to do this)




    • If you encounter any overheat or lagging issues follow this:

      Code:
      adb shell
      logcat -b all  -d | egrep -i "thermal|kill" > /sdcard/Download/log.txt
      ps -A  >> /sdcard/Download/log.txt
      free -m >> /sdcard/Download/log.txt 
      logcat -b crash -d >> /sdcard/Download/log.txt 
      exit 
      adb pull  /sdcard/Download/log.txt
      Share the log.txt as an attachment of your reply (bc txt is fine for that) or - as usual - by your favorite paste service

    • Platform Security Patch: 2020-08-05

    • Due to some user reports I reverted the GPS updates by kessaras. Please let me know if GPS works better with this build or not.

    • New signing keys. You may now the "Trust" feature by LOS telling you if the build is trustworthy or not?! It checks if selinux is enforcing (it is in my builds) and if non-default signing keys (I sign my builds with my own ones) are in use.
      The signing keys are required to allow installing OTA updates (it downloads, checks if the signature is mine, rejects if not or accepts and installs if).
      Unfortunately I had to re-generate the signing keys that means you have to install this new build as usual in TWRP.
      All builds after that one will fully support OTA. sorry for that :p

    • ...... and more. Read "Full details"


    • Full details:
      kernel: commits
      g4-common tree: commits
      g4 unified tree: commits
      /e/OS: gitlab


    Keep in mind that almost all pie ROM's sharing the same common device tree (or main parts of it), same model device trees and for sure the same kernel - so you can enjoy most fixes for any pie ROM available.. :victory:

    ok enough of words, just one more thing:
    flash and enjoy this privacy focused and totally Google-Free experience :D


    .-
    3
    Would you care to build a last Pie version then ? Or is your e-1.0-p-20200826-CUSTOM-h815 build the latest already ?
    there is already a newer release (yesterday) ;) only posted in my TG group.. I may stop posting new release infos on XDA completely so better join ;) (find "automation" link my sig)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone