yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] netra3441:
Yes... and you were and you are right with that, @Ivan_Meler

Its a real experience: my Samsung Galaxy S7 smartphones - I own two of them - work much better, faster without the Google stuff.

And I really do not need the Google stuff: no Google Pay, no GSF, and the very most apps, I load from Google Play Store via Aurora, work perfectly without that GSF (Google Ssystems Framework).

But beeing honest: so much apps I do not use from Google Play Store anymore. Mostly I use apps from Fdroid.

On my humbly opinion there are arround 99% crap apps in Google Play Store.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] netra3441:
Well... when I want to use an app, I always contact the coder directly and ask, how to pay, but tell him/her, that I do not have GSF, so no payment via Google Pay.

All coders, I had contact with, had other possibilities to pay, there was no one, who was surprised, that I have no GSF and so no Google Pay...

Additionally I can pay via Google Pay, but just by using my Linux PC and the Google Pay website.

But I never more will do any money matters with my smartphone - mobile units are unsafe units, so not made for serious usage, f.e. money matters.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] SLAYER96:
No coders that value privacy uses Google play anymore, there is just f-droid and the page that host their source code to download the app, to support them you can donate as you want without throwing money to Google...

That said, the rom without Google is really good, I've been using it as my second device and the battery usage is amazing, with really low usage, connected to wifi, no battery saver and It lasted more than a week!

I also kept the connectivity logs and there's no weird calling home function from preinstalled apps, cut the Google, cut the problem. Just the GPS still uses the Google address for the SUPL, change it with the grapheneos one or another with magisk is really simple but would be nice to have an alternative as default
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Razer(x):
I just need Google Pay, can I use it without installing other GAPPS?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] SLAYER96:
No, Google pay depends on other gapps and as far as I know there's no way to do it
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Not_Rich:
Well after flashing roms for maybe three years or so, FloydQ, your builds of Lineage 18,19 and 20 all with Gapps, like you I cannot get by without them. This battery drain issue hit me on Lineage 20 after installing Super Status Bar, I am not blaming the play store app, it just seems gapps break all of a sudden. I Wiped and went back to '19 all good with that Rom
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] jerrygardener7:
Using 19.1 with my S7 and I am very happy and appreciate the great work. I update from 18.0.

But as already mentioned Edge Forum for Lineage 19.1 (https://xdaforums.com/t/lineageos-1...ta-updates-for-s7-edge-exynos.4369001/page-38) I also have difficulties with my wireless headphones. Listening to music and videos is no problem but via calling I can not establish a connection (just hizzing noises and caller and person called can't hear each other).

Any help (developper settings? app settings? redo the installation?

Headphones connected via cable do the work. And it worked with 18.0.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Peter_Petersen:
i have the same issue. some apps are using the notification led and some apps do not.

does anybody has a solution or idea what can i do?

It afects in LOS 16, 17, 18, 19 but not in LOS 14.1
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] netra3441:
My experience with LineageOS 19 after returning from 20

I had LineageOS 20 running on my two Samsung Galaxy S7s for a long time because I thought the more up-to-date the better.

But since in LineageOS 20 (= Android 13) you can no longer format the SD card as internal storage, and I missed that a lot over time, I went back to LineageOS 19 (= Android 12) two weeks ago.

And what can I say: 19 runs smoother and more stable than 20, everything works fine, I'm very satisfied.

It is probably the case that the two Galaxy S7 run very stably up to Android 12 or LineageOS 19, but from Android 13 (LineageOS 20) it may become too stressful for the older hardware.

But maybe that's just subjective. It should also be mentioned that of course I work without *Gapps, so my S7 are also GSF-free (without any Google stuff) under LineageOS 19.

Anyway, many thanks to everyone who makes LineageOS, many thanks also to everyone who makes XDA, and many thanks of course to @Ivan_Meler

And if I should have forgotten anyone: many thanks to you too!

Because for someone like me, who is unfortunately severely disabled and therefore lives on a very small pension, it is very helpful and good if you don't have to save yourself a new expensive smartphone from the mouth, but buy older used ones and with that and thanks to LineageOS a lot can save costs.

Long live LineageOS and XDA and @Ivan_Meler

And I wish you all here on XDA a nice weekend!

(written at currently 34 degrees Celsius... I am a human and not a damn bread dough that has to go in the fu..ing hot oven..)

Yeah! ;)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] raile:
Yes, I orignally made the plunge about a week ago from stock S7 ROM to LineageOS 20 (because like you said, the more up-to-date the better). I also didn't like not being able to use my SD card the way I'd like, but more importantly the battery life was horrible for some reason. I downgraded to LineageOS 19.1 the next day and I couldn't be happier with how 19.1 is performing. 1000000 thank yous to Ivan for maintaining this ROM!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] netra3441:
Well... the battery drain is a problem, what *Gapps might cause... if you have installed some *Gapps, because you want to use Google Systems Framework (GSF), then it can be, that your battery gets low quickly. With LOS 20, but also with 19.

