Related
After upgrading to 1.40, connecting to GPRS is hit or miss. When the problem occures it is normaly after the GPRS connection has been disconnected for a while, then when connecting again, I get the error "Cannot Connect". The only way out of this is to soft reset or turn ON then OFF "flight mode" (restart radio). The real problem in troubleshooting this issue is, I can not make it happen on a consistant basis, in fact, I can not duplicate it at all (it happens when it wants to). If you also have this issue, please offer any info you have on WHEN it happens or sequence of events that makes it happen.
Problem: "Cannot Connect" error when connecting to GPRS (all connection settings are correct).
When: ?????
Work around: restart radio
Note: This is not the same problem as "red phone button disconnects GPRS" ("Flags2") as discussed in http://forum.xda-developers.com/viewtopic.php?t=21972&sid=ff63b7f3db5fceffff1cd54fe61ffd27
the same for me!!
don't know why!!!
Does it seem to happen after a couple of hours after a soft reset?
Also, I have noticed turning flight mode ON then OFF only works for the next connection, after that I get the "Cannot Connect" error. A soft reset may work for several connect/disconnect cycles before it craps out.
Please post when it happens for you.
Got the same for a while now. Started to occur indeed after installing 1.40. My use is quite simple: an hour in the morning and an hour in the evening; in the evening it won't connect; soft reset and the thing goes again.
Did not found a woraround yet but will keep trying and share it with you if so.
XdaIIi - Cannot Connect GPRS
My XdaIIi is also giving the same problem. Turning Flight mode on/off gives some relief; buy only temporary. Compared to soft rest, this is far better. Why O2 is not providing any solution.
nraj
India
Norwegian devices with the 1.40 ROM is also having this problem!
Oystein
This seems to be the fix!!!!
efjay
Posted: Thu Jun 16, 2005 08:17
--------------------------------------------------------------------------------
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
_________________
Rom version 1.40 WWE
Radio 1.12
Ext Rom 1.40.147 (Cooked)
ftp://xda:[email protected]/BlueAngel/CAB_Files/Caller ID/IA_CallerID_1.20_WWE.CAB
Thanks to efjay!!!!!!!!!!!
What is the best way to update the Caller_ID cab? When I update, it tells me that it is available in ROM. Can it be done without doing a hard reset i.e. re-installing all over again?
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.
Hope this help.
Chris,
I tried what you suggested but I still get the message re file windows/ai???.dll is in ROM. I do not have any of these dlls in the windows directory or at startup.
Please let me know if you have other ideas. Thanks.
SK
You have to use gsfinder or resco explorer to see all system files.
Anybody else try this or the people who did it before today, Is it still working? I have the same issue. I just applied this fix, but it is too early to tell if it did anything...
thanks for the replies
It worked for me! Thanks very much to everybody who helped to discover and post this fix. It saved me from having to downgrade my entire rom, because I was cheesed off with having to do flight mode off/on every time I wanted to connect to the internet via cellular line, which I do often, because I've got an old Genie SIM with free WAP (not GPRS).
I found the instructions easy to follow, and I didn't even need to use gsfinder or resco explorer - I just set File Explorer to Show All Files.
Cheers,
John
_____________________
I-mate PDA2k Model No PH20B
Rom 1.40.00 WWE from club-imate
Radio 1.12.00
Protocol 1337.42
ExtROM 1.40.176 WWE
BT Build 3990
Network: O2 UK
From with files in ROM
Next time install safemode, then install your updates in safemode.
Cheers!
This fix has worked great for me (xda IIi ROM 1.11.00 Radio 1.00.00 ExtROM 1.11.923). When prompted that certain files are in ROM or in use, simply changing the file name of the files in question did the trick. For the first time in a very long time of using the XDA II and now the XDA IIi, I can reconnect to GPRS without a hitch.
Same Problem Here. I am going to try the Fix now
Moving to caller id version to 1.20 build 17957 worked great for me. No more GPRS cut outs at all.
Working Good Here. even the Wifi reconnects very very Nice THank you
Problem solved!!, This upgrade works great, thanks!!!
Please, help!
I am unable to persuade my AS 4.0 sync with my newly upgraded mda III. If I downgrade to wm2003SE, it works again, but when I try wm5, it does not do anything. Sometimes there is a signal: the first sound of the upwards connection signal three times, then nothing happens.
When I first upgraded to wm5, a found new hardware appeared and intended to go to the net for some driver. I said OK, then the installation failed after a few seconds. That was the only occassion of any real activity between the MDA III and AS4.
Via Infrared, it works fine, but it is very slow.
Any idea? Or any forum about this, I really tried to find one but found nothign so far.
Thanks a lot!
barrney said:
Please, help!
I am unable to persuade my AS 4.0 sync with my newly upgraded mda III. If I downgrade to wm2003SE, it works again, but when I try wm5, it does not do anything. Sometimes there is a signal: the first sound of the upwards connection signal three times, then nothing happens.
When I first upgraded to wm5, a found new hardware appeared and intended to go to the net for some driver. I said OK, then the installation failed after a few seconds. That was the only occassion of any real activity between the MDA III and AS4.
Via Infrared, it works fine, but it is very slow.
Any idea? Or any forum about this, I really tried to find one but found nothign so far.
Thanks a lot!
Click to expand...
Click to collapse
Have you read the WiKi about setting the IP and disabling the firewall?
Hi all,
I tried to use the blueooth for the first time in ages and I get an error message saying the license has expired, then the bluetooth is turned off automatically.
I found some earlier articles about this problem, and they suggested a solution was to install the widcomm bluetooth driver, which the author posted as an attachment. I installed this and reset the device, but when I click on the bluetooth icon I just get the same error message as before.
In case my customised ExtROM was the problem, I installed the standard O2 1.11.169 ExtROM, but the problem is still there. This is wierd because I have used bluetooth under that ExtROM version successfully in the past!
Can anyone help me???
Hey All-
Rather then adding to the large Helmi thread, I figured it would be best to start my own...
In short today I upgraded from TuMa v1.3 to Helmi's new ROM: Helmi_BA_WM2k5_AKU_2.3_32mb_v1.rar
Everything went fine during the upgrade, I set the Operator Code to T%CID? which was retrieved by using GetDeviceData.exe and the upgrade went smoothly... but now the phone functionality doesn't work at all. I've tried with two different SIM's, one being a T-Mobile and the other a Cingular. Both just show no service when inserted, although if I place those SIM's into other phones everything works properly without issue and I get 'full bars' (I have another Cingular 8125 and a T-Mobile SDA).
Here is what I have done so far:
- Reupgraded the Radio to the latest rev 1.15
- Recreated the nk.nbf again with retyping the operator code
- Reupgraded to the ROM to Helmi's
- Reunlocked SIM with xdadev_all_unlock-v1.5.exe
... and still no phone service.
Any suggestions on how to get the phone functionality to work properly? Its pretty much useless right now...
Thanks!
tempie23
I'm not sure that T%CID is right for an operator code... I know for O2 UK it's O2___001 and I'm sure a T-Mobile code isT-MOB101, both of these are 8 digits... check you're devicedata output again and use the setoperator.bat to set it properly, then try again
It's all good clean fun
spkr4thdd
I have the same operator code T%CID? but only on WM5. When i use 2003SE it is DANGA001.
tempie23
I had such error on TuMa 1.4 but reinstalling the ROM helped for a while. Then I tried helmi's ROM and the problem gone. But a couple of days ago it appeared once and reflashing did not help. What I done is downgraded to 2003SE, did a hardreset and reinserted SIM. The phone came back to work. Then installed helmi's ROM again. Now it is working for a day without any trouble, HOPE it's gone forever.
Tried a few things...
I tried downgrading and then reupgrading, but it still is stuck. No phone service. Interestingly enough the LED for the phone doesn't even come on anymore.
Interestingly enough when I select the phone settings from the upper menu I'm getting a Popup message stating "The phone is not ready. Wait 15 Seconds and try again." Obviously waiting 15 seconds does nothing...
Any other ideas?
Thanks!
tempie23
sometimes (happened to me) the operator info corrupts when upgrading to WM5
copy the files attached to the update directory and run 'MaUpgradeUt_noID.exe'
spkr4thdd said:
I'm not sure that T%CID is right for an operator code... I know for O2 UK it's O2___001 and I'm sure a T-Mobile code isT-MOB101, both of these are 8 digits... check you're devicedata output again and use the setoperator.bat to set it properly, then try again
It's all good clean fun
Click to expand...
Click to collapse
No it is not, it sounds like he has the same SX 66 that I have.
The ID is = AT%CID?
I posted this in this thead Here
read my above post, it can happen to anyone when upgrading to any wm5, mine happened the very first time i upgraded (TuMa 1.3), i dont know how it happens, but it seems to be permanent even with further reflashes (haven't tried 2k3)
NO Service
Midget_1990 said:
read my above post, it can happen to anyone when upgrading to any wm5, mine happened the very first time i upgraded (TuMa 1.3), i dont know how it happens, but it seems to be permanent even with further reflashes (haven't tried 2k3)
Click to expand...
Click to collapse
HI.
Sorry for my post, but I did not "get" how to fix the "NO Service" error:
This is what I've done today with Helmi_BA_WM2k5_AKU3.5_v1.4.CF2 by baniaczek:
Hi all.
Today finally spent some time, trying to upgrade my Qtek 9090.
Everything went fine:
1st) Did a SD backup of my current settings;
2nd) Updated ROM with SetOperator to my Operator (got from getdevice.txt);
2nd) Updated without problems;
Then used the Qtek by 5 minutes (inclusively i did a phone call), after that could no longer get the "phone" working - exactly when I received a call, the phone "gone out" and never more. After several soft resets and hard resets the phone was always with "no service" message (but strangely, I could go to settings phone, and look for "the broadcasting" networks).
I swaped the SIM to another phone and it was working, never the less I got another working sim, but the problem continues (btw, I always have the PinCode disabled, and I remember now that I forgot to test enabling PinCode request!!!).
Then, just in case I downgraded the phone to W2003SE, again, and everything was working fine.
My radio was 1.12. So upgraded radio to 1.15, and started over again but with no sucess.
When I downgraded once again, the Qtek works fine with either RADIO versions or sims.
Has anyone got this "nice feature"?????
Is there any overcame solution? (My only missing test is to enable Pincode, and test if it works?)
tks for any help
I'm having the same issue here as well, tried the comm manger on and off and disable and enable it. Still makes no difference, someone please help me out, I can't get anyone to help me
Has anyone gotten their diamond to work successfully with z-push? There seems to be a problem with the diamond not sending authentication for every ping request, and therefore push not working.
This thread (http://z-push.sourceforge.net/phpbb/viewtopic.php?f=2&t=198) seems to isolate the issue to the latest wm 6.1 devices with direct push enabled. I can confirm that a wm 6 blackjack 2 operates without issue.
Has anyone faced this? Does anyone know how to make the diamond behave like a wm6 devices in terms of authenticating pings?
It would seem one guy managed to tweak z-push to receive those pings correctly(http://z-push.sourceforge.net/phpbb/viewtopic.php?f=2&t=198&start=10#p1272), but he only explains his solution, he doesn't provide the patch, and I'm not familiar enough with memcached to use it.
Maybe someone else will read his explanation and implement it?
Here's hoping (and wihtout the security issue mentioned on that board). I just find it strange that a WM 6.1 Tytn II is listed among the working devices, but the 6.1 diamond fails to authenticate pings. I was hoping there was a tweak or registiry trick available for correcting this.
I have a wm6.1 tytn2, and I can confirm it doesn't work. I'd think it's a rom issue.
i stand corrected, i thought i read somewhere on the z-push forum that the tytn 2 with 6.1 worked.
i'm running bepe .99 right now, but i will test dutty and swifts versions and report back
Ive ran z-push before with my diamond without issue. I didnt know about any ping issue, but then I didnt continue to use it. BTW, my name on there is the same as on here, and I wrote an entire how to install.
did push work for you? z-push does indeed work on the diamond, but there is no push functionality. instead, it will sync up every so often. if push worked for you, i would really like to know what, if anything, is different between your phone and mine
z-push is still running here on my root server... syncing to my diamond is no problem...
Unchained said:
z-push is still running here on my root server... syncing to my diamond is no problem...
Click to expand...
Click to collapse
Does it push? can you check your debug log for a ping request from the diamond? if it does push and you are successfully passing the ping command, can you tell us what rom you're using? diam100 i presume?
bigwill3 said:
Does it push? can you check your debug log for a ping request from the diamond? if it does push and you are successfully passing the ping command, can you tell us what rom you're using? diam100 i presume?
Click to expand...
Click to collapse
Code:
07/31/08 08:20:31 Client supports version 2.5
07/31/08 08:20:31 IMAP connection opened sucessfully
07/31/08 08:20:31 POST cmd: Ping
07/31/08 08:20:31 Ping received
07/31/08 08:20:31 Waiting for changes... (lifetime 780)
I tried GER Roms O2 1.39, O2 1.93, HTC 1.93 and all bepe ROM; no problem there. Device is diam100; as u presumed..
But note; I am using z-push 1.1.1; not the current version... the actuall version isnt pushing here... But never looked, whats buggy there... Switched back to the old one.
Unchained said:
Code:
07/31/08 08:20:31 Client supports version 2.5
07/31/08 08:20:31 IMAP connection opened sucessfully
07/31/08 08:20:31 POST cmd: Ping
07/31/08 08:20:31 Ping received
07/31/08 08:20:31 Waiting for changes... (lifetime 780)
I tried GER Roms O2 1.39, O2 1.93, HTC 1.93 and all bepe ROM; no problem there. Device is diam100; as u presumed..
But note; I am using z-push 1.1.1; not the current version... the actuall version isnt pushing here... But never looked, whats buggy there... Switched back to the old one.
Click to expand...
Click to collapse
Thank you! I will test 1.1.1 and report.
no ping with 1.1.1. all other things being equal, it must be a rom issue. i will test with different roms and report my findings. any ohter input would be greatly appreciated
What about the log??
Unchained said:
What about the log??
Click to expand...
Click to collapse
that's how i determined that no ping is being successfully passed. it simply spits out:
09/23/08 14:58:01 Start
09/23/08 14:58:01 Z-Push version: 1.1.1
09/23/08 14:58:01 Client supports version 2.5
09/23/08 14:58:02 IMAP connection opened sucessfully
09/23/08 14:58:02 IMAP connection closed
09/23/08 14:58:02 end
nothing else. i do get email, but it appears to operate on a schedule instead of as it arrives (which the phone is set to)
success on duttys 2.2 (today's build). it must have been bepe .99 that was hanging me up (though I love bepe and wish he would continue development).
i'm going to test with z-push 1.2 and report