Their answers are usually not very informative, at least I don’t remember having seen a detailed and meaningful one. Mostly slogans, like ‘for legal reasons’. Nevermind, they won’t switch to LOS base, anyway.
1 Like
Oh man, that works! I just scanned a QR code with my bank app and was able to pay.
(I knew of course about native QR readers and I realize I wasn’t very clear in my previous post but I specifically meant the above.)
So how did you figure this out? I tried getting the camera working in AAS as well but didn’t manage it.
I did check the settings, but there’s nothing there. Let me add a screenshot later.
I wonder if it’s DNS.
2 Likes
journalctl also lists errors from AAS and libhybris, so I saw that it can’t find the device.Then looked around on internet for possible ICameraProvider devices and found some in a random place. One of them worked.
want to report a successful flashing of sailfishos-Xperia-5-IV-XQCQ54-5.0.0.71-testing-2.zip on 5mk4 (2sim/256gb XQ-CQ72).
as in LOS only 1 sim-slot is detected.
3 Likes
Guess I didn’t come across that random place in my searches 
1 Like
On the 10 III and 10 V it discovers and shows the SIM card and mobile network name there. Then you can enter deeper screens and see even more. So judging by your screenshots where the entire “SIM card” and “Calls & SMS” items are greyed out, it looks that it’s not just mobile data that AAS doesn’t see, but it doesn’t discover the SIM card in general, or maybe even the modem. It looks that it is a problem with seeing by AAS anything mobile network related in general, not just internet but also calls, etc.
The first two screenshots are from 10 III where that settings menu on Android 11 looks slightly different, the third one is from 10 V (Calls & SMS, SIMs menus like on yours, sorry for Polish language, somehow I couldn’t switch it to English). In both cases all mobile network and SIM card details are recognized and fully shown.
So it makes me wonder if the situation isn’t similar like with @bundyo’s camera fix, where maybe e.g. some very trivial thing, like e.g. a different name of the modem or some modified intent name prevents AAS from seeing it.
There are some kernel switches about networking that are missing in 1 IV’s kernel config (according to the AAS helper). See here which ones:
There might be a missing device too, I guess.
1 Like
Thank you @bundyo, I will try to figure out something out of this…
1 Like
BTW. I’ve just learned that unlocking the bootloader permanently wipes DRM keys from TA partition, which causes that advanced camera functions (does anyone know which ones exactly?) irreversibly vanish, even if one goes back to stock Sony Android and relocks the bootloader… Which maybe isn’t a huge problem on e.g. 10 III and its mediocre camera, but certainly is a huge loss in case of 1/5 IV’s really advanced cameras… Is there any solution?
sometimes I feel good
$ cat dmesg_los.txt |rg -i radio
...
[ 33.899836] servicemanager: Found vendor.qti.hardware.radio.qtiradio.IQtiRadioStable/slot1 in device VINTF manifest.
[ 33.900604] servicemanager: Found vendor.qti.hardware.radio.qtiradio.IQtiRadioStable/slot1 in device VINTF manifest.
that was strange, so I $ cat /vendor/etc/vintf/manifest.xml where I see some discrepancies between radio/sim-slots count
I took this as an example for Dual-Sim version:
https://github.com/LineageOS/android_device_sony_sm8350-common/blob/lineage-23.0/manifest_ds.xml
$ diff -u vendor_orig/etc/vintf/manifest.xml vendor_new/etc/vintf/manifest.xml
--- vendor_orig/etc/vintf/manifest.xml 2026-01-28 16:26:02.459794401 +0000
+++ vendor_new/etc/vintf/manifest.xml 2026-01-28 16:17:41.751860042 +0000
@@ -49,7 +49,9 @@
<name>android.hardware.radio</name>
<transport>hwbinder</transport>
<fqname>@1.2::ISap/slot1</fqname>
+ <fqname>@1.2::ISap/slot2</fqname>
<fqname>@1.6::IRadio/slot1</fqname>
+ <fqname>@1.6::IRadio/slot2</fqname>
</hal>
<hal format="hidl">
<name>android.hardware.radio.config</name>
@@ -61,7 +63,6 @@
<transport>hwbinder</transport>
<fqname>@1.2::ISecureElement/SIM1</fqname>
<fqname>@1.2::ISecureElement/SIM2</fqname>
- <fqname>@1.2::ISecureElement/eSE1</fqname>
</hal>
<hal format="aidl">
<name>android.hardware.security.keymint</name>
@@ -182,11 +183,13 @@
<name>vendor.qti.hardware.data.connection</name>
<transport>hwbinder</transport>
<fqname>@1.1::IDataConnection/slot1</fqname>
+ <fqname>@1.1::IDataConnection/slot2</fqname>
</hal>
<hal format="hidl">
<name>vendor.qti.hardware.data.iwlan</name>
<transport>hwbinder</transport>
<fqname>@1.1::IIWlan/slot1</fqname>
+ <fqname>@1.1::IIWlan/slot2</fqname>
</hal>
<hal format="hidl">
<name>vendor.qti.hardware.data.latency</name>
@@ -288,16 +291,19 @@
<name>vendor.qti.hardware.radio.uim</name>
<transport>hwbinder</transport>
<fqname>@1.2::IUim/Uim0</fqname>
+ <fqname>@1.2::IUim/Uim1</fqname>
</hal>
<hal format="hidl">
<name>vendor.qti.hardware.radio.uim_remote_client</name>
<transport>hwbinder</transport>
<fqname>@1.0::IUimRemoteServiceClient/uimRemoteClient0</fqname>
+ <fqname>@1.0::IUimRemoteServiceClient/uimRemoteClient1</fqname>
</hal>
<hal format="hidl">
<name>vendor.qti.hardware.radio.uim_remote_server</name>
<transport>hwbinder</transport>
<fqname>@1.0::IUimRemoteServiceServer/uimRemoteServer0</fqname>
+ <fqname>@1.0::IUimRemoteServiceServer/uimRemoteServer1</fqname>
</hal>
<hal format="hidl">
<name>vendor.qti.hardware.secureprocessor.device</name>
Unpacked vendor.img, patched, repacked it back with afsr, flashed only vendor partition and we’re good to go.
@rinigus could you please add this to your images?
also where should I look now in SFOS? vendor partition is the same, but still only 1 sim is detected in UI.
5 Likes
oh boy
# cat > /etc/ofono/binder.d/dual-sim.conf
[Settings]
ExpectSlots+=slot2
[slot2]
path = /ril_1
slot = 1
[s]we gotta do something about 3-seconds delay when pressing power button. cause double-tap doesn’t work all the time.
Also seems like usb connection is charging-only. [/s] found this issue on github
created 60-doubletap.conf (I thought it was in updates?), seems to be working ok
5 Likes
Congratulations, amazing work @remote! Now, if someone could help resolve the issue with AAS not seeing mobile data, it would become my best Sailfish OS phone ever (and forever)… 
3 Likes
that could be a difference between 2 physical sim and version with esim + physical sim. Would have to think how to approach it. In principle, we have also overlay that can be used to adjust any android file before android boots. that way we can make a package that is for your variant and replaces corresponding files.
and adds dual sim config as you have in SFOS… not sure what will be needed for esim in this case.
yes, should be there. part of droid config, version 0.2.0: droid-config-sony-nagara/sparse/etc/mce at main · sailfishos-sony-nagara/droid-config-sony-nagara · GitHub
As long as we’re nitpicking: the wifi ip address isn’t listed in developer tools when enabling remote login.
Strange, today it works.
1 Like
When the fixes are available, suggest them via PRs. Repos are there…
it’s not in droid-config-xqcq54 (1+main.20250917191946.d5a07f8-1.59.9.bso).
seems like only on 1mk4
[root@Xperia5IV defaultuser]# free -h
total used free shared buff/cache available
Mem: 16.6G 3.4G 11.2G 25.7M 2.0G 14.0G
Swap: 2.2G 0 2.2G
is that ok?
strange. try to update zypper ref && zypper up. something is off, as devel and testing both have newer config, as far as I can see at OBS. If it will not help, paste ssu lr
Enabled repositories (global):
- adaptation-common ... https://releases.jolla.com/releases/5.0.0.71/jolla-hw/adaptation-common/aarch64/
- adaptation-community ... https://repo.sailfishos.org/obs/nemo:/devel:/hw:/sony:/nagara/sailfish_latest_aarch64/
- adaptation-community-common ... https://repo.sailfishos.org/obs/nemo:/devel:/hw:/common/sailfish_latest_aarch64/
- apps ... https://releases.jolla.com/jolla-apps/5.0.0.71/aarch64/
- hotfixes ... https://releases.jolla.com/releases/5.0.0.71/hotfixes/aarch64/
- jolla ... https://releases.jolla.com/releases/5.0.0.71/jolla/aarch64/
Enabled repositories (user):
- harbour-storeman-obs ... https://repo.sailfishos.org/obs/home:/olf:/harbour-storeman/5.0_aarch64/
- openrepos-CoanTeen ... https://sailfish.openrepos.net/CoanTeen/personal/main
- openrepos-Juanro49 ... https://sailfish.openrepos.net/Juanro49/personal/main
- openrepos-ade ... https://sailfish.openrepos.net/ade/personal/main
- openrepos-anarchy_in_the_uk ... https://sailfish.openrepos.net/anarchy_in_the_uk/personal/main
- openrepos-basil ... https://sailfish.openrepos.net/basil/personal/main
- openrepos-crun ... https://sailfish.openrepos.net/crun/personal/main
- openrepos-ichthyosaurus ... https://sailfish.openrepos.net/ichthyosaurus/personal/main
- openrepos-olf ... https://sailfish.openrepos.net/olf/personal/main
- openrepos-vasvlad ... https://sailfish.openrepos.net/vasvlad/personal/main
- sailfishos-chum ... https://repo.sailfishos.org/obs/sailfishos:/chum/5.0_aarch64/
- store ... https://store-repository.jolla.com/xqcq54/aarch64/?version=5.0.0.71
I had the same thing. Reading through the thread again now I see all kinds of comments by @bundyo that I apparently missed and I made the same comments later in the thread 
2 Likes