Closed Bug 1179354 Opened 9 years ago Closed 9 years ago

Automatic brightness jumps from A to B without fading gradually or at all

Categories

(Firefox OS Graveyard :: GonkIntegration, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: scabral, Assigned: tzimmermann)

References

Details

(Keywords: foxfood)

Attachments

(1 file)

Automatic brightness jumps from A to B without fading gradually or at all
The brightness slider is nice and gradual and can adjust at a very fine level. The auto-adjust brightness just sharply goes from point A to point B with no transition whatsoever.
QA Whiteboard: [foxfood-triage]
This is annoying and I am going to fix it.
Assignee: nobody → cyu
It appears that the problem is not in the gaia layer. The same system app is pushed to aries-kk and aries-l, but the 2 devices behaves differently w.r.t. auto brightness. On KK the mapping from [0.1, 1] to actual screen brightness is much smoother than that on L.
This is a comparison of brightness settings on KK (left) and L (right).
The camera setting is fixed at ISO 200, F2.0, shutter speed 1/125.

From up to down, the brightness is set to minimum, ~45%, ~80%, maximum.

It can be seen that Aries-KK has far more dramatic changes in screen brightness when the setting changes. That means even a small change (0.1, the minimum change we will make in gaia) results in a visible change to the user. Even walking by a lamp, or standing on the escalator, where the artificial light sources results in 0.1 or 0.2 gaia brightness change, will cause pretty visible adjustment of screen brightness and create a feeling of screen flickering.
Unassign from this bug since the problem is very likely to be in the gonk level. We need gonk guys to investigate further.
Assignee: cyu → nobody
Thomas, is there something you can do on that ?
Assignee: nobody → tzimmermann
(In reply to David Scravaglieri [:scravag] from comment #6)
> Thomas, is there something you can do on that ?

Not before Thursday, but I can that a look later this week.
ni?'ing myself
Flags: needinfo?(tzimmermann)
To clarify, with bug 1179353 landed, this bug may not be valid. The original problem is that we don't have a smooth transition with auto brightness. The test I made in this bug shows that flame and aries-l has a narrow brightness range, which hides the problem with the screen brightness algorithm to some extent, but it's another problem. Now we should not see an abrupt jump between screen brightnesses so I think we can close this bug.
Component: General → GonkIntegration
Cervantes,

is this bug report still valid?
Flags: needinfo?(tzimmermann) → needinfo?(cyu)
This bug is no longer valid.
Flags: needinfo?(cyu)
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: