1032101 - [Flame] Date and Time on are frequently incorrect [When using/fiddling with "Set Time Automatically"]

Status: RESOLVED WONTFIX

(Firefox OS Graveyard :: Vendcom, defect)

Description

[Mark Banner (:standard8)]

I'm using v122 for the fireware with a shallow-flash of gaia + gecko and then just updated to the latest nightly - 20140629160201. I have one UK sim card in my phone (although the signal is very weak here).

The Date & Time is set to automatic, and the Region is Europe with the City as London.

My flame device just doesn't want to keep the right time:

- Currently the time on my flame shows 1:43am, when it is in fact 10:07am.

=> It restarted with the time as 1:58am.

- Next I:
-- Go into settings, turn off automatic time setting
-- Set the time to 10:11am
-- Turn on automatic time setting
-- restart

=> Time is now 2:03am

In all the above, the Date is correct.

- Next I:
-- Go into settings, turn off automatic time setting
-- Set the time to 10:11am
-- restart (without setting automatic time)

=> It is now 10 Jan 1970 at 08:08am.

- If I wait a while and then turn on automatic time settings

=> It is the correct time and day! (30 June 2014 at 10:18am)

- So now I restart, and the time is back to 02:14am

It looks like there could be multiple bugs here:

1) Timezone is not applied on startup when automatically getting the time
2) The local time of the device is not being set correctly in manual mode

I've seen this on both devices I've got here, possibly in gecko 2.0 as well (not tested in earlier devices).

Comment 2

[Jason Smith [:jsmith]]

QA Wanted for branch checks.

Comment 3

[Mark Banner (:standard8)]

More info from testing over the course of a day with two devices:

- If you turn off automatic time setting, then set the date, it doesn't stick. You have to restart then set the date again. After that if you leave automatic time setting off, then it is stable even across restarts.

- As soon as turn on automatic time setting, expect random times to be set.

Comment 4

[Chris Kreinbring [:CKreinbring]]

The bug repros on Flame 2.1, Flame 2.0, Flame 1.4 and Open C 1.4

Flame 2.1
Build ID: 20140701040201
Gaia: 90bb898e8401f5fb98edcf38293073c5c26ab7bd
Gecko: 83c09fe3a658
Platform Version: 33.0a1
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Flame 2.0
Build ID: 20140701000201
Gaia: 8fb5e2a9ad1025ee7d247b90af7499766afadd28
Gecko: 5da69a493324
Platform Version: 32.0a2
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0

Flame 1.4
Build ID: 20140630000201
Gaia: aa896d5db1b4929f3bf31a0f4bb7de50530222a8
Gecko: 8cba60bc12ef
Platform Version: 30.0
Firmware Version: v122
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Open C 1.4
Build ID: 20140630000201
Gaia: aa896d5db1b4929f3bf31a0f4bb7de50530222a8
Gecko: 8cba60bc12ef
Platform Version: 30.0
Firmware Version: P821A10V1.0.0B06_LOG_DL
User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0

Actual result:  When restarting, the time shown on the lockscreen is different from the time that is set.  It's even worse if the Set Automatically switch is off, as the date will be changed to January 1970.

--------------------------------------------------------------------------------------------------------

The bug does not repro on Buri 2.1

Build ID: 20140701063753
Gaia: 34a52e7f024cc3d0e3aade94970773d2555f5ccb
Gecko: ffb8b976548bE
Platform Version: 33.0a1
Firmware Version: v1.2device.cfg
User Agent: Mozilla/5.0 (Mobile; rv:33.0) Gecko/33.0 Firefox/33.0

Actual Result: After restarting, the time on the lockscreen matches the set time.  Even if the Set Automatically switch is off the lockscreen time and set time match.

Comment 5

[Joshua Mitchell (Inactive)]

not a regression

Comment 6

[Mark Banner (:standard8)]

Bug 1032233 may or may not be related to this one - there are some comments overlap.

Comment 7

[Mark Banner (:standard8)]

The workarounds in Bug 1032233 comment 13 and 14 seem to fix this issue.

Comment 8

[James Graham [:jgraham]]

I am seeing something like this. When I enable the automatic date and time update, I get the following output in logcat:

D/QC-time-services(  291): Lib:time_genoff_operation: pargs->base = 2
D/QC-time-services(  291): Lib:time_genoff_operation: pargs->operation = 1
D/QC-time-services(  291): Lib:time_genoff_operation: pargs->ts_val = 0
E/QC-time-services(  291): Lib:time_genoff_operation: Connection failed !!
I/Gecko   (  291): Error reading system time
I/Gecko   (  291): Error unable to set time. Time will be lost after reboot
D/QC-time-services(  291): Lib:time_genoff_operation: pargs->base = 2
D/QC-time-services(  291): Lib:time_genoff_operation: pargs->operation = 1
D/QC-time-services(  291): Lib:time_genoff_operation: pargs->ts_val = 0
E/QC-time-services(  291): Lib:time_genoff_operation: Connection failed !!
I/Gecko   (  291): Error reading system time
I/Gecko   (  291): Error unable to set time. Time will be lost after reboot

