• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM][Unofficial][10.0][signed][OTA] Lineage OS 17.1 for Xperia Z1 compact

Search This thread

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Still now, after having pressed "refresh"?
Alright, now it came back to me; had confused the situation with another issue I recently had with my Xperia tablet. So let me recap the current situation with my Z1c:

Device is still running the January build; updater keeps telling me that there aren't any updates, no matter how often I press "refresh"

flashing one of the recent updates (February or March) from twrp both result in this behaviour:
  • after installing in twrp choose "boot to system"
  • LOS boot animation appears and runs for an exceptionally long time (feels like 3 - 5 minutes)
  • then still in the animation screen goes black, then SONY logo appears
  • no boot animation now, but reboot to TWRP
What I tried so far to solve this:
  • from the working January build I created a simple backup of just the boot partition; after trying to flash a newer build, and then back in twrp I restore just that boot image ==> does not help
  • before flashing the update build uninstall Magisk (V 21.4) from TWRP, then flash the update ==> down't help either
So at the moment it looks like I'm stuck at the January build.

Apart from doing a complete wipe then trying a new setup: any idea what I could try to solve this?
 
Alright, now it came back to me; had confused the situation with another issue I recently had with my Xperia tablet. So let me recap the current situation with my Z1c:

Device is still running the January build; updater keeps telling me that there aren't any updates, no matter how often I press "refresh"

flashing one of the recent updates (February or March) from twrp both result in this behaviour:
  • after installing in twrp choose "boot to system"
  • LOS boot animation appears and runs for an exceptionally long time (feels like 3 - 5 minutes)
  • then still in the animation screen goes black, then SONY logo appears
  • no boot animation now, but reboot to TWRP
What I tried so far to solve this:
  • from the working January build I created a simple backup of just the boot partition; after trying to flash a newer build, and then back in twrp I restore just that boot image ==> does not help
  • before flashing the update build uninstall Magisk (V 21.4) from TWRP, then flash the update ==> down't help either
So at the moment it looks like I'm stuck at the January build.

Apart from doing a complete wipe then trying a new setup: any idea what I could try to solve this?
In regards to the "Updater does not show any updates" issue:
If you go to Settings - About Phone - Android Version : What is the exact value shown at 'LineageOS-Version' ?

In regards to the issues to flash via TWRP, please try the following:
  1. Make a full backup and copy / store it to a different place than Internal memory (you may need it later!)
  2. Next, use the option "Fix SELinux contexts" in the "Extended" menu, reboot to system (just to see, whether it boots normally), and reboot again into TWRP. If you end up in a bootloop, proceed with step 4.
  3. Now try to flash the update again.
  4. If unsuccessful, make a backup of your internal memory, too
  5. format the /data partition and reboot to recovery. /That's why you must make a backup of Internal memory!)
  6. If your device has been encrypted before, don't restore anything, but just flash the January build again, reboot and encrypt the device again.
  7. Reboot to recovery, restore your full backup and restore your internal memory.
  8. Reboot to system and verify, that all is fine.
  9. Reboot to recovery and flash the update.
 
  • Like
Reactions: lm089
Before I begin, just to be sure: with "internal Memory you reference the /data partition, correct?
Not exactly.
I mean the portion of it, which is visible to your apps, and appears, when you connect your phone via USB and allow file transfer.
Or in other words, that part you can see in a non-root file explorer app like the shipped file browser.
Also often referred to as "internal SD" card, the target of the symlink /sdcard.
That part, which is skipped, when you do a full backup in TWRP.
 
  • Like
Reactions: lm089

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Hmm, ok - could you please do another thing?
Connect to the phone with a root terminal (either via adb or in TWRP with mounted /system partition, whatever) and give me the output of the command grep UNOFFICIAL /system/build.prop
Code:
amami:/ $ su
amami:/ # grep UNOFFICIAL /system/build.prop
ro.lineage.version=17.1-20210114-UNOFFICIAL-signed-amami
ro.lineage.releasetype=UNOFFICIAL-signed
ro.modversion=17.1-20210114-UNOFFICIAL-signed-amami
 
  • Like
