Closed Bug 1181606 Opened 10 years ago Closed 10 years ago

[aries-l] Resolution of phone is incorrect

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

defect
Not set
normal

Tracking

(blocking-b2g:2.5+, b2g-master fixed)

RESOLVED FIXED
FxOS-S2 (10Jul)
blocking-b2g 2.5+
Tracking Status
b2g-master --- fixed

People

(Reporter: AdamA, Assigned: gerard-majax)

References

Details

(Keywords: regression, smoketest, Whiteboard: [aries-l-support][Spark])

Attachments

(7 files)

Attached file logcat
Description: The text and many elements of the phone are very small. Repro Steps: 1) Update a Aries to 20150707205829 2) Progress to home screen 3) Observe screen 4) Navigate throughout phone 5) Observe size of screen elements Actual: Many elements of the screen are very small Expected: It is expected that users can read all email elements Environmental Variables: Device: Aries 2.5 Build ID: 20150707205829 Gaia: 553e4e281d11500bea702918841f011bfb5405f7 Gecko: 0246d86e619670bf381d45d587e8ab036e7a8db5 Version: 42.0a1 (2.5) Firmware Version: D5803_23.1.A.1.28_NCB.ftf User Agent: Mozilla/5.0 (Mobile; rv:42.0) Gecko/42.0 Firefox/42.0 Repro frequency: 10/10 Link to failed test cases: https://moztrap.mozilla.org/manage/case/1296/ https://moztrap.mozilla.org/manage/case/6784/ See attached: screenshot, logcat
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(pbylenga)
Whiteboard: [aries-l-support][Spark]
Attached image Small text settings
Attached image Small lock screen
Attached image Small text homescreen
NI on Component owner to take a look.
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Component: General → Layout
Flags: needinfo?(pbylenga) → needinfo?(npark)
Product: Firefox → Core
[Blocking Requested - why for this release]: Required for Lollipop support of Aries device.
blocking-b2g: --- → 2.5?
NI on myself to investigate later.
Flags: needinfo?(nhirata.bugzilla)
Right, flashing my old boot.img fixes. It's likely something broke on kernel side :(. Maybe adam know ? I cannot investigate this for now.
Flags: needinfo?(adam)
I recently hit a similar issue on two Sony devices, I fixed it in kernel dtsi with: qcom,mdss-pan-physical-width-dimension = <56>; qcom,mdss-pan-physical-height-dimension = <99>; somc,mdss-phy-size-mm = <56 99>; most Z devices have the somc line, but not the qcom lines, which seem to be the important ones. The should be added to arch/arm/boot/dts/qcom/dsi-panel-<device>.dtsi
Flags: needinfo?(adam)
That do works :). Why was this not broken before, I cannot tell.
Attachment #8631138 - Flags: review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Flags: needinfo?(npark)
Assignee: nobody → lissyx+mozillians
Component: Layout → GonkIntegration
Product: Core → Firefox OS
blocking-b2g: 2.5? → 2.5+
Target Milestone: --- → FxOS-S2 (10Jul)
Blocks: aries-l
Summary: [Aries] Resolution of phone is incorrect → [aries-l] Resolution of phone is incorrect
Flags: needinfo?(nhirata.bugzilla)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: