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

[ROM][Unofficial][10.0][microG][signed]hardened LineageOS 17.1 Oneplus 3/3T

Search This thread

borisSweden

Senior Member
May 10, 2021
70
3
Not aware - could you please explain in more detail, what you mean?
Sorry sorry, I missspelled. Are these apps like them.
Not aware - could you please explain in more detail, what you mean?


I am not really experienced in the "RCS" topic (I use Signal as messenger and SMS app), so I have searched a little.
How did you attempt to use RCS? I.e. which app did you install? G* messages?
As G* hasn't opened the APIs to app developers, this seems to be some "exclusive" feature combo of the Google messages app and the G* proprietary spy services...
If that's the case, I can't give you any good advice - proprietary G* apps are usually very deeply integrated with the genuine G* spy services, especially, when it comes to making use of even undocumented functions, so in general, proprietary G* apps tend to work worse with microG. I don't think this is due to Safety net, as Google normally uses SN for REAL needs (not like some other app manufacturers, who even use it for no valid reason, like e.g. the app of a known fast food franchise).
Then I will stop using it. Didnt even have that many contacts.

But I have another issue and that is AOSP keyboard.Is suggestions Play Service based? Can I find a good 3 language keyboard. Its optimized for one language at the time. And is the idea with hardened ROM that Im supposed to lock the bootloader after installing as rooting is discouraged? Thankfully banking,payment and ID apps dont check root in Sweden but Android Pay, Slack doesn't work.
 
But I have another issue and that is AOSP keyboard.Is suggestions Play Service based?
No. AOSP delivers dictionaries as part of the ROM, that's it.

Can I find a good 3 language keyboard. Its optimized for one language at the time.
Good question, Idk - looking forward to suggestions from others as well...

And is the idea with hardened ROM that Im supposed to lock the bootloader after installing as rooting is discouraged?
You CAN re-lock the bootloader on the op3/t, yes. The advantage of doing so however is not huge.

Normally, with a Stock ROM having a restricted recovery refusing to flash "non-original" stuff, a locked boot loader prevents flashing a custom recovery and hence prevents accessing and altering the data and system components of the phone, and if the BL is unlocked, the /data partition will be purged for security reasons to make sure, that e.g. the data of a stolen phone cannot be accessed by unlocking the BL and flashing a custom/special recovery.

On this phone, I would assume you have TWRP as recovery, which will allow all, what is needed also with a locked BL, so it is important to encrypt your /data partition with a proper passphrase.

Remains the question of apps aiming at checking the BL state - the 17.1 kernel overrides some of those flags anyhow (the 18.1 kernel of the test builds not yet). I myself doing development don't lock the BL, because for me, things like fastboot boot test-boot.img need to work.

There still might be some advantages to lock the BL, I think @nvertigo67 has a deeper inside to this and may want to step in.

Thankfully banking,payment and ID apps dont check root in Sweden but Android Pay,
The root checking of banking/payment apps is anyhow only 'security theater', but it's annoying.

Really?
I don't have difficulties - but I only use it to access the LineageOS chat (probably very limited scope of what Slack can be used for...)
 

nvertigo67

Senior Member
Dec 28, 2011
6,020
12,328
There still might be some advantages to lock the BL, I think @nvertigo67 has a deeper inside to this and may want to step in.

I use the unlocked bootloader (bl) to boot/test kernels (e.g. when preparing to kang your kernel...;) ) and new releases of twrp. Other then that I don't see any advantage for an unlocked bl. On the other hand: I can't see any security advantage in locking the bl, as long as twrp is installed. (Assuming the kernel throws away the tripped verity bit - otherwise you need a locked bl to make use of the safetynet api, because current root detection kits detect magisk.)
 

borisSweden

Senior Member
May 10, 2021
70
3
I use the unlocked bootloader (bl) to boot/test kernels (e.g. when preparing to kang your kernel...;) ) and new releases of twrp. Other then that I don't see any advantage for an unlocked bl. On the other hand: I can't see any security advantage in locking the bl, as long as twrp is installed. (Assuming the kernel throws away the tripped verity bit - otherwise you need a locked bl to make use of the safetynet api, because current root detection kits detect magisk.)
Even older hardware and software? I know JohnW jumped ship and axed Hide but I thought older phones would still work.
 

