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

Search This thread

ttmob4

Senior Member
Nov 1, 2007
78
22
@ttmob4 , is there any way to remove BitGapps that I had installed as "System Image", and install NikGApps or any other packages are? Else, instead, if I flash NikGApps on top of BitGapps using TWRP, will new package get installed? Is there any known issues afterwards? Thanks for your time Chief!
I don't think you can dirty flash NikGapps after having Systemless BitGapps...or if you can I could not work out how to do this. I did a full back up in TWRP and also in the phone backed up all of my settings, apss like WhatsApp, Signal, Nova Launcher, Bubble UpNP, SMBsync2, Musicolette (I use this in AA and for local.music) AND then a full back up in MIGRATE. I then did a clean flash, brought back my apps using MIGRATE (if you have not done this you can find info on XDA...it seems reliable to me...have done it a few times now), loaded magisk, safetynet fix, reloaded Nova configuration...then set up my settings in the phone. The above is not quick....2-3 hours at least.
 

ttmob4

Senior Member
Nov 1, 2007
78
22
Does anybody know were to locate

That's not what I meant, I could have been more clear ;-).

No need to built anything.
To be able to use Android Auto you need to have a stub 'installed' before your first boot. It is not the app itself, it is kind of a placeholder if I understand correctly. Opengapps (on lineageos 18.x) always includes it, but did not at first. I do not know if Bitgapps of NikGapps includes it by default.

I have flashed Lineageos, 19.1 NikGapps-core-arm64-12.1-20220501-signed.zip and NikGapps-Addon-12.1-AndroidAuto-20220421-signed.zip in that order.

It all works like a charm.
Agree...I use those versions of NikGapps and AA addon and also good for me.
 

BroPl

Member
Dec 8, 2014
17
11
Hi. Today I reinstalled latest version of this ROM and interesting thing was that when I had it without NikGapps I had a robotic sound on calls after reinstalling with NikGapps the problem disappeared
 
  • Wow
Reactions: Bujiraso

Bujiraso

Member
Apr 24, 2013
14
2
Can anyone confirm that Orgzly's widget isn't working on the default launcher?

1. Download http://www.orgzly.com/
2. Create a Saved Search widget
3. Using the default "Agenda" search, add an item using the "+" and return to the home screen
4. Interact with the new item you added (either check it off or tap the text)

Expected: it works
Actual: the launcher crashes

Here's a logcat from the last build (new build has the same problem)
Code:
06-19 16:49:14.512     0     0 F I[4:    ksoftirqd/4:   29] IPv6: ipv6_generate_eui64: dev type: 1
06-19 16:49:15.513 12742 12742 E AndroidRuntime: FATAL EXCEPTION: main
06-19 16:49:15.513 12742 12742 E AndroidRuntime: Process: com.google.android.apps.nexuslauncher, PID: 12742
06-19 16:49:15.513 12742 12742 E AndroidRuntime: java.lang.NoSuchMethodError: No interface method registerRemoteAnimationForNextActivityStart(Ljava/lang/String;Landroid/view/RemoteAnimationAdapter;)V in class Landroid/app/IActivityTaskManager; or its super classes (declaration of 'android.app.IActivityTaskManager' appears in /system/framework/framework.jar)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at com.android.launcher3.uioverrides.QuickstepInteractionHandler.onInteraction(SourceFile:12)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.appwidget.AppWidgetHostView.lambda$getHandler$1$AppWidgetHostView(AppWidgetHostView.java:882)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.appwidget.AppWidgetHostView$$ExternalSyntheticLambda2.onInteraction(Unknown Source:4)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.appwidget.AppWidgetHostView.lambda$getHandler$1$AppWidgetHostView(AppWidgetHostView.java:882)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.appwidget.AppWidgetHostView$$ExternalSyntheticLambda2.onInteraction(Unknown Source:4)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.widget.RemoteViews$RemoteResponse.handleViewInteraction(RemoteViews.java:6555)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.widget.RemoteViews$RemoteResponse.access$200(RemoteViews.java:6403)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.widget.RemoteViews$SetOnClickResponse.lambda$apply$0$RemoteViews$SetOnClickResponse(RemoteViews.java:1199)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.widget.RemoteViews$SetOnClickResponse$$ExternalSyntheticLambda0.onClick(Unknown Source:4)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.view.View.performClick(View.java:7455)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.view.View.performClickInternal(View.java:7432)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.view.View.access$3700(View.java:835)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.view.View$PerformClick.run(View.java:28810)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.os.Handler.handleCallback(Handler.java:938)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.os.Handler.dispatchMessage(Handler.java:99)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.os.Looper.loopOnce(Looper.java:201)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.os.Looper.loop(Looper.java:288)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at android.app.ActivityThread.main(ActivityThread.java:7870)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at java.lang.reflect.Method.invoke(Native Method)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
06-19 16:49:15.513 12742 12742 E AndroidRuntime:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)
06-19 16:49:15.521  3842  5699 W ActivityTaskManager:   Not force finishing home activity com.google.android.apps.nexuslauncher/.NexusLauncherActivity
06-19 16:49:15.521  3842  5699 W ActivityTaskManager:   Not force finishing home activity com.google.android.apps.nexuslauncher/.NexusLauncherActivity
06-19 16:49:15.525  3842  3869 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
06-19 16:49:15.525  3842  3869 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
06-19 16:49:15.561  3842  5597 W ProcessStats: Tracking association SourceState{ab237d7 system/1000 BTopFgs #25932} whose proc state 2 is better than process ProcessState{22f78c4 com.arn.scrobble:bgScrobbler/10182 pkg=com.arn.scrobble} proc state 3 (1 skipped)
06-19 16:49:15.590  3617  4309 E IPCThreadState: attemptIncStrongHandle(130): Not supported
06-19 16:49:15.594  4514  4514 W OverviewProxyService: Service disconnected
06-19 16:49:15.601  3842  5703 W InputManager-JNI: Input channel object 'recents_animation_input_consumer (client)' was disposed without first being removed with the input manager!
06-19 16:49:15.605  3842  4510 W InputManager-JNI: Input channel object 'c0fe005 com.google.android.apps.nexuslauncher/com.google.android.apps.nexuslauncher.NexusLauncherActivity (client)' was disposed without first being removed with the input manager!
06-19 16:49:15.410     0     0 W [3:[email protected]: 3639] healthd: battery l=80 v=4059 t=29.6 h=2 st=3 c=-154 chg=
06-19 16:49:15.620  3842  5718 W ActivityManager: Scheduling restart of crashed service com.google.android.apps.nexuslauncher/com.android.quickstep.TouchInteractionService in 1000ms for connection
06-19 16:49:15.622  3842  5718 W ActivityManager: Scheduling restart of crashed service com.google.android.apps.nexuslauncher/com.android.launcher3.notification.NotificationListener in 10998ms for connection

I would generally file this upstream but Lineage are extremely strict about this, at least they seem so on their bug report page.
 

aelfinn

Senior Member
Jun 3, 2012
633
175
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
If I should happen to have a spare S7 lying around, what country would I have to post it to? :)
 

Ivan_Meler

Forum Moderator / Recognized Developer
Staff member
If I should happen to have a spare S7 lying around, what country would I have to post it to? :)
Croatia, honestly biggest issue so far has been that most decent ebay listings are from UK and thanks to them leaving eu import tax would end up costing more than device. if that wasn't the case i wouldve gotten new display or s7 long time ago haha
 
  • Like
Reactions: ymz1376 and aelfinn

Kenajcrap

New member
Jun 30, 2022
2
1
Brazil
It seems like I'm still having keystore issues with my banking app even after the 2022.06.24 update.

