yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Seanthedroid:
Does this happen after you change the LED color?

If you cycle through more than 3 colors while changing the light color in settings, for either low battery, notifications, or charging, or move around the color picker too quickly, the LED will shut off and then stop working until the next reboot. I don't think this is a software issue, because if it were it would likely have been one of the first things Ivan dealt with, most likely the LED's controller chip is too weak to handle the throughput of rapidly previewing different colors because it's not designed to ever change color in the stock ROM. This issue isn't unique to the S7 or even LineageOS, most custom ROMs have had issues with custom LED colors as far back as I can remember, all the way back to Sense-based ROMs or CyanogenMod on the HTC One (my first smartphone, I carried around both a feature phone and a Palm TX before that). It's not a big deal, just reboot if you can't get the color you want in 3 tries, as many times as it takes, then reboot again after you've got the colors you want. It's not something you should ever have to touch again once you've got it set the way you want. All non-OEM ROMs are going to have little glitches, due to the impossibility of getting the reverse-engineering of proprietary binary blobs perfectly right.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] magzen:
Error 7 in TWRP

Hello,

When i try to install i get Error 7 in Twrp, i did try to solve the issue by removing assert line in system-update as suggested in youtube videos but it didnt work.

I did try to install lineage os 16 builds from the website https://www.los-legacy.de/hero2lte, it worked without giving that error

Can anyone please help me solve the issue?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] rho-bot:
herolte is SG7, hero2lte is SG8

Say thanks to TWRP for protecting your phone ;)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] magzen:
Thanks for the help appreciated :), solved my issue ;)

---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------

Thanks for the help appreciated :) , solved my issue ;)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] angello2299:
hero2lte is SG7 Edge
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] kakamaws:
Is fast charging not working?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] girtsn:
Thanks Ivan for the effort making S7 and S7 Edge LOS 16 go out of beta - fixing the last thing outstanding. Donation sent and appreciated.

One question though.

Is it a lot of effort to go official LOS roms? The main reason for this is OTA possibility, as long as the builds are stable it would be the the easiest option to perform the updates which is working nicely even for my older Galaxy S5 LOS. Is there any additional cost or something that we as the community could help with to get it official?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Exodusnick:
Please note that you do use my build with microg

See herehttps://xdaforums.com/s7-edge/development/rom-lineageos-16-microg-t3921092
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] FlorianMLBRK:
Baseband issues

Great work. I've been using this as daily ROM for a few weeks and it seems rock stable. Only issue I'm running into are random WiFi drops. WiFi disconnects and within a few seconds automatically connects again. I'm suspecting is baseband related and want to flash a new baseband.

Which baseband for 930F NL region is best and any idea regarding download source?

Thanks!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Exodusnick:
Officially or not officially is not a big difference .

Is it about ota update ? So ask Ivan if he gets in touch with me.... Ivan could run his builds on my ota server if he wants, there will be no additional cost to him. ;)

Edit: My builds have all ota in build.

Also for Samsung s7 with microg
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] maxbeat93:
is there any custom kernels that we can use for this rom?

i've been using this rom for almost a day and feeling good. just curious about the kernel option.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Tagdu17:
Hi mate,

You can try to use Reflux kernel for LineageOS by clicking here (note that this link is for herolte and hero2lte).

Happy flashing :good:
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] :
Hi.

Firstly, my thanks to all the developers that give us mere mortals the ability to have the choice of what we run on our hardware, the idea of going back to Stock fills me with dread.

I've been using this ROM for a few months now and apart from a few forced reboots (which haven't happened since the last update), the only issue that has affected me relates to Bluetooth.

I have a pair of Bluetooth headphones (Soundcore Spirit X) that I use with my S7 handset:

1. The headphones work fine with other devices.

2. The headphones worked fine when I was running Stock on this handset.

3. The headphones work fine with this ROM if I am stationary with the handset up to a few meters away.

4. If I walk around with the handset in a pocket, the sound intermittently drops out for a fraction of a second and then returns. Sometimes it happens every few seconds and sometimes it only happens after several minutes. Every time this happens I see the following logged:

05-15 09:15:42.775 4481 5004 W bt_btif_a2dp_source: btif_a2dp_source_enqueue_callback: TX queue buffer size now=24 adding=5 max=28
05-15 09:15:42.778 4481 4878 W bt_btif_a2dp_source: btm_read_rssi_cb: device: e8:07:bf:12:ea:0f, rssi: -41
05-15 09:15:42.779 4481 4878 W bt_btif_a2dp_source: btm_read_failed_contact_counter_cb: device: e8:07:bf:12:ea:0f, Failed Contact Counter: 0
05-15 09:15:42.781 4481 4878 W bt_btif_a2dp_source: btm_read_automatic_flush_timeout_cb: device: e8:07:bf:12:ea:0f, Automatic Flush Timeout: 0
05-15 09:15:42.782 4481 4878 W bt_btif_a2dp_source: btm_read_tx_power_cb: device: e8:07:bf:12:ea:0f, Tx Power: 12

