LineageOS 19.1 (Android 12L) [Signature Spoofing][OTA updates] for S7 Exynos

Search This thread

master373

Senior Member
Feb 1, 2022
85
30
system/vendor/mixer_paths_0.xml
I guess people just dont understand that not all s7's are identical. Thats why some do have problems and some dont. For an developer this is the worst scenario because it cannot be reproduced on development device. If there is no log apart from that practical use, than its like the bug doesnt exist. Its really hard to figure out that bug, if its not happening on your own device and theres even no log which says what is happening.
People just dont get that.
 

Yvonne5

New member
Jul 15, 2013
1
0
Samsung Galaxy S5
Here we go, issues with apps are resolved now (Thanks for breaking keymaster google, really cool)
14.03.2022.
- Fixed issue with keystore where apps would crash when invoking it (Security related apps mostly like signal and a lot of work apps)
- Officially rebranded as 19.1
- Updated changelog URL in updater app to point to a valid changelog
- Fixed battery icon styles (Again..)
- Removed invalid zram config.
- Cleaned up source
- Performance and stability improvements
- Updated some stock apps to math with new design
- Synced with LineageOS source

Once again sorry for inconvenience, also since lineageos bumped version to 19.1 yesterday you will have to manually install this update
next one will have ota as its 19.1 to 19.1 and no version bump, For zygisk use magisk 24.1 and if you cant find gapps i posted ones that work in the OP.
As this is version bump from 19.0 to 19.1 you WILL have to reinstall gapps as addon.d isnt executed

As always big thanks to everyone who supported this project and helped me cover build server cost and got me coffee, and once again sorry for issues with initial 12L build,
ENjoy new build and stay safe

I think the issue with Keystore is not fully fixed for Seedvault yet. I have the exact same issue as carallo has in this GitHub issue. He is also using LineageOS 19 on a S7. The code that interacts with the key store seems to be here.

