[ROM][EXYNOS] LineageOS 18.1 for S10e|S10|S10+ - v2.2 (UPDATE: 2021-07-23)

[ioeg41]

Since 18.1 hasn't been "officially" released yet it wouldn't suprise me if one runs into build errors.

Did you manage to get the magiskinit64 file? Since v22 they merged Magisk and the Magisk Manager App, so there is no more downloadable Magisk.zip which contains the arm/magiskinit64 file. Seems like one also has to build Magisk on it's own.

I read that 18.1 official builds are being generated here (and I hope it isn't an April Fools joke), so I thought the lineage-18.1 branch is ready for builds. It's unclear which branch is being used and I am not familiar with official build process/ pipelines to know.

I did build Magisk from source, however the default built process is generating magiskinit for armeabi-v7a which is 32-bit.
Upon further internet search, I came across this, and to quote:



I double checked with v1.4 source by downloading the init file Modpunk used from here and ran:
saitejal@MacBook-Pro ~ % file Downloads/init Downloads/init: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), statically linked, BuildID[sha1]=1e6afa77c4724a091cd787585cba739f04bbaaa3, stripped
I am yet to build a bootimage and test it out but I am attaching the Magisk v22.1 init file zipped.

I'll upload a boot.img which is pre-patched for Magisk 20.4. You can flash this via twrp and Magisk should work, just need to install the Magisk Manager.

edit: Here it is https://www.androidfilehost.com/?fid=4349826312261761185 Unzip the file. If you wish, you can verify it using gpg, then flash the boot.img via TWRP.

Who can provide the beyond0lte-boot-magisk20.4 (LineageOS 18.1) file?
Perhaps Downgrade patch.
Rescue LineageOS 18.1

 

[phaze3131]

can twrp backups be done to backup everything included data?

I'm on lineage 17.1 and twrp backups CAN NOT be done because you just get twrp backup failed "required key not available"

thanks for any help

 

[Sheffield Steve]

I couldn't get the data partition to backup in TWRP with the latest version. All other partitions do backup OK.

From what I can tell it's a TWRP issue.

 

[bym22028]

My Wifi hotspot disables immediately after enabling it. "error"
In 17.1 it worked but in 18.1 not anymore. I did a complete fresh install.

Does anybody know how I can fix that?

I use latest 2021-06-23 | 2.1
with Magisk

 

[kugel.]

I can confirm that wifi hotspot does not work.

 

[The A.I. Project]

Guys I am having some issues setting up the fingerprint. When I tap on "fingerprint" in the security menue the screen turns black and after some time I get an "app not responding" message. The top slider still responds and the "back" button is still shown. But only thing I can do to get rid of the black screen is kill the app. Note that this is not the bug mentioned in the known bugs for the fingerprint sensor (since that assumes one can even start the setup)...

I had a similar reaction during initial setup when trying to setup the google account and services. From online search there it looked like an issue from OpenGapps deleting WebView... I was able to circumvent (not fix) that part by completely deleting the setup wizard directory and just going with the basic LOS setup

The logcat does not really speak to me regarding what is going on.

I'm using the S10
I did a format + wipe + clean flash of
LOS 18.1, 2021-06-23 version
OpenGapps pico 2021-07-17
Firmware XXSBFUE6 as suggested

I ran Ivan's ROM a few days back (yes, I did a complete format after that), and with it the fingerprint sensor worked fine. At that point I think I had an even more recent firmware version though (I had updated to the most recent released with Samsung stock OTA), i.e. XXSBFUE6 was probably a downgrade.

Anybody else experiencing the "frozen black screen" issue, or anything else specific to fingerprint sensor setup?

Thanks in advance!

Edit: here is a bit of logcat that keeps repeating more or less the same, that looks suspicious:

