A920 Tethered data connection issues

Forums › Spark New Zealand (including Skinny and BigPipe) › A920 Tethered data connection issues

Filterer

489 posts

Ultimate Geek

#9734 9-Oct-2006 18:14

I have been trying to get tethered data to work through my a920 on telecom.
The techies reckon it should be working and im on the correct plan etc

Spent an about 2 hours on the phone this afternoon

trying variuos things, installing, reinstalling drivers etc.
Managed to narrow the problem down to the command ATDT#777 - have a look at the modem log below

Ive tried to troubleshoot the connection in hyperterminal over the relevant com port and I can issue the modem with most AT command except the ATDT command always returns ERROR. Anyone know of or had this problem on the A920

10-09-2006 15:57:18.921 - File: C:\WINDOWS\system32\tapisrv.dll, Version 5.1.2600
10-09-2006 15:57:18.921 - File: C:\WINDOWS\system32\unimdm.tsp, Version 5.1.2600
10-09-2006 15:57:18.921 - File: C:\WINDOWS\system32\unimdmat.dll, Version 5.1.2600
10-09-2006 15:57:18.921 - File: C:\WINDOWS\system32\uniplat.dll, Version 5.1.2600
10-09-2006 15:57:18.921 - File: C:\WINDOWS\system32\drivers\modem.sys, Version 5.1.2600
10-09-2006 15:57:18.921 - File: C:\WINDOWS\system32\modemui.dll, Version 5.1.2600
10-09-2006 15:57:18.921 - File: C:\WINDOWS\system32\mdminst.dll, Version 5.1.2600
10-09-2006 15:57:18.921 - Modem type: SAMSUNG CDMA Modem
10-09-2006 15:57:18.921 - Modem inf path: oem34.inf
10-09-2006 15:57:18.921 - Modem inf section: SAMSUNG.Install
10-09-2006 15:57:18.921 - Matching hardware ID: usb\vid_04e8&pid_6601&mi_00&os_nt
10-09-2006 15:57:18.937 - 230400,8,N,1, ctsfl=0, rtsctl=1
10-09-2006 15:57:18.937 - Initializing modem.
10-09-2006 15:57:18.953 - Send: AT
10-09-2006 15:57:18.953 - Recv: OK
10-09-2006 15:57:18.953 - Interpreted response: OK
10-09-2006 15:57:18.953 - Send: ATE0V1
10-09-2006 15:57:18.968 - Recv: OK
10-09-2006 15:57:18.968 - Interpreted response: OK
10-09-2006 15:57:18.968 - Send: ATS7=60
10-09-2006 15:57:18.968 - Recv: OK
10-09-2006 15:57:18.968 - Interpreted response: OK
10-09-2006 15:57:18.968 - Sending user initialization commands.
10-09-2006 15:57:18.984 - Send: at&f
10-09-2006 15:57:19.015 - Recv: OK
10-09-2006 15:57:19.015 - Interpreted response: OK
10-09-2006 15:57:19.015 - Waiting for a call.
10-09-2006 15:57:19.031 - Send: ATS0=0
10-09-2006 15:57:19.031 - Recv: ATS0=0
10-09-2006 15:57:19.031 - Command Echo
10-09-2006 15:57:19.031 - Recv: OK
10-09-2006 15:57:19.031 - Interpreted response: OK
10-09-2006 15:57:19.031 - 230400,8,N,1, ctsfl=0, rtsctl=1
10-09-2006 15:57:19.031 - Initializing modem.
10-09-2006 15:57:19.046 - Send: AT
10-09-2006 15:57:19.046 - Recv: AT
10-09-2006 15:57:19.046 - Command Echo
10-09-2006 15:57:19.046 - Recv: OK
10-09-2006 15:57:19.046 - Interpreted response: OK
10-09-2006 15:57:19.062 - Send: ATE0V1
10-09-2006 15:57:19.062 - Recv: ATE0V1
10-09-2006 15:57:19.062 - Command Echo
10-09-2006 15:57:19.062 - Recv: OK
10-09-2006 15:57:19.062 - Interpreted response: OK
10-09-2006 15:57:19.078 - Send: ATS7=60
10-09-2006 15:57:19.078 - Recv: OK
10-09-2006 15:57:19.078 - Interpreted response: OK
10-09-2006 15:57:19.078 - Sending user initialization commands.
10-09-2006 15:57:19.093 - Send: at&f
10-09-2006 15:57:19.125 - Recv: OK
10-09-2006 15:57:19.125 - Interpreted response: OK
10-09-2006 15:57:19.125 - Dialing.
10-09-2006 15:57:19.125 - Send: ATDT####
10-09-2006 15:57:19.125 - Recv: ATDT#777
10-09-2006 15:57:19.125 - Command Echo
10-09-2006 15:57:19.125 - Recv: ERROR
10-09-2006 15:57:19.125 - Interpreted response: Error
10-09-2006 15:57:19.125 - Hanging up the modem.
10-09-2006 15:57:19.140 - Send: ATHE1
10-09-2006 15:57:19.140 - Recv: ATHE1
10-09-2006 15:57:19.140 - Command Echo
10-09-2006 15:57:19.140 - Recv: OK
10-09-2006 15:57:19.140 - Interpreted response: OK
10-09-2006 15:57:19.140 - 230400,8,N,1, ctsfl=0, rtsctl=1
10-09-2006 15:57:19.156 - Initializing modem.
10-09-2006 15:57:19.156 - Send: AT
10-09-2006 15:57:19.156 - Recv: AT
10-09-2006 15:57:19.156 - Command Echo
10-09-2006 15:57:19.156 - Recv: OK
10-09-2006 15:57:19.156 - Interpreted response: OK
10-09-2006 15:57:19.171 - Send: ATE0V1
10-09-2006 15:57:19.171 - Recv: ATE0V1
10-09-2006 15:57:19.171 - Command Echo
10-09-2006 15:57:19.171 - Recv: OK
10-09-2006 15:57:19.171 - Interpreted response: OK
10-09-2006 15:57:19.187 - Send: ATS7=60
10-09-2006 15:57:19.187 - Recv: OK
10-09-2006 15:57:19.187 - Interpreted response: OK
10-09-2006 15:57:19.187 - Sending user initialization commands.
10-09-2006 15:57:19.203 - Send: at&f
10-09-2006 15:57:19.234 - Recv: OK
10-09-2006 15:57:19.234 - Interpreted response: OK
10-09-2006 15:57:19.234 - Waiting for a call.
10-09-2006 15:57:19.234 - Send: ATS0=0
10-09-2006 15:57:19.234 - Recv: ATS0=0
10-09-2006 15:57:19.234 - Command Echo
10-09-2006 15:57:19.234 - Recv: OK
10-09-2006 15:57:19.234 - Interpreted response: OK
10-09-2006 15:57:19.250 - Session Statistics:
10-09-2006 15:57:19.250 - Reads : 47 bytes
10-09-2006 15:57:19.250 - Writes: 30 bytes

