LineageOS 19.1 (Android 12L) [Signature Spoofing][OTA updates] for S7 Exynos

Search This thread

lebon00

Member
Apr 13, 2010
11
3
Hi,

First thank you to Ivan for this great ROM.

Is anyone having success to pass the safetyNet on this ROM.

The basic integrety pass but not the CTS profile match.

1- I have Magisk 24.1(24100) with Zygist enable and DenyList
2- MagiskHide Props config module by Didgeridoohan and Universal SafetyNet Fix 2.2.1 module by kdrag0n.

When I try to add Google Play Services to the deny list with com.google.android.gms and com.google.android.gms.unstable activate, those activations are removed after a reboot.

Can someone put me in the right direction or tell me what I am doing wrong.

Thank you very much!
 

xabu

Senior Member
Hi,

First thank you to Ivan for this great ROM.

Is anyone having success to pass the safetyNet on this ROM.

The basic integrety pass but not the CTS profile match.

1- I have Magisk 24.1(24100) with Zygist enable and DenyList
2- MagiskHide Props config module by Didgeridoohan and Universal SafetyNet Fix 2.2.1 module by kdrag0n.

When I try to add Google Play Services to the deny list with com.google.android.gms and com.google.android.gms.unstable activate, those activations are removed after a reboot.

Can someone put me in the right direction or tell me what I am doing wrong.

Thank you very much!
The New Magisk

This Rom is not made for Magisk and Magisk is not made for this ROM .... Please study in the link above and make your choices.
 
Last edited:

bgsdeluxe

Senior Member
Feb 23, 2013
131
40
Hi,

First thank you to Ivan for this great ROM.

Is anyone having success to pass the safetyNet on this ROM.

The basic integrety pass but not the CTS profile match.

1- I have Magisk 24.1(24100) with Zygist enable and DenyList
2- MagiskHide Props config module by Didgeridoohan and Universal SafetyNet Fix 2.2.1 module by kdrag0n.

When I try to add Google Play Services to the deny list with com.google.android.gms and com.google.android.gms.unstable activate, those activations are removed after a reboot.

Can someone put me in the right direction or tell me what I am doing wrong.

Thank you very much!
Good point, thanks for bringing this up.
I ran into exact same issue, although I'm not using the MagiskHide Props config module. I realized that Google Play Services have been set to default, but after deleting app cache and settings everything was fine, so I forgot about it. Now that I read your post I checked again and it is removed once more.
Already checked discussion thread on Magisk and posted a request in the new thread dedicated to Zygisk:
Btw.: Are you using BitGapps?
Apps other than system apps are still in hidelist in my case, even after reboot.
 
Last edited:

lebon00

Member
Apr 13, 2010
11
3
Good point, thanks for bringing this up.
I ran into exact same issue, although I'm not using the MagiskHide Props config module. I realized that Google Play Services have been set to default, but after deleting app cache and settings everything was fine, so I forgot about it. Now that I read your post I checked again and it is removed once more.
Already checked discussion thread on Magisk and posted a request in the new thread dedicated to Zygisk:
Btw.: Are you using BitGapps?
Apps other than system apps are still in hidelist in my case, even after reboot.
Hi,

Thank you for your response.

I am on NikGapps, I will follow your post in the Magisk thread.
 

lebon00

Member
Apr 13, 2010
11
3
Hi,

I have a problem involving the ROM itself, I have noticed that the sound coming out from the top speaker (ear phone speaker) is crakling and weird when on a call.

The sound coming from the bottom speaker is fine.

And people on the other end is hearing me fine without any crakle.

I upgraded from LOS17.1 and in LOS17.1 the sound was fine.

Any thoughts.

Thanks!
 

Zuikkis

Senior Member
Nov 20, 2013
90
32
Hi,

First thank you to Ivan for this great ROM.

Is anyone having success to pass the safetyNet on this ROM.

The basic integrety pass but not the CTS profile match.

1- I have Magisk 24.1(24100) with Zygist enable and DenyList
2- MagiskHide Props config module by Didgeridoohan and Universal SafetyNet Fix 2.2.1 module by kdrag0n.

When I try to add Google Play Services to the deny list with com.google.android.gms and com.google.android.gms.unstable activate, those activations are removed after a reboot.

