I recently updated my Samsung Galaxy S10 (“beyond1lte”) to iodeOS 6.9 the manual way. This means I made some backups und installed iodeOS 6.8 from scratch. (Btw.: Using v.6.8 made me test the builtin update process, which went well :-)) After installation I used SeedVault to restore as much apps and settings as possible.
I do not often use SMS these days so it took me a while to recognize that sending a SMS does not work. I searched the WWW for some ideas to solve the problem and came along with configuring the SMSC (Short Message Service Center). Now here is what I encountered when I tried to change:
Open phone app, type *#*#4636#*#*
Select “Telefoninformationen“
Select “Phone 0” (first SIM card) in the up most dropdown menu
Scroll to bottom of the page –> SMSC setting
The input field is empty, two buttons are active: “Update” and “Refresh”
Input “+491710760000“ and push Update –> nothing happens, send SMS not working after that, when leaving and reentering “Telefoninformationen“ the input field is empty again
Push “Refresh” –> the input field shows ":¡m",0 –> send SMS not working either
So setting up the correct SMSC didn’t work for me. In addition I need to mention that “Nachrichten” (the default iode OS SMS app) had an issue with restored data from SeedVault: The list of conversations had showed names and texts from different people i had conversations using SMS. When trying to send and SMS the sent text suddenly appears on a different conversation (and “Nachrichten” switched to that conversation too).
I even tried a different SMS app “QUIK“ which was unable to send SMS either (conversations are displayed correct though).
Now I made a strange discovery: When removing “Nachrichten” from my system, QUIK is able to send SMS!
For the moment this seems a valid workaround for me…
Does anyone have an idea what I could have done wrong on my phone or what I could do to make “Nachrichten” work again (after reinstallation)?
I can’t speak to not sending SMS, but to clarify, your messages are not stored as part of the app but instead as a separate DB on the device so you should be safe to clear the storage of the Messages app which may clear up the issues with it showing the wrong thread, etc?
Regarding not being able to send SMS, maybe that is fixed by clearing the storage as well?
Since you uninstalled it, you could try reinstalling and see if the same “mixed up messages” issue still exists, or if it re-breaks SMS sending.
I’m experiencing a similar problem under iodeOS 7.5 :
I’m using QUIK
I can receive SMS but cannot send any (unable to send message)
using the 4636 code to access the hidden menu, under “telephone information”, I also have incoherent SMSC settings : at first the field is empty, then upon pressing “update” it fills-in automatically with an incoherent chain of characters. Setting a valid phone number does not stick after clicking “update” and “refresh” either (the same incoherent setting appears).
Also it seems sometimes a part of my phone reboots (I have to enter my screen code or sim code again), and I have to restart my phone when the data would stop working (while outside and not using wifi. This glitch happened twice last week.
Fossify Messages is the default SMS app on this version of iodeOS but I cannot uninstall it (I can only uninstall the updates), so I can’t try this workaround.
Sometimes inability to send SMS is because your carrier is up-scaling the SMS to RCS messages since they detect your device is RCS capable (but iodéOS and other microG based de-Googled ROMs do not have have RCS support from the software side of things), or instead if your number was associated with an iPhone before then it could be iMessage is still hijacking your messages.
@velologiste: I encountered exactly the same behaviour in the service menu settings.
Just input the SMSC following the steps above.
I felt it worked somehow.
Yes, a correct MMSC may be needed (only for MMS though I think). If you are sending group messages (instead of individual plain text SMS to each person) or rich text / attachments then you would need MMS functionality.