Database Develop

[OFFICIAL] [WEEKLIES] Lineage OS 15.1

{
"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"
}
Moto Z2 Force
Code:
- Your warrenty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the official Lineage OS thread for the Motorola Moto Z2 Force, codename nash.
We support both the Sprint, International, and T-Mobile variants, as their bootloaders are unlockable, while we can 't support the Verizon and AT&T variants, as their bootloaders are permanently locked.
How to install:
Necessary Base Firmware: 8.0.0 (OCSX27.1.2, May 2018) (for TMO, or equivalent security patches for other variants)
Boot the newest TWRP .img from the Official TWRP Project Site.
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest weekly
(Optionally) You can flash the newest TWRP Installer also found at the Official TWRP Project Site if you wish to maintain TWRP, though the pre-installed Lineage Recovery instance will do everything you need it to in most cases. We don't recommend or support the use of the TWRP installer, as it is overwritten on every update (will need ot be re-installed every update), and has no addon.d-v2 persistence.
Click "Reboot, then choose "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - MindTheGApps arm64 are recommended, OpenGApps are compatible with A/B as of 09102018, but I still only reccoemend and support MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Known Problems:
Audio Mods don't work (this includes headphone jacks on mods) -- We can't fix this, don't use custom ROM's if you care about these.
Official Lineage OS builds will not ever allow Moto's Battery Mod "Efficiency Mode" to work -- though these can be made to work unofficially, join our discord if you're interested in this feature.
Wi-Fi Calling won't work until either the International or T-Mobile variant gets 8.1 blobs.
Ultrasonic Proximity Sensor doesn't work -- likely won't ever. It is used my Motorola's Active Display, but by nothing in Lineage.
Compass doesn't work -- no clue why.
Stock Display Color Profiles (the ones in Settings, "Display", "Colors") -- The ones in Settings, "Display", "LiveDisplay" work.
The default LiveDisplay "Natural" setting in Settings, "Display", "LiveDisplay", will occasionally dispaly color corruption, to deal with this, just swap to the "SRGB" profile, and swap back to "Natural", or leave it on "SRGB if you don't mind, then you won't experience those infrequent issues.
Notes:
Official Lineage OS builds will not pass CTS/SafetyNet -- due to the AVB flag's "red" status.
Official Lineage OS builds ship with full treble compatibility, with VNDK runtime enforcement! This means that unlike most "ported treble" you'll see, ours is just as it would be from the OEM, and can run any GSI (yes, even Pie!) without need for hacks or additional flashable zips. We relabeled /oem as /vendor (as /oem isn't used in custom ROM's anyway). To use a GSI, flash official Lineage, then flash your GSI, it's that simple! Flashing a factory image will likely write over /oem and remove the mock vendor image. Please don't report GSI bugs here, report them instead to the GSI's maker.
Download:
LineageOS Updater
XDA:DevDB Information
[OFFICIAL] [WEEKLIES] [TREBLE] Lineage OS 15.1, ROM for the Moto Z2 Force
Contributors
npjohnson, invisiblek, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: 8.0.0 (OCSX*)
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-15
Last Updated 2019-03-18

first (always wanted to do that)
thanks for this, nice work everyone!!!

Nice, I was wondering when we were going to get an official thread. I'll be waiting for the 17th to install the weekly.

I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?

felipevsw said:
I have the international version (-05) and have installed plenty of these version (since unofficial release from both invisiblek site and ods.ninja site) as well as the official weeklies (all versions already released) and everything works (based on the description here and known issues), so I'd say it's safe to say intl version had been tested and known to be working as well.
Let me know if you need additional/specific tests that I can do here.
Thanks the official post!
Also, how about volte support? Is it supposed to work?
Click to expand...
Click to collapse
If it isn't in the bugs list, its expected to work, it works on TMO and SPR. And I'll flag the international as compatible, thanks.

Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.

Uzephi said:
Since it isn't in known issues, I assume VoIP compression was fixed?
Edit: known workaround is use Bluetooth for video/VoIP calls. I don't know if USB audio would work or not.
Click to expand...
Click to collapse
Added to OP as an issue.

??? for listing known accurate issues ???
I was pissed after installing Invictrix rom only to find out sound mods don't work.

I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.

fixed, can remove this.

DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.

