[ROM]LineageOS 19.0(W/ signature spoofing) /Android 12 + Material You for S10E/S10/S10+/S10 5G Exynos

[Cosbot_]

Installed yesterday, now I'm using as daily driver, everything works fine. Passed safety net with magisk no probs.

I got used tho to the one UI festure to swipe down the fingerprint sensor to open the notification panel. Tried three apps from playstore and didn't work.
Another thing I realized that lineage os is limited in options to change the Bixby button, I can't find a way to use it for torch.

These problems aren't specific for this ROM as they occur on any aosp so thank you Ivan for this great ROM.

 

[ne_Zaebavaj]

I'm having problems registering with Viber, do any of you experience this problem as well? (I'm on s10e)

 

[DusanDobranic]

I'm having problems registering with Viber, do any of you experience this problem as well? (I'm on s10e)

No problems with my device with viber from the first release to the last

 

[Ryptox]

Installed yesterday, now I'm using as daily driver, everything works fine. Passed safety net with magisk no probs.

I got used tho to the one UI festure to swipe down the fingerprint sensor to open the notification panel. Tried three apps from playstore and didn't work.
Another thing I realized that lineage os is limited in options to change the Bixby button, I can't find a way to use it for torch.

These problems aren't specific for this ROM as they occur on any aosp so thank you Ivan for this great ROM.

Try an app called 'buttons remapper - mapping and combination'
I use that to remap Bixby to the camera app, there's an option for flashlight I've just tested and that works fine!

 

[Cosbot_]

Try an app called 'buttons remapper - mapping and combination'
I use that to remap Bixby to the camera app, there's an option for flashlight I've just tested and that works fine!

Thank you, it worked, now to figure out how to do the fingerprint swipe.

 

[^^rac]

Thank you, it worked, now to figure out how to do the fingerprint swipe.

That is one of the greatest features i miss from AOSP Roms... that finger print sensor swipe (Notifications)... tried numerous apps. Could not replicate it

 

[CitaroSR]

Try an app called 'buttons remapper - mapping and combination'
I use that to remap Bixby to the camera app, there's an option for flashlight I've just tested and that works fine!

thank you, this works so well

 

[kubis111]

hi, thanks for the nice rom. I have a question. It's possible to run the settings text-to-speech (google)? I can't open it in settings. Some app don't work. Maybe it's just my fault. THX

 

[mecaskey]

hi, thanks for the nice rom. I have a question. It's possible to run the settings text-to-speech (google)? I can't open it in settings. Some app don't work. Maybe it's just my fault. THX

I got it to work by downloading it, trying to set it default then un installing, reinstalling and bingo. No "hello Google" yet however. But now works w/Mi Band etc. Good luck.

 

[Virnik0]

Flashed yesterday. Dirty flash didn't went as expected, clean one faced struggle (outdated BL/CM), but after sorting those, the ROM runs perfectly. I have noticed few glitches:
a) 'Recent' view sometimes freezes for more than 10s, user is unable to do anything
b) Nav Bar configuration mostly do not work. Enabling button reverse mode do nothing.
c) This is probably something we can't change, but the way random wireless MAC works is weird. For one, there is never actual physical MAC, it is always virtual - but could be stuck to given wireless network (similarly it worked in LOS18). We can either enforce full randomization, or each network could have statically assigned MAC. Works well, just took time to understand/adjust to this ;-) But then you reboot, and MAC will change even for saved networks :-(
d) AA is broken (BitGapps, will test with NikGapps) in both wired and wireless mode. To me, it looks like gapps problem
e) Google Assistant do not work correctly (never did since LOS18). Could be triggered manually, but there is no animation. Voice activation doesn't work (again, this is with BitGapps, will retest with NikGapps soon).
f) BT audio seems to be working fine (tested with R-Link Audio system and with Niceboy plugs) for both phonecalls and music.
g) external app is required, as custom button mapping doesn't work yet
i) Phone setup wizzard usually crashes during wireless setup (initial, after wipe). - fixed by rebooting without setting anything, and then re-trying.

I am not complaining. I am actually pretty impressed. Despite these issues, I prefer to stay on LOS19, as LOS18 with PixelProps was causing endless 'update' downloads pushed by GMS, depleting carrier FUP (maybe my misconfiguration, but it was happening on three more phones I had no control over).

 

[Virnik0]

Flashed yesterday. Dirty flash didn't went as expected, clean one faced struggle (outdated BL/CM), but after sorting those, the ROM runs perfectly. I have noticed few glitches:
a) 'Recent' view sometimes freezes for more than 10s, user is unable to do anything
b) Nav Bar configuration mostly do not work. Enabling button reverse mode do nothing.
c) This is probably something we can't change, but the way random wireless MAC works is weird. For one, there is never actual physical MAC, it is always virtual - but could be stuck to given wireless network (similarly it worked in LOS18). We can either enforce full randomization, or each network could have statically assigned MAC. Works well, just took time to understand/adjust to this ;-)
d) AA is broken (BitGapps, will test with NikGapps) in both wired and wireless mode. To me, it looks like gapps problem
e) Google Assistant do not work correctly (never did since LOS18). Could be triggered manually, but there is no animation. Voice activation doesn't work (again, this is with BitGapps, will retest with NikGapps soon).
f) BT audio seems to be working fine (tested with R-Link Audio system and with Niceboy plugs) for both phonecalls and music.
g) external app is required, as custom button mapping doesn't work yet
i) Phone setup wizzard usually crashes during wireless setup (initial, after wipe). - fixed by rebooting without setting anything, and then re-trying.

I am not complaining. I am actually pretty impressed. Despite these issues, I prefer to stay on LOS19, as LOS18 with PixelProps was causing endless 'update' downloads pushed by GMS, depleting carrier FUP (maybe my misconfiguration, but it was happening on three more phones I had no control over).

Update: With NikGapps, symptoms are almost identical. Just Android System Intelligence force-closes any time notification is received. Solved by removing pixel3 build of the apk, and replaced it with 'oem' build of the same version. Works fine since. AA does work, just remove any PlayStore installed version, and then flash NikGapps AA addon. It has unresolved access rights in terms of call logs and SMS, should be fixed in next update (AA Update just came out, fixed - perms could be given just fine). Works in both wired and wireless mode. Assistant works better with NikGapps, it has gui/animations. Voice activation doesn't work (expected). With NikGapps, Setup Wizzard doesn't crash during phone initiatialization. NikGapps package Basic or bigger removes Trebuchet, which causes Recent view to stop working. In my case, I just copied Trebuchet install from priv-apps backup I made earlier back to filesystem, works fine after reboot.

 

[Fusseldieb]

Just installed this ROM.

Awesome work, OP!!

One thing tho: My 128GB SD Card says it needs formatting, however it was working just fine with stock and is also filled with stuff, not a optimal solution. Would love to see a fix for this

EDIT: Also, after doing all hard work geting the damn SafetyNet to pass and my banking app to open, it crashes as soon as it wants to take a picture of me to confirm my identity. Unfortunately, I'll need to switch to another ROM in the meanwhile, as this is kinda crucial. (Logcat of the moment of the crash is attached)

 

[Virnik0]

Just installed this ROM.

Awesome work, OP!!

One thing tho: My 128GB SD Card says it needs formatting, however it was working just fine with stock and is also filled with stuff, not a optimal solution. Would love to see a fix for this

EDIT: Also, after doing all hard work geting the damn SafetyNet to pass and my banking app to open, it crashes as soon as it wants to take a picture of me to confirm my identity. Unfortunately, I'll need to switch to another ROM in the meanwhile, as this is kinda crucial. (Logcat of the moment of the crash is attached)

Well, Masking your rom status takes literaly two few steps:
a) Flash Magisk apk/zip from TWRP
b) In Magisk Manager, install Props Config
c) In 'props', edit Fingerprint (1), select certified fingerprint (f), Google ->Pixel 5 (A12).
d) confirm/reboot
e) Back in Magisk, enable Magisk Hide (add banking/payment apps to the list), disable Play Protect temporarily and Hide Magisk Manager.
f) wipe Google App data, PlayStore Services data
g) reboot

As for your SD Card, what was the filesystem you used on it? I am using vfat, and the card worked fine in LOS17, LOS18 and LOS19 just the same.

 

[ilviandante]

Hi! I d like to use this rom but I don t want lose camera quality..I have tested zgcam,gcam 8.1 but front camera look so bad respect samsung camera.. there is a solution like new camera libs for this rom?

 

[DusanDobranic]

Hi! I d like to use this rom but I don t want lose camera quality..I have tested zgcam,gcam 8.1 but front camera look so bad respect samsung camera.. there is a solution like new camera libs for this rom?

