yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Katadreuffe:
I installed the January 2021 build; everything seems to work fine, big thanx to Ivan!

Exect for one thing; the notifications don't work anymore... no LED's, no sound(!), only the notifications on the screen.

Before, with the previous build, even the LED's worked!

So I reverted back to the December 2020 build.... still no LED's or sound.... :(

Who knows how to fix this?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
@Katadreuffe: The problem has already been described here several times and is also present in the December release. In this post I collected all known bugs of this Rom: https://xdaforums.com/t/stable-lineageos-17-1-for-galaxy-s7-build-20.3980101/post-84212447

In addition, there is the bug I recently discovered: VPN and tethering do not work together.

All of the bugs I described are still present in the January release. Especially annoying is the WiFi crash, which now occurs practically every day with me. The WiFi crash nearly always occurs when large amounts of data (several hundreds of megabytes) are transferred over a period of 10 to 15 minutes. Like that is the case with Dropbox synchronizations etc. Therefore not everyone notices it.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Mohamedkam000:
If you have "Do Not Disturb" enabled, it's natural that no notifications will annoy you, however, your case seems a bit more to these:

Your notification settings were modified,either by you, accidentally, or any other reason. This can be solved by taking a look at Settings > Apps & Notifications > Notifications

A special battery saving mechanism was set on your device, of which can be an app, a module, a custom kernel, ...

Kernel settings were modified.

There is a "Screen on notifications" tickle available on LOS-based ROMs, of which only shows notifications when the screen is on, otherwise it will not, you need to either clean flash the ROM, or disable that tickle from your previous ROM.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
But that doesn't explain why LED notifications work for days and then suddenly they just stop working until you reboot. After that they are working again.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Katadreuffe:
@fipsy

@Mohamedkam000

Thanx for your swift responses!

To prevent misunderstandings:

I'm aware of the LED troubles; had them ever since I switched to the LOS17 build (LED's didn't work, but audio notifications did!). In my case rebooting didn't help, and it wasn't every now and then; LED's didn't work at all for months(!). Untill I accidentially drained my battery... due to the daily WIFI crashes... Which I can confirm; switching WiFi off and on also helps in my case.

Strange thing is: LED's worked in the Dec build, stopped working (LED's & audio!) in the Jan build, but when I now reinstall the Dec build, they don't work anymore...

I checked the "Do not disturb", "Total silence", "Screen on notifications" etc settings; I don't see a cause for my problem there.

Don't know about kernel settings; I didn't change anything (neither did I for the "Screen on notifications", worked before). :unsure:

So:

Nice ROM, with in my case 2 drawbacks:

- Daily WIFI crashes

- No notification LED's (nor sound)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
Thanks a lot for your response and for confirming the Wi-Fi bug! The two drawbacks you mentioned are the main problems for me too. You may perhaps install Smartpack Kernel Manager from the Playstore and play around a bit with it. I haven't had any success with this yet, but it might be worth a try.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Roberto W.:
provide logfile-entries while wifi is crashing, so this might help to see why.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] QhyQhy:
installed the last january build

everything work fine except for camera

soooo slow to take picture (1s after pressing button) and impossible to take photo with flash :/
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] vampsm:
Hi i used original play store google camera, this works fine, some times with flash light crashed, led works wifi works

BUT hal echo is especially nerdy (german network is also lost when calling)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] QhyQhy:
which version of google camera? tried one this morning! crashed a loooot! deinstalled then
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] downhere:
Take a look at Footej Camera. It's working well for me.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] backtotopic:
ZGCam works for Pictures in high quality but slow, for quick pictures I take Footej Cam 2.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] QhyQhy:
Footej Camera 2 - PRO HD CAM – Applications sur Google Play

L'appli caméra la plus simple et puissante pour capturer vos moments préférés !

play.google.com

this one I supposed?

edit: work like a charm! thanks :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
In fact, OpenCamera is generally always recommended. I've been using it for years and it works quickly and very reliably as well.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Nevaran:
Anything that records calls in here? I see an options in the phone app but dont see any way of recording...
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Nevaran:
For me it takes pictures incredibly slow and the focusing is bad :/
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
@Nevaran: Maybe it also depends on which of the two camera modules is installed in the device.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] QhyQhy:
open camera is quicket to launch than footej 2 but it take ages to take a picture compared to footej2

but even footej2 is slower than the regular stock samsung camera app :/
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] .Michael.:
The initial / 1st post tells:

