yashsingh1/xdaforums huggingface dataset:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chris_khho:
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'.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] ChrisSpera:
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...
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chris_khho:
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,
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] tekhound:
Well it's been a week and I have not had one problem with the bluetooth, wifi or gprs connections getting stuck. In fact the gprs has been so flawless that I have been a little nervous to test any further by adding more of the EXTROM items back in because of how well it's been working.

I have only done one soft reset since last thursday and that was because of tweaks2k2.net configuration change.

I am off to a convention in Long Beach, CA next week, so maybe I'll try and blow it up when I get back. I am trying to get up the nerve to convince the CIO to let me get a spare one so I can blow that one up instead of my own. It would be alot easier if the damm thing wasn't $800 frickin dollars (kind of alot of money for a spare)!

Good luck to all on this...
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chris_khho:
Finally, I have to downgrade to 1.33 ROM which I believe is the most stable ROM and 1.10 Radio as well. But I am wrong. 1.33 also have this problem even w/ 1.08 radio.

The 1.40 / 1.33 ROM 1.12 / 1.10 / 1.08 Radio still have problem with the GRPS connection.

I totally gave up on this.

I downgraded the device to 1.31 ROM / 1.02 radio now. See what's happen....the only effect is no wmp10 BUT better wmp playlist showing all traditional chinese characters and pie w/ pocket plus can show multi pages now (well 1.33 Rom also but not 1.40).

Good luck everyone.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] snapper245:
same problem with Cingular

Just want to add my two cents. With my config (listed in my signature), I am also experiencing the GPRS disconnect (or inability to reconnect) as mentioned by tekhound.

I am with Cingular
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Cruzzer:
Re: same problem with Cingular

Same problem here!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] cbrow51:
Tekhound Wrote:

Tekhound, I am having the same problems as you after the "Upgrade" to the iMate 1.40 ROM. I am with T-Mobile also. The ROM is practically unusable for me and since we just implemented GoodLink server, a stable GPRS connection is a must for me also... I am thinking I need to go back to the old O2 1.31 ROM, but before i do I would like to try your fix, but I am not sure how to "copy out the extended ROM files" Can you tell me what you did or point me to where I can read more?

Many Thanks

Chris

PS GoodLInk appears to be all you said it was! All I need now is a good GPRS connection. :cry:
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chris_khho:
Well, I finally have to admit that it's the device problem...

It doesn't mattered which ROM 1.31, 1.33, 1.40. They all have the "unknown connection" problem after you disconnected the GPRS and tried to connect it again. Well, sometimes it worked but most of the time it didn't.

One possible way is to turn to flight mode and turn off flight mode. Then you will not have to reboot your device.

Just a thought, is it possible to make a small programme for turning on flight mode and off by a single press.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chris_khho:
Deleted duplicated post.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] cbrow51:
chris khho wrote:

Hi Chris

Well, I have to say that while I was on the O2 1.31 ROM in corporate mode, my GPRS connection was flawless... No drops, no connection issues, just always stayed on or restated when I switched profiles in phoneAlarm or Pocket Zen Phone..

I think Tekhound may have found the answer in his previous post, which seems to involve copying out the problem files in the extended ROM. I have PM'd him to see if I can get more info.

In the meantime, I am also in constant "flight mode off" / "flight mode on" mode to keep my connection :cry:

Regards

Chris
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chris_khho:
That's the only issue that I am facing with BA.

Cheers,
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] efjay:
I posted this before, I had the same problem with GPRS not reconnecting. Now i am able to use GPRS without any problem. My solution was to downgrade my caller id version to 1.20 build 17957. When i first upgraded to AKU_RC 20 was when i first had the problem, tried the later version RC21 and still didnt work. I tried this several times, only the caller id version being changed produced the problem. Try that and see if it works for you
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chris_khho:
Which rom contains this caller I'D?

