• 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

EOL [ROM][Unofficial][8.1.0][signed][OTA] LineageOS 15.1 for Xperia Z1 compact

Status
Not open for further replies.
Search This thread

Hackmann

Member
May 8, 2007
20
2
Gapps: There are two build variants, the standard one and the microG one. And whilst you can think about Gapps for the standard one, this is a No-Go for the microG variant. I will however add a phrase like "For the standard variant, the following applies:" after the "Don't flash Gapps on microG variant."
As i understand it, GApps, in all its variants (pico, nano, micro, mini, etc), and MicroG are something entirely different. I'm not sure which i would call the "standard" one, they are simply two different options and i would be quite happy if other maintainers would offer the option with a "security hardened MicroG".
One necessary step to be able to use OTA updates from within the ROM is to update the TWRP recovery by installing TWRP 3.2.3-1 for amami.
IMPORTANT: BEFORE UPDATING TWRP, MAKE A 'NANDROID' BACKUP IN TWRP! - The first TWRP launch after updating TWRP will most probably perform a factory reset!
I've updated to this version a few weeks ago from within TWRP and then flashed the August build. No factory reset and no other issues so far.
 
Last edited:
  • Like
Reactions: MSe1969
As i understand it, GApps, in all its variants (pico, nano, micro, mini, etc), and MicroG are something entirely different. I'm not sure which i would call the "standard" one, they are simply two different options and i would be quite happy if other maintainers would offer the option with a "security hardened MicroG".
I call the one "standard", because it corresponds to the scope of "official" LineageOS builds. On that one, you can (but don't have to) flash GApps, whatever flavor you like (pico, nano, bloated, fully bloated, or contaminated :) ) - the other one with MicroG is more "special", but I fully agree with you that it would be desirable, if this became more common.

I've updated to this version a few weeks ago from within TWRP and than flashed the August build. No factory reset and no other issues so far.
Good to know, thanks - this happened to me however on both of my Z1c devices, so I thought to better raise a clear warning.
 

Hackmann

Member
May 8, 2007
20
2
I can record 4k videos (not that i really need it), but when i use OpenCamera the Camera2 API seems to be missing. Is this normal?
I've read several threads about porting the original Sony noise reducing algorithms and other features, but they seem to be outdated. How much of those features have been incorporated in this build? Does it still makes sense to apply some of those mods on top of it and which one would be recommended for this build?
 

zoltaaaan

Member
Mar 10, 2019
12
3
I remember something from my cm-12.1- thread, maybe it is related - but not sure:
Could you please do the following? Connect your phone via 'adb' and enter a root shell, where you enter the following command:
Code:
cat /sys/devices/mdss_dsi_panel/panel_id
Please post the result.

I still have a problem, where my third party touchscreen freezes quite regularly. The display freezes, when mobile internet is enabled, but there is no signal or the signal is lost. It never unfreezes on it's own, you always have to switch it off with the red button.

Therefore, I tried to read this file to give you the info, but it says "Permission denied"

I am not quite sure how to enter a root shell. I tried the command
Code:
./adb.exe root
but there was no noticable reaction to that.
When I try to run
Code:
cat /sys/devices/mdss_dsi_panel/panel_id
I get the same result before and after the root command.
 
I still have a problem, where my third party touchscreen freezes quite regularly. The display freezes, when mobile internet is enabled, but there is no signal or the signal is lost. It never unfreezes on it's own, you always have to switch it off with the red button.

Therefore, I tried to read this file to give you the info, but it says "Permission denied"

I am not quite sure how to enter a root shell. I tried the command
Code:
./adb.exe root
but there was no noticable reaction to that.
When I try to run
Code:
cat /sys/devices/mdss_dsi_panel/panel_id
I get the same result before and after the root command.
Have you enabled root? (Developer settings)
'adb root' will only give you root when you have allowed it before.
 

JIJOK

Senior Member
Jun 24, 2015
144
21
cool, new update thanx !

ps : I know this is not the right place but no answer on the other side, Am I the only one who can't reboot to TWRP with latest magisk manager (224) ?
ps2 : only can boot with buttons
 

115ek

Senior Member
Jan 30, 2017
563
631
How do we know what one is being used?
Is it possible to switch between them easily?

It depends on the android version you used when encrypting the device.
The easiest way to switch would be taking a backup, formatting /data, restoring backup and encrypt with LOS 15 again.
However - encryption on our device isn't that safe as the bootloader is unlocked. Persons knowing what they do can brute force your key. Long keys help to keep them out for a bit longer...
Anyway: to prevent snoopy people from accessing your peronal data (or thiefs.. whatever) the encryption should be sufficient I think. So I'd always advise you to encrypt.
And always keep in mind: nothing is secure.
 
What if I don't remember?

---------- Post added at 05:30 PM ---------- Previous post was at 05:29 PM ----------



What if I don't remember? Is there a file or command that would say?

No idea - but I would not worry too much. Having a long password is more important than the Android release, which was used to encrypt the device.

If you insist on having the encryption with the latest Android version, do as advised by @115ek :
Make a nandroid backup with TWRP, backup your internal storage(!), format the /data partition (this will also wipe the internal storage, that's why you must back it up before), restore your backup and the internal storage and then encrypt again.

If you ask me, not worth the effort - rather get used to a longer, nontrivial password instead of a four-digit PIN, or even a pattern nonsense, that brings more security.
 

esemef

Senior Member
Aug 3, 2013
135
38
Latest standard build, it happens with every single url. It was happening with the previous build as well.

It started on 24th September. I updated to the latest to see if it fixed it but it did not.
 
Latest standard build, it happens with every single url. It was happening with the previous build as well.

It started on 24th September. I updated to the latest to see if it fixed it but it did not.
Is it only happening with the Browser app or all apps on the phone?

A couple of options to try:
- Boot into recovery and wipe cache & dalvik (that does never harm)
- If only the Browser app: Check the data usage option of the Browser app (Settings - Apps), to see, whether Internet access is still allowed, alternatively clear the Browser app data
- If all apps: Make a backup with TWRP and perform a factory reset to see whether it works again. If not - something is wrong with your device, if yes, you need to think about how to initialize your device (either start from scratch or restore your backup and do an individual backup of the apps of your choice with adb or titanium backup)
- I assume you do not use any custom kernel or fancy magisk or xposed modules?
 
  • Like
Reactions: marsa47
New builds with October ASB

Hi all,

new builds are available for download having the 2019-10-05 security string:

A. Standard LineageOS 15.1
https://www.androidfilehost.com/?fid=1899786940962608878
- System Webview on 77.0.3865.92

B. Security hardened microG build
https://www.androidfilehost.com/?fid=1899786940962608877
- Bromite Webview on 77.0.3865.104
- AuroraStore updated to 3.1.3

In the course of today, the updater app will propose you an OTA update accordingly (if you are at least on the respective August build of this ROM).

Regards, M.
 
  • Like
Reactions: jho55
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 18
    Thread Closed Per OP Request

    This thread is dedicated to provide Lineage-OS 15.1 builds for the Sony Xperia Z1 compact with current security patches.
    This thread is discontinued - please visit the LineageOS 16.0 successor thread

    This is the joint effort of 115ek and MSe1969 (contributions welcome).
    There are two build flavors available, both are signed (see further below):

    A. Standard LineageOS 15.1
    This build flavor aims at providing LineageOS 15.1 "as is" with most recent security patches.
    Consider this flavor as continuation of the thread here by 115ek.
    Download here

    B. Security hardened microG build
    For the security/privacy focused
    Download here
    • Pre-installed microG and F-Droid same as the LineageOS for microG project
    • Pre-installed AuroraStore
      [*]Pre-Installed pre-release of microG DroidGuard helper to have a working SafetyNet attestation (see comments below!)
    • Additional security hardening features listed below
    • Access to /proc/net blocked for user apps
    • Bundled netmonitor app to allow network monitoring
    • Enhanced Privacy Guard: Switches for motion sensors, other sensors and certain background activities
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking
    • Optional disable captive portal detection
    • Option to set own DNS
    • Option to deny new USB connections
    • 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
    • Additional restriction options for secondary users

    Current release levels
    Security string: 2020-02-05
    AOSP tag: 8.1.0_r52
    System Webview: M79 (Standard build)
    Bromite Webview: M79 (microG build)


    Source-code and build instructions
    Kernel: https://github.com/lin15-microG/kernel_sony_msm8974/tree/lineage-15.1
    Build manifest: https://github.com/lin15-microG/local_manifests

    TWRP Recovery
    Please use the TWRP recovery referred to in this thread

    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)
    • Problems with some 5 GHz Wifi channels (can be avoided by not using autochanneling) fixed with 20190408 build
    • MHL does not work
    • 5 GHz hotspot does not work (2.4 GHz hotspot works fine)

    Installation Instructions

    YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!

    Please note - we won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty information available.

    Pre-Requisites
    • Get familiar with the hardware keys of the Xperia Z1 compact device, especially how to enter fastboot mode and recovery mode
    • Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
    • Download the most current .ZIP file of our ROM and place it to your phone's internal memory or SD card
    • Only valid for the "standard build flavor": If you wish to install Google apps (GApps), please refer to the GApps section further below
    • An unlocked bootloader (read the warnings carefully and backup your data!)
    • Only in case your device is still with the pre-delivered Sony Stock ROM: It is recommended that you have updated the Stock ROM to the latest version offered by Sony to make sure that the bootloader has the needed capabilities (see also 'trouble-shooting' below)

    Install TWRP recovery
    If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. If you have already a working custom recovery on your device, there is no necessity to replace it. However - we recommend to use the TWRP recovery linked in this thread. The following instructions are based on TWRP.
    To install TWRP, download the TWRP.img file (Note: replace "TWRP.img" in the following instructions with the real file name) from this section to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
    Code:
    fastboot flash FOTAKernel TWRP.img
    Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and use the right hardware keys to get into recovery mode) - we recommend not to boot the phone's Android system after having flashed TWRP. Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP should be TWRP in recovery mode.
    Trouble-shooting:
    Depending on the Stock ROM you are on, you may face some difficulties to get the phone into recovery after flashing TWRP. If you are facing such difficulties (i.e. phone always boots into Stock ROM), get into fastboot mode, and manually boot into TWRP by entering the below command:
    Code:
    fastboot boot TWRP.img
    If that also does not help you, it could be that the firmware, you have previously used, included an outdated bootloader. In that case, use the Sony flash tool (Windows only) or Androxyde's Open source flshtool to flash a more current Sony firmware image.
    Both approaches can also help to "unbrick" your device.

    Advanced Wipe
    ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM!
    Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and spefify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory" or "SD Card". Swipe to confirm the deletion and get back into the main menu.

    GApps
    DO NOT attempt to flash GApps on the "microG" build variant!
    For the "Standard" variant, the following applies:
    You do not need to install GApps, but you may wish to do so. In that case, download GApps from here and put the .ZIP also to the SD card or Internal memory of your device. Choose ARM as platform, Android 8.1 and the flavor of your choice. We recommend "pico", as this leaves you the most freedom to only install, what you really need; you can later still install all the Google products you want and do not need to live with pre-installed Google applications you have no use for.

    Install our ROM
    In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard) or your SD card (path /external_sd). Choose the .ZIP file of our ROM and swipe to flash.
    If you update from a previous version of our ROM, you don't need to perform a wipe. If you had GApps already installed before the update, there is no need to flash them again. They will be automatically restored during the flash process. (Note: If you wish to get rid of GApps, navigate to TWRP's file manager in the Advanced section of the main menu, go to path /system/addon.d and delete the file 70-gapps.sh, before flashing the ROM update)
    If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. If you wish to install GApps, select the respective .ZIP file directly afterwards, do not boot into Android before having flashed GApps.
    When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into our Lineage OS 15.1 - be patient, the first boot after flashing a new ROM takes quite long!

    microG
    Only valid for the "microG" build variant: After the first installation of this ROM, you need to setup microG.
    Please read the instructions given on the LineageOS for microG site, section "Post Install - UnifiedNlp"


    Encryption
    Encryption works, however - please consider the below important information:

    • If you have previously encrypted your device with a "Lollipop" (Android 5.x) based ROM (e.g. this one), our ROM unfortunately cannot decrypt and you will have to format the data partition and encrypt again. Be aware, that your 'Internal Memory' will be lost in that case, so don't forget to make a backup!
    • If the device has been encrypted with a "Nougat" (Android 7.x) based ROM, there won't be any issues, even if you switch between different Android releases including Android 8.x and 5.x for testing purposes
    • If you encrypt the device with our LineageOS 15.1 ROM, you will not be able to decrypt the /data partition with TWRP and have to 'sideload' any updates instead
    We consider this as a still open issue. We will be grateful for any advice on how to solve these compatibility issues.
    For the time being, it seems that flashing a naked Nougat-ROM (e.g. this one) to perform the encryption and then wipe and install LineageOS 15.1 will leave you with the most flexibility.


    Dealing with signed builds
    Please note, that our builds are signed with our own key. When you come from a different build, you cannot directly "dirty-flash" our build. You either have to perform a "clean flash" (recommended), or - if you e.g. would like to update from one of 115ek's previous builds, you need to follow below instructions.

    Coming from 115ek's Lineage 15.1 build:
    • Download and extract the file migration.sh from this archive
    • boot into TWRP
    • push the migration.sh file to the directory /data/local on your device and mount the /system partition in TWRP (you can do so using the dedicated TWRP's menu entry)
    • launch the built-in terminal in TWRP, cd into /data/local, make migration.sh executable (chmod +x) and execute the command ./migration.sh official
    • (In case you receive an error, try sh ./migration.sh official instead)
    • flash the ROM .zip
    • wipe Cache and Dalvik/ART Cache
    • reboot system
    More background information "theory behind" can be found in the LineageOS wiki and AOSP reference.


    Switching between build flavors
    You can easily do so via clean-install. However, if you want to switch between the standard build and the microG build and vice-versa without wiping your data, please follow the below instructions:

    Standard build => microG build
    • De-install any of the following apps, in case you have manual installations of them: Yalpstore, Privacy-friendly netmonitor, microG Services Core, microG Services Framework Proxy, Fake Store, F-Droid, Mozilla Unified NLP Backend, Nominatim Geocoder Backend
    • Deactivate System Webview
    • If you have flashed GApps before, deactivate all of them to remove any installed updates
    • Boot into TWRP recovery
    • If you have flashed GApps before, delete the file /system/addon.d/70-gapps.sh
    • Flash the microG ROM ZIP (make sure not to use an older version than the current standard build)
    • Wipe Cache & Dalvik and reboot
    • Follow the 'Post-install' steps outlined here

    microG build => standard build
    • Deactivate the following apps: Yalpstore, Privacy-friendly netmonitor, microG Services Core, microG Services Framework Proxy, Fake Store, F-Droid, Mozilla Unified NLP Backend, Nominatim Geocoder Backend, Bromite System Webview
    • Boot into TWRP recovery
    • Flash the standard ROM ZIP (make sure not to use an older version than the current microG build)
    • If you want to flash GApps, do it before re-boot
    • Wipe Cache & Dalvik and reboot

    Please note, that you may face issues with some apps, which depend on play services. In that case, try solving them in the following order: 1. delete app cache, 2. delete app data, 3. de-install and re-install app


    Weather Widget

    LineageOS does currently not offer Weather provider apps for LineageOS 15.1 for download (only for LineageOS 14.1)
    We've have built an APK for OpenWeatherMap for download from the LineageOS sources here, which works well with LineageOS 15.1


    SafetyNet

    Google SafetyNet is a device certification system, ensuring that the device is properly secured and compatible with Android CTS. Some applications use SafetyNet for security reasons, to enforce DRM or as a prerequisite for tamper-protection. General information about SafetyNet can be found here or e.g. see LineageOS' statement about SN.

    The below information is only relevant for the microG build. In the standard build, you have SafetyNet, if you flash Gapps. Whether the SN attestation passes or not is completely out of our influence!

    If you don't need SafetyNet (i.e. you don't use apps requiring it), I recommend to switch off SafetyNet in microG settings and in addition, go to Settings - apps, make system processes visible and disable the app 'microG DroidGuard Helper'
    In that case, you can safely skip the below information. (If you access the play store with Yalp coming with this build, apps, which the original playstore app would hide because of failed SafetyNet, such as e.g. Netflix, are still listed, so you don't need SafetyNet for that specific purpose)

    If you need SafetyNet, because you use an app requiring SafetyNet attestation to pass, switch SafetyNet on in microG settings and make sure the a.m. DroidGuard Helper app is active. Further, please consider below important information.

    The typical use-case, for which SafetyNet has been developped and is e.g. used by Google, is e.g. "Google Pay".
    Although it seems not to be the intention of Google to make SafetyNet part of "ordinary, average" apps - unfortunately - a certain tendency can be observed that more and more apps make use of it. Especially nosy and privacy intrusive apps seem to start using SafetyNet against Custom ROMs, because Custom ROMs usually allow to at least restrict uncontrolled data collection.

    microG GmsCore contains a free implementation of SafetyNet, but the official server requires SafetyNet requests to be signed using the proprietary DroidGuard system. A sandboxed version of DroidGuard has been added to this microG build as a prebuilt “DroidGuard Helper” app to run the Google code in an isolated environment. The chosen approach in my build is proposed and discussed within the microG project, but not yet officially implemented by microG.

    As of March 11th 2019, the microG build passes the SafetyNet attestation, when installed w/o root or Xposed.
    So, if you need SafetyNet and you also need root, Magisk would be the way to go.
    To avoid confusion: Magisk can hide itself from being detected by SafetyNet and thus help to pass SN, if the device would pass SN without having Magisk installed. Nothing more.

    Note: Currently, the DroidGuard helper app is not part of the build, as it currently does not work any more.

    There are apps available on the Play store to show, whether SafetyNet attestation is passed, for example 'SafetyNet Test' (org.freeandroidtools.safetynettest)


    IMPORTANT
    I cannot and I will not give any assurance that SafetyNet attestation is passed by this build!
    The SafetyNet code, which is dynamically downloaded from Google servers and executed on the device as part of the defined functionality, is regularly maintained and further developped by Google. Although it currently works, it could stop working in the future, until the microG team finds again a solution.
    (Interesting enough: Remote code execution is normally considered a severe vulnerability, but hey, it's Google and we all "trust" them 100%, don't we? ;) - At least I, besides others, exactly for that reason, do not use Gapps!)
    Further, I for my part refuse to use apps requiring SafetyNet, but that is of course everybody's own decision.


    Usage of ANT+

    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.


    Bug reports:
    If you have a problem please create a post with these information:
    Original Kernel shipped with this rom:
    Build Date:
    And try to get log as described here


    Credits
    In continuation of the previous thread, we would like to acknowledge:
    Android Open Source project (AOSP)
    LineageOS project
    AICP project
    SpiritCroc: big thanks to him for maintaining the device trees and a lot of very useful hints
    rcstar6696
    SuperLamic
    drakonizer
    AdrianDC
    munjeni: thanks for tips and tricks
    nailyk: thanks for tips and tricks
    All the other contributors on sony msm8974 platform
    microG project
    CopperheadOS project
    csagan5 (Bromite)
    Yeriomin (Yalp)


    XDA:DevDB Information
    [ROM][Unofficial][8.1.0][signed] LineageOS 15.1 for Xperia Z1 compact, ROM for the Sony Xperia Z1 Compact

    Contributors
    MSe1969, 115ek
    Source Code: https://github.com/lin15-microG/local_manifests

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.4.x
    Based On: LineageOS

    Version Information
    Status: Stable
    Stable Release Date: 2020-02-09

    Created 2018-12-29
    Last Updated 2020-03-09
    6
    Using old firmware blobs from bacon mentioned here did the trick for me.
    Anyway I'm going to look into the difference between bacon and amami blobs - I just thought I understood how it works... :rolleyes:
    I'm able to see and use upper 5GHz channels now which means wifi auto channeling now works with my router.
    Going to build a clean testbuild for you now. I'll report back in a few hours :)

    ---------- Post added at 03:56 PM ---------- Previous post was at 02:59 PM ----------

    I'll only provide a testbuild for pure lineage - microg users have to wait at least for next ASB update (early april). I'm a bit lazy :laugh:
    You'll find the build here
    Just wipe /system, /"cachestuff" and install new .zip.
    Please report and share your experiences. I'm also interested if some other things are broken now (hotspot...).

    BTW: If there's a strong demand for a fixed microg version --> let us know. It's no problem to get one built before april.

    If you report the problem solved this fix will also be included in Lineage 16 and AICP 14 by @SpiritCroc
    5
    New build with February '19 ASB

    Hi all,
    new builds are available for the February ASB patches:

    A. Standard build flavor
    https://www.androidfilehost.com/?fid=1395089523397889456
    • ASB Security string 2019-02-05
    • Kernel: Various Security Patches and some additional 'spectre' mitigations
    • Fix of Eleven and LockClock app taken over from microG flavor

    B. microG build flavor
    https://www.androidfilehost.com/?fid=1395089523397889455
    • ASB Security string 2019-02-05
    • Kernel: Various Security Patches and some additional 'spectre' mitigations
    • Bromite SystemWebView updated to M72

    Happy flashing!
    Regards, M.
    4
    New builds with November 2019 ASB patches

    New builds available with November 2019 ASB patches (sec. string 2019-11-05):

    A. Standard variant
    https://androidfilehost.com/?fid=4349826312261626355

    B. Hardened microG build variant
    https://androidfilehost.com/?fid=4349826312261626354
    - Updated Bromite SystemWebview to 78.0.3904.72

    OTA updates will be offered from within the ROM (Updater app), if you are at least on the August build of this ROM.
    Regards - M.
    3
    Change log

    March 9th, 2020
    Announcement to discontinue this thread - please visit the LineageOS 16.0 successor thread

    February 9th, 2020
    • ASB Security string 2020-02-05
    • Replaced DRM lib (fixes issues with Netflix)
    • Standard flavor: System Webview on 79.0.3945.136
    • microG flavor: Bromite Webview on 79.0.3945.139
    • microG flavor: Updated AuroraStore to 3.1.8

    January 14th, 2020
    • ASB Security string 2020-01-05
    • Standard flavor: System Webview on 79.0.3945.116
    • microG flavor: Bromite Webview on 79.0.3945.107
    • microG flavor: Updated AuroraStore to 3.1.7
    • microG flavor: Updated AuroraServices to 1.0.5

    December 7th, 2019
    • ASB Security string 2019-12-05
    • Standard flavor: System Webview on 78.0.3904.96
    • microG flavor: Bromite Webview on 78.0.3904.119
    • microG flavor: Updated AuroraStore to 3.1.5

    November 10th, 2019
    • ASB Security string 2019-11-05
    • Standard flavor: System Webview on 77.0.3865.116
    • microG flavor: Bromite Webview on 78.0.3904.72
    • microG flavor: Updated microG GMS core 0.2.9.x

    October 14th, 2019
    • ASB Security string 2019-10-05
    • Standard flavor: System Webview on 77.0.3865.92
    • microG flavor: Bromite Webview on 77.0.3865.104
    • microG flavor: AuroraStore updated to 3.1.3

    September 10th, 2019
    • ASB Security string 2019-09-05
    • Standard flavor: System Webview on 76.0.3809.111
    • microG flavor: AuroraServices updated to 1.0.4

    August 11th, 2019
    • ASB Security string 2019-08-05
    • OTA Support
    • Standard flavor: System Webview on 76.0.3809.89
    • microG flavor: Bromite Webview on 76.0.3809.100
    • microG flavor: Aurorastore 3.0.9 with AuroraServices install method
    • microG flavor: Updated microG GMS core 0.2.8.x

    July 5th, 2019
    • ASB Security string 2019-07-05
    • microG flavor only: Bromite Webview on 75.0.3770.109

    June 12th, 2019
    • ASB Security string 2019-06-05
    • Recovery boot fix for Magisk 19.x
    • System Webview updated to 74.0.3729.157 (non-microG flavor)
    • microG flavor only: Bromite Webview on 75.0.3770.86
    • microG flavor only: Replaced Yalpstore with Aurorastore
    • microG flavor only: Removed RemoteDroidGuard
    • microG flavor only: Updated F-Droid & priv. extension
    • microG flavor only: Updated microG GMS core 0.2.7.x

    May 9th, 2019
    • ASB Security string 2019-05-05
    • System Webview / Bromite Webview both on M74
    • microG flavor only: Option to set own DNS
    • microG flavor only: Backport of 'Deny new USB' feature
    • microG flavor only: Additional options for secondary users
    • microG flavor only: Increased max. password length 64

    April 8th, 2019
    • ASB Security string 2019-04-05
    • Solved WLAN 5GHz channel issue (see thread discussion)
    • microG flavor only: Control switch in dev. settings for hosts file update

    March 11th, 2019
    • ASB Security string 2019-03-05
    • SystemWebView updated (includes CVE-2019-5786): M72 (standard flavor) / M73-Bromite (microG flavor)
    • microG flavor only: Prebuilt microG DroidGuard helper app to pass SafetyNet attestation

    February 10th, 2019
    • ASB Security string 2019-02-05
    • Kernel: Various Security Patches and some additional 'spectre' mitigations
    • microG flavor: Bromite SystemWebView updated to M72
    • Standard Flavor: Fix of Eleven and LockClock app taken over from microG flavor

    January 14th, 2019
    • ASB Security string 2019-01-05
    • SystemWebView updated to M71 in Standard flavor
    • Various Kernel security fixes

    December 29th, 2018
    Initial load
    • ASB Security string 2018-12-05
    • AOSP tag android-8.1.0_r52
    • SystemWebView: M69 (Standard flavor) / M71-Bromite (microG flavor)

    Initial feature list of microG flavor:
    • Pre-installed microG and F-Droid same as the LineageOS for microG project
    • Pre-installed YalpStore (Version 0.45)
    • Access to /proc/net blocked for user apps
    • Bundled netmonitor app to allow network monitoring
    • Enhanced Privacy Guard: Switches for motion sensors, other sensors and certain background activities
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking
    • Optional disable captive portal detection
    • No submission of IMSI/IMEI to Google/Sony when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView