system/vendor/mixer_paths_0.xmlplease give me the name of this file and if you remember where the configuration file is located, because I was looking for but I did not find it, I did 3 minutes to the village, best regards
system/vendor/mixer_paths_0.xmlplease give me the name of this file and if you remember where the configuration file is located, because I was looking for but I did not find it, I did 3 minutes to the village, best regards
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.
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
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
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..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 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 can confirm that one of the January builds was OK regarding voice calls quality.
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 differentI 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
First thing is related to google apps and not the rom itselfGreat 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
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 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
You clearly dont understand that ivan didnt make any change which would effect the problemNope, 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.
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.You clearly dont understand that ivan didnt make any change which would effect the problem
You probably didn't format system and data. This ROM does not have gapps included so clearly something went wrong.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?
Not convincing. Facts are not on your side.You clearly dont understand that ivan didnt make any change which would effect the problem
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)?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.
You were right. The format and wipe went wrong. I did it again and it works fine. Rhank you for the adviceYou probably didn't format system and data. This ROM does not have gapps included so clearly something went wrong.
/*
* 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.
*/
BTC: bc1qqan6m5tn284g38tu52nalc9x5z4all8z5geq6y
ETH(erc20): 0xB737100035a989fA9EaD13B81af2a32EFe6E1C0f