• 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

tramp20

Senior Member
Jan 15, 2012
739
139
Rosenheim
The patch is only needed for the first installation of Magisk until tjohnwu has changed his code (at least this bug is recognized/confirmed by him).
Updates to a newer build of Magisk are possible without problems.
 

115ek

Senior Member
Jan 30, 2017
564
632
F:\FastBoot>adb devices
List of devices attached
CB5A20MV00 device


F:\FastBoot>adb shell getprop lineage.updater.uri


F:\FastBoot>
That confirms my suspicion - the property isn't set and thus the update file can not be found.
You can set it with (Standard build)
Code:
adb shell setprop lineage.updater.uri https://raw.githubusercontent.com/lin17-microG/OTA/lineage-17.1/amami.json
or if you're on the microg build:
Code:
adb shell setprop lineage.updater.uri https://raw.githubusercontent.com/lin17-microG/OTA/lin-17.1-microG/amami.json

Afterwards an update should show up (of course not if you're already on the march version...).
Maybe the property is only read at startup by the updater app. I'm not sure about that. Then you would have to add this property to build.prop or default.prop and reboot the device.
 
Apr 30, 2016
6
0
HI all, hi @115ek

thanks for your ongoing effort in providing builds for our phone 🥳
I tried to build LOS 18.1 (for verification of the Unified-Patch) by myself with your repository and readme but run into the error "vendor/aicp/build/target/product/product_launched_with_j_mr2.mk" does not exist. You can see the whole error in the spoiler. I was able to fix it by copying from build/target/product/product_launched_with_j_mr2.mk to the requested position. That's the first error I wanted to report.
The second one: during searching for this problem I came across the old mentioned patch LOS-Patch 295701 in the readme. I guess it should either be LOS-Patch 305449 or could be removed completely from the readme as 305449 is already merged.

I was able to verify the Unified-Patch in the meantime so there is no need to hurry ;-)
@115ek As long as the VM is still set up with this massive amount of diskspace I could try to verify a fixed 18.1 build if you want to?

In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
vendor/sony/msm8974-common/msm8974-common-vendor.mk:16: error: _nic.PRODUCTS.[[device/sony/amami/lineage_amami.mk]]: "vendor/aicp/build/target/product/product_launched_with_j_mr2.mk" does not exist.
17:00:53 dumpvars failed with: exit status 1
Device amami not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_sony_amami
Default revision: lineage-18.1
Checking branch info
Default revision lineage-18.1 not found in android_device_sony_amami. Bailing.
Branches found:
cm-11.0
[...]
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
In file included from build/make/core/config.mk:291:
In file included from build/make/core/envsetup.mk:266:
vendor/sony/msm8974-common/msm8974-common-vendor.mk:16: error: _nic.PRODUCTS.[[device/sony/amami/lineage_amami.mk]]: "vendor/aicp/build/target/product/product_launched_with_j_mr2.mk" does not exist.
17:00:55 dumpvars failed with: exit status 1
 

tramp20

Senior Member
Jan 15, 2012
739
139
Rosenheim

Does not work on Z1c #1:
I get
F:\FastBoot>adb shell setprop lineage.updater.uri https://raw.githubusercontent.com/lin17-microG/OTA/lineage-17.1/amami.
json
setprop: failed to set property 'lineage.updater.uri' to 'https://raw.githubusercontent.com/lin17-microG/OTA/lineage-17.
1/amami.json'

On another Z1c #2 (both 17.1) I get a correct answer:
F:\FastBoot>adb shell getprop lineage.updater.uri

Should I get a correct answer (getprop) if I did a setprop before?

I will later try to change build.prop or default.prop.


Edit:
I forgot to update the ROM on #1, sorry.
The #2 was updated to the last ROM 29219309 and had the correct entry in build.prop.
 
Last edited:

115ek

