[ROM][S9/S9+][LineageOS 17.1][UNOFFICIAL][09/01/2020]

[tomcatxx]

deleted

 

[Speedmatze]

Yes .... since the version EdXposed works smoothly. Xposed has not existed since Q. Now calls itself EdXposed. RiruCore 19.7, RiruEdXposed 0.4.6.1.
However, it can happen that after the flash from EdXposed you get stuck in download mode. That's how it happened to me. Then something has to be changed in the EdXposed file via TWRP. Only then did the phone start the regular system start.

Thanks for the hint! I was waiting for Xposed to be working before switching to LOS17.
Can you tell me what needs to be changed in the EdXposed file or where to find an instruction for that?

 

[mvn23]

So I see there's a new release as of yesterday, but no release notes... Anything special to take care of with the update? What's the permissive-boot.img for?

 

[Deleted member 5115178]

So I see there's a new release as of yesterday, but no release notes... Anything special to take care of with the update? What's the permissive-boot.img for?

See github for the relevant changes. All releases have a SELinux enforcing kernel, if you for whatever reason need a permissive kernel you can flash the permissive-boot.img.

 

[Fadzz]

Issues I've had so far (bear in mind many of these are probably not the fault of the developer). Otherwise, everything runs smoothly, battery lasts longer, no performance issues:

1) During device setup, it forces you to activate Google Assistant by asking you to say "ok Google", but when you do that, nothing happens, it doesn't respond to it and just keeps waiting (only way around this is to finish phone setup without connecting to internet)

2) There is no clipboard (except through a 3rd party keyboard)

3) WiFi stopped working randomly, but disconnecting then reconnecting fixes this

4) Battery percentage (or any battery icon modifications) are not working

5) Magisk did not pass safety net, but there's a module to fix this

6) File transfer via USB is working, though transfers were notably slower than on stock firmware

7) Probably mentioned before, but phone identity to my wifi network changes upon every restart, requiring me to login again

SCREENSHOTS

 

[testerS4]

Thanks for the hint! I was waiting for Xposed to be working before switching to LOS17.
Can you tell me what needs to be changed in the EdXposed file or where to find an instruction for that?

Install RiruCore 19.7 via Magisk, install Riru EdXposed 0.4.6.1. Then see if Phone starts until registration. If it only starts up to download mode, then rename or delete the file post-fs-data.sh via TWRP data / adb / modules / riru_edxposed / ... That has helped me. good luck

 

[Fadzz]

Issues I've had so far (bear in mind many of these are probably not the fault of the developer). Otherwise, everything runs smoothly, battery lasts longer, no performance issues:

1) During device setup, it forces you to activate Google Assistant by asking you to say "ok Google", but when you do that, nothing happens, it doesn't respond to it and just keeps waiting (only way around this is to finish phone setup without connecting to internet)

2) There is no clipboard (except through a 3rd party keyboard)

3) WiFi stopped working randomly, but disconnecting then reconnecting fixes this

4) Battery percentage (or any battery icon modifications) are not working

5) Magisk did not pass safety net, but there's a module to fix this

6) File transfer via USB is working, though transfers were notably slower than on stock firmware

7) Probably mentioned before, but phone identity to my wifi network changes upon every restart, requiring me to login again

SCREENSHOTS

8) Echo during phone calls can be heard by the person I'm talking to

9) "This OS is incompatible with this game" error (screenshot below; only seen this on Pokémon Go so far). Magisk hide doesn't resolve this

 

[Deleted member 5115178]

Issues I've had so far (bear in mind many of these are probably not the fault of the developer). Otherwise, everything runs smoothly, battery lasts longer, no performance issues:

1) During device setup, it forces you to activate Google Assistant by asking you to say "ok Google", but when you do that, nothing happens, it doesn't respond to it and just keeps waiting (only way around this is to finish phone setup without connecting to internet)

2) There is no clipboard (except through a 3rd party keyboard)

3) WiFi stopped working randomly, but disconnecting then reconnecting fixes this

4) Battery percentage (or any battery icon modifications) are not working

5) Magisk did not pass safety net, but there's a module to fix this

6) File transfer via USB is working, though transfers were notably slower than on stock firmware

7) Probably mentioned before, but phone identity to my wifi network changes upon every restart, requiring me to login again

Don't use Google Assistant, so can't help you with 1. I don't experience 2-4 & 6 and 5 is known. 7 can be fixed by using your phone's own MAC-address.

 

[Apunkt]

confirm, works like a charm!

Thanks!