07-20 11:37:24.770  5509  5509 E bauth_FPQCBAuthSensorControl: BAuthDeviceCtrl sys call failed rv : -1
07-20 11:37:24.770  5509  5509 I bauth_FPQCBAuthSensorControl: dscc 0
07-20 11:37:24.770  5509  5509 E bauth_FPBAuthService: Sensor Device SpiCtrl on Fail
07-20 11:37:24.770  5509  5509 E bauth_FPBAuthService: Sensor Device Control Fail
07-20 11:37:24.771  5509  5509 I bauth_FPQCBAuthSensorControl: FPQCBAuthSensorControl, 205
07-20 11:37:24.771  5509  5509 I bauth_FPQCBAuthSensorControl: already closed
07-20 11:37:24.771  5509  5509 I bauth_FPBAuthService: ncmi : , ncpf : 1
07-20 11:37:24.771  5509  5509 I TLC_BAUTH: Call FP cmd 0xc (43)
07-20 11:37:24.771  5509  5509 I TLC_BAUTH: status : 0, cmd : 0x0x4 rsp : 0x0x177008
07-20 11:37:24.771  5509  5509 E TLC_BAUTH: TZ Session is not opened properly - Ignore
07-20 11:37:24.771  5509  5509 I bauth_FPBAuthService: check_opcode status = 5, opcode = 43, func_ret_val = 67, function_status = 0, timeout = 0
07-20 11:37:24.771  5509  5509 I bauth_FPBAuthService: FPBAuthService, 11586
07-20 11:37:24.771  5509  5509 I bauth_FPBAuthService: FPBAuthService, 11590
07-20 11:37:24.771  5509  5509 I bauth_FPQCBAuthSensorControl: FPQCBAuthSensorControl, 568
07-20 11:37:24.771  5509  5509 I qfp-vendorlib:  failed to open /dev/qbt2000_fd
07-20 11:37:24.771  5509  5509 I bauth_FPBAuthService: done

The "failed to open part" looks like the issue

EDIIT: if this helps at all to break it down. The fingerprint sensor works fine with v1.4 (i.e. LOS 17.1) and with the current firmware it also works with Ivan's ROM. I also flashed the stock firmware in between, to make sure that any remainders of the "multi disabler" are gone. So it really seems to be specific to v 2 (I tried all 3 of them so far).

Any clues or help are warmly appreciated

 

[modpunk]

New version is out.

 

[penguyman]

Just to understad. I rebooted in TWRP buy seems cannot decrypt my storage (pin and fingerprint removed), what could it be?

Update: tried to reflash twrp + vbmeta but same, Lineage works smoothly but cannot decrypt storage from twrp

Update 2: Did the update without decrypt and it works.

 

[rahman0924]

hey guys, i tried to install this rom following the instructions carefully, but when i install it with gapps, the rom wont boot, its just stuck on the lineage boot screen, but when i try to install the rom without gapps, the rom boots perfectly

 

[penguyman]

AudioFX after last upgrade crashes. Someone can confirm?

Update: found that crashes only during a call

 

[John5788]

I am noticing hotspot is not working with the 2.1 release. I have not updated to 2.2 yet since changelog does not mention anything about hotspot fix.

Here is relevant logcat outputs from trying to activate hotspot