Man i am jus amazed with gcam 8.1 i dont see the need for samsung camera, personaly i would try to install gcam on oficial rom aswell.

 

[Asapakyou01]

Man i am jus amazed with gcam 8.1 i dont see the need for samsung camera, personaly i would try to install gcam on oficial rom aswell.

Bro where to download gcam 8.1 for exynos

 

[ilviandante]

Man i am jus amazed with gcam 8.1 i dont see the need for samsung camera, personaly i would try to install gcam on oficial rom aswell.

I have yet installed 8.1 on official rom, rear camera is fine but the quality of front camera is very low compared to samsung camera app

 

[Fusseldieb]

Well, Masking your rom status takes literaly two few steps:
a) Flash Magisk apk/zip from TWRP
b) In Magisk Manager, install Props Config
c) In 'props', edit Fingerprint (1), select certified fingerprint (f), Google ->Pixel 5 (A12).
d) confirm/reboot
e) Back in Magisk, enable Magisk Hide (add banking/payment apps to the list), disable Play Protect temporarily and Hide Magisk Manager.
f) wipe Google App data, PlayStore Services data
g) reboot

As for your SD Card, what was the filesystem you used on it? I am using vfat, and the card worked fine in LOS17, LOS18 and LOS19 just the same.

Hi Virnik0, thanks for the quote!

SafetyNet did pass, that wasn't the problem. The banking app crashes the moment it wants to take a picture and a I can clearly see it inside logcat. It looks like some UI things are being enforced in A12 which weren't on older versions (the banking app is creating multiple views when it opens the camera and A12 doesn't seem to like that). I researched that error quite a bit.

I don't know if there's a fix for that. Maybe recompiling the banking app to an older target version of android MIGHT work, but I think I'll just stick with A11 for the time being.

As per logcat:

E WindowManager: android.view.WindowLeaked: Activity br.com.neon.features.login.ui.activities.LoginPasswordActivity has leaked window DecorView@e98da91[LoginPasswordActivity] that was originally added here

EDIT: Also, I just did what another user did recently and was caught offguard. Adjusting screen edges in the developer option does freeze and then BOOTLOOP your device. After some boot attempts, Lineage Recovery greets me with the message: "Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory reset and erase all user data stored on this device."
Well, now it's toast anyways. Time to go back

 

[Virnik0]

Hi Virnik0, thanks for the quote!

SafetyNet did pass, that wasn't the problem. The banking app crashes the moment it wants to take a picture and a I can clearly see it inside logcat. It looks like some UI things are being enforced in A12 which weren't on older versions (the banking app is creating multiple views when it opens the camera and A12 doesn't seem to like that). I researched that error quite a bit.

I don't know if there's a fix for that. Maybe recompiling the banking app to an older target version of android MIGHT work, but I think I'll just stick with A11 for the time being.

What Camera app you use and what Gapps package you used? I tested the same thing with AirBank and Commerz Bank here in CZ. I tried to use a camera to read EAN and QR codes (loading up payment slip, authorizing logon to a service....) using their android apps and it works. But yes, if the banking app uses some 'neat' feature A12 prohibits, it is well possible. I already noticed multiple apps which doesn't work correctly on A12 (ot just AOSP, I let my father with Stock, unrooted S21 Ultra to try them too with the same results), so it is not surprising.

What exactly is it complaining about in the catlog?

 

[Fusseldieb]

What Camera app you use and what Gapps package you used? I tested the same thing with AirBank and Commerz Bank here in CZ. I tried to use a camera to read EAN and QR codes (loading up payment slip, authorizing logon to a service....) using their android apps and it works. But yes, if the banking app uses some 'neat' feature A12 prohibits, it is well possible. I already noticed multiple apps which doesn't work correctly on A12 (ot just AOSP, I let my father with Stock, unrooted S21 Ultra to try them too with the same results), so it is not surprising.

What exactly is it complaining about in the catlog?

I edited my post, should be clearer now.

I did use BitGapps.

The camera per se opens without problem and displays my mediocre face on the verify cutout, but after some seconds it crashes. Sometime it goes as far as telling me to "blink" and then crashes.

Will try with AOSP A11, but if that also doesn't work, I'll install it on rooted stock, backup it there after verifying and then restore on AOSP again. If that ALSO doesn't work, I guess I'll just change banks
I'm so fed up with lagging stock that I'm ready to give up the Samsung camera AND my bank. That's quite something.