Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
Known issues
- [Fixed] New icons are not working when TorchButton is installed to Storage Card
Todo
- Create an app to configure the registry settings
- See if support for Omnia Pro (B7610) is feasible (someone should send me the related dlls...)
- [Done] Add a seperate timeout for bright mode
- [Done] Add blink mode with bright led
- [Done] Use new icons provided by tnyynt
- [Done] Add support for Omnia (the one found here)
- [Impossible] See if it's possible to control leds seperately ('economic mode') Sorry, this is not possible. (Tech-talk: setting a single GPIO enables both LEDs. There doesn't seem to be a GPIO for each LED seperately.)
Wishful thinking
- Camera app to interpret the morse
History
Version 2.3
- Fix icons not showing in HTC Sense or WM 6.5 start menu when installed to Storage Card.
Version 2.2
- New icons for all TorchButton apps (thanks tnyynt!). These only work in WM6.5 and up. Older OS's will still see the old icons.
- Added registry setting to use bright setting in blink mode (see BlinkUsesBrightMode).
- Bright mode now has a seperate timeout, configurable in registry (see BrightModeTimeout).
- Added support for Samsung Omnia i9x0 devices (hopefully they all work). Thanks to raph/zemrwhite2/PaSSoA. Thanks to Chainfire for testing on his Omnia i900L.
- [edit] Shortcut names have changed. I found them nicer this way, no two-line icons. And the text is now also not cut-off when added as shortcut in the home screen.
- [edit] Improved handling of bright mode. It should stop immediately now when pressed again, instead of waiting for a 500ms interval. This makes BlinkUsesBrightMode possible combined with low intervals for blink mode.
- [edit] Soft-reset your phone after upgrading from an older version! Else the new icons will not show.
Version 2.1
- Bright mode is now support on the HTC HD2 (Leo).
- Added a one-time warning message when bright mode is used for the first time.
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Dont think about something. Untill i read your post. This could be handy sometimes. Thnx
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Great ! thanks
Have it on my Omnia and was hoping to have it for my future HD2 !
You're all welcome! Glad to hear you like it.
12aon said:
Awesome man I was just thinking how I missed that
Btw what's missing for bright mode to work? If I'm not mistaken there is a brighter mode just before taking a pic.
Click to expand...
Click to collapse
The mode is there, but it's not as easily called as it was on the Touch Pro. In fact I haven't found the API call at all yet. May need some hacking around the API to get that to work. The normal mode produces _quite_ the amount of light though, it's even more light than the bright mode of the Touch Pro thanks to the dual led.
Zero Masamune said:
Thanks! I was dissapointed that hTorch didn't work on the HD2 now I got this. Wonderful!
Click to expand...
Click to collapse
hTorch will work again once I update the C# wrapper to support the Leo, as hTorch makes use of my C# library. I'll do that somewhere in the upcoming week.
Great, works perfect ! Txs
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
kinnyfaifai said:
Can anyone confirm this don't burn anything out? On the X1 the light modules weren't heatsinked properly and caused vibrator motor to screw up after 15secs use as a torch.
Thanks!
Click to expand...
Click to collapse
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
NetRipper said:
I can't confirm it won't ever burn out. However, realise that enabling the LED is actually the same as using your camera with the lights on in the dark. This _shoud_ be possible for prolonged times as well.
Were you using the 'bright' setting on the X1? (If that's possible there.) That might explain it better... otherwise you could just send in the device for repair, as it's normal use of the device. Especially if it's after only 15 seconds.
Click to expand...
Click to collapse
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Heej nice, i come from oud-Beijerland
nice app, but bright mode doesn`t work for me..
NetRipper said:
Continuing my quest of using the LED as flashlight for my new HD2, I updated TorchButton to support the HD2 as well.
Dropped your keys? Finding something behind the bench? Performing surgery on a computer and need to find that jumper on the mainboard?
This is a simple application built for some HTC devices that have a hardware LED, normally used to take pictures in the dark. However I found the LED to be perfect to be used as a handy pocket flashlight.
Usage
There is no GUI for this application. Just start TorchButton to enable the LED on the back of your device. Start TorchButton again to turn it off.
Check out the readme if you're an advanced user and wish to change some registry settings, i.e. to allow a longer maximum time the LED is enabled.
History
Version 2.0
- Initial version with support for the HTC HD2 (Leo) (bright mode is not supported on the Leo)
Version 1.x
- Support for the Touch Pro
Click to expand...
Click to collapse
20mihalko said:
nice app, but bright mode doesn`t work for me..
Click to expand...
Click to collapse
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
ET said:
Isn't it clearly stated that brightmode doesn't work.......jeez....dude...read
Click to expand...
Click to collapse
sorry, my mistake
kinnyfaifai said:
It was a known problem that the LEDs weren't heatsinked properly on the X1 and there was a huge warning on using hTorch. I've not installed hTorch and never used the LEDs on my X1 as a torch cos of this oversight by the manufacturer. I do miss being able to use the LEDs as a torch though, it's very handy.
Click to expand...
Click to collapse
The vibrate function does not work at all on my X1 after installing and using hTorch. User beware..!
This is my next phone when O2 decide to put it on their shelves, and hopefully its built better than the X1.
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
l3v5y said:
Any chance of some source code?
I've been looking through the HD2 camera drivers, and have found a few things that should be the LED (can't test it as I have no device), but am wondering if it's the same method as yours!
Click to expand...
Click to collapse
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
NetRipper said:
Here are the important code snippets of the API that I'm using. The methods were pretty obvious (luckily).
typedef int (__stdcall *LEO_INIT)();
typedef int (__stdcall *LEO_SETCURRENT)(DWORD dw1);
...
LEO_INIT InitFlashLight;
LEO_SETCURRENT PMICFlashLED_SetCurrent;
...
hCamera=LoadLibrary(L"CameraPlatform.dll");
...
InitFlashLight = (LEO_INIT) GetProcAddress(hCamera, L"InitFlashLight");
PMICFlashLED_SetCurrent = (LEO_SETCURRENT) GetProcAddress(hCamera, L"PMICFlashLED_SetCurrent");
...
InitFlashLight(); // must be called before SetCurrent has any effect
...
PMICFlashLED_SetCurrent(0); // turns it off
PMICFlashLED_SetCurrent(1); // turns it on
There's also a PMICFlashLED_SetMode(x); but I haven't been able to figure out what it does. As far as I could see when disassembling it wants one parameter.
If you have any ideas on the bright mode, they'd be more than welcome. If you want the full source to make some modifications or to toy with it, let me know.
Click to expand...
Click to collapse
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
l3v5y said:
That's what I'd come to as a conclusion, so glad that works!
Is there any need to un-init the flash light?
PMICFlashLED_SetMode will probably need some playing around, though might enable your "bright" mode. Will have a play with that when I get an HD2!
Click to expand...
Click to collapse
There doesn't seem to be an un-init function. However, the debug console shows that it detects when the DLL is being attached to or detached from, so there's probably some cleanup code there.
I also haven't found any side-effects yet. TorchButton works fine even when the camera app is running. They don't interfere with eachother (other than toggling the LED to their own behalf). On the Touch Pro it wasn't possible to run TorchButton and the camera app at the same time. Not that I ever wanted to, but still.
In regard to that mode function. It must be for something. I tried using it in various ways already but it didn't matter. Maybe you'll have more luck
might be confused right now, but seems that when in camera mode, and battery is below 50% you cant use the flash - anybody know if this will affect the app?
haven't got my hd2 yet so cant help you out, but there's a thread under the Leo -- > Leo sub-forum
cheerios!
Hi,
I wonder if there is an application that will allow me to control the light in my apartment through bluetooth or wifi? Also wonder if there is any hardware that applying this?
Would be nice to control the light through my PDA
If this solution is already available, please let me know.
The hardware, I can probably build myself, but i dont know anything about programming.
So was wondering 1) what that light was called on the left side of the ear piece that lights up orange when charging, green when charged, and flashes green when you have a notification and 2) if there are any hacks to make it do different things...?
I tried searching for serivce light and notification light, but didnt come up with anything.
TIA
It would be called a power led or status led. You can change the notification settings but I don't know of anything else.
I was wondering the same thing. I am going to try nueled that used on my tilt a long time ago.
http://freewareppc.com/utilities/nueled.shtml
we'll see what happens.
I think it will work as that hack is supposed to work with any htc phone that uses AllLEDManager to control LEDs and our rhodiums do in fact use allLedManager. Im gonna give it a try as well. See what happens.
K it works... Unfortuneately, our LED on the phone near the ear piece is only green or orange from what I can see. For example, we dont have a bluetooth light that lights up when connected to bluetooth.
What I've been scouring XDA and the rest of the web for is how to turn the Wireless Network Status function of that LED on... I've searched & posted here and a couple of other forums with no luck. Really, that's the only thing I miss that my hTC Kaiser and most of my previous other devices had... ?
I hate having to wake my device up just to see if it (a) is even on (device is totally dark in standby), and (b) am I still in range for a signal *blinking green or solid red/orange*.
I've even gone through the registries of both my Rhodium and my Kaiser to see if there are any differences between the LED entries I could find... if anything, the Rhodium has a few entries in it that the Kaiser doesn't. *heh*
I have a TP2 with Verizon's 6.5 upgrade... nueLED didn't do squat for me... Anyone have any tips?
magna131 said:
I have a TP2 with Verizon's 6.5 upgrade... nueLED didn't do squat for me... Anyone have any tips?
Click to expand...
Click to collapse
Disregard...nueLED doesn't work, but I figured how to change the settings in the registry.
Hi there people, does any one know if u could make an app to get the leds beteende the buttons to flash on new sms and so on?
+ 1 to this question... i know that "LightFlow" appwill allow the keypad leds ( the two between the three keys ) to lit up Constantly.. but "Led Me Know" app does not even find the leds to control.. Its something with 2.3 android, and LED codes..
Hopefully Led Me Know will support this at some point.. or some other app ofcourse
Either way, im looking forward to it.. as the Arc's Notification led is almost useless if you lay your phone down..
But i quess this post should be in http://forum.xda-developers.com/forumdisplay.php?f=1182
Hello to all, am going to ask if anybody of you have a problem in TPs Touch Capacitive Pad? I used this app
Nav Debug Tool by HTC
http://forum.xda-developers.com/showthread.php?p=2511016
To check out this multi touch stuff in my TP (though I know before that it has a multi touch feature, I just want to check if it's working properly) but it seems that the pad has a problem. The problem was sometimes, it can register my touch and most of the time, not.. sometimes it can register the multi touch, and most of the time, not .. even the nav wheel has a problem which doesn't register the rotation most of the time. Is this a common problem in TPs or even Diamond??
I even use the signed os WM6.1 but still has a problem.. so I wonder if any of you guys having the same..
thanks!
It's been happening to me for about a year already as well. Seems like it's just defective. It resets thought after sleeping the phone and waking it. I'm not sure if it was because I used to use Sensor scroll or it's a little scratched up.
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
R^7Z said:
I hear the d-pad was a good conceptual idea but that is about it... I personally don't use the d-pad at all because of this, much less any of the buttons (to include the power button). On the other hand, from what I can tell about the d-pad "sensor" from using the NDT(Nav debug tool), it does seem pick up points but it seems to not like repetitive touches. It almost seems like the sensor overloads the processor to the point that it fails in terms of keeping up with the actual location that is being touched; if that makes any sense?
Click to expand...
Click to collapse
that made sense but why would HTC permit a buggy front pad???
You know, it seems many phone brands/cooperations come under fire due to lack of something or another; maybe proof of concept? Perhaps the debug tool is to blame? Or even the sensor degradation over time? One can only speculate so far before it becomes a volatile thought... Again, I point out the idea being good, conceptually. So, I don't know where that exactly puts us as being end users? Then again, I've never really had a decent experience with phones, much less with newer phones; my thoughts and expectations may be slightly on the negative/lesser side of things because of this.
I have the same issue. I used to use GScroll to flip pages in e-books, but finally it got so buggy I had to dump it (other GScroll features were almost impossible to use). I've used NavPad DBug. What I do find is that running the compact heaps command of SK Tools will temporarily fix things, at least most of the time. When I have NavPad DBug running, if it's logging compact heaps will clear out the traces. Somehow or other, it cleans things out when the nav pad gets confused or overloaded with inputs. But even compact heaps doesn't work all the time.
It would be sweet if the capacitative area really worked, but unfortunately it appears to get worn out about the time that you figure out all the things you can do with it. Lol.
Edit: I wonder if the device has problems distinguishing a single touch of your finger vs. several touches. That could really screw up the function of the device.