here is the error stacktrace:
Code:
06-30 03:55:40.285  5916  6043 W System.err: com.ca.mas.foundation.MASException: Error generateKeyInAndroidKeyStore
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.foundation.notify.Callback.transform(Unknown Source:63)
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.foundation.notify.Callback.onError(Unknown Source:56)
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.foundation.MASUser$2.onError(Unknown Source:131)
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.core.MAGResultReceiver.onReceiveResult(Unknown Source:80)
06-30 03:55:40.285  5916  6043 W System.err:     at android.os.ResultReceiver.send(ResultReceiver.java:86)
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.respondError(Unknown Source:276)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.handleErrorResponse(Unknown Source:231)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.onProcessRequest(Unknown Source:221)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.onCredentialsObtained(Unknown Source:156)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.onHandleWork(Unknown Source:124)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService$ServiceHandler.handleMessage(Unknown Source:310)
06-30 03:55:40.286  5916  6043 W System.err:     at android.os.Handler.dispatchMessage(Handler.java:106)
06-30 03:55:40.286  5916  6043 W System.err:     at android.os.Looper.loopOnce(Looper.java:201)
06-30 03:55:40.286  5916  6043 W System.err:     at android.os.Looper.loop(Looper.java:288)
06-30 03:55:40.286  5916  6043 W System.err:     at android.os.HandlerThread.run(HandlerThread.java:67)
06-30 03:55:40.287  5916  6043 W System.err: Caused by: java.lang.RuntimeException: Error generateKeyInAndroidKeyStore
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.security.DefaultEncryptionProvider.encrypt(Unknown Source:60)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.storage.MASSecureSharedStorage.save(Unknown Source:38)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.datasource.MASSecureStorageDataSource.put(Unknown Source:72)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.store.ClientCredentialStorage.saveClientCredentials(Unknown Source:35)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.context.MssoContext.setClientCredentials(Unknown Source:572)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.policy.ClientCredentialAssertion.processRequest(Unknown Source:70)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.policy.PolicyManager.processRequest(Unknown Source:119)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.policy.PolicyManager.execute(Unknown Source:152)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.context.MssoContext.executeRequest(Unknown Source:408)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.onProcessRequest(Unknown Source:177)
06-30 03:55:40.287  5916  6043 W System.err:     ... 7 more
06-30 03:55:40.287  5916  6043 W System.err: Caused by: java.lang.RuntimeException: Error generateKeyInAndroidKeyStore
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.util.KeyUtilsSymmetric.generateKeyInAndroidKeyStoreAndroidN(Unknown Source:283)
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.util.KeyUtilsSymmetric.generateKey(Unknown Source:155)
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.security.KeyStoreKeyStorageProvider.getKey(Unknown Source:86)
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.security.DefaultEncryptionProvider.encrypt(Unknown Source:56)
06-30 03:55:40.288  5916  6043 W System.err:     ... 16 more
06-30 03:55:40.288  5916  6043 W System.err: Caused by: java.security.ProviderException: Keystore key generation failed
06-30 03:55:40.288  5916  6043 W System.err:     at android.security.keystore2.AndroidKeyStoreKeyGeneratorSpi.engineGenerateKey(AndroidKeyStoreKeyGeneratorSpi.java:413)
06-30 03:55:40.288  5916  6043 W System.err:     at javax.crypto.KeyGenerator.generateKey(KeyGenerator.java:612)
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.util.KeyUtilsSymmetric.generateKeyInAndroidKeyStoreAndroidN(Unknown Source:278)
06-30 03:55:40.288  5916  6043 W System.err:     ... 19 more
06-30 03:55:40.289  5916  6043 W System.err: Caused by: android.security.KeyStoreException: Unsupported block mode
06-30 03:55:40.289  5916  6043 W System.err:     at android.security.KeyStore2.getKeyStoreException(KeyStore2.java:356)
06-30 03:55:40.289  5916  6043 W System.err:     at android.security.KeyStoreSecurityLevel.handleExceptions(KeyStoreSecurityLevel.java:57)
06-30 03:55:40.289  5916  6043 W System.err:     at android.security.KeyStoreSecurityLevel.generateKey(KeyStoreSecurityLevel.java:145)
06-30 03:55:40.289  5916  6043 W System.err:     at android.security.keystore2.AndroidKeyStoreKeyGeneratorSpi.engineGenerateKey(AndroidKeyStoreKeyGeneratorSpi.java:400)
06-30 03:55:40.289  5916  6043 W System.err:     ... 21 more
06-30 03:55:40.293  5916  6043 W System.err: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
06-30 03:55:40.293  5916  6043 W System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(Unknown Source:226)
06-30 03:55:40.294  5916  6043 W System.err:     at com.google.gson.Gson.fromJson(Unknown Source:932)
06-30 03:55:40.294  5916  6043 W System.err:     at com.newrelic.agent.android.instrumentation.GsonInstrumentation.fromJson(Unknown Source:126)
06-30 03:55:40.294  5916  6043 W System.err:     at com.google.gson.Gson.fromJson(Unknown Source:897)
06-30 03:55:40.294  5916  6043 W System.err:     at com.newrelic.agent.android.instrumentation.GsonInstrumentation.fromJson(Unknown Source:117)
06-30 03:55:40.294  5916  6043 W System.err:     at com.google.gson.Gson.fromJson(Unknown Source:846)
06-30 03:55:40.294  5916  6043 W System.err:     at com.newrelic.agent.android.instrumentation.GsonInstrumentation.fromJson(Unknown Source:99)
06-30 03:55:40.294  5916  6043 W System.err:     at o.jIb.d(Unknown Source:446)
06-30 03:55:40.294  5916  6043 W System.err:     at o.jIb.e(Unknown Source:143)
06-30 03:55:40.294  5916  6043 W System.err:     at o.jKO.b(Unknown Source:35)
06-30 03:55:40.294  5916  6043 W System.err:     at o.jKO$e.invokeSuspend(Unknown Source:15)
06-30 03:55:40.294  5916  6043 W System.err:     at o.lOr.resumeWith(Unknown Source:33)
06-30 03:55:40.294  5916  6043 W System.err:     at kotlinx.coroutines.UndispatchedCoroutine.afterResume(Unknown Source:142)
06-30 03:55:40.294  5916  6043 W System.err:     at kotlinx.coroutines.AbstractCoroutine.resumeWith(Unknown Source:102)
06-30 03:55:40.295  5916  6043 W System.err:     at o.lOr.resumeWith(Unknown Source:46)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.DispatchedTask.run(Unknown Source:104)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(Unknown Source:571)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(Unknown Source:750)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(Unknown Source:678)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(Unknown Source:665)
06-30 03:55:40.295  5916  6043 W System.err: Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
06-30 03:55:40.295  5916  6043 W System.err:     at com.google.gson.stream.JsonReader.beginObject(Unknown Source:386)
06-30 03:55:40.295  5916  6043 W System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(Unknown Source:215)
06-30 03:55:40.295  5916  6043 W System.err:     ... 19 more