Code:
04-20 12:26:11.889  4702  3208 I TLC_BAUTH: Call FP cmd 0x7;1308
04-20 12:26:11.890  4702  3208 I tlc_communication: Send Trustlet TCI Message;214
04-20 12:26:11.890  4702  3208 I tlc_communication: mcNotify is completed;224
04-20 12:26:11.913  3486  3486 W [email protected]: Not performing software digesting for symmetric cipher keys
04-20 12:26:11.913  3486  3486 W [email protected]: Not performing software digesting for symmetric cipher keys
04-20 12:26:11.914  3486  3486 I keymaster_tee: [INFO]:  (nwd_keymaster_mdfpp.cpp:817) entered import_key function.
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:36) *********print_params***********
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:37) params->length = 8
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_ALGORITHM params->params[0].tag = 0x10000002
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:48) tc_KM_ENUM 32 0x00000020
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_PURPOSE params->params[1].tag = 0x20000001
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 0 0x00000000
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_PURPOSE params->params[2].tag = 0x20000001
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 1 0x00000001
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_MIN_MAC_LENGTH params->params[3].tag = 0x30000008
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:60) tc_KM_UINT 96 0x00000060
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_BLOCK_MODE params->params[4].tag = 0x20000004
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 32 0x00000020
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_PADDING params->params[5].tag = 0x20000006
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 1 0x00000001
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_NO_AUTH_REQUIRED params->params[6].tag = 0x700001f7
04-20 12:26:11.914  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:56) tc_KM_BOOL 1 0x00000001
04-20 12:26:11.915  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_CREATION_DATETIME params->params[7].tag = 0x600002bd
04-20 12:26:11.915  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:76) tc_KM_DATE 0x180dedb88b8
04-20 12:26:11.915  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:95) *************************************
04-20 12:26:11.917  4702  3208 I tlc_communication: mcWaitNotification is completed;237
04-20 12:26:11.917  4702  3208 I TLC_BAUTH: Check the Trustlet return code is completed;1358
04-20 12:26:11.917  4702  3208 D bauth_FPBAuthService: FPBAuthService, 4195
04-20 12:26:11.917  4702  3208 D bauth_FPBAuthService: check_opcode status = 2, opcode = 7, func_ret_val = 0, function_status = 2, timeout = 50
04-20 12:26:11.921  3486  3486 D keymaster_tee: [DEBUG]: (nwd_keymaster_mobicore.c:353) TLC_COMMAND(e): cmd = 0x0000000A, ret = 0x00000000
04-20 12:26:11.921  3486  3486 I keymaster_tee: [INFO]:  (nwd_keymaster_mdfpp.cpp:826) exit import_key function, returns 0
04-20 12:26:11.933  3486  3486 I keymaster_tee: [INFO]:  (nwd_keymaster_mdfpp.cpp:817) entered import_key function.
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:36) *********print_params***********
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:37) params->length = 9
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_ALGORITHM params->params[0].tag = 0x10000002
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:48) tc_KM_ENUM 128 0x00000080
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_DIGEST params->params[1].tag = 0x20000005
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 4 0x00000004
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_MIN_MAC_LENGTH params->params[2].tag = 0x30000008
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:60) tc_KM_UINT 256 0x00000100
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_PURPOSE params->params[3].tag = 0x20000001
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 0 0x00000000
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_PURPOSE params->params[4].tag = 0x20000001
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 1 0x00000001
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_PURPOSE params->params[5].tag = 0x20000001
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 2 0x00000002
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_PURPOSE params->params[6].tag = 0x20000001
04-20 12:26:11.933  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:52) tc_KM_ENUM_REP 3 0x00000003
04-20 12:26:11.934  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_NO_AUTH_REQUIRED params->params[7].tag = 0x700001f7
04-20 12:26:11.934  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:56) tc_KM_BOOL 1 0x00000001
04-20 12:26:11.934  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:43)  tc_KM_TAG_CREATION_DATETIME params->params[8].tag = 0x600002bd
04-20 12:26:11.934  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:76) tc_KM_DATE 0x180dedb88b8
04-20 12:26:11.934  3486  3486 D keymaster_tee: [DEBUG]: (keymaster_packing.c:95) *************************************
04-20 12:26:11.939  3486  3486 D keymaster_tee: [DEBUG]: (nwd_keymaster_mobicore.c:353) TLC_COMMAND(e): cmd = 0x0000000A, ret = 0xFFFFFFFE
04-20 12:26:11.939  3486  3486 E keymaster_tee: [ERROR]: (nwd_keymaster_tc_api.c:1326) KM_TZRunCommand returned -2
04-20 12:26:11.939  3486  3486 I keymaster_tee: [INFO]:  (nwd_keymaster_mdfpp.cpp:826) exit import_key function, returns -2
04-20 12:26:11.940  4633  4637 E keystore2: keystore2::error: In import_key: Trying to call importKey
04-20 12:26:11.940  4633  4637 E keystore2:
04-20 12:26:11.940  4633  4637 E keystore2: Caused by:
04-20 12:26:11.940  4633  4637 E keystore2:     Error::Km(ErrorCode(-2))
04-20 12:26:11.941  2523  2523 D AndroidRuntime: Shutting down VM
04-20 12:26:11.941  3486  3486 I keymaster_tee: [INFO]:  (nwd_keymaster_mdfpp.cpp:862) entered delete_key function.
04-20 12:26:11.941  2523  2523 E AndroidRuntime: FATAL EXCEPTION: main
04-20 12:26:11.941  2523  2523 E AndroidRuntime: Process: com.stevesoltys.seedvault, PID: 2523
04-20 12:26:11.941  2523  2523 E AndroidRuntime: java.lang.RuntimeException: java.lang.reflect.InvocationTargetException
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:558)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
04-20 12:26:11.941  2523  2523 E AndroidRuntime: Caused by: java.lang.reflect.InvocationTargetException
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     ... 1 more
04-20 12:26:11.941  2523  2523 E AndroidRuntime: Caused by: java.security.KeyStoreException: Failed to import secret key.
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.security.keystore2.AndroidKeyStoreSpi.setSecretKeyEntry(AndroidKeyStoreSpi.java:807)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.security.keystore2.AndroidKeyStoreSpi.engineSetEntry(AndroidKeyStoreSpi.java:1177)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at java.security.KeyStore.setEntry(KeyStore.java:1596)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at com.stevesoltys.seedvault.crypto.KeyManagerImpl.storeMainKey(KeyManager.kt:80)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at com.stevesoltys.seedvault.ui.recoverycode.RecoveryCodeViewModel.storeNewCode(RecoveryCodeViewModel.kt:90)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at com.stevesoltys.seedvault.ui.recoverycode.RecoveryCodeInputFragment$storeNewCodeAfterAuth$callback$1.onAuthenticationSucceeded(RecoveryCodeInputFragment.kt:174)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.hardware.biometrics.BiometricPrompt$1.lambda$onAuthenticationSucceeded$0$BiometricPrompt$1(BiometricPrompt.java:485)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.hardware.biometrics.BiometricPrompt$1$$ExternalSyntheticLambda2.run(Unknown Source:4)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.os.Handler.handleCallback(Handler.java:938)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:99)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.os.Looper.loopOnce(Looper.java:201)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.os.Looper.loop(Looper.java:288)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:7870)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     ... 3 more
04-20 12:26:11.941  2523  2523 E AndroidRuntime: Caused by: android.security.KeyStoreException: Unsupported purpose
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.security.KeyStore2.getKeyStoreException(KeyStore2.java:356)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.security.KeyStoreSecurityLevel.handleExceptions(KeyStoreSecurityLevel.java:57)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.security.KeyStoreSecurityLevel.importKey(KeyStoreSecurityLevel.java:166)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     at android.security.keystore2.AndroidKeyStoreSpi.setSecretKeyEntry(AndroidKeyStoreSpi.java:804)
04-20 12:26:11.941  2523  2523 E AndroidRuntime:     ... 15 more
 
