• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[ROM][LineageOS 14.1][substratum] for Moto G [falcon]

Search This thread
Edit: If by provider you mean a location module/backend in microG settings, then I only have a Mozilla Location Service. I tried to activate it but the apps keep misbehaving.
Then the answer already given by @zagzag99 is the explanation.
microG cannot 100% replace the genuine Google Spy Services and also does not aim at doing so. Many apps having Google dependencies work fine, but in general, apps developped by Google themselves usually very deeply integrate and hence have issues with microG and also apps making use of a deep integration with Google Maps are supposed to have problems with microG.

So if you can't make use of alternative apps, i.e. it is an absolute must for you to use those specific apps, then there may be only two options:
a. Not sure, whether this is still the case or not, but earlier, GMaps itself did not need the Google play services, so you may want to try installing Google maps as a regular user app and see what happens?
b. As indicated by zagzag99, you would have to go with the genuine Google stuff and variant A
 

Uusijani

New member
Aug 23, 2021
2
0
Firstly, a big thank you @MSe1969 for keeping my old Moto G (falcon) secure!

My question is about a specific feature: for some reason, Motorola has apparently disabled charging the device when the camera (flash) LED is on (I've found at least one Reddit thread confirming this). Do you happen to know if this is a hardware-level limitation, or if there's any way to override it in the OS/kernel?

I've been testing the phone as a security camera, and while it's otherwise working, in practical use not having the flash LED means having to have a separate light source, adding its own complications (timers and so on).
 
Firstly, a big thank you @MSe1969 for keeping my old Moto G (falcon) secure!

My question is about a specific feature: for some reason, Motorola has apparently disabled charging the device when the camera (flash) LED is on (I've found at least one Reddit thread confirming this). Do you happen to know if this is a hardware-level limitation, or if there's any way to override it in the OS/kernel?

I've been testing the phone as a security camera, and while it's otherwise working, in practical use not having the flash LED means having to have a separate light source, adding its own complications (timers and so on).
Interesting, I wasn't aware about that - so I assume, that you have observed that behavior yourself and not only read about that?
I guess, this would be a hardware limitation, I can't think about a setting controlling this - however, honestly, I don't know.
 

Uusijani

New member
Aug 23, 2021
2
0
Interesting, I wasn't aware about that - so I assume, that you have observed that behavior yourself and not only read about that?

Yes I have: with a charger plugged in and the flash LED on, the phone does show the charging indicator, but the charge level is still dropping. Ampere also shows that it is in fact draining the battery:

Screenshot_20210810-170452.png

I guess, this would be a hardware limitation, I can't think about a setting controlling this - however, honestly, I don't know.

Okay, thanks anyway. Motorola probably had a good reason for this limitation, such as temperature control, and overriding it would thus be risky too, even if it were possible.
 
Yes I have: with a charger plugged in and the flash LED on, the phone does show the charging indicator, but the charge level is still dropping. Ampere also shows that it is in fact draining the battery:

View attachment 5401453



Okay, thanks anyway. Motorola probably had a good reason for this limitation, such as temperature control, and overriding it would thus be risky too, even if it were possible.
Maybe even only a result of the simple hardware design - the device was in 2013 a low budget device with still some notable offerings. As internal memory for example, the content of an ordinary SD card is used, so I would not be surprised, if this simply is a side effect of a clever, but very minimalistic hardware design
 

koshikas

Senior Member
Jun 16, 2015
709
306
Colombo
and may i remind, for a budget device the LED was pretty powerful, i've only found few that can match it in light emitted(lumens). personally i use it as a "smart" torch now
 

d4foasta

Member
Aug 26, 2012
14
1
hi thx for the latest update; nice rom; my first time trying it; undortunatley i can't seem to get the location working?
i installed microg core from f-droid which comes with default location package no?

edit/
forgot to mention when i try to configure backend in nlp settings i get message "error initializing backend".

edit2/
okay doh it was a permissions issue! location working now
Hi peelie,

sorry for digging this up, but i have exactly this problem after using this directions
Which permissions did you have to change, do you remember?

kind regards,
d4foasta

EDIT: Sorry i overlooked that this was only the last post on the first page *facepalm* MAY BE DELETED :)

EDIT2: It seems i am not able to find any information on this topic other than the reference in Post #22

EDIT3: If someone is interested, i managed to get it all checked. I think what finally did the trick is moving the NetworkLocation.apk from priv-app/UnifiedNLP/NetworkLocation.apk to /system/app/NetworkLocation.apk
Ah, and maybe after moving the apk removing the backends and reinstalling them + rebooting.
 
Last edited:
Hi peelie,

sorry for digging this up, but i have exactly this problem after using this directions
Which permissions did you have to change, do you remember?

kind regards,
d4foasta

EDIT: Sorry i overlooked that this was only the last post on the first page *facepalm* MAY BE DELETED :)