Thanks to anyone that can help

pɐǝɥ sıɥ uo ƃuıpuɐʇs

Jama

1420 posts

Uber Geek

Trusted

#48097 9-Oct-2006 20:26

where are you putting ATDT#777?

In the DUN profile the number to dial is #777
user: mobile@jamamobile
pass: telecom

Filterer

489 posts

Ultimate Geek

#48101 9-Oct-2006 20:53

Jama: where are you putting ATDT#777?

In the DUN profile the number to dial is #777
user: mobile@jamamobile
pass: telecom

Yea i know ive got all that sorted but when I try to connect it comes up saying harware modem failure
So in an effort to dignose the problem I looked at the modem log when it tries to connect (see above)

Anyway in hyper terminal you can connect to a modem and send the same AT commmands that would be sent to make a dialup connection. I did that to see if I could further diagnose the problem. ATDT#777 effectively means try to make a data connection to the phone number #777. This is where the problem lies as it always returns ERROR and nothing else.

pɐǝɥ sıɥ uo ƃuıpuɐʇs

Filterer

489 posts

Ultimate Geek

#49324 22-Oct-2006 23:16

Well after going around in circles for ages with complex technical support they have decided that the a920 is not actually supported!
If you have a look on the telecom website they have also changed the modem speed to n/a on the a920s page, it didn't use to say that it used to have a modem speed

pɐǝɥ sıɥ uo ƃuıpuɐʇs

freitasm

BDFL - Memuneh
79281 posts

Uber Geek

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#49331 23-Oct-2006 00:05

Interesting, because this phone on Sprint works as a modem.

Samsung A920 anual.
Samsung A920 FAQ.

Filterer

489 posts

Ultimate Geek

#49337 23-Oct-2006 08:42

Yes it is a little weird but as all all know Telecom has a little play with the firmware before they release it here and in their infinite wisdom have decided that they won't support it.....

I have tired another a920 as a modem and you get the same problem, after initilizing the modem it always gives up at the dialing stage as if there is no command to dial. Same problem using the windows dialer, telnet and the sprint connection program. In fact witht the sprint connection manager you can see all the data about the modem including if you are in 3G coverage, signal strength in dB and battery level, but it just can't dial... Grrrrr

pɐǝɥ sıɥ uo ƃuıpuɐʇs

NealR

426 posts

Ultimate Geek

Trusted

Lifetime subscriber

#49423 24-Oct-2006 08:27

Neither the Samsung nor Sanyo nor LG phones are able to use tethered data. i.e. you cannot use them as modems.

There are a number of technical reasons both in the handset and the network that prevent this. This is under investigaiton but is not expected to be resolved anytime soon.

The comments I write on this forum do not necessarily reflect the views of my employer and as such cannot be taken as official statements of my employer.

Filterer

489 posts

Ultimate Geek

#49426 24-Oct-2006 08:46

Thanks for your reply, in future it would be great that the powers at be communicate this with the web designers because for a long time the website said it had a modem that could go at xyz kb/s. Well theres no point saying that if it doesn't work....

I'd have to say its more of a network issue then a handset issue if none of those manufactuers work in NZ, Telecom had spent megabucks aligning their network with Sprint, why did this get left out? Well you probably can't answer this on a public forum but Ill ask anyway :)

pɐǝɥ sıɥ uo ƃuıpuɐʇs