Hi, i just installed the 21-03-20 image (on DTB4 BL and vendor) and everything is working fine except for the bluetooth calls on my Bose QC35 II. Music and car bluetooth calls are working
I experienced the same issues in LOS 16. Any idea how to fix this ?

Thank you
Apunkt

 

[dedq]

Can I flash permissive boot. img on 14/3 build?

 

[Speedmatze]

Install RiruCore 19.7 via Magisk, install Riru EdXposed 0.4.6.1. Then see if Phone starts until registration. If it only starts up to download mode, then rename or delete the file post-fs-data.sh via TWRP data / adb / modules / riru_edxposed / ... That has helped me. good luck

Works like a charm. Thanks!

 

[dedq]

Yes .... since the version EdXposed works smoothly. Xposed has not existed since Q. Now calls itself EdXposed. RiruCore 19.7, RiruEdXposed 0.4.6.1.
However, it can happen that after the flash from EdXposed you get stuck in download mode. That's how it happened to me. Then something has to be changed in the EdXposed file via TWRP. Only then did the phone start the regular system start.
_____________________________________________________________________________________
20.3. 18:10 GMT+1
And today an update! Thanks to the developers for the time you invest.
I can report the following after this update:
I installed the LOS March 20, 2020 dirty. The first thing I did was look at Magisk. Everything was green there. Nevertheless, my EdXposed was faulty. So I flashed the associated BootImage file. Then Magisk was faulty again as at yesterday on March 19, 2020. So Magisk 20.3 flashed again and then everything fit again. Magisk current, EdXposed active. So everything does not fit without BootImages, but also not with BootImages. Something is always shot down. But once I have noticed the procedure, I can live with it.
Wifi, mobile internet, GPS ... ok
The SystemCam and the gallery can only be used together, on internal storage. Faulty on SD card. (alternative: OpenCamera and Simple Galerie)
The separate setting of start and lock screen does not work.
The start screen is always the lock screen.
(sorry for Engl ... I use translators)
SM-G960F

I managed to get it working with Riru Core 19.7 and YAHFA which I flashed normally in TWRP.
No Download mode by the way at all!

Thanks.

 

[testerS4]

I managed to get it working with Riru Core 19.7 and YAHFA which I flashed normally in TWRP.
No Download mode by the way at all!

Thanks.

After I flashed the update from March 19th, 2020 with the corresponding image, my Magisk was broken and at the same time EdXposed. Had to flash Magisk manually via TWRP. And the same problem with March 20, 2020. The image in the update probably always shoots the Magisk.

 

[dedq]

After I flashed the update from March 19th, 2020 with the corresponding image, my Magisk was broken and at the same time EdXposed. Had to flash Magisk manually via TWRP. And the same problem with March 20, 2020. The image in the update probably always shoots the Magisk.

It does screw up the Magisk image actually and you have to reflash it later.
The same happened to me.

 

[testerS4]

I wonder if I always have to flash the associated image in the update folder? KB moderate there are slight differences for each image.

 

[CM@S5]

Here my issues

I'm sorry, but i switched back to version 9 after testing:

Same issues on dirty flash and after factory reset
1) using it during driving and with BT mobile network is switching on and off
2) phone almost not understandable, tried incoming and outgoing calls

After dirty flash:
3) it is not possible to set finger print any more or lock/unlock the phone, locking has to be switched off. For new user added it works - factory reset is necessary

stay healthy

 

[jorgespv]

I just dirty flashed 20200324 Without recovering data
I have an SM-G650F with TWRP 3.3.1-0
I have just rebooted to recovery, data backup, installed ROM and rebooted to system. No bootloop
Then I have rebooted to install WhiteWolf kernel and Magisk and had no problem. Thank you very much for the amazing ROM!

 

[testerS4]

After dirty flash:
3) it is not possible to set finger print any more or lock/unlock the phone, locking has to be switched off. For new user added it works - factory reset is necessary

stay healthy

I don't even want to try what you describe. Already possible that the finger sensor gets mixed up with a dirty flash. Then maybe deactivate before flashing security.
(sorry for Engl ... I use translators)

 

[Pierfranc]

Is the camera good? Is it supporting slow motion 960 Fps and other Samsung features?

 

[beugologist]

Having some issues with BT calls using true wireless earbuds (WF 1000 XM3's).
>Tried forcing SBC codec, doesn't seem to do anything.
>Toggling off AAC in bluetooth settings does nothing, either.
>On rob's latest 24/03/2020 build.

Anybody had luck with this? Cheers