DTHayakawa said:
I'm having an issue with video calls on Whatsapp and Duo. The other person can't hear me and I can't hear the other person.
Some other issues:
- Ok google not working with screen off (but it's fine to me)
- Overview is messy sometimes when using multi-window (doesn't show previews of multi-windowed apps)
- Even when installing Moto Camera the app does not show secondary camera functions (Portrait, B/W, etc)
For my daily usage the audio on video calls is the most serious issue that drives me back to stock. I hope they fix it soon.
Click to expand...
Click to collapse
1. Added to known bugs.
2. I don't experience this (and if it is present, its platform wide, and not our problem specifically).
3. I can't really easily support a prebuilt app all that easily. The B&W cam us supported in the default Snap camera.

Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).

fixed, can remove post now.

Uzephi said:
Anything that uses VoIP compression is broken. Most video calling or internet calling apps in general use it.
Click to expand...
Click to collapse
So I assume this would apply to hangouts and hangouts dialer?

npjohnson said:
Also, OTA will be broken until we figure out why signing server's aren't signing our payload zips right.
To work around this, you can update weekly by sideloading the nightly, rebooting to recovery (important), re-sideloading any mods you use (GApps, AddonSU, etc.).
Click to expand...
Click to collapse
Resolved.

Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?

MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?

Magisk Works
3's&7's said:
I was literally plugging in to try this ROM until I read this. Have you tried Magisk yet?
Click to expand...
Click to collapse
I have ran into this same issue when flashing build > lineage-15.1-20180721-nightly-nash-signed.zip
I can confirm that it happens with both TWRP 3.2.2-2 & TWRP 3.2.1-1
I flashed Magisk 16.4 and it works flawlessly no issues.
I am very happy with this ROM it works great for me. Thank You Devs! :good:

MattKilla said:
Unable to install Lineage su addon (using TWRP 3.2.2-2)
_BEGIN_
Installing su addon...
set_metadata: Error on lstat of "/system/etc/init/superuser.rc": too many symlinks encountered
Updater process ended with ERROR: 7
_END_
Thoughts?
Click to expand...
Click to collapse
was TWRP installed or did you just boot to it?

[ROM][UNOFFICIAL][microG][root][OTA][WireGuard][enchilada][9] LineageOS 16.0

{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This build includes microG, a free and open implementation of the Google Play Services Framework. It allows applications calling proprietary Google APIs to run on AOSP-based ROMs like Replicant and LineageOS. Acting as a replacement for the closed-source Google Apps (GAPPS), it is a powerful tool to reclaim your privacy while enjoying Android core features such as Google Cloud Messaging.
It also includes WireGuard, a next generation secure VPN tunnel for the Linux kernel, with modern yet conservative cryptography and simple design principles. It is meant as a replacement for OpenVPN and for IPsec, and generally has better performance and security characteristics than both. It also is much easier to use. The whitepaper was peer reviewed for NDSS17 and the protocol itself has been formally verified. Since it lives in the kernel, it not only is very fast, but it is able to integrate in clever ways that are quite nice for battery life and overall smoothness. There are already commercial VPN providers offering services using WireGuard, and it is very easy to run your own WireGuard servers as well.
I probably won't do other types of builds unless somebody has a really terrific suggestion. These builds exists for my own convenience and I thought I'd share it with the XDA community where I've been lurking and leeching for years.
Features
Embedded root (can be enabled in Developer Settings)
Restricted (system-only) signature spoofing
microG (FakeStore, GmsCore, GsfProxy, legacy mapsv1 implementation)
Mozilla Location Services + Nominatim for network-based location
FDroid (+Privileged Extension)
WireGuard-enabled LineageOS kernel
Monthly automagical OTA updates (signed builds, https)
Reporting Bugs
I just build using the latest official LineageOS (also see this thread), wireguard patch, TheMuppets proprietary files and microG prebuilts. Report any "regular" bugs to those threads and/or Git pages unless you're sure the problem is unique to these builds.
Initial installation
NOTE: TWRP gets replaced by the stock recovery every time you install a ROM zip. Either use fastboot to boot TWRP or flash the TWRP zip file every time after you flash a ROM zip.
OnePlus firmware must be installed on your device on both A/B slots. Hence the instructions below tell you to flash OxygenOS twice.
Wipe system, data and cache.
Flash latest OxygenOS using TWRP.
Reboot to TWRP
Flash OxygenOS again using TWRP.
Reboot to TWRP
Flash the newest build using TWRP.
Reboot to TWRP.
Flash the newest build using TWRP again.
Reboot and enjoy!
OTA Updates
For OTA updates, use the built-in Updater app. Everything should JustWork(TM) without any TWRP/recovery magic.
Downloads
https://lineage.darwinkel.net/builds/full
Delta/partial updates are not supported.
I recommend Aurora Store if you want to download and install apps from Google Play.

Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?

Cygnust said:
Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?
Click to expand...
Click to collapse
This build has a free software alternative to opengapps baked-in. This ROM is probably not what you're looking for if you want to install the regular Google Play Services. No clue about Magisk or a custom kernel surviving OTA.

Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?

Tomatot- said:
Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?
Click to expand...
Click to collapse
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!

perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?

AndroidBolder said:
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!
Click to expand...
Click to collapse
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?

Master One said:
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?
Click to expand...
Click to collapse
I'm not that fond of Magisk and neither are the LineageOS devs. I don't use any apps that use SafetyNet and this works for me personally (I mainly use root for Yalp Store and WireGuard). I have, however, tested it. I enabled DroidGuard and microG's SafetyNet attestation and tested it with an app. Unfortunately, it didn't seem to pass even with root disabled in developer settings. Magisk Hide might help, though.
Toni Moon said:
perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?
Click to expand...
Click to collapse
I'm pretty sure you can install a Google Play Store APK, but you would have to disable or remove FakeStore for it to work, I think. I personally use Yalp Store to download apps from Google Play (including paid ones).
EDIT: download speeds have been fixed.

1 Question, how to get snapchat and chromecast work?

TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I don't use either of those apps, no clue.

Can I use blue Spark twrp?

noky76 said:
Can I use blue Spark twrp?
Click to expand...
Click to collapse
You can.

@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.

@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?

This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?

Master One said:
@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.
Click to expand...
Click to collapse
Sounds really interesting, but the way you're putting it, it seems somewhat unstable/unreliable. VoLTE works fine with my carrier so I have no way to test it. If multiple people can confirm it works without causing instability then I'll consider changing build.prop.
Master One said:
@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?
Click to expand...
Click to collapse
I presume addonsu remove would work, no clue if the 15.1 version works on Pie. Did a quick search but I can't find one for LOS16. Bingo! uploaded by Luk1337, one of the LOS devs.
admiralderp said:
This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?
Click to expand...
Click to collapse
Like most custom roms slightly worse than OxygenOS, but completely fine otherwise!

Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).

nksonfire said:
Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).
Click to expand...
Click to collapse
It works on most custom ROMs as long as you use Maps 9.82.1

