[ROM] LineageOS 17/18/19 UNOFFICIAL - (Update: 2023-02-25)

[petefoth]

Should I run `applyPatches.sh` to apply all the patches, or just the `fix-custom-apn-script` patch?

I ran `applyPatches.sh` and it seems ti have done the trick - thanks

 

[fenamori]

Heya, i'm having no luck with getting GPS to work on my G8441 running the 11-15 build of LOS 18.1. I've tried clearing AGPS with GPS test and leaving that running outside for a while, but i'm still unable to get a consistent signal. Maps will pick up an accurate signal about once every 30 minutes, and then nothing. GPS test gets a lock fairly quickly, between around 5 seconds to a minute or so, if not instantly. Anything else that uses GPS (Pokemon GO, some restaurant apps) just doesn't work at all. Any ideas?

 

[Flamefire]

(Late) Merry Christmas!

December updates are out including the first 19.1 release. In a quick test I was able to upgrade from 18.1 to 19.1 without loosing data. However the issue is OpenGApps which isn't available for Android 12 (yet?). So you need to wipe /system before flash 19.1 from 18.1 to remove OpenGApps and then install another GApps (e.g. MindTheGApps) in a matching version.
Of course the 19.1 version contains all the goodies I added to my other builds including passing SafetyNet and enhanced brightness control (Ultra-Dim)

I was working very hard to get another major change set into this release both to kernel and vendor files but decided to delay that to next year for proper testing etc. although a lot of time was already spent on that.

---

Thats great news! I wonder how did you decide to add 19.1?

I asked before if there was any interest since derf elot discontinued building it. There was so I added it especially as I'll backport what I can to especially 17.1.
Additionally if I was to choose between 18.1 and 19.1 I'd go for 19.1 especially due to finally being able to use BLE without location permissions. Generally I see 18.1 as only minor improvement over 17.1 not worth loosing the Sony camera app but 19.1 has enough new stuff to consider switching

Should I run `applyPatches.sh` to apply all the patches, or just the `fix-custom-apn-script` patch?

You should only apply the patches you really want. Some of them do major changes so check their very descriptive names and the changes done. A lot of work went into those patches alone so I'd consider them my (not-so-)secret sauce.

Heya, i'm having no luck with getting GPS to work on my G8441 running the 11-15 build of LOS 18.1. I've tried clearing AGPS with GPS test and leaving that running outside for a while, but i'm still unable to get a consistent signal. Maps will pick up an accurate signal about once every 30 minutes, and then nothing. GPS test gets a lock fairly quickly, between around 5 seconds to a minute or so, if not instantly. Anything else that uses GPS (Pokemon GO, some restaurant apps) just doesn't work at all. Any ideas?

It looks like Sony turned off their AGPS server (supl.sonyericsson.com) so in the December builds I switched back to the Google servers. Give that a try

 

[fenamori]

It looks like Sony turned off their AGPS server (supl.sonyericsson.com) so in the December builds I switched back to the Google servers. Give that a try

Works perfectly now, thank you so much!

 

[V0latyle]

Of course the 19.1 version contains all the goodies I added to my other builds including passing SafetyNet and enhanced brightness control (Ultra-Dim)

Please be aware that SafetyNet has been replaced by Play Integrity

More information here

 

[Flamefire]

Please be aware that SafetyNet has been replaced by Play Integrity

More information here

Thanks for the info. I just tried: The ROM passes the 2 lower levels of Play Integrity the same way it passes SafetyNet, i.e. only failing the "Strong integrity"/hardware-based attestation. This is expected as I'm using a version of the USNF.

 

[V0latyle]

Thanks for the info. I just tried: The ROM passes the 2 lower levels of Play Integrity the same way it passes SafetyNet, i.e. only failing the "Strong integrity"/hardware-based attestation. This is expected as I'm using a version of the USNF.

Correct. Strong integrity should always fail on an unlocked bootloader.

 

[Dfis]

Where can I download 2022-12-27 update?

 

[victor126]

Where can I download 2022-12-27 update?

Search Files Results for "lilac.zip" | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

 

[Dfis]

Search Files Results for "lilac.zip" | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com

Thanks!
Can I dirty update from twrp on the existing 17.1 version?

 

[victor126]

Thanks!
Can I dirty update from twrp on the existing 17.1 version?

17.1 to 17.1 should be no issue. but then again im not the developer.

 

[victor126]

(Late) Merry Christmas!

December updates are out including the first 19.1 release. In a quick test I was able to upgrade from 18.1 to 19.1 without loosing data. However the issue is OpenGApps which isn't available for Android 12 (yet?). So you need to wipe /system before flash 19.1 from 18.1 to remove OpenGApps and then install another GApps (e.g. MindTheGApps) in a matching version.
Of course the 19.1 version contains all the goodies I added to my other builds including passing SafetyNet and enhanced brightness control (Ultra-Dim)

im guessing your 19.1 has the same big icons for the pulldown quick setting ?

 

[Flamefire]

Where can I download 2022-12-27 update?

Download link for all versions is in the initial post. It leads to a folder on AFH containing subfolders for the versions.

Thanks!
Can I dirty update from twrp on the existing 17.1 version?

Dirty flash is possible staying on the same version (I.e. 17 to newer 17) and also to higher versions (17 to 18) but you need to have twrp decrypt data (if that fails then the upgrade may not work) and make sure the gapps matches the Android version (when upgrading to a newer major version) so you may need to flash that too

