[SOLVED: nueKBLight] Quest to modify the timeout for hardware keyboard.

[Cicatrize]

Yeah, both PE Explorer and Reflector only handle managed code. If these DLL's were written in .NET, I'm pretty sure either of those would have disassembled it.

I think what stroths is suggesting may be a possibility, but will take more time, as I'm not exactly sure how to speak to the LED DLL's. I may have to get with no2chem on this one...

[no2chem]

Originally Posted by Cicatrize

Ok...I'm going to do this. It's probably going to take a while, but it will happen. Everyone knows the keyboard backlight goes out after about 6 or 7 seconds, and it's very frustrating. If there was one thing I could change about the Touch Pro, this would probably be it. So, let's get this project rolling...

I'm fairly fluent in VB and C++, so as long as the alleged system dll's that control these lights are coded in one of these two languages, I could, in theory, recode and compile with the proper tools. One of the following needs to happen:

1. Someone with a dll/exe decompiler needs to decompile the code and send it to me.
2. Someone needs to donate enough money to pay for a decompiler license (not cheap, $100+)

Since 2 is unlikely to happen, please let me know if you have access to a decompiler.

I think there are further possibilities as well, but I don't know. I haven't seen this talked about before. If you have, please chime in as well.

i'm aware of these issues and they should be controllable with next build of nueROM, along with some mappable keys.

[no2chem]

Originally Posted by mdodge

I only have PE explorer and reflector (which is free btw). I tried the following:

IL
MC++
C#
Visual Basic
Delphi
Chrome

I'm sure a way exists to do it but I'm not an experienced in decompiling but thought I would help in anyway I could, cause this problem drives me nuts lol

And I'm sure a new driver could be introduced by someone with the know-how. But without seeing the current structure, source of the dll's, I would assume it would be much harder to make one. Kind of like programming in the dark.

Drivers are not written in C#/.net for performance reasons, and no C++ decompiler exists (well, that works well anyway) for ARM. If you are going to attempt to modify the driver, you need to have a clear understanding of ARM assembly, and a resonably clear understanding of Win32 and the WinCE driver model. Even with that, it still takes a bit of creativity to both read the obscure driver code (which I don't know, seems that HTC intentionally obfustacates, at times) - and to patch in what you want it to do in the limited space you have. As stroths mentioned, I wrote an intermediate driver for older, non-MicroP/pSOC devices, because it was appropiate given the limited amount of space, however, IMO, this isn't the best approach with the new devices.

Either way, there is no way to just "plop" your own C code and get the drivers to do what they want; that would be way too easy. Sorry, but if you want to do stuff, you'll have to get your hands grimy in assembly... Sometimes, it may take you an hour to just identify or find a part of the code you want to modify or understand! Reverse engineering is an art, which they unfortunately do not teach in school... fortunately, they do usually teach some kind of assembly (RISC assembly, typically, last I checked), so any experience in that would help greatly - it is just the different mode of thinking - (how do I change this code given that I've identified this routine, and these imports, and, i have 6 opcodes to do it in?) that will be the leap..

[Exil3d]

mighty one has spoken! TUM TUM TUUUMMMM! thxs for all the help no2chen in the past with our toys.

[mdodge]

Yeah I am by no means a programming expert or claim to be but was happy to see someone trying at least to solve this annoying issue. And now I'm even happier seeing no2 involved. Looking forward to the results!

[no2chem]

Well, i spent an hour or two on it -

I think the timeout might be set by the light controller, not 100% sure. Would a driver that keeps the kb light on whenver the keyboard is out be better?

[stroths]

Originally Posted by no2chem

Well, i spent an hour or two on it -

I think the timeout might be set by the light controller, not 100% sure. Would a driver that keeps the kb light on whenver the keyboard is out be better?

That would be pretty nice. Maybe you could make one of your nue control panels to control it as well (timer, always on, etc).

[hempy]

Originally Posted by no2chem

Well, i spent an hour or two on it -

I think the timeout might be set by the light controller, not 100% sure. Would a driver that keeps the kb light on whenver the keyboard is out be better?

That would be great!

I can't imagine what this community would be like without you.

[mdodge]

Originally Posted by no2chem

Well, i spent an hour or two on it -

I think the timeout might be set by the light controller, not 100% sure. Would a driver that keeps the kb light on whenver the keyboard is out be better?

+3

Thats how I had it on my mogul. I wouldnt even need a timeout at all really.

[eptd]

Originally Posted by no2chem

Well, i spent an hour or two on it -

I think the timeout might be set by the light controller, not 100% sure. Would a driver that keeps the kb light on whenver the keyboard is out be better?

YES!!!!!!