Reactions: MSe1969
Code:
amami:/ $ su
amami:/ # grep UNOFFICIAL /system/build.prop
ro.lineage.version=17.1-20210114-UNOFFICIAL-signed-amami
ro.lineage.releasetype=UNOFFICIAL-signed
ro.modversion=17.1-20210114-UNOFFICIAL-signed-amami
Thanks - hmm, ok, then I really don't have a good explanation, why the Updater does not show you the update...
@115ek - maybe I am blind, but I have verified each entry of the amami.json file already. Maybe you see something, which I have overlooked?
 

lm089

Senior Member
Jun 26, 2011
500
161
Munich
In regards to the issues to flash via TWRP, please try the following:
  1. Make a full backup and copy / store it to a different place than Internal memory (you may need it later!)
  2. Next, use the option "Fix SELinux contexts" in the "Extended" menu, reboot to system (just to see, whether it boots normally), and reboot again into TWRP. If you end up in a bootloop, proceed with step 4.
  3. Now try to flash the update again.
  4. If unsuccessful, make a backup of your internal memory, too
  5. format the /data partition and reboot to recovery. /That's why you must make a backup of Internal memory!)
  6. If your device has been encrypted before, don't restore anything, but just flash the January build again, reboot and encrypt the device again.
  7. Reboot to recovery, restore your full backup and restore your internal memory.
  8. Reboot to system and verify, that all is fine.
  9. Reboot to recovery and flash the update.
Unfortunately didn't work. Performed all steps, skipping #6 as the device is not encrypted.
There's only one difference to the situation before:
before the device stopped booting after ~5 minutes into the boot animation. After performing step #2 (SE Linux fix) the boot animation apparently now goes on forever; I forced stopping boot up after ~10 minutes.
Meanwhile I'm back up @ the January build.
Before I go ahead and do a complete clean installation: any more ideas what I could try to do?
 
Meanwhile I'm back up @ the January build.
Before I go ahead and do a complete clean installation: any more ideas what I could try to do?
I had a funny situation once with a different device (S2 tablet):
I had to re-enter TWRP and manually wipe cache and dalvik and afterwards it booted ok. Maybe worth a try?
 
  • Like
Reactions: lm089

lm089

Senior Member
Jun 26, 2011
500
161
Munich
I had a funny situation once with a different device (S2 tablet):
I had to re-enter TWRP and manually wipe cache and dalvik and afterwards it booted ok. Maybe worth a try
Had that too several times in the past. So I tried that already.
Never mind if this can't be solved remotely; this is my secondary device with just a few apps installed, and I use Titanium to backup my data.
 

115ek

Senior Member
Jan 30, 2017
564
632
Maybe something was messed up with the ro.lineage.releasetype :unsure:

I'm going to check that on my side if I get some time (most likely at the weekend).
@lm089 could you get a log after searching for updates?
Code:
adb logcat -b all > logcat.txt

Else a quick and dirty solution would be flashing manually. But you told that you ended up in a bootloop, right? That's strange, though.

Is anyone here who did a successful update to the march version - on microg or standard build?
 

waterpolo

Senior Member
Aug 6, 2008
831
187
Naarden (NL)
Maybe something was messed up with the ro.lineage.releasetype :unsure:

I'm going to check that on my side if I get some time (most likely at the weekend).
@lm089 could you get a log after searching for updates?
Code:
adb logcat -b all > logcat.txt

Else a quick and dirty solution would be flashing manually. But you told that you ended up in a bootloop, right? That's strange, though.

Is anyone here who did a successful update to the march version - on microg or standard build?
Dirty flash in TWRP was working for me, but I can't for some reason Magisk working. I restore the boot.img from january and then everything working smooth. I haven't see any bootloop.
 

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Maybe something was messed up with the ro.lineage.releasetype :unsure:

