Closed
Bug 1133803
Opened 9 years ago
Closed 6 years ago
Flame: when SIM card is not present and wifi is connected, the phone gets incorrect time
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(b2g-v1.4 affected, b2g-v2.1 affected, b2g-v2.2 affected, b2g-master affected)
People
(Reporter: njpark, Unassigned)
References
Details
STR: - Check phone with active sim card has 'set automatically' enabled under Settings -> Date/Time - Check the time is correct - Turn off the phone, pull out the sim card, restart the phone - Enable wifi and ensure it is connected - Go to settings -> Date/Time Actual: Even when the correct timezone is set, and 'set automatically' switch is still enabled, the time is off by 45 min ~ 3 hours Expected: Time is correct Version info: This reproduces in 2.2 and Master branch. Gaia-Rev 2a2b008f9ae957fe19ad540d233d86b5c0b6829e Gecko-Rev https://hg.mozilla.org/mozilla-central/rev/2f5c5ec1a24b Build-ID 20150213010213 Version 38.0a1 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150213.043439 FW-Date Fri Feb 13 04:34:49 EST 2015 Bootloader L1TC000118D0 Gaia-Rev e827781324cbde91d2434b388f5dead3303a85ee Gecko-Rev https://hg.mozilla.org/releases/mozilla-b2g37_v2_2/rev/0552759956d3 Build-ID 20150209002504 Version 37.0a2 Device-Name flame FW-Release 4.4.2 FW-Incremental eng.cltbld.20150209.040038 FW-Date Mon Feb 9 04:00:51 EST 2015 Bootloader L1TC000118D0
Comment 1•9 years ago
|
||
I don't repro on a Buri with the latest 1.4. This might be linked to bug 1061797. Let's make sure this is an actual bug with the Flame or the base image. QA wanted to check 1.4 Jelly Bean on the Flame. If it doesn't repro there, please check 2.1 KitKat vs 2.1 Jelly Bean.
status-b2g-v1.4:
--- → ?
status-b2g-v2.2:
--- → affected
status-b2g-master:
--- → affected
Keywords: qawanted
fyi, not sure if this is just flame.
Flags: needinfo?(mwu)
Comment 3•9 years ago
|
||
Buri would not show this problem. This needs to be tested on a Flame or some other modern QC device.
Flags: needinfo?(mwu)
Comment 4•9 years ago
|
||
This issue DOES occur on Flame JB 1.4 and 2.1 as well as Flame KK 2.1. I do not have access to Aurora or b2g32 builds for Flame JB so I had to go with the last 2.1 build before Central became 2.2 instead. Flame KK: Environmental Variables: Device: Flame 2.1 BuildID: 20150217093136 Gaia: 221e911a388916834d5da40190c52189b1676b21 Gecko: 36e5b43c1970 Version: 34.0 (2.1) Firmware Version: v18D-1 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Flame JB: Environmental Variables: Device: Flame 1.4 BuildID: 20150217054832 Gaia: 04265f42139a7a5c611c45e4869582642927e835 Gecko: 4d96752782bf Version: 30.0 (1.4) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Environmental Variables: Device: Flame 2.1 BuildID: 20140901224717 Gaia: 44bf2e3bc5ddea9db9a8c851bd353cb234aa883c Gecko: c360f3d1c00d Version: 34.0a1 (2.1) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0
Updated•9 years ago
|
QA Whiteboard: [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Updated•8 years ago
|
QA Whiteboard: [QAnalyst-Triage+] → [QAnalyst-Triage+][Low_QA]
Comment 5•6 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•