How is this meant? There are not (stable) working features in this ROM, see the LED / WiFi / Echo / Camera error reports above.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
I've already criticized that. I found another issue: After a phone call, when you remove the smartphone from your ear, the display is often at full brightness and the automatic brightness control is switched off. And there are also other, smaller errors such as Settings that are reset after a reboot (also reported above). Unfortunately this release is being neglected a bit.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Nevaran:
The phone crash-restarts when I try to record a video with both the stock camera, and OpenCamera if recorded more than a few seconds :/
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] .Michael.:
1st of all it is really great that our old S7 cell phones are still usable with an up to date OS. (y)

On the other hand it would be good to inform users about problems. As fipsy confirms this is not made by Ivan.

@ Ivan: Is there any reason for that (beside that a bug tracker tool is missing)?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] chrisrevoltes:
Maybe because none of you posting any useful information, so that Ivan or anyone can confirm that.

I'm on LOS17 since July last year and have only the echo issue and some missing (??) options.

No repeatable reboots (around three at all), no brightness issues after calls or any time, no LED issues, no Bluetooth issues and so on.

I may just have good luck. I don't know that's possible, if we have the same phones. But just because I doesn't work for, doesn't mean it doesn't work for others.

Edit: Some points should be mentioned, but in the end its Ivan's decision.

We all can check the latest posts and just try it.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
I also think that this would be an extremely important decision aid for new users. Anyone looking for an OS for daily use must be informed about such errors. That e.g. VPN does not work together with tethering, can be a knockout criterion for professional use. Something like that should definitely be communicated. Otherwise someone makes the effort to set up their device with this OS in a time-consuming way and then later find out during everyday use that it is not suitable for their purposes.

It has already been said here that these problems have nothing to do with the LineageOS version, but are a Samsung problem. Nevertheless, these problems do not arise with the Stock OS, only with Lineage. Regardless of whether they are caused by Samsung or not, they should definitely be announced.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
I don't have this particular problem, but today I took a photo with the "Manual Camera" app. After the photo was taken I switched the phone to standby without exiting the app. This forced the camera module to crash and there was only a black or green camera display afterwards. Until I rebooted the phone, then it worked again.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] bastard83:
True. Camera crash, at stock app it's impossible to take a good photo with flash. OpenCamera also crashed.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
I can't sign this like that. Errors that occur sporadically are not so easy to prove. But if they occur in many cases, there is evidence. And as far as settings are concerned that are simply reset after the reboot, I have documented them very precisely. Without getting a reaction.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] backtotopic:
Please read the first post:

[...]

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

[...]

I think Ivan don't have those issues you report, and without logs he wouldn't be able to identify your problem. ;)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MikeTheTechSavvy:
Hello guys, I created a video review and a short tutorial of the most recent LOS 17.1 build - I found it incredibly stable, responsive and battery friendly. That kinda says it all :))

The video is here if you want ot check it out before trying it out:

@Ivan_Meler: Great job as always, you're keeping these older Galaxy veterans still alive. Feel free to post the video in the OP if you think it'll help the users.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
The only problem is that these are often errors that occur sometime in the middle of the night unobserved and where you don't even know the exact time. It is then impossible to post a suitable log file. For clearly reproducible errors, such as settings that are not beeing saved, no log files should be required.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] .Michael.:
If I would know what all this means ... I'm happy -if- I can flash a OS, i.e. I'm far away from being an expert in this area of knowledge.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] misan1834:
Hi - Many thanks for all your work with this ROM. Everything seems to work well on my SM-G930F so far, however callers are getting an echo both on speaker and via the headset when they call me.

I remember in previous LineageOS versions you could change some settings in mixer_paths.xml. However, I've had a look around in there and can't see anything obvious. Perhaps related to Audio Noise Cancelling?

Any ideas?

Any thanks once again :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] ytccts:
Exactly same problem and still looking for a workaround. Very interested if somebody have the answer.

And one more things.... Thank you Ivan !
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Robert7x:
After you write "Everything is working beautifully, the ROM has a very good RAM management which results in great battery life as well. " in this video, you have no restrictions when making calls or no problem that the other person can only understand you with great difficulty due to strong echo or poor voice quality?

May I ask you how you solved this problem, which is sure a big problem for many users?

Or but why don't you draw the attention of the people who may have installed a cell phone with an original rom or an old official lineage, and now reset the device (delete everything) in the hope of having a well-functioning current rom on the cell phone?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] backtotopic:
I really don't know why, sorry, but I haven't got those problems, too. Probably I should have brought a lottery ticket the day I flashed LOS 17.1, but it works fine for me.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Robert7x:
Hello,

