since installing radio 1.13 i have not been able to connect to GPRS using wap.voicestream.com. this is after a hard reset with none of the EXT rom tools loaded. i try to connect, and it times out. in 1.12 i would be able to connect once but after connecting to activesync or disconnecting GPRS i was not able to log back in unless i soft reset or turned on flight mode then turned it off. I have 1.40 ROM installed with phone alarm 1.21, pocket plus, and wisbar 2.4.11
UPDATE!!!
ok, i uninstalled pocket contacts 1.1 from www.pocketx.net and installed pocket conctacts PRO 3.0. i also unloaded mort ring. well when i did that i was not only able to connect to gprs, i am now able to RECONNECT when i disconnect! wierd...
What device do you have and what ROM are you running? I'm looking to solve this problem on my PDA2K.
i have the same device and ROM as you do. since i last posted. i am only able to connect to GPRS after a soft reset, not turning on/off flight mode
Downgrading Caller ID to IA_CallerID_1.20_WWE.CAB will fix this problem. It worked on mine at least...
downloading and installing the cab for the caller_id worked for mine as well. i've had no problems with gprs connections since performing the downgrade -- which was a little over a week ago. i think you can find the cab in these forums if you search for it.
i dont have that caller id sodtware installed at all and i still have the gprs reconnect issue
Related
Hi all,
I have a strange problem: bluetooth manager works fine after a soft reset. I can my PPC the whole day and it will always start normally (read: the screen that shows BT shortcuts shows up). The problem occurs when I turn off the phone over night (flight mode). The next day I can't get the BT manager to show the shortcuts screen - BT can be switched on and off but neither the BT manager or the BT settings screen will show up (there is no error message!!!). After I do a soft reset everything starts working...
Has anyone come across this kind of a problem in the past? I couldn't find anything using search on this forum...
My device info is (DutchRetail ROM):
ROM: 1.40.00 WWE
Radio: 1.13.00
Ext ROM: 1.40.556 WWE
I have tried uninstalling almost all extra software that I have installed after a hard reset but the issue is still here.
Thanks for all suggestions on what else I can try.
Hi Poga,
Yep, I get exactly the same problem :-(
AndrewB
ROM (i-Mate) 1.40.00 WWE
Radio 1.12.00
ExtROM 1.40.176
Hi Poga,
Yep, I get exactly the same problem :-(
AndrewB
ROM (i-Mate) 1.40.00 WWE
Radio 1.12.00
ExtROM 1.40.176
Do either of you have Goodlink software on your device?
same problem no goodlink
Same problem but no goodlink software
I also get another funny problem where sometimes I go to connect to my bluetooth access point from my phone and it just has the little pie icon saying it's doing something, then it stops and it hasn't connected (the connection icon stays the same) and I can't make any sort of connection. It then does this everytime I try to connect.
I don't know how i fix it, but I combination of many soft resets various flight mode turn ons and fiddling it eventually works. It's very frustrating and it's happened on every software version. Right now i"m running 2.04.00. I have a CDMA from Telecom NZ running radio HA_01_151 right now (but I've tried other radios).
Somebody else had this problem I noticed but nobody replied to his posts.
I've got the same problem I hope someday that someone makes a fix for it. I run the XDA IIs BlueAngel 1.40.00 Asian O2 ROM WWE. =/.
Same problem here - only solution I had was to go into settings/memory and then stop all programs running - then the bluetooth manager appears without the need for a softboot..
Pain in the arse. :!:
poga said:
Hi all,
I have a strange problem: bluetooth manager works fine after a soft reset. I can my PPC the whole day and it will always start normally (read: the screen that shows BT shortcuts shows up). The problem occurs when I turn off the phone over night (flight mode). The next day I can't get the BT manager to show the shortcuts screen - BT can be switched on and off but neither the BT manager or the BT settings screen will show up (there is no error message!!!). After I do a soft reset everything starts working...
Has anyone come across this kind of a problem in the past? I couldn't find anything using search on this forum...
My device info is (DutchRetail ROM):
ROM: 1.40.00 WWE
Radio: 1.13.00
Ext ROM: 1.40.556 WWE
I have tried uninstalling almost all extra software that I have installed after a hard reset but the issue is still here.
Thanks for all suggestions on what else I can try.
Click to expand...
Click to collapse
cw6447 said:
Do either of you have Goodlink software on your device?
Click to expand...
Click to collapse
I do and I have the same problem. I've been suspecting that it may have something to do with that because when I reset and I can start the manager just fine before I start Goodlink, but after I start goodlink it's a pain. Once, I tried to start BT manager then it didnt... i forgot all about it then suddenly some 11 hours later it just popped up by itself. Goodlink had been running continuously.
Any ideas???
I sometimes have the same effect.
What I usually do to resolve it (without soft reset):
- I installed PocketNav (kills programs which run in the background)
- I select 'Close all but Ative' in PocketNav
Then the Bluetooth Manager works again.
Hope it helps.
A
This is due to memory limitation in WM2003SE. When it finds that the memory is not sufficient it wont run Bluetooth Manager or Wifi. I had this problem a lot until i have shifted to WM5 which has more than 100 mb when the device starts. I guess that is why M$ has built WM5 for that reason and also for persisten storage of course.
The "memory limitation" is indirectly the problem. The Goodlink, which is more than three times the memory hog as any other 3rd party app out there, is the direct problem. I could write a college discertation on the amount of bugs in this awful software. And yes, it is good for push email...but at the expense of everything else that is good about these multimedia devices we own. The typical "close-when-you-tap-the-X" software utilities don't shut down Goodlink on my device even though they successfully shut down every other software I own (over 40 titles). So I have to use MemMaid to kill its process. But Goodlink will restore itself in a matter of minutes as it ventures out to the server looking to synch mail, calendar, contacts. If there was ever a reason to bring back public hangings, it would be for the Goodlink windows OS development team.
I don't really see any issues with Goodlink eating my memory. Then again, I've converted from a strictly fun user to a strictly business user so the whole gaming and multimedia thing doesn't quite do it for me anymore.
Steiner,
I tried PocketNav to see if it would truly close GoodApp.exe. Although it does seem to shut the application down, the 6+MB exe still is open in memory. Using MemMaid it shows that it never really closes.
I also didn't have the Goodlink software installed . My solution to the problem was: I installed the Sprite Backup software and set it to automatically restart my PPC @ 6 am after creating a backup. So in a way, this problem was very benifical to me - I now have a fresh backup of all the software every morning and the device reboots every morning without my intervention (no BT errors, no WiFi errors, etc).
poga said:
I also didn't have the Goodlink software installed . My solution to the problem was: I installed the Sprite Backup software and set it to automatically restart my PPC @ 6 am after creating a backup. So in a way, this problem was very benifical to me - I now have a fresh backup of all the software every morning and the device reboots every morning without my intervention (no BT errors, no WiFi errors, etc).
Click to expand...
Click to collapse
Good idea!!! :lol:
Tried the 'g' hack to get recognised on wifi G only networks and now my wifi won't connect to anything.
Uninstalled the cab from add/remove programs, but I'm still stuffed.
Can anyone help with a suggestion or the original registry values for the wifi?
I originally did it via the hack compiled in cab form, then manually set the registry via the msmobiles site, then tried another suggestion - only joy I have is seeing but being unable to connect to any network.
Before it was 'fussy' anyhow, not wanting to connect to some networks and I was hoping to improve it's connectivity to include those set to G only.
Help...
Try hard resetting your phone, this should restore the original settings fully and it should work again.
Tried that, no difference. Also after hard reset (0) my boot loader splash screen is still the same (customised) and I am now unable to upgrade the rom it seems. Tried what I did before, only switching to the CE from my original O2 rom, and it examines device ok, disconnects it ok, restarts it when the device boots up and the rom upgrade utility sits at 'do not turn off' doing nothing....
Update, put device into boot loader mode, flasher now worked, re wrote the rom and setup again, now wifi works again. Long way round hey, even hard reset didn't work!
Not sure if this was on the fault of my carrier or not, but I actually had this problem before and resolved it once.
I was running 3.60.1 and even tho I had Unchecked "Enable Advanced USB Connection" or whatever under USB to PC in the Connections Tab, My phone would not connect to WMDC (I use Windows Vista). I would just connect to get my contacts via Bluetooth, which worked fine.
I am a heavy user of tethering via USB as I like to charge the phone while I am connected. 3.60 series has been pretty good...I haven't had a complaint really since I upgraded from 3.0 (Which IMO is a bit more stable but I'm not sure why). Every once in awhile, I lose connection. I'm not sure why it does this. I'm using radio 1.48 and I have been using it for both 3.0 and 3.60. I had problems using 1.50 as data connections would drop instantly...so I never caught on to that radio. I am located near the NYC Metro area.
The latest problem I had was...sometimes my data connections would drop and would not reconnect without restarting the phone. I'd SR the phone and all of a sudden during the boot (while still connected to USB), my WMDC picks up the device. Not sure why it chooses to do it after I've had the ROM Flashed for several days now...but I go ahead and set it up only to see my phone assumes a permanent Flight Mode. Under Comm Manager, I am unable to switch back to Phone Mode. I do not have access to Phone settings. I cannot even open my dialer.
I've done it before and I don't save that many new things to my phone...so I went on to HR. After HR...the phone was completely unstable. During the loading of the "customizations" (which correct me if I'm wrong...is the EXTRom), it will install everything and then hang after finishing the last one which I believe was the theme of ATT.tsk.
Frustrated, I decided to flash back to 3.0 I still use 1.40Oli (HardSPL V6) which was always fine and I was never able to update to 2.10Oli for I have weird issues with SSPL and Vista. I do everything normally...I get to the progress screen. It hangs. No problem. Run RUUWrapper again...bootloader screen is accessible and my SPL and HTC_BOOT should be unaffected. Still hangs. I try to flash a radio...hangs. Almost everything I try to flash...hangs.
I've tried multiple USB Cables...thinking that was the problem...same problem though. It gets all the way to the progress and the Bootloader screen recognizes when its plugged to the USB so I don't think that's the problem.
My phone is stuck in bootloader right now and nothing will flash to it. No matter what it will get to progress and load 0% of any NBH I try to flash.
The main point of this post:
1. What caused 3.60.x to not connect to WMDC from the beginning via USB...only to do it randomly later?
2. What caused the corruption to the ROM leading me "GSM-less" stuck in Flight Mode and no access to anything to turn it back on to Phone Mode?
3. What is the cause of my phone not updating any NBHs I try to flash (OS Only/Radio Only/Original Shipped) ROMs?
I'm not sure if I was the only one receiving these errors. I have not updated my signature in awhile but I was running:
HARD-SPL V6: 1.40.Oli
Radio: 1.48.00
ROM: VP3G 3.60.1
Thanks for your help in advance.
I had to soft reset my orbit the otherday and since then have been unable to sync with my pc.
I have tried re installing activesync and soft resetting the orbit with no joy. when I select activesync on the orbit I get the message displayed in the attached jpeg.
I would rather not do a hard reset as some of the programs I use (particularly DrugDoses) use a device key for registration which is changed whenever the device is hard reset.
Any help and advice would be appreciated.
Forgot to add, I am using XP pro and my other WM6 device has no problems so the problem must be on the orbit.
ROM: 3.4.206.2 WWE
ROM Date: 8/31/07
Radio: 02.98.90
Protocol: 4.1.13.47
Same problem
I have the same problem since installing B&B 4.3 GER on my device. I should mention that I am using Vista.
Ideas, anybody?
I had the same problem when i was running B&B 4.3 whilst using xp. At first i thought it was a bad connection from the phone to the mini usb cable (as i manange to get connected whilst bending the wire). I managed to get a connection after 2 days of trying. I then reflashed the phone with a different ROM & all was well again. For some reason some people are affected by this whilst others arent. No idea why, but there is a conflict somewhere which was resolved once i changed to a different ROM. Hope this helps. But dont dispair cos you will eventually get a connection & then you can reflash.
On PPC, You could try looking at connections, USB connection and make sure advanced usb is disabled. May help.
I've searched but can't find the answer to this one - sorry if I've missed it somewhere. I have an unmolested T-Mobile UK MDA Vario 2 and I'm trying to install the official TM UK WM6 upgrade ROM.
On my desktop PC (which is properly paired to the phone through ActiveSync to sync with Outlook etc) running the exe results in a grey box with red text saying "Checking files on your PC" forever unless I unplug the phone. Then it will eventually launch the wizard. If I plug the phone in again and wait until it's synced and "Connected", the wizard will go all the way through to checking the existing version and starting the upgrade. However, when the upgrade starts the progress bar stays at 0% and the phone turns off!! Eventually it times out with a 260 error, and no changes have been made to the phone. The PC is running XP, but the only fixes I've seen for the 260 error are if you're running Vista?
I've also tried on my XP laptop - this isn't paired, so the connection through Activesync is just as Guest. The update still does the strange thing with the "Checking files on your PC" box if the phone's plugged in, but unlike the desktop PC the RUU won't talk to the phone at all - connection error before it can even verify the existing ROM version.
Can anyone help? I've been waiting for months to get WM6!
Cheers,
Tim
Phone just turns off?
OK, so now I've done a hard reset on the phone, paired it up to my XP laptop and told it not to sync anything. Now I get to the same stage as I do on the desktop - i.e. the phone switches itself off when the upgrade begins (at 0%), then the RUU times out with an error 260!
One odd thing I noticed is that if I plug the phone in with "Advanced network functionality" enabled (which it is by default) the PC tries to connect it as a new 10mb network card!? However, the RUU does the same thing whether this is enabled or not.
Getting desparate for help now - I've tried 2 different machines and even cleared the phone completely, what more can I do?
Cheers,
Tim
Try flashing from an sdcard. There are quite a post on it here, if you do a quick search you should be able to find the information and hopefully get your device upgraded.
It might be worth installig spl V7 from here before hand just in case anything goes wrong.
http://forum.xda-developers.com/showthread.php?t=296722
Working!
Thanks for the reply. Finally got it flashed using the instructions from here:
http://forums.cingular.com/cng/boar...thread.id=42389&view=by_date_ascending&page=1
Basically, you have to:
- Connect using Activesync and let it finish syncing.
- Start RUU.
- Activesync will close - ignore it and carry on.
- Eventually the phone will go into debug mode.
- Continue through the wizard - it won't be able to identify the existing rom version but this seems to be normal.
- Let it finish!
I was fiddling when Activesync closed - strangely, by disconnecting, restarting AS and reconnecting the wizard carried on and even identified the existing rom properly! It seems that it needs AS to connect to the phone initially, then it closes AS but keeps the USB connection open for the update.
Hope that helps anyone else with the same problem.
Cheers,
Tim