yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze Themes and Apps] yaneck:
Very good app, better than G-Light for me because it works fine with PocketShield
[Touch Pro, Fuze Themes and Apps] nik3r:
Use Advanced Config tool to set your desired keyboard backlight duration, set it about 1 minute and you will get about what you want ;)
[Touch Pro, Fuze Themes and Apps] adamkossoy:
Lumos

This does not work on my Fuze. This is what I get:

Error

An unexpected error has occured in LumosWizard.exe

Slect Quit and then restar this program, or select details for more information

This application requires a newer version of the Microsoft. Net Compact Framework than the version installed on this device.

I would have thought that the fuze has the most updated.

what do can I do?

Adam
[Touch Pro, Fuze Themes and Apps] noellenchris:
LevelSight changed his app into a service. Maybe he can shed some "light" hehe (had to say something corny) on how to make it into a service without signing. I think he explained it in a post furthur down on the page..Thanks and keep up the excellent work!

http://xdaforums.com/showthread.php?t=446434
[Touch Pro, Fuze Themes and Apps] nik3r:
adamkossoy:

You NEED .net framework 3.5 for most good tools out here. It uses a little more space than 2.0 but it's supposed to be faster and mainly allows devs more control in their programs.

http://www.microsoft.com/downloads/...49-3C6B-42F1-9FD9-0041345B3385&displaylang=en

Flash and tweak addictions is not yet cureable, we're all doomed :D

I will look at that later.
[Touch Pro, Fuze Themes and Apps] snudel:
i give it a try

but from what i can see it is already 1000 times better than the standard one, which changed my device into a flashlight in the dark... ;)

muffins via paypal will follow when the app will stay on my device for more than a week...
[Touch Pro, Fuze Themes and Apps] ivtec20:
Should this work on a Sprint Diamond running a custom ROM made using a kitchen found on another site? I'm trying to use it, but I just don't think it's working as intended. Sometimes, it seems like it's not working at all, it goes down to 2 or 3 in brightness and stays there. Other times, it seems to flucuate ramdomly. Like when I'm stopped in one location with a steady light source, it dims then brightens then dims again.

I've followed all instructions and unchecked the auto adjust backlight box on the settings. Is there some way to re-calibrate the light sensor itself? Or the sensorSDK file, can I replace it (in case the probem is with my phone/file)? Thanks.
[Touch Pro, Fuze Themes and Apps] nik3r:
Try to recalibrate the sensor again and make sure you use strong enough light source for the second part.

You can also enter calibration values manually on settings tab. I recommend setting sensor minimum to 0 and maximum to 700, that works fine in most cases as long as there's only linear backlight control.

If you have been playing with the manual settings and screwed things up a bit, you may also consider deleting the Program Files\Lumos\settings.txt file. That will force program to defaults and you will need to recalibrate again, this should fix most issues.
[Touch Pro, Fuze Themes and Apps] ivtec20:
I've tried to recalibrate a few times and it usually ends up with the same results. I feel like the program isn't starting up after soft reset (yes, the file is in the startup folder) or my light sensor itself isn't working properly. Do you know of a way to recalibrate the light sensor itself? Thanks.
[Touch Pro, Fuze Themes and Apps] norkoastal:
Whats the easiest way to remap the launch of this program to the PTT key on the phone? I dont use the MSVC program which is currently launched in the NATF ROM.

Thanks!
[Touch Pro, Fuze Themes and Apps] TheMostToys:
This is truly unfortunate. I had very high hopes for LUMOS. I've been a solid contributor to the gLight project, but it's progress slowed so I returned to the built in auto adjust. LUMOS seems much more efficient (one of my problems with gLight) but I occasionally use Opera (for good or bad) and I can't afford to have by backlight stop auto adjusting randomly (always at the worst possible time.) Oh well, the built in still wins :( the quest continues.

I am impressed with your approach, so far it sounds like the best potential solution. Keep up the great work.
[Touch Pro, Fuze Themes and Apps] nik3r:
There are still a few versions to go, don't give up your hope ;)

But right now I did my best and need to focus my efforts on school again for a while, I may get back to this later next week for v09 but don't expect the release until the next weekend.

If you read this, try to put the file attached to windows\opera9\ (backup your original first). It may fix your issues with Opera but I'm not sure.