Senior Member
Jan 30, 2017
564
632
I tried to build LOS 18.1 (for verification of the Unified-Patch) by myself with your repository and readme but run into the error "vendor/aicp/build/target/product/product_launched_with_j_mr2.mk" does not exist. You can see the whole error in the spoiler. I was able to fix it by copying from build/target/product/product_launched_with_j_mr2.mk to the requested position. That's the first error I wanted to report.
The second one: during searching for this problem I came across the old mentioned patch LOS-Patch 295701 in the readme. I guess it should either be LOS-Patch 305449 or could be removed completely from the readme as 305449 is already merged.

Yeah, I know this problem. I was to lazy to fix it yet. And I'm a bit surprised that someone actually builds from the sources and instructions. Nice.
Basically this problem arises as lineage and aicp store these makefiles in a different location. And as I use complete lineage sources with aicp device trees you'll end up there.
I didn't want to fork off the aicp devicetree yet. Fragmentation is always a bad thing.
I'm going to clean this up once I find some time.

And please directly post to the Lineage 18.1 thread next time, this is for 17.1 :)

Should I get a correct answer (getprop) if I did a setprop before?
Actually yes.

The #2 was updated to the last ROM 29219309 and had the correct entry in build.prop.
So
Code:
lineage.updater.uri
was correctly set in build.prop but nothing was returned by
Code:
getprop lineage.updater.uri
?
Which version is your other device on? Does setting the property makes you find updates again?
 

lm089

Senior Member
Jun 26, 2011
500
161
Munich
Does not work on Z1c #1:
I get
F:\FastBoot>adb shell setprop lineage.updater.uri https://raw.githubusercontent.com/lin17-microG/OTA/lineage-17.1/amami.
json
setprop: failed to set property 'lineage.updater.uri' to 'https://raw.githubusercontent.com/lin17-microG/OTA/lineage-17.
1/amami.json'

On another Z1c #2 (both 17.1) I get a correct answer:
F:\FastBoot>adb shell getprop lineage.updater.uri

Should I get a correct answer (getprop) if I did a setprop before?

I will later try to change build.prop or default.prop.


Edit:
I forgot to update the ROM on #1, sorry.
The #2 was updated to the last ROM 29219309 and had the correct entry in build.prop.
had the same "setprop: failed" message but it's working for me now.
What I did was get into shell then su then called setprop:

Code:
d:\Dev\platform-tools>adb shell
amami:/ $ su
amami:/ # setprop lineage.updater.uri https://raw.githubusercontent.com/lin17-microG/OTA/lineage-17.1/amami.json
amami:/ # getprop lineage.updater.uri
https://raw.githubusercontent.com/lin17-microG/OTA/lineage-17.1/amami.json
amami:/ # exit
amami:/ $ exit

back at the "DOS"-prompt checked getprop again, and now it's set:

Code:
d:\Dev\platform-tools>adb shell getprop lineage.updater.uri
https://raw.githubusercontent.com/lin17-microG/OTA/lineage-17.1/amami.json

d:\Dev\platform-tools>

As I'm still running the February build I could test the updater, and now it's showing the March build (y)

UPDATE:
oops, had forgotten to edit build.prop. But now the property apparently is persistent

UPDATE 2:
just to have this complete: after updating to the March build, Magisk was gone. I had taken a Nandroid of just the boot image so I could get it back that way
 
Last edited:

kejkla

Member
Oct 27, 2018
6
0
Hello is there a way to upgrade to this rom from LOS 16.0 13.12.2020 or do I have to make clean install? Sorry if it was already said here but if i try to search this thread it always just show "No results found."

Thanks
 
Hello is there a way to upgrade to this rom from LOS 16.0 13.12.2020 or do I have to make clean install? Sorry if it was already said here but if i try to search this thread it always just show "No results found."

Thanks
If you remain in the same build Variante and you come from the ROM of the predecessor thread of that one, you can update w/o wiping.
 
  • Like
Reactions: kejkla

traegr

