I didn’t try it before, so I don’t know if it would work from the start.
Didn’t tinker with anything, just installed packages from 10mk3.
PS I’m not sure there are any new connectivity related options in a new kernel by @vlagged. I’ve checked /proc/config.gz for those kernel options mentioned in a thread and they’re still not there.
Ok, I’ve found why there was no sound.
$ pactl list sink-inputs
Sink Input #861
...
Mute: yes
...
Properties:
media.icon_name = "mpv"
media.name = "123.mp4 - mpv"
application.name = "mpv"
native-protocol.peer = "UNIX socket client"
native-protocol.version = "34"
policy.application.id = "37c5220"
application.process.id = "32"
application.process.user = "defaultuser"
application.process.host = "Xperia5IV"
application.process.binary = "harbour-mpvqml"
application.language = "ru_RU.utf8"
application.process.machine_id = "Xperia5IV"
application.icon_name = "harbour-mpvqml"
application.process.arg0 = ""
policy.group = "othermedia"
policy.stream_flags = hex:00000000
media.role = "x-maemo"
module-stream-restore.id = "sink-input-by-media-role:x-maemo"
$ pactl set-sink-input-mute 861 false
Hmm. After rebooting, sound works.
And I have sound in the SFOS camera preview, too. But its loudness is very low, especially sound recorded by the lower microphone is very silent
This I have, too.
Hmmm, not sure why mpv was muted on your device, it wasn’t on mine….
As for the video playback in e.g. SFOS Camera preview, did you have to disable the avc codec in /etc/gst-droid/gstdroidcodec.conf in order to get smooth video playback, or was it working OK?
Hmmm, so it’s really interesting what made it work. Maybe the needed changes were actually in the new LOS21 base for the 5 IV? @vlagged, could you please shed some light on what actually could have made AAS mobile data work (so wonderfully well) on @remote’s 5 IV in your recent updates? 
I just did and now it’s smooth and it also plays it and video files in Gallery, though not everything.
PS I guess low microphone volume when taking videos is the only semi-blocker I have before I move from 10mk3.
It’s not a secret:
As with config tweaks, might not all be used, but definitely some are since the modules rebuilt and changed version.
Oh, so it takes updating the LOS base for the 1 IV to make it work…. Well, sadly too big of a task for me, so it looks that sometime in May is the soonest we can see it on the 1 IV 
@vlagged I’ve flash the last LOS build (20260307) and my xperia 5IV didn’t start. I see the LOS boot animation and after some time phone reboots. But if I flash SFOS on it - SFOS is able to boot and works. Have you tried to boot last LOS build on xperia 5IV?
I guess that for LOS to correctly boot up you need to wipe / format the data partition in LOS recovery. At least that’s what worked for me. Sadly, it’ll wipe your SFOS data, too.
Thats probably it, can you confirm @tohaturok ?
No, it isn’t.
I faced this problem first time when I had issue in SFOS with airplane mode (I couldn’t turn off it) and decided to try run LOS and check if LOS has the same issue. I’ve flashed LOS boot and vendor_boot partitions and after that wiped/formatted data partition in LOS recovery.
After that I decided to flash LOS from scratch and went through all steps in LOS installing instruction from rinigus’ SFOS Nagara repository, but used the last LOS build (20260307). Unfortunately, got the same result as in the first try - bootloop on LOS loading indicator.
But it interesting when I flash SFOS on top of this LOS - SFOS boots and works.
P.S. Didn’t check the airplane mode issue in the new installation 
I will try to replicate this sometime.
Oh, that is a known issue. There is a workaround documented here.
If this is just the kernel, shouldn’t it be changed after updating to latest?
Or maybe the updates to 1 IV (since we are on that with wetab73) don’t include those changes in the kernel?
Only 5 IV got the kernel rebuilt. The 1 IV kernel will be rebuilt when rinigus May have the time;)
Well, the CPU is the same and the folder name mentions it, so I assumed it might be the same for the two devices. Though the rest of the hardware is not really the same. 
They share the same source, but I don’t think they’re the same binary kernel. There are two configs set differently and then the kernel image packaging which also adds cmdline parameters - which are concatenated with bootloader ones, which also differ - so better wait for the tested build.
Thanks for reporting this - I have published an updated lineage build. You might get away with only flashing product.img (an updated Euicc app from google caused this, weirdly). Backing out that apk update is the only change I’ve done, and would explain the fact that it did not impact Sailfish. Let me know how this goes.
I bought my 3rd X 5 IV today. This time, if the seller sent me a true screenshot, it should work…
Motivation : still 100%.
(I hope it will last at least a decade!)
I resorted to a local used devices bazaar, turned out to have less not very honest sellers.
Hi.
The LED missed call notification only works for an odd missed call, it does not work for an even missed call.
Setings:
Sounds and feedback
Vibration Only when sounds on
Ringtone for incoming calls Only contacts
When a call comes from an unknown number, the vibration works. But in this case, vibration should not work.
Looks like yet another come back of very old SFOS bug
I haven’t checked but I bet that also in this case it’s a general SFOS bug, not Nagara port specific. If so, it should be reported to Jolla using a general bug report form….