Open spoorun opened 10 years ago
Hi @spoorun , the timestamp you request it 1) When message was sent on the phone 2) When message was received on the phone If this is what you want, it's already done because stored timestamp (not the added/last_modified field but sms_date field) is the timestamp on content://sms on Android.
For delivery status, you mean draft, sending, sent ? This is stored into database but not handled by client and server to update the message status
Hi @spoorun you didn't answer my question. After 1 month without activity i'll close the issue
Hi, Sorry I didn't notice your question (bombarded with emails!) 1) Outbound messages Yes, I see what you mean - that the timestamp of a message sent is stored. However, the time it is received by the recipient is not stored. By status I mean the delivery status of that message (i.e. failed, received [by recipient network], delivered [to recipient's handset]) (or the status i.e. Failed, Received, Delivered). 2) Inbound messages I also see that the time an inbound message is received is stored. However, the time it was sent by the sender should also be available. 3) Thus, at present the following three bits of data are lost when syncing: Outbound messages: a) delivery status (i.e. received by network, delivered to handset, pending, or failed). b) time of delivery status (i.e. time received by recipient, or time failed). Inbound messages: a) time sent by sender. Thanks
Hey any progress with this?
It would be really useful to record the actual time sent, received, and the delivery status (and update these as necessary).
We are happy to put a bounty on this! :)
@olantrust there is no field for that in Android database
At present the app seems to merely record a single timestamp for each message.
It would be good for incoming and outgoing messages to store: 1) sent timestamp, 2) received timestamp, 3) delivery status.
For incoming messages this information is static. Obviously for outgoing messages, the delivery status is dynamic, and the timestamp is not marked until it has been delivered (or not).
This information would enable users to properly archive messages and conversations.