Thanks for your advise.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] efjay:
It should be on the ftp, try this link ftp://xda:xda@ftp.xda-developers.com/BlueAngel/CAB_Files/Caller ID/IA_CallerID_1.20_WWE.CAB
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] BaGRoS:
http://www.gb-soft.cz/XDAII/product_gprs_tweak_en.htm

??
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] chris_khho:
Oh sxxt!

We just got the O2 Asia 140 ROM. I have to do another hardreset this weekend.....

Anyway, thanks very much guys for your advices. Let's see whether this new ROM has some good fixes!!!

Cheers,
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] cbrow51:
1.40 GPRS Disconnect Issues on T-Mobile USA

efjay wrote:

YIPPEE!!!!!!! :D It worked for me!!! 2 days and no GPRS drops! Thanks to all here for the help!!

One observation on the 1.40 upgrade thread. I may have missed it in the wiki instructions, but I couldn't for the life of me find the "config.txt" file to edit in the 1.40 Ext ROM... efjay advised that this particular ROM does not have it.... Did I miss something, or should we update the wiki instructions?

Thanks again all!

Regards

Chris
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] :
Hi.

I am new in this forum.

I have this problem,since the old ROM then 1.31 and now 1.40+1.12 Radio.

I can connected to the GPRS network but downloading of a page even a mobile site take forever.even download o2 connect also forever (can connected but update it content take forever).

I have tried my sim card to a mini and all OK no problem but it only happend on my 2s.

But if I use the CSD connection it seems OK. WHY?

Any workaround, need some expert help here. ???????

Thanks.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] mascott:
How to install the cab?

Keep getting the message that IACallerid.dll is in use?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rdaprix:
You guys are GODS! You ROCK!

Hi: I’ve upgraded to 1.40 ROM on the PDA2K (unlocked) on T-mobile, and as I use it for a good link license push and three pop3 accounts, it’s my lifeline.

I’m on T-mobile and was losing my MIND over this problem! Imate in Dubai couldn’t help, onthegosolutions couldn’t help, so in desperation I googled the ROM version and known bugs and wouldn’t you know, CDA developers had the fix.

I leave for vacation tomorrow and you guys just saved my but. Thank you so, so very much. I installed the new file on my device, and voila, the GPRS disconnect problem went away.

You have performed a terrific public service!

Now, if I could only get the thing to power off after three minutes on batter power the way it’s supposed to instead of just shutting the backlight off… what’s up with that?

Anyway—this is the really important piece, and I thank you for the fix!

(IMATE should be ashamed of themselves for releasing this with this bug).
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rdaprix:
Damn, Not so fast...

I need to run and install the file: IA_CallerID_1.20_WWE.CAB to solve the GPRS connection problem, but when I try I get the error message The file: "\windows\iacontacts.dll" is in use or is in rom. If the file is not inr rom, please close the application using the file."

How can I run this file? what do I need to do to run it? Any help would be greatly appreciated...
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] 6381891:
Just to let you know, this is not an US - T-mobile problem only. In my case I have a Dutch T-Mobile SIM and a QTEK9090 (Dutch retail) after the upgrade to ROM 1.40 (official QTEK upgrade). I also experience the GPRS disconnect (or inability to reconnect) as mentioned by tekhound.

I don't have the red phone button disconnect issue.

I am with T-Mobile - Netherlands

So I'm not sure I should go for the cab replacement with the ROM level I have - somebody any suggestions on that.

thanks
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] Yung:
In regards to the GPRS not being able to re-connect, I had the same problem on my Jam, and then on the new M2000 I bought. In both cases, I solved the problem by downgrading to an older version of the Caller-ID cab...
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] 6381891:
Hi Yung, thanks for the confirmation! So I took the step but have the same issue as describe above:

I tried all the answers possible: yes/no/cancel

Anybody solved this?

thanks
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rdaprix:
Heeellllppppp!! T-mobile customers abandonded!

I’ve still got this problem as well, and T-mobile is useless (they don’t support the MDA-III/XDA II in the US).