You can create a shortcut of Lumos.exe itself and put it to windows\start menu\programs somewhere. Than map it to your key, it will work as a toggle on/off for the auto backlight.
[Touch Pro, Fuze Themes and Apps] thx1200:
I haven't noticed this problem myself, but it is possible to have a process that WM (or Opera, for that matter) will not kill during normal operation. I thought Lumos already did that (all it entails is having all your windows hidden). I've written several "pseudo-services" that way and never had them close no matter what I was doing. All I had to do was programmatically hide the primary HWND and the app was forever completely ignored. This is different from minimizing. Minimized apps can still be closed by WM memory management (and, presumably, Opera). Commonly, S2U2, PocketShield, and other screen lockers use this approach.
[Touch Pro, Fuze Themes and Apps] thx1200:
I think a GetForegroundWindow() option would be great.

As for the time profiles, you make a very good point. May I suggest something that is hopefully smaller and less performance impact?

It would be great if there was a way I could SendMessage to LUMOS to have it reload the settings file. This way, if I write an external app that makes changes to the LUMOS config, I can just SendMessage LUMOS after the configuration change and there's no apparent interruption to the automatic backlight adjustment and also a lot less CPU overhead compared to killing LUMOS and launching it again.

I could be wrong, but listening for a custom message in the window message queue should very low overhead, since I know you are very concerned about performance.
[Touch Pro, Fuze Themes and Apps] nik3r:
Lumos actually doesn't have any window or anything visual at all, I don't get how can Opera *sometimes* just kill it.

This is what I've done initially and I thought it will be fast but the idle CPU usage raised by about 50%, can't explain this. I eliminated all methods of communication with the process, messages, registry, storage, with any of these active, CPU usage couldn't fall below 0.10% in idle. After all that I settled on just killing the process when the need arises.

As for the GetForegroundWindow(), I said I will add this but this will get me hwnd, then I need to get name from hwnd - two succesive pinvokes.

What I now use uses just a single pinvoke and looks directly for the window name. Plus getforegroundwindow window will probably get child windows as well and thus any dialog window will bypass the rule.

Perhaps I can first search for the window using current method and then check which hwnd is in foreground and cross reference. And also add a switch to optionally chose to do this doublecheck whether the window is active or not (and save the additional CPU cycles if you don't desire the feature or it causes problems in teh apps you're using).
[Touch Pro, Fuze Themes and Apps] willybilly:
So far LUMOS v08 works very well on my TP.

It's been 8 hrs since last charged and my battery indicator still showing 98%. Of course with some sms and on standby mode. I am very happy with it.

For the interest of everyone the setting I configure:

Use on AC power : On

Min Applicable backllight : 2

Max Applicable backlight : 5

Sensor min : 0

Sensor max : 751

Sensor polling interval : 1500

Tolerance threshold : 1

Force BL=0 : 1

And lastly thanks for the apps.
[Touch Pro, Fuze Themes and Apps] :
The battery indicator isn't the most reliable.

After 8 hours your battery surely has NOT 98% left.

I experience this error, too. Just let the device running for some minutes and you will see how fast the battery indicator will drop..
[Touch Pro, Fuze Themes and Apps] kanthai:
Hi, I'm very interested in your app but when I installed it on my X1, It crashed.

I got "LumosWizard.exe TypeLoadException" when trying to run Lumos.exe or LumosWizard.exe. Furthermore, when I soft-reset my X1, I got "No configuration file found" on startup of Lumos.exe.

Additional Information:

Sony Ericsson XPERIA X1i running on WM 6.1 Pro

.NET Compact Framework 3.5 Installed

Stock ROM + Touch HD CABs

Can you point me out please?

Thank you,

Kan
[Touch Pro, Fuze Themes and Apps] nik3r:
X1 is possibly using different API than Diamond, raphael and Blackstone, honestly I don't know. I only included HTC specific API calls to keep Lumos lightweigt. Since the X1 calls should be very similar I may build a version specifically for Xperia later. I may contact you later for testing, but don't expect this any time soon, a week at least, I have other projects that need more attention atm.
[Touch Pro, Fuze Themes and Apps] kanthai:
Thanks, nik3r. That was fast.

As X1 are very similar to Blackstone (They both have the same chip, motherboard and screen), I take for granted that Lumos will work on my X1.

If I can be any of help, please let me know.

I will looking forward for this.

Thanks!,

