I'm having a problem with SMS that manifest recently.. I went on holiday and took with me a prepaid Mastercard card that I loaded money onto.
The service sent text messages every day of the balance on the card. The SMS seem to have been sent with the literal text CASH P'PORT in the "sender number" area of the sms, rather than a proper phone number

One oddity I noticed with these messages was that, though I could see the contents of them in the Conversations app (in the list of all conversations) thus:

if i tapped on them to open the conversation, the screen was always blank.

The problems seem to have come when I accidentally sent a message in response to one of these SMS. A notification banner saying "SMS sending failed" appeared. CASH P'PORT was bumped to the top of the Conversations inbox, and had a red triangle next to it. I held my finger on it for a while then opted to delete the conversation from the phone.. It's gone, but now (and this may be coincidental) SMS won't send, and there's a problem with receiving SMS:

When an SMS comes in, there is the notification and the sound. If I go to task manager, I can see the SMS in a yellow box, tap on it to open it and read it normally, including all the previous SMS in a normal conversation flow.
If I close the SMS and go back to Conversations app, the SMS text of what I just received isnt shown underneath the contact and the list of conversations hasnt updated to show the latest SMS. If I reopen the conversation by tapping on it from the list, the conversation flow does NOT include the latest SMS received

Conversations is now running very sluggishly and behaving unusually. If I send an SMS to myself it opens it instantly rather than showing a notification.


I note that if I remove el-v1.db from the ~/.rtcomm-eventlogger directory, I lose all SMS etc since I upgraded to PR1.2 but the Conversations app works correctly. If I run with both el.b and el-v1.db in the dir, or just el-v1.db then it doesnt wok correctly..

Does anyone know what's going on?