What would be REALLY helpful (HINT HINT to moderators!! Please help the newbies!!!) is:

1.	a direct link to the caller ID cab file.

2.	step by step instructions (for dummies!) on how to run and install it with minimal damage.

We would really be grateful for any assistance. I have been in touch with HTC support in Texas in the US, and they have no ideas about how to resolve this, and IMATE Support in Dubai is worse than useless.

I think I’m just going to have to leave T-mobile and move over to another carrier. I don’t want to, but I can’t think of an alternative at this point. T-mobile doesn’t want to support the device in the US and good link technology says it’s the carrier’s problem and the manufacturer of the handset says it’s the carrier’s issue.

That means a lot of people leaving T-mobile unless there’s a resolution.

Anybody… anybody at all… please help us with some explicitly clear answers and directions. Thanks!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] tekhound:
rdaprix...

I am a t-mobile customer and have good link. I solved my problem by removing everything out of my extended rom. I eventually put back some of them, but for the most part I took out all the junk imate put in it. I had no problems after that.

I am in limbo for a few more days until my JASJAR (fricken stupid name for the Universal) arrives. Once I have that in and up and running, I will do a wipe on my BA and redo all of my steps. My BA is company property and I can't afford to wack it out and not get my email alerts from my servers. Once I have the Universal running, the BA will be a spare and I can mess with it to my hearts content.

Remember...you got an overseas model of a phone that t-mobile doesn't sell in the states. The Customer Service people don't make the rules, they just try and help as much as they are allowed to by the big cheeses. You'll get the same responce from ANY cell vendor that you go with using the imate. Kinda goes with the territory. That's why you came to the right place. These guys are the ones that SHOULD be developing these phones. I think they know more about them than even HTC does!

I'll post in the next few days with everything I did.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rdaprix:
Whew!!! Tekhound, I appreicate that...

If you could post a link to the caller .dll cab file that I can drop into storage and run, and please provide the step by step instructions (again, for dummies) to clean out the extended ROM and get the goodlink license working without the GPRS disconnect again, I will be eternally grateful.

I like the Universal, but given the slightly larger form factor and what I’ve got invested in my XDA I and XDA II, I’ll wait a bit and see how it works. I’m pretty handy with the slide out keyboard and I don’t see any stereo MP-3 on the universal and I’m tired of being HTC’s guinea pig.

I hear what you’re saying about T-mobile not wanting to support the device BUT (and that’s a big but) they DO support this in Europe, so it’s not like they don’t need to support the 1.40 ROM version. Additionally (working for a carrier) I think the market is headed away from the iron—the money is in the providing (and KEEPING) the carrier services. Not in the couple of hundred dollars on the handset.

T-mobile is about to lose some 500 accounts because of this problem with my company alone, so that’s just plain stupid, but REALLY gets my goat is the poor support from HTC direct in Houston.

This is their responsibility. They should have had a working ROM version specifically for t-mobile on their web site months ago. If HTC wants to dominate the handset market, it’s up to them to provide some decent level of support. They’re not doing that—you don’t want to see my phone bill to Dubai, and they are equally clueless there at IMATE Support.

Blech. This has really soured me on the HTC product line. Here’s the kicker—my company is about to standardize on one handset and leverage our purchasing power. We have 1400 employees and we need about 500 handsets that are converged devices and support goodlink. It’s between the Treo and the IMATE PDA2K which is the better device for our purposes because it’s unlocked so our Directors and VPs can use whatever carrier has better coverage for their travel region.

It looks like TREO will win (Ugh~!) because HTC can’t get their act together long enough to provide service to the three VPs in my organization that have this device. They will lose a huge sale and ongoing support revenue as a consequence of this—a lot of our traveling directors use T-mobile for the wide coverage area and data plans (unlimited).

Somewhere, someone is making an incredibly stupid business decision.

Anyway, I’ll be anxiously awaiting your instructions here. Thanks!
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] eagle 1:
Sorry for the dis, but