Kan
[Touch Pro, Fuze Themes and Apps] :
Thank you for your program!! It is perfect. Htc should have this from the begging ..
[Touch Pro, Fuze Themes and Apps] jonnythan:
I'm not sure if this has been mentioned, but, while Lumos is very good, it kills my battery life.

And after I uninstalled it, the built-in backlight auto-adjustment stopped working. Now I'm just screwed :(

Any tips?
[Touch Pro, Fuze Themes and Apps] karloe:
Strange, my battery life improved...

The easiest way to get the built-in backlight back is a hard reset :p

(or you could read the first post or do a search :cool: )
[Touch Pro, Fuze Themes and Apps] jonnythan:
I was trying to avoid doing a hard-reset. That involves about an hour of follow-up work.

Is there something else I'm missing?
[Touch Pro, Fuze Themes and Apps] sm8ckd0wn1:
Consensus?

I commend nik3r's work on this. I'm really considering installing this on my Fuze. I've read the entire thread and I get a lot of mixed feelings. The main reason I am considering installing Lumos is the extended battery power on my Fuze. However, I see in this thread that there are instances where there is not much of a difference on battery life. And there's also the risk of installing it and then having it crash during installation and then having to hard reset it (while losing all your files if you don't back it up).

So I'm just wondering what's the general consensus with Lumos? Does it really make a difference on battery life?
[Touch Pro, Fuze Themes and Apps] pazookie:
sorry i didnt read through the whole thread i was about to goto bed and went to set some exceptions and saw 3 options in the drop down menu..PRG/CLS/CLP ..what might these be..? and also you can change the value (first box on the left) up or down what is this?
[Touch Pro, Fuze Themes and Apps] nik3r:
I be forever damned if Lumos will directly cause something that requires a hard reset of your device!

The comment before was obviously a joke, because hard reset indeed is the fastest way for a total newbie to get the default factory behaviour. Shamefully this is the same thing as claim that all you need to do if your Windows PC gets screwed is to do a clean windows reinstall. You see, that will work always, but it doesn't solve the issue, it just shows your incompetence to solve simple problems the easy way. Like killing a fly with a napalm strike :D

If you uninstall Lumos, obviously the built-in auto backlight remains in disabled state, because YOU had to disable it MANUALLY before even getting Lumos to work in the first place.

So just go to Start - Settings - System Tab - Power - Backlight Tab

and tick the Auto adjust backlight feature, then hit OK and the old HTC backlight should be back in place, if not do a soft reset.

If it's not fixed, it's just you and only you!

Lumos doesn't change a thing in your system, there are no dependencies to system with the sole exception of \Windows\Startup entry.

Lumos is now spread all over the internet (not by me), it has been downloaded by almost 2500 people only on xda-devs, and so far there hasn't been a single complain except for people who don't know their way around the system and are confused. And even they would be fine if they just read the first two posts and FAQ.

If you don't like Lumos, don't use it and move along OR tell me what you don't like and I will consider changing it if your suggestion is reasonable.

It's that simple.

Now if you excuse me, I have some programming to do...

NIKER OUT

PS:

PRG = detection by program window name

CLS/CLP = detection by class name or both class and window name

stick with PRG for all usual usage

.. and the numeric up and down on the left is the backlight you want to force for the application you are adding ;)
[Touch Pro, Fuze Themes and Apps] Magicdead:
Adobe Acrobat Reader and Lumos

i have 2 problems with Lumos on my Blackstone.

It concerns Adobe Reader for Pocket PC 2.0 (didn't test it with the LE version).

First of all, as the window title changes when you open a pdf, i had to use classes. So I made an Exception for AfxFrameOrView42u, a subclass of the adobe reader process, as the process itself always uses another class descriptor (like Afx:89e593b6:b:7c070384:44:7c09bc34 with the hex-encoded data being different each run) and the FrameOrView one is always the same. But it never changes the brightness when i run Acrobat. i tried it with different brightness settings (1,5 and 10) for the exception

And the second problem, which might be related, even though i set the exception to "CLS" and pressed "Save&Apply", when i check back to Lumos wizard, it's set to "PRG", so it seems like its not saving the setting correctly.

I also tried "CLP", but to no avail.

Help would be greatly appreciated :)

It works fine for programs that don't change the window title, though. And if this little bug could be fixed, i'd love it ;)

