Same for me here with my s9 after Update to eOS 4.0 : no SMS transmission.
In addition, I need frequently to restart /e/OS in order to getting normal sound back from the speaker when making a call. Otherwise the words of the person I am speaking to are incomprehensible.
1 Like
Thanks for sharing the log. You show some “recovering” errors just like mine.
Quite possibly worth adding to your issue.
Reflecting on my own log … I took two logs with that command one transmit one receive successful SMS but I guess they don’t tell a sufficiently big picture.
Maybe with all apps closed for a few minutes (to ensure useful timestamps), try opening Message at a recorded time then
$ adb logcat -d > logcat.txt
See if anything crops up there (and perhaps submit to your issue but would require redacting).
Perhaps someone could suggest a more useful logcat command (or spot something obviously relevant) … you could consider to ask on your issue. (??)
Thanks for the report! I have the exact same problem: no sms sending possible on Samsung S9 since /e/ 4.0, also with other tools like quik or fossify messages. And also in my case the SMSC field is empty until I hit “Aktualisieren”, then the correct number of my provider (congstar/Telekom) gets inserted, followed by “145”. But even after that, no sms sending possible. I wanted to support your gitlab report but they would not let my register (refused my email provider).
3 Likes
Please check the “Getting login error” here Report an issue.
It suggests to use the email address derived from an account at murena.io.
same Problem with SMS on Galaxy S9 here.
Also the Sound while having a Telefon Conversation is very distorted.
2 Likes
Although this seems to be Samsung Galaxy specific, I have a similar issue on FP6 with a permanent workaround, maybe its worth giving a try.
Call *#*#4636#*#* (or whatever is required to access the Phone Information settings, may be phone specific) and the select “Phone information”. There you can set the “preferred network type” to “LTE only” and then restart the phone.
I have exactly the same problem since the update to 4.0 (galaxy S9, RégloMobile). I can’t sent SMS or receive phonecall.
Can you do something to fix it ?
1 Like
I solved my problem with receiving a phone call by forcing the connection to 3G. This is a temporarily acceptable solution…
1 Like
Same here, I can receive and respond to calls again after deactivating VoLTE 
The SMS issue remains
Today I plugged the SIM card from my S9 into an old Android device because I wanted to check the SMS sending. Also on that device the reception works, but not the sent. Maybe the update did something to the sim card? I tested a third device, the result was the same. Have any of you tried this yet?
Not a full explanation but Samsung does not do VoLTE on (most) Custom Roms as Samsung use their proprietary firmware for this.
Around the world users have mostly been hit by this as their carrier makes “announced” changes to VoLTE.
Maybe the upgrade caused some settings to change to a non-match with what your carrier can do.
Hence
is a winner.
Forum search #Samsung + #volte
Well it is always possible that a SIM card fails to keep up with the current way the carrier can operate with AOSP releases, if Google Android or the carrier builds in any SIM “helpers”. See also Post #12 where “updating” the SIM is described.
@aibd Unfortunately, another thread got in between what I was saying And it was missed that my problem has been for a couple of months and with v3.73, then continued into 4.0. I thought I would not be adding 4.0 but then it was in the updater and when I read the release notes, apparently there are several modified versions and each phone has a slightly different variation. This is not a Samsung, it is a warranty replacement for a Murena one, that I bought thru Murena. It was a great little phone but one day just died. That was in 2024 and this replacement has been PIA ever since.
Now with reading various articles about Mediatec, I think I am going to stop eating and buy a new phone.
Anyway, I have been reading everything I can find, I have tried all the fixes I could find, nothing works except restarting phone.
Thank you for all your help.
Naillig59
if you read logcat, I’d skip the grep filtering to the message appid and get the full second after a the sending attempt action. Entries by the telephony stack or firmware even can be me more relevant.