I hate to say it, but maybe your 3 vp's and 1400 employee's could afford to hire a real IT guy or at least one who can read and search the forums for the resolution to your gprs disconnect problem. Sorry for the Rant. I know it can be frustrating using a device that has some problems. The people on this forum are very smart and offer many solutions to other people's problems. Just try the search function. The posted suggested solutions is as follows.

(you will need to use another file explorer for this task as some of the files are hidden/sys files. Try total commander (free) or the better solutions Resco explorer)

You have to move the following files from \windows directory to a temporary location before installing the cab.

CallerID.dll

DisplayCID.dll

IA_CID_StartUp.exe

IA_CID_StartUp.lnk (From /windows/startup)

IACIDSync.dll

iacontacts.dll

After re-installation, change all the dll files in the temporary location to txt file. Softreset. You can then delete these files in temporary location.

Download the following downgraded caller id cab and COPY to your PDA. then select (double click) on the file to install it. Soft reset and your good to go.

ftp://xda:xda@ftp.xda-developers.com/BlueAngel/CAB_Files/Caller ID/IA_CallerID_1.20_WWE.CAB

If you still have problems or before purchasing 500 phones, hire an IT guy, a consultant or better yet, Read the wiki

http://wiki.xda-developers.com/index.php?pagename=HTC_Blueangel

Good Luck.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rdaprix:
PS--If anyone can walk me through this porcess...

This really does matter to me. If it matters, I am desperate and though I am traveling (without e-mail mostly as my goodlink keeps disconnecting) if someone can actually walk me through this over the phone, I'll do whatever I have to. I'll pay, I'll beg, I just can't go on anymore business trips with this thing not working.

I go on at least one business trip a week. I really need something that works. they're going to make me convert to a treo if I can't get this thing working reliably. They won't accept me bing out of e-mail contact.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] eagle 1:
1) Download total commander from link below and install via activesync.

2) Download the downgraded caller id cab listed below to sd card or other location. cab must be on pda prior to installing it will not install via activesync

3) using total commander Browse to the windows directory and move the files listed below to a generic or temp folder on sd card or other temp folder

4) Install the caller id cab file by selecting or opening or double clicking

5) rename the files you moved to the temp file such as callerID_dll.txt

6) Soft reset the pda

7) you may delete the moved temp (original) files or save for later if needed

(you will need to use another file explorer for this task as some of the files are hidden/sys files. Try total commander (free) or the better solutions Resco explorer)

Total commander info page

http://www.ghisler.com/pocketpc.htm

Total Commander download link

http://ghisler.fileburst.com/ce/tcmdpocketarm.exe

You have to move the following files from \windows directory to a temporary location before installing the cab.

CallerID.dll

DisplayCID.dll

IA_CID_StartUp.exe

IA_CID_StartUp.lnk (From /windows/startup)

IACIDSync.dll

iacontacts.dll

After re-installation, change all the dll files in the temporary location to txt file. Softreset. You can then delete these files in temporary location.

Download the following downgraded caller id cab and COPY to your PDA. then select (double click) on the file to install it. Soft reset and your good to go.

ftp://xda:xda@ftp.xda-developers.com/BlueAngel/CAB_Files/Caller ID/IA_CallerID_1.20_WWE.CAB

hope this helps.

Sorry about the rant, but an IT department that can't assist a vp piloting a new device (that they may purchase 500, i think thats 500 x 500 = $250,000.00) isn't really helping the business succeed. Maybe that's small money to you, but i would hope someone in IT could lend a hand if needed. But I guess if you are running cray machines, that is not a lot of money.

Good Luck
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rdaprix:
Thanks, I'll try it... here's hoping when I get time to try

this again Friday and I find a few hours to try this porcess.

And I understand, but it's not that they can't support it--it's that they don't see the need to. The point of the test is to see what requires the least in the way of custom support.