Thank you a TON for providing these builds. This finally gives me a path to move off of OxygenOS. Installed, tested, everything working beautifully *including VoLTE and VoWiFi* (on U.S. T-Mobile).
TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I have managed a way to get at the very least Snapchat working on this ROM.
Flash as normal.
After that, flash Magisk from TWRP.
Add the *Nanodroid*, not official, microG repo to F-Droid and install the DroidGuard Helper from there. You'll have to web-search "nanodroid fdroid repo" as I cannot provide external links on this new account.
(I've not tested any of this with the official repo's DroidGuard Helper, but there are issues on microG's Github repo suggesting that SafetyNet will only pass with Nanodroid's version of DroidGuard Helper.)
Install a file manager with root capability (such as Amaze on F-Droid) and navigate to /data/app where you will find the DroidGuard Helper under "org.microg.gms.droidguard-randomstringhere". Move this folder to /system/priv-app and reboot.
Make sure SafetyNet is on in microG Settings and ensure it is using the official server (by hitting the three dots in the corner, selecting Advanced and selecting "Use official server".)
Enable Magisk Hide in Magisk Manager and enable hiding for Snapchat and DroidGuard Helper.
Try SafetyNet attestation under Magisk Manager. Hopefully both checks should pass.
Enjoy.
I did a test OTA (the current 1/30/19 version is available there, so I just downloaded and installed it again) and the only changes to be made were to re-flash TWRP and Magisk then re-install DroidGuard Helper and move it to /system/priv-app. All microG and Magisk Manager settings were retained.

As your post says, I have a really terrificant suggestion.
Why don't you try to port Sailfish Os on op6?
If you think that my suggestion is not terrificant I will understand. I would like to port it but I can't do that. For many reasons. Bye and congrats for this build. it looks like great.
Ceers

