Hello,
I have designed a intermediate LED driver that sits between the led driver and decides which calls to pass through and whether to redirect them or not.
NEW VERSION 1.5 with loads of new features. Its HIGHLY suggested that you update! Improved device support and memory leak fix.
Basically, you can now turn off your signal light, make it flash blue instead of green, or whatever you wish. So far it's been tested on the titan and the kaiser, but should work on any device that uses ALLLEDMGR. nueLED renames allledmgr to LED2: and names itself LED1:. Please let me know if it works/doesn't work on your device.
Settings are stored in the registry, -1 means active and -2 means inactive, any other number is a redirect. To figure out new addresses, use diagnostic mode in settings.
Heres a short tutorial on how to make your signal LED flash blue:
Select the signal led from the list. It has address 8, mode 1.
Select the option "Redirect to LED Address", and select bluetooth LED.
Soft-Reset your device.
Your signal LED should now be blue!
If you use the cab version and decide to remove it, you need to set
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\AllLEDMgr]
"Index"=dword:1
and perorm a soft reset to re-enable the old led driver. Also delete the [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\nueLED] key.
You can find nueLED at
http://www.weienterprises.com/nue
Stroths has provided a cab version for your convenience : see
http://forum.ppcgeeks.com/showthread...618#post189618
Special thanks to stroths for figuring out how to package this into a simple cab.
A program to help you control your leds, nueLEDControl is also included. The syntax is relatively simple, i.e. nueLEDControl "address" "mode".
If you appreciate nueLED, donations are welcome. Comments, bug reports, etc. are also welcome.