Related
THIS THREAD WILL NO LONGER BE UPDATED AS THE THREAD IS NOW OFFICIALLY HERE!https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508https://forum.xda-developers.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508
:good:
YouTube Link!
"Listen to the Dolby Atmos™ Difference!"
Dolby Atmos™
for
Android Oreo
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Description:
Dolby Atmos™ Digital Signal Processer with effects and Graphic User Interface ported from the latest ZTE™ Axon 7 Android Oreo firmware.
Dolby Atmos™ sound effects applied to media audio output supporting various media players.
MiFavor Music Player from the same firmware included only because of its Settings option to directly launch Dolby Atmos™ for testing purposes such as the possibility of additional features and/or other unique functionality.
Flexible custom recovery installation archive supporting Magisk and SuperSU installations including the options to install directly to /system for Magisk users and to install to /su for SuperSU¹ users. ¹ Experimental
Details:
A minimum of SDK 26 (Android 8.0) is required for installation to begin, else Exit 1 will abort the recovery installation activity.
Magisk users are provided the option of installing directly to /system instead of creating a Magisk module using the included arise_parameters.prop.
SuperSU users with the systemless root solution are provided the option of creating a SU module instead of installing directly to /system. This is similar to Magisk module installations and is a great alternative for those with insufficient /system space to accommodate a /system installation among other benefits Magisk users enjoy.
arise_parameters.prop may be extracted from the installation archive, placed directly into root of internal storage (e.g. /sdcard/arise_parameters.prop), and edited (details and instructions inside prop file) before installing the archive in recovery.
arise_parameters.prop (with no options active) will be automatically placed in the root of internal storage if not already present during the installation in recovery.
SuperSU users and Magisk users instructing a /system installation via a prepared /sdcard/arise_parameters.prop are encouraged to confirm a minimum of 100MB of /system space is available before beginning installation in recovery.
Magisk users performing the default Magisk module installation and SuperSU users performing the optional systemless installation will require 100MB more than the minimum available /data space acceptable (usually 500MB, 500MB + 100MB = 600MB).
Permissive SELinux Mode is currently required and will be set automatically each device boot. Do not install archive if this is not acceptable.
Third party audio effects and DSP's such as https://forum.xda-developers.com/showpost.php?p=75262097&postcount=201 ViPER4Android (<--
link to @docnok63's solution :highfive may require some extra effort to allow processing due to Dolby Atmos' dependency on its output_session_processing music effect.
Instructions:
Performing a backup of the /system partition in recovery is encouraged for users other than Magisk users receiving the default installation in recovery:
TWRP > Backup > Check System > Edit name, if desired > Swipe to perform backup operation
Confirm device requirements are met and installation results are acceptable.
Confirm an escape route is available in the event of unsuccessful device boot or unsatisfactory experience.
Confirm successful download and location of downloaded archive(s).
Boot to recovery > Install > *.zip > Swipe to perform installation operation > Advanced > Copy Log > Reboot
Updating procedure is no different unless specified otherwise.
Additional Information:
Escape routes for unsuccessful/unsatisfactory installations:
Magisk Module Installation:
If booted, navigate to /magisk using a capable file manager application and delete /dolbyatmos before rebooting the device. If experiencing an unsuccessful device boot, boot to recovery using the appropriate hardware button combination for the device, install the Magisk Recovery Management archive attached below, and follow the given instructions to delete the Magisk module (/magisk/dolbyatmos).
SuperSU/Magisk /system installations:
Restore Backup in recovery if available: TWRP > Restore > appropriate backup folder > Check System > Swipe to perform Restore operation
Install the currently installed rom zip in recovery without any partition wipes or install a different rom zip according to the rom developer's installation instructions.
Reporting bugs/failures:
An acceptable report will include the /sdcard/recovery.log received after the installation session before booting from recovery even if the recovery session appeared to be free from any error. An acceptable report will include relevant information/details to equip me to efficiently address the report.
Auditing:
Assessing the installation is encouraged for all users and is especially helpful when the collected information is included in reports of less than perfect experiences.
Dumpsys:
The dumpsys utility in Android can be a very valuable troubleshooting tool, especially audio output processing related issues, when targeting the audioflinger service. Recommended terminal application's include Terminal Emulator for Android and Termux.
In Android Terminal:
Code:
su
dumpsys media.audio_flinger
OR
Code:
su -c dumpsys media.audio_flinger
The output generated upon tapping the Enter key is the information of interest and can be copied from the Terminal and pasted with a report, if necessary.
This output includes the list of successfully configured audio sound effect libraries and any successfully created effect-chains from one or more of those libraries when combined with the successful installation of an appropriate apk, Dolby Atmos being one of many examples.
Logging:
The log utility in Android is another valuable tool for many various purposes, including troubleshooting. This utility is most convenient when used with a logging application such as Matlog in order to utilize features such as word filtering and syntax highlighting among others.
Using the logging application's search feature, the user can filter the displayed log output using words or characters relevant to this Dolby Atmos™ port such as: dolby, dax, dlb, dseffect and include that relevant log output with reports, if necessary.
Testing:
The possibility of my experience being different from others' experiences is always present! Those meeting the installation requirements may certainly test against various aspects stated as facts within this OP such as compatibility with other audio effects, functionality in Enforcing SELinux Mode, etc.
Vulnerabilities:
The installation, as with any device content, is not immune to impact from existing and future installations of custom content. This custom content may remove or modify necessary content, or introduce conflicting content preventing Dolby Atmos™ from functioning as intended by this mod's installation. Security measures can block these scenarios from occuring but will typically be implemented only after the discovery of such cases of "breaking" Dolby Atmos™ functionality, in which case, the relevant vulnerability will be omitted from this particular section.
Audio Modification Library (ver: ? - 2.9):
Scenarios: The AML 2.9 Magisk module has been found to remove a necessary audio effects configuration entry upon every device boot, if found by AML's detection mechanics targeting content to eradicate. This vulnerability for the Dolby Atmos™ system exists in every installation method if AML 2.9 is installed.
Solutions: Until this vulnerability is no longer exploited by the AML 2.9 Magisk module, the appropriate AML uninstallation procedure must be performed to restore Dolby Atmos ™ functionality. Fortunately, this vulnerability can be addressed quickly due to the active development of AML in addition to existing and active communication with AML authors.is currently being accommodated by the AML authors and should no longer present an issue with the next AML update. Props to the AML guys for focusing on securing a complimentary experience with this single package. :good:
Downloads:
Android File Host
Latest: 20180125[*]MD5: 7e0631ce15c0d4fed611842b25c21bd6
Changelog:
Code:
[B]20180125 -[/B]
- Adjustment to Xposed detection.
Code:
[B]20180124-1 -[/B]
- Unique atmos library and effect
UUID to accommodate native Dolby
effects.
[B]20180124 -[/B]
- Adjustment to Magisk variables with
existing audio effects configurations.
[B]20180122-2 -[/B]
- Mount magisk.img with Magisk's
util_functions.sh if initial mount
attempt was unsuccessful.
[B]20180122-1 -[/B]
- Correction to audio effects
configuration manipulation.
[B]20180122 -[/B]
- Correction of introduced errors.
[B]20180121 -[/B]
- Extensive adjustments to installation script.
- Addressed Pixel, Samsung, /su module, and
general installations.
- Removed previously bundled music player.
- Beginning of DolbyAtmos.apk customization
and experimentation.
[B]20180120-1 -[/B]
- Conservative shift of boot scripts.
[B]20180120 -[/B]
- Various and discriminate installation
and boot script adjustments.
[B]20180119-3 -[/B]
- Third time's the charm??
[B]20180119-2 -[/B]
- Yet another correction to boot script.
[B]20180119-1 -[/B]
- Correction to boot script.
[B]20180119 -[/B]
- Extensive adjustments to systemless
module creation and boot script.
- Removed build properties.
- Default installations intended to
accommodate HTC devices.
[B]20180117-1 -[/B]
- Correction to
/odm/etc/audio_policy_configuration.xml
symlink.
[B]20180117 -[/B]
- Various script corrections.
- Recovery Management zip now supports
SuperSU's /data/su.img and is now included
in the Dolby Atmos zip for convenient access.
[B]20180114-4 -[/B]
- More script corrections.
[B]20180114-3 -[/B]
- Script error correction.
[B]20180114-2 -[/B]
- Further script changes.
[B]20180114-1 -[/B]
- Adjustment to supported .prop detection.
- Removed experimental /*_contexts patches.
- Various script changes.
[B]20180114 -[/B]
- Corrected Magisk module installation.
- Added systemless installation option
for SuperSU users (/su/dolbyatmos).
- Updated /sdcard/arise_parameters.prop
(will overwrite the no longer supported .prop).
- Various script changes.
[B]20180112-2 -[/B]
- Added missing setprop section
to script in /system installations.
[B]20180112-1 -[/B]
- Added two library dependencies
to accommodate devices without
either library. (@Zackptg5)
- Adjustment to vendor partition
audio effects configuration
detection. (@Zackptg5)
- Added Xposed alert describing
potential conflict and potential resolution
of Dolby Atmos functionality. (@MMWolverine)
- Added /system free space detection,
resolution methods, and installation exit
for /system installations destined to fail due
to insufficient space to accommodate the
Dolby Atmos system.
Massive shout out to the many users
responsible for the current success rate
enjoyed by this Dolby Atmos Oreo solution!
:highfive:
[B]20180112 -[/B]
- Updated Magisk module.prop to 1530
[B]20180112 -[/B]
- Updated Magisk module.prop to 1530
[B]Initial Release -[/B]
-
Nice work
Sent from my LG Nexus 5X using XDA Labs
Dos this work on the 5T also ?
SlyUK said:
Dos this work on the 5T also ?
Click to expand...
Click to collapse
I have successfully tested both Magisk module and /system installations (Magisk, not SuperSU) on the OnePlus 5 Open Beta 3 during the past seven days or so.
Testing elsewhere has been very minimal and unsuccessful, however, the installation script has continued to improve significantly since the most recent unsuccessful report, and is nearly perfect for the time being.
A successful and compatible installation absolutely hinges upon /system/bin/audioserver (introduced to Android devices with Nougat) of the device. This discovery was made last year when I ported the very first Nougat Dolby Atmos system, which ironically, was from the Axon 7 device as well.
This binary service is crucial to the current Dolby Atmos systems used in Nougat and now Oreo in their native environment. However, this file has completely different dependencies in Oreo than it does in Nougat thanks to the drastic changes to the audio framework in Android 8.0, and still more changes in Android 8.1.
Furthermore, it is not uncommon for /system/bin/audioserver to exist in several forms for a device in the various custom rom's available, so the rom currently installed on the device can play a critical role, although stock firmware seems to always have the better chance, at least for last year's Axon 7 Nougat Dolby Atmos port. For development purposes and efficiency, I only run stock firmware on my device.
When upgrading firmware or changing rom's, pay special attention to /system/bin/audioserver, as any change may allow a successful installation for a device achieving only unsuccessful installations previously. Typically, these unsuccessful installations result with device boot failure due to the media.dolby_memoryservice audioserver overwriting the existing audioserver on the device.
There is no way around this audioserver dependency, but we can certainly learn as much as we can by building a database of device audioservers with two groups:
Successful
Unsuccessful
I was able to determine audioserver compatibility accurately for Nougat, and the same should be possible for Oreo, although using different mechanics, I imagine.
I'll add a link to my Drive where users can upload a successful/unsuccessful audioserver to the relevant folder some time today. :good:
Two questions:
is this independent of the "audio tuner" comming with OOS 5.0.1 or is this a replacement?
Does it work with BT connected headphones?
bormo said:
Two questions:
is this independent of the "audio tuner" comming with OOS 5.0.1 or is this a replacement?
Does it work with BT connected headphones?
Click to expand...
Click to collapse
Fantastic questions! :highfive:
#1:
Embarrassingly, I completely forgot to check Audio Tuner (Dirac) while testing headset output for Dolby processing a few days ago.
It will be a day or so before I am able to test your inquiry as I am currently "in the doghouse" with my wife (AKA friend's couch), but I would be very surprised if Audio Tuner was negatively affected in any way by this Dolby Atmos installation.
Dirac is typically quite persistent in informing the user of any conflicts and I know for certain that Dirac has not complained once, at least in my usage this week.
#2:
Unfortunately, by not possessing a pair of Bluetooth headphones, I have no way of testing your inquiry. However, my audio sessions are almost exclusively Bluetooth output into a Sony SRS-X88 speaker system and I can confirm success. :good:
Hi,
Atmos GUI force closes for me on OOS 5.0.1 with Magisk 15.3. Flashed in codeworkx and blu_spark TWRP recovery. Logs attached.
Previously I was using Ainur Sauron MK II and your Dolby/V4A Oreo ports from the A.R.I.S.E. forum. Everything was working alongside the Dirac Audio Tuner. Of course I uninstalled those mods before flashing this new port.
MMWolverine said:
Hi,
Atmos GUI force closes for me on OOS 5.0.1 with Magisk 15.3. Flashed in codeworkx and blu_spark TWRP recovery. Logs attached.
Previously I was using Ainur Sauron MK II and your Dolby/V4A Oreo ports from the A.R.I.S.E. forum. Everything was working alongside the Dirac Audio Tuner. Of course I uninstalled those mods before flashing this new port.
Click to expand...
Click to collapse
Thank you very much for the report and included information! :good:
It seems the sound effect libraries may not be properly configured to allow the apk to function properly.
Would you mind providing the output generated from following the Dumpsys procedure detailed in the Auditing section of the OP?
Thanks again! :good:
guitardedhero said:
Thank you very much for the report and included information! :good:
It seems the sound effect libraries may not be properly configured to allow the apk to function properly.
Would you mind providing the output generated from following the Dumpsys procedure detailed in the Auditing section of the OP?
Thanks again! :good:
Click to expand...
Click to collapse
Dumpsys attached, hope that helps.
MMWolverine said:
Dumpsys attached, hope that helps.
Click to expand...
Click to collapse
This absolutely helped and did, indeed, confirm my suspicion of an audio effect configuration issue. :good:
The dumpsys output confirms that a vendor audio effects configuration is sourced, so our next step is to examine any audio effects configurations existing in /system/vendor/etc (anything similar to audio_effects.conf, including audio_effects.xml).
Be sure to also confirm the presence of /system/(lib&lib64)/soundfx/(libswdap.so&libswvlldp.so)
:good:
Ok, libswdap.so & libswvlldp.so are present, I've attached audio_effects.conf file and a screenshot of everything inside system/vendor/etc
MMWolverine said:
Ok, libswdap.so & libswvlldp.so are present, I've attached audio_effects.conf file and a screenshot of everything inside system/vendor/etc
Click to expand...
Click to collapse
It appears audio_output_policy.conf was "thumbed" instead of audio_effects.conf lol. Thank you for the screenshot, audio_effects.conf is the only file necessary to examine. :good:
guitardedhero said:
It appears audio_output_policy.conf was "thumbed" instead of audio_effects.conf lol. Thank you for the screenshot, audio_effects.conf is the only file necessary to examine. :good:
Click to expand...
Click to collapse
Waiting for the solution as mine one also isn't opening. keeps stopping.
@guitardedhero You know I had to try this ASAP! I'm on OOS 5.0.1, Flash kernel 2.15.1, Magisk 15.3, codeworkx recovery. @ahrion and @Zackptg5 's V4A installed through Magisk Manager, and this mod. It installed flawlessly and I haven't had any crashes like others are reporting. Atmos sound amazing and was sorely missed. I just wish AM3D worked with our device. The only think I noticed is that that notification can't be swiped away nor does it launch the app. No biggie.
Strong work!!! :highfive:
EDIT: @bormo - I just verified this works in conjunction with Audio Tuner (Dirac) ...screen added
Seems the cause of the crashes in my case is Xposed. After I uninstalled it, Dolby is operating well. :good: Would like to have both, though.
P.S.
Re-installed Xposed with a cache wipe, no Dolby fc. I'll report if anything changes.
@guitardedhero
Stuck on the boot animation on my nexus 5x. I'm on latest stock 8.1 AOSP with magisk 15.3. I attached the logcat and it looks like the problem is related to audioserver. It's saying that:
Code:
library "libradioservice.so" not found
The lib is not present on my device so is it another dependency from the rom you ported dolby from? Thanks
Absolutely fantastic reports reports, guys! :highfive:
These initial hours are providing substantial insight and forward progress, much more than I anticipated when deciding to limit visibility to this single device's forum section. :good:
@docnok63, congratulations on the very first successful installation besides me on the non-native device! The confirmation of unrestricted Audio Tuner functionality is crucial for our device, in my opinion, especially if using this section for exposure, so thank you for the quick confirmation. The matter of most importance to me has been compatibility with other third-party effects, specifically ViPER4Android. Are you able to assess this compatibility? Thanks again for the help getting a Dolby Atmos solution to the Oreo users! :good:
@MMWolverine, great job targeting your conflict so quickly! I observed the Xposed mentions in your long but was not going to address it until confirming a successful installation of all Dolby Atmos content and configurations. Having not been an Xposed user for a very long time, can you suggest an effective way to determine an existing Oreo Xposed installation by the presence of content installed to the device belonging to Xposed? Thanks again for such quick reports! :good:
@Zackptg5, what are the odds of three consecutive reports providing crucial and completely different reports of 100% relevant information lol? The libradioservice.so library exists natively on my device and the dependency of it is likely only noticed if unavailable. I have studied every bit of the Dolby Atmos apk and do not recall any mention of it whatsoever, so your report is incredibly valuable to me and possibly will not be the last unless this is a "missing link", doubtful as this would all prove to have been far too easy lol! I am incorporating libradioservice.so into the default installation, overwriting the native libraries if present, until reports warrant testing a custom installation when not already present. Everything is ready to archive, just waiting on an appropriate Xposed detection before wrapping it up. :good:
Zackptg5 said:
@guitardedhero
Stuck on the boot animation on my nexus 5x. I'm on latest stock 8.1 AOSP with magisk 15.3. I attached the logcat and it looks like the problem is related to audioserver. It's saying that:
Code:
library "libradioservice.so" not found
The lib is not present on my device so is it another dependency from the rom you ported dolby from? Thanks
Click to expand...
Click to collapse
I am about to get started replacing a water heater and do not want to keep you waiting. Attached below are the two libraries native to the Dolby Atmos system with additional extensions to be supported by XDA's attachment system. I will not insult your intelligence by instructing the necessary procedure to incorporate them into your existing installation except that these are NOT vendor libraries lol. :good:
guitardedhero said:
I am about to get started replacing a water heater and do not want to keep you waiting. Attached below are the two libraries native to the Dolby Atmos system with additional extensions to be supported by XDA's attachment system. I will not insult your intelligence by instructing the necessary procedure to incorporate them into your existing installation except that these are NOT vendor libraries lol. :good:
Click to expand...
Click to collapse
Haha, it's all good
So now it's saying that libradio.so library isn't found. You wouldn't happen to have a copy of that with you? I have a feeling this may go on for a while lol
Zackptg5 said:
Haha, it's all good
So now it's saying that libradio.so library isn't found. You wouldn't happen to have a copy of that with you? I have a feeling this may go on for a while lol
Click to expand...
Click to collapse
I am proficient in patience lol. :good:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
**** These builds are for both: official unlocked and UsU'd devices ****
UsU? http://bit.do/unlockg4
Requirements
Your device need to be unlocked either officially (h815 international or h811) or by UsU
Your bootloader stack should be on MM 20p (20x for H811) or higher! (see FAQ #8 for how to upgrade your bootloader stack without lgup BUT for your convenience I have alternatively created TWRP flashable files for that !!!! (click))
in particular that means this thread is for:
F500 (UsU'd)
H810 (UsU'd)
H811
H812 (UsU'd)
H815 (official unlocked or UsU'd)
H819 (UsU'd)
LS991 (UsU'd)
US991 (UsU'd)
VS986 (UsU'd)
Latest TWRP - PREVIEW build: click
Do a full Nandroid backup before doing anything!
Installation
This single very first step is for UsU'd devices only:
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 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)
Full clean install as described here (FAQ "#2") is highly recommended. DO NOT REPORT ISSUES when you have skipped that step!
Flash LOS
Optional (f-droid is already included): Flash GApps (9.0 - ARM64) if you like to use google apps
Optional (if you want root): Flash the official LOS root-addon (addonsu-16.0-arm64-signed.zip) or Magisk (ensure you read FAQ #1 when using Magisk though)
Boot (will take a bit on first boot!!!)
Enjoy
Features
Pure LineageOS ROM experience
F-Droid included (Open Source alternative to Google Play)
Torch workaround included (no root)
BT voice FIXED
Known issuesI can't test everything on my own, so a lot of things only show up after a release. That means:
- back up regularly and frequently!
- report issues the issue tracker (see next)
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
DownloadGet your builds from my leech server
https://leech.binbash.rocks:8008/lineage/16.0/
Note:
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
only at my Telegram group
Credits
LineageOS
The Suicide-Squirrel team (ThePiGuy, kessaras, steadfasterX)
aoleary
WiZaRd981
berkantkz
sdembiske
and more..
Sources
build manifest
LEGACY XDA DB infoXDA:DevDB Information
lineage-16.0, ROM for the LG G4
Contributors
steadfasterX, ThePiGuy, kessaras, aoleary, WiZaRd981, HardStyl3r
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: latest MM / N (exact version is model dependent)
Based On: pure LineageOS
Version Information
Status: Stable
Created 2019-05-10
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:
Code:
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?
TL;DR answer is: no.
Background:
LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
For sure we do not met all and the most problematic one will be the kernel reqs as do provide a good battery life and a fast kernel kessaras had made unacceptable (for LOS) changes regarding several parts of that requirement topic. So a new kernel (branch) is needed to remove all the improvements we made which are not accepted. This process alone can take weeks (if you do not want to loose every good thing here). A much easier approach here would be to build a "just working" LOS stock kernel without any improvements and fixes and tell everyone: "Flash LOS, then a TITAN kernel afterwards". So while that might be the easier approach it will nevertheless take time to do that kernel and include the reqs + sec patches to the day.
Besides that a bit work is needed to fulfill some of the others like that.
Other then that and that is one of the most important things here:
Even when the device was accepted going official in the past (14.1... long time ago..) an incredible amount of changes happened to get oreo and now pie running. All these will be put to the test. Which actually means every commit we made will be discussed (worst case, yea, but ..) and changed. That can be from a simple "the commit message is wrong" to "pls re-write the code here". You maybe get an idea that this process is nerve-wracking (for me) and costs a lot of my free time.
Before RIL has been fixed (which had happened in the end of June 2019 first) it would have been impossible, I guess.
Now the base is fine, we could put a big amount of time into going to official to get finally ........ yea, what?
Well.. I would free resources on my build and leech server (I don't care - atm)
I would save bandwidth (I don't care - atm)
I would not need to tamper around anymore with (i.e jenkins) build issues (I don't care - atm)
you?
you would get a (LOS signed) build with a slow kernel, bad battery life and all the goodies missing... unless I build LOS kernels to bring those things back.
ok but to be honest. I can fully understand that request and I would feel better by myself when I were you. You do not know me so are my builds trustworthy ? Who knows. I could be a bad guy. :fingers-crossed:
Besides that I wrote above "I don't care - atm" so that might change in the future right? Correct.. there is no guarantee how long I can provide new builds or offer them on my leech server. There is nothing at the horizon that this might change soon but who knows? I can say that I am incredible happy with my OnePlus 6T and - believe it or not - I run STOCK OxygenOS here.. Why? It is just enough for me. So no need to do any dev there - which means all my dev time is still going here - to the G4. It is also a personal project to learn stuff around the Android eco system and woa.. who knows maybe Q came one day to the G4 as well..
... and yea official builds would give you some kind of guarantee that builds will happen - while that might change with my unofficial builds some day.
So.. as said in the TLDR above: No I personally do not have any plans in going official for the described reasons.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
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. I fixed that from the latest July (2019) builds on.
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 #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?
You need a ROM with pstore fully enabled and working (pstore = debug kernel panics/oops happened in a ROM)!
All builds starting from 2019-08-15 on support pstore due to: commit#1, commit#2, commit#3
This is a 2-site change if you want to make use of it in TWRP you must install the latest TWRP "PREVIEW" release as well (TWRP is only able to show pstore logs when the ROM is able to write them so I needed to fix pstore in the ROM first (see above commits #1 + #2 )).
Besides those 2 patches these kernel configs were set: PSTORE
You can check if a ROM does support writing pstore logs by:
as soon as possible on a fresh boot:
Code:
adb shell
dmesg | grep "ramoops|pstore"
Code:
[ 0.000000] cma: Found [email protected], memory base 0x000000001fe00000, size 2 MiB, limit 0xffffffffffffffff
[ 0.000000] cma: CMA: reserved 2 MiB at 0x000000001fe00000 for ramoops_mem
[ 0.200846] cma: Assigned CMA region at 0 to ramoops.78 device
[B][ 3.957553] console [pstore-1] enabled
[ 3.957939] ramoops: attached [email protected], ecc: 16/0[/B]
[ 3.958079] drv probe : 200 ramoops 3744
[ 6.262463] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts
or (if you are not fast enough) this ensures mostly the same check:
Code:
adb shell
ls -la /dev/pmsg0
Code:
crw-rw-rw- 1 camera camera 254, 0 2015-01-05 04:54 /dev/pmsg0
If you get no output your ROM does not support pstore logs.
From now on when you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM):
1) reboot (without taking out the battery!) to either TWRP 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:
boot Android
once booted : reboot to TWRP
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
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
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
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:
If you don't mind you can use lgup as long as you do not have an UsU'd device!
For UsU devices follow the UsU FAQ #20 instead of this one!!!!!
If you just wanna upgrade the bootloader stack without loosing data: Check the OP topic "Requirements" of this thread because:
it has a link to TWRP flashable files for updating your bootloader with just 1 click ..
Anyways if you still want to go on doing it manually instead of the easy way then:
Download a KDZ of your device model.
Keep in mind that there a frankenstein devices out there (means refurbished devices with mixed hardware inside so you think u have model XXX as it was shown in Android but the mainboard is NOT the same!).
How to identify a Frankenstein device? Read FAQ #21 in the UsU thread.
IMPORTANT: Check the ARB of that KDZ (SALT v3.11 will show the ARB of a KDZ on extract!) - If you are unsure - DO NOT PROCEED. you can easily hard brick your device if!
Extract that KDZ with SALT - DO NOT USE ANY OTHER TOOL FOR EXTRACTING! The known windows tools like LG Firmware extract does not extract what we need here and not in the way we need it! So do not use that! You have been warned..
Open a terminal in the directory where you SALT backup before flashing UsU (or your extracted KDZ) is.
Then put your device in fastboot mode and type these commands (you have another file extension? read FAQ #24 of the UsU thread):
Again this guide is NOT for UsU'd devices!!!
Code:
fastboot flash aboot aboot.bin
fastboot flash factory factory.bin
fastboot flash hyp hyp.bin
fastboot flash modem modem.bin
fastboot flash pmic pmic.bin
fastboot flash rpm rpm.bin
fastboot flash sbl1 sbl1.bin
fastboot flash sdi sdi.bin
fastboot flash sec sec.bin
fastboot flash tz tz.bin
Alternative with TWRP (if the above fastboot cmds work for you no need to do this!):
Again this guide is NOT for UsU'd devices!!!
Code:
Boot TWRP
adb push factory.bin /tmp/
adb push hyp.bin /tmp/
adb push modem.bin /tmp/
adb push pmic.bin /tmp/
adb push rpm.bin /tmp/
adb push sbl1.bin /tmp/
adb push sdi.bin /tmp/
adb push sec.bin /tmp/
adb push tz.bin /tmp/
adb push aboot.bin /tmp/
adb shell sync
adb shell "dd if=/tmp/factory.bin of=/dev/block/bootdevice/by-name/factory"
adb shell "dd if=/tmp/modem.bin of=/dev/block/bootdevice/by-name/modem"
adb shell "dd if=/tmp/hyp.bin of=/dev/block/bootdevice/by-name/hyp"
adb shell "dd if=/tmp/pmic.bin of=/dev/block/bootdevice/by-name/pmic"
adb shell "dd if=/tmp/rpm.bin of=/dev/block/bootdevice/by-name/rpm"
adb shell "dd if=/tmp/sbl1.bin of=/dev/block/bootdevice/by-name/sbl1"
adb shell "dd if=/tmp/sdi.bin of=/dev/block/bootdevice/by-name/sdi"
adb shell "dd if=/tmp/sec.bin of=/dev/block/bootdevice/by-name/sec"
adb shell "dd if=/tmp/tz.bin of=/dev/block/bootdevice/by-name/tz"
adb shell "dd if=/tmp/aboot.bin of=/dev/block/bootdevice/by-name/aboot"
Download this verify tool to ensure the flashing was successful: [ATTACH]4687157[/ATTACH] ([URL="http://leech.binbash.it:8008/misc/verifyflash.zip"]mirror --> verifyflash.zip[/URL])
Usage:
extract verifyflash.zip
adb push verifyflash.sh /tmp/
adb shell chmod 755 /tmp/verifyflash.sh
adb shell /tmp/verifyflash.sh
Read the output of the flashing on the screen and in your terminal. Do NOT flash anything else! Just the above - but ALL of the above! (if you miss a single file you will HARD BRICK)
If something is failing do NOT continue and try to re-do the above commands. if it still fails write in this thread or better come into IRC (when between Monday and Friday)!
If something failing here it WILL brick your phone.
Q #9: 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!
WARNING:
The last build supporting this spoofing method was 20210307. Everything later has that patch removed. Sorry for any inconvenience but maintaining that patch took more time then thought and for those who really care about privacy there is now /e/ OS available containing full microG support. I will leave the instructions here for those who cannot or do not want to switch to /e/ OS.
So if you feel one or both reasons might fit your personal needs here are some first steps to go (if you do NOT want to switch to /e/ OS):
1) all my builds come with FDroid which is a special app store containing just free open-source apps. As this might be a very limited I recommend to install Aurora from here which is a frontend for Google play. So search in FDroid for "Aurora Store" and let it install. Start Aurora and choose anonymous!!! and you can install everything from play as before.
2) install the microG repo in FDroid. Just open that link from your G4 and it will install the repo:
https://microg.org/fdroid/repo?fing...EB6DAB39B73157451582CBD138E86C468ACC395D14165
3) due to the fact that many apps depends on Google services as backend you need to do 2 things now:
a) developer options -> scroll down to signature spoofing and enable it *(read FAQ #11 why)
b) Download the current stable "Services Core" apk from here: https://microg.org/download.html and install it like that:
Code:
adb install com.google.android.gms-[REPLACETHIS].apk
c) if you have root:
Code:
adb shell
su
mount -o remount,rw /system
exit
adb push /tmp/com.google.android.gms-[REPLACETHIS].apk /system/priv-app/GsmCore.apk
if you do not have root, boot to TWRP now and mount system, then:
Code:
adb push /tmp/com.google.android.gms-[REPLACETHIS].apk /system/priv-app/GsmCore.apk
4) Install a location backend provider to make location services work without Google (yea Google is spying you..).
There are several available, just search for them in F-Droid:
Apple UnifiedNlp Backend uses Apple’s Wifi database.
LocalGsmNlpBackend uses downloaded GSM Cell data (local)
LocalWifiNlpBackend uses (on-device generated) WiFi data (local)
Déjà Vu Location Service uses (on-device generated) WiFi + GSM Cell data (local) * recommended
MozillaNlpBackend uses Mozilla Location Services * recommended
Radiocells.org UnifiedNlp Backend uses Radiocells.org
Also install a reverse location backend:
- e.g. NominatimNlpBackend (currently the only I know)
5) Now it's time to configure microG. Go in the app drawer and open microG settings:
you will be prompted or a notification is showing for setting permissions, go through all of them and choose allow.
UnifiedNlp settings:
- Configure the location backend service (choose the one you installed in step 4)
- Configure the address lookup backend (choose the one you installed in step 4)
Go back to the main screen of microG:
Choose Self-Check:
- Tap "System grants signature spoofing permission" and you wou get a request for allowing that (which you should do..)
- Tap Battery optimizations ignored to ensure microG is function properly
- Ensure "UnifiedNlp is registered in system" is checked (if not repeat the above steps for pushing the APK to system/priv-app)
- Ensure "Location Backends" is checked (if not repeat UnifiedNlp settings above)
Read the installation wiki for microG and install whatever else you might need:
- https://github.com/microg/android_packages_apps_GmsCore/wiki/Installation
6) reboot & re-do the self-check in microG settings
7) ensure the location service is *NOT* set to GPS-only (for LOS that means enable battery saving)
8) some general things now:
you might need to switch to alternatives sometimes. I use Waze instead of Google maps even though Google would work (but I don't like the Google spys). I use FairEmail as I love my privacy and supporting open-source. Usually you can find always an alternative, often paid apps offer activations and buying without Google play and that is often even cheaper (e.g. AquaMail costs 39€ on play and 30€ on their website etc).
There is one thing which really hurts me when it comes to gapps-less life: no smart lock. I really enjoyed it but for me the both reasons above have more weight then this.
So as you can see a life without Google has its advantages but also some changes are needed. If it's worth it depends on you. I can just recommend it
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)"
Click to expand...
Click to collapse
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)' "
Click to expand...
Click to collapse
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 LOS 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 LOS is 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. That's what I don't like.
I want the user to decide if he wants to take the risk or not and not exposing a feature for everyone even when they don't need it.
That's why the user must enable it explicitly in developer options before it gets activated (as described in FAQ #9).
All details of the implementation and why can be found here:
https://github.com/steadfasterX/android_signature_spoofing
https://github.com/Suicide-Squirrel/issues_pie/issues/30
Q #12: The ROM is lagging and/or the device gets very hot/warm, what can I do to help fixing that?
Ensure you read and understand about the ILAPO first.
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
Q #13: 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
.-
User recommendations to enhance the LOS experience
The following contains a list of 3rd party apps or mods to enhance the default LOS experience.
They are not tested by myself but recommended by the community for whatever reason..
If you miss something here post in the thread at least the app name, the google play store link to that app and a short description why it is that good.
Camera:
Google Cam as it has more options/settings.
Download Google Cam #1
or the trCamera_V5 port of Google Cam as recommended by Gigio755 here as finally videos are shown in gallery and you have also a lots of settings and advanced settings
Note: disable 2x and wide camera (in advanced settings) to avoid accidental touch and crashing camera app (just this)
Download Google Cam #2
Hedgecam 2 because it has tons of customization features & best in class (free app) manual video control options
Download Hedgecam 2
Launcher:
Nova Launcher because it feels more snappy
Download Nova Launcher
Keyboards:
Simple Keyboard because it is just that (a keyboard), also good for your privacy and available via F-Droid
Google Gboard because it has so many (but keep in mind: spying) features
Fleksy because I like it
Root:
Magisk because the LOS root-addon will be deprecated in LOS 17 and ofc because Magisk has so many nice features like hiding etc.
Download Magisk - only there - nowhere else!
Web Browser:
Via Browser, a very fast browser, clean UI, decently customizable. noteworthy features: 1) Back without reloading & 2) Use volume buttons to scroll.
Download Via Browser
Misc / Tools:
AnyMote for remote controlling IR devices because it seems to be the most stable and working one
Download AnyMote
Simple gallery pro (free when downloaded in F-Droid) as a replacement for the gallery app as it has a lot of customization options and feels much better
Download Simple Gallery Pro (F-Droid store, which is included in all LOS builds, free) alternative Download (Play Store, paid)
Frost for Facebook, a web based FB client, light, fast, & customizable. Allows for some extra control over notifications compared to the app (afaik) and it's also less cluttered
Download Frost for Facebook
TUNING:
Kernel Adiutor settings by User gkg2k for a faster and smoother experience: check out his great guide here
Note: I recommend to skip the RAM settings mentioned there when using build 20200324 or later. If you feel you still need those settings try it first without nevertheless .. I made a lot of improvements since that mentioned build so give it a go first.
.-
Nice. I never used UsU before, is that really necessary? I'm unlocked.
Glad we got Pie too. Hope it gets much more stable asap. Great work :good:
:highfive: can't wait, android pie plus LOS 16 is coming! Many thanks
Sent from my Samsung Galaxy S8+ using XDA Labs
Deleted
pedrogcsb said:
Nice. I never used UsU before, is that really necessary? I'm unlocked.
Click to expand...
Click to collapse
where do you read that UsU is necessary..?
.-
No builds atm ...
terema91 said:
No builds atm ...
Click to expand...
Click to collapse
dunno how i can say it more clear that this is in progress... https://i.imgur.com/bffYoNp.png
.-
No progress atm ...
terema91 said:
No progress atm ...
Click to expand...
Click to collapse
really? you must be god.
thread is closed for now as I do not have the time to feed trolls
.-
Builds are up for:
H811
H815
H815 - UsU
VS986
H812
H810
Before reporting issues ensure you have read the KNOWN ISSUES topic in the OP before
Keep in mind that this is brand new stuff so it may contain issues unknown yet!
That's why the whole project is declared as BETA - not STABLE.
It wasn't until Pie felt stable enough for everyday use that I released it publicly, but I still can't test everything on my own, so a lot of things only show up after a release.
So back up regularly and frequently.
If you find a bug, follow the instructions here and provide me with the logs: http://bit.do/logcat
.-
Does this have to be done for an LG G4 LS991 SV1? Or can I just straight up root no problem? Sorry. New to all this!
Stavinair Bluewing said:
Does this have to be done for an LG G4 LS991 SV1? Or can I just straight up root no problem? Sorry. New to all this!
Click to expand...
Click to collapse
afaik there is no SV1 for the LS991 but you really should go to the UsU thread and take the time to read first.
.,
This rom pass safetynet! Great, from time to time I have some lags but in general is fine, the performance of the battery is really good, many thanks and great work @steadfasterX
Sent from my Samsung Galaxy S8+ using XDA Labs
Just to say "thank you guys" for all this work !
Grazie mille, Merci beaucoup !
Looks great so far! I don't know why SELinux is disabled for me though... Is it because I flashed the ROM, Gapps, Magisk, then the high resolution video fix at the same time?
Edit: UI is a bit choppy (not too bad though), and app icons sometimes don't show when you're moving icons from the app drawer to your home screen for me. Also brightness slider might be a bit broken...
Sir Daniel III said:
Looks great so far! I don't know why SELinux is disabled for me though... Is it because I flashed the ROM, Gapps, Magisk, then the high resolution video fix at the same time?
Edit: UI is a bit choppy (not too bad though), and app icons sometimes don't show when you're moving icons from the app drawer to your home screen for me. Also brightness slider might be a bit broken...
Click to expand...
Click to collapse
regarding SELinux read the known issues. it is not enforcing atm.
yes the GL renderer is not optimal but you can try Pie's new default one if you like (known to have glitches)
just execute this (as root I guess)
Code:
setprop debug.hwui.renderer skiagl
That one works well for me but has sometimes in some situation graphic bugs. It will take effective immediately and will not survive a reboot (so must be set then again).
.-
Also, I have trouble backing up data via TWRP.... It says something about it unable to locate a storage device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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? 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)
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-03
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:
IP's of /e/ and cleanapk are at least nearby
During an ongoing discussion about exactly that topic something took my attention: the welcome notification on api.cleanapk.org was exactly at that time: https://archive.is/U1E0y (I mean.... )
/e/ itself was audited several times by a site named "infosec-handbook" and of course even they find that app store at least "mysterious"
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.
Click to expand...
Click to collapse
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:
boot Android
once booted : reboot to TWRP/SHRP
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
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
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
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)"
Click to expand...
Click to collapse
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)' "
Click to expand...
Click to collapse
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
.-
Reserved
Awesome! Nice initiative! Cannot wait to test it when I get my hands on my old G4!
Thank you so much for this port!
No more tinkering with Magisk to stub Google services.
And such good news for the OTA!
Amazing work. I just came back to my G4 to set it up as an in car GPS and this is an amazing ROM for it.
It is very smooth, the device does not overheat, and location works very well.
Thank you Steadfasterx.
Man, this is AWESOME !
The most sustainable phone (well, second to the Fairphones, of course) with the best Google-alternative ROM… Could I ever dream of something better ? OTA updates, maybe ?
EDIT (after reading fully) :
Wow… OTA updates are there. You rock. You really do !!
Thank you for the love that you give to keep this community alive. I still cannot believe that you brought /e/ to LG G4 OTA is also very exciting news.
I also appreciate that you pre-install F-Droid (it is almost the first thing I need when booting to a new ROM).
I have been running your LOS ROMs for a long time. I have heard about /e/ before, and now, I am excited to give it a shot on my h815 device! Just hoping that it receives updates along with your LOS builds.
Good luck
Does encryption work?
I imagine that it's the same limitations as with LineageOS version, TWRP cannot decrypt, isn't it?
zeduck said:
Does encryption work?
I imagine that it's the same limitations as with LineageOS version, TWRP cannot decrypt, isn't it?
Click to expand...
Click to collapse
yes it does. the limitations is not in the ROM its in TWRP so yes you cannot decrypt.
.-
steadfasterX said:
yes it does. the limitations is not in the ROM its in TWRP so yes you cannot decrypt.
.-
Click to expand...
Click to collapse
Thanks for the quick and very clear response!
Just to be sure: as we have OTA updates on this ROM, it's completly usable to encrypt the phone, even if we cannot decrypt partitions with TWRP, right?
zeduck said:
Thanks for the quick and very clear response!
Just to be sure: as we have OTA updates on this ROM, it's completly usable to encrypt the phone, even if we cannot decrypt partitions with TWRP, right?
Click to expand...
Click to collapse
correct. flashing a ROM (and so an OTA) will just modify the /system partition which is always unencrypted so no issue on that.
.-
I encrypted the phone, but now I cannot boot anymore.
The prompt for decryption pop up correctly, and I am sure of the password.
What did I do wrong?
zeduck said:
I encrypted the phone, but now I cannot boot anymore.
The prompt for decryption pop up correctly, and I am sure of the password.
What did I do wrong?
Click to expand...
Click to collapse
do you have the latest bootloader stack for your device?
.-
steadfasterX said:
do you have the latest bootloader stack for your device?
.-
Click to expand...
Click to collapse
I thought I had.
I reflashed it just in case (h815_20p_bootloader_20p_modem_TWRP-flashable.zip).
It doesn't change anything.
zeduck said:
I thought I had.
I reflashed it just in case (h815_20p_bootloader_20p_modem_TWRP-flashable.zip).
It doesn't change anything.
Click to expand...
Click to collapse
Hm strange . Did you format (!) data before ? If not try it now pls (ofc that means your data is gone).
I may can re-check tomorrow but the last time it went without any issues here....
EDIT:
hm.. thats weird. I tested it on my h815 UsU'd device with a build from 16th of July and it works fine (no PIN set). After it booted I set a PIN and choose to ask that on boot. still working fine.
on my other H815 I tested it with the latest eOS build (PIN set before) and it does not work.
same for a LOS (!) build from July. still investigating..
EDIT2:
re-flashed latest version and set no pin, encrypt, bootloops. so there must had happen something between 16th july and august.. will check
EDIT 3:
uh I was a bit too impatient. it looped just 2 or 3 times then it boots up and is encrypted now! so a workaround is to set no pin/pass before the initial encryption. Once it is encrypted setting a key works fine...
so there must be something failing on initial encryption when a pin/pass is set.. will check
.-
Sent from my OnePlus 7T Pro using XDA Labs
steadfasterX said:
:
EDIT 3:
uh I was a bit too impatient. it looped just 2 or 3 times then it boots up and is encrypted now! so a workaround is to set no pin/pass before the initial encryption. Once it is encrypted setting a key works fine...
so there must be something failing on initial encryption when a pin/pass is set.. will check
.-
Click to expand...
Click to collapse
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.
zeduck said:
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.
Click to expand...
Click to collapse
yea the strange thing is now I cannot re-produce it anymore.. whatever I do it just works all the time now..
.-
zeduck said:
I confirm, I had a password set!
Meanwhile, I reflashed the ROM after having wiped everything.
Click to expand...
Click to collapse
wait! iirc there is a bug in TWRP: after you encrypted did you tried to decrypt in TWRP?
EDIT:
nah that wasn't it as well.. damn cannot reproduce the issue..
EDIT 2:
ok finally ..
I was able to reproduce it by flashing LOS 17 and encrypting there (which is failing atm). After that encrypting in Pie (LOS and /e/) fails as well.
Have moved that into an github issue #52
EDIT 3: @zeduck
the workaround is mentioned here: https://github.com/Suicide-Squirrel/issues_pie/issues/52#issuecomment-675457810
or wait until the next TWRP preview which allows to wipe it in the UI
.-
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
Recommended: Backup (system, userdata in TWRP, your internal storage which contains your photos etc elsewhere)
Required: Do a "REGULAR CLEAN FLASH" (see bottom of this post)
Flash LOS - DO NOT choose to reboot afterwards - stay in TWRP.
TWRP menu: "Mount" --> choose "System"
From a terminal execute:
Code:
adb shell md5sum /system/etc/firmware/venus.mbn
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.
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.
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:
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:
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
...... 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
.-
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WELCOME TO 420 ROM - MAGISK ROM FOR SAMSUNG GALAXY Z FOLD 3 5G F926B (SD888)
Telegram-Group
Please bear in mind that things will be added as and when my learning and time permits (being a dad with a family and having ADHD myself means things get a lil gnarly) but i will aim to support this ROM as regularly as possible.
Ill usually release a test to one or two users before each release also - :cyclops:
CUSTOMIZABLE ONEUI EDITION MAGISK ROM FEATURES: - with Vol +/- keys
-Add YouTube Vanced - thanks to Vanced peeps github
-Add 3minit battery - thanks G Harrington - if online menus don't appear, install the apk that the module places on your internal storage in the 420rom folder.
-Add 3minit clock - thanks G Harrinton
-Add V4A
-Add custom 420rom bootanimation thanks to @chalmizzle
-Add SamsungSans fonts apk
-Add Goodlock
-Add SoundAssistant (for increased vol steps)
-Add Customized Secsettings
-Add Custom wallpapers (new for A12)
-Add custom power app with several reboot options
-Add CTS fix
-Remove Chrome
CORE MAGISK ROM FEATURES
-Detects OMC code and ensures correct OMC folders and files installed
-detects base rom or rooted stock and presents relevant install features and aborts if attempted to be installed on anything else - should help keep non compatible setups intact
-Device detection to prevent flashing on other devices
Enabled the following CSC fetures: (thanks @m8980
- Disable shutter sound menu
- Support RealTime Network Speed in status bar - working
- Enable Camera during call
- Enabled call recording
- Data usage in quick panel - the feature displays but not the actual data used - if anyone knows a fix, let me know
GOOGLE EDITION FEATURES (FURTHER TO THOSE IN ONEUI EDITION MODULE ABOVE) (coming soon!!!)
This Module is based on the main Main 420rom Rom Module but replaces some of the Samsung apps with Google ones. It is recommended to backup your Samsung apps 1st!!!
Installed with Module - Samsung App it replaces
--------------------------------------
Google Phone - Samsung Phone
Google Contacts - Samsung Contacts
Google Messages - Samsung Messenger
Google Chrome - Samsung Internet Browser
Google Calculator - Samsung Calculator
Google Calendar - Samsung Calendar
Google Clock - Samsung Clock
Google Drive - Samsung Cloud (stays installed)
Google Files - Samsung MyFiles
Google Fit - Samsung Health (can be reinstalled from Galaxy Apps)
Google Pay - Samsung Pay
Google Keep Notes - Samsung Notes
Google Photos - Samsung Gallery
Google Recorder - Samsung Recorder
Google TTS - Samsung TTS
Google Duo - n/a
Google News - n/a
Google Tasks - n/a
Google Sounds (Sound Picker) - n/a
Google Apo - n/a
Google Carrier Services (for RCS) - n/a
GBoard - Samsung Keyboard
GMail - Samsung Email
YouTube Music - Samsung Music
YouTube Vanced, Vanced Manager & Vanced MicroG - YouTube
Nova Launcher - OneUI Launcher
RECOVERY FLASHABLE BASE CONVERTOR FEATURES
-Does away with warning on splash
-Debloats a fair whack but not too much
-rooted with magisk manager
-flashes latest TWRP during Base flash
-mines stock files from phone for use in rom flash
Changelog
v2.2
- Rebased to BVA9 firmware - 1 Jan 2022 sec patch (EUY)
- TWRP updated to A8
- Magisk updated to V24001 (v24 public release)
v2.1
- Rebased to BUL8 firmware - 1 Jan 2022 sec patch
- convertor no longer debloats klmsagent so Samsung health works if version 6.19.5.017 is installed - thanks @dr.ketan and @starbucks2010 for the info
- added 420rom folder reset zip - this is sent to sdcard and is to be used only when your rom install choices arent being actioned or if old features selected are still being unintentionally installed
- roboto-thin.ttf added to firmware to stop 3minit clock fc - thanks @dr.ketan
v2.0.1
- simple bugfix for those that wish to keep bixby - no need to flash unless you use bixby or have ORD (obsessive romming disorder)
v2.0
- rebased on BUL6 OneUI 4 - Android 12 firmware
- updated magisk
- updated goodlock apps
- added new bootanimation
- added new TWRP to convertor
- added new wallpapers
- added wallpapers to dex
- removed encryption from firmware
- updated safteynet v2.2.1 fix added
- updated bluetooth lib patcher added
v1.1-b5
- added option to either keep or kill Bixby - this is done at the system level and if you nuke Bixby and want it back, you will need to restore a backup or flash the stock rooted odin files.
- added magisk 23001
- all Goodlock apps updated
- Rebased to AUI4 firmware
V1-b2
- initial xda release
what's next? & Known Bugs we can't do much about or will sort eventually
- 420rom folder in internal storage needs deleting between every fresh rom flash - this wont matter until you need to select different rom choices - just delete this folder from internal using TWRP file manager
- you may get the odd systemUI FC in dex
-if A SYSTEM APP hasn't been removed, try uninstalling it you should now be able to - any updates installed over an original system app remain as they are data apps following an update
CORE DEV TEAM
Myself - team owner and Rom Module chef
@abun880007 - team co-conspirator
Huge thanks to.................
@abun880007 for the legendary support and collab
@Zackptg5 for the brilliant MMT Extended zip
Rooted with Magisk - thanks @topjohnwu
@topjohnwu for magisk
@Winb33) for the samsungsans7.2 fonts
@superr for the kitchen
@starbucks2010 for the csc features inspiration
@Team_DeWitt for the Awesome V4A 2.7 - a must have for audiophiles!!
G Harrington for the 3minit apps
Team Vanced for bringing us all youtube Vanced
@dr.ketan for the various pointers and sage advice
Finally, @m8980, thanks for letting me adapt your CSC features into my module. :good::good::good:
DOWNLOADS
420rom website
XDA:DevDB Information
[MAGISK Rom & Base], ROM for the Samsung Galaxy Z Fold 3
INSTALL PROCEDURE
FIRSTLY ROOT YOUR DEVICE BY FOLLOWING THIS GUIDE
1 - FLASH "MASTER MODULE" IN MAGISK AND ENTER INSTALL CHOICES WHEN PROMPTED
2 - CHECK INTERNAL STORAGE/420ROM FOLDER FOR THE "BASE CONVERTOR" - REBOOT TO TWRP AND FLASH THIS FILE
3 - THIS FILE WILL DEBLOAT, PERFORM SOME OTHER UNDER THE HOOD MODIFICATIONS AND MINES SYSTEM FILES WHICH THE FINAL ZIP WILL AUTOMATICALLY MODIFY MID-FLASH
4 - REBOOT TO SYSTEM AND CHECK THE SAME FOLDER AS IN STEP 2 - FLASH THIS "ROM MODULE" IN MAGISK - ALL THE INSTALL OPTIONS YOU MADE IN STEP 1 WILL BE AUTOMATICALLY DETECTED AND ACTIONED IN THIS FLASH.
5 - REBOOT TO ACTIVATE ROM MODULE AND ENJOY!!
Please flash this module in magisk after setting up - this will prevent reboots if you accidentally hit camera app (this is an issue with unlocked bootloader fold 3s on AUHF firmware)
thanks to @ianmacd for this
Awesome! Look forward to trying this out when I take plung to mod. Thanks!
please note that you will need to wait for the stock rooted firmware to upload and then follow my rooting guide first
did you solve the problem with the camera in Rom?
unix2208 said:
did you solve the problem with the camera in Rom?
Click to expand...
Click to collapse
Sorry bud no - i havce heard there is a fix about (mishaal rahman's tweet) but til then we have to make do without
Im not expecting many rooters at the moment as a result of this camera issue admittedly but ported my rom over as i was bored
I will include the fix the moment it lands though (if its open source)
Turns out G-drive hates me everyone!!
I am re-uploading the patched AP file to Mega for my teammate to mirror - thanks for bearing with us!! (and apologies for my ADSL line eeeeek!)
Ok everyone!
The firmware has been uploaded - thanks to @abun880007
The Master Module Rom is uploading and will be live as soon as you have finished rooting - use this guide if needed
Goes without saying the camera is still borked on bootloader unlock, mind
SM-F926B ONLY!! Android 12 update and ROOT GUIDE - BVA9 rooted firmware provided - if you missed the good news, camera works :)
Hi All!! This thread will now contain pre rooted Odin files for F926B users to flash and update Before you start, download "420rom_F926B_BVA9_Odin_EUY.zip" from HERE THIS IS FOR F926B ONLY The process requires knowledge of basic adb and YOU...
forum.xda-developers.com
Links also available via our website.... - huge thanks to @abun880007 for setting this up!!
420rom
Welcome to 420rom's The home of our custom rom for the Samsung Galaxy Fold 3 5G (F926B), Note 20 Ultra (N986B), Note 10+ Series (N97##) and the Tab S6 Series (T86#)
www.420rom.co.uk
please see this post for a module to flash after flashing the rom - this will prevent the phone from rebooting when camera is pressed with an unlocked bootloader
finally - if anyone needs more urgent assistance and/or wants to come and chat crap for a bit.......
https://t.me/Home_of_420roms
exocetdj said:
Sorry bud no - i havce heard there is a fix about (mishaal rahman's tweet) but til then we have to make do without
Im not expecting many rooters at the moment as a result of this camera issue admittedly but ported my rom over as i was bored
I will include the fix the moment it lands though (if its open source)
Click to expand...
Click to collapse
Wait what is this tweet?! Can you link it or provide any details?
I spent about 7 hours yesterday rummaging through the open source kernel files for our device looking for things. Found the name of the camera, and camera driver files, but hadn't found disabling code pointing to it yet. Still have tons of code to sort through. Stopped when my head started hurting and decided to get drunk last night. Still trying to wake up lol
Acoustichayes said:
Wait what is this tweet?! Can you link it or provide any details?
I spent about 7 hours yesterday rummaging through the open source kernel files for our device looking for things. Found the name of the camera, and camera driver files, but hadn't found disabling code pointing to it yet. Still have tons of code to sort through. Stopped when my head started hurting and decided to get drunk last night. Still trying to wake up lol
Click to expand...
Click to collapse
here you go mate
https://twitter.com/i/web/status/1430946260383584257
i must admit - its natural to doubt the validity of these claims when no proof of concept is provided and also when time ebbs on
- no reason to doubt Mishaal though - a very weird situation indeed
exocetdj said:
here you go mate
https://twitter.com/i/web/status/1430946260383584257
i must admit - its natural to doubt the validity of these claims when no proof of concept is provided and also when time ebbs on
- no reason to doubt Mishaal though - a very weird situation indeed
Click to expand...
Click to collapse
I just messaged Mishaal to see if information on it was willing to be shared with us
Acoustichayes said:
I just messaged Mishaal to see if information on it was willing to be shared with us
Click to expand...
Click to collapse
It would be nice for us to be put out of our misery - whether we need to pay or not hahahaha
Wow long time no see bro (8 or 9 years ago htc desire) things have changed a tad since then!
Looks like a wonderful rom, well done old chap!..too bad I got the flip instead last week and no twrp/roms yet.
beanbean50 said:
Wow long time no see bro (8 or 9 years ago htc desire) things have changed a tad since then!
Looks like a wonderful rom, well done old chap!..too bad I got the flip instead last week and no twrp/roms yet.
Click to expand...
Click to collapse
Hi mate! Yep very long time! Been on Sammy for a few years now ta for the kind words mate and hoping to support flip too. That's If the software is similar (which it will bw)
AFAIK twrp is in the making too
I cannot see any reason why we shouldn't support the flip soon.
Thanks for great work, just remaining to finish the camera fix, once more Big Thanks.
And as normal Knox is broked and warranty void when I root my F3!?
ltth said:
Thanks for great work, just remaining to finish the camera fix, once more Big Thanks.
And as normal Knox is broked and warranty void when I root my F3!?
Click to expand...
Click to collapse
Thanks mate
Yep unfortunately this will break know so Samsung pay won't work. AFAIK secure folder is now from a11 onwards (unless I have mixed that up with something else lol)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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? http://bit.do/unlockg4
About /e//e/ is 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
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?
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed but NOT activated by default (activate them with just a finger tip! That's needed to ensure you only get what you want)
added PhoneSky a patched Google playstore allowing in-app-purchase on 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 issuesKeep 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
Not available (yet) -> OFFICIAL builds (new install or re-install):
https://doc.e.foundation/search?q=LG G4
CUSTOM builds (new install or re-install):
http://leech.binbash.rocks:8008/e-os/a11
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 fix 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
SupportOf 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 LG G Four team (aoleary, steadfasterX, Paul Tully)
and more..
Sources
build manifest
e OS source
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:
logcat GUIDE
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: LIMITED SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have magisk installed currently UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Try to re-produce the issue. If it is gone, its magisk related. otherwise 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 is placed 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 might happen when the following has been solved / implemented (which is NOT the case currently (see known issues):
- selinux = enforcing
- device encryption working
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:
boot Android
once booted : reboot to TWRP/SHRP
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
once in TWRP ensure that "Cache" is mounted in the "Mount" menu (if not mount it by ticking the box)
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
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)"
Click to expand...
Click to collapse
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)' "
Click to expand...
Click to collapse
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 OpenGL instead of skiaGL 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 or "skiagl" it means skiaGL is active.
If for any reason you wanna enforce skiaGL you can do so by
temporary (immediately activated):
Code:
adb root (must be enabled in dev options)
adb shell setprop debug.hwui.renderer skiagl
or make that change persistent:
Code:
boot TWRP
backup system
mount system
adb shell
echo "debug.hwui.renderer=skiagl" >> /system/build.prop
sync
reboot
.-
I uploaded it, good speed, I will continue to try. Thank you
Thanks for this new ROM
I recommend a full cleanup with format
The only issue I have so far is that I can't connect to my Murena.io account, it keeps on loading. Logs attached
Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.
cvmg333 said:
Thanks for this Rom, installed 72 hours ago, feels a bit slower than the same Pie Rom,thats expected, but it is fine, very usable. You do an excellent job with this Rom, feels more fluid and energy efficient than linage pie plus gapps and gms working as it should out of the box, this is the first and only Rom of all, i have tried, in every phone i had since my first android, from 2011 doing that. Wont gonna write nothing about battery usage, or SoT, batteries are the oem LG put in these phones.
Until now the only incovenience is that with dark theme enabled, sometimes, 3 out of 10 times, when i wake the screen its lights wont use the brightness it supposed to use, it wake very dim, i´m still debuging this glitch, pushing the power button to turn it off and then pushing it again bring back to full brightness the screen.
Click to expand...
Click to collapse
The blackout when phone display is off is a well known issue since years with any custom ROM for the g4. We tried to fix that for a long time without any real success.
Interesting note, i did not know about it, thanks for the tip, i will use light theme now onwards then, got another little problem with the microphone, the other person hear me to low, only when i use speakerphone in a whatsapp call, with out the speakerphone activated every thing is working well, have not tried in a normal telephone call yet, i have tried changing microphone volume setting in kernel with ex kernel manager, but no success in that, changing screen colors and saturation works in that app, thank you.
@steadfasterX this could be tried https://github.com/sthomsonpl/devic...mmit/07db7d8be41997765f9a0c60d7e7476b5440545e
I installed this ROM yesterday, and its running fine so far.
Thanks a lot for bringing this gem to ye ole G4.
You really did an excellent job!
Auto rotate not working. H815 UsU'd. Yes - flashed UsU zip.
Edit: Also, when turning on bluetooth, connecting bluetooth headphones then playing a video, bluetooth turns off.
I haven't tested bluetooth on the pie /e/OS or the various LineageOS builds, so it could very well be affecting those too.
Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?
pizza_alarm said:
Hello,
I have unlocked my G4 H815 EU version with USU and installed /e/-OS with Android 11 on it, but afterwards I noticed that I can't make phone calls. I also can't receive phone calls, but the phone sends a message that I have received a phone call. How could this error be fixed?
Click to expand...
Click to collapse
flash 20p bootloader stack and modem
Thanks. Where can I find the correct bootloader and modem files?
pizza_alarm said:
Thanks. Where can I find the correct bootloader and modem files?
Click to expand...
Click to collapse
pls check the OP -> Requirements (bootloader stack), Installation (Modem)