Last edited:

chomsky55

Senior Member
Sep 21, 2020
219
67
Samsung Galaxy S7
OnePlus 5T
Is there any advantage - concerning the update (new build of identical version) or upgrade (e. g. Lineageos 18 -> 19) process itself on the phone - of sideloading a new build via adb instead of using TWRP to flash the zip file(s)?
I am thinking about switching from 18.1 to 19.1 and wonder if sideloading might circumvent problems coming with the TRWP way, since most guides mention sideloading instead of flashing in TWRP …
I'm not a custom ROM guru but I think that sideloading ( also uses TWRP ) or using TWRP directly is no different in most cases unless the developer explicitly mentions to sideload. Why you ask? don't know why..

I myself dirty flashed this ROM coming from CrDroid 7 and everythings works. I do get this error popping up regularly that "Intent Filter Verification Service keeps stopping". It let me keep al my apps and data so I'll take that trade, assuming that this is related to the dirty flash.
 
Jul 8, 2015
21
11
I can confirm that one of the January builds was OK regarding voice calls quality.
I second that. And it actually was with the build that @Ivan_Meler mentioned (the one that moved audio to vendor) when the audio issues first appeared on my device. In the change log I could not find any obviously audio-related changes except for the move to vendor. So I guess that it may have been a collateral damage introduced by one of the changes.

I guess most of us know that it is pretty much impossible to debug an issue that happens only on others' systems. So thank you for trying anyway! Maybe let's see if one of us who have the issue can find a hint to where it comes from and how to fix it. @Ivan_Meler: Do you maybe still have the two Jan builds (the one before and the one with audio in vendor) or even a git branch with their changes that one could clone?
 
  • Like
Reactions: bixaon and hmendes3

pawpawel

Senior Member
Jul 3, 2014
99
10
Siedlce
Hey, someone will suggest or toss files to make the PS4 pad work sometimes but no movements Hey, someone will suggest or toss files to make the PS4 pad work sometimes but no movements
 

Ivan_Meler

Forum Moderator / Recognized Developer
Staff member
I second that. And it actually was with the build that @Ivan_Meler mentioned (the one that moved audio to vendor) when the audio issues first appeared on my device. In the change log I could not find any obviously audio-related changes except for the move to vendor. So I guess that it may have been a collateral damage introduced by one of the changes.

I guess most of us know that it is pretty much impossible to debug an issue that happens only on others' systems. So thank you for trying anyway! Maybe let's see if one of us who have the issue can find a hint to where it comes from and how to fix it. @Ivan_Meler: Do you maybe still have the two Jan builds (the one before and the one with audio in vendor) or even a git branch with their changes that one could clone?
you have no idea how much nonsense you are talking right now, its like saying moving song from desktop to some folder makes it sound different
 

master373