Can someone put me in the right direction or tell me what I am doing wrong.

Thank you very much!

As I said some messages earlier, SafetyNet passes with Magisk v23.

I see Magisk is now offering the 24 update, but I'm afraid to do it until I hear some success stories first. :)
 

pawpawel

Senior Member
Jul 3, 2014
99
10
Siedlce
Witam, ktoś mi powie jak naprawić wyświetlacz telefonu i pamięć karty.
Więc użyłem karty sd jako pamięci wewnętrznej, ale w twrp widzę pamięć telefonu, karty nie ma, w komputerze widzę kartę i jakiś uchwyt pamięci z folderem twrp, jak to naprawić?

Translated by GT:
Hello, someone will tell me how to fix the phone display and card memory.
So i used sd card as internal memory but in twrp i can see phone memory, card is gone, i see card in pc and some memory stick with twrp folder, how to fix it?
 
Last edited by a moderator:

xabu

Senior Member
Witam, ktoś mi powie jak naprawić wyświetlacz telefonu i pamięć karty.
Więc użyłem karty sd jako pamięci wewnętrznej, ale w twrp widzę pamięć telefonu, karty nie ma, w komputerze widzę kartę i jakiś uchwyt pamięci z folderem twrp, jak to naprawić?
Try to safe your data which are possibly placed on the internal sdcard. Do this via backup or move them onto the external sd-card and after that reflash TWRP over the old same one, which should be twrp-3.6.0_9-0-herolte.img or tar ....hope this might help you.
 
Last edited:

mnsr

New member
Dec 24, 2021
1
0
Hi,

I have a problem involving the ROM itself, I have noticed that the sound coming out from the top speaker (ear phone speaker) is crakling and weird when on a call.

The sound coming from the bottom speaker is fine.

And people on the other end is hearing me fine without any crakle.

I upgraded from LOS17.1 and in LOS17.1 the sound was fine.

Any thoughts.

Thanks!
I've got the same problem. Updated from LOS 19 a few days ago and call quality got pretty bad... Hope that can be fixed @Ivan_Meler ? Would be great !
 

ttmob4

Senior Member
Nov 1, 2007
75
22
@Ivan

As ever the latest ROM is pretty smooth and everything I do on the phone works brilliantly (I have 197 apps and only 1 does not work (My Audi) – not a banking app).

I am wondering on the best way to load BiTGapps – standard or Systemless.

Currently I have your latest build (27th January...typo I have the 28th January build), latest BiTGapps (R45 with Gearhead and Assistant (R33 Add on)) latest Magisk 24.1 with 2 magisk modules (kdrag0n/safetynet-fix v2.2.1 (Zygisk) and VIPER4AndroidFX). Rootbeer gives successful non-rooted status and all my banking apps are fine. The question is because I moved from NikGApps to BiTGapps, I cleared data, loaded the 27th Jan ROM, then magisk and used Migrate to copy all apps across (having taken a full back up before starting) – which took a while to check all apps were ok. BiTGapps when I did this was NOT Systemless.
So...is there any advantage/disadvantage loading BiTGapps (and addons) as Systemless (so it runs as a Magisk module I understand?) - e.g. In the future can I dirty flash LOS and then just load Magisk and its modules on top and not have a bootloop and then loading updates to BiTGapps will be independent from loading the ROM?

Sorry if the above is a dumb question – it is not obvious when reading the many threads on XDA re Los19/BiTGapps…only been looking at Phones and ROMs for years but have only since COVID actually loaded anything onto my S7.
 
Last edited:

xabu

Senior Member
@Ivan

As ever the latest ROM is pretty smooth and everything I do on the phone works brilliantly (I have 197 apps and only 1 does not work (My Audi) – not a banking app).

I am wondering on the best way to load BiTGapps – standard or Systemless.

Currently I have your latest build (27th January), latest BiTGapps (R45 with Gearhead and Assistant (R33 Add on)) latest Magisk 24.1 with 2 magisk modules (kdrag0n/safetynet-fix v2.2.1 (Zygisk) and VIPER4AndroidFX). Rootbeer gives successful non-rooted status and all my banking apps are fine. The question is because I moved from NikGApps to BiTGapps, I cleared data, loaded the 27th Jan ROM, then magisk and used Migrate to copy all apps across (having taken a full back up before starting) – which took a while to check all apps were ok. BiTGapps when I did this was NOT Systemless.
So...is there any advantage/disadvantage loading BiTGapps (and addons) as Systemless (so it runs as a Magisk module I understand?) - e.g. In the future can I dirty flash LOS and then just load Magisk and its modules on top and not have a bootloop and then loading updates to BiTGapps will be independent from loading the ROM?

