Bug 4670 – make brightness static unless brightness is pressed

Bug 4670 - make brightness static unless brightness is pressed

Summary:

make brightness static unless brightness is pressed

Status:	RESOLVED FIXED

Product:	SB 2/3
Classification:	Unclassified
Component:	Graphics
Version:	75
Platform:	All All

Importance:	P2 enhancement (vote)
Target Milestone:	---
Assigned To:	Chris Owens

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2007-01-15 10:37 UTC by Kevin Pearsall
Modified:	2007-10-26 09:12 UTC (History)
CC List:	2 users (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Kevin Pearsall 2007-01-15 10:37:25 UTC

http://forums.slimdevices.com/showthread.php?t=31652

seems reasonable to have the brightness saved in nvram like the player name is now.  that way squeezenetwork maintenance for instance wouldn't change the brightness of the display...

Comment 1 Andy Grundman 2007-01-15 12:47:32 UTC

Since this is only really a problem for the SN downtime service, I'm also going to see about getting the right prefs or setting brightness to 0 until a key press.

Comment 2 Mark Lanctot 2007-01-16 07:18:52 UTC

Wouldn't this also be an issue for SlimServer operation when it loses contact with SlimServer?  "Problem: Can't connect to SlimServer" is displayed at full brightness.

I didn't fully understand the thread in question, I believe the poster's SlimServer was in hibernate mode at the time, but this would be useful for SlimServer operation as well - you'd want to know when the SB loses contact with SS, but there's no reason for full brightness.  If this was fixed, might as well make it work for both SS and SN.

Comment 3 Andy Grundman 2007-01-16 13:00:51 UTC

I tweaked the downtime service so it should do the right thing when it comes to brightness levels.  There does appear to still be a minor firmware bug though related to a flash of bright text whenever the slimproto connection is closed.  I've opened this as bug 4673.

Comment 4 Blackketter Dean 2007-10-26 09:12:08 UTC

This appears to be fixed.  Reopen if it's still an issue.