yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Iron_Overheat:
@Ivan_Meler I really appreciate your work and I really wish I could support you monetarily (sadly I don't have my own income stream).

Is it possible for you to update the ROM's source code with your changes? I'm investigating signature spoofing ROM patches. For building it's just a matter of compiling the source code you provide with the link in the main thread, correct?

Alternatively, if that would be okay with you, there's also the option of you adding signature spoofing patches on the main builds yourself. I might be wrong on this, but it seems to just be a matter of adding an existing patch to the ROM, isn't that right?

I would use Xposed to use MicroG but I can't get it to work even by compiling the latest build of the FakeGApps module. I tried following this thread first and the permission dialogue for signature spoofing even popped up, but it wouldn't actually spoof the signature no matter what I tried.

Regardless thank you for your great work!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] chomsky55:
I have the exact same model S7. The device is rooted with Magisk, no google apps whatsoever and apart from the issues I listed everything works fine once the device is booted up. I don't use the phone for calling anymore due to the echo problem or sometimes no sound at all. Love the advanced charging controller by the way.

I'll just wait for the next build and hopefully everything willl return to 'normal'.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] skavenger360:
Doesn't work. Twrp says i dont have an herolte version. I dont understand...

CSC > G930FOXA5ESD2 might be a problem ?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Frugipon:
Hi,

I am unable to browse past /system/storage/[External-SD_ID]/Android/Data

The folder is empty, when it even shows at all.

Yet, I know for a fact that it is here (can browse it in TWRP file manager) and several apps can write in it.

I am trying with both the vanilla File Explorer and MiXplorer.

I use the January build (clean install) with Magisk 22 (for Viper4android) with no other issues apart from the usual ones already reported (Wi-Fi disconnects, in-call sound issue).

Does someone else has this problem? Anyone can help me with this?

Thanks
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MikeTheTechSavvy:
Hey guys, I've created a video review and a short tutorial of the LOS 18.1 ROM - I found it pretty good given it's only been launched for a few months, I believe it will be the go-to ROM for the S7 (if it's not already).

The video is here if you want to check it out beforehand:

@Ivan_Meler: Again, this ROM is making the S7 an option in 2021 for sure. Congrats man. Feel free to post the video in the OP if you think it'll help the users.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Mohamedkam000:
G930F is actually herolte, there is only one way to check what your phone model really is, your bootloader (or your bootloader version).

As some people may spoof non-international model with international one, it may cause you a really hard problem if you did not make sure what model do you have.

How:

Shutdown your phone. Press Volume Down + Home + Power, skip the warning by pressing Volume Up. Phone model is shown in clear, what is written there is the clear truth.

Open terminal (no root needed), write:

getprop ro.bootloader

This will show your bootloader version, the first five strings are your actual phone model.

CSC, AP, {Settings >> About Phone}, etc ... are not trusted, anyone can change them.

Since you have TWRP, your phone's probably an Exynos variant, follow this guide.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Queeq:
I know this is due to SELinux policies, but I don't know how to fix it. I'd expect root would have access everywhere but apparently not. I think it has something to do with tightened security of Android 11.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Frugipon:
Yes apparently it's due to Google changes in Android 11 (see this post on reddit), not ROM related so I apologize and I asume everyone is affected.

Even though OT, It'd be great if someone could share any workaround (again, in my case MiXplorer gives access to internal Android/data folder but not the external one).
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] tvdler:
Is anyone having trouble with encryption? I have to reinstall every time I try
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] kase2804:
i had problems with encryption if i flashed magisk.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] tvdler:
That sucks, i really want root, is there an alternative?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] kase2804:
you can try flashing magisk 21.4 , not magisk 22.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] armkreuz:
Hey guys, I updated to this version last night. My only issue is with Magisk 22. I can't get it to pass Safetynet cstProfile. I even tried to install version 1.1.1 of safetynet-fix but during install I got this error:

Unsupported CPU Architecture:

Updater process ended with error 123 ...

Any of you have it successfuly pass ?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] drgonzo69:
Hi everyone,

For those using v18 for a while now, do you think the latest build is as stable as v17?

I'm using v17 for several months now and it's perfectly working but you know... why not upgrading to 18 for fun and for no particular reason ;)

Thanks!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] zetex.otm:
I am running the 2021-03-05 version (latest) of LineageOS 18.1, encrypted phone and Magisk 22.0 with no issues. Clean install. I ADB sideloaded Magisk with TWRP.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] armkreuz:
But if you go in Magisk, and do a Check SafetyNet, does it pass or it fails ?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] zetex.otm:
Pass. Hide works with banking apps.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] StanWiz:
Safetynet fix is described in this thread in detail - read a few pages back or use the search function.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] armkreuz:
Great.. thanks. Found this from K2Silver:

