[ROM] [P-T] LineageOS 16.0 - 20.0 with microG for Samsung S7 Flat/Edge

[ProjectSource]

Great work Exodusnick!

I'm on LineageOS 16. Tried OTA update. It always works. But now it keeps saying "The update verification failed". Any ideas?

 

[Exodusnick]

Great work Exodusnick!

I'm on LineageOS 16. Tried OTA update. It always works. But now it keeps saying "The update verification failed". Any ideas?

Can you tell me also which version you are (date)

I think you still have an old version with old dev key. I had to renew it. You can install the update manually via twrp. With the next update OTA update works again

 

[ProjectSource]

Can you tell me also which version you are (date)

LineageOS 16.0 on version 9 October 2020.

I think you still have an old version with old dev key. I had to renew it. You can install the update manually via twrp. With the next update OTA update works again

Sure thanks, I'll give this a go later tonight.

 

[Exodusnick]

Yes it does, install the build of 20201217 manually via twrp , and then go through the lineagos updater and download the latest build and you will see that it works.

 

[Exodusnick]

only for lineageos 17.1 microg rom
If you are updating from build, clean install or remove passwords, who don't do it you need to delete it via twrp

/data/system/locksettings.db
/data/system/locksettings.db-shm and
/data/system/locksettings.db-wal delete

Unfortunately, they have to do it because to fix fingerprint authentication for third-party apps, we had to revert to Oreo-Mobicore, Gatekeeper, Keymaster, and fingerprint blobs that use legacy paths to store the fingerprint

new update available via ota or see download link

Changelog
- Synced with LOS source

Download link Samsung s7 flat (herolte)

lineage-17.1-20210107-microG-signed-herolte.zip

 

[swot_thomper]

only for lineageos 17.1 microg rom
If you are updating from build, clean install or remove passwords, who don't do it you need to delete it via twrp

/data/system/locksettings.db
/data/system/locksettings.db-shm and
/data/system/locksettings.db-wal delete

Unfortunately, they have to do it because to fix fingerprint authentication for third-party apps, we had to revert to Oreo-Mobicore, Gatekeeper, Keymaster, and fingerprint blobs that use legacy paths to store the fingerprint

neues update verfügbar via ota oder siehe dowload link

Changelog
- Synced with LOS source

Download link Samsung s7 flat (herolte)

lineage-17.1-20210107-microG-signed-herolte.zip

I installed this and its working great so far.

I'm curious about whether wireguard is included in the kernel. From what I understand, it should be, however the wireguard app seems to show 'userspace backend' instead of 'kernel backend'.

Appreciate your work and your feedback.

 

[Exodusnick]

Wireguard is an advanced solution for accessing vpn networks. However, for the "backend kernel" to work, it must be rooted. Wireguard is supported from version S (12) and officially integrated into Android.

 

[kjoetom]

I may have good news for some of you whose counterparts complain about strong echoes.

Echoes are possibly caused by the SIM card (or perhaps the provider), and not by the ROM. I have this suspicion after installing the latest version (lineage-17.1-20210107-microG-signed-herolte) on a second S7 (herolte) and inserting a sim card from another provider for testing purposes.

When calling with my own phone and my sim-card, the called party had a really disturbing echo, but when calling with the other phone, there was no echo at all. After I swapped the sim cards between the phones, it was the other way around.

Can anyone confirm or verify this? I have to admit that the "problematic" sim card is an older one and was reduced to the size of a nano sim card by myself.

I will get myself a replacement sim card in the next few days. I will report the results here as then I can narrow down whether it was due to the sim card or perhaps the provider.

kjoe

 

[Exodusnick]

@kjoetom
Thanks for your message .

I can confirm it with the echo .
With one sim card I had no echo at all but with the second sim card I had echo . Possible cause could be the ril.

Another question for you:
How is the reception strength with you in the top right of the status display ? I have tested it with an app and this shows me that it is at dbm 99 in the Edge network. Normally, a perfect network should have a value between -60 to -92dBm.

Test *#*#4636#*#*

 

[Exodusnick]

But there is something wrong. In both screenshots, an untopical difference is displayed. Seems to be only a display error, would have to fix the maintainer should be nothing big. @Ivan_Meler ?

 

[kjoetom]

@kjoetom

Test *#*#4636#*#*

Enclosed you will find the phone info for the two SIM cards. I am aware that one is UMTS and the other is LTE. However, it is probably not because of this, since the echoes occur regardless of location.

I have already ordered the replacement SIM and hope to receive it tomorrow or the day after. I will then immediately test it and report here.