The less time these guys spend cut off from access and the less they time they spend on help desks and loading stiff (and the more people we need to do it for them) the less productive it is.

It is a conscious decision not to fix that which is better off replaced or more efficiently handled easily through the manufacturer. It's a business decision about what is most reliable and requires the least intervention to maintain. That is to some extent contingent on carrier netowrk adoption (if they sell it they'll have the patches and they'll be self extracting and issued realtively quickly), and if the carrier doesn't support it, it's incumbent upon the manufacturer to figure out the solutions if they want to work around that from a sales and marketing perspective.

If they had a sefl extracting patch for this fix for t-mobile, companies that sold these devices generically and idependent reatilers would sell the heck out of that as a work around to commerical accounts.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] tekhound:
Are we talking about the caller id program that imate installs as being the problem? The one that lets you put a picture with a phone number when the phone rings?
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] 6381891:
thank you, thank you Eagle 1

you are a hero...I'm so happy, it finally works like it should be and the way it was before my upgrade to 1.40.

I did not use the Total commander explorer, but used the ActiveSync file explorer (via the PC) and cut and pasted the files to the a special temp. directory. It worked fine

After the reset, my today screen was corrupted (I had that before with seperate cab. installs) but after installing SPB Pocket Plus 3.0, that problem also dissapeared.

thanks again, and thanks for your patienc, so that also newbies can do the job.

cheers

Ronald
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] kazmi:
Hi!

by reading through this post and many others, I think I have come to the conclusion that I too have the same problem and that callerID might be the culprit.

When I got my PDA2K, it worked fine but I noticed that adding any third party apps or even a today plugin would somehow "reset" the GPRS in such a way that it would only connect if I would toggle the Flight mode OR do a soft reset on it......

Recently, it wouldn't do it after that too....so I have had to do two hard resets.....

The caller ID version I'm running is : Caller ID version 1.20 (Build 19167)

I would appreciate if someone could tell me the version and build of the downgraded caller ID cab available here? Should I downgrade, since I'm fed up with this thing being so unreliable.......

If so, I have another question : when you say to copy the downgraded caller ID cab to the PPC, where should we place it? in the default place which opens up when you hit "Explore" on the ActiveSync window or on the Storage care? If on the storage card,do we need to copy it over to the main memory prior to installing or will it install just fine from the storage card?

Sorry for all the questions but I'm no genius when it comes to technology!

Thanks in advance for any help.
[MDA III, XDA III, PDA2k, 9090 Software Upgrading] rdaprix:
TEKhound is a god...

It all depends on what you're doing. TEKhound and I are running goodlink licenses for outlook exchange push e-mail (like Blackberry), so the GPRS connection is always on.

THe updated ROM version--1.40 isn't terribly stable and is in fact not certified with goodlink technology. TEKhound graciously posted the original ROM version for me--that would be the ROM version titled:

Imate_PDA2k_WWE_12200_162_10600_SHIP.exe

If you install that and hard reset, this prior version is far more stable and works fine with goodlink.

I also noticed the following tips and tricks:

1) If you use T-mobile, the netowrk periodically has a disconnect issue in some areas.

2) When you provision the goodlink license, be sure to do it over GPRS instead of your 802.11 WIFI access or you won't connect properly

3) Check your SIM card. THe contact occasionally wear out if you switch devices a lot. A new SIM card costs $25 and I havent' really had any problems to speak of since I got a new one.

4) Make sure your GPRS setting is set for internet3.voicestream.com on t-mobile instead internet2.voicestream.com or T-zones because you need the VPN setting.

The downgrade means you lose Mediaplayer version 10 and get 9 instead. BFD. It makes little or no difference.

Stable for about two weeks, now thanks to TEKhound.

If you're not doing a constant push, you should be able to use the 1.40 ROM by downgrading just the caller ID files, or stripping out all of ht extended ROM completely, but why bother? The above references ROM is stable and works well with push technologies.

My advice? Go with the original ROM version and stay with what works.