Member
Sep 26, 2020
13
0
Hey y'all, I was vaguely aware that there are monthly updates for Lineage 17.1 and reaslized recently I haven't been getting updates. I checked the forum and saw there was a March release but mine is still on the January 14th build. When I try to refresh, it says 'no new updates found'.

I also found some things stopped working like the shake function to snooze (though I'm not sure if it's because I dropped my phone too many times (though vibration mode for notifications still works) and automatic backlight adjusment (I have to manually slide the brightness). These are not a big deal, but I do wonder about the lack of updates.

Thanks in advance
 
Last edited:
Ok thanks. I have normal variant. And how it is with gapps? Because its android 9 to android 10. Do I have to remove them before update and then install new ones?
You need to manually update your setup (standard variant plus Gapps) as follows:
  • Check the version of TWRP and upgrade your TWRP with the one linked in the OP, if needed
  • Place the ROM zip and the suitable Gapps zip (arm architecture, for Android 10, flavor of your choice, I recommend pico or nano) on your device (internal memory or external SD, as you wish)
  • Reboot to TWRP
  • Wipe the /system partition and also Cache & Dalvik
  • Flash the ROM zip and afterwards, without reboot, flash the Gapps zip
  • Reboot
 
  • Like
Reactions: kejkla
Hey y'all, I was vaguely aware that there are monthly updates for Lineage 17.1 and reaslized recently I haven't been getting updates. I checked the forum and saw there was a March release but mine is still on the January 14th build. When I try to refresh, it says 'no new updates found'.

I also found some things stopped working like the shake function to snooze (though I'm not sure if it's because I dropped my phone too many times (though vibration mode for notifications still works) and automatic backlight adjusment (I have to manually slide the brightness). These are not a big deal, but I do wonder about the lack of updates.

Thanks in advance
The January build, as already correctly mentioned in previous posts, had - for the standard build variant only - a wrong updater URI (to be more precise, the correct one hadn't yet been overlaid at that time). This means, that the January build for the standard variant will unfortunately not offer any OTA update, sorry. Please update manually by downloading the March build and flash with TWRP, no wipe necessary.
 
  • Like
Reactions: waterpolo

waterpolo

Senior Member
Aug 6, 2008
831
187
Naarden (NL)
The January build, as already correctly mentioned in previous posts, had - for the standard build variant only - a wrong updater URI (to be more precise, the correct one hadn't yet been overlaid at that time). This means, that the January build for the standard variant will unfortunately not offer any OTA update, sorry. Please update manually by downloading the March build and flash with TWRP, no wipe necessary.
Thanks for the explanation.
 

DeadXperiance

Senior Member
Jun 4, 2014
395
109
Mehsana
I am on latest build with nano Gapps.How to enable any app in full screen.{hide status bar}?
Because of an app doesn't work with status bar shown. I can't search in setting to enable full screen mode.
 
Regarding the MicroG build: The included Aurora Store is outdated, any plans to include the new Aurora Store version into the next build ? ;)
Yes, next build will have AuroraStore 4.0.2 with AuroraServices 1.1.0

EDIT: If you can't wait (Aurora 3.2.9 is almost nonfunctional), download the apk file from here and update manually. But in that case, you have to use "unknown sources" and you should, before updating the ROM, freeze/unfreeze Aurora to undo the update first.
 
Last edited:
  • Like
Reactions: 2faraway2
New builds with April 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-04-05
  • System Webview on 89.0.4389.105

B. Pre-installed microG build variant with additional security patches
  • Security String 2021-04-05
  • 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

@115ek - please update OP/Changelog

Regards, M.
 

115ek

Senior Member
Jan 30, 2017
564
632
By the way: There were some further fixes in lineage worth to be mentioned:
  • Photos can be saved to /DCIM folder on the sdcard again
  • Music title sorting has been fixed (there were problems with sorting with more than 9 tracks per album in some cases)
  • Trebuchet launcher now supports icon packs
  • some more stuff
You can read more about it here: https://lineageos.org/Changelog-25/
 

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.
    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
    1
    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.
  • 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