I've searched this thread, the XDA forums and the web, and I can see various references to issues with Bluetooth on Pie, although I'm not sure how current they are. I don't find many hits for the messages I am seeing.

I'm trying to work out if I, as an end user, should investigate these messages further or if this is a known issues with Bluetooth on Pie which I'll just have to wait to be fixed?

Many thanks.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] K2silver:
On the first post under the MD5 there are 2 links

1.for OpenGaAPPS

2.Root

Are we supposed to flash 1. after ROM or the second option? are we to use the second option if we have root? so confused :/
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] joen74:
Hi, thanks Ivan for this great rom. Everything works but the person i phoned hear echo only when i use the speaker.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Tagdu17:
Flash latest build (i.e. the one from 05/12) and then flash OpenGAPPS package of your choice (I use nano personally) . Root download is an add-on but idk what is it supposed to do.

Echo on speaker mode isn't a LineageOS issue, it's because of a missing noise cancelation file which is Samsung's proprietary code. You will face the same "issue" on all AOSP custom ROMs (like RR or PE).
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] joen74:
thanks
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] sirsalmanzadeh:
hope it also can be fixed soon
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Allandin:
I have the exact same issue, but only on the two most recent builds. The connected device must be quite close to the phone, or else sound will drop out. When connected to my headset, I have to carry the phone in my right pocket, and if I turn my head to the left, sound drops, until I look straight ahead again.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] claas42:
I think that there are (at least) two more advantages to go official in addition to the OTA updates:

1.. You reach much more people that will use the LineageOS 16.0. E.g., people looking to buy a new (or used) device take a look at lineageos.org to see which devices are supported (the S7 doesn't appear there anymore). So it would be important for the LineageOS community, as the S7 is widely used, I think.

2. The official OTA-Upgrades from one version to the other are supported by LineageOS. You can upgrade from 14.1 -> 15.1 -> 16.0 without reinstalling everything (as far as I understood and it worked perfectly for me until upgrading to 14.1, then I stopped upgrading). Reinstalling everything takes quite a lot of time (a few hours for installing Apps, setting them up, etc.). This is especially true if you don't sync with google.

Big thanks for the good work to Ivan, of course! :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] CountDirku:
Great ROM with only a few small glitches

First of all: many thanks to Ivan Meler for this great ROM! I did a clean install yesterday, and as far as I can tell, everything works fine including Bluetooth with aptX!

Thus far, I have noticed only a few small glitches:

1). The serial number has changed. Can I modify this back to the original serial number, maybe as root in a terminal (I've installed addonsu), or via adb? Searching with Google wasn't really helpful (I found an Xposed module or an App "Device ID Changer", none of which I want to use).

2). The built-in camera does not synchronise properly with the flash (as mentioned already elsewhere in this thread).

3). The Gallery does not display new pictures saved on the external SD-card: they are grayed-out, but are properly display both in edit-mode and in the file manager. Removing and rebuilding the Gallery data helps, but only until the next new picture is saved on the SD-card.

Many thanks again and best regards!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] sooperior:
Can you check if their size is 0? And if they appear (=show some size) after reboot?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] CountDirku:
Hi, the size of the SD-card appears to be correct: 18 GB used from 51 GB in a terminal under LineageOS. I also did a file system check (under Linux): the exFAT file system on the SD-card is okay.

Cheers,
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] sooperior:
Sorry, I didn't explain correctly: If the size of each file is reported as 0 (not the sd cart, it can be whatever but it wil be interesting to know if it is >=64).
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] VoidedKN0X:
since hwc is now working i have installed this rom but somehow my device still feels sluggish with the animations, i also have this with other roms based on this... is there anything that i can check if hwc is working? or is there a simple fix wich i'm not noticing?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] popermenko:
Try fde.al,but remove viper4androidfx cuz it caused me a bootloop once,fde gives better performance and even improves battery from my experience.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] VoidedKN0X:
i've installed FDE.AI (even with V4A installed, needed to install audio modification library) i've gotten a bit of improvement but still not as smooth as touchwiz experience.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] popermenko:
Well its true that is not smooth as touchwiz,even with fde,but its much cleaner and better looking,and battery life is better,so the choice is up to you.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] VoidedKN0X:
i guess i'm staying with touchwiz then for a while might check it out again in the next update or something
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Virnik0:
This is my long going issue...some photos shows as zero size, but after reboot, they appear with correct size and could be shared.

---------- Post added at 11:24 PM ---------- Previous post was at 11:04 PM ----------

Well, yeah... dirty-flashing, Magisk is already installed.

