[ROM][Unofficial][9.0.0][microG][signed]LineageOS 16.0 for Osprey

Search This thread
Aug 6, 2019
24
24
As indicated above, I will stop providing the build variant A for LineageOS 17.1 - people who were using my build variant A for LineageOS 16.0 should switch to the official builds of 17.1.

M:

I was surprised to see that LineageOS are once again supporting the Moto G3 as they dropped this model some time ago. Are you creating their official build, or has someone else at XDA recently acquired this phone?

When LineageOS dropped the Moto G3, I picked up your custom ROM but went with Variant A since I didn't think I needed the added features of Variant B and so I opted for "simplicity". However, now that you are standardizing on the microG build, I'm thinking that maybe I should simply switch to this version, and stay the course with the tried and tested, rather than go back to LineageOS and have them drop support at some point.

I realize that developers move on from time to time, and that some phones will inevitably lose support at some point. It's just that I'm happy to keep my Moto G3 alive for as long as possible and I have found your builds to be very efficient in this regard.

Alan
 
  • Like
Reactions: Tiki Thorsen
M:

I was surprised to see that LineageOS are once again supporting the Moto G3 as they dropped this model some time ago. Are you creating their official build, or has someone else at XDA recently acquired this phone?

When LineageOS dropped the Moto G3, I picked up your custom ROM but went with Variant A since I didn't think I needed the added features of Variant B and so I opted for "simplicity". However, now that you are standardizing on the microG build, I'm thinking that maybe I should simply switch to this version, and stay the course with the tried and tested, rather than go back to LineageOS and have them drop support at some point.

I realize that developers move on from time to time, and that some phones will inevitably lose support at some point. It's just that I'm happy to keep my Moto G3 alive for as long as possible and I have found your builds to be very efficient in this regard.