I dont use GSF, because I do not have installed any *Gapps... this is really not necessary for using the smartphone properly...
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] raile:
I do use Google apps, and the battery drain is severe with LOS 20, much more quickly than with 19.1. With LOS 19.1 the battery usage is equivelent (if not better than) stock S7 firmware
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Ivan_Meler:
September builds are out, You can get them from this thread of via OTA update.

18.1 and 20.0 builds will be out next week hopefully.

As you might also know Android 14 release is nearing, from what i know so far it will require more BPF backports which ill try to work around till we get more recent of a kernel running on exynos 8890

So s7 will live to see yet another android version, other than that there shouldnt be major changes needed.

As always huge thanks to everyone who supported this project, Helped cover the build server cost and got me coffee.

Enjoy new builds and stay safe
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] raile:
I've tried twice now to encrypt my device. Both times, the "encrypting" screen (the screen with the green "bugdroid" in the lower right corner of the screen) started around 3 hours left, and quickly goes down to 10 minutes left to encrypt and stays at 10 minutes. The first time I let it sit for about 4 hours and then forced a reboot and it got stuck in a bootloop. The second time I let it sit for about 7 hours and then forced a reboot and got stuck in a bootloop, but did prompt for a password during the boot process, which didn't happen the first time. Had to restore from TWRP backup both times

Has anyone successfully encrypted their S7 running LOS 19.1? Any advice?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] ScanX:
No. I only managed to do this under LOS18.1.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] easylivin:
Since this ROM offers signature spoofing, what is the best way to make microG run properly on my device? Is simply installing via F-Droid enough or do I have to take also other measures to get it done?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] derders:
Would go with this installer MinMicroG - I chosed the minimal variant - installed F-Droid - updated all packages - installed AuroraStore...

You can make a rom backup first and try it out.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] easylivin:
From your experience, is it necessary to install MinMicroG again right after a new ROM version once a month?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] derders:
No it is not necessary. As magisk module you don't need to do this if you update ROMs.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] easylivin:
Ah, okay, you used Magisk to install MinMicroG!?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] derders:
Here you can read some infos about install - I flashed it as .zip in TWRP but it is long time ago...
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] easylivin:
Jepp, that's what I did. Worked flawlessly BUT it's not possible to update microG via F-Droid/NeoStore (incompatible version, this version is signed with a different certificate...).
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] xMelon:
EDIT:

I re-did everything (for a 3rd time) and it worked this time.

Did I just mess up my Galaxy S7?

It's been a while since I've done this and thought I knew what I was doing.. but apparently I missed something as my phone now seems to just continuously loop (galaxy intro, then lineage loading, then restarts). My phone is already rooted from a long while ago with a custom rom and kernel - not that I recall which as it has been years since I have done this. Gapps before, did with no Gapps this time as I'd like to save space and battery using alternatives.

What I did:

- Entered TWRP Recovery mode

- Wiped Dalv/Cache/System/Data

- Flashed Lineage 19.1 ROM

- Rebooted device

Am I able to fix this? If anyone is able to provide a step-by-step guide for me I'd greatly appreciate it..
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] xMelon:
Just wanted to add;

Beautifully done ROM! Everything works so flawless and effortlessly. Super fast charging speed and battery life significantly improved overall.

No Gapps installed so if anyone has any (free) alternative recommendations, please let me know! I'm always down to explore different options and new apps. Camera, gallery, basic everyday apps, etc. Currently using Aurora and UpToDown for my downloads but they're moderate so far.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] netra3441:
Yes! Great ROM! Congrats to @Ivan_Meler ! And also a big thanks!

Much better than the 20. I am glad too, and I am happy have done that step back from 20 and run 19.1 now.

Regarding your question, @xMelon : try FDroid. There are very nice apps. And no trackers or other mess.

I had looked to that UptoDown, what you are using, but for me Aurora (to load the few apps, I need from Google Play Store) and Fdroid is good enough for everything.

Honestly I do not understand, what UpToDown at the end is, they look like a one-to-one copy of Google Play Store.

I do not have installed an *Gapps, so no GSF (Google Systems Framework), and so do not see the need of a copy of Google Play Store.