After clearing storage + cache, and then reinstalling the app, here is the full `adb logcat --pid [app's pid]`:

dmesg:

My apologies for the external links. Neither of the texts were small enough to post directly

please, let me know how may I provide "proc/kmsg" and "data/tombstones" as I'm not sure how to do it, and also any other needed information.

Thank you for your work!

Edit:
Update: I had done an upgrade from LineageOS 18.1 from Ivan_Meler, so I tried doing an install from scratch and experienced the same problem.
More information on steps to reproduce:
- Download banking app
- Select "I'm already a client"
- Input a valid identification number
- Input any password (it can be a correct or incorrect password)
- The error happens after pressing "Enter"
 
Last edited:

Mft73

New member
Jul 1, 2022
1
0
Hi guys. After installing the latest version of the ROM, after entering the pubg new state game, I constantly receive server errors. This is if this error never appears in the original version of Samsung ROM. Can anyone help me ?!
 

meesam3379

Senior Member
Feb 2, 2022
79
17
Samsung Galaxy S7
Oppo A37
This rom works great.

However the material you theming is not working on Google apps after updating.
The colours go to default Blue instead of getting the colours from the wallpaper. The apps had colours based on the wallpaper before updating.
Non Google apps like YASNAC still have the colour from the wallpaper so it's only for Google apps.

I flashed NikGApps
 
Jan 6, 2021
39
11
Since a few days, my phone freezes occasionally when I use it. One time it froze when I was charging it and got very hot.

There doesnt seem to be a pattern...but it happens at least once a day so maybe there is something wrong and I could give you some logs or something?
 