[edit] never mind the title of the post, was testing some settings with lumos and used the edit-field to write down some temporary taskmanager stuff about the classes
[Touch Pro, Fuze Themes and Apps] nik3r:
I will add the PRG->CLS edits to my already long todo list. I must admit I never tried doing that :D
[Touch Pro, Fuze Themes and Apps] JoeSchmoe22:
PhoneAlarm + Lumos = not so good

I would like to use both PhoneAlarm and Lumos, but each time I have a profile change from PhoneAlarm, it seems to lock-up or freeze Lumos. I can see that Lumos is still running via Task Manager, but something that PhoneAlarm does on the profile changes stops Lumos from working. Is there a way to reload the Lumos settings using a command line? If so, I can force PhoneAlarm to run the command line to reload the settings at each profile change.

Can you help?
[Touch Pro, Fuze Themes and Apps] nik3r:
I need you to try something.

When the lumos gets stuck because of PhoneAlarm, look to some task manager for its CPU usage, Lumos shouldn't have 0% all the time.

I myself experience similar issue on the latest PDAVIET ROM. Lumos goes to hibernation on standby and never comes back on, CPU usage stays on 0%. It takes some time for this to happen and I can't do much about it without being able to reproduce it on debugger. And I can't quite debug the app when the device goes standby and disconnects from activesync :confused:

Anyone knows a registry hack not to disconnect active sync connection on standby? It can be done for wifi I expect there's a trick for cable too...
[Touch Pro, Fuze Themes and Apps] jonnythan:
Wow. I report a problem or bug with your app and you respond by calling me incompetent.

Of course I reenabled the auto backlight feature. I soft reset, then enabled it and soft reset again, then disabled it and soft reset, etc etc and it still doesn't work. I've checked and even restored all the backlight registry settings.

It worked fine for weeks before I installed Lumos.. and in the two days I tried Lumos I didn't install or remove anything whatsoever. Auto backlight still doesn't work.

I'll probably end up doing a hard reset, but I just wanted to check with people here to see if anyone else has experienced this and if anyone has a potential fix I haven't already tried repeatedly.

Well, now you have had one complaint from someone who knows his way around the system :) Nothing in the first two posts or FAQ address this issue.

I quite like the program, in fact. I really want to keep it.. I'm even considering keeping it despite the battery issue because it has the "Force BL=0 below" feature, which is fantastic.
[Touch Pro, Fuze Themes and Apps] nik3r:
I still insist this can not be caused by Lumos. Enough to know that if you don't disable the built-in backlight manually, Lumos can't even change the backlight. Even if you enable the HTC auto-backlight while Lumos is running, it will override Lumos settings and take over the backlight completely.

Lumos doesn't change your registry settings or any system files. It's like saying that running Notepad can uninstall your videocard drivers xD

I'm not saying you're incompetent but this simply has to be caused by something else not directly related to this app. Try to install Advanced Config, there's a backlight polling interval for the built-in backlight, maybe something disabled it or whatever, but Lumos can't do this it has to be some other application or some settings.

And the battery issue is weird, I'm using Lumos ever since v01 and I can last 3 days and still have ~25% battery left. And I chat on wifi a lot.
[Touch Pro, Fuze Themes and Apps] JoeSchmoe22:
Lumos is NOT at 0%. In fact it's registering mostly in the 2.20% to 2.46% [sometimes it drops down to 0%, but only for a split second]. During this time, it appears that the back light setting is being overwritten by the PhoneAlarm back light setting.

I have now tried one additional thing, I changed every PhoneAlarm profile to "Leave Unchanged" for the back light setting, hoping to not disturb Lumos, but that doesn't work either. Now when it changes profiles it stays locked at whatever the last back light setting that was determined by Lumos.

If you could write a command line that simply reapplies the existing settings, this would stop this problem because PhoneAlarm could run this command line AFTER the profile change. Also, other people have this same problem could use Mort Script to run the command line as well. Just a thought. :rolleyes:

Thanks for the hard work!!! :D
[Touch Pro, Fuze Themes and Apps] jonnythan:
OK, that's fine. Curious, though, don't you think?

If I do end up doing a hard reset, I'll see if I can recreate the issue by installing and removing Lumos before I do anything else.

