Re: Quest to modify the timeout for hardware keyboard.
This is the one thing I would change also. I think with every other phone used, the keyboard/keypad was synchronized with the screen backlight. This seems very logical, I don't know why they would have the keyboard light go out so soon.
|
Re: Quest to modify the timeout for hardware keyboard.
This is prolly my number one complaint ATM with this phone...
|
Re: Quest to modify the timeout for hardware keyboard.
Subscribed!
|
Re: Quest to modify the timeout for hardware keyboard.
Quote:
|
Re: Quest to modify the timeout for hardware keyboard.
Just of note since I've been playing a little with this. The GSM version of the pro responds to the qkeytimeout reg key, but sprints does not. I tried to install some dll's from the gsm rom but it only disabled my key lights completely. But you may want to look at those to get an idea. I'm convinced its not hardware because of this.
|
Re: Quest to modify the timeout for hardware keyboard.
Quote:
|
Re: Quest to modify the timeout for hardware keyboard.
I tried a few programs to decompile it but was unsuccessful. Said there is no CLI header. I'm refering to Microp.dll and allledmgr.dll. I'm wondering if they can even be decompiled at all
|
Re: Quest to modify the timeout for hardware keyboard.
Anything can be decompiled.
What disassembler are you using, and what language are you trying to disassemble? If there's no CLI header, then it can't be .NET, which I didn't expect, but I guess that's the deal. All your decompilers must only handle managed code. Do you have access to a diassembler that will handle unmanaged or native code? EDIT: Now that I think about it, I'm not surprised if it's not managed code. Hell, they've been using these same DLL's for ages, most likely. Probably before .NET even became a programming standard. It's probably coded in old C++. |
Re: Quest to modify the timeout for hardware keyboard.
Quote:
|
Re: Quest to modify the timeout for hardware keyboard.
Quote:
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. |
All times are GMT -4. The time now is 07:00 PM. |
Powered by vBulletin® ©2000 - 2024, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com