Sorry posted this in the wrong area at first...
http://forum.xda-developers.com/viewtopic.php?t=14416&highlight=keyboard+light
this post talks about how to do the change on a Blue Angel, how do we do this with a Wizard? It has a similiar registry (HKEY_CURRENT_USER\ControlPanel\Backlight) just no file called "QKeyLedTimeout" in there, is it located somewhere else in the wizard? Mad Monkey Boy has this same thing posted on his tips site but again there is no "QKeyLedTimeout" in my registry. This keyboard timeout after 5 seconds or whatever is driving me crazy!
This patch doesn't work on Qtek 9100 with I-mate ROM...
I noticed as much, is there a similar hack we can do on these things?
i think this is everyones dream!
not sure what the developers were drinking when they set this time limit
will be waiting to see this thread with a successful answer too!
I wonder if this key would work if added to the registry? Although its easy to do this on a PC I'm not sure how you add keys on a mobile device, anyone have any ideas?
does not work on dopod838 wwe.
installed the DL_ed cab file fr madmonkeyboy, this creates the registry line with setting 30, but mine still goes off in 3 sec.
This doesn't work on QTek 9100 with the original QTek ROM either.
The way I see it, there are 5 possible ways that the keyboard backlighting is handled...
A. It is read from registry every time you open the keyboard. If this is the case, CeRegSpy should be able to detect it - even if the key doesn't exist. I have not tried this (yet).
B. It is read from registry at start-up. If this is the case, and it executes before any other programs - perhaps even as part of a device driver - I don't know if there's any way to find out what registry key it tries to read from. Checking out the device driver might help, but I have no idea which file is the external keyboard device driver
C. It is part of the LEDs interface. A programmer on here should be able to help out in that case. The LED interface is well-documented and there are examples here:
http://www.pocketpcdn.com/articles/led.html
With those examples, it should be easy to determine how many LEDs there are, and turn them on/off - or make them blink. Any programmers up to the task ?
D. It is hardcoded in the driver or a support file. This would mean you would have to edit the driver/file. Not impossible, but far from user-friendly. Again, you would need to know what the device driver or support file is, first - and -then- you would still need to reverse-engineer it.
E. You won't like this one: hardware-controlled. By this I mean a simple SMD circuit or even controller chip which turns the light on as soon as a connection is made, runs for 5 seconds, and then stops. The time, in those cases, would typically be controlled by means of a tiny resistor. Anybody want to void warranty, open up their device, and go about soldering? I didn't think so.
I hope it's either A or C.. I'll give A a try, myself, after lunch. If it's not A, then a programmer might help out with checking whether it's C (a simple interface with on/off checkboxes for each LED device should do the trick!)
CeRegSpy unfortunately fails for me ("Exception in DllStartTracer()"), but if it the author/publisher can help me get it working, I'll post findings eventually.
Hmmm, I'm using the Wizard ROM on my BA and it has that registry entry in location mentioned above. I set it to 30 and it works.
BlueAngel and Wizard are quite different devices, though
That said - which Wizard ROM had the entry? My Qtek 9100 doesn't have it, I tried adding it and seeing if it'd work a few days ago - no go.
ZeBoxx said:
BlueAngel and Wizard are quite different devices, though
That said - which Wizard ROM had the entry? My Qtek 9100 doesn't have it, I tried adding it and seeing if it'd work a few days ago - no go.
Click to expand...
Click to collapse
True, they are different hardware.
I'm not sure which device the BA-Wizard ROM was pulled from...
You can change the backlight setting in the control panel right? That value has to be stored somewhere in the registry I think...
There is no settings for the HTC Wizard keyboard backlight in Control Panel. The only backlight control panel settings are for the main screen's backlight.
I was provided with a beta of CeRegSpy that works with WM5, but there was nothing of interest in its output either. At this point I'm inclined to believe that the timeout is hardcoded in the driver file. I'm dismissing the hardware option, as the keyboard doesn't respond at all until the Windows Mobile loading screen - if it were in hardware, it'd likely react as soon as power was supplied to it.
Unless HTC or QTek or, etc., can provide us with exact information on where the timeout may be controlled, I think this is not likely to be adjusted by us anytime soon.
Related
I was getting frustrated with the problems I was facing with GPRS in i-mate's new rom. Some people couldn't connect and disconnect properly, I personally was suffering from having my Red Phone button disconnect GPRS when I merely pressed it, not held it, every time.
I got pissed off with it last night, and decided to find the problem once and for all.
First, I cleared my extended rom, and did a hard-reset. I then noted that the red phone button sound reverted to normal, and that the GPRS didn't disconnect unless I held the red phone button. In other words, I discovered my problem lied within the extended rom.
So, then I went through cab by cab and tried to find out exactly which one caused the problem. All the obvious choices did not. I then stumbled upon the problem cab; the I-Mate customization cab (Default_ImateV112.002.cab). This little 74kb cab was causing my GPRS to disconnect whenever I pressed the Red Phone button. So, I recooked my extended rom without that cab, then hard reset. Voila, GPRS was working properly.
My comparison of the new I-mate customization cab with the older one, brought up one small difference in CM_Entries.xml, and it was exactly this small change that resulting in GPRS disconnecting when the Red phone button is pressed instead of held.
The lines that cause the problem are:
<characteristic type="Registry">
<characteristic type="HKLM\ControlPanel\Phone">
<parm name="Flags2" value="8" datatype="integer" />
</characteristic>
</characteristic>
The section of code that I identified to be causing the problem creates a key named "Flag2" within HKLM\ControlPanel\Phone. What this does is actually creates the Disconnect button we now see in the Connectivity bubble. It seems that enabling this button is the root of my (and perhaps other people's) GPRS problems.
Here is the information on this code:
To get just the disconnect/time online in your bubble, Tweak the following key:
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"Flags2"=dword:00000000 = no button disconect in buble con.
"Flags2"=dword:00000008 = button disconect on buble con.
"Flags2"=dword:00000010 = button disconect and time con. on buble conection (hex)
Removing the key "Flags2" solves the problem, but removes the disconnect button (I assume this is the same as setting it to 0). The new default 8 setting is the problem. Setting it to 16, which adds the button and a connection length timer seems to be problem free from my testing, so if you like the disconnect button, I recommend setting it the key to 16 (DECIMAL, 00000010 HEX) and giving that a try, and if you aren't satisfied then remove the key altogether. Reset after any changes to the registry to see the results.
THE CABS BELOW ARE NOT PATCHES. THE SHORT TERM SOLUTION IS TO CHANGE THE REGISTRY KEY. THESE CABS ARE MEANT TO BE REPLACEMENTS FOR THE ORIGINAL PROBLEM CAB IN YOUR EXTENDED ROM, NOT TO BE RUN SEPERATELY
I have also made 2 cabs meant to replace the old Default_ImateV112.002.cab within your extended rom for a more perminent solution.
http://qlink.queensu.ca/~3bsg/16Flags2/Default_ImateV112.002.cab : Sets the key Flags2 to 16, keeping the disconnect button and adding a timer
http://qlink.queensu.ca/~3bsg/RemovedFlags2/Default_ImateV112.002.cab : Stops the key Flags2 from ever being created, removed the disconnect button[/b]
Sweet, (still looking for the coffee hack), thanks
Re: Solution to i-mate 1.40 GPRS woes
TheLastOne said:
The lines that cause the problem are:
<characteristic type="Registry">
<characteristic type="HKLM\ControlPanel\Phone">
<parm name="Flags2" value="8" datatype="integer" />
</characteristic>
</characteristic>
Click to expand...
Click to collapse
Maybe imate fixed this already???
I did fresh install from imate website and after reading your post, I checked my Registry and it is already "16"
Let me verify this.
Edit:
I went through a lot of trouble to disprove this.
I just went to clubimate.com, downloaded a fresh rom, reinstalled the extended rom, and can disprove this. Nothing has changes. Flags2 is still set to 8 by default. Problems still occur with GPRS.
Great solution! Applied this to my pda2k and JAM and could not be happier. Make sure you upload it to the FTP.
Better why not use Phone Alarm 1.13.2 latest version.It does the same as explained and I am using it.....
Re: Solution to i-mate 1.40 GPRS woes
Your registry hack works very nicely...thanks.
My problem is more than not after a phone call the GPRS will not connect again until I either do a reset of the ppc or go into flight mode and come back out.
Any ideas on a fix for that?
tekhound, you have changed your registry and then reset your device to apply the changes? Go into your registry and change the Flags2 key in question to 16, then reset your device (or run the Flags2 = 16 cab I included in the first post). If that doesn't fix your problem, then your problem is different than those faced by others.
TLO...
I actually had your cab file already installed. I went ahead and deleted the reg key all together. Hopefully that will work, since I use the GPRS for my push email more than I use the phone.
Thanks for all of your hard work. I find it amazing that groups like this and people like you seem to know more about this stuff than the people who make or support them.
Update....
I was still having problems even after i made the changes and uploaded the cab TLO made. No luck on keeping the the GPRS not only connected, but be able to connect it again with out having to reset.
I decided to copy all of the extended rom files out completey and do a hard reset. Everything has been working fine so far without any disconnect or reconnect problems I experienced before. I have since gone back in and added the battery patch and a few other files I wanted.
I will add a cab at a time and hopefully see when the cab causing the problem is installed.
I have a sneaky feeling that one of those cabs does something that makes the BA not talk to the US T-Mobile network correctly. I have seen a few post on different boards from people that use the US T-Mobile network have similar problems when they updated their imate PDA2K device to the new version.
I will post with any updates.
Thanks again for everyones support!
i would like to know what you find, i had a similar problem before the Imate rom was released; gprs would not reconnect after the first connection without a soft reset. What worked for me was not installing the AKU26_RC20 Caller id cab. I was already using GBSOFT Tweak to enable the disconnect and time display in the gprs bubble. But other people reported no problem using that cab so may just be coincedence.
My experience is (unfortunately) consistent with tekhound's, even after installing the TLO's cab. Although TLO's cab is still an improvement with the Disconnect button and counter. I am also with T-Mobile in the US.
Odd. Then perhaps the different GPRS problems to not share the same cause.
I must say, I am not facing the same problem as you guys are. After changing the key to 16 and reset, GPRS has worked flawlessly.
However, I think it is important to note that everyone who is still facing GPRS problems is in the United States (I would assume using T-Mobile). Are all your devices SX66's as well?
I'm having problem using my i-mate JAM.
i-mate's forum led me here via howardforums....i-mate recently released their JAM ROM upgrade and that looks to be where the GPRS connection problems have surfaced. They are not being reported as specific to T-Mobile or even the US. Users with different carriers and/or the ROM for another country (at least saw UK referenced) are finding the bug.
From a quick scan of i-mate's forum for the PDA2K, similar symptoms are being reported after the ROM upgrade for that device.
I used the new hacked .cab for a few days and had no problems whatsoever when I installed it from a hard reset WHEN NOT INSTALLING THE EXTROM. The GPRS ran great and no longer disconncted with the touch of the red phone button.
Unfortunately, I had problems with "Phone Pad" among others which I thought could be solved by installing the full 1.11 EXTROM. After installing the extrom and the .cab fix, my phone pad was working fine, but now the damn "Unknown reason" Error message is back again which leads me to belive that there is something in the extrom that is messing stuff up.
I'm afraid that I'm going to have to head back to 1.06WWE now for the 5th time. It's pain in the ass as I have to set up my exchange server settings all over again. I'm getting really tired of Imate's piss poor programming. Do they not test their own software? I noticed problems minutes into the new ROM. It's unacceptable.
Well, that's my ranting raving for the evening. I'm sure that after I spend my Saturday reinstalling everything back to 1.06 that I-Mate will release a file to fix everything. :-(
Maybe it's me....but I thought that this was the B/A forum.....
:?
mbc said:
I'm having problem using my i-mate JAM.
i-mate's forum led me here via howardforums....i-mate recently released their JAM ROM upgrade and that looks to be where the GPRS connection problems have surfaced. They are not being reported as specific to T-Mobile or even the US. Users with different carriers and/or the ROM for another country (at least saw UK referenced) are finding the bug.
From a quick scan of i-mate's forum for the PDA2K, similar symptoms are being reported after the ROM upgrade for that device.
Click to expand...
Click to collapse
I also have the same problem with the new rom in HK. So, I can confirm that this is not operator related. It also happened to magician as well.
I installed again a previous version of wireless manager from other rom and will report later. Not the 'Remove wifi logo' one but 'Default_OEM_BA_09080401.CAB'.
thanks, TLO! I appreciate all of your hard work! This added the timer for me and doesn't seem to kill my GPRS connection when I hit the hang up button more than once, as it was before.
Now if I can just get the darn device to actually consistently MAKE a connection without requiring a soft reset...
The 'Default_OEM_BA_09080401.CAB' is no good.
It also had the same effect.
I hard reset my device and change the autoconfig file to NOT to install any patch. I then check the connections by turning on and off again and it's working so far. Will report again tomorrow.
Cheers,
Hi there,
I have an XDA2i from O2 - I am not sure how to find out things like ROM version etc, but from the about screen it says:
Windows Mobile 2003 Second Edition Version 4.21.1088 (Build 14235.2.0.0)
Anyhow, my problem is that when I try and access certain items on the settings menus (GPRS settings and Power settings in particular) it takes me to the backlight settings page... Also, it seems like the backlight stays on whilst its in the cradle, even though I have set it to turn off after 2 mins. Don't know if that's relevant.
Anyone know why this could be and how I could remedy it? I am new to this place so I'm not sure what information to include - if you need more info just ask.
Thanks
I can't believe how very stupid I was. I did a soft reset and it was fixed... Sorry for wasting your time!
Ok guys, I believe I've found the regkey to fix all the dropping wifi issues within WM2005. This has been tried and tested on my Blue Angel SX66 Cingular with the hack listed in the wiki to get up to WM2005. Anyways, to the patch, unfortunately I don't know how to make cab's so follow along. Get yourself a registry editor (i.e. TRE) and navigate to HKEY_LOCAL_MACHINE\Comm\"Your Adapter Name. Mine had 2 keys, tiacxwln and tiacxwln1, tiacxwln1 was the ticket for me" Within the Parms folder you'll find a DWORD value named ResetOnResume which should be set to '1' change that value to '0' and hit ok in the bottom left corner. Give your BA a soft reset and all should be good. I haven't tested this for side effects, but it now reconnects to wifi on resume without a hitch. Please post results back here, I hope I am not jumping the gun!
TIP: To find your adapter name go into Settings>Connections>Network Cards>Network Adapters and look for "xxxxxxx Compatible Wireless Ethernet" again, mine was called 'tiacxwln Compatible Wireless Ethernet'.
Hallelujah!!!!!!!!!!!!
This has been my number one gripe with WM5, everything else as just been small annoyances. But this one... I use WiFi a lot, actually almost every time I turn he thing on. I even got WiFi in my car! So thank you, thank you, thank you, thank you, thank you!
Oh, do I have to say that it really works? :lol: Qtek 9090 btw.
You who try this, don't forget to turn off the unit for 15 seconds before you do the soft reset, this flushes the registry.
This also appears to work on WM2003, at least with my SX66 running the current revs from the SX66 Standardization Project.
WOW ... its perfect ..... you're realy MAN !!! thx thx thx.....
I've updated BA_WM5_FIX.CAB so that it sets this registry value:
ftp.xda-developers.com/Uploads/Blueangel/wm5_test/BA_WM5_FIX.CAB
with this registry setting wifi on my BA will not stay off. anyone else getting this?
Yes, I see the same thing. Now suspending the unit will turn on wifi on resume. So is that a problem for those who worry about battery life? Probably. Do I care? Nope! But then I'm in my own home around 90 % of the time, within reach of the charger. No, I'm not a slacker, I actually run a business and work 8-10 hour days, but I have my office at home!
Sorry guys I don't understand what's happening. What's going on with the wifi?
brn2prgrm: On WM5, if you turn Wifi on, switch the device off, then back on, Wifi does not resume. This action was default on WM2003SE. The registry key that makes Wifi resume by itself when you turn the device back on was found, and then integrated in the WM5 patches CAB. That's basically all
Eh...it was he who found that key! What he's wondering about is why it isn't possible to make it stay off when you have enabled this key, even if WiFi is off when you suspend, it will turn on when you turn on the PPC again, which it didn't do in WM2003. It was restored to last state, on or off.
Another thing: Has anybody tried this hack with the wireless control app from the Universal that was posted here a while ago, to see if it stays off then?
mamaich said:
I've updated BA_WM5_FIX.CAB so that it sets this registry value:
ftp.xda-developers.com/Uploads/Blueangel/wm5_test/BA_WM5_FIX.CAB
Click to expand...
Click to collapse
I think there is a TYPO in the cab file.
I found the reg setting as tiacwln1
Shouldn't this be tiacxwln1 ????
yes, it is a typo.
I've removed the mistyped key from BA_WM5_FIX.CAB and made a BA_WIFI_FIX.CAB which sets the correct registry value. They are in the same dir on FTP
I don't understand the wifi thing:
I get some connections from my neighbours,but my own linksys won't connect?
What do I have to do to connect my MDA to my linksys router??
since I upgraded to WM5 I can't get my wifi to operate 100% of the time--for example, when I connect to wifi--the signal is locked then I try to send/receive my email and then my SX66 tries to connect via GPRS--do I have a setting that's incorrect? or is it because of this thread which is now patched?? HELP--I use my wifi a lot and lately I can't TIA!!
Mastiff said:
Eh...it was he who found that key! What he's wondering about is why it isn't possible to make it stay off when you have enabled this key, even if WiFi is off when you suspend, it will turn on when you turn on the PPC again, which it didn't do in WM2003. It was restored to last state, on or off.
Another thing: Has anybody tried this hack with the wireless control app from the Universal that was posted here a while ago, to see if it stays off then?
Click to expand...
Click to collapse
I'm waiting for a patch that does exactly what you thought off, restores its last stage. Not sure hwo long would it take to come out with it.
Anyway, I do not find it a hassle to Turn On Wifi once again instead of it swtiching on by itself upon power up..... I use wifi a lot too though, but haven't found a prob with it.
how about a registry patch that fixes that bluetooth auto turn off annoyance?
O2 XDA IIs (wifi)
Hi , I have recently upgraded my 02 xda IIs to WM5 ,
after applying the patch , wifi worked for a while , then now when i try wifi again, i get this error.
FORBIDDEN.
you were denied access because: access dinied by access control list.
Someone please help me.
Greetings fellow tweakers,
I am having a problem with my newly acquired US-version T-Mobile MDA Vario (aka HTC Wizard).
For some reason, I can't get ANY 3rd party SIPs (software input panels) to work with this damned thing. NONE. I have tried at least half a dozen (Calligrapher, InterKey, etc.), and the result is always the same. The SIP installs, and when I click on the SIP icon, the option shows on the popup menu (although that menu takes FOREVER to display). Then, when I try to select it, the device reverts to the default keyboard SIP and the one I installed never works.
I once had this problem on my older Wallaby device, and it mysteriously went away. Is it possible that I have a corrupted DLL or registry setting somewhere?
Is anybody else seeing this kind of problem?
Thanks, and happy hacking.
- Justin
This is a know problem with the WM5 devices. I had the same problem.
Luckily Fitaly made a version 4 which doesn't have this problem.
All the other alternetive input methods suffer from this problem.
A small workaround: Soft reset and then choose the SIP of choice before opening any other programs. Works most of the time. Sometimes Todayplugins can interfere.
Wouter
I've tested a bunch of SIPs, and there's several where after the install, you need to soft reset first. Some of them actually do this for you (TopKey was one of them, I think).
I know this topic is months old, but I have recently run into this issue. I'm using Molski's WM5 v3.3 and am getting the EXACT issue as the 1st post recounts.
I install calligrapher, soft reset, run anything, click the keyboard icon (in order to change input methods), the PDA pauses for 7-12 seconds, menu pops up, I click on calligrapher, the keyboard icon remains and the input method doesn't change.
I absolutely LOVE calligrapher, and this is really worrying me on this AKU version.
Is there a fix for this or another AKU3.3 ROM that allows calligrapher to work?
Lowkee
Hello,
at first I would like to say sorry for my english knowledge ^^
My Problem: I have a HTC Tytn II (or MDA Vario 3 <- the name of T-Mobile) and I would like to use its Internet connection for chatting with ICQ with the program "Palringo".
Every time, when my Phone turns "off" (standby with black display) after 2 minutes of unusage the device cuts the connection to my wlan router at home.
So if Palringo has been started, the program suppresses these function and the phone is in the normal mode with the dimmed display light.
Can you tell me a program, which turns the display off without cutting the connection? Because I won't my display to be turned on 24 hours a day.
I thank you in advance very much
Advanced Config "attached"
Under:
Network\Turn Off Wi-Fi if no activity.
thanks for the quick reply
ok by installing the cab there is an error: I need a higher version of Microsoft .NET Framework than my installed version.
can you tell me which version I need?
Do they exist as.cab file because I don't have my ActiveSync at the moment.
thanks
MDA User 2 said:
thanks for the quick reply
ok by installing the cab there is an error: I need a higher version of Microsoft .NET Framework than my installed version.
can you tell me which version I need?
Do they exist as.cab file because I don't have my ActiveSync at the moment.
thanks
Click to expand...
Click to collapse
It's .Net Compact Framework 3.5
Hope that this works for you as i searched XDA for the .cab since mine is .exe for active sync.
Have uploaded to share as XDA won't allow attach.
http://www.mediafire.com/?fmqjmobmymm
thanks for the great support
I've installed both on my device, did a soft reset and did your instrucions with a second soft reset.
But the phone always still cuts the wlan connection, when the phone turns in standby mode.
I noticed no difference too before
A possibility, that I can receive text messages while the display is black would be great.
To be honest i was guessin and that looks like the option.
Kaiser Tweak does it
Also
http://pockettoolman.blogspot.com/
Bear in mind i'm using the search here as never had to always have wi-fi always on.
i have always desired this feature also but the kaisertweak and/or advancedconfig setting seems to be highly ROM dependent. i have recently moved on to wm6.5 ROMs and so far NONE of the wm6.5 ROMs i have tried can keep WIFI on in standby mode.
in my experience with some cooked ROMs, the ONLY ROM that actually achieves this feature has been SJ's HyperDragon IV Rhodium ROM (link in my signature).
another option (i have not tested this option myself) might be to use a screen off utility...i believe PSShutXP does something to that effect?!?
good luck!
NOTE: i posted detailed testing results a month or two ago in another thread that prove that the particular HyperDragon ROM i have mentioned REALLY has this behavior. search my posts and you will certainly find it!
here is the thread i mentioned with my testing results for the functionality the thread-starter desires:
http://forum.xda-developers.com/showthread.php?t=511979