Is Wifi on or off when you are sending SMS?
I tried both. But why you ask this?
1 Like
Yesterday I could not send SMS. I turned off Wifi and SMS was sent. Is there any connection with these two, I don’t know, but it happened.
This didn’t work on my phone
10 III here, noticed today first time after update SMS couldn’t been sent. VoLTE is disabled, 4G preferred (O2 Germany)
When choosing “2G only” the SMS is sent immediately. So my workaround: switching to 2G for sending SMS.
Receiving SMS is working flawlessly.
Uh, wait - not flawlessly, because the receipt isn’t sent, so the provider sends the message twice. I got most of the SMS twice because of this, but this is only in secondary Sailfish’s fault.
From Ofono-Log:
2025-02-14 19:43:19.795 src/sms.c: tx_next() tx_next: 0x1c516240
2025-02-14 19:43:19.796 src/binder_sms.c: binder_sms_send() pdu_len: 19, tpdu_len: 18 flags: 0x00
2025-02-14 19:43:19.796 imsradio0 < 43 sendImsSms
2025-02-14 19:43:19.796 0000: 76 65 6e 64 6f 72 2e 71 74 69 2e 68 61 72 64 77 vendor.q ti.hardw
2025-02-14 19:43:19.796 0010: 61 72 65 2e 72 61 64 69 6f 2e 69 6d 73 40 31 2e are.radi o.ims@1.
2025-02-14 19:43:19.796 0020: 32 3a 3a 49 49 6d 73 52 61 64 69 6f 00 00 00 00 2::IImsR adio....
2025-02-14 19:43:19.796 0030: 3d 00 00 00 85 2a 74 70 00 00 00 00 d0 de 51 1c =....*tp ......Q.
2025-02-14 19:43:19.796 0040: 00 00 00 00 40 00 00 00 00 00 00 00 00 00 00 00 ....@... ........
2025-02-14 19:43:19.796 0050: 00 00 00 00 00 00 00 00 00 00 00 00 85 2a 74 70 ........ .....*tp
2025-02-14 19:43:19.796 0060: 01 00 00 00 90 fa 11 ca 71 00 00 00 06 00 00 00 ........ q.......
2025-02-14 19:43:19.796 0070: 00 00 00 00 00 00 00 00 00 00 00 00 08 00 00 00 ........ ........
2025-02-14 19:43:19.796 0080: 00 00 00 00 85 2a 74 70 01 00 00 00 08 f9 11 ca .....*tp ........
2025-02-14 19:43:19.796 0090: 71 00 00 00 01 00 00 00 00 00 00 00 00 00 00 00 q....... ........
2025-02-14 19:43:19.796 00A0: 00 00 00 00 18 00 00 00 00 00 00 00 85 2a 74 70 ........ .....*tp
2025-02-14 19:43:19.796 00B0: 01 00 00 00 30 30 00 ac 71 00 00 00 12 00 00 00 ....00.. q.......
2025-02-14 19:43:19.796 00C0: 00 00 00 00 00 00 00 00 00 00 00 00 30 00 00 00 ........ ....0...
2025-02-14 19:43:19.796 00D0: 00 00 00 00 ....
2025-02-14 19:43:19.800 imsradio0 > 37 sendImsSmsResponse
2025-02-14 19:43:19.800 0000: 76 65 6e 64 6f 72 2e 71 74 69 2e 68 61 72 64 77 vendor.q ti.hardw
2025-02-14 19:43:19.800 0010: 61 72 65 2e 72 61 64 69 6f 2e 69 6d 73 40 31 2e are.radi o.ims@1.
2025-02-14 19:43:19.800 0020: 32 3a 3a 49 49 6d 73 52 61 64 69 6f 52 65 73 70 2::IImsR adioResp
2025-02-14 19:43:19.800 0030: 6f 6e 73 65 00 00 00 00 3d 00 00 00 ff ff ff ff onse.... =.......
2025-02-14 19:43:19.800 0040: 03 00 00 00 01 00 00 00 ........
2025-02-14 19:43:19.800 src/vendor_qti_ims_radio.c: vendor_qti_ims_radio_send_ims_sms_response() [imsradio0] msgref:4294967295 result:3 reason:1
2025-02-14 19:43:19.801 src/sms.c: tx_finished() tx_finished 0x1c516240
2025-02-14 19:43:19.801 src/sms.c: tx_finished() Sending failed, retry in 15 secs
From ConnectionManager.GetContexts.ril_0:
struct {
object path "/ril_0/context3"
array [
dict entry(
string "Name"
variant string "IMS"
)
dict entry(
string "Active"
variant boolean false
)
dict entry(
string "Type"
variant string "ims"
)
dict entry(
string "Protocol"
variant string "dual"
)
dict entry(
string "AccessPointName"
variant string "ims"
)
dict entry(
string "Username"
variant string ""
)
dict entry(
string "Password"
variant string ""
)
dict entry(
string "AuthenticationMethod"
variant string "none"
)
dict entry(
string "Settings"
variant array [
]
)
dict entry(
string "IPv6.Settings"
variant array [
]
)
]
}
]
1 Like
2G connection didn’t help. For me it looks like my phone doesn’t even try to send. It just tells immediately (I translate from Finnish): An issue when sending a text message. Recently I also downloaded and tried to use this Ofono but it wrote nothing (maybe I can’t use this).
Similar is mentioned in this thread.
What is this “Ims”-thing? It failed with “ims” but there’s no “ims” when it’s working.
Ah, got it: IP Multimedia Subsystem - Wikipedia
Hm, according to this sourcefile the system should try GSM if IMS fails.
And this looks like there’s a reason the old workaround didn’t work anymore, I guess. But this is way beyond my knowledge…
Been in that kind of situation before, the solution was to
- stop ofono (
devel-su systemctl stop ofono) - delete everything in
/var/lib/ofono/<sim_id>/sms_assembly. (i think it’s the sim id, not completely sure). - start ofono (
devel-su systemctl start ofono)
This did the trick for me. You should also check if there’s something in the tx_queue folder, but those were usually causing ofono to crash (fixed).
2 Likes
I couldn’t open ofono -folder (I havn’t permission).
You need to devel-su first, then rm -irf /var/lib/ofono/*/sms_assembly/*. If there’s something left in that directory (i for interactive will tell you), then you may be in the situation i was in. In that case, delete it (y).
1 Like
It worked for me. Thanks a lot
“ 17:46:14.117 src/sim-info.c: sim_info_network_check() ril_0 home network “elisa” - This is only I can get when I tried to send a text message. Actually Ofono adds this log again and again…
Have to say I recently had suddenly a little moment when I could send few sms messages but phone went back to mode it doesn’t try anymore to send sms messages.
@jovirkku I think blaming Elisa won’t help (you highlighted the text “elisa”). I’m using at the moment a spare phone (not a Sailfish phone) and it never had problems with text messages. My Sailfish phone had earlier (during previous year) problems with sending and receiving text messages and after the newest Tampella-update problems with sending text messages came back. I believe the problem is in my phone but I understand nothing about this problem. All I know that problems with sms is quite common atm and we hope this problem will be fixed.
Can you:
devel-sucd /var/lib/ofonofind
And post the output? (potentially, replacing the directory with a long number by XXX, i’m not sure how private this information is).
1 Like
There was a question about the operator earlier in this chain but no answer. I found the answer in that log. It is crucial to know which network to use for reproducing the problem and for testing a fix although I do not think the problem is in the network. It is rather in the way how the phone and the network co-operate. Or even more likely, some old conflicting data on the phone causes issues in some cases.
Funny enough, i’m now in the exact same situation. Last thing i have done is trying to send an sms with some special characters. Receiving seems to still work. Will try to work around this…
Can we get some instructions how to clean/fix them to confirm/exclude that?
5.0.0.61 fixed the VoLTE switch, so the previous workaround is working again (unregister VoLTE for sending SMS). Thanks to the devs!