And saying that straight: in Google Play Store really 95% of the apps are garbage, full with trackers and other spyware, so in fact really no need to use this store. Google has lost the control of its store, because they do not stop, do not clean up, that all that very messy garbage apps and games can be downloaded from there.

Furthermore I do not do any money regarding things with the smartphone, because all mobile units are not safe enough to do money matters. I do online banking, but only on a specially hardened Linux system at home. Also I do not order any goods with the smartphone or with a tablet, because with ordering in the regular there is a payment act to do too, and this also is unsafe on any mobile unit.

Let me explain that: doing money matters on mobile units, Android or Apple, is nonsense, because all these mobile units are not safe for doing money matters, furthermore these banking apps are unsafe garbage in the regular. Just because banks offer banking apps, that does not guarantee, that this apps are safe - banks and their employees and coders do cook with water only too.

The reason for that is simple: on a unit, where a lot of apps are installed (f.e. from that damn Google Play Store), wich include all kind of trackers and other spyware, it is very stupid to do money matters, because these money matters can be spyed out, so that money loss follows. This means to online banking and to ordering goods alltogether. So no banking app is safe against this, and so all ordering apps or payment or credit card apps are unsafe too in the regular on mobiles.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] xMelon:
I don't plan on using anything like banking and such on mobile any longer. Hence the removal of Gapps as well. Thanks for the info!

I'll check out FDroid! I'm only using UpToDown for a few apps that Aurora didn't have. Aurora I mainly use for the Play Store links redirect while searching for apps. I've heard of FDroid but never checked it out so thanks for that!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] netra3441:
Well... as far as I understood, the Aurora app is not a store itsself, its more a better surrogate for the Google Play Store app, but without the need to have installed the GSF by some *Gapps.

Fdroid app is a store, but without the need of GSF or *Gapps, and also the apps inside Fdroid do not need that - and they are free of spyware.

Furthermore, when one uses apps to pay from Fdroid, getting contact to the coders is easy, and the they get all the payment, have not to give fee like in Google Play Store...
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] sooperior:
I was able to do it with january (or march?) version. But know I have tried to update to October and have failed into a bootloop. I'm using twrp 3.7_9-1 and updated from a sd card.

I'm trying to wipe cache/dalvik but seems that they are on the encrypted partition and twrp cannot mount them. I'm a little stuck now.

Anyone has an encrypted device and has a trick for updating? (without fully wiping the device)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] KhanhLeeVn:
Does the ROM support exFAT format for OTG devices ?

Tks !
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] ScanX:
Autoupdate works again now. Thanks @Ivan_Meler for latest sec. patch nov.23!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] netra3441:
Also many thanks to @Ivan_Meler from me too!!!

(y)(y)(y)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] PietjePuk75:
First of all: it's amazing that I can get a fully updated system on my 'old' Galaxy S7. Thank you!

I'm currently on LineageOS 14.1 (Android 7.1) and now I want to upgrade to this version.

I have updated TWRP to 3.7.0_9-1-herolte, downloaded zip files for this ROM and BiTGApps-arm64-12.1.0-v2.4-CORE.

But I also want to have root access. I got root on my current ROM via SuperSU which I flashed together with the 14.1 ROM (and OpenGApps), but it seems the current (best) practice is to use Magisk.

But for the life of me I can't figure out how to do that.

https://topjohnwu.github.io/Magisk/install.html#samsung-devices talks about OEM unlocking, but I don't have that option in Developer Tools. There are a LOT of other options, but not that. I'm pretty sure that my bootloader is fully unlocked.

Then the instructions talk about downloading the original firmware files, but I don't want that as I want this ROM.

Then they talk about patching "AP, together with BL, CP, and CSC", but I don't know what that means. I'm guessing there are various files with the original firmware with those 'names' which you apparently need to patch. But I just have 1 zip file from this ROM.

I found that Magisk is also available in F-Droid so I took a look, but that also seems to want to patch a file ... which I AFAIK don't have.

There is a procedure that seems simple "Custom Recovery", but that is clearly marked as deprecated.

So my question is: What and how do I need to do to make sure I get root on my new/updated ROM?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] PietjePuk75:
I thought "What's the worst that can happen" and just tried it.

Booted into recovery, installed this ROM, BiTGApps and Magisk, wiped Dalvik cache and rebooted ... and looked at the boot animation ... forever.

Now I can't seem to power off the device anymore or go (back) into recovery. Only going into download mode works.

Did ``heimdall flash --RECOVERY recovery/twrp-3.7.0_9-1-herolte.img`` that seemed to work ... but still the same result.