Alan
Hi Alan,
I use the official LineageOS device config, kernel and blobs of 17.1 for my Osprey "microG" build. This means, that if I did also a "build variant A", it would be identical (except for the build signature) with the official 17.1 build of LineageOS, and that does not really make a lot of sense.
I *may* (not sure, yet) consider working on an own kernel fork to apply additional patches - but even that would not really justify to publish an own build variant A. (In that case, I could e.g. consider to simply offer a boot.img to be flashed via TWRP or similar, if there was a real interest).
If however - for whatever reason (which I don't believe for the moment) - LineageOS decides to drop the official Osprey support in the future, I will be happy to step in again.
Regards, M.
 
LineageOS 17.1 thread created

Hi all,

I have just posted a new thread for my hardened 17.1 microG buld for the Osprey device:

It contains a 17.1 hardened microG build with the January 2021 ASB patches included.
As explained in this thread before, I would like to summarize the below information:
  • I will stop providing 16.0 builds in this thread
  • The hardened 17.1 microG build from the referred thread can simply be "dirty-flashed" over the latest version of the build variant B from this thread - this is what I recommend to do in the near future
  • People having used the 16.0 build variant A so far should switch to the official LineageOS 17.1 Osprey ROM. I have explained here the details.
  • People already using my 17.1 test build should be offered an OTA update via the Updater app
I would like to use the opportunity to thank you for your interest in these builds and look forward to seeing you in my new 17.1 thread.

In the meantime, I will keep this thread open for a while to answer further topics to my LineageOS 16.0 builds and/or to help migrating to 17.1, if needed.

Cheers, all the best
M.
 
Thank you very much @MSe1969 for your hard work on this builds. Your builds are always high quality one !
I would like to thank you with a few beers/coffees (what's your preferred way of transfert) !?
Many thanks for the positive feedback and for considering making a donation, much appreciated - but don't worry.
I am referring you to an answer, which I have given in another thread about that topic; it outlines my point of view:

Cheers, M.
 
  • Like
Reactions: Tiki Thorsen
Heading towards EOL
Hi all,
as announced already before, there is now a LineageOS 17.1 successor thread for the "microG" build variant B. Btw, an update with February '21 ASB patches has been published there. Also, a "howto" for folks using the 16.0 build variant A to migrate to the "official" LineageOS 17.1 builds has been provided. Further, no additional questions and/or comments to the 16.0 builds have been posted here.

So I think it's time to declare the EOL of this thread. I will soon ask the forum admins to close this thread - if you have any questions on how to migrate, please feel free to ask them in my successor thread.
A last time here, thanks for your interest and hope to see you in my LineageOS 17.1 thread.
Cheers, M.
 
Back again
As explained in the updated and reworked OP, this thread has been re-activated. I will again provide hardened LineageOS 16.0 "microG" builds for the Osprey device. Please read through the updated OP to get the full picture.

You can download the build from here:
  • ASB Security string 2021-12-05
  • Bromite Webview 96.0.4664.54
  • microG 0.22.214516-21
  • F-Droid 1.13
  • Many kernel sec. patches
  • Updated DRM blobs
Happy flashing!
Regards, M.
 
Quote from my 17.1 thread about this 16.0 build from @Tiki Thorsen :
I tested Substratum with DarkCroc and it works like your Lineage 14.1 ROM. Sadly, is not as good as the native dark mode in Android 10, but is usable.
(y)

What I sorely miss from Android 10 is under Settings>Accessibility, is the slider for the balance of the left and right audio channels.
Finding a bloatware/free Music Player that has an internal equalizer with left and right balance was a failure.
This is a feature I need because my hearing on my right lower than the left. In general, I need +3 on the right channel.
I have some good news for you - please have a look at this test build here (will become part of this build from next month onwards - feedback welcome):

Also, the stock music player works, but I tried "Auxio" and "Music Player GO" from F-Droid and it gives me an error:
Media player error -38.
"Music Player GO" seems to work on my latest test build, please check again and let me know.
 

Tiki Thorsen

Senior Member
Jan 27, 2017
238
51
39
Argentina
Samsung Galaxy J4+
Moto G7 Plus
I performed a clean install and tested it for a couple of days.

The audio channel balance under Settings>Accessibility works just as it did on Android 10.
Music Player Go works correctly now.

In case someone is interested in getting a full dark mode;
For Substratum Theme Engine to work, you must have root access
Install this via recovery and then enabled "developer options" and enable "Root Access", afterwards install this.
(I prefer this method over having Magisk installed just to get root)

EDIT: I found a small glitch, entering the wallpapers "app" and scrolling down, is very laggy/delayed and slow.
 
Last edited:
  • Like
Reactions: jemail and MSe1969
@MSe1969 What are your thouts on the Simple Mobile Tools suite?
I am currently testing them, so far they are lightweight and bloatware free. (The gallery, calendar, contacts and phone for now)
Getting them from F-Droid (including Simple Thank You) allows you to have all the PRO versions.
Looks like a good alternative to bloatware stock apps, so for sure worth to consider for folks with Stock ROM on their phones. I haven't tested so far, but makes a really good impression.

In case your thoughts point into suggesting to ship them in my build:
The respective apps provided by default LineageOS are also either based on AOSP or known opensource projects. So I don't see any point in shipping them instead of the LineageOS ones, especially, as everybody can simply install them and decide to use instead of the shipped ones, or install things not shipped by LineageOS (like Draw or the notepad) Or do you see any particular app of them doing things better than the LineageOS ones?
 

Tiki Thorsen

Senior Member
Jan 27, 2017
238
51
39
Argentina
Samsung Galaxy J4+
Moto G7 Plus
Looks like a good alternative to bloatware stock apps, so for sure worth to consider for folks with Stock ROM on their phones. I haven't tested so far, but makes a really good impression.

In case your thoughts point into suggesting to ship them in my build:
The respective apps provided by default LineageOS are also either based on AOSP or known opensource projects. So I don't see any point in shipping them instead of the LineageOS ones, especially, as everybody can simply install them and decide to use instead of the shipped ones, or install things not shipped by LineageOS (like Draw or the notepad) Or do you see any particular app of them doing things better than the LineageOS ones?
I was looking for an SMS app and calendar replacement; since the stock calendar is not usable without an account, and personally I don't like the stock SMS app. The Simple Camera has a very nice feature to remove the metadata from the pictures.
But I do agree with you that it is not necessary to include them in the build.
 

Tiki Thorsen

Senior Member
Jan 27, 2017
238
51
39
Argentina
Samsung Galaxy J4+
Moto G7 Plus
New build with January 2022 ASB patches
Hi all,
a new build is available for download and offered in the Updater app:
  • ASB Security string 2022-01-05
  • Some kernel patches
  • Backported Audio balance (accessibility settings) from Android 10
Happy flashing!

Regards, M.
Which version of TWRP do you recommend? (To avoid using/errors when installing via OTP)

The OTA updated failed to install, it went to TWRP;
Error opening: '/data/system/dropbox/[email protected]' (I/O error)
I:Real error: Unable to stat '/data/system/dropbox/[email protected]'

I did a manual installation of the update and it installed correctly, but it gave me the same error at the end.
I can attach the whole .log file from TWRP if you want/need.
 
Last edited:
Which version of TWRP do you recommend? (To avoid using/errors when installing via OTP)

The OTA updated failed to install, it went to TWRP;
Error opening: '/data/system/dropbox/[email protected]' (I/O error)


I did a manual installation of the update and it installed correctly, but it gave me the same error at the end.
I can attach the whole .log file from TWRP if you want/need.
I just made a test on my 2nd osprey device, and all went smoothly without any issue - using TWRP 3.3.1
 

TheLabCoat

Member
Jun 16, 2021
9
1
Moto G 2015
Hi i found a bug yesterday this all happened because i forced the cpu (i did nothing to the cpu only i tried to play this) trying to play clash of clans the device couldn't handle and it happened something that always happened to me on havoc os or cr droid to reprudece the bug you have to use the rom some time and it comes at a hard reset(holding power button to simulate taking off the battery) the notification bar dosn't show anymore and don't get any push notifications only sound you cant expand notifications or the bar plugin usb don't show the phone folder on the pc. So i was on linage 16 and updating everyday manually with ota this happened so i wiped out internal memory and factory reset and installed this rom (clean flash) in the rom and solved. I got another error that i posted here but it was my fault i forgot to mount data. To reproduce the bug i mentioned before i was using the rom like for 1 month and for this to happen on havoc i was on 3 months or 6 but on that try i didnt forced the cpu just happened and one day woke up turn on my phone and found that i cant use notification bar maybe the customizations of the rom forced



appart from this the rom works great and it is so stable, im going to purchase a battery latter to expand the vital life this is an incredible phone dispite the olderness. Thanks for you effort is really appreciated.
 
Last edited:

Ritik99

Senior Member
Feb 24, 2016
472
117
23
Greater Noida
Hi i found a bug yesterday this all happened because i forced the cpu (i did nothing to the cpu only i tried to play this) trying to play clash of clans the device couldn't handle and it happened something that always happened to me on havoc os or cr droid to reprudece the bug you have to use the rom some time and it comes at a hard reset(holding power button to simulate taking off the battery) the notification bar dosn't show anymore and don't get any push notifications only sound you cant expand notifications or the bar plugin usb don't show the phone folder on the pc. So i was on linage 16 and updating everyday manually with ota this happened so i wiped out internal memory and factory reset and installed this rom (clean flash) in the rom and solved. I got another error that i posted here but it was my fault i forgot to mount data. To reproduce the bug i mentioned before i was using the rom like for 1 month and for this to happen on havoc i was on 3 months or 6 but on that try i didnt forced the cpu just happened and one day woke up turn on my phone and found that i cant use notification bar maybe the customizations of the rom forced



appart from this the rom works great and it is so stable, im going to purchase a battery latter to expand the vital life this is an incredible phone dispite the olderness. Thanks for you effort is really appreciated.
Try this next time.
 
  • Like
Reactions: TheLabCoat

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    New build with April 2022 ASB patches

    Hi all,
    a new build is available for download and offered in the Updater app:
    https://sourceforge.net/projects/lin16-microg/files/osprey/lineage-16.0-20220509-UNOFFICIAL-microG-signed-osprey.zip/download
    • Custom build release 2022-05-01
    • Some kernel patches
    • Bromite Webview on 101.0.4951.53
    • microG updated to 0.2.24.214816-10
    • Mozilla Location provider on 1.5.0
    • F-Droid 1.15
    Happy flashing!

    Regards, M.
    1
    All fine with my own device. A log and a more detailed description of your issue would definitely help...
    Sorry man, I had not configured correctly the APN (my bad). Now it's all working fine, thx again for your work! my phone flies
    1
    A first search suggests this is a TWRP problem. Is twrp-3.3.1-0-osprey still the version the updates are tested with? In case the next update fails, I think it would be probably easier to downgrade TWRP.
    I am using 3.4.0-0, but 3.3.1-0 should also be OK, I think.
    Yes, as a rule of thumb, "never touch a running system" - and more modern TWRP versions are basically created and developped to cope with the respectve latest Android version. As TWRP largely depends on device config, the most advanced TWRP versions are created with device configs aiming at latest Android versions - hence it can (but does not have to) be indeed a reason to "roughly" stick with the TWRP versions, which were optimized for the Android release in use, especially for OTA functionality.
    1
    Thanks for the info. I will instruct to downgrade to version 3.4.0-0 then.

    I bought the device last month and installed the latest TWRP available. I should have checked the thread more carefullly.

    Another small note: it is instructed to use addonsu-16.0-arm64-signed.zip for root access, which did not work for me, but addonsu-16.0-arm-signed.zip did.
  • 13
    Welcome back!

    This thread is dedicated to provide Lineage-OS 16.0 builds for the Motorola Moto G 2015 (Osprey) with current security patches.

    You can consider this thread as kind of a successor of my LineageOS 14.1 Osprey thread
    Well, and as well also a 'successor' of my LineageOS 17.1 Osprey thread !

    Sounds weird? Well, here comes the explanation:
    In May 2020, I have created this thread as a successor of my LineageOS 14.1 builds. Until December 2020, I used to provide two build flavors, one for Standard LineageOS and one with my hardened microG build. From January 2021 onwards, I have provided my hardened microG build flavor with LineageOS 17.1 in above linked thread, whilst I had asked the users of the "Standard" flavor to simply switch to the official LineageOS 17.1 builds. It has turned out, that indeed Android 10 is the boundary, of what can be done with this old device. Especially the hardening measures ask for a stronger hardware, so the builds were "still okay", but not really as agile as the 16.0 builds (especially on an 8GB device). Based on own experience and user feedback in my 17.1 thread, I have finally decided to go back to Android 9 / LineageOS 16.0 - so here we are.

    I have decided to re-enable this thread instead of creating a new one, to allow you to better search for any answers and issues.

    Until December 2020, There were two build flavors available, both signed (see further below). Both builds have aimed at providing stable and reliable "daily-driver" builds. The last "Standard LineageOS 16.0" build can still be downloaded here - I will however not offer this build flavor any more.

    The build flavor, which I offer now again in this thread is my

    Security hardened microG build
    The latest build can be downloaded here.
    It is mainly based on the work of chil360 and the main features are:
    • Fork of Hybrid-X kernel with frequently applied security patches
    • Encryption fully functional
    • Enforcing SE Policy
    • OTA support
    • Pre-installed microG and F-Droid like the LineageOS for microG project (own fork)
    • Pre-installed AuroraStore
    • eSpeak TTS engine (FOSS TTS solution)
    • 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 and other sensors
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking
    • Optional disable captive portal detection
    • Firewall UI
    • 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
    • Constified JNI method tables and hardened bionic lib

    Current release levels
    Custom build release: 2022-05-01
    Security string: 2022-01-05
    AOSP tag: 9.0.0_r46
    Bromite Webview: M101


    Source-code and build instructions
    Kernel: https://github.com/lin16-microg/android_kernel_motorola_msm8916/tree/mse_v1
    Build manifest: https://github.com/lin16-microg/local_manifests

    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 2015 (osprey) 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 key to the reboot recovery option and select with power key)
    • Activate the Developer options (Settings, about phone: tap 7 times on the build number), get into the new menu Developer options and activate, if available, the option "OEM unlocking")
    • 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 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!)

    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 official TWRP recovery from the TWRP site. 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 recovery 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) - 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 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 (if you really want to flash the "historic" build from December 2020), 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 9.0 and the flavor of your choice. I 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.
    (To be more precise, I EXPLICITLY DO NOT RECOMMEND any Gapps variant larger than "nano"!)

    Install the 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 the ROM and swipe to flash.
    If you update from a previous version of the 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 16.0 - 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"


    Dealing with signed builds
    Please note, that my builds are signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You either have to perform a "clean flash" (recommended), or flash "interim-wise" one of my migration builds.

    If you don't want to perform a "clean flash" (which means, you will loose your data), you can work with my prepared "Migration Builds". Simply flash the respective Migration Build flavor (A or B) over your existing build. If you had Gapps before, make sure to also flash the respective Gapps (correct android version!) on top before rebooting and wipe cache and dalvik.
    A migration build resets the package signatures during each boot and thus supports "dirty-flashing" from a different build.
    If you choose to go that path, make sure to immediately perform the OTA update, which will be offered by the Updater app - stay on the migration build as short as possible and UNDER NO CIRCUMSTANCES install or update any app! (if you e.g. had Gapps installed before, deactivate auto-updates).
    The migration builds are foreseen to support the following scenarios only:
    • My Lineage 14.1 (Nougat) Osprey build variant A => my LineageOS 16.0 standard build >> use migration build A
    • Any Lineage 15.1 (Oreo) LineageOS build => my LineageOS 16.0 standard build >> use migration build A
    • Any Lineage 16.0 (Pie) LineageOS build => my LineageOS 16.0 standard build >> use migration build A
    • My Lineage 14.1 (Nougat) Osprey build variant B or C => my LineageOS 16.0 microG build >> use migration build B
    • One of my previous LineageOS 16.0 microG test builds => my LineageOS 16.0 microG build >> use migration build B
    In case you come from my LineageOS 14.1 Osprey builds, please read the detail migration instructions in this thread.
    Download sources:
    Migration Build A
    Migration Build B



    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
    Android Open Source project (AOSP)
    LineageOS project
    chil360
    squid2
    microG project
    csagan5 (Bromite)
    Whyorean (AuroraStore)

    XDA:DevDB Information
    [ROM][Unofficial][9.0.0][signed]LineageOS 16.0 for Osprey, ROM for the Moto G 2015

    Contributors
    MSe1969
    Source Code: https://github.com/lin16-microg/local_manifests

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10.x
    Based On: LineageOS

    Version Information
    Status:
    Stable
    Stable Release Date: 2022-05-09

    Created 2020-05-06
    Last Updated 2022-05-09
    8
    Change Log

    May 9th, 2022

    • Custom build release 2022-05-01
    • Some kernel patches
    • Bromite Webview on 101.0.4951.53
    • microG updated to 0.2.24.214816-10
    • Mozilla Location provider on 1.5.0
    • F-Droid 1.15

    April 15th, 2022
    • Custom build release 2022-04-01
    • Bromite System Webview updated to 100.0.4896.57

    March 17th, 2022
    • Custom build release 2022-03-01
    • Bromite System Webview updated to 99.0.4844.58
    • microG 0.2.24.214816-2
    • AuroraStore 4.1.1

    February 19th, 2022
    • Custom build release 2022-02-01
    • F-Droid updated to 1.14, F-Droid privileged extension to 0.2.13
    • Bromite System Webview updated to 97.0.4692.106
    • microG updated to 0.2.24.214816-2

    January 22nd, 2022
    • ASB Security string 2022-01-05
    • Some kernel patches
    • Backported Audio balance (accessibility settings) from Android 10

    December 26th, 2021
    • Relaunch of LineageOS 16.0 microG builds
    • ASB Security string 2021-12-05
    • Bromite Webview 96.0.4664.54
    • microG 0.22.214516-21
    • F-Droid 1.13
    • Many kernel sec. patches
    • Updated DRM blobs

    - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    December 18th, 2020
    • ASB Security string 2020-12-05
    • System Webview 87.0.4280.101 (Standard variant)
    • Bromite Webview 87.0.4280.106 (microG build variant)
    • Updated microG from upstream to 0.2.14.204215-15 (picked until 720b089)
    • F-Droid updated to 1.10-alpha1-114 (microG build variant)

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

    October 13th, 2020
    • ASB Security string 2020-10-05
    • Bromite Webview 86.0.4240.73 (microG build variant)
    • microG 0.2.12.203315 - including "Exposure notification API" for use of Covid tracing apps (microG build variant)
    • Additional hardening: bionic and constified JNI method tables (microG build variant)

    September 13th, 2020
    • ASB Security string 2020-09-05
    • Kernel: Wireguard tag v1.0.20200908
    • System Webview 85.0.4183.101 (Standard build variant)
    • Bromite Webview 85.0.4183.86 (microG build variant)
    • Added eSpeak TTS engine (microG build variant)

    August 10th, 2020
    • ASB Security string 2020-08-05
    • Kernel: Wireguard tag v1.0.20200729
    • System Webview 84.0.4147.89 (Standard build variant)
    • Bromite Webview 84.0.4147.113 (microG build variant)
    • Location of the firewall functionality moved to Network > Data usage in Settings (microG build variant)

    July 12th, 2020
    • ASB Security string 2020-07-05
    • Kernel: Wireguard tag v1.0.20200623
    • microG: updated prebuilt GmsCore fom /e/ project to fix FCM registration issues (microG build variant)
    • F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11 (microG build variant)
    • Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6 (microG build variant)

    June 10th, 2020
    • ASB Security string 2020-06-05
    • Kernel: Wireguard tag v1.0.20200520
    • Disabled NearbyMessagingService and DiscoveryService (only relevant, if genuine Gapps are used) to improve WiFi performance, when BT is used
    • System Webview on 81.0.4044.138 (Standard build variant)
    • Bromite Webview on 83.0.4103.101 (microG build variant)
    • Sepolicy: Netmonitor exception f. "Tracker Control" app (microG build variant)

    May 6th, 2020
    Initial feature list:
    • OTA Support
    • Enforcing SELinux
    • Forked Hybrid-X kernel with native Wireguard support and current sec. patches
    • System Webview on 81.0.4044.117 (Standard Build)
    • Below listed initial features apply to the "microG" build variant:
    • Pre-installed microG and F-Droid same as the LineageOS for microG project
    • Pre-installed AuroraStore (Version 3.2.8) with AuroraServices 1.0.5
    • 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
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking
    • Optional disable captive portal detection
    • Firewall UI
    • No submission of IMSI/IMEI to Google when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView 81.0.4044.127
    • Additional restrictions for secondary users
    • Increased password length
    8
    Detail features of "microG" build flavor

    1. Pre-installed microG and F-Droid
    same as the LineageOS for microG project

    2. Pre-installed AuroraStore
    works w/o having to enable the "unknown sources feature"

    3. Restrict access to /proc/net for user apps
    An adapted SELinux policy prevents user apps from accessing the /proc/net pseudo file system, which can be misused to monitor and track the phone's internet traffic. For technical backgrounds, see here. For the legitimate use case of the smart phone owner him/herself monitoring the network traffic to see, what the installed apps do, the app Privacy-Friendly Network Monitor has been bundled.

    4. Enhanced Privacy Guard - Sensor permission switches
    An own sensor template to control access to motion sensors ('ask' mode) and all other sensors (allowed by default, but can be restricted) has been implemented into the Privacy Guard.

    5. Cloudflare (instead of Google) default DNS
    Cloudflare DNS has a better privacy policy than Google Public DNS and has DNS-over-TLS and DNS-over-HTTPS. In the deafult DNS settings (as fallback) and network diagnostics, the Cloudflare DNS adresses 1.1.1.1 and 1.0.0.1 are specified as defaults (instead of Google's 8.8.8.8 and 8.8.4.4)

    6. Privacy-preferred default settings
    When newly installed, the below settings are defaulted, different from standard LineageOS 16.0 (all settings can be changed at any time later):
    • Privacy Guard is enabled on install (proposal during Setup)
    • Anonymous LineageOS statistics disabled (proposal during Setup)
    • The standard browsing app does not get the location runtime permission automatically assigned
    • Sensitive information is hidden on the lock screen
    • Camera app: Location tagging disabled by default
    Further, when a lock screen protection is set (PIN, pattern, password), the Nfc, Hotspot and airplane mode tiles require authentication and cannot be set without

    7. Optional blocking of Facebook- and Google-Tracking
    Settings => Network & Internet (scroll down)
    When activated, all outgoing connection attempts to Facebook servers will be suppressed.
    Same applies to Google, but certain apps on an internal exception list will still be able to connect (AuroraStore, microG, or e.g. NewPipe, if installed)

    8. Optional disable captive portal detection
    Settings => Network & Internet (scroll down)
    When activated, the system will not ping a specific Google server any longer when establishing a WiFi connection to determine, whether a captive portal is being used.

    9. No submission of IMSI or phone number to Google/Sony when GPS is in use
    GPS also works fine, if no SIM card is present, so there obviously is no benefit for the phone holder (different from other involved parties :rolleyes:) to provide this data . . .

    10. Default hosts file with many blocked ad/tracking sites
    The system's hosts file redirects a comprehensive list of URLs known to be adware, tracking, etc. to 127.0.0.1 (ipv4) and ::1 (ipv6)

    11. Privacy-enhanced Bromite SystemWebView
    Instead of the default Chromium System Webview component, the Bromite SystemWebView is used offering more privacy, more ad blocking and less Google tracking.

    12. Firewall UI
    Settings => Security & Location - Firewall
    Lists all apps and allows to restrict Internet access per app in regards to WiFi, mobile network or VPN
    This per-app feature is a standard feature in LineageOS, but the UI to show all apps is an Extra (taken from a topic in LineageOS's Gerrit - it may, or may not, become part of the official LineageOS one day)

    13. Maximum password length increased to 64

    14. Additional restriction options for secondary users
    - Disallow app installation option
    - Disallow audio recording option

    15. Miscellaneous hardening
    - hardened bionic lib
    - constified JNI method tables
    8
    New builds with June 2020 ASB

    Hi all,
    new builds with June 2020 sec. patches are available for download - they will also be offered for OTA update by the updater app within the next 30 minutes:

    A. Standard LineageOS 16.0
    https://sourceforge.net/projects/li...0200610-UNOFFICIAL-signed-osprey.zip/download
    • Sec. string 2020-06-05
    • System Webview on 81.0.4044.138
    • Kernel: Wireguard tag v1.0.20200520
    • Disabled NearbyMessagingService and DiscoveryService (only relevant, if genuine Gapps are used) to improve WiFi performance, when BT is used

    B. Security hardened microG build
    https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download
    • Sec. string 2020-06-05
    • Bromite Webview on 83.0.4103.101
    • Kernel: Wireguard tag v1.0.20200520
    • Sepolicy: Netmonitor exception f. "Tracker Control" app (microG build variant)

    Note:
    This month, no platform patches have been applied (only kernel has been updated with many sec. patches):
    The AOSP tag android-9.0.0_r56, which was merged already in May, did already contain all patches, which were pushed again by Google in tag android-9.0.0_r57, which represents the June 2020 ASB.
    6
    New builds with July 2020 ASB patches

    Hi all,
    new builds are up and will soon be offered also as OTA update:

    A. Standard LineageOS 16.0
    https://sourceforge.net/projects/li...0200712-UNOFFICIAL-signed-osprey.zip/download
    • ASB Security string 2020-07-05
    • Kernel: Wireguard tag v1.0.20200623

    B. Security hardened microG build
    https://sourceforge.net/projects/li...-UNOFFICIAL-microG-signed-osprey.zip/download
    • ASB Security string 2020-07-05
    • Kernel: Wireguard tag v1.0.20200623
    • microG: updated prebuilt GmsCore fom /e/ project to fix FCM registration issues (fixes also the delay with Signal messenger)
    • F-Droid updated to 1.8 / F-Droid privileged extension updated to 0.2.11
    • Aurorastore updated to 3.2.9 / AuroraServices updated to 1.0.6

    Happy flashing - cheers, M.