mar.ste

Member
Aug 11, 2011
39
7
I don't know the details about lichess. Can you somehow produce a log or at least more details about the error, which you face?


Sorry for late reply but since this problem I didn't move to this phone. Today I tryed to insert the SIM with data traffic but is the same.

Don't know how to produce a log. I'm pretty "techy" (e.g. 1k real chess for ZX81 or SlyMlego AI framework), but with scattered experience with Android system)

If someone else want to check it works the same also anonymously without creating a user (and lichess is a fantastic open source app to see): is enough to try to start a new game
 

borisSweden

Senior Member
May 10, 2021
70
3
Could you please give a more explicit example?
After some time, I think there is a problem with the connectivity stack.

Wifi isnt as good, I get disconnected even from 2.4Ghz. Screen off causes this. I gave up on 5Ghz. My speed is 250/250.

Phone and BW2 get disconnected if not used for a long time. I have to reregister my headset and Audi MMI every time. ApTX HD is disabled as it overheats the phone. SBC XQ is enough.

WCDMA/UMTS calling is weird. As I dont have VoLTE and VoWifi, 3G calling is very good only when Wifi is active. I only get "HD voice"/AMR-WB with wifi on. So I see the cause as "faulty dual channel data".

So in summary, what kind of logcat do you need MSe1969?
 
Last edited:

nvertigo67

Senior Member
Dec 28, 2011
6,020
12,328
Be a power user! :)

Here "adb logcat" exerpt with lichess not connecting to play after starting correctly, and the app chineasy not able to start (or aborting just after it): https://drive.google.com/file/d/19X-_qXQ-gbgZXQHnlxMiGENfwPF63UhD/view?usp=sharing

There's no backtrace from lichess - maybe incomplete. But I see some sepolicy denials. Since your device is rooted you can try switching selinux to permissive.

Code:
su setenforce 0