im guessing your 19.1 has the same big icons for the pulldown quick setting ?

I avoid modifying stuff if I don't have to so I'd guess yes although I don't know what you are comparing them to

 

[victor126]

Download link for all versions is in the initial post. It leads to a folder on AFH containing subfolders for the versions.

Dirty flash is possible staying on the same version (I.e. 17 to newer 17) and also to higher versions (17 to 18) but you need to have twrp decrypt data (if that fails then the upgrade may not work) and make sure the gapps matches the Android version (when upgrading to a newer major version) so you may need to flash that too

I avoid modifying stuff if I don't have to so I'd guess yes although I don't know what you are comparing them to

just wondering. samsung android 12 still has the small icons when you pull down the notifications. and so far all android 12 los based roms use the new big ones

 

[Arcline]

just wondering. samsung android 12 still has the small icons when you pull down the notifications. and so far all android 12 los based roms use the new big ones

Samsung is OneUI, Los is stock Android with more features.

 

[petefoth]

December updates are out including the first 19.1 release. In a quick test I was able to upgrade from 18.1 to 19.1 without loosing data. H

I tried making my unofficial and custom lineageOS for MicroG builds from your repos (previous builds are based on whatawurst's) but I'm stumped by the fact that most vendor blobs aren't in the vendor/sony/lilac repo. I usually build on cloud servers, and I don't have an image on hand to extract the files. I've been round this loop before when tryong to make up-to-date /e/OS builds, but the process of extracting blobs from an image and putting them in my own repo is too fiddly and error prone.

So I'll stick with making v20.0 builds

 

[Flamefire]

I tried making my unofficial and custom lineageOS for MicroG builds from your repos (previous builds are based on whatawurst's) but I'm stumped by the fact that most vendor blobs aren't in the vendor/sony/lilac repo. I usually build on cloud servers, and I don't have an image on hand to extract the files.

I build everything locally as I need to debug stuff etc. And as Git isn't particularly suited for binary blobs I avoid having them in the repo.

If there is interest in MicroG builds for 17-19 I can try to integrate them as separate builds. IMO it should be possible by having a Makefile/env variable switch. Would you mind sharing your changes/build script for the MicroG build? I remember doing a quick test based on their Docker image recipe natively but must have missed something as it failed.

 

[Arcline]

Just to mention, including signature spoofing would allow for a choice by the user.

 

[petefoth]

I do (mostly) use a build script, but that's because, as well as the 'standard` LineageOS for MicroG builds I make a 'custom' build with some apps added and removed to make it more like /e/OS. To do that I use this project and my scripts are structured to fit in with that. All the scripts I use are here and an example of how I use them is in my project Wiki.

If you build the normal way (`repo sync, lunch, mka`) then you really only need some of what is in my `before.sh`, specifically lines 55-87 which Get and apply the restricted signature spoofing patches from the L4M docker-lineage-cicd repo. That logic was pulled from their `Dockerfile` -lines 110-143, and 204-214 (or 204-238 if you want full signature spoofing rather than the recommended restricted spoofing).

However, for what you are thinking of doing it's probably easier to stick with Docker...

I remember doing a quick test based on their Docker image recipe natively but must have missed something as it failed.

Building with the Docker image as described here should be working now for 18.1 and 19.1 builds. You need

1. a manifest with the following line

    <?xml version="1.0" encoding="UTF-8"?>

    <manifest>

        <project path="vendor/partner_gms" name="lineageos4microg/android_vendor_partner_gms" remote="github" revision="master" />

    </manifest>

2. A manifest pointing to your files (including vendor blobs, or have them in place in `vendor/sony/lilac`)
3. Set the environment variable `WITH_GMS=true` in your `docker run` command

With those in place the following `docker run` command should "just work"

docker run \
  -v "/srv/src:/srv/src" \
  -v "/srv/zips:/srv/zips" \
  -v "/srv/logs:/srv/logs" \
  -v "/srv/cache:/srv/ccache" \
  -v "/srv/keys:/srv/keys" \
  -v "/srv/local_manifests:/srv/local_manifests" \
  -e "BRANCH_NAME=lineage-18.1 \
  -e "DEVICE_LIST=lilac" \
  -e "SIGN_BUILDS=true" \
  -e "SIGNATURE_SPOOFING=restricted" \
  -e "WITH_GMS=true" \
  lineageos4microg/docker-lineage-cicd

Building for 17.1 is more complicated: the method described in the L4M Readme doesn't work in my experience for 17.1. You have to do it the old way, with the manifest pointing to the deprecated `android_prebuilts_prebuiltapks` repo rather than the `vendor_partner_gms` repo, and you need to list the Microg packages in the `CUSTOM_PACKAGES` variable. Even then it doesn't always work, and I haven't built for 17.1 for some time.

I hope all / some of that is helpful / useful, and happy to help out more if required (either here or by PM)

 

[7alvoo]

There is a small privilege revocation bug in version 18/19 of com.android.dialer. The first time you start a call recording it asks for approval which works fine but sometimes 'failed to start recording' which can be fixed by restarting the phone in safe mode and clearing the com.android.dialer cache and data - don't worry it doesn't clear the call log. The subject of the bug is that unfortunately sometimes you have to do this because 'failed to start recording' returns and only clearing in safe mode helps. Never had this in the 17 package the 18 one started I guess the automatic revocation of rights can interfere.