View Single Post
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#747
Originally Posted by mcow View Post
But I've got an N800! Could it be automated for that case?
Originally Posted by mcow View Post
edit: oh, wait: you are talking about a reset from 0-127 to 1-5, which I do not see happening. (That is mentioned on the Settings App's page for Brightness.) I don't think changing the actual level from 40 to 76 is the same thing, nor is the failure to adjust the brightness back down to 40, which ASUI should be able to do (on the N800, at least).
When MCE is started/restarted it sets brightness to the 1-5 value.

When I mentioned the ALS problem I also mentioned this:
Another problem is the dim state, there can be a slight lag between the screen dimming and ASUI receiving the signal. If ASUI were to check brightness during this period it would effectively undo the dim.

Another problem is that ASUI only checks brightness when it is mapped, so you'd have to actually map ASUI for it to correct the brightness. This is only a problem when restarting MCE and would be better handled with a button to correct the brightness in asui-settings. And also by fixing any issues that cause MCE to require a restart.


Originally Posted by mcow View Post
I can't find anything on the website about the Services or MCE settings pages. The existing docs for Settings stop after Alarm.
That section only documents the gconf keys that ASUI declares and there are no keys used by the Services and MCE pages. That section was important before the GTK app existed, now it just serves as good documentation of ASUI's internals. The first group was also outdated so thank you for mentioning it. I've also added a note to document the Services and MCE sections when I get back.
 

The Following User Says Thank You to auouymous For This Useful Post: