Closed
Bug 1066329
Opened 10 years ago
Closed 9 years ago
[Settings] After changing region manually setting date and time to set automatically does not display current region.
Categories
(Firefox OS Graveyard :: Gaia::Settings, defect)
Tracking
(b2g-v2.0 unaffected, b2g-v2.1 affected, b2g-v2.2 affected)
RESOLVED
DUPLICATE
of bug 1100261
Tracking | Status | |
---|---|---|
b2g-v2.0 | --- | unaffected |
b2g-v2.1 | --- | affected |
b2g-v2.2 | --- | affected |
People
(Reporter: rmitchell, Unassigned)
References
()
Details
(Keywords: regression, Whiteboard: [2.1-flame-test-run-2] )
Attachments
(1 file)
103.86 KB,
text/plain
|
Details |
Description: After changing region manually setting date and time to set automatically does not display current region as taken from the geolocation, which is toggled on and should have current location info. Repro Steps: 1) Update a Flame to 20140910000202 2) Go to settings date and time > turn off set automatically 3) Change the region settings to some place user is not located 4) Turn to set automatically Actual: region and time zone stay the same as manually set Expected: using geolocation find where user is and set time and region Environmental Variables: Device: Flame 2.1 Build ID: 20140910000202 Gaia: 79dc972d637ff5ef7667b231e93118b4ed83ba9c Gecko: 0890010015a2 Version: 34.0a2 Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Repro frequency: 100% See attached:logcat, video clip: http://youtu.be/5-YW4gSKgy4
This issue DOES occur on Flame 2.2 (319mb),Open C 2.2, Flame 2.1(512mb), Open C 2.1, After changing region manually setting date and time to set automatically does not display current region. Flame 2.2 Environmental Variables: Device: Flame Master (319mb) BuildID: 20140910040203 Gaia: 8e02f689b0fc39cb6ccdc22d02ed7e219c58faa7 Gecko: 152ef25e89ae Version: 35.0a1 (Master) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Open C 2.2 Environmental Variables: Device: Open_C Master BuildID: 20140910040203 Gaia: 8e02f689b0fc39cb6ccdc22d02ed7e219c58faa7 Gecko: 152ef25e89ae Version: 35.0a1 (Master) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 Flame 2.1 Environmental Variables: Device: Flame 2.1 (512mb) BuildID: 20140910000202 (512mb) Gaia: 79dc972d637ff5ef7667b231e93118b4ed83ba9c Gecko: 0890010015a2 Version: 34.0a2 (2.1) Firmware: V123 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 Open C 2.1 Environmental Variables: Device: Open_C 2.1 BuildID: 20140910000202 Gaia: 79dc972d637ff5ef7667b231e93118b4ed83ba9c Gecko: 0890010015a2 Version: 34.0a2 (2.1) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 This issue does not occur on Flame 2.0(319mb), and Open C 2.0 Flame 1.4 (319mb) 1.4 Open C Phone uses geolocation find where user is to set time and region Flame 2.0 Environmental Variables: Device: Flame 2.0 (319mb) BuildID: 20140910000203 Gaia: 3f4c635106c5364228782d12b1cb76b0c105b971 Gecko: 02a5b9234c13 Version: 32.0 (2.0) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Open_C 2.0 Enviromental Variables: Device: Open_C 2.0 BuildID: 20140910000203 Gaia: 3f4c635106c5364228782d12b1cb76b0c105b971 Gecko: 02a5b9234c13 Version: 32.0 (2.0) Firmware: P821A10v1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0 Flame 1.4 Environmental Variables: Device: Flame 1.4 (319mb) BuildID: 20140910000204 Gaia: 6018a1c18f0c3eab25aac2ba3064904740591dd2 Gecko: 90e68c490bf9 Version: 30.0 (1.4) Firmware Version: v123 User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0 Open C 1.4 Environmental Variables: Device: Open_C 1.4 BuildID: 20140910000204 Gaia: 6018a1c18f0c3eab25aac2ba3064904740591dd2 Gecko: 90e68c490bf9 Version: 30.0 (1.4) Firmware Version: P821A10V1.0.0B06_LOG_DL User Agent: Mozilla/5.0 (Mobile; rv:30.0) Gecko/30.0 Firefox/30.0
Comment 2•10 years ago
|
||
The user can manually set it back to the country they are currently in so I don't think this is serious enough issue to block on. Plus, this could be a visual only issue. I'm not sure whether or the correct region is being set in the background when the user toggles automatic.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(ktucker)
Comment 3•9 years ago
|
||
Duping against bug 1100261 where UX has already put their input.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•