SMS received time displayed has false timezone adjustment

Bug Reports
1

REPRODUCIBILITY: 100
OS VERSION: 4.6.0.15
HARDWARE: X10 III
UI LANGUAGE: Enlish
REGRESSION: Yes

DESCRIPTION:

When an SMS is received, the time displayed says “in 12 hours”. I am in NZ i.e. my TZ is 12 hours +1 hr daylight savings, from UTC.

e.g. A message is rx at 7:35AM NZDT.
At 8:53am, the sms screen shows the message time as “in 11 hours”

A message is rx Fri 6 dec, 1pm. SMS screen shows Saturday 2am.

Sent message times/dates are correct.
In the activity log of the contact page dates/times are correct.

It appears to me that it is taking an already local time in the message header, and correcting it as if it was UTC and needs to be corrected to local time.

I think this is a regression, I do not recall this happening long ago.

PRECONDITIONS:

STEPS TO REPRODUCE:

EXPECTED RESULT:

ACTUAL RESULT:

MODIFICATIONS:

none

ADDITIONAL INFORMATION:

Carrier: 2degrees

2

I’m in New Zealand too but don’t have this issue. 10iii running 4.6.0.15. Which carrier are you with? I’m on Spark.

Time zone settings: auto update, automatic time zone update.
Time zone shown as New Zealand, Auckland. Correct date and time displayed.

3

2degrees.
The only place I notice this is the SMS message list. Other places it is correct

4

What about changing the time zone to something else then changing back to New Zealand?

It would be interesting to try another carriers sim to see what happens.

Has this just started happening since daylight saving started?

I had a similar issue with Meecast where the lock screen info was showing the moon instead of the sun making me think it was 12 hours out. It resolved itself without me doing anything. I’m not exactly sure when it started but possibly around the time daylight saving started.

5

This time it started over daylight saving (1 Oct).
last summer it began around start of feb, and stpped with the end of daylight saving (7 april).

so this suggests it

  • requires daylight saving
  • began around 1 feb 24, perhaps with an update
6

Your theory makes sense. I wonder, is it related to 2 degrees or a glitch on your phone?

7

I have no idea when I did updates.
I does say to me that there is a timestamp in the message that is being displayed (rather than SFOS itself saving the time it received the message)

This would all be rather difficult to diagnose and fix, except that the history of messages in the address book, displays the correct time always. It is the message app that shows the incorrect values. Therefore the problem lies in the different formatting function used to display it in messages, and should thus be an easy fix, not requiring my carrier (2degrees).

8

I agree the fix shouldn’t require any action my 2 degrees.

Before a fix can be applied though, you need to know if it’s the way 2 degrees timestamp is handled or if its just a glitch on your phone. The fix will be different for either situation. Hence my question.

9

Not really.
The history works properly.
The history datetimes are always correct. Assuming that the history datetimes are correct for everyone, then the fix is to use the same formatting code in the messages pane as in the history. Knowledge of the root cause is not actually required i.e. they shouldn’t need to be me to fix it.

10

In that case your logic makes sense. :slightly_smiling_face:

11

Thanks for this post. I’m also in New Zealand, and I’ve had this exact issue since I started using the Jolla C2, in March 2025, Sailfish version 5.0.0.55; it’s persisted over daylight saving dates. I use Nova which runs over 2 degrees.
No problems earlier, on Sony Xperia 10-II.
Not a big issue (though quite amusing to receive a message in the future); problems with connection and battery rundown have taken priority. Good to know it’s not just me.

12

Does VoLTE work for you?

13

Settings > Mobile network shows ‘4G calling (VoLTE)’, and ‘Select network automatically’. I can make and receive phonecalls, so I assume VoLTE is working. Should I check anything else?

14

Under the ‘4G calling (VoLTE)’ toggle there should be status of it, either Registered, Registering or “Not registered”.

15

Thank you–it says Registered.

16

@mguise @crun @AlanBreen

Hey guys, I hope you don’t mind me tagging you all - I’ve got a Xperia 10 III and can’t get VoLTE working in NZ. I’m on Skinny, though bought a 2 Degrees SIM to try see if that would sort it (it didn’t). It’s not registering VoLTE for me and it switches to 3G for calls.

Have any of you guys got any tips per chance (given you’ve got it working)? Could it be an issue with the specific 10 III model?

Otherwise my next step is to install LineageOS and see if I can get VoLTE working to confirm it’s not a model issue (which means a factory reset in a way).

Thanks

17

Hi Tom.

I also have a stock Android 10III and it will not do VoLTE or VoWiFi on 2degrees,Voda or Spark - it’s not a Sailfish issue. 2degrees has turned off 3G now, and mine is now useless for phone

Btw, there is no listed Lineage for 10III.

Sony did not install any .mbn files for NZ in these phones, because they weren’t selling them here. There is a dir for AU, but not NZ I have not managed to find such a file. I did ask about adding them in Community meeting on 11th September 2025 - #2 by crun but I got no answers to any of those questions.

I don’t know if the 10IV or 10V work in NZ, but 10VI allegedly does.

1 Like
18

Thanks - very disappoint to hear. I’ll try install a random rom and will give this a go

If I get it going, I’ll let you know - I’d hate for your 10 III to go to waste.

19

Nothing i tried worked, as you’ve already figured out…

20

Scratch that, I flashed the XQ-BT44_MVNO JP_62.1.A.1.431 firmware onto it (which is the 10 III Lite firmware from Japan) and i now have VoLTE - I wonder if I can bring it across to Sailfish