UPDATE: IDK if anyone else had this issue BUT

Magisk Safetynet would NOT pass CTS profile, basic integrity would PASS if I enabled Magisk Hide, then in order to have the other one pass and have device certified in Google Play Store I had to download 2 modules from Magisk

BusyBox for ANdroid NDK

MagiskHide Props config

+ safetynet-fixv.1.1.1 and

linux terminal emulator for andorid.

Once in emulator issue SU command

props

select "Edit Device Fingerprint" *(should be #1)

select "Pick a Certified Fingerprint"

then select your phone manufacture

select phone model

reboot

Then Safetynet will pass and device is certificated in Play Store too!

It now pass SafetyNet, but my Tangerine apps still doesn't works. Look like I'll use the browser instead.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] netmen-x:
how to install TWRP after installing LineageOS 18.1 it just disappeared and won't start.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MNNR:
Just do it the same way you did it before, Using Odin.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] armkreuz:
I always use Odin to flash it on my devices
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Ivan_Meler:
New builds are up and as per requests of some people Signature spoofing support is added (In a way that doesnt make it a security threat as app has to be flashed to system,have proper priv-app xml permissions and user has to explictly grant permission for the given app) you can sue it with MinMicroG

Other than that there are just some performane and satbility improvements, here is a brief changelog

- Added signature spoofing support for MicroG

- Cleaned up codebase

- Misc performance and satbility improvements

- Synced with LOSsource

Big thanks to everyone who donated as their donations help cover the build server cost and keep the device alive more than 5 years after release with up to date OS and security patches
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Darth Vader:
Can this be updated over OTA? I found the option but it says no new updates found.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] chomsky55:
No, you'll have to use TWRP to update.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] mimek:
How to update soft for newer build version with TWRP without losing already installed apps - is it possible?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Bleifuss2000:
Hello all,

are there any instructions on how to install the latest image and what to look out for?

As far as I have heard, all NiKGApps are no longer usable after the installation via TWRP and must be reinstalled after the flashes. TWRP must also be reinstalled.

What about other apps that were previously installed? Do they also have to be reinstalled and reconfigured?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Queeq:
Don't wipe data, only wipe cache and dalvik. Then flash newer system zip and magisk if you need root (v22 didn't work for me so I flashed 21.4 on previous update).
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] mimek:
Thanks! I've got some problems after that approach with NikGapps (I was receiving an error that Google Play Services must be installed, but it already was installed...). Flashing with wiping data also didn't help. Next, I've downloaded the latest version of NikGapps from Canary-Releases and now it works properly.

Next time I will try your method again, but with latest NikGapps.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Iron_Overheat:
Can confirm MicroG is indeed fully working under the new build. Thank you so much Ivan!!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Queeq:
Right, sorry, forgot to mention that NikGapps need reflashing too. And sure don't forget about having backups :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] bomsch:
Hello,

great Rom , really fast and low battery draining. Also Android Auto ist working with NikGapps Basic and Android Auto AddOn.

But i have one problem with microphone. It stops working (WhatsApp Calls, normal calls, Recorder app ...) after some times. Only a reboot can fix it, for a short time.

Is there a fix or a possible workaround, without rebooting?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MNNR:
Same here, I also get some software random restarts while using the phone, Rarely tho, I don't know if other users experience this too, Or I have something installed that's causing the soft reboots.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] bomsch:
i try to get logcat, dmesg and proc/last_kmsg next time the microphone not respond or not working.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Chaos_002:
First of all, THANK YOU for keeping this device alive! It's really incredible that you do this and with such good feature support!

I just upgraded to from 17.1 (full reinstall, just took some appdata with me) to the latest 18.1 build (lineage_herolte-userdebug 11 RQ2A.210305.006 eng.ivanme.20210304.175021 test-keys) and I read in the changelog that the bluetooth quality has been improved - tho I don't seem to be able to support this statement because since I used this unofficial port I have terrible bluetooth connectivity (-22dBm right next to the device) and I am unable to resolve that issue. (Example: I put the phone in my jeans trouser pocket and the audio on my Earbuds gets really choppy and most of the time stops completely but also when I put the phone in another room (brick) and close the door it works relatively fine?).

I have confirmed that it's not the headphones because on other phones they work great and I have tried other bluetooth speakers as well with direct line of sight losing connection after about 4-5m already.

