LineageOS 19.1 (Android 12L) [Signature Spoofing][OTA updates] for S7 Exynos
- Thread starter Ivan_Meler
- Start date
Hi,
Thank you for your response.
I am on NikGapps, I will follow your post in the Magisk thread.
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 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!
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.
Maybe sorry for this stupid question.
How about Always on Display. Work this with LOS and this Rom?
How about Always on Display. Work this with LOS and this Rom?
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?
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:
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:
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 !
@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.
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 (
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:
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:
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
- 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.
Try BiTGApps which are advised here in the thread .... you need ARM64 for
Android 12 v1.6/BiTGApps-arm64-12.0.0-R45_signed.zip click : you'll get a black page but your download starts. Enjoy !
Apparently just flash over one of these: https://sourceforge.net/projects/nikgapps/files/Releases/NikGapps-S/27-Jan-2022/
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5Here we go, March security update is here.
LineageOS 21 builds wont get update this time around as new qpr is still being merged and fixed up
There were a lot of changes from google in their quarterly platform update soboth LineageOS codebase
and some device changes are needed for it to be on par with previous builds.
There will be april builds for it soon so it made no sense to push half baked update today.
As always huge thanks to everyone who donated to help cover the build server cost.
This project wouldnt be possible without you.
Enjoy new builds and stay safe2April security update is here, nothing more to it this time around
Unfortunately as you might have noticed patches were posted a bit later past 2 months due my schedule
Ill also fix Lineage 21 qpr merge in coming days and release update for those builds too, there were tons of changes in qpr that turned out to be a bit problematic
As alwasy huge thanks to everyone who supported this project and helped cover the build server cost.
Enjoy new builds and stay safe -
73
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: 640895066fdb4b0ac2b76345ca69714a
if you want to support the project feel free to buy me some coffee http://paypal.me/melerivan
BTC: 1Q823BsSbEKP62JFM7BjXiRCgF84qgcFST
ETH(erc20): 0x979a8e42551e62e6994d3762c9d9f0e76b5d87f9
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
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: Stable27Ill just leave this here, Yep its already happening
Most of stuff is working but ill need to do some cleanup before posting this
Some lineageos featues are missing but most have already been merged
Once again huge thanks to everyone who supported this project and helped cover build server cost with donations and also got me coffee this project wouldnt be possible without them
see you soon with latest android version on 6 and a half old phone
24here it is August security update
Nothing major in this one as i am still working behind the scenes on that huge update i talked about previously which involves rewrite of almost whole graphics and media stack (its almost finished but i still have to do a bit more testing just to make sure there is no regression)
In other news android 13 should be released next month and since there were no major changes s7 should be running it soon after release with not too many issues and ill try to take a few days off from work to get it up and running on it once source is out
Once again huge thanks to everyone who supported this project, helped cover build server cost and got me coffee with donations.
This project wouldnt be alive without them as i do this in my free time as a hobby.
Enjoy new builds and stay safe23Since 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 safe22New build is up, here is a brief changelog
- Merged July 2022. Security update
- Fixed more keystore issues
- Synced with LineageOS source
Also some important news, Exodusnick decided to provide huge help and he bought and shipped s7 to me which should be here next week, so all of exciting updates i talked about last week should be way easier to achieve and this will make testing and developement a lot easier, Once again huge thanks to him.
Also big thanks to donators that helped to cover build server cost and got me coffee which helped to keep this project up and running.
Thanks to this s7 should live for few more android releases without any major issues. and Android 12 will get even better with new hals that are curently in developement
There will be updates to 18.1 and 17.1 in a few days once july security updates have been ported to them
Enjoy new build and stay safe
New posts
-
-
-
What programming language do Android developers use??- Latest: sabelacarson
-