Maybe I'll try to un-root and flash. It is just weird - by flashing new update, It also encrypts data partition, which is then inaccessible. System boots, but it is just black screen. Only thing which still works is power menu. TWRP is also unable to access /data. I'm running TWRP 3.3.0-1.

I'm able to restore last backup after formating /data first.

---------- Post added at 11:28 PM ---------- Previous post was at 11:24 PM ----------

Thanks! Going to uninstall Magisk and then I'll try again.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] sooperior:
Do you?

use a sd card >= 64 gb?

use a customized open-gapps file?

use google storage manager?

have debugging enabled?

I'm having this issue in this rom and lineageos 14 on another phone. I'm trying to find the culprit
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] volaxis:
Thanks you Ivan,

A quick ask is there any documentation on the lineage OS system apps and services?

Cell phones plans are third world here so I use a VOIP number and a tablet data plan, I need to block the data plans sms/phone connectivity ($1/min if answered) while keeping the LTE connection for the VOIP number.

As I have it currently I uninstalled:

Phone 19

Messaging 1.0.001

Messaging service 9

With those 3 uninstalled phone calls from the data plan number ring, then show as missed call, without showing an answer app so at least I'm not being charged but eliminating this all together would be nice. (No service provider won't help/can't be configured). If I uninstall 'Phone and Messaging Storage 9' then I lose LTE connectivity.

Zoiper (VOIP app) also needs to be configured for external java audio codec as openSL ES codec keeps crashing. SIP SMS over Zoiper works.

-------

No Gapps for me so manual install of swipe libraries for swiping: download gapps, unzip optional/swypelibs-lib-arm64.tar.lz and get the libjni_latinimegoogle.so file. In twrp mount system and copy that file to system/lib64/
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] nemolivier:
I'm having this issue too, when I look at my files with solid explorer. Look at the FAQ, they said it's ok, due to the method it used to scan files.

Envoyé de mon SM-G930F en utilisant Tapatalk

---------- Post added at 11:49 PM ---------- Previous post was at 11:47 PM ----------

Here the FAQ from solid explorer :

« 1. THE APP TELLS ME, THAT THE FOLDER IS EMPTY OR SHOWS INCORRECT SIZE.*

Unlike other apps, Solid Explorer can display total count and size of files contained in a folder including all subdirectories. This would be very time consuming to compute, so SE looks in Android's file database for all files contained in that directory and counts them.*

If you renamed, copied or moved the folder to another location, Android’s media scanner needs to scan the files again. That may take a while, so that’s why you don’t see the real size yet. Once the scan is complete, after you refresh the directory you’ll see the real folder size.*

It’s also worth noting, that sometimes folder size can be inaccurate. It fully depends on Android’s media scanner and on how many files it actually scanned. Anyway, in most cases folder size calculation seems to be accurate.*

If you still see the folder as empty even after waiting some time, there must be something wrong with Android’s files database. This problem is not related to Solid Explorer and can’t be fixed inside the app. »

May it be the same for files ? Or the Android file database beeing slower in LOS 16 ?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Virnik0:
My SD is 128GB from Samsung, highest class available on the market in the time when I was buying it (about a year ago).

I am using OpenGAPPs Nano, no customizations.

I do not use Google Storage Manager. This behavior is common, regardless whether you use Google StorageManager, LineAgeOS DocumentsUI (Files), or any other app.

Yes, I do have ADB enabled, as well as developer mode, and I am also rooted using Magisk.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] MrFarKew:
Guessing this conversation is related to SD card read/write issues.

Seemed worth chiming in since I'm having read/write issues with v16 and read/write to a Samsung evo 128GB SD (~4 months old from new).

Firstly, I have no trouble reading/writing from/to the SD card using windows explorer or Beyond-Compare-4.

So far the undesirable issues for me seem to be limited to playlist and music read/write from a PC accessing the phone using the latest WinAmp 58_3660_beta, available from winamp.com. Im using the latest Samsung phone drivers and have tried with an earlier Samsung driver (same results).

I don't have these issues with Ivan's LineageOS 15.1 or any earlier version s I have used.

Attempting to read from the SD drive causes laggy behavior and trying to write is almost always unsuccessful. As I mentioned this behavior isn't present with any previous version of LineageOS that Im aware of. It was also present in Ivan's previous build of v16 so guessing its related to Pie somehow. I don't have any log info but will endevour to reinstall v16 and grab some debugging as soon as I have can.

Everything else seemed to be working as expected; great work from Ivan! Since Im big on music I reverted back to 15.1 since the phone is my daily unit and driving/work music is a must for me.