Sorry if the above is a dumb question – it is not obvious when reading the many threads on XDA re Los19/BiTGapps…only been looking at Phones and ROMs for years but have only since COVID actually loaded anything onto my S7.
Is it possible you missed the 28 Jan version ?

You should run Bitgapps in the most common way as normal apps, flashing them together with the Rom in one zip .... not difficult to find in the thread how you can do this.
 

ttmob4

Senior Member
Nov 1, 2007
75
22
Is it possible you missed the 28 Jan version ?

You should run Bitgapps in the most common way as normal apps, flashing them together with the Rom in one zip .... not difficult to find in the thread how you can do this.
I cannot type....I have the 28th version...(just edited the original post as I was hoping Ivan would be able to advise if the are LoS issues with BiTGapps as systemless).
All is working fine with BiTGapps combined in 'system' with LoS 19. The question I have is about Los 19...dirty update IF BiTGapps is loaded as Systemless through bitgapps-config.prop...sorry for the misinformation in my first thread...
 
Last edited:
  • Like
Reactions: xabu

jamboss

Senior Member
Sep 17, 2013
2,018
502
I have magisk 24.1 installed and no issues with Google play services, banking app etc. I did have to download the latest version of bitgapps.
 
  • Like
Reactions: xabu

headzy

Senior Member
Dec 9, 2009
98
56
I cannot type....I have the 28th version...(just edited the original post as I was hoping Ivan would be able to advise if the are LoS issues with BiTGapps as systemless).
All is working fine with BiTGapps combined in 'system' with LoS 19. The question I have is about Los 19...dirty update IF BiTGapps is loaded as Systemless through bitgapps-config.prop...sorry for the misinformation in my first thread...
Maybe I am misunderstanding your question, but when you want to dirty flash rom update, you have to add bitgaps in 'queue' in twrp everytime, otherwise get bootloop.
 

ttmob4

Senior Member
Nov 1, 2007
75
22
Maybe I am misunderstanding your question, but when you want to dirty flash rom update, you have to add bitgaps in 'queue' in twrp everytime, otherwise get bootloop.
Thanks - like you I have always, in TWRP, on a dirty flash loaded the gapps package after the Rom and before rebooting into system. I did this on (and have done for the last 18 months using NikGapps and recently BiTGapps)...no issues also loading Magisk (previsouly V23 and now V24.1) and passing safety net (checked with rootbeer).
The query I have is on reading the Wiki for BiTGapps as implies using "System less installation" that the ROM loading and the gapps loading can be separated (hence my confusion - as I thought this caused a bootloop). The wording I was reading is as follows in the BiTGapps wiki...

How to install from recovery

Before first boot

  • Install ROM
  • Install Magisk
  • Reboot to recovery
  • Install Recovery Tool
  • Install Config Remover
  • Install BiTGApps/Addon Package
After first boot

  • Install ROM
  • Install Magisk
  • Reboot to system
  • Install Magisk APK
  • Reboot to recovery
  • Install Recovery Tool
  • Install Config Remover
  • Install BiTGApps/Addon Package