I'm going to check that on my side if I get some time (most likely at the weekend).
@lm089 could you get a log after searching for updates?
Code:
adb logcat -b all > logcat.txt

Else a quick and dirty solution would be flashing manually. But you told that you ended up in a bootloop, right? That's strange, though.

Is anyone here who did a successful update to the march version - on microg or standard build?
here's the log file just before I reset and clean flash my Z1c:

UPDATE: well I tried, but upload's not working (from PC). OK to send it via PM? Or other preferences?

UPDATE 2: last attempt, this time using Chrome instead of Firefox...

UPDATE 3: still not working; see PM please
 
Last edited:

115ek

Senior Member
Jan 30, 2017
564
632
Could you check if it finds updates when you set SE linux to permissive by
Code:
setenforce 0

You need to be root for this, of course.
Enable root over adb in developer options for example and then use
Code:
adb root && adb shell setenforce 0

EDIT: I don't think that matters here. Please see below.
 
Last edited:

115ek

Senior Member
Jan 30, 2017
564
632
@MSe1969
By seeing the following line in the log @lm089 supplied I'm pretty sure it's related to lineage.updater.uri
Code:
03-16 14:03:28.821  7062  7062 D UpdatesActivity: Checking https://download.lineageos.org/api/v1/amami/unofficial-signed/eng.androi.20210114.180500

Could you check that?

EDIT: Can someone share the output of
Code:
adb shell getprop lineage.updater.uri

It should be If it's not, that causes the update problems.
 
Last edited:

tramp20

Senior Member
Jan 15, 2012
739
139
Rosenheim
@All
All who are not able to install Magisk 22.x in LOS 17.1 or 18.1 (installing the magisk-v22.0.zip with TWRP) should read this thread (started by me):
https://github.com/topjohnwu/Magisk/issues/3636
especially the last postings from bleckdeth.

Patching the boot.img for our old Z1c is no longer necessary.
Only a simple patch in the magisk-v22.x.zip is necessary. I did it already several times in LOS 17.1 and 18.1 to help testing.
I hope that will survive the next OTA too (if it will come).
 
  • Like
Reactions: lm089

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Maybe something was messed up with the ro.lineage.releasetype :unsure:

I'm going to check that on my side if I get some time (most likely at the weekend).
@lm089 could you get a log after searching for updates?
Code:
adb logcat -b all > logcat.txt

Else a quick and dirty solution would be flashing manually. But you told that you ended up in a bootloop, right? That's strange, though.

Is anyone here who did a successful update to the march version - on microg or standard build?
Ok, I just did a complete fresh and clean install of the February build because I wanted to check the updater. Result: no update found.
@All
All who are not able to install Magisk 22.x in LOS 17.1 or 18.1 (installing the magisk-v22.0.zip with TWRP) should read this thread (started by me):
https://github.com/topjohnwu/Magisk/issues/3636
especially the last postings from bleckdeth.

Patching the boot.img for our old Z1c is no longer necessary.
Only a simple patch in the magisk-v22.x.zip is necessary. I did it already several times in LOS 17.1 and 18.1 to help testing.
I hope that will survive the next OTA too (if it will come).
Thanks for hinting; you might remember that I had that problem, too. Now with the newly encountered bootloop after updating this LOS zu the latest builds I decided to do a complete fresh/clean install of my Z1c. Because I had fully working backups I dared to also install Magisk V22 - and it's working now. So at least in my case I assume that over the years my device had gotten "dirty" somehow, and that I have a "clean" setup now.
On the other hand, after reading your linked github discussion I wonder however whether that is probably only temporary? I'll keep an eye on this
 

tramp20

Senior Member
Jan 15, 2012
739
139
Rosenheim
Ok, I just did a complete fresh and clean install of the February build because I wanted to check the updater. Result: no update found.