If I could get some help from somebody here that would be greatly appreciated!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Chaos_002:
Yeah the random restarts And freezes have gone down by far when I upgraded to the latest (experienced only 1 soft freeze (Screen would only show clock when turning on and didn't respond to any buttons/touch) in the like 3 days it's running now) but yeah booting takes longer now I guess... Went up from like 6-7 seconds without the "Galaxy S7" screen to like... 12? Idk...

Tbh I AM using magical modules but none of them alter any bluetooth or system files, mostly they are just additions.

Nice to hear I'm not the only one! I thought my Bluetooth module was wonky or something already and tried to dig through system files so I can maybe bump up it's input voltage or whatever😅
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] QhyQhy:
still no open gapp android 11 :( only nik
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] TheEYE13:
I've experienced more reboots. I even have a partly saved photo - the reboot happened while saving a photo to the sd card. A minute ago my SD card corrupted again (tried to download a podcast).

Unfortunately using FAT32 isn't suitable for me. I've to be able to save big backups to the SD card.

Sadly I didn't get a reply regarding possibilities to hunt that bug(s)...

edit: I'm going to flash the current version (20210322) today. But since Ivan hasn't said anything about it, I assume, that he's not working on the SD card corruption issue.

edit2: I've inserted a new SD card too to make sure that my old card isn't damaged or something like that.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Chaos_002:
NikGApps is pretty nice tho - what features are you looking for that it doesn't have?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] vagika:
Hi,

This is really great work, works flawlessly! 1 thing which I'm curious about, is if it could be built w/ release keys, even if it is unofficial?

RaiPay doesn't work for me on this rom/device, but it's OK on my old I9506 w/ Kyasu LOS18.1, and the only diff. I could find is the test-release keys.

Thanks!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Tails32:
I just found an issue with this ROM regarding wifi connectivity. It seems that it's not possible to connect to networks which use combined WPA2 and WPA3 (not enterprise). I've tested this with both my router and mobile hotspot. Just plain WPA2 (personal) works.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] zehkul:
I can reliably get the device to spontaneously reboot by starting AccA and selecting any profile in it. This used to work in the LOS 17 ROM. Can anybody confirm this?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] pohlymorph:
Yepp, same here. It takes a couple of seconds from selecting 'change once to #% [...]' to reboot of the device.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] downhere:
Can't confirm.

I'm using Acc 2020-11-20 with AccA, and it's working without issues. Even selecting different profile is fine.

LOS latest build (2021-03-22).
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] chomsky55:
I was using Acc v2021.2.25 without AccA and had issues with booting/rebooting/shutting down almost every boot/shutdown, after removing the Acc magisk module the problems have disappeared. Rebooted/shutdown over 5 times and everything seems fine now.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Queeq:
Do you have backups >4GB?

I've been suffering from this myself until I formatted SD as FAT32. Also tried ext4 but the system can't use it :( Although somewhere on the Internet I saw that LineageOS in general does support external SDs formatted to ext4. Maybe I just haven't tried hard enough to make it work and you'd be more lucky. Let me know if you figure it out.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] iankelly2001:
The random reboots have stopped since I reformatted my external microSD card from exFAT to FAT32 a week or two ago. I haven't noticed any slowdown in performance or any problem with the 4GB file size limit. Perhaps I don't have any single files that exceed this size.

I can only think that some video files could exceed this amount, if very high resolution and of long duration. TWRP backups are not a problem, as the backups are broken down into a series of smaller files. Note the 4GB limit is for a single file, not the size of a file folder.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] winblocker:
Try putting the phone with the display facing you into the pocket. The antennas are on the back of the device. It solved my issues while riding a bike with bluetooth earbuds.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] StanWiz:
Had the same problem a couple of builds back - solved by completely removing /reinstalling acca magisk module + acca application. Downloaded/installed acca app v1.0.31
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] TheEYE13:
I've thought about the TWRP NANDROID backups. If I'm going to experience further reboots, I'm going to format my SD card to fat32. I'll let you know how it goes!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] pbenis015:
hello my main concern is the camera performance, I just want to ask if this ROM supports the camera's OIS?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] mauricefab:
Hello, i have an issue with bluetooth with a UE Boom 2 : the bluetooth application systematically stops.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] K9100ii:
For the issues with reboots and corruption with SD cards formatted with the exFAT filesystem that have been discussed recently, those would be caused by an update to the sdfat driver, used for exFAT filesystems, in the kernel causing kernel panics: https://github.com/LineageOS/androi...mmit/ddba1674688968d672c5529068b8690ee5e79da7

Over on another device, the Samsung Galaxy Tab A 10.1" (2016), which also uses a 3.18 kernel, I found that the updated version of the sdfat driver (2.4.5) caused kernel panics when writing heavily to an exFAT filesystem (on my SD card) using it. I could very easily cause a kernel panic by, for example, taking videos or downloading torrents to an exFAT filesystem mounted using sdfat. I'm thinking that similar issues are occurring here.