Thanks.
[Touch Pro, Fuze Themes and Apps] nik3r:
Please do, with the same ROM you're using now, I too wonder :rolleyes:
[Touch Pro, Fuze Themes and Apps] nik3r:
Ok looks like I fixed the random backlight freezing issue. After all it wasn't a bug in Lumos but in the HTC libraries. When Lumos read the sensor values before the initial HTC init is completed, sensor would keep returning 0 until you restarted the reading connection. I solved this by making a new file LumosStarter.exe designed to counter this issue, detect stuck sensor and postpone the start of Lumos.exe until the startup is complete if necessary. This file can also be used to restart Lumos without any visual feedback at any point (especially useful for PhoneAlarm users). There are still issues to be adressed and I won'T be online until Sunday, so this will delay the v09 release a bit, patience.
[Touch Pro, Fuze Themes and Apps] mataempat:
I've installed v08. works like a charm. i will test battery life in the cople of coming days. thank you for the great work. you're the man. small donations will come soon so that you can buy muffins.
[Touch Pro, Fuze Themes and Apps] nik3r:
Lumos v09

Lumos v09 has been released

This version introduces a few new minor features but focuses mainly on fixing most (if not all) known bugs and improving reliability and ease of use for new users. CPU usage and battery life should be the same or little better than v08 but the difference is nominal.

My battery can last 4-5 days now with low usage :)

Main new features:

- exceptions can be set to detect only active window (both modes have similar CPU usage)

- installation will automatically disable the built-in HTC auto backlight

- uninstallation will return auto backlight to its former state

- LumosWizard can return backlight to former levels upon exit

- setting tolerance won't prevent backlight from going to lowest and highest settings

- added LumosStarter.exe that (re)starts Lumos service without any feedback

Main bug fixes:

- fixed bug when Lumos got stuck on device softreset due to a bug in HTC sensor libraries

- fixed bug that would set AC power brightness on switch from cable to battery even if disabled in settings

- fixed glitches while deleting and saving multiple exceptions

- fixed erratic backlight control during operation of LumosWizard

.. and many more I forgot to track :)

If you like and use Lumos, you are welcome to donate.

Enjoy the new version!
[Touch Pro, Fuze Themes and Apps] johanromijn:
Tnx, I'll try the new version right away!!
[Touch Pro, Fuze Themes and Apps] snark_be:
Installed, working fine for the moment (as expected).

Thanks for a nice piece of software, nik3r!
[Touch Pro, Fuze Themes and Apps] tyguy:
@nik3r

Quick (and perhaps stupid) question:

Default backlight level ranges from 1 - 10.

If I set i.e. 1 - 100 would this work in a way that I get a higher granularity between the adjustments OR would it be just useless?

Thanks

Ty
[Touch Pro, Fuze Themes and Apps] nik3r:
The backlight values in settings are just a limit beyond which the backlight cannot go, the real maximum and minimum are read directly from device so no, this wouldn't change the granularity as the device don't support more backlight states.

You can however set some bogus sensor maximum value to get more sensitivity in darker places (like 500 instead of ~750 that would give you proper sensor calibration). :)
[Touch Pro, Fuze Themes and Apps] fmcastro:
In Call Backlight / Sleep

Hi, I've searched the entire thread but couldn't find anything related to in call settings / actions.

As I see, the factory implementation of auto-sleep (screen off) based on the light sensor that happens when you receive or place a call is really buggy. It doesn't work every time (for lots of different reasons) and I cant really accept the fact that a simple thing like that doesn't work.

Have you taken a look a that? Do you think you could improve the usability of the auto-sleep using the light sensor?

Maybe another thread for that...

Thanks
[Touch Pro, Fuze Themes and Apps] nik3r:
I never really understood how's that supposed to work, because the light sensor reports "0" most of the time you're indoors it just can't work the way it was meant to.

It's supposed to switch off the display when you cover the sensor with your ear, right? But that can only work in good light conditions, the idea itself is wrong when we're dealing with a light sensor with such a poor sensitivity in the dark, no wonder it's behaving strange, no software will help here unless you combine G and light sensors, oh and you need to be a bit of a seer too :D.
[Touch Pro, Fuze Themes and Apps] tyguy:
@nik3r

Thanks for the quick response. actually I set mine to 10 (min) / 400 (max) which works so far best for me combined with apolling of 500 and change rate of 1000 (very smooth, nothing erratic).

@fmcastro

That's a totally different can of worms. I read somewhere here that a polling set to > 10000 (10-thousand) or even higher will not prevent BUT delay the switch off in-call. It's buggy anyway IMO and has nothing to do with brilliant Lumos.