[B2GDroid] Disabling Lock Orientation in Firefox OS has no affect if Droid has Auto-rotate screen disabled.

NEW
Unassigned

Status

B2GDroid Graveyard
General
P2
normal
3 years ago
2 years ago

People

(Reporter: Johnt, Unassigned)

Tracking

Details

(Whiteboard: [3.0-Daily-Testing], URL)

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
Created attachment 8622729 [details]
logcat_20150615_1443.txt

Description:
Disabling the Lock Orientation in Firefox OS has no affect if Droid has Auto-rotate screen disabled.


Repro Steps:
1) Update to B2GDroid 20150612092905
2) Select Droid Settings > Display
3) Deselect Auto-rotate screen box.
4) Launch Firefox OS.
5) Select Firefox Settings > Display
6) Disable Lock Orientation
7) Launch a screen that uses Landscape mode. (Such as browser and photos from gallery.)


Actual:
Firefox OS lock orientation remains enabled due to Droid settings.

Expected:
It is expected that the Firefox OS settings can have the lock orientation disabled regardless of Droid settings OR that the Droid Auto Rotate Screen will update according to the Firefox Lock Orientation settings.

Repro frequency: 100%.
See attached: Logcat & Video
(Reporter)

Comment 1

3 years ago
This issue does NOT occur on the Flame 3.0

Result: There are no Droid settings in Firefox Flame.

Environmental Variables:
Device: Flame 3.0 Kitkat Full Flash (319mb)
BuildID: 20150615010203
Gaia: 1bf2da102560481748ff3f6202fbed5c4daa5832
Gecko: 3c26bef95d54
Gonk: a4f6f31d1fe213ac935ca8ede7d05e47324101a4
Version: 41.0a1 (3.0) 
Firmware Version: v18D-1
User Agent: Mozilla/5.0 (Mobile; rv:41.0) Gecko/41.0 Firefox/41.0
Blocks: 1170323
QA Whiteboard: [QAnalyst-Triage?]
status-b2g-master: --- → unaffected
Flags: needinfo?(ktucker)
Whiteboard: [3.0-Daily-Testing]
status-b2g-master: unaffected → ---
Flags: needinfo?(ktucker)
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]

Updated

2 years ago
Component: General → General
Priority: -- → P2
Product: Firefox OS → B2GDroid
You need to log in before you can comment on or make changes to this bug.