Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Skip to content

device receives SMS and MMS again and again

  • /e/ version: 0.11-20200803170821
  • Device model(s): FP3

Summary

My device "receives" SMS and MMS again and again. But they haven't really been sent.

The problem

My device once received an MMS message from a person I know, all correct so far. Then, exactly 24h later, I got the same message again. Next day the same, and also the following days, again and again, always the same message. But the sender did send it only once at the beginning.

Meanwhile it happened also with simple SMS messages.

One message came even twice every day, the same message in two exemplars.

Not every message is received again and again, only some special, about 1 of 20.

First I thought it was the Message app. But now it happens also with QKSMS, so it must be deeper in the system.

I also thought about the provider and contacted him. Didn't get an answer for a weak now. But I can't beleave the provider does this. I never had this in 15 years.

Note: my device does no synchronization with any cloud at all.

Steps to reproduce

Start an SMS chat, 20 or more messages on both sides, and don't delete one. A problem reproducing it is that you must wait for 24h. But when it happens it will be reliable, next day in the same minute.

What is the current behavior?

See what I said above, that's exactly the current behavior.

What is the expected correct behavior?

I would like to receive a message when it has been sent. Don't see any worth in getting it again and again.

Technical informations

Relevant logs (adb logcat)

Don't know where to look at, sorry.

Relevant screenshots

Solutions

Workaround

The receiving seems to stop when you terminate the Message app hardly, clear all it's data and cache completely and then reboot the device, so that the device restarts the Message app. After this you have some peace and quiet and you can indeed receive some ordinary messages until a new message causes this mess again.

Possible fixes