Thanks for hinting; you might remember that I had that problem, too. Now with the newly encountered bootloop after updating this LOS zu the latest builds I decided to do a complete fresh/clean install of my Z1c. Because I had fully working backups I dared to also install Magisk V22 - and it's working now. So at least in my case I assume that over the years my device had gotten "dirty" somehow, and that I have a "clean" setup now.
On the other hand, after reading your linked github discussion I wonder however whether that is probably only temporary? I'll keep an eye on this
 

Top Liked Posts

  • There are no posts matching your filters.
  • 8
    New builds with July 2021 ASB patches available

    Hi all,
    new builds are available and already offered as OTA updates via the updater app.


    A. Standard LineageOS 17.1 build
    • Security String 2021-07-05
    • System Webview updated to 91.0.4472.101
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-07-05
    • Bromite System Webview and Browser updated to 91.0.4472.146
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • microG 0.2.21.212158-2
    • AuroraStore 4.0.7

    @115ek - please update OP/Changelog

    Regards, M.
    2
    Just installed it yesterday, everything is great. This ROM has LDAC support if anyone's wondering. Even Stock doesn't support LDAC. Thanks again.
    2
    LineageOS 18.1 "microG Variant" Testbuild

    Hi all,

    for the 2nd build variant ("microG build"), a test build on LineageOS 18.1 is available here:

    It has the same features, as described in the OP for this 17.1 build variant, with the following additions:
    - AuroraDroid app replaces F-Droid app to access F-Droid repositories
    - Option to only use fingerprint unlock for apps and not for the device
    - Optional timeout for Bluetooth and WLAN connections
    - Some more hardening features ported from GrapheneOS

    @115ek and I plan to switch completely to LineageOS 18.1 for both build variants (variant A is already available for LineageOS 18.1, as you for sure know). Right now, this is still a test build, this means we truly appreciate any feedback (especially, if things don't work as expected). And there definitely will be an update with ASB patches for August for both 17.1 build variants.

    Installation instructions:
    • Make a backup in TWRP

    • If your device is not encrypted, it is up to you whether you want to do a clean or dirty flash
    • Do or don't do a factory reset and flash the test build

    • If your device is encrypted, encryption is not compatible! It will be necessary to format the /data partition.
    • If you need to format the /data partition, make sure to before:
      - Backup the 'Internal memory' of your device
      - Watch out for your TWRP backup files and copy them, if needed, to your local PC
    • Format /data, reboot into TWRP and flash the above test build build and boot into an empty system (don't restore anything,yet)
    • Encrypt the device now - it'll take not very long until the device reboots - wait for the reboot to finish
    • Restore now the Internal Memory and reboot to TWRP
    • if you want to "dirty-flash", restore the nandroid backup now and afterwards, still in TWRP,
    • Flash the above test build again
    Feedback appreciated - Thanks & regards, M.
    1
    • Kernel: Many sec. patches applied

    Awesome to see my CVE patcher used more!
    You might want to give it another run, I did a huge addition for 3.4 recently from @haggertk's 3.4 backports.

    You might also put the patches on an another branch, as patch output can change/improve overtime and it'll be easier to maintain that way.
    1
    I did already apply before Kevin's 3.4 backports from his LineageOS Samsung msm8974 branch and for the recent patching action with this ROM's Sony msm8974 kernel, I used the patches listed in here as this is also a msm8974 kernel in your 17.1 directory.
    Do you recommend to me to look further?

    And by the way, whilst I have the opportunity to communicate with you:
    As I prefer to truly apply the commits to my/our kernel forks, I have noticed, that few of your patches do not contain commit messages. For some of them, I found them and applied accordingly, but at least for that one I did not manage to find it.
    Do you have the commit message(s) handy?
    And if not - would you like me to make a pull request for those patches, where I was able to identify the originating upstream commit?

    > I used the patches listed in here

    The program is intended to be used to check which patches apply.

    > I have noticed, that few of your patches do not contain commit messages.

    Many of them are plain diffs due to various reasons, eg. Gerrit only gives base64'ed plain diff
    I'm happy to accept patches that replace diffs with matching patches.

    > but at least for that one

    That is https://lkml.org/lkml/2017/10/2/352

    --

    In case it isn't clear, patches are added to this file first https://raw.githubusercontent.com/Divested-Mobile/Kernel_Patches/master/Kernel_CVE_Patch_List.txt

    then downloaded with the program https://github.com/Divested-Mobile/CVE_Checker

    and also checked using the program

    you can use https://github.com/Divested-Mobile/CVE_Checker/blob/master/mk_dir_from_list.sh to convert the program output to a directory of the patches

    you can download prebuilts of the program here https://gitlab.com/divested-mobile/cve_checker/-/jobs/artifacts/master/browse?job=build

    furthermore a large amount of the patches in the list are extracted using this tool https://gitlab.com/cip-project/cip-kernel/cip-kernel-sec, you can add any kernel you want to the script config and extract matching patches from any given repository, and propagate that back into the final patch list


    edit: here is example output https://github.com/SkewedZeppelin/android_kernel_sony_msm8974/commits/fixup it contains an additional ~60 patches
  • 19
    This thread aims at providing LineageOS 17.1 builds for the Sony Xperia Z1 compact with current security patches.
    You can consider this thread as a successor of our LineageOS 16.0 thread, where you may also find some useful information.
    This is the joint effort of 115ek and MSe1969 (contributions welcome).

    Code:
    #include <std_disclaimer.h>
    /*
    * Your warranty is now void.
    *
    * We are 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 us for messing up your device, we will laugh at you. Hard & a lot.
    *
    */

    We offer two build variants:
    A. Standard LineageOS 17.1 build
    This build flavor aims at providing LineageOS 17.1 "as is" with most recent security patches.
    If you want to install Google Apps (GApps) you have to use this build variant.
    GApps are optional, of course. The smaller the GApps package, the better (pico). If you want "Okay google" support you need at least nano.
    Just check the package comparison to see what fits your needs.

    B. Pre-installed microG build variant with additional security patches
    For the security/privacy focused (more details about below feature list, see here)
    • Pre-installed microG and F-Droid same as the LineageOS for microG project
    • Pre-installed AuroraStore
    • eSpeak TTS engine (FOSS TTS solution)
    • Bromite as default browser
    • Additional security hardening features listed below
    • Cloudflare as default fallback DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
    • Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
    • Increased max. password length of 64
    • No submission of IMSI/phone number to Google/Sony when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView
    • Extra control of sensor access for additionally installed user apps (Special access under app permissions)
    • Firewall (control internet access per app - under Trust)
    • Constified JNI method tables


    Status
    List template by AdrianDC
    Code:
    - Partitions (Data, Cache) : Ext4 and F2FS supported
    - Bluetooth : Ok
    - WiFi : Ok
    - WiFi Hotspot : Ok
    - RIL - Phone - Data : Ok
    - GPS : Ok
    - Camera : Ok
    - Camcorder : Ok
    - Lights : Ok
    - MicroSD : Ok
    - Accelerometer : Ok
    - Compass : Ok
    - Gyroscope : Ok
    - Touchscreen : Ok
    - FM Radio : Ok (mono)
    - ANT+ : Ok
    - Vibrator : Ok
    - Microphone : Ok
    - Audio & music : Ok
    - Bluetooth audio : Ok
    - MHL: broken
    - NFC : Ok
    - Kernel : Ok
    - Graphics : Ok
    - 3D Rendering : Ok
    - Clock : Ok
    - Offline Charging : Ok
    - USB : Ok
    - USB OTG : Ok
    - Encryption : Ok
    - SEPolicies : enforcing
    Limitations
    Following limitations are known:
    • NFC-HCE does not work (needed for example for google pay)
    • FM does not work in stereo mode (mono works fine, though)
    • MHL does not work
    • 5 GHz hotspot does not work (2.4 GHz hotspot works fine) (5 GHz option disabled with 2020-03-11 build as it isn't even available on stock)
    • GPS gets wrong time due to GPS week rollover since 3rd November 2019 (of importance when you record GPS tracks for example). fixed with 20200520 build
    • Using GApps AND encrypting the device may result in bootloops. More infos here.
    • Standard Trebuchet Launcher shows small artifacts in the fonts of app names in some situations.
    Download
    FAQ
    What recovery system to use?
    Please use this TWRP if you want to use OTA updates and/or encryption.

    What about root access?
    Root isn't included per default (except root over adb, but it's off by default).
    If you want to gain root access to your apps use magisk (everything > 20.4 is broken):
    ANT+ isn't working?
    You need the 2 apps:
    afterwards setting proper permissions is essential!
    1. Go to Apps & Notifications -> See All Apps
    2. Select 'ANT Radio Service'
    3. Select Permissions
    4. Select Additional permissions
    5. Slide switch to allow using of ANT hardware
    This refers to those instructions which worked for me :)
    I've got problems AND have magisk/exposed installed
    We won't support anything related to magisk/exposed/other heavily system modifying things.
    If you're encountering problems please make sure you're using a clean installation (at most gapps) to verify/reproduce the issue.

    Bugreports
    You'll find information about logging here.
    Please also note how you got the error or how it can be reproduced.
    Sources
    Credits
    • SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
    • NeoArian: also big thanks to him ;)
    • rcstar6696
    • SuperLamic
    • drakonizer
    • AdrianDC
    • munjeni: thanks for tips and tricks
    • nailyk: thanks for tips and tricks
    • All the other contributors on sony msm8974 platform
    • LineageOS team

    Installation instructions


    XDA:DevDB Information
    Lineage OS 17.1 for Xperia Z1 compact - amami, ROM for the Sony Xperia Z1 Compact

    Contributors

    115ek, MSe1969, SpiritCroc, NeoArian, drakonizer, rcstar6696, SuperLamic, AdrianDC, nailyk, LineageOS team
    Source Code: https://github.com/lin17-microg/local_manifests

    ROM OS Version: Android 10
    ROM Kernel: Linux 3.4.x

    Version Information
    Status:
    Stable
    Stable Release Date: 2020-12-29

    Created 2019-11-22
    Last Updated 2021-07-10
    8
    New builds with July 2021 ASB patches available

    Hi all,
    new builds are available and already offered as OTA updates via the updater app.


    A. Standard LineageOS 17.1 build
    • Security String 2021-07-05
    • System Webview updated to 91.0.4472.101
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-07-05
    • Bromite System Webview and Browser updated to 91.0.4472.146
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • microG 0.2.21.212158-2
    • AuroraStore 4.0.7

    @115ek - please update OP/Changelog

    Regards, M.
    8
    New builds with May 2021 ASB patches available

    Hi all,
    new builds are available and offered as OTA updates via the updater app.

    A. Standard LineageOS 17.1 build
    • Security String 2021-05-05
    • System Webview on 90.0.4430.82

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-05-05
    • Bromite System webview updated to 90.0.4430.204
    • Bromite Browser updated to 90.0.4430.204
    • microG upstreamed (but no new version)
    • Update: AuroraServices 1.1.1

    @115ek - please update OP/Changelog

    Regards, M.
    7
    New builds with March 2021 ASB patches available

    Hi all, new builds are available and offered as OTA updates via the updater app.

    A. Standard LineageOS 17.1 build
    • Security String 2021-03-05
    • System Webview on 88.0.4324.152

    B. Pre-installed microG build variant with additional security patches
    • Security String 2021-03-05
    • Bromite System webview updated to 88.0.4324.207
    • Bromite Browser updated to 88.0.4324.207
    • F-Droid 1.11
    • microG 0.2.18.204714

    @115ek - please update OP/Changelog

    Regards, M.
    6
    Changelog

    10.07.2021

    • ASB Security string 2021-07-05
    • Kernel: Many sec. patches applied (taken from Divest-OS, thanks to @SkewedZeppelin)
    • standard build only:
      • System Webview on 91.0.4472.101
    • microG build only:
      • Bromite System Webview and Browser updated to 91.0.4472.146
      • microG 0.2.21.212158-2
      • AuroraStore 4.0.7
    14.06.2021
    • ASB Security string 2021-06-05
    • A few kernel patches
    • microG build only:
      • Bromite System Webview and Browser updated to 91.0.4472.102
      • Upstreamed microG (0.2.19211515-9)
    12.05.2021
    • ASB Security string 2021-05-05
    • standard build only:
      • System Webview on 90.0.4430.82
    • microG build only:
      • Bromite System webview updated to 90.0.4430.204
      • Bromite Browser updated to 90.0.4430.204
      • microG upstreamed (but no new version)
      • Update: AuroraServices 1.1.1
    11.04.2021
    • ASB Security string 2021-04-05
    • standard build only:
      • System Webview on 89.0.4389.105
    • microG build only:
      • Bromite System webview updated to 90.0.4430.59
      • Bromite Browser updated to 90.0.4430.59
      • F-Droid 1.12
      • Update: AuroraStore 4.0.4 with AuroraServices 1.1.0
    09.03.2021
    • ASB Security string 2021-03-05
    • standard build only:
      • System Webview on 88.0.4324.152
    • microG build only:
      • Bromite System webview updated to 88.0.4324.207
      • Bromite Browser updated to 88.0.4324.207
      • F-Droid 1.11
      • microG 0.2.18.204714
    07.02.2021
    • ASB Security string 2021-02-05
    • misc. kernel patches
    • microG build only:
      • Bromite System webview updated to 88.0.4324.141
      • Bromite Browser updated to 88.0.4324.141
      • F-Droid 1.10-alpha-234
      • microG 0.2.17.204714-5
    14.01.2021
    • ASB Security string 2021-01-01
    • standard build only:
      • Kernel slightly upstreamed
      • System Webview: Fix of persistent histogram bug (eating space in some cases)
    • microG build only:
      • Bromite Webview on 87.0.4280.131
      • Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
      • Updated F-Droid to 1.10-alpha1-212
    29.12.2020
    • introduce microG build variant (see this post or the OP for more information)
    18.12.2020
    • synced LineageOS sources (security patch level December 05, 2020)
    08.11.2020
    • synced LineageOS sources (security patch level November 05, 2020)
    • Seedvault is included officially now (inbuilt backup solution)
    07.10.2020
    • synced LineageOS sources (security patch level October 05, 2020)
    13.09.2020
    • synced LineageOS sources (security patch level September 05, 2020)
    17.08.2020
    • synced LineageOS sources (security patch level August 05, 2020)
    13.07.2020
    • synced LineageOS sources (security patch level July 05, 2020)
    16.06.2020
    • further GPS improvements
    • synced LineageOS sources (security patch level June 05, 2020)
    20.05.2020
    11.05.2020
    • synced LineageOS sources (security patch level May 05, 2020)
    16.04.2020
    • synced LineageOS sources (security patch level April 05, 2020)
    15.03.2020
    • fixed livedisplay
    • fixed OTA update URL
    11.03.2020
    • remove 5GHz hotspot option as it isn't available even on stock
    • start signing builds
    • enable OTA updates
    • synced LineageOS sources (security patch level March 05, 2020)
    28.02.2020
    • fixed sony bootlogo
    • fixed TWRP time bug
    25.02.2020
    • fixed buggy bootanimation
    11.02.2020
    • DRM fix (Netflix and co should work now)
    • synced LineageOS sources (security patch level February 05, 2020)
    01.02.2020
    • SE enforcing
    • synced LineageOS sources (security patch level January 01, 2020)
    22.11.2019
    • initial release