Senior Member
Feb 1, 2022
85
30
you have no idea how much nonsense you are talking right now, its like saying moving song from desktop to some folder makes it sound different

I googled a bit and found only this:

Its an different device although but maybe its a hint for something. Maybe people who have this Problem can switch to 2g only and look if its happening.
I apolige if this dont make sense at all but atleast i try to find a soulution that maybe makes sense to you. 3G is gone in some countries and that could be maybe the reason some has this issue and some dont. So it could be a operator problem and not a rom problem at all
 
Last edited:

bigsterer

Member
Jun 15, 2021
8
1
Great ROM. Done clean flash and installed the same Gapps in OP.

Only problems I have so far:
- Google Opinion Rewards not working
- No built in blue light filter
 

Ivan_Meler

Forum Moderator / Recognized Developer
Staff member
Great ROM. Done clean flash and installed the same Gapps in OP.

Only problems I have so far:
- Google Opinion Rewards not working
- No built in blue light filter
First thing is related to google apps and not the rom itself
There definitely is blue light filter, Go to settings>display>LiveDisplay>Display Mode
 
  • Like
Reactions: bigsterer

derders

Senior Member
Oct 2, 2011
95
28
@Ivan_Meler

thank you very much for all your work on our lovely S7! I mean really thank you! :)

Had for years your 15.1 Version installed and switched to 19.1. It runs like butter!


I don't know if this is a lineage os 19 problem or just from this rom, but I can't add a vpn connection.
There is no option in the vpn menu. Is this only for me, not added option at this development stage or a general LOS 19 problem atm?



My Screen in VPN Settings --- without the plus icon on right top corner.
Screenshot_VPN.png
 
Jul 8, 2015
21
11
you have no idea how much nonsense you are talking right now, its like saying moving song from desktop to some folder makes it sound different
Nope, I am exactly not saying that. I say that one of the changes in that particular build did have the effect because the builds before where fine in terms of audio and all the ones after that were not. I am NOT saying that it is the move in the folder structure.
 

master373

Senior Member
Feb 1, 2022
85
30
Nope, I am exactly not saying that. I say that one of the changes in that particular build did have the effect because the builds before where fine in terms of audio and all the ones after that were not. I am NOT saying that it is the move in the folder structure.
You clearly dont understand that ivan didnt make any change which would effect the problem
 

BroPl

Member
Dec 8, 2014
16
11
Hello,

I've just wiped out everything from the phone (I had LoS 19.1 and Gapps) and installed only latests LoS 19.1 build and I have Play Store app. I would like to have "clean" (meaning no google whatsoever) phone how can I do it?
 
Jul 8, 2015
21
11
You clearly dont understand that ivan didnt make any change which would effect the problem
For starters, I don't even say that the problem is necessarily a change that Ivan made; it may be a change in the synced LOS source for all we know! But the problem is definitely one (or multiple) of the things that changed between the previous build and the one that moved audio to vendor.

Nonetheless, what you are implying with your statement? Do you believe in the kind of magic that makes phone audio break for many devices exactly at the time they install the same update but it has nothing to do with the underlying code? Come on, give me a break! EDIT: Thanks for the hint toward the 3G issue, but the fact still remains that the issue only occurs with and after that particular build. Even if the undesirable behavior is on the network/operator side, it only happens to give problems together with the ROM versions after that Jan build. So finding the code change in question would at least open the door for a workaround.

To clarify: I am not criticizing @Ivan_Meler or his work. In fact, I appreciate his effort very much! His work is the reason why I am still hanging on to this phone! So what I am saying is that I don't even expect Ivan to fix the issue because he has no way of reproducing it. But those who can reproduce the problem don't have access to the code changes, which prevents them from hunting the bug down. If the code changes of that particular build were accessible there would be a reasonable chance that one of us finds the issue.
 
Last edited:

bixaon

Member
Feb 19, 2022
28
19
I guess people just dont understand that not all s7's are identical. Thats why some do have problems and some dont. For an developer this is the worst scenario because it cannot be reproduced on development device. If there is no log apart from that practical use, than its like the bug doesnt exist. Its really hard to figure out that bug, if its not happening on your own device and theres even no log which says what is happening.
People just dont get that.
What types of SM-G930F do you know? Can we find out the exact difference between our devices relatively to sound chip (id or something like that)?
We all don't get something unless try to find out the reason.
 

