Well one thing for sure, my jolla one with sailfish 3.4 does not lose any message, so something happened on the road to sf 4 (i noticed i was losing messages in sf 4.5)
I know sf 3.4 is working cause if i request an activation code or an otp, it arrives straight away, while on the xa2 i often have to resend the message multiple times…
X10III, SFOS 5.0.0.68 (current), no VoLTE (incompatible operator )
This morning: I received only the last from a series of SMSs from a sender. No trace of the others.
Past issues, older SFOS versions: some SMSs -or even parts of longer ones- appear like sent by a special, short number- instead of being linked under the message sender.
The sender is abroad if that matters,on Android, and may use some unicode chars.
My hypothesis: something in the message structure (operator related, charset related ) derail the SFOS handling of the message.
Question: is it possible to turn on persistent logging of the raw data of SMS/MMS/alerts/voice message notifications etc - for offline inspection?
@247
A lot about the networks has also changed.
@rtr2001
Rather fantastical hypothesis, but ofono logger should be just that.
1 Like
Today i discovered that my problem just disappeared. I don’t have a clue what happened, i changed nothing.
10ii sfos 5.0.68 : last weeks, a random part of SMS I,ve received was seriously delayed (around 1 week delayed).
I think it was my operator which get the problem.
I have the same problem recently with one contact on XA2 (h4113), Sailfish 5.0.0.68, 2G. I’ve looked into /var/lib/ofono//sms_assembly, but there was no track of the completely missing message (and same for the previous noticed occurence). Later he re-sent the message and it was also interesting, because according to my operator’s metadata, both consisted of 4 parts. But the re-sent message happend to be incorrectly assembled, leaving part 004 inside subdirectory of sms_assembly, showing that part 004 is not the last, as after the omitted part there were 9 more characters the message continued with. Time of the 004 file is 18:51:44, a second after third message and two seconds before fourth by operator’s metadata. Time distance (as recieved by operator? - would need to investigate) between parts was in both cases <=6s. I will try ofono logger, hope I will get some more useful info.
1 Like
I’ve also seen partial SMS many times, or SMS received as “corrupted”, containing parts of some earlier messages in them. There is definitely something wrong with the messages/parts handling.
3 Likes