Closed
Bug 1081862
Opened 11 years ago
Closed 7 years ago
Presetting the device time to something close build time if both NITZ and NTP fail to update correct time
Categories
(Firefox OS Graveyard :: Gaia::First Time Experience, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: wchang, Unassigned)
Details
Often times the device would get started up and loaded into homescreen without network or SIM card at first, and hence failing to retrieve time from NTP or NITZ information.
The default time is 1970/1/1 and causes all SSL connections to fail including marketplace. If we can setup the device time to something close (within a month or so) then this should be avoided in most cases if NTP or NITZ fails.
Starting this bug for discussion and solution.
| Reporter | ||
Comment 1•11 years ago
|
||
Shawn,
As discussed previously you might have some ideas to do this?
Flags: needinfo?(sku)
Updated•11 years ago
|
Flags: needinfo?(sku)
Comment 2•11 years ago
|
||
Ooops, wrong cc'd vchang for this bug. keep ni? myself.
Flags: needinfo?(sku)
Comment 3•11 years ago
|
||
It really depends on the flash procedure partners have.
Take our flow as an example:
we will use below commands to update the device time after flashing the image.
run_adb wait-for-device &&
run_adb shell toolbox date `date +%s` &&
run_adb shell setprop persist.sys.timezone $TIMEZONE
Flags: needinfo?(sku)
Comment 4•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•