Or (depending on the root package you are using:

Code:
su -c "setenforce 0"

Check the selinux state:
Code:
getenforce

If you've set the device successfully to permissive, increase log buffer size in dev-opts to 1 Mio, force stop lichess, delete cache from lichess and try starting lichess. If it works now, get a logcat and grep each and every line containing "avc:" from it. If lichess still doesn't work, post the complete logcat (not only the avc-lines).
 
Last edited:
  • Like
Reactions: MSe1969

mar.ste

Member
Aug 11, 2011
39
7
...su setenforce 0...
...If lichess still doesn't work, post the complete logcat...

Still not working even with permissive set

Here the full log: https://drive.google.com/file/d/1-s14uC7xGQfPWQTL1xaox7UIBuIJTW1S/view?usp=sharing

Anyway I think that the problem (or part of it) might be here:
Code:
10-03 13:48:17.036  5136  5136 D Capacitor/Console: File: http://localhost/lib/socketWorker.js - Line 202 - Msg: [homeLobby xeGzgwPzJ_vN] connection attempt to wss://socket.lichess.org/lobby/socket/v5?sri=xeGzgwPzJ_vN&mobile=1
10-03 13:48:17.036  5136  5136 E Capacitor/Console: File: http://localhost/lib/socketWorker.js - Line 58 - Msg: Uncaught SecurityError: Failed to construct 'WebSocket': Access to this address is not allowed.
 

mar.ste

Member
Aug 11, 2011
39
7
Just to say that I also experienced some connection instability in phone calls. I tried with another ROM (PixelExperience) and it seems all is working.
Anyway I hope you'll be able to stabilize everything since a hardened microg ROM is for sure a nice alternative to this still wonderful phone!
 
Is this also present in 17.1?
No, unfortunately not. However, I will very soon open a LineageOS 18.1 thread for the OP3(T) device.

I fixed Wifi by whitelisting wifi from battery saving mode but Bluetooth is still not working. Already paired devices dont reconnect when reused, have to re-pair with phone for the session.
Thanks for providing feedback. So far, I haven't received any complaints of that kind in regards to the 17.1 build before. As I will start a LineageOS 18.1 thread for this device, I will provide for this month a final 17.1 build very soon. That being said, you may understand, that I will not really spend too much time any more for any issue lookup in the 17.1 build. So I would like to invite you to upgrade to 18.1 soon (once the new thread has been published).
 
  • Like
Reactions: borisSweden

borisSweden

Senior Member
May 10, 2021
70
3
No, unfortunately not. However, I will very soon open a LineageOS 18.1 thread for the OP3(T) device.


Thanks for providing feedback. So far, I haven't received any complaints of that kind in regards to the 17.1 build before. As I will start a LineageOS 18.1 thread for this device, I will provide for this month a final 17.1 build very soon. That being said, you may understand, that I will not really spend too much time any more for any issue lookup in the 17.1 build. So I would like to invite you to upgrade to 18.1 soon (once the new thread has been published).
Understood, I searched dianlujitao thread and people noticed the bug, no custom fix with adb but it looks like it was fixed later on. Will wait for your 18.1 ROM and then we can make a logcat for bugs.
 
New build with October ASB - FINAL

Hello all,
a new build is available for download and also offered as OTA update in the Updater app:
  • ASB Security string 2021-10-05
  • Bromite browser and Webview updated to 93.0.4577.83
  • The official kernel tag is still the same as last month, but I have picked the commits after the tag
As already announced earlier, this probably is the final build. I will tomorrow create a new Lineage 18.1 thread for this device and recommend you to update at your convenience. Btw, the 18.1 build with October ASB, which will be announced in the new thread, is here.

Happy flashing!
Regards, M.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Yeah your explanation pretty much answers why GNSS isnt that good. But which NLP apps do I need? Not all of them of course.
    Depends on your personal preference. I think for the address resolution, there is only Nominatim. For the Coarse location, I in fact see two options (personal opinion):

    a. With the shipped Mozilla one, you have a very good "allrounder". However, you may dislike, that it also requires internet connection, as it uses Mozilla's servers to calculate your location, based on your device's provided data. You don't need an account for that, but at least a "fingerprint" of your device is being tracked.

    b. I personally use the combo of GSM Location Provider and DéjàVu - it is less accurate, but entirely "offline".
    GSM Location provider needs to initially download cell tower data to build a database and yes, whenever you feel like it, you download an update - but the location calculation itself happens offline (after downloading the cell tower data, you can even cut the internet connection for that app, if you like). DéjàVu simply watches, when your GPS is on, locations and nearby WiFi ID's and stores, if certain combinations happen "statistically often enough", such points. Hence it learns (no internet connection!), where you are located usually and at least those points are identified with a remarkable accuracy.

    If you use coarse location for things like weather widget and/or supporting a faster initial GPS fix, "b." is sufficient.
    "a." is less effort and more accurate, but the location calculation happens at a server, which needs to keep track of your device - without account and hence somehow "pseudonymously".
    2
    How do I stop wifi from shutting down when the screen turns off stays idle?
    Could you please give a more explicit example?

    Also any tips on how to configure GPS settings? I downloaded all NLP apps from F-droid. Accuracy is 10m while OOS was around 5m.
    OOS uses, as any stock ROM, the genuine Google spy services as coarse location provider. It has to be admitted, that the accuracy is really good, but to the price of Google knowing your location at any time.
    Seems that the combo of GPS and Google's Wifi DB is able to better calibrate the location.
    Just a guess...

    I also wonder if I need to contact LOS team for GnssStatus.getCarrierFrequencyHz() API support or does the ROM follow OxygenOS code?
    The ROM is a modified LineageOS, which itself is a modified AOSP - no idea about the specifics of OOS.
    2
    But I have another issue and that is AOSP keyboard.Is suggestions Play Service based?
    No. AOSP delivers dictionaries as part of the ROM, that's it.

    Can I find a good 3 language keyboard. Its optimized for one language at the time.
    Good question, Idk - looking forward to suggestions from others as well...

    And is the idea with hardened ROM that Im supposed to lock the bootloader after installing as rooting is discouraged?
    You CAN re-lock the bootloader on the op3/t, yes. The advantage of doing so however is not huge.

    Normally, with a Stock ROM having a restricted recovery refusing to flash "non-original" stuff, a locked boot loader prevents flashing a custom recovery and hence prevents accessing and altering the data and system components of the phone, and if the BL is unlocked, the /data partition will be purged for security reasons to make sure, that e.g. the data of a stolen phone cannot be accessed by unlocking the BL and flashing a custom/special recovery.

    On this phone, I would assume you have TWRP as recovery, which will allow all, what is needed also with a locked BL, so it is important to encrypt your /data partition with a proper passphrase.

    Remains the question of apps aiming at checking the BL state - the 17.1 kernel overrides some of those flags anyhow (the 18.1 kernel of the test builds not yet). I myself doing development don't lock the BL, because for me, things like fastboot boot test-boot.img need to work.

    There still might be some advantages to lock the BL, I think @nvertigo67 has a deeper inside to this and may want to step in.

    Thankfully banking,payment and ID apps dont check root in Sweden but Android Pay,
    The root checking of banking/payment apps is anyhow only 'security theater', but it's annoying.

    Really?
    I don't have difficulties - but I only use it to access the LineageOS chat (probably very limited scope of what Slack can be used for...)
    2
    New build with October ASB - FINAL

    Hello all,
    a new build is available for download and also offered as OTA update in the Updater app:
    • ASB Security string 2021-10-05
    • Bromite browser and Webview updated to 93.0.4577.83
    • The official kernel tag is still the same as last month, but I have picked the commits after the tag
    As already announced earlier, this probably is the final build. I will tomorrow create a new Lineage 18.1 thread for this device and recommend you to update at your convenience. Btw, the 18.1 build with October ASB, which will be announced in the new thread, is here.

    Happy flashing!
    Regards, M.
    1
    LineageOS 18.1 thread
    As announced, the new LineageOS 18.1 thread has been posted.
  • 18
    This thread is dedicated to provide hardened Lineage-OS 17.1 builds with microG included for the OnePlus 3/3T with current security patches.

    It is the successor of my Lineage 16.0 thread.
    It may be worth to also look there, if you are looking for information.

    Features of this ROM
    Download here
    • Pre-installed microG and F-Droid like LineageOS for microG project (own fork)
    • Pre-installed AuroraStore
    • OTA Support
    • eSpeakTTS engine
    • Bromite as default browser
    • Additional security hardening features listed below
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
    • Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
    • Firewall UI (under Trust)
    • Increased max. password length of 64
    • No submission of IMSI/phone number to Google when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView
    • Extra control of sensor access for additionally installed user apps (Special access under app permissions)
    • Kernel kept up to date with ASB patches and Google kernel/common 'android-3.18' branch
    • Debloated from Oneplus blobs for Alipay, WeChatpay, Soter and IFAA
    • Hardened bionic lib and constified JNI method tables


    Current release levels
    Security string: 2021-10-05
    AOSP tag: 10.0.0_r41
    Bromite System Webview: M93


    Source-code and build instructions
    Kernel: https://github.com/lin17-microg/android_kernel_oneplus_msm8996/tree/lin-17.1-mse3
    Build manifest: https://github.com/lin17-microg/local_manifests/tree/lin-17.1-microG


    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 of information available.

    Pre-Requisites
    • If you come from OxygenOS Stock ROM, make sure to update to the latest offered software version (if not, no issue).
    • 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
    • An unlocked bootloader (see e.g. LineageOS install instructions)
    • OxygenOS 9.0.6 firmware, which is needed for LineageOS 17.1 - see next section
    • Download the most current .ZIP file of the ROM and place it to your phone's internal memory

    OxygenOS 9.0.6 Firmware
    If you come from my LineageOS 16.0 build - or any Android 9 or 10 based ROM, you most probably have already the proper firmware.
    And yes, LineageOS 17.1 is Android 10, but the latest firmware for this device has been published by Oneplus for Android 9.
    How to find out about your current firmware, if you use a Custom ROM:
    Connect as root via adb to your phone and enter the command adb shell cat /system/vendor/firmware_mnt/verinfo | grep Time_Stamp
    If the result is "Time_Stamp": "2019-11-04 21:25:29", you are on the latest firmware, if the date/time is earlier, you need to update the firmware. THIS THREAD has got more information for you.
    If you come from an Oreo (Android 8.x) Custom ROM, READ THE OP OF THIS THREAD CAREFULLY !
    I can't explain it better and I am not going to repeat or summarize this. It really is in your interest to carefully read it - you have been notified and warned. Please also pay attention to the last section named "Alipay, WeChatpay, Soter and IFAA" - I strongly recommend to use the debloated firmware.


    Install TWRP recovery
    If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. I recommend to use the TWRP recovery for the OnePlus 3/3T. The following instructions are based on TWRP.
    To install TWRP, download the twrp-x.x.x-x-oneplus3.img file (Note: replace "x.x.x-x" in the following instructions with the respective values from the real file name) 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-x.x.x-x-oneplus3.img
    Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and hold Power and vol.down) - DO NOT boot into 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 must 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". Swipe to confirm the deletion and get back into the main menu.

    DO NOT flash Gapps!
    This ROM comes with pre-installed microG. So don't attempt to flash Gapps.

    Install 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 our ROM and swipe to flash.
    If you update from a previous version of my ROM, including my LineageOS 16.0 build, you don't need to perform a wipe. If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
    When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 17.1 - be patient, the first boot after flashing a new ROM takes quite long!


    Dealing with signed builds
    Please note, that this builds is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash" (recommended), or - you do this on your own risk - you may try the below steps.

    This happens at your own risk - make a backup with TWRP before!
    • Download and extract the file migration.sh from this archive
    • This file helps you to migrate from a build signed with the publicly available test keys (i.e. all builds around, which do not state that they are signed). If you come from another signed build (e.g. official LineageOS), you have to adapt the file accordingly (see below links).
    • 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 and the "theory behind" can be found in the LineageOS wiki and AOSP reference.



    Bug reports:
    If you have a problem, please create a post with these informations:
    Original Kernel shipped with this rom:
    Build Date:
    And try to get log as described here
    Please note that I can't and won't support issues with builds using a different kernel or Xposed.
    In regards to microG, I will try my best to help when it is related to this ROM (I use it myself), but any questions of the type "the YXZ-app can't do <some sort of fancy xyz Google functionality> properly" are better asked in the respective microG forums.

    Credits
    AOSP project
    LineageOS project
    microG project
    Graphene OS project
    csagan5 (Bromite)
    WhyOrean (Aurora)
    nvertigo67 (for the modded 9.x firmware and for collaboration)
    9
    Change log

    2021-10-14 - FINAL

    • ASB Security string 2021-10-05
    • Bromite System Webview and Browser updated to 93.0.4577.83
    • Kernel upstreamed (note: tag equals last months tag)

    2021-09-12
    • ASB Security string 2021-09-05
    • Kernel upstreamed to tag ASB-2021-09-05_3.18
    • microG microG 0.2.22.212658-2

    2021-08-08
    • ASB Security string 2021-08-05
    • Kernel upstreamed to tag ASB-2021-08-05_3.18
    • Bromite System Webview and Browser updated to 92.0.4515.134
    • F-Droid updated to 1.13
    • Fix in WiFi randomization

    2021-07-10
    • ASB Security string 2021-07-05
    • Kernel upstreamed to tag ASB-2021-07-05_3.18
    • Bromite System Webview and Browser updated to 91.0.4472.146
    • microG 0.2.21.212158-2
    • AuroraStore 4.0.7

    2021-06-13
    • ASB Security string 2021-06-05
    • Kernel upstreamed to tag ASB-2021-06-05_3.18
    • Kernel WLAN driver (qcacld-2.0) patched to include mitigations against "Frag" vuln.
    • Bromite System Webview and Browser updated to 91.0.4472.102
    • microG 0.2.19211515-9

    2021-05-09
    • ASB Security string 2021-05-01
    • Kernel upstreamed to tag ASB-2021-05-05_3.18
    • Bromite System Webview and Browser updated to 90.0.4430.204
    • microG upstreamed (no version change)
    • Update: AuroraServices 1.1.1

    2021-04-10
    • ASB Security string 2021-04-01
    • Kernel upstreamed to tag ASB-2021-04-05_3.18
    • Bromite System Webview and Browser updated to 90.0.4430.59
    • F-Droid updated to 1.12
    • Update: AuroraStore 4.0.4 with AuroraServices 1.1.0

    2021-03-08
    • Security string 2021-03-05
    • Kernel upstreamed to tag ASB-2021-03-05_3.18
    • Bromite System webview updated to 88.0.4324.207
    • Bromite Browser updated to 88.0.4324.207
    • F-Droid 1.11
    • microG 0.2.18.204714

    2021-02-04
    • Security string 2021-02-05
    • Kernel upstreamed to tag ASB-2021-02-05_3.18
    • Bromite System webview updated to 88.0.4324.141
    • Bromite Browser updated to 88.0.4324.141
    • F-Droid 1.10-alpha-234
    • microG 0.2.17.204714-5

    2021-01-15 - Initial build
    • Pre-installed microG (0.2.16.204713-10) and F-Droid like the LineageOS for microG project (own fork)
    • Pre-installed AuroraStore
    • Bromite as default browser (87.0.4280.106)
    • eSpeak TTS engine (FOSS TTS solution)
    • Additional security hardening features listed below:
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
    • Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
    • Firewall UI (under Trust)
    • Increased max. password length of 64
    • No submission of IMSI/phone number to Google when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView (87.0.4280.131)
    • Extra control of sensor access for additionally installed user apps (Special access under app permissions)
    • Constified JNI method tables and hardened bionic lib
    7
    LineageOS 18.1

    Hi all,

    a LineageOS 18.1 test build is available here:

    It has the same features, as described in the OP for this 17.1 build, with the following additions:
    - AuroraDroid app replaces F-Droid app to access F-Droid repositories
    - Option to only use fingerprint unlock for apps and not for the device
    - Optional timeout for Bluetooth and WLAN connections
    - Some more hardening features ported from GrapheneOS
    - Kernel is based on the upstreamed kernel of this build (with many necessary adaptations for 18.1, of course)
    - Sec. string 2021-08-05

    Right now, this is still a test build, this means:
    I truly appreciate any feedback (especially, if things don't work as expected). And there definitely will be an update for 17.1 with ASB patches for September. It is possible to "dirty-flash" over this 17.1 build, but make a backup in TWRP before, to be able to get back.

    Feedback appreciated - Thanks & regards, M.

    EDIT:
    Kernel source: https://github.com/lin18-microG/android_kernel_oneplus_msm8996/tree/lin-18.1-mse2
    Build Manifest: https://github.com/lin18-microG/local_manifests/tree/lin-18.1-hmalloc

    EDIT2 (2021-08-22):
    Seems the kernel needs more rework: on my device, it always crashes after a while. If you use the "original" LineageOS kernel (e.g. extract and flash boot.IMG from an official LineageOS ROM Zip), it will work.
    7
    New build available with March ASB patches

    Hi all, new build available for download, will soon also be offered as OTA update through the Updater app.

    • Security string 2021-03-05
    • Kernel upstreamed to tag ASB-2021-03-05_3.18
    • Bromite System webview updated to 88.0.4324.207
    • Bromite Browser updated to 88.0.4324.207
    • F-Droid 1.11
    • microG 0.2.18.204714
    Happy flashing!
    Regards, M.

    EDIT: OTA update now offered through Updater app
    6
    New build available with February ASB patches

    Hi all, new build available for download, will soon also be offered as OTA update through the Updater app.
    • Security string 2021-02-05
    • Kernel upstreamed to tag ASB-2021-02-05_3.18
    • Bromite System webview updated to 88.0.4324.141
    • Bromite Browser updated to 88.0.4324.141
    • F-Droid 1.10-alpha-234
    • microG 0.2.17.204714-5
    Happy flashing!
    Regards, M.