Nightsax

Member
Sep 17, 2015
23
17
Hello, sorry for my noobness, but i can't even flash the TWRP (twrp-3.6.2_9-0-herolte.img) using ODIN (3.14.4, and some olders versions too), it fails.
I've installed latest Samsung drivers (1.7.50, also tried 1.59), turned on OEM and usb debugging, my phone shows up in ODIN (light blue "COMx" showing), I select AP and TWRP tar file, and then...FAIL.
I am stuck using the stock Android 8.0 rom, and no root on my phone, so can't use another method I guess :(
Any help appreciated.
Edit: I have a SM-G930U model, and i think that's is the problem. Nevermind, I will try to find a solution myself.
 
Last edited:

yseraa

New member
Apr 19, 2010
1
0
Since the problem is still present for some people, maybe would be relevant to share more details, such as,

  1. Model number of your device,
  2. Which country you're currently in,
  3. Carrier,
  4. Network (3g, 4g)
  5. What type of communication was used (normal call, call using an app eg: whatsapp, signal, video calls).

If there is any assumption that different hardwares could be inducing it, at leats this would be useful data.
For people that had their problem solved with this update, sharing the data would be useful to others trying to discern successful cases.
I have an SM-G930, a problem with echo on all firmware (Lineages 19.1, Lineages 18.1, Lineages 17.1) - the interlocutor hears himself. There is also another problem - I can't be heard well, as if I'm talking to a sick tooth.
As a result, I installed Floyd_V7.0, there are no problems described above on it.
 

master373

Senior Member
Feb 1, 2022
109
34
Hello there...don't take this the wrong way..but is there hope for Android 13 on s7?👉👈

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.
 

bixaon

Member
Feb 19, 2022
30
20
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
Hi!

After last build update (06.24) my banking and some other apps (keepass) that used FP (fingerprint) login earlier have lost ability to use such way to login now.

If I try to enable FP in apps, after short period of time they get broken again.

But for unlocking Android and some other apps FP works as expected.