[CLOSED] [ROM][CUSTOM][O][SM-J530F] /e/ OS for Samsung J5 2017 (j5y17lte)

{
"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.
*/
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 the stable Lineage OS
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 our LOS 15.1 builds.
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 FAQ #0 why I did this drastic change)
AuroraStore has been added (pls always use "anonymous" unless you need paid apps to avoid bans)
F-Droid has been added (The OpenSource alternative store. First search for any apps here!)
Dozens of F-Droid repositories are pre-installed (activate them with just a finger tip! That's needed to ensure you only get what you want)
The above changes are the reasons why my builds are of the type "CUSTOM" and not "UNOFFICIAL".
This is according to the rules defined by /e/.
Known issues:
Keep in mind that this is brand new stuff so it may (still) contain unknown issues!
So back up regularly and frequently!
When your current STOCK firmware or the latest you had flashed is PIE (Android 9) RIL will not work in this ROM. I am trying to fix that currently but while it works when your STOCK firmware/bootloader stack is on Oreo or earlier it stops working when you ever upgraded to pie
If you find a bug not listed let me know and SHARE LOGS! -> READ FAQ#1 for how to provide proper logs.
Requirements
Latest TWRP or SHRP build.
Latest TWRP build based on Oreo sources (build by myself) can be found here: click
Do a full Nandroid backup before doing anything!
Installation
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
Get your builds from my leech server (new installs or re-installs)
http://leech.binbash.rocks:8008/e-os/oreo/
If you have /e/ installed already and just want to update to a newer release:
Android settings -> Updater (yes my builds have OTA support!)
Note:
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
search results from this thread: click
Support
Of course in this thread but also by Telegram. I have created a generic group for all stuff around Android : here
and another one if you want to keep up2date whenever I build something (TWRP, SHRP, LOS, /e/, ...): here
Credits
nailyk
LineageOS (the base of /e/)
The /e/ foundation and all related devs making this experience possible!
The Exynos7870 Team
and more..
Sources
build manifest
XDA:DevDB Information
j5y17lte_eos-oreo_custom, ROM for the Samsung Galaxy J5
Contributors
steadfasterX, nailyk, ananjaser1211,DarkLord1731,Exynos7870 Team (github)
Source Code: https://gitlab.e.foundation/e
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
ROM Firmware Required: NOUGAT/OREO only - if you have stock PIE installed RIL won't work!
Based On: Lineage OS
Version Information
Status: Beta
Created 2020-08-05
Last Updated 2020-09-09

-
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 have an audio issue follow FAQ #6 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 when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed.
Pro-Tip: a very first test is to set magisk on core functions only to see if an extension causes your issue or not.
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official /e/ builds?
TL;DR answer is: who knows...
Background:
/e/ points to LineageOS requirements which need to be met first. LineageOS has "some" requirements before they accept it to do official builds: device-support-requirements.
No I personally do not have any plans in going official atm. That might change though.
If someone else wants to go that way and needs help, I am here. But I cannot spend my whole free time on that.
Q #04: 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 #5: Is there an /e/ specific FAQ?
Sure:
FAQ: click
Forum: click
HOWTOs: click (a great resource for all your first questions)
Q #6: 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 audio issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org
Q #7: 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.
.-

Reserved

Encryption of storage works?

jw96 said:
Encryption of storage works?
Click to expand...
Click to collapse
Haven't tested yet
Sent from my OnePlus 7T Pro using XDA Labs

I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.

Morceaux said:
I just installed it on my J5 2017 (SM-J530F). I did a full clean install (No magisk or xposed installed), but sadly my sim card is not detected.
Click to expand...
Click to collapse
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-

steadfasterX said:
yes one reason for that (I encountered that rn) might be the bootloader version.
What was the last stock ROM version you flashed? exact version if possible but at least if it was nougat, oreo, pie
or even better show a screen of "baseband version" in Android settings
.-
Click to expand...
Click to collapse
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?

Morceaux said:
My baseband Version is "Unknow" rn, and I didn't check on my last ROM.
I used the stock ROM and was in pie version (I don't have the exact version rn, if you really want it I'll check tonight.
Do you want more informations ?
Click to expand...
Click to collapse
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-

steadfasterX said:
exactly what happened to me. I have upgraded the STOCK bootloader and modem to pie and RIL stops working. Was trying to figure out the reason for that but no luck yet.
so for sure the prev. STOCK version is an issue here. My last Samsung is a while ago so I dont know if one can downgrade without an issue or if I would brick it..
EDIT:
woa.. I cannot downgrade.. "check fail" in ODIN pointing to lower ARB levels.. damn.
so it seems that I have to find out the root cause for newer (i.e pie) bootloader stack
.-
Click to expand...
Click to collapse
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)

Morceaux said:
I tried the same things last night, and I had the same problems (just so you know, If maybe it can help)
Click to expand...
Click to collapse
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-

steadfasterX said:
thx. yes it definitively depends on the bootloader stack if it works or not. I have updated the OP with that information ("firmware required").
technical site info: I was able to flash the OREO radio (modem.bin) and cp_debug (modem_debug.bin) partitions without a problem but this alone does not make it work again.
Like for LG the 2nd stage bootloader likely initializes the hardware and the software (i.e. e.g. RIL) must know where and how these are loaded in memory etc. That's why just replacing the radio partitions will not fix it. RIL (and that is not just replacing a file) must fit to that as well..
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)

Morceaux said:
Do you have a link to the last stock rom ? I think I don't have the right one, because I couldn't flash it, or maybe I did something wrong
(Nevermind, I found the right one)
Click to expand...
Click to collapse
https://sfirmware.com/samsung-sm-j530f/

goodjob

steadfasterX said:
The good news are: I am able to boot the radio now - PIN popup comes up and baseband is now correctly displayed (I am on the latest stock pie ROM available..)
but as you can see in the status bar still no cell service so still something missing..
View attachment 5078627
IMEI is still 0 as well so it might has to do with the EFS.. which would explain it
but at least some progress.. At least it is clear now why some ppl reported on our LOS thread that SIM does not work for them while it worked for others.
.-
Click to expand...
Click to collapse
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged

jaggedN said:
Hi,
do you think there is a chance to get this running for phones which are already on PIE? (I think this is the majority of all phones.....)
kind regards
Jagged
Click to expand...
Click to collapse
Oof .. Well i don't have much time atm but i need that phone as my navigation device for my motor bike. so i need to fix it
Sent from my OnePlus 7T Pro using XDA Labs

New eOS v1-oreo build *20200909* has finished!
Changes:
- kernel: commits
- Device tree: commits
- Common Device tree: commits
Download: see OP
Known issue with the OTA Update!
Unfortunately it will work with the next update first. There was a missing entry in the fstab causing the install to fail. You can still use the Updater to download the package though!
1. Open Settings —> System
2. Expand Advanced & select Updater
3. Refresh if not listed already
4. Download
5. Reboot to TWRP
6. browse to /data/lineageos_updates/ and select the zip from here
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
The second one will also show sha256sums of every build for those who need it.
.-

No more OREO builds!
The reason is that almost everyone has flashed stock PIE in the meanwhile and I switched to Android 10 already. A10 works great so far and so backporting whatever is needed is not worth it.
Check it out: j5y17lte - Android 10 / Q
Thread closed.
.-

[OFFICIAL] LineageOS 18.1 for the Samsung Galaxy S4 (All QCOM Variants)

{
"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"
}
Samsung Galaxy S4
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for all Galaxy S4 variants.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
Official Builds:
jactivelte (GT-I9295)
jflteatt (SGH-I337) - Please note you will need to be on bootloader I337UCUAMDB or I337UCUAMDL
jfltespr (SCH-R970/C/X, SPH-L720)
jfltevzw (SCH-I545) - Please note you need to be on bootloader I545VRUSMDK
jfltexx (GT-I9505, SGH-I337M, SGH-M919) - NOTE: GT-I9505G is supported in this build, but due to system size space limitations it will not fit any form of GApps package.
jfvelte (GT-I9515/L)
Unofficial - built once a month by me, includes GApps and Pixel goodies:
jactivelte (GT-I9295)
jflteatt (SGH-I337) - Please note you will need to be on bootloader I337UCUAMDB or I337UCUAMDL
jfltespr (SCH-R970/C/X, SPH-L720)
jfltevzw (SCH-I545) - Please note you need to be on bootloader I545VRUSMDK
jfltexx (GT-I9505, SGH-I337M, SGH-M919) - NOTE: GT-I9505G is supported in this build, but due to system size space limitations it will not fit any form of GApps package.
jfvelte (GT-I9515/L)
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
MHL doesn't work after LineageOS 14.1, and likely never will again, as Google dropped support for it platform-wide in AOSP.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Kernel Source: https://github.com/LineageOS/android_kernel_samsung_jf

good and many thanks

Is MindTheGapps like pico or nano Gapps?

Thanks @npjohnson and of course the one how did the most work: @arco68
all seems good so far.
just and only if someone stumbles over it, two hints:
1. Hint:
On an linux box I followed the install instruction " Installing a custom recovery using heimdall" and the following from here:
Install LineageOS on jfltexx | LineageOS Wiki
wiki.lineageos.org
It seems the second TIP on the page is wrong/outdated.
cit.: "TIP: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success."
*I* got no "failed to read command: Success."
Don't wonder, the Rom installed correct !
see attached photo's
2. Hint:
if one is searching for the "advanced power menu", it's now under system => gesture.
AFAIK, for LOS 17.1 it had been under the dev. opt's

I have problems installing apps from google play, it gives me a storage error and my mobile is empty, any solution?

joam280 said:
I have problems installing apps from google play, it gives me a storage error and my mobile is empty, any solution?
Click to expand...
Click to collapse
what is empty ?
try a reboot...

rw_on_xda said:
Thanks @npjohnson and of course the one how did the most work: @arco68
all seems good so far.
1. Hint:
I followed the install instruction and it seems the second Tip is wrong/outdated.
cit.: "Tip: If the process succeeds the output will stop at 47% and report adb: failed to read command: Success."
*I* got no "failed to read command: Success." (see attached photo's)
2. Hint:
if one is searching for the "advanced power menu", it's now under system => gesture.
AFAIK, for LOS 17.1 it had been in the dev. opt's
Click to expand...
Click to collapse
Please note that if you’re currently on an official build, you DO NOT need to wipe your device, unless your device’s wiki page specifically dictates otherwise, as is needed for some devices with massive changes, such as a repartition.
Click to expand...
Click to collapse
What that means @rw_on_xda ? If im on the official 17.1 can i just upgrade to 18.1? "Dirty flash" possible to 18.1 from 17.1 ?
EDIT:
Dirty flash from official 17.1:
Wiped Cache, Dalwik ART Chache, System rebooted to TWRP:
1. Flashed LOS 18.1
2. OpenGapps
3. Magisk
Everything works well for now.
Regards !

bersem said:
What that means @rw_on_xda ?...
Click to expand...
Click to collapse
What does what mean ?

hello!
with here maps I can't select sdcard for saving maps. With previuos lineage OS I haven't any problems

Savatage76 said:
hello!
with here maps I can't select sdcard for saving maps. With previuos lineage OS I haven't any problems
Click to expand...
Click to collapse
That's not a ROM issue. Rules for external SD have changed in android 11. Apps have to comply.

deleted

rw_on_xda said:
what is empty ?
try a reboot...
Click to expand...
Click to collapse
problem solved with a format

@npjohnson Ahaha, well played!
So the april fool of 2021 for S4 has been that LOS18.1 on 1st of April for wasn`t a hoax for real...
I fell for it.
Thx to all involved making 18.1 happen on this device

bersem said:
What that means @rw_on_xda ? If im on the official 17.1 can i just upgrade to 18.1? "Dirty flash" possible to 18.1 from 17.1 ?
EDIT:
Dirty flash from official 17.1:
Wiped Cache, Dalwik ART Chache, System rebooted to TWRP:
1. Flashed LOS 18.1
2. OpenGapps
3. Magisk
Everything works well for now.
Regards !View attachment 5267359
Click to expand...
Click to collapse
Hi,
Which TWRP did you used for that? The official last one is 3.2.3-0 and as far as I remember doesn't work completely on ours S4 (GT-I9505 at least). I only used it to make backups then I changed to LOS recovery un order to have automatic updates.
Thanks in advance

hello!...another question...
I can't find lens for search a song or other in stock music player. where is it?

Hi again,
I also dirty flashed using TWRP 3.2.3-0 (backing up previously) and all works fine for me at this moment. At the end, I flashed LOS Recovery to prevent issues when next updates arrives.
I have noticed that there is a "new?" option into LOS updater preferences that allow to update the recovery. I switched on to see how it works

Gitanitos said:
Hi again,
I also dirty flashed using TWRP 3.2.3-0 (backing up previously) and all works fine for me at this moment. At the end, I flashed LOS Recovery to prevent issues when next updates arrives.
I have noticed that there is a "new?" option into LOS updater preferences that allow to update the recovery. I switched on to see how it works
Click to expand...
Click to collapse
im using the last one:
twrp-3.5.1_9-0-jflte.img
no problems with updater.
EDIT: The secure method to upgrade to 18.1:
LOS upgrade Wiki

bersem said:
im using the last one:
twrp-3.5.1_9-0-jflte.img
no problems with updater.
EDIT: The secure method to upgrade to 18.1:
LOS upgrade Wiki
Click to expand...
Click to collapse
Thanks for the answer, I've checked before and I didn't found this recovery maybe a wrong web... let's see first how it works the recovery update and later will try these TWRP.
And for sure the safest way to upgrade is the LOS Wiky (I upgraded my old S4 since LOS14 ) but sometimes I love to try alternative methods.
Have a good day

@npjohnson
Bah... introduced in Android 11
Code:
/system_ext
wtf
"The /system_ext partition
The /system_ext partition was introduced in Android 11 as an optional partition. (It’s the place for non-AOSP components that have tight coupling with the AOSP-defined components in the /system partition.) The /system_ext partition is assumed to be the OEM-specific extension to the /system partition, without an interface defined across the two partitions. Components in the /system_ext partition can make private API calls into the /system partition, and components in the /systempartition can make private API calls into the /system_ext partition."
AOSP
As i understood, this is a dynamic mounted img, no way to rw (at least i haven`t found a way yet), so you can`t remove some of the default apps under /system_ext/apps or /system_ext/priv-app, like snap or camera.
As mentioned in the link above,
"The /system_ext partition is optional, but it’s beneficial to use it for any custom features and extensions that are tightly coupled with AOSP- based components. This distinction helps you identify changes you need to make, to move such components from the /system_ext partition to the /productpartition over a period of time."
Wouldn`t it be better to move them back to /system/priv-app or product? At least, people, who don`t use these apps could remove them, like they can with i.e. the music or audiofx app. This is somehow inconsistent, or is there a reason, why some of the "LOS-Bloat" ( ;-) ) is located under /system_ext/priv-app and others don`t?

many thanks all developers - great work.
i had dirty flashed from official 17.1 with 65 installed apps yesterday
(SAMSUNG_I9505)
rebooted to TWRP (twrp-3.5.1_9-0-jflte)
0. wiped only system/dalvic/cache:
1. flashed LOS (lineage-18.1-20210401-nightly-jfltexx-signed.zip)
2. MindTheGapps-11.0.0-arm-20210328_143701
3. magisk 22.0
everything works well.
but there was to much google-apps.
i had unzipped MindTheGapps-11.0.0-arm-20210328_143701
and reduced apps like "open_gapps-arm-pico"
deleted:
system/product/app/GoogleTTS
system/product/app/talkback
system/product/priv-app/AndroidAutoStubPrebuilt
system/product/priv-app/Velvet
and zipped again "MindTheGapps-11.0.0-arm-20210328_reduced"
also once again
0. wiped only system/dalvic/cache - rebooted to TWRP:
1. flashed LOS 18.1
2. MindTheGapps-11.0.0-arm-20210328_reduced
3. magisk
everything works well for now.

[OFFICIAL] LineageOS 18.1 for the Google Pixel 3a XL

{
"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"
}
Google Pixel 3a XL
Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.
Introduction:
This is the Official Lineage OS 18.1 thread for the Google Pixel 3a XL.
Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
bonito
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
Known Bugs:
None.
Find any? Report them according to this guide.
Notes:
The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Kernel Source: https://github.com/LineageOS/android_kernel_google_msm-4.9

Going to try it now.
Thank you!

npjohnson said:
​
Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!
Click to expand...
Click to collapse
syntax error Are we talking about the Kernel being bundled?

ssurell said:
syntax error Are we talking about the Kernel being bundled?
Click to expand...
Click to collapse
What? No, firmware, like modem, bootloader, etc.

Question:
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.
So are you saying if we root there is no support? As most of us coming from stock would at least need root temporarily to restore all our apps.
Can anyone confirm if root even works on this build. I woudnt see any reason not but would like to know cause of the above reason.
UPDATE: Decided to just go for it and everything is working great so far. Took a little work to get google apps working instead of the included aosp ones (phone calendar and contacts) and a bt more work to get it to pass safteynet but its all working 100% now. Also tested this build with both ex kernel and mvk and they both seem to work just fine as well. Will report back if anything changes as have only been running it.a few hours but so far no issues or complaints at all.
Great job LOS team

What is the official way to obtain root access? or is there one any more?

cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
Based on the above statement i quoted sounds like root is not "officially" supported at all. That said to get root i followed the process by which you patch a boot image file with magisk manager. Making it pass safteynet net took additional steps.
If you need more details on either process just post back and i can be more detailed

adm1jtg said:
If you need more details on either process just post back and i can be more detailed
Click to expand...
Click to collapse
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!

cliffordd said:
Yes please - maybe message me off thread, as this topic might not be appropriate on here.
I have Magisk app installed, due to using Titanium Backup to keep a backup of my app. The upgrade went great and everything is working fine under LOS 18.1. But I miss the ability to take backups and use certain features properly on the device (ie clipboard sharing and other features in KDE Connect, scheduling backups etc) There used to be a package provided by LOS to add or remove su - https://download.lineageos.org/extras but that seems to have stopped now. I was just wondering if there was an "official" way of doing it!
I actually held off upgrading due to the previous download being released on 1st April and not finding some previous April fools pranks to be very funny!!
Click to expand...
Click to collapse
sent you a private

cliffordd said:
What is the official way to obtain root access? or is there one any more?
Click to expand...
Click to collapse
i flashed the version of Magisk (v21.4) via the LineageOS recovery using the adb sideload and just updated to v22 via the app. I haven't had any issues with root since installing.

First off, I want to say thank you for all the hard work on these builds.
I have came across one issue that isn't working for me, but might not be something everyone else uses a lot. My "squeeze" for Assistant isn't working, but I can change it to take a screenshot of any other option, except the Assistant. Am I doing something wrong or is there another settings need to activate for it to work?
Thanks!

Really want to try this, but can't "fastboot boot twrp.img" or "fastboot flash boot twrp.img" in Android 11 to backup my partitions. What's the point of Android OS if I can't backup my system? I can boot into Lineage OS Recovery, enable adb, figure out the partition names, dd the partitions from shell or pull with adb? But good grief, kinda ridiculous if you ask me.

Haven't been able to use twrp since Android 9 far as i know

lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.

Nevermind, user error.

ssurell said:
lineage-18.1-20210401-nightly-bonito-signed.zip
Searching Settings aborts after a matter of seconds and while typing.
Derelict non-clearable notifications requiring reboot or force close.
Desk Clock stuck at "Loading".
The final LOS 17 seems more polished, but lingering notifications are still present requiring force close.
Click to expand...
Click to collapse
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.

npjohnson said:
you're using opengapps - don't do that ;p
Use MindTheGapps, which doesn't break that feature.
Click to expand...
Click to collapse
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1

ssurell said:
Actually, it's the first time I've used MindTheGapps. I used OpenGapps after falling back to 17.1 though since it is recommended on the LOS site. I kind of liked the Slim Gapps feel of MTG though, and might try it on 17.1
Click to expand...
Click to collapse
weird - we don't have MTG builds for 17.1 though, sadly.

How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.

ssurell said:
How do I disable encrypted device? Tried ElemntalX kernel and Disable_Dm-Verity_ForceEncrypt_quota.zip but phone is still encrypted under security settings after first boot.
When I see "Say Hello To Trust", I just want to punch it in the face. Somebody just needs to build an updated LOS 16 so we have TWRP and possible access to /data (formerly user space) and call it a day.
Click to expand...
Click to collapse
Why do you want encryption disabled?
It's hardware backed, and FBE, so very little gain from running unencrypted...
"Trust" has nothing to do with encryption, it can be on, off, trust just reports it to the user.
Why do you want TWRP? Lineage Recovery does the job just fine. What do you mean "/data (formerly userspace)"? That statement doesn't make much sense.
Regardless of all the above, the disabel force encrypt zip, followed by `fastboot -w` to format userdata ought to do it - but be warned, if you set a PIN, Android (AOSP, not a lineage thing specifically) will re-encrypt you... hence there being no point.