Assuming that the issues are really caused by the update (I can't think of any other possibility), the only fixes/workarounds are to use a kernel with that update to sdfat reverted, or with whichever parts of the update causing the kernel panics reverted or a proper fix to the sdfat driver. We're still using an older version of sdfat, 2.3.0, over on the Tab A.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Iron_Overheat:
Further reason that the kernel should be updated to the latest supported LTS version (4.4.263 as of 28/03). It would be really good to be on a properly maintained kernel with the essential security updates. 3.18 is only maintained unofficially in AOSP, it entered EOL in January 2017. Who knows what vulnerabilities present in this kernel might be being explored in the wild.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] RickBH:
My G930W8 phone will not boot the latest (20210322). Just goes back to TWRP (3.5.1_9-0). This is a dirty update from the last release. Will see what i can find in logs.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] RickBH:
I tried again after removing Magisk v.22 just in case it was a problem. No change, boots for a while and then back to TWRP. I have attached the log.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] RickBH:
Try again with the log. Not showing up. Do not know why.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] K9100ii:
I never said that the update causes issues with 3.18 kernels exclusively, although I might've subtly implied that. In fact, I suspect that similar issues can occur on other kernels with the updated sdfat driver, including kernels based on 4.4.

Updating kernels to newer major releases of the Linux kernel for android devices is very much easier said than done. That would require all of the drivers and other bits to be forward ported, which is extremely difficult, time consuming, and requires quite a lot of knowledge, and there is a very high chance of there being issues after getting everything to compile, and even more changes would be needed to fix such issues. Android device manufacturers and SoC vendors very often make very extensive changes to their kernels, and this is true for Samsung as well as others, making things all the more complicated. Almost (think >99.9%) everyone has to go with their vendors older downstream kernels as a result - if it was so easy to update kernels to newer major updates, no one or less people on fewer devices would still be using older downstream kernels. Many are still using even older 3.10, 3.4 and 3.0(!) kernels on older devices with backports. Drivers could also be written from scratch, but that has its own significant set of difficulties.

The last minor update for 3.18 was actually 3.18.140, released on May 2019 (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/log/?h=v3.18.140), and it was updated for that long for the many devices out there running on 3.18. The 3.18 Android common kernel indeed continues to get updates, including some fixes to security vulnerabilities. On my kernel for the Tab A, as a compromise, I'm also applying changes from 4.4 as well as changes from the 3.18 Android common kernel and previously also, when it was still maintained, Linux 3.16.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Iron_Overheat:
I'm sorry I spoke of it as if it was a simple thing. I'm just worried about security and bugs. Specially since this kernel is really old by modern standards (even if it's by far not the worst as you clearly mentioned) which skyrockets the chance it's being exploited in the wild (I would assume newer kernel vulnerabilities take a while to get working exploits unlike old ones which have a large window of time to be exploited). I'm kind of obsessed with updating anyway so admittedly that's my bias.

Is there any way to apply critical security updates to this kernel? I'm not sure if I understood correctly, you said you did that to your Tab A's kernel? I'm on Manjaro Linux so I might be able to do it also, if you can do it. Is there any guide on doing that or something?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] shayandely:
Dear developer

thank your for your brilliant ROM and also your hard working.

I installed this ROM two weeks ago and every thing is working fine.BUT!!

recently, i've found some problem which might be fixed by your code review.

1-. when I call someone and after answer, switch to speaker , Nothing happen and the speaker doesn't works.

2- when the phone rings and I answer the call, sometimes call end unexpectedly without any reason ( I dont have logcat for this)

the attached logcat is for the first problem which hope to fixed it in your next release.

thank you for your hard working and I will support your project!!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Iron_Overheat:
I can confirm these issues as well. And random reboots (which I've read can be fixed with formatting sd to FAT32, but I've got too much data on it and nowhere to copy it to). And after a random amount of idle time all pps will freeze upon opening (though quitting them works fine) until a manual reboot. I was having call hangup issues with my previous ROM as well, Havoc OS.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] blei:
Hi, I tried to update via full wipe to LOS18.1 from ivan on my SM-G930F with baseband G930FXXU4ESB1. But I can't get the phone to connect to any WLAN - tried to disable 5Ghz on access point, but still doesn't help - with the LOS17 from Ivan everything works as expected? Any ideas? Thanks
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Tails32:
Are you trying to connect to a wifi network which uses combined WPA2 and WPA3 encryption? I also had issues connecting to wifi and this was the reason for me. If possible, change the encryption to WPA2 only and your issue should be resolved. I didn't use the LineageOS 17 version of this ROM, so I can't tell if this issue existed before or not.