[Touch Pro, Fuze Themes and Apps] nik3r:
FAQ:

What exactly is the calibration for, backlight is still the same after calibration?

The calibration ensures Lumos can detect the detection range of your light sensor properly and lets you set minimum and maximum possible backlight easily.

It has 4 steps:

1) Minimum value the sensor can read (probably 0 on all devices)

2) Maximum value the sensor can read (expect this to be something around 1400), you need to use a light bulb tor this step.

3) Minimum brightness you want. Lumos will calculate everything with minimum value reported by your device, but it will not let the backlight go below this value. (like if you want to have backlight 2 in shade because 1 is too dark for you)

4) Maximum brightness you want. Lumos will calculate everything with maximum value reported by your device, but it will not let the backlight go above this value. (You may notice that backlight level 7 and 10 is a little difference and can be both read in direct light, however if you limit the maximum to only 7 here, you will save a lot of battery)

5) After you are done with the calibration, you can review your setting on the settings tab and click 'Apply+Save' to exit LumosWizard and actually start Lumos service. There is no auto-backlight while the configuration Wizard is open, it defaults at level 6!

How program exceptions work?

- Switch to the Windows tab and start for example TomTom, leave TT and click it's name in the window list, then specify the backlight you want for this app and tap Add.

- If you disable "Exc. for active window only" on settings tab, you need to specify exact window name and exception will be triggered even for inactive application (minimized for example).

- If you activate "Exc. for active window only" on settings tab, you only need to specify part of the window name in exception settings (useful in case part of the window name changes). If the window name is "AdobeReader - document.pdf", only add exception "AdobeReader -". Be aware enabling this option increases CPU requirements of Lumos by about 20% (means roughly 0.06% total for slow diamonds).

Note that you will probably need to enable "Exc. for active window only" on settings tab for exceptions to work on WM6.5.

How to set a program exception step by step?

1. run lumos wizard

2. switch to the tab "windows" (the last one) and let the wizard run in background

3. run your program(s) you want to add

4. close the program(s)

5. switch back to lumos wizard -- voila, all the window names you visited are there!

6. tap the program name you want in the window list, it will switch you to the "exceptions" tab and fill the form for you

7. set the backlight level you want (1-10) and tap add to exceptions

What is a Relative Exception?

- relative exception does not force one specific level but rather amplifies and attenuates normal auto-backlight behaviour for the application in question.

Consider this scenario:

- my allowed backlight ranges in levels 2-7
- I want to use a navigation app in car and it is kind of difficult to see on sunlight, shades in car would read for level 3 or 4 and that is not bright enough
- I can either create an exception and force backlight all the way to 7, but that might not be optimal on battery
- therefore I create a Relative Exception of +2
- for the navigation application if the backlight would normally be set to 3 by Lumos, it will be amplified by two to 5. What would normally be level 6 will get amplified to 7, since that is my maximum level.

- You can also use negative values in Relative Exception to decrease the backlight for certain app by certain amount to save battery for example.

How backlight modes work?

- Backlight modes are individual equations used to determine proper backlight level from current sensor value.

- Linear - this mode is equally sensitive in dark and light environment.

- Root - this mode is more sensitive in dark environment and is best suitable for human eye and therefore default.

- Quadratic - this mode is more sensitive in light environment.

- Custom - this mode features customizable graph, you can draw a graph yourself with stylus or click on the blue area under each level number to input border sensor value manually.

Levels outside your min-max boundaries are hidden.

- Note that using custom mode do not affect CPU requirements in any way.

Commandline switches?

- There are 4 switches that can be used

"+" will increase backlight by one

"-" will decrease backlight by one

"s" will run normal Lumos operation without restart prompt after +/- tasks are completed

"q" will quit Lumos after +/- tasks are completed

Example to increase backlight by 3 and disable automatic:

"...iles/Lumos.exe" +++q

My *insert a game using G-sensor* is lagging strangely, can I fix it?

- guys from HTC thought it would be a cool idea to tie all sensors together in a framework, unfortunatelly it appears that when one program locks a sensor for read, other sensors may get locked as well on some devices. There is only one solution that will de-lag such game - not to use the sensor while it runs.

- Create a non-relative exception for the game in question and your lag should go away.

Backlight is not changing at all, it's the same all the time?

1) go to Start - Settings - System tab - Power - Backlight tab and DISABLE the 'Auto adjust backlight' feature.

2) close the configuration Wizard with "Save+Apply" button, auto-backlight service is disabled when you are configuring Lumos or when there is no configuration specified.

Program won't start at all?

You NEED .NET 3.5 Compact Framework Redistributable. It is faster and more stable and offers more stuff for developers than the 2.0 you probably have. It is rumored it may even make your device work faster (or at least .NET based apps).

Download it HERE (only about 3MB on device, don't be scared by the installer size as it contains support for more processors)

LUMOS CHANGES TRACKER:

(changes prior to RC1 version dropped)

! non linear backlight in the GLight style for people all over the net who are demanding this

! exceptions now need only part of the window name in "detect only active windows" mode

! recalibrated sensor readings for more sensitivity

! fixed bug in custom graph mode

! faster loading

! dropped DIM_TO_MINIMUM_PLUS_ONE_BELOW option

(below only in RC2 version)

! fixed custom mode alignment

(below in 1.0 Final)

! add support for relative level in exceptions

! add support to keep alive only as exception

! add command line support (change level & quit, +, -)

(below ideas for future development)

- add support for alternative backlight handling (WM default without HTC drivers)

WIZARD CHANGES TRACKER:

(changes prior to RC1 version dropped)

! support for setting linear, quadratic and root/logaritmic backlight

! support for custom backlight mode with interactive graph

! support for changing keyboard backlight delay on RAPH

! improved max/min detection in wizard

! forcing consistency between settings and graph plotting

! switching language in flight

! faster loading times

! support for language packs

! smaller text to allow better translations

! bigger tabs for better finger friendliness

! dropped DIM_TO_MINIMUM_PLUS_ONE_BELOW option

! fixed minor flaws from beta2 connected with translations

! improved settings tab scrolling redraw speed

! settings tab will back off from deploying soft keyboard

! added new languages: Bulgarian, Czech, Francais, Japanese, Nederlands

(below only in RC2 version)

! fixed Window detector taking you to the Mode tab instead of Exceptions

! fixed settings tab layout width

! added another failsafe mechanism against saving invalid min/max backlight and polling interval

! added warning message for options with potentially negative effect on battery

! added new languages - currently Bulgarian, Czech, French, German, Greek, Japanese, Dutch, Polish, Russian, Sim./Trad. Chinese

(below in 1.0 Final)

! set "BL=1 below" option to be relative to the sensor minimum

! set calibration to disregard sensor minimum 0 until the driver is initialized

! add support to release sensors on active exception

! add wizard warning if built-in auto backlight currently overrides Lumos control

! ability to recognize missing sensor drivers and the need for Backlight Hotfix package

! add support for relative level in exceptions

! add support to keep alive only as exception

(below ideas for future development)

- support for forced "on wakeup" backlight level

- = bug / missing part

? = possible bug/not able to reproduce/not verified/idea

* = in development

+ = fixed bug / completed part

! = fix/feature included in released version

NOTES:

Please disregard the hacks from previous versions and always set your sensor minimum and maximum to real values (0-xxxx)! Some sensors might have different minimum than 0 - this is a hardware defect and you need to use the defected value for Lumos to work correctly.