Develop Bugs

[EXPERIMENTAL][AOSP][NRD90U] Unofficial Android 7.0 Nougat build

Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* 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.
*/
Hello guys, this is an unofficial build of AOSP Nougat (with tag android-7.0.0_r6). Kernel is based on CM13's, with some recent commits in kernel/common in AOSP. Sources and patches are available at the end of the post.
Note: this ROM is just for having the first taste of Nougat, and thus missing a lot of key features. I may not be able to update it regularly.
Basic hardware functionality:
Almost everything works, except video hardware encoding, which causes camcorder to fail. HW decoding works though.
Everything should be working since 20160903.
I didn't find more hardware failures, but there can be more.
And remember, the proprietary firmwares and blobs are still in the age of Marshmallow, and a system won't be complete without corresponding firmwares and blobs.
Known bugs:
1. HW disk encryption is likely broken. I reverted some commits to make cryptfs_hw build, but I'm not sure if that works. Do not try it.
2. SELinux is permissive, and init allows service without a SELinux domain to start.
3. GPS may take longer to obtain a position fix. (yes it's working... sorry for the misunderstanding)
4. Only Launcher2 is included. You may install a new one as you like.
5. No LiveDisplay and gestures except DT2W (DT2W can not be turned off via Settings app for now) Color calibration is possible, see FAQ below.
6. Default input method could be broken. Be ready to "pm install your_ime.apk" in adb shell. Fixed in 20160828
7. com.qti.dpmserviceapp may produce continous FC. You can disable it via adb shell ("su -c pm disable com.qti.dpmserviceapp"). Removed in 20160828
8. Rotating screen while playing video can cause the display to "split" Fixed in 20160903
9. Camera service and media codecs all run in the same process, eliminating one of the security enhancements of Android N. May not be fixed until new HAL and blobs are available.
So the security improvements in Nougat are not making much difference in this only-a-taste ROM. If you rely on this, it would be better to wait for official releases.
FAQs:
1. Root / Gapps?
I'm using SuperSU 2.76 stable and OpenGapps 7.0 pico. They work without any issue.
If your contacts / calendars is not syncing, try the following steps:
1. Goto Settings > Apps, tap "Show system" in menu
2. Find "Google Contacts Sync", tap on it, tap "Permissions", turn on everything
3. Go back to Detail screen, clear its data
4. Go back to app list, clear "Contacts Storage"' data
5. Do the same for calendars (2-4)
6. Reboot
Click to expand...
Click to collapse
2. F2FS?
I did not test this myself... But kernel has support already (of cource, it's from CM) so you may have a try. Remember to backup!
EDIT: Some users reported that F2FS partitions are corrupted. If you are using F2FS, maybe you should wait.
Click to expand...
Click to collapse
3. Menu key / App switcher?
Menu key now acts as recents, since I don't think the former is as useful as the latter. And there is no more lag while tapping home button since we don't check for double tap anymore.
Click to expand...
Click to collapse
4. TWRP shows error?
If that's two lines of "log", you can safely ignore it.
If there is something else, please stop and post it here.
If you are using MultiROM, you may modify update-script. Read the first ~8 pages and you will find it.
Reference: I'm using official TWRP 3.0.2 w/o MultiROM This recovery didn't get replaced by stock one...
Click to expand...
Click to collapse
5. File manager (to install APKs)?
http://forum.xda-developers.com/showpost.php?p=68402423&postcount=73
Click to expand...
Click to collapse
6. Disable HW keys, enable soft keys, screen color calibration?
Disable HW keys: echo 0 > /proc/touchpanel/keypad_enable (needs repeat on reboot)
Enable soft keys: echo "qemu.hw.mainkeys=0 >> /system/build.prop (once)
Screen color calibration: echo "32768 31784 27852" > /sys/class/graphics/fb0/rgb (needs repeat on reboot, change the values as you need. This example is 100% R, 97% G, 85% B)
Optionally you can enable color enhancing: echo 1 > /sys/class/graphics/fb0/color_enhance
Click to expand...
Click to collapse
Screenshot spoiler
{
"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"
}
Flashing Guide by @The Dork Knight Rises
In the 3rd post. Direct link: http://forum.xda-developers.com/showpost.php?p=68397804&postcount=3
Video hands-on by @savadam
https://www.youtube.com/watch?v=r54vWk-Azh8
Thanks for all your support!
Download:
20160919: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAYWRKd1owSUNudEU Mirror 2: https://mega.nz/#!fEk1CTyJ!F8rdnqT_oiipP-tHCuzFGFvsQGmUV6LRaD2t81N2WIA
You can still use HALs from 20160906 if you want.
(And if you are posting this somewhere else, please include the HALs in your post)
Older versions:
20160918: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAMWZ4OEx6Unp5bU0 Mirror 2: https://mega.nz/#!rdlkgboI!LQuFDtcppbizC_7Tfww1uWAmhw-lYuxjAlrhg9Z0tuQ
20160910: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAdGVTV3V0ekZaWHM Mirror 2: https://mega.nz/#!XEsTESpR!QDa7he2jdPCeIsbMY1vJAlCZ0RokAKV0IdtyuB0R-yc
20160906: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAWHNFb0xyYlBZM3c Mirror 2: https://mega.nz/#!zBVX1DTZ!S-LnpIEgJqn1r7So6QmEoD_APUqDnp93XbP-Ug__XBk
CAF and original AOSP HALs: https://drive.google.com/open?id=0BwkmhbR5VHpAaGdCQmxDUWgxQlU
Note on the HALs:
AOSP HALs (msm8996 display + msm8974 media) can not record screen, but they "seem" to make the system smoother. (msm8974 display HAL cannot be used because it corrupts the display when rotating screen with video playing)
CAF HALs (both based on vanilla CAF LA.BF.1.1.3_rb1.13) can record screen but "seem" not to be so efficient as AOSP ones.
The HAL included in the ROM are the AOSP variant.
20160903: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpATlN5T29WTS01Qkk Mirror 2: https://mega.nz/#!OcFlTDDK!EYiNpfE-9Pxx2wu4Oto7kO_oevfe0bMkXOTdhP1HDZc
20160831: Mirror 1: https://drive.google.com/open?id=0BwkmhbR5VHpAVE1WR2xYd180MzA Mirror 2: https://mega.nz/#!jE92iSAD!pl0NMU6PPY3UNXE5DTDBKLUd4sFLG6fNTaUUMI0xdzg
20160828: Mirror 1: https://mega.nz/#!XdlXFDBQ!p7E0N64IEkGHn4GBzOZQDTCgR4KdD00O0dRwJlEnvcw Mirror 2: https://drive.google.com/open?id=0BwkmhbR5VHpAczA2T2g0RUZRS3c
20160827: https://drive.google.com/open?id=0BwkmhbR5VHpAUVdWUHNlc0lHZWs
Note: please read "known bugs" section before flashing! Also you can read the guide below.
When updating the ROM, just dirty-flash new build and Gapps (if you use them).
In order to prevent your recovery from being replaced by the stock one, flash SuperSU along with the ROM.
Sources:
Kernel: https://github.com/updateing/android_kernel_oneplus_msm8974/tree/nougat
Device: https://github.com/updateing/android_device_oneplus_bacon/tree/nougat
Build system: https://github.com/updateing/platform_build/tree/custom-kernel
And there are a lot more repos I didn't fork. The changes there as well as local_manifest are here:
20160918+ Check GitHub
20160910 https://drive.google.com/open?id=0BwkmhbR5VHpAcmo1RjhPd0N1c3c
20160906 No new patches except the HALs. For AOSP HALs, check previous patch archive and Sony's guide. For CAF HALs, just cherry-pick "Fix clang build" from CM.
20160903 https://drive.google.com/open?id=0BwkmhbR5VHpAQXFqZEJCT21UNDA
20160831 https://drive.google.com/open?id=0BwkmhbR5VHpASW54QnR4eGFlR1E
20160828 https://drive.google.com/open?id=0BwkmhbR5VHpAOEx2OWNYcE1xU2s
20160827 https://drive.google.com/open?id=0BwkmhbR5VHpALXdkNkptRnBLMkU
Changelog:
20160919
Fixed Fackbook crash by avoiding preloading libboringssl-compat.so (CM camera HAL is the only camera HAL that does not require this)
Updated BT configuration (please test if it has any side effect. Sometimes you need to search twice to find your Bluetooth gadgets.)
Tried to fix network location (added Google's network location provider)
20160918
Reverted to previous "stub" power HAL. May fix lagging and unusual power consumption noticed by some users.
Tried to fix NFC FW download mechanism. May fix non-working NFC for some users.
20160910
Updated to NRD90U (android-7.0.0_r6)
Switched to CM/QCOM power HAL. The original power HAL is more like a placeholder.
Now on Tap can be launched by long-pressing home button
Switchable WebView implementation, thanks to @fards here
Note:
1. If you are experiencing display issues (such as screen flicker with FLV SW decoding), try switching on "Disable HW Overlay" in Development Settings.
2. If you need multi-user feature, remove /system/priv-app/com.qualcomm.location. Otherwise the system will crash. It was accidentally added in this build.
20160906
Switched back to AOSP HALs to increase performance, but screen recording is broken again. You can choose CAF HALs listed above to fix that. Camcorder and HW encoding work with both variants, no need to worry.
Updated media profiles. Front camera knows that it is not capable of 1080p recording.
20160903
Fixed HW encoder and camcorder (they are different issues, though related) (and switched to CM13 media HAL)
Fixed display corruption while rotating screen with video playing (by switching to CM13 display HAL, don't know which lines of code fixed that)
DT2W can be turned off via Settings
Added Reboot option in power menu
20160831
Fixed crash in World Clock page when selecting countries/regions
Fixed hang in Developer Settings when the ROM is installed as secondary
Fixed crash when taking photos with HDR on
Added support for kexec
Added Stk
20160828
Fixed default input method FC
Remove com.qti.dpmservices to prevent FC
Dev: updated build system to finally automate everything
20160827
Initial build
Click to expand...
Click to collapse
Notes on the sources:
1. Build system produces correct boot.img in $OUT, but the boot image in OTA zip still has no DT included. Fixed in 20160828
2. Some fixes are really "dirty" (as I'm not able to find a proper way)...
3. Some JNIs fail to build (lots of C++ symbols no found). You may try linking C++ libs dynamically (c++_static -> c++_shared) to avoid this. See 20160828 patches, packages/inputmethods/LatinIME for example.
4. Some apps require android-8 ndk, but the earliest version in the tree is android-9. A symlink will do (or you can change the Android.mk in app) but I'm not really sure this will not introduce any bug.
5. Android N split mediaserver into multiple processes to improve security, such as cameraserver, mediacodec, etc. But camera blobs and old HALs were not designed like this. They assume they run in the same process, thus a buffer created by blobs are being used everywhere, which will cause illegal memory access under Android N. I reverted lots of patches about this, forcing camera and codec services to run in the mediaserver process as before - security compromised with functionality, again.
Hope you enjoy this.

I am going to try this out, thanks @updateing for your work:good:
If I could find fixes then I would send an pull request.

The All-In-One Post
Oh look at the time...it's flashy time already? XD
Screenshots:
(Layers themes work. Use Substratum app)
Guide to flashing this properly (TWRP v3.0.2-0):
(THIS GUIDE IS MAINLY FOR THE FIRST BUILD 20160827. AS I AM RUNNING IT SMOOTHLY, I DO NOT PLAN TO UPDATE TO 20160828, AS IT HAS SOME MINOR FIXES, ALREADY COVERED IN MY GUIDE.
IF HOWEVER, YOU'RE FLASHING 20160828 OR LATER BUILD, HERE'S WHAT YOU SHOULD DO DIFFERENTLY:
-Flashing Google keyboard is not mandatory, as default input mode has been fixed
-adb steps do not need to be performed as the com.qti.dpmserviceapp has been removed
-You probably shouldn't flash the SystemUI Tuner mod zip, as the SystemUI APK from previous build may not be compatible with new build. If you flash it on 28 build and have SystemUI FCs or missing SystemUI, just reflash ROM, and don't flash the mod.
REST OF THE GUIDE REMAINS THE SAME)
(This guide is for flashing as primary ROM without MultiROM. MultiROM guide by @7u5h4r: http://forum.xda-developers.com/showpost.php?p=68413163&postcount=242)
TL;DR version (that means short version)
http://forum.xda-developers.com/showpost.php?p=68552389&postcount=1172
Download ROM zip from OP and Google Keyboard flashable zip, as well as any of the zips I linked below.
Wipe your device (data, cache, dalvik/ART cache; preferably even system, just to be as "clean" as possible)
(NOTE ABOUT DIRTY FLASHING:
-If you dirty flash this ROM (eg. flashing newer build), you will need to flash GApps again along with the ROM zip as GApps are not preserved
-This ROM actually booted for me even on a dirty flash from an MM custom ROM, and as a result I didn't face a lot of the problems you'd face on clean flash (GApps crashes, continuous qti app FCs, etc)
But a lot of my apps were crashing until I reinstalled them, and in any case, it is not advised to dirty flash when coming from MM)
Flash ROM zip and keyboard zip, optionally any of the following addons (DO NOT FLASH GAPPS YET):
-SuperSU (v2.68+) for root
-Any of the mods I linked below
-Any other mods like Viper4Android etc (AT YOUR OWN RISK)
Boot into the ROM. you'll probably see a lot of crashes, ignore them, and just find a PC for the next step
(Optionally, you could try to enable Developer Options by tapping past the FC dialogs, once you have DevOps enabled, you'll see an option to mute FC notifications till next boot)
Using ADB on your PC, disable the com.qti.dpmserviceapp package by running following commands:
Code:
adb devices
You should see a device in the list of devices connected
Code:
adb shell
pm disable com.qti.dpmserviceapp
If you get error with permissions, you may need root. If your device is rooted:
Code:
su
pm disable com.qti.dpmserviceapp
(SKIP 6, 7 & 8 if you do not need Google services)
Now reboot into recovery and flash a compatible GApps package (USE 7.0 GAPPS ONLY)
Boot into ROM
Go to Settings>Apps
Find Google Play Services, and go to its Permissions. Enable essential permissions. Now Play Services won't keep crashing on you. Also find Google Contact Sync and give it permission to access Contacts.
Go to Settings>Accounts and add your Google account
Profit
Praise DuARTe
Hit Thanks if this helped
Here's some helpful zips for you guys!
My flashable zip to ENABLE Navbar/softkeys (same as the one on the MM thread) https://drive.google.com/open?id=0B2Y1syM7UNuDYVRhM3BTYVA3SXc
Flashable zip to DISABLE HW keys
https://drive.google.com/open?id=0B2Y1syM7UNuDSFZwUHNLQ0RfdXM
Flashable zip to ENABLE HW keys (revert changes made by zip above)
https://drive.google.com/open?id=0B2Y1syM7UNuDalVLVzd0SFdLekk
Flashable stock bootanimation (same as the one in MM thread; since this ROM doesn't really have a bootanimation and uses the basic fallback bootanimation)
https://drive.google.com/open?id=0B2Y1syM7UNuDelFPZVh6dmxSR2c
Flashable zip to ENABLE Hidden SystemUI Tuner Features (thanks to @AL_IRAQI, see his original guide here)
This one was tricky, my first time decompiling an APK. I was getting some crashes at first, but I think this ZIP should work fine (I tested it on a dirty flash, and it works)
https://drive.google.com/open?id=0B2Y1syM7UNuDd0JBV2ViMXl1bnc
Flashable Google Keyboard 5.1
https://drive.google.com/open?id=0B2Y1syM7UNuDbnBmdEtWZlRlNlk
Flashable Nexus Launcher (credits to uploader)
https://www.androidfilehost.com/?fid=24588232905722237
Replace the stock Power Menu with an extended custom power menu (thanks to @nofx161):
See his post
Link to app
Layers themes are supported, use Substratum app (Play Store link) to apply
(ROOT NEEDED)
NOTE: Themes made only for Substratum will not work (properly) as this ROM doesn't support Substratum (that will need patches to ROM source). Only which support RRO/Layers will work without any issues.

Wow! Great work
Subscribed!

thanks for your work dude

Cool, thanks, gonna try asap
Enviado desde mi A0001 mediante Tapatalk

Great! Thank u dev!

updateing said:
2. SELinux is permissive, and init allows service without a SELinux domain to start.
Click to expand...
Click to collapse
Which sepolicy did you use? I am porting to a different device and Im currently trying to fix neverallows which is painful but I think I merged a commit to qcom/sepolicy which allows domain to start (im not very good in sepolicy). Its based off Cyanogenmod qcom/sepolicy repo. If you want to take a look its here android_device_qcom_sepolicy-1 and I had to add one thing to platform_system_sepolicy. I hope we'll be able to fix sepolicy soon.

Awesome.... Downloading already.

Awesome! Has anyone tried If gapps work?

Flashed it. But i get a FC all the time
com.qti.dpmserviceapp has stopped.
I cant do anything..?

Deltastylez said:
Flashed it. But i get a FC all the time
com.qti.dpmserviceapp has stopped.
I cant do anything..?
Click to expand...
Click to collapse
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)

A fellow hamster I see! Nice one.

updateing said:
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
Click to expand...
Click to collapse
I am kind of a newbie to ADB
Could you perhabs tell me how to? step a step?
Thanks!

Deltastylez said:
I am kind of a newbie to ADB
Could you perhabs tell me how to? step a step?
Thanks!
Click to expand...
Click to collapse
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.

updateing said:
Really sorry that I forgot this. You could do "pm disable com.qti.dpmserviceapp" in adb shell (su first if it asks so)
Click to expand...
Click to collapse
updateing said:
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
Click to expand...
Click to collapse
well, getting this error
" Error: java.lang.SecurityException: Shell cannot change component state for com.qti.dpmserviceapp/null to 2 "
Never mind, fixed

updateing said:
You may find a lot of adb tutorials around...
But if there is a mute option in the FC dialog, you can mute it and disable in Settings.
Click to expand...
Click to collapse
i've tried through adb shell but it doesn't work shell cannot change component state for com.qti.dpmserviceapp/null to 2 moreover it is not possible to disable it in settings thank u for your job

anyone!! please any reviews??

Knew it wouldn't be long before the famous Bacon machine got that great taste of nougat :good:

holy crap holy crap
EVERYONE BOARD THE HYPE TRAIN! CHOO CHOO!

[ROM][magisk-based]*** GoogleWiz *** {Pixelize your OnePlus 7T pro}

***
{
"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"
}
Wiz *** Pixelize your OnePlus 7T pro
"Extreme debloat: Go where OnePlus has never gone before"
You thought that OnePlus phones were pretty stock Android? Hmmm .... think again ... there's still lots of stuff on these phones that you actually don't need (or want).
For example, did you know they have an engineering mode? Did you know that they can connect to your phone remotely? Did you know that when the phone starts up it connects to a OnePlus server in the back? Well, I don't want all that ...
In addition, there are even standard things in Android that only 0.01% of the people ever use ... for example ... tracing, android dumps, ... these things are disabled in this ROM.
Then there's bits and pieces of Qualcomm stuff that you actually do not need/want (I don't even know what they do).
This is a ROM in the form of a Magisk (thanks: @topjohnwu) module. That's great (I think). You can install it on top of the normal OnePlus software. If you don't like it or want to revert back to the "standard" OnePlus software, just remove the Magisk module and ... done!
Upfront "warning"
There are a few features which I personally do not use. When you install this module then:
- you will no longer have face unlock
- you will not have VoLTE (I have disabled this because it does not work on my carrier)
Basic requirement
(1) Your OnePlus 7T pro must be ROOTED! Without root, do not read any further as you will not be able to use this ROM. There are other threads in the OnePlus 7T Pro pro forums which explain how to root (so please don't start asking how to do this).
(2) You must also be on the latest OnePlus software: 10.0.7.HD01BA (since I own a EU model of the OnePlus 7T pro, I have ONLY tested this ROM in this device/software). It "may" work on other variants of the device ... but I don't know. I can't answer questions to that either.
(3) You must have access to ADB over USB. If you don't know what this means, stop reading, then this is not for you.
Kernel requirement
This ROM will work with the standard out-of-the-box OnePlus 7T pro kernel. However, I would strongly advice you to flash the "arter97" kernel (see https://forum.xda-developers.com/on...development/arter97-kernel-oneplus-7-t3952578). It's a fantastic kernel and this ROM has some optimizations which go very well with this kernel (don't worry, they will work on the standard kernel as well).
Download?
Interested? Start downloading the magisk module from the link below (but please read further for installation instructions !!!).
https://drive.google.com/file/d/1XpiDKFQiuFuuTBvbKMAsxMH-B9Obi-Gz/view?usp=sharing
(click on the donwload icon upper right of screen)
The link contains always the LATEST version; check the changelog in post #2 below. You can find the file size and md5sum there as well.
Changelog
See post #2 below.
History
I once owned a Galaxy S8. ***GoogleWiz*** was one one the most popular ROMs on that phone. See https://forum.xda-developers.com/ga...t/rom-googlewiz-oreo-extreme-debloat-t3750641. The difference is that I have now converted this to a Magisk module (reason: the "dynamic partitioning scheme" of Android Q makes it really hard to flash in the classical way; as you know even full TWRP functionality does currently not exist for the OnePlus 7T pro.
(Re)Using this work
Other devs, please feel free to (re)use this for your own work ... I am not asking anything from anybody, no donation, no thanks, no beer ... you don't even have to mention that you (re)use this. We are here on XDA to share and learn from eachother. If you unzip the Magisk module, you can see exactly what is inside. But ... there has been quite some work into this. It was not created in 5 minutes. But I do this as a "hobby" ... I have always rooted and customized my Android phones. So hopefully you will enjoy. Source code in post #3 (https://forum.xda-developers.com/showpost.php?p=81887167&postcount=3).
Telegram
No telegram group; I don't have time for that, so do not ask please.
Features
The ROM does NOT contain OnePlus applications! The only OnePlus applications are "Settings" and "Camera".
Nova launcher (https://play.google.com/store/apps/details?id=com.teslacoilsw.launcher)
SwiftKey keyboard (https://play.google.com/store/apps/details?id=com.touchtype.swiftkey)
Google
play services (which can be put into doze mode)
play store (https://play.google.com/store)
photos (used as gallery; but NOT integrated with camera) (https://play.google.com/store/apps/details?id=com.google.android.apps.photos)
dialer (https://play.google.com/store/apps/details?id=com.google.android.dialer) with spam detect and nearby places
contacts (https://play.google.com/store/apps/details?id=com.google.android.contacts)
messaging (https://play.google.com/store/apps/details?id=com.google.android.apps.messaging)
text-to-speech (https://play.google.com/store/apps/details?id=com.google.android.tts)
gmail (https://play.google.com/store/apps/details?id=com.google.android.gm)
keep (https://play.google.com/store/apps/details?id=com.google.android.keep)
drive (https://play.google.com/store/apps/details?id=com.google.android.apps.docs)
maps (https://play.google.com/store/apps/details?id=com.google.android.apps.maps)
chrome (https://play.google.com/store/apps/details?id=com.android.chrome)
clock (with Spotify integration) (https://play.google.com/store/apps/details?id=com.google.android.deskclock)
calendar (https://play.google.com/store/apps/details?id=com.google.android.calendar)
calculator (https://play.google.com/store/apps/details?id=com.google.android.calculator)
search app integrated with Nova search bar (https://www.google.com/search/about/)
assistant (https://www.apkmirror.com/apk/google-inc/google-assistant/)
tasks (https://play.google.com/store/apps/details?id=com.google.android.apps.tasks)
translate (https://play.google.com/store/apps/details?id=com.google.android.apps.translate)
earth (https://play.google.com/store/apps/details?id=com.google.earth)
fit (https://play.google.com/store/apps/details?id=com.google.android.apps.fitness)
now cards integrated with Nova launcher (see https://forum.xda-developers.com/showpost.php?p=75591011&postcount=4)
lens (https://play.google.com/store/apps/details?id=com.google.ar.lens)
news (https://play.google.com/store/apps/details?id=com.google.android.apps.magazines)
chromecast (aka Google home) (https://play.google.com/store/apps/details?id=com.google.android.apps.chromecast.app)
youtube (https://play.google.com/store/apps/details?id=com.google.android.youtube)
markup (https://9to5google.com/2018/03/07/android-p-dp1-markup-screenshot-editor/)
measure (https://play.google.com/store/apps/details?id=com.google.tango.measure)
weather (just type "weather" in the google search app; it will offer you to get an icon on the desktop)
android auto (Google's car mode) (https://www.android.com/auto/)
snapseed photo editor (https://play.google.com/store/apps/details?id=com.niksoftware.snapseed)
docs (https://play.google.com/store/apps/details?id=com.google.android.apps.docs.editors.docs)
slides (https://play.google.com/store/apps/details?id=com.google.android.apps.docs.editors.slides)
spreadsheets (https://play.google.com/store/apps/details?id=com.google.android.apps.docs.editors.sheets)
streetview (https://play.google.com/store/apps/details?id=com.google.android.street)
pixel icons in statusbar, quick settings tiles
pixel ringtones, notifications, UI sounds
camera2 API enabled (but I don't think this actuall does something useful)
- OnePlus bloatware removed (dialer, phone, messages, calculator, notes, gallery, zen, ...) + lots of background APKs
- OnePlus background processes (which send data to OnePlus) are disabled
- ad-free through large "hosts" file (works both for apps and web pages)
- lots of optimizations, really, *lots* of them (too many to list)
- support for init.d / services.d (see posts below if you want to use this)
- passes SafetyNet (I am using Google Pay and some Belgian NFC pay apps)
- "clean" and as close as possible to a Pixel phone
- optimized network/wifi config
- optimized touchboost (slightly faster application startup)
- optimized kernel scheduling settings
- disabled all kernel debugging/tracing
- frequency scaling throughout full CPU frequency ranges (saves battery and better performance when needed)
- disables swapping / zram (who needs this with 8GB of RAM)?
- bash shell in "su" mode (when using "adb shell")
- latest busybox (by @osm0sis)
- 1x7 icon row for quick settings, 5 icons per row when you swipe down the full quick settings
- added .xml permission files to enable Pixel exclusive features (e.g. Google dialer)
- optimized .proto, .conf, .json, .ini, .sql files in the system
- improved thumbnail quality
- dalvik VM optimized settings (for "speed")
- auto clean junk files at boot time
- optimized audio settings
- optimized camera settings (e.g. supernight mode; but personally I don't see a difference in the night pictures)
- disabled "factory" and "engineering" mode
- reduced wifi scan interval
- auto sqlite optimization at boot time (only runs every 3 days)
- support for both 2.4GHz and 5GHz wifi bonding
- speaker and headset volume boost
Installation (really IMPORTANT to read)
You must start from the 10.0.7 "standard" OnePlus 7T pro software. I suggest you do a clean install from factory reset. Strictly speaking a full reset is not needed (so you could just go and install the Magisk module on your phone) but there may be certain side effects in that case. Anyway, assuming you will do a full reset, follow the instructions below:
Go to Settings > System > Reset options > Erase all data (factory reset)
Proceed through the normal setup sequence: accept the terms and conditions of OnePlus, skip the User Experience Program, skip the System Stability Program, skip the Push Notifications, skip the Built-in App Updates, connect to your wifi network, do NOT copy apps and data, enter your google account email of phone number, enter your google password, do 2 factor authentication (if you have enabled this on your google account), if a dialog pops up with "Add your current account", do that, disable Backup to Google Drive, disable Use Location, disable Send Usage and Diagnostic Data, type NEXT to use fingerprint, enter PIN code (twice), set up 1 or more fingerprints, you see a message about Google Assistant, press NEXT, you see a message about Google Pay, press Got It, skip the Anything Else screen, choose your screen calibration, choose font (slight preference for Roboto, better compatibility with Google apps), choose Navigation bar or Gestures, press START on the Setup Complete screen, you are now in the OnePlus launcher, allow carrier location service, swipe down the notification which says: Android Setup, click on Finish Setup, copy your data if you want that, press START, system will now check for updates, let it complete, copy your data from cloud or iphone, continue until you are back in the OnePlus launcher, go to Settings > About phone, tap build number 7 times to activate developer options (if you don't know what this is, search XDA)., enter your PIN, press back arrow, go to Settings > System > Developer options, enable "Advanced reboot", disable "Automatic system updates", enable "USB debugging mode", connect your phone to a PC, a dialog will pop up to Allow USB debugging (tick "Always allow from this computer") and press ALLOW, install the LATEST Magisk Manager APK (see https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445), push the Magisk Manager APK to your phone, e.g.
Code:
> adb push MagiskManager-v7.5.1.apk /sdcard/
open the app drawer, open the app called "Files", on the upper right, click the 3 dots, then "Show internal storage", on the upper left, click the 3 lines, select "OnePlus 7T Pro", scroll down and click on MagiskManager-v7.5.1.apk; install the app, open Magisk Manager, it will say your phone requires Additional Setup, click OK ... your phone will reboot 5 seconds later, open Play Store, select My Apps and Games, it will say that a number of updates are pending, press "Update all", exit Play Store, reopen it ... it might still say that there are pending updates, do them, activate NETFLIX ... do it NOW ... (if you first install the Magisk module, you will no longer be able to activate Netflix), push the downloaded magisk module to your phone
Code:
> adb push mm-googlewiz.zip /sdcard/
open the Magisk Manager app, press the 3 lines (top left of screen), press Modules, press + button (and allow Magisk Manager to access media), press the 3 lines top left in the file manager, select OnePlus 7T pro, scroll down and click on the mm-googlewiz.zip file, Magisk Manager will now install the module ... you will see some text output on the screen ... wait until installation is done (it will take a minute or so), press the yellow Reboot button which appears (your phone will reboot), unlock the lock screen by entering your PIN, let the ROM settle 30 secs ... it will say "Restarting" and reboot once more your phone, unlock the lock screen by entering your PIN, open the drawer, open the Settings app (will be in black mode [my personal liking] ... you can change later back to white), press Apps & Notifications, select Default Apps, press home app and select Nova Launcher, open Settings, press Apps & Notifications, select Default Apps => select "Phone app" and then select "Phone" (this is the Google phone app)
Now you will have NOVA launcher as default ... which you can customize to your liking (much better than OnePlus launcher).
Open Drawer, use the app Nova-settings to customize.
Open Drawer, click on "Nova Google Companion" => this will enable left swipe Google Now behavior in Nova launcher
Done! .... now you can further customize your phone in any way you want ...
Bootloop?
If - after installation - you should get into a bootloop then check the following thread (https://forum.xda-developers.com/7t-pro/how-to/guide-remove-magisk-modules-twrp-t3995677) for how to remove the Magisk module.
Disclaimer
I will try to support questions / feedback. I will not answer questions such as "Can you please add OnePlus feature X,Y,Z" ... I have deliberately removed them. If you want OnePlus apps, use the standard OnePlus software.. The usual applies: no warranty, installing this void warranty, install at your own risk, ... I am not responsible for soft or hard bricks. Your phone must be rooted (again).
Help ... I really don't like it ... I want to remove it ...
Stay calm. Open Magisk Manager, press the 3 lines top left on screen, press Modules, then press the trash icon next to "googlewiz" module and reboot ... you will have the standard OnePlus software again.
Removing Google apps
You can remove Google apps from the ROM as follows. Go to the following URL: https://raw.githubusercontent.com/foobar66/googlewiz/master/googlewiz.config click right and then "Save as". Save the file using "googlewiz.config" as file name. Note that this file is a LINUX plan vanilla text file. The file will look as follows:
Code:
keep=1
lens=1
news=1
assistant=1
sheets=1
snapseed=1
street=1
home=1
measure=1
fit=1
tasks=1
earth=1
slides=1
clock=1
calculator=1
docs=1
Edit the file and put "xyz=0" for Google apps that you do NOT want to install. Above is respectively for Google {Keep, Lens, News, Assistant, Sheets, Snapseed, Streetview, Home, Measure, Fit, Tasks, Earth, Slides, Clock, Calculator, Docs}. Put the file onto your sdcard, e.g. via adb ("adb push googlewiz.config /sdcard/"). Download today's version ([version: 2020-03-30 18:28]) of the module (or later). Re-install the module via Magisk manager and reboot. You will see debug output on the screen during module installation which Google apps are getting removed.
Credits
@topjohnwu, @osm0sis, @Zackptg5, @DeadmanxXD, @arter97

Changelog
[version: 2020-02-28 17:28]
Initial version
File size: 877404687, MD5: 038c3285a68e2be5421dc1a3eb2d041e
[version: 2020-03-01 08:34]
- fix some permissions in system/xbin files
- updated com.google.android.apps.docs.editors.sheets
- updated com.google.android.apps.turbo
File size: 881052548, MD5: 7fed9105aaba0bb1def6ca145527ea4d
[version: 2020-03-01 10:54]
- use original APN files
- update com.google.android.apps.docs.editors.sheets
File size: 881149942, MD5: 93d54a90fef970d7250723895b7c6cec
[version: 2020-03-11 18:46]
- small bug fixes
- upgraded a number of Google apps to latest version
File size: 898125981, MD5: 4b82cff7e572da635f6ca252ec54f58f
[version: 2020-03-30 18:28]
- updates to Google apps
- supports configuration file /sdcard/googlewiz.config
File size: 898132639, MD5: 1bcfa989673f3e59a378243306dc3d94
[2020-04-30 07:09]
- updated to Google apps
- update to latest OnePlus camera
- added Android Auto phone screen
File size: 963547129, MD5: 67a5057d0e882ec38b7e5101c8d0bbe7

How was this Magisk module created?
Actually the Magisk module is generated by a bash script (I use linux) starting from the original OnePlus software zips.
The script is attached to this thread. Download the zip file attached and then rename the file by removing the ".zip" extention). You will have a plain Linux bash shell script file. No secrets. Sharing all in the open (which I believe should be the spirit of XDA).
Reuse as you like ...
Source code
Feel free to (re)use ... no secrets, no hidden stuff, no need to thanks, no need to donate ...
https://github.com/foobar66/googlewiz
My only request ... if you make an interesting improvement, please share with the community so we all can benefit from it!

Misc stuff
a) How do you debloat? Well ... there are different ways.
- some init.rc files are not needed, the Magisk module bind-mounts "empty" files over the original ones so they do not run
- OnePlus APKs are "debloated" by bind-mounting an "empty" APK over them; Android will no longer recognize them as valid applications
- some background processes are not needed, they are "debloated" by bind-mounting empty files over the executables in /system/bin
Unzip the Magisk module, look at the file called "service.sh" and you will understand how this is done (partly).
Check out the previous post where you can find the bash shell script which I use to "generate" the Magisk module.
b) Debug info
To see what the module has done during boot, there is a dedicated log file /data/googlewiz/googlewiz.log, do:
Code:
> adb shell
$ su
# cat /data/googlewiz/googlewiz.log
c) Logging of init.d and services.d scripts. Init.d scripts run immediately together with Android boot. services.d scripts run once /sdcard is mounted. To see the debug output do:
Code:
> adb shell
$ su
# cat /data/LS00*
# cat /data/LS99*
d) You talk about "bloatware" ... what is actually "removed"?
Code:
./system/vendor/app/com.qualcomm.qti.improvetouch.service/com.qualcomm.qti.improvetouch.service.apk
./system/vendor/app/PowerOffAlarm/PowerOffAlarm.apk
./system/vendor/app/CACertService/CACertService.apk
./system/vendor/app/CneApp/CneApp.apk
./system/vendor/app/IWlanService/IWlanService.apk
./system/vendor/app/pasrservice/pasrservice.apk
./system/product/app/remotesimlockservice/remotesimlockservice.apk
./system/product/app/SimSettings/SimSettings.apk
./system/product/app/Duo/Duo.apk
./system/product/app/QdcmFF/QdcmFF.apk
./system/product/app/OPCarrierLocation/OPCarrierLocation.apk
./system/product/app/datastatusnotification/datastatusnotification.apk
./system/product/app/embms/embms.apk
./system/product/app/GoogleLocationHistory/GoogleLocationHistory.apk
./system/product/app/uceShimService/uceShimService.apk
./system/product/app/Music2/Music2.apk
./system/product/app/imssettings/imssettings.apk
./system/product/app/PerformanceMode/PerformanceMode.apk
./system/product/app/uimgbaservice/uimgbaservice.apk
./system/product/app/TTS/TTS.apk
./system/product/app/talkback/talkback.apk
./system/product/app/Videos/Videos.apk
./system/product/app/uimlpaservice/uimlpaservice.apk
./system/product/app/DynamicDDSService/DynamicDDSService.apk
./system/product/app/uimremoteclient/uimremoteclient.apk
./system/product/app/com.qualcomm.qti.services.secureui/com.qualcomm.qti.services.secureui.apk
./system/product/app/LatinImeGoogle/LatinImeGoogle.apk
./system/product/app/DeviceInfo/DeviceInfo.apk
./system/product/app/CallFeaturesSetting/CallFeaturesSetting.apk
./system/product/app/TmoEngMode/TmoEngMode.apk
./system/product/app/ConfURIDialer/ConfURIDialer.apk
./system/product/app/uimremoteserver/uimremoteserver.apk
./system/product/app/colorservice/colorservice.apk
./system/product/app/remoteSimLockAuthentication/remoteSimLockAuthentication.apk
./system/product/priv-app/GoogleFeedback/GoogleFeedback.apk
./system/product/priv-app/StorageManager/StorageManager.apk
./system/product/priv-app/GoogleRestore/GoogleRestore.apk
./system/product/priv-app/CarrierConfig/CarrierConfig.apk
./system/product/priv-app/OPAppLocker/OPAppLocker.apk
./system/product/priv-app/GooglePartnerSetup/GooglePartnerSetup.apk
./system/product/priv-app/daxService/daxService.apk
./system/product/priv-app/dpmserviceapp/dpmserviceapp.apk
./system/product/priv-app/seccamservice/seccamservice.apk
./system/product/priv-app/QAS_DVC_MSP/QAS_DVC_MSP.apk
./system/product/priv-app/WallpaperCropper/WallpaperCropper.apk
./system/product/priv-app/AndroidAutoStub/AndroidAutoStub.apk
./system/product/priv-app/ims/ims.apk
./system/product/priv-app/ConfigUpdater/ConfigUpdater.apk
./system/app/OPAppUpgrader/OPAppUpgrader.apk
./system/app/OPLiveWallpaper/OPLiveWallpaper.apk
./system/app/OPBugReportLite/OPBugReportLite.apk
./system/app/OPFilemanager/OPFilemanager.apk
./system/app/DeskClock/DeskClock.apk
./system/app/BuiltInPrintService/BuiltInPrintService.apk
./system/app/NVBackupUI/NVBackupUI.apk
./system/app/GooglePrintRecommendationService/GooglePrintRecommendationService.apk
./system/app/OPBreathMode/OPBreathMode.apk
./system/app/OPSoundTuner/OPSoundTuner.apk
./system/app/SimAppDialog/SimAppDialog.apk
./system/app/WapiCertManage/WapiCertManage.apk
./system/app/EngSpecialTest/EngSpecialTest.apk
./system/app/Backup/Backup.apk
./system/app/Traceur/Traceur.apk
./system/app/PacProcessor/PacProcessor.apk
./system/app/CarrierDefaultApp/CarrierDefaultApp.apk
./system/app/OPScreenRecord/OPScreenRecord.apk
./system/app/CompanionDeviceManager/CompanionDeviceManager.apk
./system/app/OPMmsLocationFramework/OPMmsLocationFramework.apk
./system/app/SmscPlugger/SmscPlugger.apk
./system/app/OPGamingSpace/OPGamingSpace.apk
./system/app/OPBackup/OPBackup.apk
./system/app/BasicDreams/BasicDreams.apk
./system/app/OemAutoTestServer/OemAutoTestServer.apk
./system/app/ARCore_stub/ARCore_stub.apk
./system/app/EngineeringMode/EngineeringMode.apk
./system/app/SoterService/SoterService.apk
./system/app/OPIntelliService/OPIntelliService.apk
./system/app/PartnerBookmarksProvider/PartnerBookmarksProvider.apk
./system/app/OPGeoIpTime/OPGeoIpTime.apk
./system/app/WAPPushManager/WAPPushManager.apk
./system/app/oem_tcma/oem_tcma.apk
./system/app/SensorTestTool/SensorTestTool.apk
./system/app/WifiRfTestApk/WifiRfTestApk.apk
./system/app/BackupRestoreRemoteService/BackupRestoreRemoteService.apk
./system/app/SdCardService/SdCardService.apk
./system/app/BookmarkProvider/BookmarkProvider.apk
./system/app/PhotosOnline/PhotosOnline.apk
./system/app/OPPush/OPPush.apk
./system/app/QColor/QColor.apk
./system/app/Calculator/Calculator.apk
./system/app/AntHalService/AntHalService.apk
./system/app/WallpaperBackup/WallpaperBackup.apk
./system/app/CtsShimPrebuilt/CtsShimPrebuilt.apk
./system/app/OEMLogKit/OEMLogKit.apk
./system/app/OPCommonLogTool/OPCommonLogTool.apk
./system/app/PlayAutoInstallConfig/PlayAutoInstallConfig.apk
./system/app/LiveWallpapersPicker/LiveWallpapersPicker.apk
./system/app/BluetoothMidiService/BluetoothMidiService.apk
./system/app/Rftoolkit/Rftoolkit.apk
./system/app/EasterEgg_O2/EasterEgg_O2.apk
./system/app/HTMLViewer/HTMLViewer.apk
./system/app/OPWallpaperResources/OPWallpaperResources.apk
./system/app/Netflix_Stub/Netflix_Stub.apk
./system/app/BTtestmode/BTtestmode.apk
./system/app/OPTelephonyDiagnoseManager/OPTelephonyDiagnoseManager.apk
./system/app/OPSesAuthentication/OPSesAuthentication.apk
./system/app/LogKitSdService/LogKitSdService.apk
./system/app/Netflix_Activation/Netflix_Activation.apk
./system/app/NFCTestMode/NFCTestMode.apk
./system/priv-app/Houston/Houston.apk
./system/priv-app/OPMms/OPMms.apk
./system/priv-app/InputDevices/InputDevices.apk
./system/priv-app/ProxyHandler/ProxyHandler.apk
./system/priv-app/DynamicSystemInstallationService/DynamicSystemInstallationService.apk
./system/priv-app/OPAppCategoryProvider/OPAppCategoryProvider.apk
./system/priv-app/OPCellBroadcastReceiver/OPCellBroadcastReceiver.apk
./system/priv-app/OPFaceUnlock/OPFaceUnlock.apk
./system/priv-app/LocalTransport/LocalTransport.apk
./system/priv-app/Contacts/Contacts.apk
./system/priv-app/HotwordEnrollmentOKGoogleWCD9340/HotwordEnrollmentOKGoogleWCD9340.apk
./system/priv-app/ONS/ONS.apk
./system/priv-app/ManagedProvisioning/ManagedProvisioning.apk
./system/priv-app/TagGoogle/TagGoogle.apk
./system/priv-app/RcsSDK/RcsSDK.apk
./system/priv-app/CallLogBackup/CallLogBackup.apk
./system/priv-app/OnePlusGallery/OnePlusGallery.apk
./system/priv-app/OPDeviceManager/OPDeviceManager.apk
./system/priv-app/WfdService/WfdService.apk
./system/priv-app/OPDeviceManagerProvider/OPDeviceManagerProvider.apk
./system/priv-app/CtsShimPrivPrebuilt/CtsShimPrivPrebuilt.apk
./system/priv-app/IFAAService/IFAAService.apk
./system/priv-app/SharedStorageBackup/SharedStorageBackup.apk
./system/priv-app/HotwordEnrollmentXGoogleWCD9340/HotwordEnrollmentXGoogleWCD9340.apk
./system/priv-app/MmsService/MmsService.apk
./system/priv-app/EmergencyInfo/EmergencyInfo.apk
./system/priv-app/BackupRestoreConfirmation/BackupRestoreConfirmation.apk
./system/priv-app/Dialer/Dialer.apk
./system/priv-app/OPSimContacts/OPSimContacts.apk
d) Which /etc/init scripts are disabled?
Code:
system/etc/init/tombstoned.rc
system/etc/init/perfetto.rc
system/etc/init/atrace.rc
system/etc/init/bluetooth-events.rc
system/etc/init/[email protected]
system/etc/init/perfservice.rc
system/etc/init/heapprofd.rc
system/etc/init/dumpstate.rc
system/etc/init/sarahd.rc
system/etc/init/incidentd.rc
system/etc/init/traceur.rc
system/etc/init/iorapd.rc
system/etc/init/bootstat.rc
system/etc/init/mdnsd.rc
system/etc/init/uncrypt.rc
system/etc/init/engineermode.rc
system/etc/init/recovery-persist.rc
system/etc/init/caffed.rc
system/etc/init/update_verifier.rc
system/etc/init/rss_hwm_reset.rc
system/etc/init/wfdservice.rc
system/etc/init/update_engine.rc
system/etc/init/recovery-refresh.rc
system/etc/init/flags_health_check.rc
system/etc/init/statsd.rc
e) If you want to have full "black", use Substratum (https://play.google.com/store/apps/details?id=projekt.substratum) and the Swift Black theme (https://play.google.com/store/apps/details?id=com.brit.swiftblack.layers). That will allow you to mod all the Google apps (and others) into full black mode.
f) "adb logcat" does not seem to move ... correct, to re-enable it do:
Code:
> adb shell
$ su
# setprop log.tag I

i use face unlock...

yenkoPR said:
i use face unlock...
Click to expand...
Click to collapse
Good for you, stick with OnePlus standard software.

Nice one might give this a blast later thanks op?

Ok what have I done wrong lol ?

jaythenut said:
Ok what have I done wrong lol ?
Click to expand...
Click to collapse
You downloaded from: https://mega.nz/#!2BZSiCwR!A4VQ6ZhSr...Sd_8F5W8Njb5Sg
I downloaded and it installs fine for me (just to be sure I was not using a local copy) ... it installs fine for me.
Check the md5 sum if you know how to do that: 3fb9c987cbe94874471c7c699e65d8a1

foobar66 said:
You downloaded from: https://mega.nz/#!2BZSiCwR!A4VQ6ZhSr...Sd_8F5W8Njb5Sg
I downloaded and it installs fine for me (just to be sure I was not using a local copy) ... it installs fine for me.
Check the md5 sum if you know how to do that: 3fb9c987cbe94874471c7c699e65d8a1
Click to expand...
Click to collapse
Asking for decryption key ?

jaythenut said:
Asking for decryption key
Click to expand...
Click to collapse
Weird ... that is the first time I see mega doing this ...
I will upload to a different cloud storage ... please wait a few mins ...
Edit: uploading to my Google drive ... will take 30 mins ...
Edit: OK ... file is uploaded to Google drive, please use following link:
https://drive.google.com/file/d/1XpiDKFQiuFuuTBvbKMAsxMH-B9Obi-Gz/view?usp=sharing
(click on the donwload icon upper right of screen)
File size: 877404687, MD5: 038c3285a68e2be5421dc1a3eb2d041e
I will update OP as well.

Can I 'dirty install' over the latest global stock ROM (already rooted with Magisk)?
Is the stock call recorder activated on this ROM?
Also, any possibility of working V4A being bundled in with this ROM? (I had no luck via the adb method).
Many thanks.

elmor0 said:
Can I 'dirty install' over the latest global stock ROM (already rooted with Magisk)?
Click to expand...
Click to collapse
Is the stock call recorder activated on this ROM?
Also, any possibility of working V4A being bundled in with this ROM? (I had no luck via the adb method).
Many thanks.[/QUOTE]
Dirty install should be possible.
ROM uses the Google dialer, so no call recording for now.
V4A ... never tried it so far, I would need to investigate ... try to find a Magisk module for it (not sure if that exists).

Done a dirty flash all seems to be working fine so far ?

Hi, thx for your work. Sadly for me its not working. Going to endless boot. Followed every Step. Sadly I didnt realize that I have Netflix installed wich was not Active and now even after removing the Modules it Says not Compatible with my Device....My Vault... Is there a Workaround for this?
Iam on Hd 1.0.0.7 AB
Edit: got it fixed with Netflix but even after full reset Iam not able to boot this Module

iceraum said:
Hi, thx for your work. Sadly for me its not working. Going to endless boot. Followed every Step. Sadly I didnt realize that I have Netflix installed wich was not Active and now even after removing the Modules it Says not Compatible with my Device....My Vault... Is there a Workaround for this?
Iam on Hd 1.0.0.7 AB
Edit: got it fixed with Netflix but even after full reset Iam not able to boot this Module
Click to expand...
Click to collapse
Did you have any other Magiks modules active when you tried to install this one?

foobar66 said:
Did you have any other Magiks modules active when you tried to install this one?
Click to expand...
Click to collapse
No. Just Clean new Install after Factory reset.

can i use this rom for op7p ?
and one question. hows swipe to home animation doing here? i've tried nova launcher on stock rom but swipe to home doesnt work properly and i the app icon doesn't collapse nicely

Dark Fear said:
can i use this rom for op7p ?
and one question. hows swipe to home animation doing here? i've tried nova launcher on stock rom but swipe to home doesnt work properly and i the app icon doesn't collapse nicely
Click to expand...
Click to collapse
I don't know it if will work for op7p ... try ...
Swipe to home works fine for me on OnePlus 7T pro

iceraum said:
No. Just Clean new Install after Factory reset.
Click to expand...
Click to collapse
Which country are you in? Just realize that I might have copied the wrong APN file ... (but not sure this is why it does not work in your case).
I am uploading a new version with the original APN files ... please wait a bit.
Edit: new version available (use original download link).

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

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

[CLOSED][ROM] [UNOFFICIAL] [PhhGSI 12][MicroG] for OnePlus Nord N10

Treble ROM based on Phh Treble 12 with MicroG, signature spoofing, Feb 05 security patch and most FOSS apps.
Even it's treble rom it builds for Nord 10 5G, some stuff I removed, not sure about other models.
After some people ask me to put more stuff in my personal build I made more fat ROM to share here.
Be aware still very slim ROM!!!
Tested on model BE86AA 11.02 and 11.03 vendors.
Inside:
AntennaPod -podcast manager/player
SoftUI Calculator
Etar -calendar
EteSync - encrypted sync contacts,calendar and tasks
Fdroid with extra repos (microg and unoficial F-Droid)
Latest MicroG and location backends:
NominatimNlpBackend
MozillaNlpBackend
DejaVuLocationService
K9Mail -email client
KeePassDX - password Manager
Lawnchair12 - launcher
SmpleGalleryPro -Gallery
MiXplorer - File Manager. Clean chache and storage in case of problem at beggining.
Foss Browser - Browser
MupdfViewer - Pdf Viewer
Music Player Go - Music Player
NewPipe - YouTube replacement
NextCloud - Google Drive alt
Notally - Notepad
OAndBackup - Backup utility
OpenCamera - Camera
OpenTasks
Photok - Encrypted Photo Safe for Android
RethinkDns - Firewall+DNS+Ad Blocker
QKSMS - messenger
Signal - messaging/chat/calls/voip calls
SimpleReboot - reboot w/o buttons
WaveUp - Gravity Screen alternative
Weather - Geometric Weather
Bromite-Webview
What Works:
For me all that I and my wife needed. My wife on Dec rom, won't change anything. Me on latest rom with less stuff..
Source
Release AOSP 12.0 v402 · phhusson/treble_experimentations
More February security patch level (previous one had only some patches, not all) Available as OTA from v401 in Treble Settings => Updater
github.com
Requerements:
Unlocked bootloader, Android 11, adb installed, some knowledge
Allready rooted/phh su
Installation
There is two versions rw and ro.
Download what you need
Unpack
Inside you find:
All related img files
flash.bat - Windows
flash.sh - Linux
install.txt - terminal and manual instruction
mi folder - some themes for MiXplorer
Backup all your data because it would be deleted!!!
I'm not responsible for any loss or damage!!!
When inside folder start from terminal/command prompt ./flash.bat or ./flash.sh
Wait untill done ~ 5 min
Downloads
RW
RO​Some tips:
For navigation I use Magic Earth, but GMaps works too.
My banks and airline apps working you have to test your stuff.
Aurora Store should work if you need some stuff from Goole Play install it from FDroid and try.
Don't forget to give some permissions in MicroG and enable location backends.
90FPS
90 FPS can be enabled in Settings/Phh Treble Settings/Misc Features/Forse FPS
or in Settings/Display/Smooth Display with would auto adjust fps
or Settings/Dev Options/Force Pick refresh rate and to be sure Show refresh rate
MiXplorer
If MiXplorer wan't works right from start just clear cache and storage Setting/Apps/MiXporer/Storage & Cache
To import extra skins for MiXplorer copy files that I provided to storage, open MiXplorer navigate to files, short click on file and import to apply
3.5 jack
If got problems with sound enable Alternative audio policy in Setting/Phh Treble Settings/Qualicomm Features
Other
There is 2 launchers -Stock and Lawnchair12. Free to remove any but keep stock if you wanna Recent App view.
Any apps from rw version can be removed.
If for some reason rom won't boot don't panic and try to hard reboot (hold power button)
Enjoy!

r/w link not working but i got it!
you just did a typo

PopCaps1996 said:
r/w link not working but i got it!
you just did a typo
Click to expand...
Click to collapse
Don't use link inside install.txt it old.

gives me this error
{
"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"
}

fersabi said:
gives me this error
View attachment 5543415
Click to expand...
Click to collapse
You not in fastboot mode. After reboot in bootloader you do fastboot reboot fastboot before flash.
Check install.txt file for manual order.

fersabi said:
gives me this error
View attachment 5543415
Click to expand...
Click to collapse
you need fastbootd driver
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com

Updated - MusicPlayer, KeepassDX, StinglePhotos,Signal
Fix problem with ImagePipe, replaced LeafPics with SimpleGallerPro
Added Photok as secure safe media on local drive.,QR Barcode.OpenBoard

This Gsi is good but not great without of Auto Brightness, is a kind of killer.
There must be some requirments regarding this Gsi:
Auto Brightness
Live Display with Picture adjustment
Dirac Audio Tuner
without pre rooted
must include Stock Camera
with Oneplus Stock Dialer,contact and messaging apps
With google play services and support

Hello.
Thanks for all the work and time it's wonderful.
I have a couple problems I have been reaching and unable to fix them.
My phone is a OPO nord n10 5g unlocked. I had no problem installing the ROM. Since day one my 5g will not work only 3g on the T-Mobile network. I have fixed this problem in the past with not much problem, been weeks and still no fix. Every time I try to change the APN and reboot the phone switches back the APN she was set to during the setup and still on super slow 3g.
Do you know the T-Mobile 5g APN for the Tampa FL area I don't thinkit makes a difference.
2. Since the install of your ROM the when I open most apps microG like magic earth and other apps I get a microG core error and if I type to the side the app king of works guidance kept the vocals going but the visual was frozen. Any way fix this maybe update microG. I also have Vanced YouTube instaled with microG not sure if this will cause a problem.
Thasnks in advance.
Tony

tsman said:
Hello.
Thanks for all the work and time it's wonderful.
I have a couple problems I have been reaching and unable to fix them.
My phone is a OPO nord n10 5g unlocked. I had no problem installing the ROM. Since day one my 5g will not work only 3g on the T-Mobile network. I have fixed this problem in the past with not much problem, been weeks and still no fix. Every time I try to change the APN and reboot the phone switches back the APN she was set to during the setup and still on super slow 3g.
Do you know the T-Mobile 5g APN for the Tampa FL area I don't thinkit makes a difference.
2. Since the install of your ROM the when I open most apps microG like magic earth and other apps I get a microG core error and if I type to the side the app king of works guidance kept the vocals going but the visual was frozen. Any way fix this maybe update microG. I also have Vanced YouTube instaled with microG not sure if this will cause a problem.
Thasnks in advance.
Tony
Click to expand...
Click to collapse
You need update microg. Drop what version you have in private message and I give you link to different microg. For T-Mobile if I recall right they have some apps installed on stock that control apn. don't have T-Mobile version to look at it. Also check if there is imssettings apk.It shoud be in product I guess. If not try to install it.

LOL
Oops
Tony

@boom15
can you rebuild the gsi with a13
GitHub - TrebleDroid/treble_experimentations: Scripts to automatically build/CI/Release TrebleDroid GSI
Scripts to automatically build/CI/Release TrebleDroid GSI - GitHub - TrebleDroid/treble_experimentations: Scripts to automatically build/CI/Release TrebleDroid GSI
github.com

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

{
"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 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​
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
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 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)