Here are some more tips and experiences that have worked for me using Windows XP. PLEASE comment:
- First you always have to remember to have RIM Desktop Manager loaded in Windows and showing "Connected" before you do anything related to getting the Pearl online. This includes checking the modem diagnostic in the Windows modem driver. As long as you get some AT commands back from the BB, the driver is installed.
- Use only the Standard 33.6 Modem driver. The 56K modem driver will not work according to what a T-Mob wireless data specialist told me. Don't worry, you aren't going to connect at 33600, it will be faster.
- As previous poster poined out, it is essential to install the Windows modem driver on one of the COM ports occupied by Pearl. Too bad this is not in any of the Tmob documentation. I would have 1 day more of life. Check your Device Manager in Windws for the RIM Virtual Serial Ports. Mine are COM4 and COM5 and I installed the Standard 33.6 Modem driver on COM4.
- Max Port speed 115200 on modem driver and the Dial-Up connection. This works fine and is much faster than EDGE can fully utilize anyway. You can name the dialer connection whatever you want. This isn't the OTA speed, but the internal connection speed used between modem and the lapop.
- I've been regularly using hardware flow control even tho some TMO instructions say "none". Note there is a setting for this in the modem driver and also buried deep in the dialer.
- Make sure under the Networking tab in your dialer that TCP/IP Connection > Properties button > Advanced button > "Use Default Gateway on Remote Network" is checked. This is required. However I've been able to connect with IP Header connection checked and also unchecked.
- Password and user name on dialer screen should be blank. In the Pearl the Advanced > TCP/IP setting should be APN=wap.voicestream.com (no quotes) and Password and user name on dialer screen should also be blank. Some of the instructions floating around say to enter your Tmobile.com Uid/PW in the dialer screen but I've never found this to be necessary.
- If you get stuck in "Dialer..." phase of logon and can't get past that, try cold booting the Pearl. Remove battery, wait briefly and replace. I have had this problem when disconnecting such as when online during Pearl auto-shutoff. I think the port gets left open or some crap stuck in there. It may also be helpful to remove the modem driver restart PC and reinstall. Does anyone have any better resolution to being snagged up in the "Dialer..." phase?
- If you get Error 736 TCP IP Control Protocol. There may be interference between a voice call and the Internet connection. You cannot use both simultaneously. However unlike analog modems you don't have to disconnect from Internet to make a voice call! Your phone seems to take priority. It will let u resume Internet activity as soon as hanging up.t
- If you get error 734 PPP this is a common error that even the front line Blackberry reps are familiar with. I was suggested to do these two things, and the first one worked.
1) try changing the "IP" in the extra initialixation string to "ip" (ie lowercase ip in quotes ) or vice versa. Note than in XP you cannot modify the extra initialization string and have your changes "stick" unless you uninstall the modem driver, reboot PC and reinstall the modem driver with the corrected initialization string. Tmob told me that in Vista you need to use the lowercase ip. Another tip is to make sure the string is only using double quotes and commas. No apostrophe's, periods or spaces. Amazingly, this little change of case was preventing me from connecting.
2) Try dialing *99***1# instead of *99#. This could also be added as an alternate dialup number.
- Make sure your dialer doesn't add anything to the dialing pattern such as dial 1+ or an area code.
-Here are four slightly different versions of the initialization string that are reported to work. But most likely, only one of them will work for YOU!
+cgdcont=1,IP,"wap.voicestream.com" (most common in the docs. worked for me but then stopped)
+cgdcont=1,ip,"wap.voicestream.com" (worked when above failed)
at+cgdcont=1,IP,"wap.voicestream.com" (I have not tried with the AT but works in some BB settings, not sure about Pearl in particular)
+cgdcont=1,,"wap.voicestream.com" (IP removed, reported working in this rabroad forum)
The latter three of these are a bit more unusual. What are your experiences with them?
- The number of possible settings can seem overwhelming. But most of the default settings on the modem driver will work as installed. You just have to add the modem initiatization string such as +cgdcont=1,IP,"wap.voicestream.com". Also make sure software compression and software flow control are always OFF.
- On BB Advnced TCP/IP check to see you are indeed set to APN=wap.voicestream.com
I had this entry disappear on me once and had to re-enter.
- With 4 bars EDGE I connect at 70-160K, usually about 110K. That's about 2-3x dialup speed. The wireless data specialist told me that customers connect at 200-800K but that is closer to Broadband speed. I have yet to see those speeds on the EDGE network.
Please ADD your experiences. There is a tough oyster shell to break through to get to the beauty of the Pearl. A well-tethered Pearl makes a very happy owner. Once you get it..
"Very Nice"
-borat
(posted via tethered Pearl)