Did you test the quality of the call with a second cell phone, or do the people you talk to do not dare to complain? ;)

Which device and which ROM do you use exactly?

Have you made any changes?

Thank you in advance!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
I also have no microphone problems or echoes. But as you can read here, I have a number of other problems that others don't have. I'm afraid we won't get an inch if we continue like this.

Incidentally, I think it is very conceivable that the echo problems depend on the cellular provider. Or on other technical requirements that are not part of the Smartphone.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] backtotopic:
I'm using a SM G930F and ran stock ROM till last spring. I first tried Havoc 3.x OS, based on LOS, and switched to LOS 17.1 in October because of missing security updates and random reboots.

Some Havoc-Users wrote about the echo problem, but all my phone contacts told me, there is no echo at all. I use my phone nearly every day for ordinary phone calls. If they wouldn't work, I would never use this ROM.

Btw I don't have any other bugs like interrupted wifi and Bluetooth connections or bad microphone quality. Thank you again, Ivan!

We both don't know, whats the normal case - to experience annoying bugs or to have a smooth running daily driver. In this context it's not very nice to blame MikeTheTechSavvy for not mentioning bugs in his review, he probably not experience.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Ivan_Meler:
New builds with February security update are up here is a brief changelog

- Merged February 2021 Security Update

- Added proper flicker free (DC dimming) implementation

- Added support for smart cover

- Misc performance and stability improvements

Big thanks to everyone who supported this project by buying me a coffee and helping coverbuild server cost as without them it wouldnt be possbile tokeep s7 series alive
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fipsy:
I would also like to encourage everyone to donate a few dollars to @Ivan_Meler, even if you have problems or bugs. Because without donations it wouldn't go on at all.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Robert7x:
Thanks for the details! When was the last update the original Rom?

Maybe it is because of the topicality of PDA / CSC ...

About:

"In this context it's not very nice to blame MikeTheTechSavvy for not mentioning bugs in his review, he probably not experience."

That's why I ask whether he has this problem, or rather his interlocutors .....

Anyway ...

I think everyone who reads and posts in this forum knows that this problem of echoes can not only be a marginal phenomenon, after countless reports from various people!

(By the way, it would be really interesting to know what percentage is really affected here!)

Therefore I am of the opinion that if you encourage people on other platforms to try out this rom (who may not read this here) over should inform you about any problems that may arise, because as already described, maybe some people after they have reset everything and have undertaken a lot of work then maybe very disappointed because in many cases the Rome is not STABLE after all!

Is my opinion really that wrong?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Robert7x:
Sure, I did some time ago, even think twice ... Hope he has" gehodlt" ;)

Nevertheless for me the S7 has become unusable .....

Even with / e / there are apparently messages about this bug ..

Anyway ... I wish everyone else where it works, have a lot of fun with Lineage 17.1 or 18.1 on S7! (y)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] tvsite:
I dirty flashed version 21 over version 20. I did not delete the locksettings. db because I had version 20 which is a January file. I got stuck in the boot screen. Do you need to delete lock settings.dB every time from now on for new versions. I had to revert back to version 20
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] RickBH:
I dirty flashed the updated ROM with no problems on boot. You should not have to delete the lock settings every time. I have had a problem with one S7 booting 17.1 at all and expect there are some hardware differences on some phones. maybe wait until the next update.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] :
@Ivan_Meler, great you added support for smart cover, working perfectly.

Thanks for your effort!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] nostromo12:
I did a dirty update from the January fix for my 930F. Everything went fine!! Thanks Ivan :cool:

Unfortunately I have no smart cover to test it.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MarcosPinheiro:
I did a clean install of the ROM and the mobile data is not working, does anyone know how to fix it? Otherwise, everything looks normal and so far there has been no random restart.

I want to highlight two strengths:

- Battery: lasts more than a day, great for a cell phone with 4 years of use;

- Call quality: loud and clear.

Thanks Ivan Meler
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] tha_G:
For all of us having a 'dumb' flip cover with card slot...

I just made mine smart :cool:

I created a plastic placeholder for a magnet and inserted it into the cover it's card slot, works like a charm!

View attachment 5216077

View attachment 5216079
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] chrisrevoltes:
Hi, I need some advice.

I removed fingerprints and deleated locketings.db and did a dirty flash from november to feb version + gapps nano + magisk 21.4 and did TWRP update from 3.4 to 3.5.