EDIT2: It seems i am not able to find any information on this topic other than the reference in Post #22

EDIT3: If someone is interested, i managed to get it all checked. I think what finally did the trick is moving the NetworkLocation.apk from priv-app/UnifiedNLP/NetworkLocation.apk to /system/app/NetworkLocation.apk
Ah, and maybe after moving the apk removing the backends and reinstalling them + rebooting.
It seems you use the build variant A and install UnifiedNLP to it. I am wonderng, why you don't use variant B then, which brings all pre-installed. UnifiedNLP is a subset of microG, and if you simply switch off the device registration and GCM, you have in fact UnifiedNLP.
Of course, your choice - but I don't really see the advantage...
 
New builds available with September 2021 ASB patches

Hi all, new builds are available and already offered via Updater app:

A. Default LineageOS 14.1 with substratum and microG patch
  • Security string 2021-09-05
  • System Webview 92.0.4515.159
B. Hardened build with pre-installed microG and F-Droid, patched for substratum
  • Security string 2021-09-05
  • microG 0.2.22.212658-2
Regards, M.
 
Last edited:

phpbb3

Senior Member
Pretty tickled to see another security patch for falcon, thank you kindly @MSe1969 ...

Last time I fresh installed this, I used some weird mod I found somewhere to give me a Play Store I could turn on/off at whim. I did this because Aurora store was rough around the edges.

probably 3 months ago, this modified play store won't load anymore (likely because it can't be updated).

No big deal, as the music apps I needed were already installed.

HOWEVER, decided today to re-enable Aurora and it's service and I am amazed how much better it has gotten both in UI and functionality.

My falcon still runs better than ever, appreciate your hard work bringing it all together for this old ARM.
 
Dont these CVEs impact only 8.1 and newer?
Well, the answer is not so trivial as the question may indicate:
  • Google does not support Android 7.1 since longer times, if I'm not mistaken, the last ASB with official 7.1 fixes is the October 2019 one. Any later ASB simply does not mention any more Android 7.1.
  • The community however has continued to back-port the announced patches, if they were showing Android 8.x as being relevant and if the code would be fitting and the LineageOS directors have merged those patches, if this was strictly ASB patches.
  • The mentioned CVE's in fact have been addressed by Google with a major version upgrade of the V8 engine (instead of a couple of simple commits). The code changes themselves seem to apply, but the blocking point at the moment is, that the newer version uses the .bp soong-style make files instead of the older .mk format, and an Android 7.1 buildenvironment can't deal with that. The Android.bp file of that newer version is nightmarishly complex and cannot be easily "back translated". Assuming that issue is solved, we still would need to see, whether it really works or not.
So the above question cannot be answered with a simple yes or no at the moment. Further, an ASB usually contains three parts:
  1. The "platform part" (date string ending with -01, like e.g. 2021-09-01)
    This is absolutely required.
  2. The "device-dependent part" (date string ending with -05, like e.g. 2021-09-05).
    This part usually contains the kernel fixes, which depend on the kernel release and device-specific situation. They are required, if they apply. Funny enough, the mentioned CVE's are listed here and not in the platform section, which could be interpreted as also being 'device-dependent' - Google does not call them "device-dependent", but as a matter of fact, this is what happens in almost all cases.
  3. "Pixel" bulletin - in a nutshell: "optional" (but recommended, if applicable)