Seems like some things was not fixed but broken (
 

Kenajcrap

New member
Jun 30, 2022
2
1
Brazil
It seems like I'm still having keystore issues with my banking app even after the 2022.06.24 update.

here is the error stacktrace:
Code:
06-30 03:55:40.285  5916  6043 W System.err: com.ca.mas.foundation.MASException: Error generateKeyInAndroidKeyStore
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.foundation.notify.Callback.transform(Unknown Source:63)
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.foundation.notify.Callback.onError(Unknown Source:56)
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.foundation.MASUser$2.onError(Unknown Source:131)
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.core.MAGResultReceiver.onReceiveResult(Unknown Source:80)
06-30 03:55:40.285  5916  6043 W System.err:     at android.os.ResultReceiver.send(ResultReceiver.java:86)
06-30 03:55:40.285  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.respondError(Unknown Source:276)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.handleErrorResponse(Unknown Source:231)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.onProcessRequest(Unknown Source:221)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.onCredentialsObtained(Unknown Source:156)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.onHandleWork(Unknown Source:124)
06-30 03:55:40.286  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService$ServiceHandler.handleMessage(Unknown Source:310)
06-30 03:55:40.286  5916  6043 W System.err:     at android.os.Handler.dispatchMessage(Handler.java:106)
06-30 03:55:40.286  5916  6043 W System.err:     at android.os.Looper.loopOnce(Looper.java:201)
06-30 03:55:40.286  5916  6043 W System.err:     at android.os.Looper.loop(Looper.java:288)
06-30 03:55:40.286  5916  6043 W System.err:     at android.os.HandlerThread.run(HandlerThread.java:67)
06-30 03:55:40.287  5916  6043 W System.err: Caused by: java.lang.RuntimeException: Error generateKeyInAndroidKeyStore
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.security.DefaultEncryptionProvider.encrypt(Unknown Source:60)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.storage.MASSecureSharedStorage.save(Unknown Source:38)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.datasource.MASSecureStorageDataSource.put(Unknown Source:72)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.store.ClientCredentialStorage.saveClientCredentials(Unknown Source:35)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.context.MssoContext.setClientCredentials(Unknown Source:572)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.policy.ClientCredentialAssertion.processRequest(Unknown Source:70)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.policy.PolicyManager.processRequest(Unknown Source:119)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.policy.PolicyManager.execute(Unknown Source:152)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.context.MssoContext.executeRequest(Unknown Source:408)
06-30 03:55:40.287  5916  6043 W System.err:     at com.ca.mas.core.service.MssoService.onProcessRequest(Unknown Source:177)
06-30 03:55:40.287  5916  6043 W System.err:     ... 7 more
06-30 03:55:40.287  5916  6043 W System.err: Caused by: java.lang.RuntimeException: Error generateKeyInAndroidKeyStore
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.util.KeyUtilsSymmetric.generateKeyInAndroidKeyStoreAndroidN(Unknown Source:283)
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.util.KeyUtilsSymmetric.generateKey(Unknown Source:155)
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.security.KeyStoreKeyStorageProvider.getKey(Unknown Source:86)
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.security.DefaultEncryptionProvider.encrypt(Unknown Source:56)
06-30 03:55:40.288  5916  6043 W System.err:     ... 16 more
06-30 03:55:40.288  5916  6043 W System.err: Caused by: java.security.ProviderException: Keystore key generation failed
06-30 03:55:40.288  5916  6043 W System.err:     at android.security.keystore2.AndroidKeyStoreKeyGeneratorSpi.engineGenerateKey(AndroidKeyStoreKeyGeneratorSpi.java:413)
06-30 03:55:40.288  5916  6043 W System.err:     at javax.crypto.KeyGenerator.generateKey(KeyGenerator.java:612)
06-30 03:55:40.288  5916  6043 W System.err:     at com.ca.mas.core.util.KeyUtilsSymmetric.generateKeyInAndroidKeyStoreAndroidN(Unknown Source:278)
06-30 03:55:40.288  5916  6043 W System.err:     ... 19 more
06-30 03:55:40.289  5916  6043 W System.err: Caused by: android.security.KeyStoreException: Unsupported block mode
06-30 03:55:40.289  5916  6043 W System.err:     at android.security.KeyStore2.getKeyStoreException(KeyStore2.java:356)
06-30 03:55:40.289  5916  6043 W System.err:     at android.security.KeyStoreSecurityLevel.handleExceptions(KeyStoreSecurityLevel.java:57)
06-30 03:55:40.289  5916  6043 W System.err:     at android.security.KeyStoreSecurityLevel.generateKey(KeyStoreSecurityLevel.java:145)
06-30 03:55:40.289  5916  6043 W System.err:     at android.security.keystore2.AndroidKeyStoreKeyGeneratorSpi.engineGenerateKey(AndroidKeyStoreKeyGeneratorSpi.java:400)
06-30 03:55:40.289  5916  6043 W System.err:     ... 21 more
06-30 03:55:40.293  5916  6043 W System.err: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
06-30 03:55:40.293  5916  6043 W System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(Unknown Source:226)
06-30 03:55:40.294  5916  6043 W System.err:     at com.google.gson.Gson.fromJson(Unknown Source:932)
06-30 03:55:40.294  5916  6043 W System.err:     at com.newrelic.agent.android.instrumentation.GsonInstrumentation.fromJson(Unknown Source:126)
06-30 03:55:40.294  5916  6043 W System.err:     at com.google.gson.Gson.fromJson(Unknown Source:897)
06-30 03:55:40.294  5916  6043 W System.err:     at com.newrelic.agent.android.instrumentation.GsonInstrumentation.fromJson(Unknown Source:117)
06-30 03:55:40.294  5916  6043 W System.err:     at com.google.gson.Gson.fromJson(Unknown Source:846)
06-30 03:55:40.294  5916  6043 W System.err:     at com.newrelic.agent.android.instrumentation.GsonInstrumentation.fromJson(Unknown Source:99)
06-30 03:55:40.294  5916  6043 W System.err:     at o.jIb.d(Unknown Source:446)
06-30 03:55:40.294  5916  6043 W System.err:     at o.jIb.e(Unknown Source:143)
06-30 03:55:40.294  5916  6043 W System.err:     at o.jKO.b(Unknown Source:35)
06-30 03:55:40.294  5916  6043 W System.err:     at o.jKO$e.invokeSuspend(Unknown Source:15)
06-30 03:55:40.294  5916  6043 W System.err:     at o.lOr.resumeWith(Unknown Source:33)
06-30 03:55:40.294  5916  6043 W System.err:     at kotlinx.coroutines.UndispatchedCoroutine.afterResume(Unknown Source:142)
06-30 03:55:40.294  5916  6043 W System.err:     at kotlinx.coroutines.AbstractCoroutine.resumeWith(Unknown Source:102)
06-30 03:55:40.295  5916  6043 W System.err:     at o.lOr.resumeWith(Unknown Source:46)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.DispatchedTask.run(Unknown Source:104)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(Unknown Source:571)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(Unknown Source:750)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(Unknown Source:678)
06-30 03:55:40.295  5916  6043 W System.err:     at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(Unknown Source:665)
06-30 03:55:40.295  5916  6043 W System.err: Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 1 path $
06-30 03:55:40.295  5916  6043 W System.err:     at com.google.gson.stream.JsonReader.beginObject(Unknown Source:386)
06-30 03:55:40.295  5916  6043 W System.err:     at com.google.gson.internal.bind.ReflectiveTypeAdapterFactory$Adapter.read(Unknown Source:215)
06-30 03:55:40.295  5916  6043 W System.err:     ... 19 more


After clearing storage + cache, and then reinstalling the app, here is the full `adb logcat --pid [app's pid]`:

dmesg:

My apologies for the external links. Neither of the texts were small enough to post directly

please, let me know how may I provide "proc/kmsg" and "data/tombstones" as I'm not sure how to do it, and also any other needed information.

Thank you for your work!
Update: I had done an upgrade from LineageOS 18.1 from Ivan_Meler, so I tried doing an install from scratch and experienced the same problem.
More information on steps to reproduce:
- Download banking app
- Select "I'm already a client"
- Input a valid identification number
- Input any password (correct or incorrect)
- The error happens after pressing "Enter"
 
  • Like
Reactions: pcenachi

Ivan_Meler

Forum Moderator / Recognized Developer
Staff member
New build is up, here is a brief changelog
- Merged July 2022. Security update
- Fixed more keystore issues
- Synced with LineageOS source

Also some important news, Exodusnick decided to provide huge help and he bought and shipped s7 to me which should be here next week, so all of exciting updates i talked about last week should be way easier to achieve and this will make testing and developement a lot easier, Once again huge thanks to him.

Also big thanks to donators that helped to cover build server cost and got me coffee which helped to keep this project up and running.

Thanks to this s7 should live for few more android releases without any major issues. and Android 12 will get even better with new hals that are curently in developement

There will be updates to 18.1 and 17.1 in a few days once july security updates have been ported to them

Enjoy new build and stay safe
 

master373

Senior Member
Feb 1, 2022
109
34
New build is up, here is a brief changelog
- Merged July 2022. Security update
- Fixed more keystore issues
- Synced with LineageOS source

Also some important news, Exodusnick decided to provide huge help and he bought and shipped s7 to me which should be here next week, so all of exciting updates i talked about last week should be way easier to achieve and this will make testing and developement a lot easier, Once again huge thanks to him.

Also big thanks to donators that helped to cover build server cost and got me coffee which helped to keep this project up and running.

Thanks to this s7 should live for few more android releases without any major issues. and Android 12 will get even better with new hals that are curently in developement

There will be updates to 18.1 and 17.1 in a few days once july security updates have been ported to them

Enjoy new build and stay safe
Thank you so much, cant wait the future updates.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 21
    here it is August security update
    Nothing major in this one as i am still working behind the scenes on that huge update i talked about previously which involves rewrite of almost whole graphics and media stack (its almost finished but i still have to do a bit more testing just to make sure there is no regression)

    In other news android 13 should be released next month and since there were no major changes s7 should be running it soon after release with not too many issues and ill try to take a few days off from work to get it up and running on it once source is out

    Once again huge thanks to everyone who supported this project, helped cover build server cost and got me coffee with donations.
    This project wouldnt be alive without them as i do this in my free time as a hobby.

    Enjoy new builds and stay safe
    16
    Another quick progress update since im back from my trip
    One of bigger issues with new rebased hwc source has been fixed (I fixed it and tested fix 2 days ago actually but didnt post anything about it) and rest of the issues have been logged

    This just leaves 2 issues related to scudo in new OMX stack and 2 or 3 edge cases in hwc stack
    after that new and improved source will be ready and it should bring quite a bit of improvements to s7 on aosp

    Big thanks to everyone who is helping to cover the build server cost and coffee spent on this project.
    4
    I think wireless charging not work. Is it only me or anybody has same issue with wireless charging like me?
    works fine for me, used it just the other day
    2
    The only annoying point for me is the call echo problem : the interlocutor hears himself.

    I have also noticed that the loudspeaker is very low when used in phone calls but powerful when viewing a video.

    Hello,

    I have done some tests about this problem and it seems it is a software problem because it does not occurs in Samsung ROM.

    Samsung ROM (Android 8)LOS 17.1 (20220708)LOS 18.1 (20220708)LOS 19.1 (20220624)
    Interlocutor echo problemNoLow (only if interlocutor speaks heavy, he hears himself)Strong (each word is heard as a echo)Strong (each word is heard as a echo)
    Loudspeaker volumeCorrect (4/5)Inaudible volume (0/5)Low (2/5)Low (2/5)

    I also tried to put the mixer_paths_0.xml from LOS 17.1 to the 19.1 ROM, but it changes nothing : echo is still strong in 19.1 with 17.1 mixer_paths_0.xml.

    I have also made a copy of all files from Samsung stock ROM /system partition if it can be helpful.

    Does someone have an idea about how we can try to correct this sound problem ? I'm still available to do some tests but not for so long because it is not my phone and the owner will soon use it as its main phone.
    2
    Hello, install this rom a few months ago without problems after having version 18.1 and for a few weeks I have a problem in any of the 2 versions that is not solved by cleaning and reinstalling, the phone turns off without prior notice of low battery when android marks me 40%, 20% ..., I had to plug in the charger 2 times in a day only with an hour of screen use. The phone will be 6 years old and never change the battery. Any recommendations for this problem?
    Hot Tip: Change the battery.
    Had similar experience when battery in my phone died.
  • 64
    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: 3da780126393650fcdecac8c183cc801


    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

    07.08.2022.
    - Merged August 2022. Security update
    - Synced with LineageOS source

    07.07.2022.
    - Merged July 2022. Security update
    - Fixed more keystore issues
    - Synced with LineageOS source

    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
    22
    New build is up, here is a brief changelog
    - Merged July 2022. Security update
    - Fixed more keystore issues
    - Synced with LineageOS source

    Also some important news, Exodusnick decided to provide huge help and he bought and shipped s7 to me which should be here next week, so all of exciting updates i talked about last week should be way easier to achieve and this will make testing and developement a lot easier, Once again huge thanks to him.

    Also big thanks to donators that helped to cover build server cost and got me coffee which helped to keep this project up and running.

    Thanks to this s7 should live for few more android releases without any major issues. and Android 12 will get even better with new hals that are curently in developement

    There will be updates to 18.1 and 17.1 in a few days once july security updates have been ported to them

    Enjoy new build and stay safe
    22
    Here are some great news for future o this project and s7 on newer android versions in general
    Huge thanks for device donation goes to Exodusnick, I recieved device today so ill be able to properly test stuff with fully working s7 instead of my old broken one which had to be used with scrcpy.

    I already started work on porting some new hals and resolving some issues that were harder to debug before.
    New hals should speed up the device quite a bit without compromissing battery life (might even improve it a bit).

    Also big thanks to everyone who supported this project with donations and helped cover the build server cost and got me coffee in the past, this project wouldnt be possible without them.

    More exciting updates coming soon.
    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