Connecting to the internet via GPRS

[shmi]

Does anyone know how to configure the Connections settings for internet access on the XDA I?

Now that it's unlocked from AT&T wireless, I am able to use it on my Cincinnati Bell Wireless (an AT&T affiliate - we don't have AT&T service available in Cincinnati). But there tech guys 'don't support that phone' so they can't give me the Access Point Name or WAP settings etc. to try and connect to the internet. I do have a GPRS connection and actually had already setup a WEBCLIENT account with them.

THanks.

[GamerDFWM]

1. Find out if you need a username, password, and domain for use with GPRS. You're "webaccount" information may be what you will use.
2. Find out what APN you need to use. It's kind of like a gateway, but it uses a name, as opposed to the ip address.
3. Set up a new connection using Celluar GPRS as the modem.
4. The phone will ask for the APN...
5. Try to go online with any app. It may ask you for your login, pass, and domain. Enter the stuff if needed. Some carriers (T-Mobile) don't require it.
6. Hit OK.


Good luck.

[ajperezcrespo]

I have a SX56. I get a good connection infact I can do everything (Ping,nslookup,NTP,DNS) But Explorer comes back with PAGE NOT FOUND (or something like it). I use ATT Wireless. Anybody, Somebody please.

[alorenzinlv]

Since installing the xda-developers special edition rom I can no longer access the Internet either. The Start... Settings... Autoconfig didn't have the USA- AT&T autoconfig settings. Start... Programs... GSM Band shows "Current: ERROR."

I've spoken w/ several AT&T techs and even reviewed all their webpages to re-set up the GPRS Connection, localhost settings, proxy settings, etc. The message from Internet Explorer is ""The page you are looking for cannot be found."

Anyone know the fix for what the special edition rom didn't have for AT&T service on autoconfig? I believe this is what is blocking Internet Explorer from accessing anything.

[alorenzinlv]

Be ABSOLUTELY SURE OF THE MODEL number you have. I used the Special Edition ROM from this forum and I ended up w/ Start... Settings... Device Info... Identity = PW10A1. My model was PW10B1. I couldn't upgrade properly w/ the Siemens free WM2003 upgrade after that.

I was finally able to upgrade to WM 2003 when I "cooked" my own ROM at http://xda.weblink.net. At the top of the screen, watch the large "space used" bar. If you've selected too many things to put in your new ROM file, it'll be overcooked and turn red. If necessary, uncheck some things you've selected. At the bottom of the screen, it's ESSENTIAL the NBF header string PW10A or PW10B matches your model number. Otherwise, the upgrade MAY NOT work, but it depends on how you install the cooked ROM file.

I used the xdatools-jeff.exe file avail in this forum @ http://forum.xda-developers.com/viewtopic.php?t=2189&highlight=xdatools. Scroll down to see the word NOTE in red ink for XDAtools link. When you move your mouse over it, a little window will open and at the bottom is "Download."

When you save this file on your computer, it'll install files on your computer. One I found in C:\Program Files\XDAtools\binaries was OSImageTool.exe. (I put it on my desktop to find easily.) When you click this OSImageTool, a screen opens up like the one you'll see in the forum at the link above. I clicked the three dots to the rt of the Source drop down box, navigated to my cooked ROM (saved it in my documents as an .nbf file), then selected the Destination box and chose "Device Memory (via Programme A)." Then I clicked Copy in the OSImageTool box.

I'm not sure if it'll always work this way for all XDA's, but after the copy to ROM was done, the Upgrade Utility started itself (!) and started to install the cooked ROM. I followed instructions to leave the XDA connected. When done (5-7 min), I undocked the XDA & shut if off w/ the unscrewed tip of my stylus in the smaller "no battery" hole (bottom rt of the XDA). After a FULL minute, I turned it back on and followed the prompts. VOILA! WM2003 w/ full Internet access AND it didn't seem to mess w/ the radio stack (I still have a good signal). GOOD LUCK! But do more reading on this site before you proceed.