The implication (perhaps I am misreading) is that the ROM can be updated separately from the GAPPS (As this is a "systemless" [Reboot to System is before any Gapps package is loaded?] loading of the BiTGapps but I am guessing that on the "after first boot" when the install magisk is done and data has not been deleted this somehow avoids the bootloop? The rest of the instructions then implies that BiTGapps packages can then be upgraded separately. In order to underake the above BiTGapps needs a config file to tell it to load System less...and again as I am "new" to this do not understand the advantages / disadvantages of going systemless. Apologies I remain confused...but at least I have a fully working system...even if if is a bit of a pain when changing which gapps package goes with the ROM.
 

headzy

Senior Member
Dec 9, 2009
98
56
Thanks - like you I have always, in TWRP, on a dirty flash loaded the gapps package after the Rom and before rebooting into system. I did this on (and have done for the last 18 months using NikGapps and recently BiTGapps)...no issues also loading Magisk (previsouly V23 and now V24.1) and passing safety net (checked with rootbeer).
The query I have is on reading the Wiki for BiTGapps as implies using "System less installation" that the ROM loading and the gapps loading can be separated (hence my confusion - as I thought this caused a bootloop). The wording I was reading is as follows in the BiTGapps wiki...

How to install from recovery

Before first boot

  • Install ROM
  • Install Magisk
  • Reboot to recovery
  • Install Recovery Tool
  • Install Config Remover
  • Install BiTGApps/Addon Package
After first boot

  • Install ROM
  • Install Magisk
  • Reboot to system
  • Install Magisk APK
  • Reboot to recovery
  • Install Recovery Tool
  • Install Config Remover
  • Install BiTGApps/Addon Package

The implication (perhaps I am misreading) is that the ROM can be updated separately from the GAPPS (As this is a "systemless" [Reboot to System is before any Gapps package is loaded?] loading of the BiTGapps but I am guessing that on the "after first boot" when the install magisk is done and data has not been deleted this somehow avoids the bootloop? The rest of the instructions then implies that BiTGapps packages can then be upgraded separately. In order to underake the above BiTGapps needs a config file to tell it to load System less...and again as I am "new" to this do not understand the advantages / disadvantages of going systemless. Apologies I remain confused...but at least I have a fully working system...even if if is a bit of a pain when changing which gapps package goes with the ROM.
Oh I see, no idea why they advise this way, I just follow Ivan's instructions and everything works great.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    And here we go as prommised, new build with improved in call audio quality and June security update
    - Merged June 2022. security update
    - Merged June 2022. pixel feature drop (SQ3A.220605.009.A1)
    - Improved in-call audio quality drastically
    - Addressed few more selinux denials
    - Improved general stability and performance
    - Cleaned up source
    - Synced with LineageOS source

    Once again huge thanks to everyone who supported this project, helped cover the build server cost and got me a coffee, this project wouldnt be possible without support of the comunity and s7 wouldnt still be running latest OS with latest security updates over 6 years after launch

    18.1 and 17.1 builds will be out over the coming days
    Enjoy new build and stay safe
    19
    New update will fix in call audio quality
    there was a weird bug in audio hal that was causing it.

    Big thanks to @Bujiraso for playing with props and audio configs which at the end lead me to finding bug in audio hal.

    Now im only waiting for google to push June security update source so I can start compiling builds and release them
    15
    New builds are up here and via ota
    - Fixed issues with keystore present in a lot of bank/secure apps like binance
    - Fixed issue where setupwizard would crash when adding fingerprint due to bug in keystore
    - Cleaned up patches required for build and removed unneeded ones
    - Synced with LineageOS source

    This was one of hardest things to track down and it prevented some security related apps from working, big thanks to everyone who supported this project and got me coffee (This took over a month on and off time to debug and figure out, one of weirdest error caused by googles keystore changes in android 12) and thanks to those who helped cover the build server cost

    Enjoy new build and stay safe
    5
    Yes, I read the post, but I don't see you saying how to root...
    Just download magisk and flash it in recovery i didnt post guide because eevryone should know how to do that i guess, if not i dont see how one would even end up with a custom rom
    2
    I was able to do it friend, I think the problem is that it has to be the latest version of TRWP and the latest version of magisk, otherwise it won't work, anyway thanks for the help! 🙏
  • 62
    k5tUT1V.png

    LineageOS 19.1 for herolte

    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    Working:
    - Wifi
    - Sound
    - mali drivers
    - USB tethering
    - HW Backed video Playback
    - Ril (Mobile data,calls, sms and stuff)
    - Sensors
    - Buttons
    - Bluetooth
    - Wifi HotSpot
    - MTP
    - 2D and 3D gpu acceleration
    - HW encoding/decoding
    - HWcomposer (HWC)
    - Charging with device powered off
    - Stuff I didn't test yet
    - Camera
    - GPS
    - Fingerprint Sensor
    - Mobicore
    - SW codecs

    Not Working
    -


    Keep in mind that some LineageOS features have not been completed yet this is not a device bug and please do not report those
    in this rom thread, also do not post bug reports for known issues or bug reports without proper
    a) Logcat
    b) proc/last_kmsg (or proc/kmsg)
    c) data/tombstones
    d) dmesg



    Install gapps right after installing the rom itself don't try to boot to system before that if you want to use gapps (Or wipe data before installing them)

    Make sure gapps you decide to use support android 12L/12.1/Are targetting api level 32
    Also make sure you are using latest official TWRP before installing rom older versions do not have proper android 12 support

    If you want to use Magisk use latest Magisk Beta (25.0) or Magisk 24.1, there is bug in 24.3 that was fixed after its release that prevents zygisk from working on some devices with 3.18 kernel

    Downloads:
    Google Drive
    Mega.nz
    GitHub Releases
    MD5: 91b6a3fbc9717b46e9a2bce054af10b6


    if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler

    BTC: bc1qqan6m5tn284g38tu52nalc9x5z4all8z5geq6y
    ETH(erc20): 0xB737100035a989fA9EaD13B81af2a32EFe6E1C0f
    Donations help cover the build server cost and since I do this in my free time, and also cover the coffee for time spent debugging stuff



    Feel free to join telegram group with early builds progress updates and some off topic stuff Join

    Based On Android 12L/S
    Changelog

    24.06.2022.
    - Fixed issues with keystore present in a lot of bank/secure apps like binance
    - Fixed issue where setupwizard would crash when adding fingerprint due to bug in keystore
    - Cleaned up patches required for build and removed unneeded ones
    - Synced with LineageOS source

    07.06.2022.
    - Merged June 2022. security update
    - Merged June 2022. pixel feature drop (SQ3A.220605.009.A1)
    - Improved in-call audio quality drastically
    - Addressed few more selinux denials
    - Improved general stability and performance
    - Cleaned up source
    - Synced with LineageOS source

    26.05.2022.
    - Updated libexynosdisplay from BSP to comply with some android 12 changes
    - Removed unused build.prop entries
    - Fixed few selinux denials related to hwc props
    - Improved UI performance and stability
    - Cleaned up source
    - Removed more unneeded patches for device support
    - Synced with LineageOS source

    18.05.2022.
    - Added QR code reader quick settings toggle
    - Improved device performance and stability
    - Added Custom low power mode power profile for cpu
    - Improved A-GNSS (A-GPS) Lock speed
    - Exposed device hw revision to settings
    - Improved fast/slow charger detection
    - Synced with LineageOS source

    10.05.2022.
    - Switched to new libperfmgr power hal which can be configured from /system/vendor/etc/powerhints.json
    - Adapted DT2W to new power hal
    - Muted phone services gps notif (Thanks google really appreciate you breaking random things for everyone)
    - Improved battery life and performance
    - Cleaned up all of leftover patches that were used by legacy power hal
    - Synced with LineageOS source

    07.05.2022.
    - Improved battery usage logging for display
    - Added QR code reader to camera app (Long hold icon and launch it from context menu)
    - Misc performance and stability improvements
    - Merged May 2022. security update
    - Synced with LineageOS source

    27.04.2022.
    - Removed libbfqio dependency from hwc since it was dropped from lineageos 19.1
    - Misc performance and stability improvements
    - Synced with LineageOS source (same base as official builds + some extras)

    18.04.2022.
    - Fixed bug wehre vibrations were too low on some devices due to inintensity being set to 0
    - Fixed bug where apps would show square popup "animation" when launching from icon instead of roudned one
    - Cleaned up build patches
    - Synced with LineageOS source

    15.04.2022.
    - Updated sepolicy and merged updated common samsung_slsi sepolicy
    - Increased microphone gain while recording media (Camcorder, voice recording etc.)
    - Added option to disable vibration feedback on fingerprint auth
    - Synced with LineageOS source

    08.04.2022.
    - Fixed extended volume panel
    - Updated icons for few more stock apps
    - Cleaned up patches further
    - Misc peroformance improvements
    - Synced with LineageOS source

    06.04.2022.
    - Merged April 2022. Security update
    - Enabled new LineageOS icons (you might have to clear launcher cache for them to show up)
    - Fixed issue where galery app would show black text on black background
    - Fixed issue where unlock sound would sometimes play twice
    - Misc performance and stability improvements
    - Synced with LineageOS source

    29.03.2022.
    - Drastically speed up app launch time (more info about that here)
    - Imrpoved performance and battery life by disabling some unnecessary logging
    - Switched to source built camera provider and removed samsung proprietary one
    - Upreved camera provider to 2.5
    - Fixed few selinux denials related to NFC trying to raad debug props
    - Removed floating_feature.xml which is unused on aosp
    - Disabled livedisplay by default
    - Cleaned up extra dependencies used for compiling
    - Synced with LOS source

    22.03.2022.
    - Added back configurable audio volume panel location
    - Speed up unlock with fingerprint
    - Updated a lot of apps to MaterialYou design language
    - Fixed issue where touch screen area bellow home button would act as a gesture area even while gestures are disabled
    - Improved stability of ADB connection
    - Implemented new LineageOS setupwizard
    - Cleaned up device tree and list of required patches
    - Stability and performance improvements
    - Pointed Changelog url in updater app to new page
    - Synced with LineageOS source

    14.03.2022.
    - Fixed issue with keystore where apps would crash when invoking it (Security related apps mostly like signal and a lot of work apps)
    - Officially rebranded as 19.1
    - Updated changelog URL in updater app to point to a valid changelog
    - Fixed battery icon styles (Again..)
    - Removed invalid zram config.
    - Cleaned up source
    - Performance and stability improvements
    - Updated some stock apps to math with new design
    - Synced with LineageOS source

    10.03.2022.
    - Merged March 2022. security and feature updates (Android 12L)
    - Fixed status bar network trafic monitor
    - Improved zram performance and enabled zram writeback
    - Cleaned up patches needed for build
    - Fixed network usage monitoring
    - Fixed per app network restrictions
    - Removed AudioFX which was causing issues
    - Decreased microphone and earpiece gain a bit to mitigate in-call issues
    - Updated some device control apps like advanced display settings
    - Improved vibrator intensity in new hal
    - Imrpoved fp sensor response time
    - A lot of 'under the hood' changes
    - Performance improvements
    - Merged more previously missing los features
    - Implemented OTA updates

    10.02.2022.
    - Merged February 2022. security update
    - Removed broken volume button location toggle
    - Synced with LOS source

    09.02.2022.
    - Fixed issue where camera would stop working after prolonged use
    - Misc performance and stability improvements
    - Merged some more lineageos features that have been posted to gerrit
    - Synced with LOS source

    28.01.2022.
    - Fixed developer options crashing on launch
    - Added Bluetooth SBC Dual Channel HD audio mode
    - Synced with LOS source

    27.01.2022.
    - Added back lineageos setup wizard present on clean installs
    - Merged some of previously missing features that have been ported over to LineageOS 19
    - Performance and stability improvements
    - Synced with LOS source

    18.01.2022.
    - Enabled selinux (Its enforcing now)
    - Moved audio hal to vendor
    - Fixed confirmation dialog box for button backlight
    - Fixed ok button which would go missing for button backlight
    - Switched to source built secril_config_svc (used for ds detection)
    - Removed obsolete debug.sf.disable_backpressure prop
    - Merged latest security updates to kernel from aosp kernel/common
    - Cleaned up source
    - Cleaned up unused props
    - Removed unused custom ld.config.txt that was overriding main one
    - Misc performance and stability improvements
    - Synced with LOS source

    06.01.2022.
    - Removed duplicate props in vendor and system
    - Cleaned up device tree code
    - Switched to source built camera provider lib
    - Switched to few source built ril related libs
    - Addressed more selinux denials
    - Fixed volume panel location settings
    - Added button backlight
    - Added Advanced Reboot
    - Added LiveDisplay entry into settings
    - Added system side toggle for navigation bar
    - Merged January 2022 Security Update
    - Merged most of previously missing LineageOS features
    - Misc performance and stability improvements
    - Synced with LOS source


    20.12.2021.
    - Fixed wireless display
    - Reduced logspam which should imrpove performance a bit
    - Misc performance and stability improvements
    - Synced with LOS source

    16.12.2021.
    - Merged r18 tag of Android 12 (SQ1D.211205.016.A1)
    - Removed liboemcrypto which was preventing drm playback in some apps
    - Synced with LOS source

    13.12.2021.
    - Updated Clearkey to 1.4
    - Addressed most of selinux denials
    - Switched to new AIDL Lights hal
    - Upreved audio hal to 7.0
    - Switched to new AIDL Vibrator hal
    - Disabled configstore which got replaced with props
    - Upreved fingerprint hal/service to 1.3
    - Removed unused kernel defconfig flag
    - Synced with LOS source

    09.12.2021.
    - Merged December 2021. Security update
    - Merged December 2021 pixel feature drop
    - Added signature spoofing support which can be used to add microg instead of gapps
    - Merged a lot of lineageos features that have been implemented
    - Fixed bluetooth sample rate while in call
    - Moved device specific ueventd rules to /system/vendor/etc
    - Freed up some ram
    - performance and stability improvements

    30.11.2021.
    - Initial release



    XDA:DevDB Information
    LineageOS 19.0 for S7, ROM for the Samsung Galaxy S7

    Contributors
    Ivan_Meler
    Source Code: https://github.com/8890q/android_kernel_samsung_universal8890/tree/lineage-19.0

    ROM OS Version: Android 12L
    ROM Kernel: Linux 3.18.x

    Version Information
    Status:
    Stable
    23
    Since my birthday is tomorrow I decided to release a little surprise build. Here is a brief changelog:
    - Updated libexynosdisplay from BSP to comply with some android 12 changes
    - Removed unused build.prop entries
    - Fixed few selinux denials related to hwc props
    - Improved UI performance and stability
    - Cleaned up source
    - Removed more unneeded patches for device support
    - Synced with LineageOS source

    Im aware of Seedvault issue curently present and im working on a fix for it.
    I wanted to release something as a gift from me to everyone using this rom and supporting this project throughout the years. Keeping older phones alive and up to date is really fun hobby and I don't think I would've kept doing it if it wasnt for all of the support from the comunity.

    Once again big thanks to everyone who helped cover the build serve cost and coffee.

    Enjoy new build and stay safe
    21
    And here we go as prommised, new build with improved in call audio quality and June security update
    - Merged June 2022. security update
    - Merged June 2022. pixel feature drop (SQ3A.220605.009.A1)
    - Improved in-call audio quality drastically
    - Addressed few more selinux denials
    - Improved general stability and performance
    - Cleaned up source
    - Synced with LineageOS source

    Once again huge thanks to everyone who supported this project, helped cover the build server cost and got me a coffee, this project wouldnt be possible without support of the comunity and s7 wouldnt still be running latest OS with latest security updates over 6 years after launch

    18.1 and 17.1 builds will be out over the coming days
    Enjoy new build and stay safe
    20
    New builds are up mainly to bring them inline with official lineageos 19.1 builds when it comes to features, here is a brief changelog
    - Removed libbfqio dependency from hwc since it was dropped from lineageos 19.1
    - Misc performance and stability improvements
    - Synced with LineageOS source (same base as official builds + some extras)

    Big thanks to everyone who supported this project so far and helped me cover the build server cost with donations and also got me coffee
    Enjoy new builds and stay safe
    19
    Well here we go first build of the year, andquite a big one while at it
    Here is a brief changelogbut there are a lot more changes you will discover in this build
    - Removed duplicate props in vendor and system
    - Cleaned up device tree code
    - Switched to source built camera provider lib
    - Switched to few source built ril related libs
    - Addressed more selinux denials
    - Fixed volume panel location settings
    - Added button backlight
    - Added Advanced Reboot
    - Added LiveDisplay entry into settings
    - Added system side toggle for navigation bar
    - Merged January 2022 Security Update
    - Merged most of previously missing LineageOS features
    - Misc performance and stability improvements
    - Synced with LOS source

    Updates for Android 11 and 10 should be out next week

    About camera, As some of you might be aware camera tends to crash afterprolongued use, Im investigatinga fix for it but due to nature of issue itself it might take time
    to figure this out completely and what the best way to deal with it is.

    Andfinally huge thanks toeveryonewho supported this and other projects of mine so far as they help me cover the build server cost and get me a coffee with their donations, 2022 marks 5 years since release of s7 and im glad i can help in keeping them alive on latest android version with latest security updates
    Hope you all had great holidays, Enjoy new build and stay safe in 2022