Official LineageOS project's point of view is, if the above CVEs are not fixed, the official build string will not be lifted in the official LineageOS repo.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Next build...
    This month, I have been somewhat quite busy work-wise, so I think I will only be able to take care about next builds towards the weekend.
    4
    Dont these CVEs impact only 8.1 and newer?
    Well, the answer is not so trivial as the question may indicate:
    • Google does not support Android 7.1 since longer times, if I'm not mistaken, the last ASB with official 7.1 fixes is the October 2019 one. Any later ASB simply does not mention any more Android 7.1.
    • The community however has continued to back-port the announced patches, if they were showing Android 8.x as being relevant and if the code would be fitting and the LineageOS directors have merged those patches, if this was strictly ASB patches.
    • The mentioned CVE's in fact have been addressed by Google with a major version upgrade of the V8 engine (instead of a couple of simple commits). The code changes themselves seem to apply, but the blocking point at the moment is, that the newer version uses the .bp soong-style make files instead of the older .mk format, and an Android 7.1 buildenvironment can't deal with that. The Android.bp file of that newer version is nightmarishly complex and cannot be easily "back translated". Assuming that issue is solved, we still would need to see, whether it really works or not.
    So the above question cannot be answered with a simple yes or no at the moment. Further, an ASB usually contains three parts:
    1. The "platform part" (date string ending with -01, like e.g. 2021-09-01)
      This is absolutely required.
    2. The "device-dependent part" (date string ending with -05, like e.g. 2021-09-05).
      This part usually contains the kernel fixes, which depend on the kernel release and device-specific situation. They are required, if they apply. Funny enough, the mentioned CVE's are listed here and not in the platform section, which could be interpreted as also being 'device-dependent' - Google does not call them "device-dependent", but as a matter of fact, this is what happens in almost all cases.
    3. "Pixel" bulletin - in a nutshell: "optional" (but recommended, if applicable)
    Official LineageOS project's point of view is, if the above CVEs are not fixed, the official build string will not be lifted in the official LineageOS repo.
    2
    Did I do something wrong? After install the ROM and gApps, i got stuck in 'checking for updates' after the restart. Is there something that I can do to by pass it?
    This happened to me many times, all you need to do is reboot and it will load normally.
    2
    I've got a question while preparing good old Moto G for my son with this superb ROM.
    I gave encryption a try, but I am not able to mount data partition in latest TWRP. Does it work if I use a password before encryption instead of a PIN? I slightly remember that this procedure was a workaround for TWRP not 'knowing about the encryption key'. Or do I have to use a different TWRP version (currently 3.5.0_9 from twrp.me)?
    MSe1969 recommends using this version of TWRP to avoid issues.
    1
    My daughter uninstalled the camera app somehow. I thought it's a system app.
    I tried reflashing but it didn't return.
    What camera app do suggest for installing ?
    this; https://forum.xda-developers.com/t/...oot-users-advanced-features-17-01-16.3216944/

    stock moto camera ripped for any ROM
  • 57
    Hi,

    this is my unofficial LineageOS 14.1 build for the Moto G (falcon) device with current security patches, microG patch and substratum support.
    (This thread is for the falcon device, I have also a thread for preregrine using the same sources)

    As announced here, LineageOS has discontinued to deliver official 14.1 builds in the course of providing LineageOS 16.0 builds, but the 14.1 tree will continue to be maintained for security patches by the community (I am one of these contibutors, btw). So this build will continue.

    The build has got the following features:
    • LineageOS 14.1 with current security patches (from official LineageOS repositories)
    • Security string 2021-09-05, AOSP tag 7.2.1_r36
    • Adapted LineageOS Jelly Browser (additionally having Startpage and Qwant as search engines)
    • Root is not included and would need to be flashed separately
    • Patched for the use of the substratum theme engine (the substratum app and the themes need to be downloaded separately)
    • System certificates taken from AOSP Oreo branch
    • Kernel forked from LineageOS and updated with many security patches
    • OTA Support
    • Enforcing SELinux

    There are two build variants available:

    A. Default LineageOS 14.1 with substratum and microG patch
    • Patched for the use of microG - you can either flash Gapps or manually install microG as apps (or use neither of those)
    • Android System Webview M92
    Download here

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    For the security/privacy focused. It has to be said that microG seems to run better if it is pre-installed.
    • Pre-installed microG same as the LineageOS for microG project
    • Pre-installed AuroraStore / AuroraServices
    • Additional security hardening features listed below
    • SQLite 'secure delete' feature enabled
    • Access to /proc/net blocked for user apps
    • Bundled netmonitor app to allow network monitoring
    • Enhanced Privacy Guard: Switches for motion sensors and other sensors available
    • Oreo backport: SET_TIME_ZONE permission restricted to system apps
    • Oreo backport: Access to timers in /proc restricted
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • No submission of IMSI/phone number to Google when GPS is in use
    • Bromite System Webview M92
    Download here

    Source Code links
    LineageOS: https://github.com/LineageOS
    Kernel: https://github.com/lin14-mGoms/android_kernel_motorola_msm8226/tree/mse_v1
    microG patches:
    (1) https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
    (2) https://github.com/microg/android_p...aster/patches/android_frameworks_base-N.patch
    Patches for Substratum: https://github.com/LineageOMS
    local manifest: https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-oms

    Installation Instructions

    YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!
    Please note - I 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 Motorola Moto G (falcon) device, especially how to enter fastboot mode (switch phone off hold power + volume down together for about 3 seconds) and recovery mode (in fastboot mode, switch with volume down key to the reboot recovery option and select with volume up key)
    • 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 this ROM and place it to your phone's internal memory
    • An unlocked bootloader (read the warnings carefully and backup your data!
    • Your bootloader must at least be on version 41.18 (find out via fastboot getvar version-bootloader) - if your bootloader is below that version, the ROM will refuse to install. In that case, you need to upgrade the BL first. See e.g. here for more info. (I currently do not find the link, which I have used some years back, but the provided link should be helpful, too)

    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 - I recommend to use the TWRP recovery. The following instructions are based on TWRP.
    NOTE: There have been reports of encryption issues in this thread, when using TWRP 3.3.x, which disappear, when TWRP 3.2.1 is used - I myself use the TWRP 3.2.1, as higher versions have mainly been developed for higher Android versions. I can't technically confirm or prove the situation, but based on the reports and the fact, that I myself did not encounter ANY issues for my own device with TWRP 3.2.1, I recommend this version
    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, get it into 'fastboot mode', connect the device via USB to your PC and enter the following command on your PC:
    Code:
    fastboot flash recovery TWRP.img
    Afterwards, directly boot into 'recovery mode' (see above) - I 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.

    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 specify "Dalvik", "System", "Cache" and "Data" to be wiped.
    Make sure NOT to wipe "Internal memory" (or "SD Card", if shown). Swipe to confirm the deletion and get back into the main menu.

    GApps (only for build variant A - do not flash on build variant B!)
    You have the choice: a. Use microG - b. Flash GApps - c. Neither of those (obviously, you cannot combine those options!)
    'microG' is installed simply by installing the respective apps, no flashing necessary. If you wish to have GApps, they need to be flashed together with the ROM. Download GApps in that case only from opengapps.org and put the .ZIP also to the Internal memory of your device. Choose ARM as platform, Android 7.1 and the flavor of your choice. I strongly recommend "pico" for two reasons:
    1. The Moto G has not much internal memory (8 or 16GB) and no SD card and GApps are notoriously known to waste a lot of space
    2. It leaves you the most freedom to only install, what you really need; you can later download and still install all the Google products you want from the play store, so you do not need to live with pre-installed Google stuff you have no use for.
    The 'microG patch' in this ROM has no negative impact on installing Gapps.

    Install the ROM
    In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard).
    Choose the .ZIP file of this ROM and swipe to flash. If you update from a previous version of this ROM, you don't need to perform a wipe. If in that case, 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.
    If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above. If you want to install GApps, flash them directly after the ROM, do not reboot in between. (Note: If you wish to get rid of previously installed 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)
    When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 14.1 - be patient, the first boot after flashing a new ROM takes quite long!


    Current / reported issues
    • WiFi hotspot needs to be toggled on/off/on after a reboot to work
    • WiFi hotspot enabled longer than 2 hours may cause a sudden reboot
    • Sometimes (root cause not clear), WiFi switches itself off after a couple of hours (fix by enabling/disabling flight mode)
    • It has been reported by some forum participants, that after messing with some Android-10 test builds for this device, WiFi wouldn't work any more: In this case, the solution can be found here:
      or here (scroll down and use the manual unpack option):

    Why still on Android 7.1 (Nougat) and not a higher Android version (like 10 or 11)?
    The falcon device is low on memory (RAM and storage flash memory), each newer Android release increases the resource demand and thus decreases performance and available memory - so higher versions won't really make sense for this device.
    Further, I haven't seen any ROM for this device on a higher Android version than Nougat with enforcing SELinux (yes, coming there indeed is "slave work"; none of the devs, including me for above stated reasons, is willing to invest this time...) - which is a No-Go for any daily-driver use (in that case, your device simply is fully open many vulnerabilities and applying monthly ASB patches on a permissive SELinux is close to a complete waste of time).


    Credits
    Android Open Source project (AOSP)
    LineageOS project
    microG project
    Substratum team
    SkewedZeppelin (Kernel patches)


    XDA:DevDB Information
    [ROM][LineageOS 14.1][substratum] for Moto G [falcon], ROM for the Moto G

    Contributors
    MSe1969
    Source Code: https://github.com/lin14-mGoms/local_manifests/tree/cm-14.1-oms

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.4.x
    Based On: LineageOS 14.1

    Version Information
    Status:
    Stable
    Current Stable Version: cm-14.1
    Stable Release Date: 2021-09-17

    Created 2018-06-24
    Last Updated 2021-09-17
    20
    Change Log

    September 17th, 2021

    • UNOFFICIAL Security string 2021-09-05 *
    • Standard flavor only: System Webview updated to 92.0.4515.159
    • microG flavor only: microG upstreamed to 0.2.22.212658-2
    ___________________________
    * CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!

    August 10th, 2021
    • UNOFFICIAL Security string 2021-08-05 *
    • Standard flavor only: System Webview updated to 91.0.4472.164
    • microG flavor only: Bromite System Webview updated to 92.0.4515.134
    • microG flavor only: F-Droid 1.13
    ___________________________
    * CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!

    July 14th, 2021
    • UNOFFICIAL Security string 2021-07-05 *
    • Kernel: Many sec. patches applied (taken from Divest-OS)
    • microG flavor only: Bromite System Webview updated to 91.0.4472.146
    • microG flavor only: microG upstreamed to 0.2.21.212158-2
    • microG flavor only: AuroraStore 4.0.7
    ___________________________
    * CVE-2021-0514 and CVE-2021-0515 from July 2021 ASB are still missing!

    June 16th, 2021
    • Security string 2021-06-05
    • Standard flavor only: System Webview updated to 91.0.4472.101
    • microG flavor only: Bromite System Webview updated to 91.0.4472.102
    • microG flavor only: microG upstreamed to 0.2.19211515-9

    May 09th, 2021
    • Security string 2021-05-05
    • Standard flavor only: System Webview on 90.0.4430.82
    • microG flavor only: Bromite System Webview on 90.0.4430.204
    • microG flavor only: microG upstreamed (no version upgrade)
    • microG flavor only: AuroraServices updated 1.1.1

    April 11th, 2021
    • Security string 2021-04-05
    • Standard flavor only: System Webview on 89.0.4389.105
    • microG flavor only: Bromite System Webview on 90.0.4430.59
    • microG flavor only: F-Droid updated to 1.12
    • microG flavor only: AuroraStore updated to 4.0.4 with AuroraService 1.1.0

    March 08th, 2021
    • Security string 2021-03-05
    • microG flavor only: Bromite System Webview on 88.0.4324.207
    • microG flavor only: F-Droid 1.11
    • microG flavor only: microG 0.2.18.204714

    February 07th, 2021
    • ASB Security string 2021-02-05
    • microG flavor only: Bromite Webview on 88.0.4324.141
    • microG flavor only: Updated microG from upstream to 0.2.17.204714-5
    • microG flavor only: F-Droid updated to 1.10-alpha-234

    January 17th, 2021
    • ASB Security string 2021-01-05
    • Standard flavor only: System Webview on 87.0.4280.101 & fix of persistent histograms eating disk space
    • microG flavor only: Bromite Webview on 87.0.4280.131
    • microG flavor only: Updated microG from upstream to 0.2.16.204713-10 (picked until 2f29b93)
    • microG flavor only: F-Droid updated to 1.10-alpha1-212

    December 18th, 2020
    • ASB Security string 2020-12-05
    • Standard flavor only: System Webview on 86.0.4240.198
    • microG flavor only: Bromite Webview on 87.0.4280.68
    • microG flavor only: Updated microG from upstream to 0.2.14.204215-15 (picked until 720b089)
    • microG flavor only: F-Droid updated to 1.10-alpha1-114

    November 08th, 2020
    • ASB Security string 2020-11-05
    • Fix of AOSP E-Mail widget
    • Fix for CVE-2020-15999
    • Standard flavor only: System Webview 86.0.4240.185
    • microG flavor only: Bromite Webview on 86.0.4240.181
    • microG flavor only: Updated microG with fixes in GCM and EN API
    • microG flavor only: Replaced weak F-Droid signatures with ROM's V2 signatures

    October 12th, 2020
    • ASB Security string 2020-10-05
    • Updated TimeService.apk
    • microG flavor only: Bromite Webview on 86.0.4240.73
    • microG flavor only: updated microG with included Exposure notification API (for Covid tracing apps)

    September 14th, 2020
    • ASB Security string 2020-09-05
    • Standard flavor only: System Webview on 85.0.4183.101
    • microG flavor only: Bromite Webview on 85.0.4183.86

    August 9th, 2020
    • ASB Security string 2020-08-05
    • Standard flavor only: System Webview on 84.0.4147.89
    • microG flavor only: Bromite Webview on 84.0.4147.113

    July 12th, 2020
    • ASB Security string 2020-07-05
    • microG flavor only: updated prebuilt microG GmsCore fom /e/ project to fix FCM registration issues
    • microG flavor only: F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
    • microG flavor only: Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6

    June 09th, 2020
    • ASB Security string 2020-06-05
    • Standard flavor only: System Webview on 81.0.4044.138
    • microG flavor only: Bromite Webview on 83.0.4103.76

    May 07th, 2020
    • ASB Security string 2020-05-05
    • Standard flavor only: System Webview on 81.0.4044.117
    • microG flavor only: Bromite Webview on 81.0.4044.127
    • microG flavor only: AuroraStore updated to 3.2.8

    April 10th, 2020
    • ASB Security string 2020-04-05
    • Fix for CVE-2020-8597 (external/ppp)
    • Kernel: CVE-2019-10638 siphash 128bit for IP generation
    • Standard flavor only: System Webview on 80.0.3987.132
    • microG flavor only: Bromite Webview on 81.0.4044.76
    • microG flavor only: AuroraStore updated to 3.2.4

    March 07th, 2020
    • ASB Security string 2020-03-05
    • Standard flavor only: System Webview on 80.0.3987.117
    • microG flavor only: Bromite Webview on 80.0.3987.118
    • microG flavor only: AuroraStore updated to 3.2.0
    • microG flavor only: Added Netguard app (F-Droid version) to SELinux domain allowing to access /proc/net

    February 07th, 2020
    • ASB Security string 2020-02-01
    • Standard flavor only: System Webview on 79.0.3945.136
    • microG flavor only: Bromite Webview on 79.0.3945.139
    • microG flavor only: AuroraStore updated to 3.1.8

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

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

    November 10th, 2019
    • ASB Security string 2019-11-05
    • microG flavor only: Bromite Webview on 78.0.3904.72
    • microG flavor only: microG GMS core updated to 0.2.9

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

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

    August 11th, 2019
    • ASB Security string 2019-08-05
    • Additional patches from AOSP branch 'nougat-mr2-security-release'
    • OTA Support
    • microG flavor only: Bromite Webview on 76.0.3809.100
    • microG flavor only: Aurorastore 3.0.9 with AuroraServices install method

    July 5th, 2019
    • ASB Security string 2019-07-05
    • System Webview updated to 75.0.3770.101 (non-microG flavor)
    • microG flavor only: Bromite Webview on 75.0.3770.109

    June 12th, 2019
    • ASB Security string 2019-06-05
    • 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: Updated F-Droid & priv. extension
    • microG flavor only: Updated microG GMS core 0.2.7.x

    May 8th, 2019
    • Security string 2019-05-05
    • System Webview M74
    • 2nd build variant: "hardened microG build"

    April 8th, 2019
    • Security string 2019-04-05

    March 12th, 2019
    • Security string 2019-03-05
    • Android System Webview updated to M72 (includes CVE-2019-5786)

    February 8th, 2019
    • Security string 2019-02-05
    • Android System Webview M71
    • Kernel updated with many security patches
    • Additional Spectre V1 mitigations for the kernel

    January 12th, 2019
    • Security string 2019-01-05

    December 8th, 2018
    • Security string 2018-12-05
    • Fix of 'adb root' bug

    November 8th, 2018
    • Security string 2018-11-05

    October 20th, 2018
    • Security string 2018-10-05
    • Android System Webview M69

    September 9th, 2018
    • Security string 2018-09-05

    August 10th, 2018
    • Security string 2018-08-05

    July 24th, 2018
    • Security string 2018-07-05
    • System certificates from Oreo AOSP branch

    June 24th, 2018
    Initial creation
    • Security string 2018-06-05
    • AOSP tag 7.2.1_r36
    • Android System Webview M67
    • microG N patches
    • Patched repositories according to LineageOMS project to support substratum
    18
    New builds with April 2020 ASB

    Hi all,
    new builds are ready and are already offered through the updater app as OTA update:

    A. Default LineageOS 14.1 with substratum and microG patch
    https://sourceforge.net/projects/li...1-20200410-UNOFFICIAL-oms-falcon.zip/download
    • ASB Security string 2020-04-05
    • Fix for CVE-2020-8597 (external/ppp)
    • Kernel: CVE-2019-10638 siphash 128bit for IP generation *
    • System Webview on 80.0.3987.132

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    https://sourceforge.net/projects/li...0200409-UNOFFICIAL-mG-oms-falcon.zip/download
    • ASB Security string 2020-04-05
    • Fix for CVE-2020-8597 (external/ppp)
    • Kernel: CVE-2019-10638 siphash 128bit for IP generation *
    • Bromite Webview on 81.0.4044.76
    • AuroraStore updated to 3.2.4

    Cheers, M.
    ________________________________________
    * Kernel is frequently updated every month, but this one I found worth mentioning
    16
    New builds with June 2020 ASB

    Hi all,

    new builds are ready for download and also already offered for OTA update through the updater app:

    A. Default LineageOS 14.1 with substratum and microG patch
    https://sourceforge.net/projects/li...1-20200607-UNOFFICIAL-oms-falcon.zip/download
    • Sec. string 2020-06-05
    • System Webview on 81.0.4044.138

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    https://sourceforge.net/projects/li...0200605-UNOFFICIAL-mG-oms-falcon.zip/download
    • Sec. string 2020-06-05
    • Bromite Webview on 83.0.4103.76

    Note:
    This time, there haven't been any platform patches, as all published patches were already pushed by Google in a previous tag upstream and already back ported.
    15
    New builds with May 2020 ASB

    Hi all,
    new builds are ready and are already offered through the updater app as OTA update:

    A. Default LineageOS 14.1 with substratum and microG patch
    https://sourceforge.net/projects/li...1-20200507-UNOFFICIAL-oms-falcon.zip/download
    • ASB Security string 2020-05-05
    • System Webview on 81.0.4044.117

    B. Hardened build with pre-installed microG and F-Droid, patched for substratum
    https://sourceforge.net/projects/li...0200507-UNOFFICIAL-mG-oms-falcon.zip/download
    • ASB Security string 2020-05-05
    • Bromite Webview on 81.0.4044.127
    • AuroraStore updated to 3.2.8

    Cheers, M.