yea I am aware about the why (and even technical details) but thanks for the link to the geo fix!
[TODAYS-SEC-PATCH-LEVEL][ROM][UNOFFICIAL][P][UsU/non-UsU] /e/ OS | BYE Google, HELLO Privacy!
- Thread starter steadfasterX
- Start date
I have the h812 model. I have the 16.0-20201024-UNOFFICIAL-812_usu rom installed. I also have the 3.4.0-PREVIEW-230_g4_P
TWRP. I have been trying to do the OTA update to a newer rom. When I do that, all what happens after the rom is downloaded
and install is pressed is that the device reboots to TWRP and just stays there. I'm supposed to have installed the 20201020 or
20201021 roms but I don't see them available for download. What can I do to make the updater work? Where are the downloaded
files stored so that I could delete them?
Also, another problem, not really a big deal. When the device is charging, the charging light is pink. But when the phone is fully charged,
the light does not turn green. Is there a simple fix for this?
Any help is appreciated. Thanks.
TWRP. I have been trying to do the OTA update to a newer rom. When I do that, all what happens after the rom is downloaded
and install is pressed is that the device reboots to TWRP and just stays there. I'm supposed to have installed the 20201020 or
20201021 roms but I don't see them available for download. What can I do to make the updater work? Where are the downloaded
files stored so that I could delete them?
Also, another problem, not really a big deal. When the device is charging, the charging light is pink. But when the phone is fully charged,
the light does not turn green. Is there a simple fix for this?
Any help is appreciated. Thanks.
The version you're on is too old bc it does not include an important ota fix. When it booted to twrp you find the file in /data/lineageos_updates (or smtg similiar) so you can install it from here manually.
Reg the led i have to check but should be fixable .
hmm I think you mean its green (not pink)? pink flashing is happening on boot only.
I found how we can set the leds on charging event so I will set it to this in my next build:
Code:
blink green while charging
solid green when fully charged
Last edited:
I finally decided to install this rom from LOS. I have the1.0-p-20210225-CUSTOM-h812_usu installed.
I did a clean install, but I blew it by not making a TWRP backup. Now the install overwrote TWRP and installed
stock recovery. Is there any way to have TWRP installed again?
Thanks
Simply follow the twrp guide to re-install (check my sig for the official thread)
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) and some other tweaks here & there
Installation instructions:
.. 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)
and some other tweaks here & thereInstallation instructions:
- follow the FAQ to do at least a regular clean flash correctly. If you encounter any issues do a full clean flash.
These are AWESOME news !!!
But I thought going official was out of the question. Has anything happened regarding this, and if so, what ? Care to share your thoughts ?
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 possibleThese are AWESOME news !!!
But I thought going official was out of the question. Has anything happened regarding this, and if so, what ? Care to share your thoughts ?
its in progress already (but depend on them atm). and no there is no ETA
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.
Alright, I've found a bug in
0.16-p-20210419-CUSTOM-h815 (clean flash) : the led blinks green (I guess ?) when the phone is charging, even when the battery led toggle is off.
oh man I wasnt even aware of that setting.. that explains a lot..
Yeah, and it's tedious to find too !
It's in Settings > Notifications > Battery light(/led/whatever)
It's in Settings > Notifications > Battery light(/led/whatever)
Hi, thanks for supporting our beloved G4!
Thanks heaps
I am a bit lost, I am running v29A at the moment and I'd like to move back to v20p in order to switch to your custom /e/ ROM. The flashable file seems to be what I need but the link is broken, can you provide a new one please?
Thanks heaps
Attachments
Updated to TWRP 3.5.2_9-PREVIEW-270_g4 and e-0.16-p-20210419-CUSTOM-h812_usu. At first I was confused by the appearance of the /e/ "Apps" store, but realized I had unwittingly installed the UNOFFICIAL version. Nope, I prefer the custom build without "Apps"! Thanks steadfasterX for making a build pretty much exactly to my liking.
Some issues/questions:
- The default Bromite browser was not able to load any webpage, with message "ERR_NAME_NOT_RESOLVED", suggesting to check internet connection and secure DNS configuration. Other apps and Fennec connected without issues. I had to look in Bromite's Settings -> Privacy and security -> Use secure DNS -> and select a provider, since it was set to Custom with a blank provider URL/IP.
- I noticed new apps DNS66 and Omega Launcher which I did not install myself. What's the reason for additions? Btw, I use Lawnchair launcher. For DNS, I know the built-in settings are very limited.. maybe that's why?
- Noticed the new feature of the green LED blinking during charging... but why? Is there any override for this? There is already a Battery Light configurable option in Settings -> Notifications -> Battery light, which I had configured for low, charging, and full states. The new feature forces itself on top of those, so that there are multiple simultaneous charging indications now, unless I turn of my customized ones and stick to the new default.
Some issues/questions:
- The default Bromite browser was not able to load any webpage, with message "ERR_NAME_NOT_RESOLVED", suggesting to check internet connection and secure DNS configuration. Other apps and Fennec connected without issues. I had to look in Bromite's Settings -> Privacy and security -> Use secure DNS -> and select a provider, since it was set to Custom with a blank provider URL/IP.
- I noticed new apps DNS66 and Omega Launcher which I did not install myself. What's the reason for additions? Btw, I use Lawnchair launcher. For DNS, I know the built-in settings are very limited.. maybe that's why?
- Noticed the new feature of the green LED blinking during charging... but why? Is there any override for this? There is already a Battery Light configurable option in Settings -> Notifications -> Battery light, which I had configured for low, charging, and full states. The new feature forces itself on top of those, so that there are multiple simultaneous charging indications now, unless I turn of my customized ones and stick to the new default.
I didn't realise that Omega Launcher was now included, but I wholeheartedly support this move, as I don't like Bliss Launcher.
Also, Lawnchair (2) is no longer maintained, while Omega is still being developped.
From what I can gather, the led blinks green (I guess) whatever the led toggle position :
Also, Lawnchair (2) is no longer maintained, while Omega is still being developped.
That's a bug. It's been reported already, both here, and in the LineageOS 16 thread.
From what I can gather, the led blinks green (I guess) whatever the led toggle position :
- If the toggle is off, you'll see blinking.
- If it's on, the led will stay on (actually, it'll blink over/under a fixed colour).
I guess I'm a bit resistant to sudden changes. I'll have to try out Omega and see how it compares to Lawnchair. I know the latter is no longer supported, but I stuck with it because I liked it best and didn't have issues with it. I had tried a whole pile of launchers when I first started using /e/ because Bliss is just... well let's leave the adjectives alone. hahaI didn't realise that Omega Launcher was now included, but I wholeheartedly support this move, as I don't like Bliss Launcher.
Also, Lawnchair (2) is no longer maintained, while Omega is still being developped.
Aha, so that's what you meant! I was confused because this was even mentioned as a feature in the "release notes" post.That's a bug. It's been reported already, both here, and in the LineageOS 16 thread.
From what I can gather, the led blinks green (I guess) whatever the led toggle position :
There's currently no way to keep the led off (AFAIK) while charging. Good luck trying to sleep in the same room as a charging phone.
- If the toggle is off, you'll see blinking.
- If it's on, the led will stay on (actually, it'll blink over/under a fixed colour).
The blinking really bugs me. I use it only for notifications that demand attention so that they get taken care of and the blinking can stop...
In any case, as long as the user has an option to override the defaults, that's what matters. Glad to know it'll be addressed.
Also, is there a way to disable the screen turning on with a "New Notification" message? That's redundant when there is a notification sound and notification LED...
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
planned.. yes. the thing is I am extreme busy. Besides that I was trying to port the G4 to AXP.OS but the cam does not work anymore at all when enabling selinux on A11 or later. so the whole thing is stuck atm while I'm ramping up AXP.OS for other devices as well..
I may have more time in 2 weeks or so and can hopefully look into that one here again -
37
brought to you by the
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? See here
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!
... 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)
- added PhoneSky a patched Google playstore working with microG
- added Lawnchair (latest from their TG group)
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!
- Check the current issues at the github tracker (feel free to help, provide logs etc!)
- 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
- 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) - 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.
- Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
- Flash /e/
- Optional (if you want root): Flash Magisk
- 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).
- Boot it (will take a bit on first boot!!! be patient!)
- Enjoy the most easy way to have a privacy focused and google-free phone!
Download
OFFICIAL builds (new install or re-install):
https://doc.e.foundation/search?q=LG G4
CUSTOM builds (new install or re-install)
https://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 CUSTOM builds have OTA support like OFFICIAL has!)
Note:
- CUSTOM builds: Builds are updated as soon as possible. There is no build cycle.
- Information pertaining to your device is displayed accordingly.
- The current build is the latest for your device.
Changelogs
- CUSTOM: posted in my Telegram build channel
- OFFICIAL: https://gitlab.e.foundation/e/os/releases/-/releases
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
- local build manifest
- repo init manifest
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: Stable
Created 2020-08-0312faq
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:
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:
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:
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:
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:
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):
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:
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:
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:
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:
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:
.-5BREAKING 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
Cooking order & LIVE cooking view
- H815
- H811
- H815 UsU
- VS986
- H812
- H810
Live - View:
- Normal view: https://shebang.binbash.rocks:8800/job/LG-G4/job/eOS-pie/job/Build all LGE-G4 models/workflow-stage/
- Blue Ocean: https://shebang.binbash.rocks:8800/blue/organizations/jenkins/LG-G4/eOS-pie/Build all LGE-G4 models/ (click at the top line )
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:
Share the log.txt as an attachment of your reply (bc txt is fine for that) or - as usual - by your favorite paste serviceCode: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
- 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
- ...... 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
.-44
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.
New posts
-
-
Trying to hack new Google Play Games Beta for Windows- Latest: anonymous_7218
