Ubuntu
repowerd package

Possible to manually set display brightness to 0 on Ubuntu Touch on Aquaris E5

Bug #1483427 reported by Stefan
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
indicator-power (Ubuntu)
Invalid
Undecided
Unassigned
repowerd (Ubuntu)
New
Undecided
Unassigned

Bug Description

Possible to manually set display brightness to 0 on Ubuntu Touch

It is possible to move the brightness slider to the very left position, which will set the display brightness of affected device to zero, or, to total darkness.

This is a bug, since this leads to user's inability to set the brightness back or, generally, to operate the device.
There is a slight chance, though, to return the brightness back to non-zero value (blindly, trying by user's memory).

Also, this gets even more problematic, if we think about a scenario, where such Ubuntu device is locked by a PIN.
User has to try to unlock the device on the dark screen, open the top panel with settings, scroll to the far right (to access the brightness settings), and then trying to hit the correct slider - all on a dark screen.

This happened on Aquaris E5.

Revision history for this message
Oliver Grawert (ogra) wrote :

funny, this bug was fixed for the 4.5 a while ago, seems the vegeta also needs the same fix of the brightness xml file.

summary: - Possible to manually set display brightness to 0 on Ubuntu Touch
+ Possible to manually set display brightness to 0 on Ubuntu Touch on
+ Aquaris E5
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-power (Ubuntu):
status: New → Confirmed
Revision history for this message
Stefan (boldos) wrote :

Bug still present on E5 after OTA-10.

Revision history for this message
Charles Kerr (charlesk) wrote :

Reassigning to powerd. Indicator-power gets the min/max brightness range from powerd by calling com.canonical.powerd's getBrightnessParams() method.

Changed in indicator-power (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Stefan (boldos) wrote :

Issue still present after OTA-11 and OTA-12.
1) Why is this closed as invalid please?
2) Shall this be re-assigned somewhere else? Please advise...

Revision history for this message
Oliver Grawert (ogra) wrote :

it was closed as invalid for indicator-power because the problem is in powerd ... so a new task against powerd was opened

Revision history for this message
Stefan (boldos) wrote :

Fixed with OTA-13. Thank you.

Revision history for this message
Stefan (boldos) wrote :

Unfortunately, bug re-introduced for E5 by OTA-14.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Lukáš Tinkl (lukas-kde)
affects: powerd (Ubuntu) → repowerd (Ubuntu)
Launchpad Janitor (janitor)
Changed in repowerd (Ubuntu):
status: New → Confirmed
Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

Repowerd reads the min/max values from the device config xml file shipped with the device. Does this file contain sane values?

Could someone with an E5 device paste the contents of:

1. /usr/share/powerd/device_configs/config-default.xml
2. /var/log/repowerd.log

Thanks.

Revision history for this message
Stefan (boldos) wrote :

My config attached.

Revision history for this message
Stefan (boldos) wrote :

And here is the second one...

Revision history for this message
Stefan (boldos) wrote :

In the example above, I dimmed backlight to complete black (nothing visible) 2x, just before posting the log...

Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

Thanks for the information.

I don't see anything wrong in the attached files. Both repowerd and the indicator use the value set in the config-default.xml file as the minimum value (5 out of max 255 => ~2%). I suspend this value may be too low for this device.

Note that '5' is also the value used for dimming the screen. If you set the normal brightness value at a normal or high level, do you notice the screen dimming a bit before the inactivity timeout expires, or do you just see the screen blanking without dimming first?

Revision history for this message
Alexandros Frantzis (afrantzis) wrote :

... I *suspect* this value may ...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.