Comment 9

[Mike Lien[:mlien]]

verify with Flame KK base image v162-3, it's fine

Comment 10

[Mark Banner (:standard8)]

(In reply to Mike Lien[:mlien] from comment #9)
> verify with Flame KK base image v162-3, it's fine

Please can you explain your comment?

There is no such base image as far as I know for the flame (and what is Flame KK?).

What do you mean by "its fine" - you don't see this issue? Which version of gecko are you using?

Comment 11

[Mike Lien[:mlien]]

(In reply to Mark Banner (:standard8) from comment #10)
> (In reply to Mike Lien[:mlien] from comment #9)
> > verify with Flame KK base image v162-3, it's fine
> 
> Please can you explain your comment?
> 
> There is no such base image as far as I know for the flame (and what is
> Flame KK?).
> 
> What do you mean by "its fine" - you don't see this issue? Which version of
> gecko are you using?

This is the latest engineering build from partner which is based on FxOS v1.4 and android KitKat
On the base image verification, I didn't encounter Date and Time incorrect problem between Set Time Automatically on/off

Comment 12

[Asa Dotzler [:asa]]

I have two Flames and one reproduces this issue reliably (or one very similar) and the other does not. If anyone would like to play with the device that's not working, feel free to visit my desk and I'll hand it over to you. (I verified that both of my devices are on the same base image and the same Gecko/Gaia shallow flash.)

Comment 13

[Martijn Wargers (dead)]

This can also cause the Marketplace app to not work, because in some cases, it won't load the site due to the wrong date (but there are cases where it might warn you that your date is probably wrong):
http://mwargers.blogspot.nl/2014/10/issues-for-first-time-user-using-flame.html

Comment 14

[Mark Banner (:standard8)]

[Blocking Requested - why for this release]:

I've upgraded to v188 a while ago, and I'm on the 2.1 series, with the previous workaround mentioned in comment 7 applied, and yet again time is now failing on my device.

Please can we get a fix on this issue - I'm not the only one seeing it, and I'm just about to give up dogfooding again, due to this issue. I'm happy to debug/test patches etc.

I hate to whine like this, but this is just fundamental to the phone.

Comment 15

[bhavana bajaj [:bajaj]]

wesly has been tracking T2M issues. I am sure there have been DUP's of this one. NI'ing to help confirm or help get input from T2M here

Comment 16

[bhavana bajaj [:bajaj]]

Hey Mark, 

I spoke to QA about this and they recommended a full flash(pick-up the choice images) :  https://intranet.mozilla.org/QA/B2G_Flash_Tools. Can you try this on the device once again and get back if you can still reproduce.

Comment 17

[bhavana bajaj [:bajaj]]

Hey Mark, have you had a chance to try this? Thanks!

Comment 18

[Mark Banner (:standard8)]

As far as I can tell, this is now WFM using the v188 image. I think what I saw a couple of weeks ago may have been a temporary regression. I'm still not sure its entirely stable, but I'm not seeing the issues I was before.

Comment 19

[Frederik Braun [:freddy]]

I still have this problem from times to times. But it's still tricky to reproduce.
v188, build-id 20141205001201, git commit 2014-12-04 21:04:37 (38e17b02).

Comment 20

[Gabriela [:gaby2300]]

This works fine for me in since several OTA updates ago.

Comment 21

[Carsten]

My Flame is also affected, running the latest v188 base image.
I am now on the latest nightly (gaia & gecko).
After a reboot, it reports the wrong time. After re-enabling, it even more off (+10 hours).
My timezone is Europe/Berlin.

Comment 22

[Martijn Wargers (dead)]

In current trunk build, I can't see the option for automatic time setting anymore.

Comment 23

[Carsten]

I've now also tried it on a second Flame, flashed it to v188 and gaia 2.1 this time. It is also losing time on every reboot (same time zone). This is really annoying behaviour...

Comment 24

[Frederik Braun [:freddy]]

(In reply to Martijn Wargers [:mwargers] (QA) from comment #22)
> In current trunk build, I can't see the option for automatic time setting
> anymore.

I get this error too sometimes. It may show up after a reboot.

Comment 26

[Carsten]

Any update on this? Bug is still there, current gaia (v2.1) flashed today. This is still very, very annoying in everyday use.

Comment 27

[Carsten]

firmware 18D fixes the issue for me completely.

Comment 28

[Mark Banner (:standard8)]

(In reply to Carsten from comment #27)
> firmware 18D fixes the issue for me completely.

This still appears to be random for different people, I see this all the time, and I've been on 18D for ages.

I believe Bug 1110010 is where most of the work is going on now.

Comment 29

[Carsten]

OK.. well, I'm also on 3.0 now. I'll test it on the other Flame with 2.1 in a week or so, I don't believe it's only a gaia bug though..

Comment 31

[BMO Automation]

Firefox OS is not being worked on