08-01 10:44:04.925  5621 13435 I WifiService: startTetheredHotspot uid=1073
08-01 10:44:04.926  5621  5758 D WifiActiveModeWarden: Starting SoftApModeManager config = null
08-01 10:44:04.959  5340  5340 E libc    : Access denied finding property "ro.vendor.wifi.sap.interface"
08-01 10:44:04.959  5340  5340 E android.hardware.wifi@1.0-service: Failed to add interface: wlan1 NOT_SUPPORTED
08-01 10:44:04.953  5340  5340 W wifi@1.0-servic: type=1400 audit(0.0:896): avc: denied { read } for name="u:object_r:vendor_wifi_prop:s0" dev="tmpfs" ino=15055 scontext=u:r:hal_wifi_default:s0 tcontext=u:object_r:vendor_wifi_prop:s0 tclass=file permissive=0
08-01 10:44:04.953  5340  5340 W wifi@1.0-servic: type=1300 audit(0.0:896): arch=c00000b7 syscall=56 success=no exit=-13 a0=ffffff9c a1=7fe336c068 a2=88000 a3=0 items=0 ppid=1 auid=4294967295 uid=1010 gid=1010 euid=1010 suid=1010 fsuid=1010 egid=1010 sgid=1010 fsgid=1010 tty=(none) ses=4294967295 exe="/vendor/bin/hw/android.hardware.wifi@1.0-service" subj=u:r:hal_wifi_default:s0 key=(null)
08-01 10:44:04.953  4981  4981 W auditd  : type=1327 audit(0.0:896): proctitle="/vendor/bin/hw/android.hardware.wifi@1.0-service"
08-01 10:44:04.953  4981  4981 W auditd  : type=1320 audit(0.0:896): 
08-01 10:44:04.957  5340  5340 W wifi@1.0-servic: type=1400 audit(0.0:897): avc: denied { sys_module } for capability=16 scontext=u:r:hal_wifi_default:s0 tcontext=u:r:hal_wifi_default:s0 tclass=capability permissive=0
08-01 10:44:04.960  5621  5758 E HalDevMgr: executeChipReconfiguration: failed to create interface ifaceType=1: 4 ()
08-01 10:44:04.961  5621  5758 E WifiVendorHal: Failed to create AP iface
08-01 10:44:04.961  5621  5758 E WifiNative: Failed to create AP iface in vendor HAL
08-01 10:44:04.961  5621  5758 E SoftApManager: setup failure when creating ap interface.
08-01 10:44:04.963  5621  5663 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.net.wifi.WIFI_AP_STATE_CHANGED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
08-01 10:44:04.964  5621  5758 D WifiController: AP disabled, remain in EnabledState.

 

[heni63]

Should I install The Official Or this one? And what are the benefits of a Ramdisk? I don't game, of it's for loading speeds

 

[rahman0924]

installing opengapps or nikgapps, crashes the initial setup wizard. but if i dont install any gapps, the rom boots and finishes the initial setup wizard. any fixes guys? TIA

 

[schlombie]

I just tried flashing LOS 18.1 over 17.1 again (w/o wiping data, but w/ wiping cache&dalvik). I understood that this is a supported ugrade method?

The system server seems to crash, and then it goes into a bootloop. I attach an logcat output but I think here's the relevant backtrace:

07-11 23:06:05.616 15455 15455 E System  : ******************************************
07-11 23:06:05.617 15455 15455 E System  : ************ Failure starting system services
07-11 23:06:05.617 15455 15455 E System  :
07-11 23:06:05.618 15455 15455 I DropBoxManagerService: add tag=system_server_crash isTagEnabled=true flags=0x2

To know how you create your bootlog would be interesting!

 

[JWildfireT]

Hi!

If you are using 18.1 since February I assume you use a build that was made by Ivan Meler. Meler's and modpunk's build are not compatible. Meler diables encryption as far as I know and does a few other things different too.

So your best bet is to do a fresh install with a full wipe before. Also, I do recommend to check out the build from Linux4. It's with working encryption, the sources are available, SELinux is enforcing and updates do come regularly. With modpunk there is some uncertainty for updates. If you follow the thread you will know what I mean.

Sorry for the delay in responding, life stuff happening.

Just wanted to say a big thank you for the above info. I switched over to the Linux4 build early July and it's been smooth sailing since.

 

[msna]

Hotspot is not working, neither in version 2.1 nor in 2.2.
Does anyone know how to get it working?
Or can others confirm that it is working for them?

 

[bym22028]

Hotspot is not working, neither in version 2.1 nor in 2.2.
Does anyone know how to get it working?
Or can others confirm that it is working for them?

I can only confirm that is does not work. A lof of guys can confirm it too.

 

[bym22028]

Does anybody know whether hotspot is working on the "official" ROM from linux4 (quite new out there)?

https://xdaforums.com/t/rom-official-lineageos-18-1-for-galaxy-s10e-s10-s10-s10-5g-exynos.4315407/

 

[kugel.]

To know how you create your bootlog would be interesting!

Well simply run adb logcat asap.

 

[ilviandante]

hi! I have found another Los18 for another phone that had miracast with Samsung smartview.. there is a way to have it on this rom for s10e??