kjoe

 

[Exodusnick]

@kjoetom Thanks for your quick reply

Colleague my question has had nothing to do with the echo . It bing only about the network display top right. But I see it is with you just like with me . (A display error) I would wish that it is fixed by the two Dev.
@Ivan_Meler and His colleague.

 

[kjoetom]

I've received my replacement SIM card today and full of hope, I immediately inserted it into the S7 to test.
I'm sorry if I raised false expectations with my previous post. The echo is unfortunately unchanged despite the new SIM card and quite annoying for the remote side.
I can now at least rule this out as the cause of the echoes.

Either it is really due to the provider (maybe there are technical differences) or it could be due to the type of connection (LTE vs. UMTS), which I will test in the next step.

kjoe :-(

 

[sirmacik]

Hi @Exodusnick,
Great job on the roms, thank you!

Unfortunately I'm unable to upgrade to latest 17.1 builds. I'm on 20200721 right now and after upgrade to 20210107 via TWRP it won't start. Meaning I get different (full) keyboard for unlocking my phone and after that it tells me that password is good, but it can't decrypt the data. Option to erase data doesn't change anything.

I've tried so far:
- erasing lockfiles and *key from /data/system,
- removing password/any protection needed to unlock the phone, twrp starts then without password prompt and works, but after update lineage still asks for password

It works again when I downgrade to 20200721.

I hope you can help with this.
Thanks again
sirmacik

 

[Exodusnick]

15.012021. build 20 new update lineageos 17.1 microG available via ota or see download link info for those who have not installed the build 19 from 20210107. Before installing the January 2021 build, remove fingerprints and delete /data/system/locksettings.db. This is required due to a version change by Mobicore to help fix fingerprinting on third-party secure apps Changelog taken from the main build of @Ivan_Meler - Fixed issues with fingerprint in 3rd party secure apps (banking apps paypal password managers) - Updated prebuilt binaries - Cleaned up mixer paths - Added neural network drivers - Disabled p2p mac randomization - Fixed wifi direct - Removed unused 32bit drivers - Improved performance and stability - A lot more unmder the hood changes - Merged januar 2021 Security Update Changelog microG - GmsCore: Update to 0.2.17.204714 - FDroid: update to 1.10 download link herolte: lineage-17.1-20210115-microG-signed-herolte.zip

 

[sirmacik]

15.012021. build 20 new update lineageos 17.1 microG available via ota or see download link info for those who have not installed the build 19 from 20210107. Before installing the January 2021 build, remove fingerprints and delete /data/system/locksettings.db. This is required due to a version change by Mobicore to help fix fingerprinting on third-party secure apps Changelog taken from the main build of @Ivan_Meler - Fixed issues with fingerprint in 3rd party secure apps (banking apps paypal password managers) - Updated prebuilt binaries - Cleaned up mixer paths - Added neural network drivers - Disabled p2p mac randomization - Fixed wifi direct - Removed unused 32bit drivers - Improved performance and stability - A lot more unmder the hood changes - Merged januar 2021 Security Update Changelog microG - GmsCore: Update to 0.2.17.204714 - FDroid: update to 1.10 download link herolte: lineage-17.1-20210115-microG-signed-herolte.zip

No change for my error :<

 

[Roberto W.]

No change for my error :<

backup ur data and then make a clean install. after this u can encrypt ur data again.

 

[sirmacik]

backup ur data and then make a clean install. after this u can encrypt ur data again.

Uh, that's bad news. Thanks.

 

[Exodusnick]

New build update for los microG 16.0 available via ota or see download link.

Changelog
- Synced with LOS source
- Merged Jan. 2021. Security update

Changelog microG
- GmsCore: Update to 0.2.17.204714
- FDroid: update to 1.10

download link Samsung S7 Flat (herolte)
lineage-16.0-20210116-UNOFFICIAL-microG-signed-herolte.zip

 

[LucN31]

Hi,

Yesterday, I updated with ROM (available via OTA updates)
https://los-legacy.de/herolte/lineage-17.1-20210126-microG-signed-herolte.zip
Thx Christian for this work.

After boot Everything is fine until the cover is closed, after, logic is inverted : Normal screen is displayed when cover is closed (even when message "smart cover detected" is displayed), and "closed" screen is displayed when cover is open.
It's not possible to use phone thru the cover ;-)

Is there a way to revert this state from ADB or TWRP or disable smartcovert function ?
I don't see it in display parameters.

To verify ROM impact, is it possible to downgrade ROM without clean install (just cleaning the cache) ?

Thx,
Luc.