Phone booted without errors. After Android system finished what ever it does after first boot, I set new fingerprints and started using it again. Few seconds after using first none sytem app the phone shutdown.

Now it shows the FRP lock message. (and LED is flashing continously...)

View attachment 5216151

I cannot boot into TWRP, but download mode. That shows:

View attachment 5216153

So any idea why that happend? TWRP update? And maybe any suggestion how to fix that without clean reflashing everything?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Hemuli:
Just for your safety before you put that term to a search engine: it says FRP LOCK. (Factory Reset Protection)

Afaik, it should only be active in stock roms. It's quite worrying if it activated by itself just like that because it can be hard to unlock.

Edit: corrected the term
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] dantexperia:
Try flash this fw but without selecting CSC file, I think that that way you would not lose anything: https://androidfilehost.com/?fid=962339331459002290
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] chrisrevoltes:
Hahaha 😂 I'm so sorry...
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] tha_G:
I'm afraid the only thing you can do is go back to stock rom and disable the lock.

Did you perhaps update your bootloader? I experienced this a few months back, the latest bootloader enables the lock by default.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] chrisrevoltes:
Trying this the hole day with no success.

After dantexperia advice didn't helped I tried to flash his whole version, which was a dump idea, because it was a) outdated and b) for United Arab Emirates. However it didt'n worked. Aborted with an error. After that the phone refuses to shut down and shows just this screen without any option (download mode still works):

View attachment 5217283

Than I tried the correct firmware (unbranded german DBT) and than every remaining German version (5+1) and version for nordic states (what ever that means) (but Im pretty sure they are mostly the same).

In all cases the same result:

View attachment 5217273

Its always the same error: stucking at system.img and aborting after some time.

Flashing just AP results in:

View attachment 5217277

I'm using Odin 3.14.4 (as admin), tried with the re-partition check-mark and the pit-extraction trick (here).

View attachment 5217279

Tried different USB ports. Some (USB2??) not working with Odin. Also there is no adb-connection. And of cause Samsung sh***y Smart Switch Software cant help. It recognized that some phone is connected, but the emergency recovery function didn't show anything.

After all that faulty flashing, in download mode the AP SWREV line says: B8 K6 S7 which isn't the same value as last night. What exactly does that mean? I think something with the software.

At this point I ran out of ideas. I need that phone and have clue what to do.

Are the errors maybe due to LOS instead of Stock or the strange triggering of FRP lock? I have no idea.

btw: flashing TWRP obviously didn't work and result in a FRP-lock error message
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] chrisrevoltes:
Not sure when I did that the last time, but not since I switched to LOS17 last summer. Since than I updated every two or three months, like I always do.

And since no one else has this problem, I'm sure I did something wrong. This really annoys me.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Roberto W.:
for the latest firmware use samfirm to download it.

did u checked the file crc? i am not sure but i think there is something strange about the file size?

as far as i remember my binary size is about 2.600 mb not 4000 mb..i am not sure
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] zehkul:
Hello!

First, thank you for this ROM, much appreciated and allowed me to get a much better phone than I would usually be able to afford. I do have however a WiFi problem: Exactly 5 minutes after the display turns off, the phone will pretty reliably disconnect from the WiFi. (Except for the rare cases where it somehow doesn’t, I wasn’t able to find a pattern here though)

Last received ping is at 00:39:03.003257, first received ping at 00:39:44.922460 and no connection is possible to the phone inbetween, see the attached logcat. Tested with 2 different WiFi access points (albeit in the same network) both of which my laptop has no problems with. Tried playing around with the values in the app ForceDoze a bit, didn’t seem to change much, although I admit that I don’t really have any idea what I’m doing there, just trial&erroring a bit. Any ideas?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] dantexperia:
Try flashing the latest version of TWRP with version 3.10 or 3.12 of Odin by selecting the option "nand erase all" and the attached .pit file.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] tha_G:
@chrisrevoltes

I did also use Odin3.14.4 (Heimdall did not work)

Why would you try and flash this stange and outdated stock rom? (if your bootloader is more recent than the one included, you cannot flash it anymore)

I would suggest you try to flash the latest stock rom with bootloader, modem everything included.

For me it failed a few times and then suddenly worked, don't remember the details.

Also similar to what @roberto W said, the stock rom I flashed was 2.8GB (G930FXXU3ESA3_G930FTEF3ESA1_O2U.zip)

Good luck in fix-flashing!