Many thanks to Ivan for his amazing work... as always. Ive been using Ivans releases for a while and greatly appreciate the hard work, knowledge and meticulous effort he puts in.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Virnik0:
Thanks again! I am running latest build now just fine. Everything it took was really to uninstall Magisk through uninstall.zip file in TWRP, reboot recovery, flash ROM + Gapps, let it boot for the first time, and then reflash Magisk. Works now just fine.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] CountDirku:
Hi! The picture size appears to be okay on the SD-card: 9.25 MB (Footej camera, highest quality setting).

I can also open the picture in the file manager, which opens it with gallery, and it looks okay. However, the gallery album view shows again only an empty looking gray picture. If I enable picture editing from within gallery, it loads the picture and displays it correctly! I find this rather odd!

Moving the picture from the SD-card to the internal storage leads to a correct display in the gallery.

I'm puzzled.

Best regards!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Virnik0:
In regard to R/W issues - I don't experience anything like that. My SD is blazing fast. No lags. The problem is, that when I take a new photo, or when I copy file from internal SD (internal storage) to external SD, resulting file has 0 size. I have to wait up to 30 minutes, or reboot to see that file in its correct size, otherwise it couldn't be used by anything else (Chrome to attach that file to some post, for example).

Strangely, Hangouts and other Google native apps does not have the issue - make a photo - attach to a message, send - done. But if I'll try to attach very same photo to post on FB for example, I am unable to. The file has 0B size, and couldn't be manipulated before its real size reveal itself.

It looks more like internal media scanner issue, than anything to me.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] trohn_javolta:
Any way to fix that? That's a big showstopper for me. It's also present in Los 15.1.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Kernle 32DLL:
Finally got around to update from 15.1 to 16 last night. Since I was doing a wipe before anyway, I took the time to update all the firmware shenanigans beforehand, too (modem, etc. - see here).

The Rom works flawlessly - nothing more to say. Everything works, and is smooth.

So - thanks a lot for your work again, Ivan! You work really is making the difference!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] windfallprophet:
Is there any chance that this will work with the GearVR? I really want to switch to LineageOS, but I don't think it supports it.

Or can I emulate DayDream?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] fmlm78:
Thanks for your ROM. The problem of echo continues. When you are using the external speaker, the other person listens his own voice and this is very annoying. I hope you can solve this as soon as possible. Anyway, thanks again!
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] catfishes:
In developer options you can turn window and transition animations off, this makes the phone fly. :)
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Tagdu17:
Use search in thread

Could you use thread search bar man ?

Here is what I explained about that "issue" 3 pages before :
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] VoidedKN0X:
i have done that already but some animations that are not affected with those settings still lag, like launcher for example and sometimes even when i pull down my notification bar (i even had a clean install but that hasn't affected anything) might it be my device?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] specter16:
Emmc bro
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] mtpx7:
Wait, isn't LOS supposed to be faster/smoother than TW?

Wysłane z mojego SM-G930F przy użyciu Tapatalka
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Mint Julep:
Emmc?
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] shaggyskunk:
embedded Multimedia Card = eMMC & far to frequently fails on the Note 4 - Haven't heard of it being an issue on other Samsung devices ?

Sent from my SM-G975W ??
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] flunkyball:
First of all thanks for the great and hard work to get LOS 16 running smoothly on the S7.

I tried it out the past weekend and liked it very much. :good:

For those who are seeking a camera recommendation besides footej: I stumbled across the working gcam 5.1 port uniXCam from expressluke.ml

Finally I came across the following issue as well:

- After successfully using LOS 16 (dirty flash over 14.1) for 2 days I was not able to login to the phone after a reboot.

- On the login screen I entered the correct password, afterwards the screen turned black for 1sec, returned to the login and prompted again. This loop went on indefinitely. (yes, the password was correct, using a wrong password led to the corresponding error message)

I tried to erase Cache/Dalvik, flashed over the LOS 16 image again without any success.

In the end I had to restore a TWRP backup.

Has anyone else had such an experience ?

For now I would resolve this to the fact that I did a dirty flash over 14.1.

Cheers,

Flunkyball
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Tagdu17:
Did you already flash a custom ROM man ?

Android major upgrade = full wipe (data loss)

Moreover, YOU JUMPED AN ANDROID VERSION ! (Oreo - Android 8) :rolleyes:

You MUST do a clean install of LOS 16 !
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Seanthedroid:
Yes, fast-charging is working

You won't see a switch to turn it on anywhere, though, because it's always on by default and can't be turned off. Your phone will just...charge faster. It will suck up however much current is being provided up to the 15W wired or 10W wireless limit, as long as your cords, AC adapters, and pads are capable of fast charging as well. If you had fast charging on before you installed Lineage, you won't notice a difference.
[Samsung Galaxy S7 (Exynos) ROMs, Kernels, Recoveri] Apollo Hartigan:
Hi, i've try to use my Playstation 4 Controller. The controller connects over Bluetooth but no button is working. Does the kernel miss the module xinput?