And I got literally smoke coming out of my USB cable ...

So I guess that was the worst that could happen :ROFLMAO:

If anyone has tips on how to get a working system again, I'm all ears.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Not_Rich:
Since download mode works, flash stock with Odin

I think this is where you went wrong, in TWRP I wipe dalvik , system ,data ,cache before you install rom gapps etc

BTW I dont know if wiping cache and dalvik are necessary but when it works I don't experiment.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] PietjePuk75:
Thanks for your reply :)

The situation got a whole lot worse I think. It seems the cable is making (?) short circuit and now there's smoke every time I connect it. Which means I can't use it anymore. It seems the USB connector is like USB micro, but slightly different as previous attempts to use a different cable usually failed?

I found another USB Connector in the (original) box, but it looks like I don't have a type A to type A cable. I do have type A to C cable, but so far I haven't been able to let my PC or laptop (and/or heimdall) be able to detect a connected device (i.e. my SGS7) with it.

IOW: it now looks like I can't communicate with my SGS7 any more :-/

FTR: the cable already had some damage before, but was still functioning then

(Odin is now also available for Linux I think?)

I may have written that incorrect or incomplete as I had to do it from memory. But after you flash a custom ROM, you immediately get an option to wipe 'some things' with dalvik in it's name/description.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] PietjePuk75:
Some progress:

I was fully ready to ``heimdall flash --RECOVERY recovery/twrp-3.7.0_9-1-herolte.img --no-reboot``, quickly plugged in the damaged cable, ran the command and unplugged the cable again.

Still only the download-mode key combo worked to reboot the device, but quickly switching to recovery-mode key combo right after it actually rebooted, made me land in TWRP :-)

Luckily it still had the zip files, so I installed the ROM and BiTGApps, but not Magisk and then did the 'extended' wipe and now it has actually booted successfully. I found a cable with which it seems to charge the battery again, but my PC still doesn't see it, so ``adb`` probably can't be used with that cable. IIRC it could also work via the (wifi) network, so I maybe able to get it working (reasonably) normal again. Fingers crossed.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] PietjePuk75:
New development:

I have now managed to install this ROM including Magisk and boot into it and I got root. So far so good.

BUT, when I went restoring the backups of my programs, the most important one (Signal) failed :-/

So then I tried to restore my (nandroid?) system backup to go back to the old state (so I could make another backup from within Signal which should work I guess/hope), but when I did that I got an "encryption unsuccessful" error with the only option to reboot which just results in the same error.

I have no idea where that's coming from as I didn't use/have encryption on my old system.

I found https://android.stackexchange.com/q...unsuccessful-even-after-system-backup-restore where the suggestion seems to be to install the original Samsung firmware ?!?

That doesn't make any sense to me and I assume it actually 'flipped a bit' somewhere which made it work?

Someone has an idea how to fix that "encryption unsuccessful" error?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] PietjePuk75:
Turns out that "encryption unsuccessful" error is related to dm-verity* and as documented in TWRP for SGS7 thread's OP can be resolved by installing the latest zip from https://build.nethunter.com/android-tools/no-verity-opt-encrypt/ **.

So now I have been able to successfully restore my Nandroid backup, which got Signal (back) into a working state and allowed me to make a Signal backup (from within Signal), which I presume will let me successfully restore Signal.

So I think I've now figured out all that I need to do, but will do some essential (other) things first before my next upgrade attempt.

FTR: None of these issues is Ivan's or anyone else's fault, but my own***.

I'm merely documenting them for myself and in the hope that if someone else would also stumble upon such issues, my notes may help them.

*) Don't know yet what that actually means and/or is for

**) I haven't found a/the source code repo for it though, seems related to Kali, but also seen deprecation warnings ... further research needed

***) I don't 'dabble' that often in ROMs, so I wasn't aware of potential issues/workarounds or current best practices. I have installed a couple of custom ROMs before, so it wasn't all new to me. And my notes wrt SGS3 actually helped a bit :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] steve8x8:
Although the highest priority should be a reliable USB cable, here's what I did on a S7 Edge (not exactly comparable, but close enough, I think): install TWRP 3.4.0 via heimdall, boot that, copy TWRP 3.6.2 to sdcard, install that. After saving baseband (modem) and efs, I wiped cache and dalvik and formatted data (I'm not into encryption), wiped all, and sideloaded LOS, NikGApps and Magisk, then rebooted. No obstacles along the path.

I think I went for PixelExperiencePlus later, not sure from my notes....

I never used TWRP 3.7.0 since (at least early) versions had issues with some phone models. 3.6.2 worked for me.