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,
Hello,
My T-Mobile MDA Vario spoke Dutch which was very unformortable so I unlocked it and installed the Qtek ROM. Installation was fine.
However, it kept on being confused about the state of the "flight mode"; either I could make phone calls even though the icon said it was not connected to the network (aerial with X) or it did not want to connect to GPRS even though it was on the T-Mobile network
Otherwise it all worked fine.
In an attempt to get rid of this annoying behaviour I installed the K-Jam ROM found on the FTP server of this website. Installation was fine again, however now the device soft resets itself all the time and does not always want to turn on when I push the button on top. The soft reset frequency is very unpredictable, and turning phone on or off does not really make a difference.
Any clue?
Many thanks in advance
Manhattan.
It looks like the reset problem is solved after installing an updated i-mate ROM that resides in the upload section of this site's FTP. It seems to me it has only an updated extended rom part, perhaps someone has figured out what's the difference?
thanks
manhattan
what's the filename? i couldn't find it...
K-JAM_WWE_1010903_106_10110_ship.exe
Anyone having the problem when they switch battery with the wm5 installed it wipes some internet settings? any fix to this
JM
soft reset twice !
I had the same problem and was quite annoying because you need to write the account details changing the account name. Ihad this problem with WM5, but never tried with WM2003.
But, I have found out that if you soft reset again just after changing the battery, before booting is completed, you don't lose any setting.
Let me know if it works.
Cheers
''
fucsia
jasonmoe, did you have any luck with this?
i new to this whole pocket pc thing, and i found this site and started upgrading my t-mobile mda. first i upgraded the rom to the k-jam upgrade and everything worked fine. then i started messing with the registry with registry wizard. that was fine also. but as soon as i hit the edge icon tweak, i can no longer connect to gprs. i get a msg saying
"Cannot connect. make sure your phone is turned on, or tap settings to check your connection settings. "
can anyone help me. i didnt alter the settings from when it was working so im unsure of what the problem is. any help is greatly appreciated
sounds like ou ahve been doing a fair amount of tweaking. Even in the registry. Are you sure it was the Edge icon tweak that did it as my Cingular 8125 is running 2.16.9.1WWE and I have made that change and mine works fine. My wonder is if one of the previous changes didn't take affect until a reload or a new program load, and that is what actually caused the problem. I loaded some cingular cabs yesterday and it broke activesync.
ethorn said:
sounds like ou ahve been doing a fair amount of tweaking. Even in the registry. Are you sure it was the Edge icon tweak that did it as my Cingular 8125 is running 2.16.9.1WWE and I have made that change and mine works fine. My wonder is if one of the previous changes didn't take affect until a reload or a new program load, and that is what actually caused the problem. I loaded some cingular cabs yesterday and it broke activesync.
Click to expand...
Click to collapse
yah i know. but even after i restored my original registry settings i still cannot connect. when i try to connect, the window that shows gprs is trying to connect flashes 2x then it reads the msg i posted. any ideas
none here... I hope someone else can help, or you can hard reset and try to do the changes slowly soft reset a couple of times after each change until you figure out which one cased it. Each change including installed programs.
Sorry
mine does the same thing and I have been able to get it to connect without reset. Tap your signal bar on screen and turn on flight mode than turn off it will reset connections. It happens after every sync or charge for me and once we are able to unlock the cid and install the cing ext rom it might go away.
i actually just got rid of the program and it works now
Did anybody notice an improvement in activesyn?
My ROM is 1.93.831.1.
The activesyn. is still unstable. It fails intermittently and usually needs a soft reset before it can succeed.
But after repeated reset, sometimes the favorite contact list would be cleared up. How come there is still bug???
What is HTC doing?????
I am feeling desperate.
My old PPC 2003SE can even do activesyn within 10-20sec but diamond need at least ~1min to do so!!!
Switching off "enable advanced network functionality" seems to work in 1.34 ROM but not in 1.93 ROM.