tureture

New member
May 18, 2022
2
0
Hello everyone, I hope this is not too off topic as I'm pretty desperate at the moment. I just tried updating to the latest Lineage OS version through a dirty flash, and after I got stuck in a bootloop, I tried going into the Lineage OS Recovery menu, and I formatted both the cache and system. After I did that, my phone now bootloops on the Galaxy screen, so I tried getting TWRP with odin again and now, it gets stuck on the TWRP splash screen.

After all of that I thought that I might just have to reflash the original firmware, so I went and downloaded the S7 firmware from sammobile, and while trying to flash, odin gets stuck on "Set Partition"

Is my phone bricked or can I do anything to recover this?

Edit: apologizes, I managed to get back to the official firmware. we good
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    And here we go as prommised, new build with improved in call audio quality and June security update
    - Merged June 2022. security update
    - Merged June 2022. pixel feature drop (SQ3A.220605.009.A1)
    - Improved in-call audio quality drastically
    - Addressed few more selinux denials
    - Improved general stability and performance
    - Cleaned up source
    - Synced with LineageOS source

    Once again huge thanks to everyone who supported this project, helped cover the build server cost and got me a coffee, this project wouldnt be possible without support of the comunity and s7 wouldnt still be running latest OS with latest security updates over 6 years after launch

    18.1 and 17.1 builds will be out over the coming days
    Enjoy new build and stay safe
    19
    New update will fix in call audio quality
    there was a weird bug in audio hal that was causing it.

    Big thanks to @Bujiraso for playing with props and audio configs which at the end lead me to finding bug in audio hal.

    Now im only waiting for google to push June security update source so I can start compiling builds and release them
    16
    New builds are up here and via ota
    - Fixed issues with keystore present in a lot of bank/secure apps like binance
    - Fixed issue where setupwizard would crash when adding fingerprint due to bug in keystore
    - Cleaned up patches required for build and removed unneeded ones
    - Synced with LineageOS source

    This was one of hardest things to track down and it prevented some security related apps from working, big thanks to everyone who supported this project and got me coffee (This took over a month on and off time to debug and figure out, one of weirdest error caused by googles keystore changes in android 12) and thanks to those who helped cover the build server cost

    Enjoy new build and stay safe
    12
    I havent posted an actual progress update in quite some time so here is some behind the scenes.
    • HWC And most of display hals will be updated and open sourced
    • Keystore will also be looked into a bit further to see if there are edge cases left where some secure apps break
    • OMX again without going into too much details we will see some changes on that end and it will be open sourced
    • Camera, well ill just let this one be a surprise for now since it will require most work
    There is a lot more going behind the scenes and some of those changes will take some time (Keep in mind i do this in my free time so i really cant talk about etas) but in general once most of those chanegs are up 8890 devices will be in perfect condition and once Android 13 source is out it won't take too long to get it working.

    Some other small notes since s7 i use to develop this rom on has broken screen (i use scrcpy to mirror screen on pc)
    feel free to send me message with any good deals you find on 8890 device be it s7 s7 edge or note fe

    And finally HUGE thanks to everyone who supported this project and helped cover the build server cost, thius project really wouldnt be possible without them, They also covered the coffee cost and some stuff like recent keystore fixes really took a long time to debug which indeed required a lot of coffee at night haha.
    2
    I was able to do it friend, I think the problem is that it has to be the latest version of TRWP and the latest version of magisk, otherwise it won't work, anyway thanks for the help! 🙏
  • 62
    k5tUT1V.png

    LineageOS 19.1 for herolte

    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    */

    Working:
    - Wifi
    - Sound
    - mali drivers
    - USB tethering
    - HW Backed video Playback
    - Ril (Mobile data,calls, sms and stuff)
    - Sensors
    - Buttons
    - Bluetooth
    - Wifi HotSpot
    - MTP
    - 2D and 3D gpu acceleration
    - HW encoding/decoding
    - HWcomposer (HWC)
    - Charging with device powered off
    - Stuff I didn't test yet
    - Camera
    - GPS
    - Fingerprint Sensor
    - Mobicore
    - SW codecs

    Not Working
    -


    Keep in mind that some LineageOS features have not been completed yet this is not a device bug and please do not report those
    in this rom thread, 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



    Install gapps right after installing the rom itself don't try to boot to system before that if you want to use gapps (Or wipe data before installing them)

    Make sure gapps you decide to use support android 12L/12.1/Are targetting api level 32
    Also make sure you are using latest official TWRP before installing rom older versions do not have proper android 12 support

    If you want to use Magisk use latest Magisk Beta (25.0) or Magisk 24.1, there is bug in 24.3 that was fixed after its release that prevents zygisk from working on some devices with 3.18 kernel

    Downloads:
    Google Drive
    Mega.nz
    GitHub Releases
    MD5: 91b6a3fbc9717b46e9a2bce054af10b6


    if you want to support the project feel free to buy me some coffee paypal.me/ivanmeler

    BTC: bc1qqan6m5tn284g38tu52nalc9x5z4all8z5geq6y
    ETH(erc20): 0xB737100035a989fA9EaD13B81af2a32EFe6E1C0f
    Donations help cover the build server cost and since I do this in my free time, and also cover the coffee for time spent debugging stuff



    Feel free to join telegram group with early builds progress updates and some off topic stuff Join

    Based On Android 12L/S
    Changelog

    24.06.2022.
    - Fixed issues with keystore present in a lot of bank/secure apps like binance
    - Fixed issue where setupwizard would crash when adding fingerprint due to bug in keystore
    - Cleaned up patches required for build and removed unneeded ones
    - Synced with LineageOS source

    07.06.2022.
    - Merged June 2022. security update
    - Merged June 2022. pixel feature drop (SQ3A.220605.009.A1)
    - Improved in-call audio quality drastically
    - Addressed few more selinux denials
    - Improved general stability and performance
    - Cleaned up source
    - Synced with LineageOS source

    26.05.2022.
    - Updated libexynosdisplay from BSP to comply with some android 12 changes
    - Removed unused build.prop entries
    - Fixed few selinux denials related to hwc props
    - Improved UI performance and stability
    - Cleaned up source
    - Removed more unneeded patches for device support
    - Synced with LineageOS source

    18.05.2022.
    - Added QR code reader quick settings toggle
    - Improved device performance and stability
    - Added Custom low power mode power profile for cpu
    - Improved A-GNSS (A-GPS) Lock speed
    - Exposed device hw revision to settings
    - Improved fast/slow charger detection
    - Synced with LineageOS source

    10.05.2022.
    - Switched to new libperfmgr power hal which can be configured from /system/vendor/etc/powerhints.json
    - Adapted DT2W to new power hal
    - Muted phone services gps notif (Thanks google really appreciate you breaking random things for everyone)
    - Improved battery life and performance
    - Cleaned up all of leftover patches that were used by legacy power hal
    - Synced with LineageOS source

    07.05.2022.
    - Improved battery usage logging for display
    - Added QR code reader to camera app (Long hold icon and launch it from context menu)
    - Misc performance and stability improvements
    - Merged May 2022. security update
    - Synced with LineageOS source

    27.04.2022.
    - Removed libbfqio dependency from hwc since it was dropped from lineageos 19.1
    - Misc performance and stability improvements
    - Synced with LineageOS source (same base as official builds + some extras)

    18.04.2022.
    - Fixed bug wehre vibrations were too low on some devices due to inintensity being set to 0
    - Fixed bug where apps would show square popup "animation" when launching from icon instead of roudned one
    - Cleaned up build patches
    - Synced with LineageOS source

    15.04.2022.
    - Updated sepolicy and merged updated common samsung_slsi sepolicy
    - Increased microphone gain while recording media (Camcorder, voice recording etc.)
    - Added option to disable vibration feedback on fingerprint auth
    - Synced with LineageOS source

    08.04.2022.
    - Fixed extended volume panel
    - Updated icons for few more stock apps
    - Cleaned up patches further
    - Misc peroformance improvements
    - Synced with LineageOS source

    06.04.2022.
    - Merged April 2022. Security update
    - Enabled new LineageOS icons (you might have to clear launcher cache for them to show up)
    - Fixed issue where galery app would show black text on black background
    - Fixed issue where unlock sound would sometimes play twice
    - Misc performance and stability improvements
    - Synced with LineageOS source

    29.03.2022.
    - Drastically speed up app launch time (more info about that here)
    - Imrpoved performance and battery life by disabling some unnecessary logging
    - Switched to source built camera provider and removed samsung proprietary one
    - Upreved camera provider to 2.5
    - Fixed few selinux denials related to NFC trying to raad debug props
    - Removed floating_feature.xml which is unused on aosp
    - Disabled livedisplay by default
    - Cleaned up extra dependencies used for compiling
    - Synced with LOS source

    22.03.2022.
    - Added back configurable audio volume panel location
    - Speed up unlock with fingerprint
    - Updated a lot of apps to MaterialYou design language
    - Fixed issue where touch screen area bellow home button would act as a gesture area even while gestures are disabled
    - Improved stability of ADB connection
    - Implemented new LineageOS setupwizard
    - Cleaned up device tree and list of required patches
    - Stability and performance improvements
    - Pointed Changelog url in updater app to new page
    - Synced with LineageOS source

    14.03.2022.
    - Fixed issue with keystore where apps would crash when invoking it (Security related apps mostly like signal and a lot of work apps)
    - Officially rebranded as 19.1
    - Updated changelog URL in updater app to point to a valid changelog
    - Fixed battery icon styles (Again..)
    - Removed invalid zram config.
    - Cleaned up source
    - Performance and stability improvements
    - Updated some stock apps to math with new design
    - Synced with LineageOS source

    10.03.2022.
    - Merged March 2022. security and feature updates (Android 12L)
    - Fixed status bar network trafic monitor
    - Improved zram performance and enabled zram writeback
    - Cleaned up patches needed for build
    - Fixed network usage monitoring
    - Fixed per app network restrictions
    - Removed AudioFX which was causing issues
    - Decreased microphone and earpiece gain a bit to mitigate in-call issues
    - Updated some device control apps like advanced display settings
    - Improved vibrator intensity in new hal
    - Imrpoved fp sensor response time
    - A lot of 'under the hood' changes
    - Performance improvements
    - Merged more previously missing los features
    - Implemented OTA updates

    10.02.2022.
    - Merged February 2022. security update
    - Removed broken volume button location toggle
    - Synced with LOS source

    09.02.2022.
    - Fixed issue where camera would stop working after prolonged use
    - Misc performance and stability improvements
    - Merged some more lineageos features that have been posted to gerrit
    - Synced with LOS source

    28.01.2022.
    - Fixed developer options crashing on launch
    - Added Bluetooth SBC Dual Channel HD audio mode
    - Synced with LOS source

    27.01.2022.
    - Added back lineageos setup wizard present on clean installs
    - Merged some of previously missing features that have been ported over to LineageOS 19
    - Performance and stability improvements
    - Synced with LOS source

    18.01.2022.
    - Enabled selinux (Its enforcing now)
    - Moved audio hal to vendor
    - Fixed confirmation dialog box for button backlight
    - Fixed ok button which would go missing for button backlight
    - Switched to source built secril_config_svc (used for ds detection)
    - Removed obsolete debug.sf.disable_backpressure prop
    - Merged latest security updates to kernel from aosp kernel/common
    - Cleaned up source
    - Cleaned up unused props
    - Removed unused custom ld.config.txt that was overriding main one
    - Misc performance and stability improvements
    - Synced with LOS source

    06.01.2022.
    - Removed duplicate props in vendor and system
    - Cleaned up device tree code
    - Switched to source built camera provider lib
    - Switched to few source built ril related libs
    - Addressed more selinux denials
    - Fixed volume panel location settings
    - Added button backlight
    - Added Advanced Reboot
    - Added LiveDisplay entry into settings
    - Added system side toggle for navigation bar
    - Merged January 2022 Security Update
    - Merged most of previously missing LineageOS features
    - Misc performance and stability improvements
    - Synced with LOS source


    20.12.2021.
    - Fixed wireless display
    - Reduced logspam which should imrpove performance a bit
    - Misc performance and stability improvements
    - Synced with LOS source

    16.12.2021.
    - Merged r18 tag of Android 12 (SQ1D.211205.016.A1)
    - Removed liboemcrypto which was preventing drm playback in some apps
    - Synced with LOS source

    13.12.2021.
    - Updated Clearkey to 1.4
    - Addressed most of selinux denials
    - Switched to new AIDL Lights hal
    - Upreved audio hal to 7.0
    - Switched to new AIDL Vibrator hal
    - Disabled configstore which got replaced with props
    - Upreved fingerprint hal/service to 1.3
    - Removed unused kernel defconfig flag
    - Synced with LOS source

    09.12.2021.
    - Merged December 2021. Security update
    - Merged December 2021 pixel feature drop
    - Added signature spoofing support which can be used to add microg instead of gapps
    - Merged a lot of lineageos features that have been implemented
    - Fixed bluetooth sample rate while in call
    - Moved device specific ueventd rules to /system/vendor/etc
    - Freed up some ram
    - performance and stability improvements

    30.11.2021.
    - Initial release



    XDA:DevDB Information
    LineageOS 19.0 for S7, ROM for the Samsung Galaxy S7

    Contributors
    Ivan_Meler
    Source Code: https://github.com/8890q/android_kernel_samsung_universal8890/tree/lineage-19.0

    ROM OS Version: Android 12L
    ROM Kernel: Linux 3.18.x

    Version Information
    Status:
    Stable
    23
    Since my birthday is tomorrow I decided to release a little surprise build. Here is a brief changelog:
    - Updated libexynosdisplay from BSP to comply with some android 12 changes
    - Removed unused build.prop entries
    - Fixed few selinux denials related to hwc props
    - Improved UI performance and stability
    - Cleaned up source
    - Removed more unneeded patches for device support
    - Synced with LineageOS source

    Im aware of Seedvault issue curently present and im working on a fix for it.
    I wanted to release something as a gift from me to everyone using this rom and supporting this project throughout the years. Keeping older phones alive and up to date is really fun hobby and I don't think I would've kept doing it if it wasnt for all of the support from the comunity.

    Once again big thanks to everyone who helped cover the build serve cost and coffee.

    Enjoy new build and stay safe
    21
    And here we go as prommised, new build with improved in call audio quality and June security update
    - Merged June 2022. security update
    - Merged June 2022. pixel feature drop (SQ3A.220605.009.A1)
    - Improved in-call audio quality drastically
    - Addressed few more selinux denials
    - Improved general stability and performance
    - Cleaned up source
    - Synced with LineageOS source

    Once again huge thanks to everyone who supported this project, helped cover the build server cost and got me a coffee, this project wouldnt be possible without support of the comunity and s7 wouldnt still be running latest OS with latest security updates over 6 years after launch

    18.1 and 17.1 builds will be out over the coming days
    Enjoy new build and stay safe
    20
    New builds are up mainly to bring them inline with official lineageos 19.1 builds when it comes to features, here is a brief changelog
    - Removed libbfqio dependency from hwc since it was dropped from lineageos 19.1
    - Misc performance and stability improvements
    - Synced with LineageOS source (same base as official builds + some extras)

    Big thanks to everyone who supported this project so far and helped me cover the build server cost with donations and also got me coffee
    Enjoy new builds and stay safe
    19
    Well here we go first build of the year, andquite a big one while at it
    Here is a brief changelogbut there are a lot more changes you will discover in this build
    - Removed duplicate props in vendor and system
    - Cleaned up device tree code
    - Switched to source built camera provider lib
    - Switched to few source built ril related libs
    - Addressed more selinux denials
    - Fixed volume panel location settings
    - Added button backlight
    - Added Advanced Reboot
    - Added LiveDisplay entry into settings
    - Added system side toggle for navigation bar
    - Merged January 2022 Security Update
    - Merged most of previously missing LineageOS features
    - Misc performance and stability improvements
    - Synced with LOS source

    Updates for Android 11 and 10 should be out next week

    About camera, As some of you might be aware camera tends to crash afterprolongued use, Im investigatinga fix for it but due to nature of issue itself it might take time
    to figure this out completely and what the best way to deal with it is.

    Andfinally huge thanks toeveryonewho supported this and other projects of mine so far as they help me cover the build server cost and get me a coffee with their donations, 2022 marks 5 years since release of s7 and im glad i can help in keeping them alive on latest android version with latest security updates
    Hope you all had great holidays, Enjoy new build and stay safe in 2022