Even after signing with T-mobile, Not able to connect to int

[indrakumar]

Hi T-mobile folks,
I am facing a issue on some of the Samsung devices. - SGH-T619, Samsung t 219, Samsung t 329

Issue - Not able to connect to internet, even after signing with T-mobile (using this link - http://portal.truenorthservice.com) . The device will get restarted, at getResponseCode(),

When I execute the below code on the SGH-T619, the device will get restarted.

Code :
---------------
public void sendRequest()
{
try
{
int nRc ;
String dis = "";
String errormsg = "";
connect_to_server();
connect_and_set_header();

System.out.println("Before getResponseCode..... ");
nRc = m_hCon.getResponseCode();
System.out.println("After getResponseCode..... ");
writeRecord("dsml nRC = " + nRc + " count = " + count);
}
catch (Exception e)
{
error = error + "\n" + (" Operation Failed 106: " + e.getMessage());
displayerroralert(error);
}
}


public void connect_to_server()
{

try
{
m_hCon =
(HttpConnection)
Connector.open("http://google.com", Connector.READ_WRITE, true ); // true == want timeout exceptions
}
catch (IllegalArgumentException exIA)
{
}
catch (ConnectionNotFoundException exCN)
{
}
catch (IOException ioe )
{
}
catch (Exception e )
{
}

}

public void connect_and_set_header()
{
try
{
m_hCon.setRequestProperty( "Content-Type", "text/xml" );
m_hCon.setRequestProperty( "Cache-Control","no-cache" );
m_hCon.setRequestProperty( "X-MVIP-Ver", "3.0.1");

m_outputStream = m_hCon.openOutputStream();
m_wireWriter =
new OutputStreamWriter( m_outputStream);
Thread.sleep(100);
m_wireWriter.write(strXml);

Thread.sleep(100);

}
catch (Exception e)
{
}

}

--------

Here, I am not getting any exception during Connector.open. The code till nRc = m_hCon.getResponseCode(); will get executed properly, i.e I am able to see the message "Before getResponseCode.....". Once the code line nRc = m_hCon.getResponseCode(); executed the device gets restarts.
In my app I am using https url, but the same issue is reproducible with google.com as well. I have selected "Samsung T619" for Samsung SHG-T619, during signing...
May I know what might be the reason, because I am facing this problem even after signing with T-mobile. Is it Signing issue with T-mobile?

[Takeshi]

Hello Indra and welcome back,

I'm bouncing this around here trying to see if we can narrow down the issue. From what I understand, the application works fine until it reaches getResponseCode(). After this the device completely shuts down and then restarts, correct?

Have you tried running the application in a simulator? If it works fine in a simulator but not on the device, it could indeed be a signing issue of some sort.

Thank you,
Takeshi

[indrakumar]

Hi Takeshi,
Thanks for the reply.

Yes - your correct. The api, getResponseCode(), will try to connect to the server to get the http response code.
Regarding the Emulator - I have not tried it, but I am sure it will works fine.

For me it looks like its something to do with T-mobile signing. Could you please try to run a sample application with getResponseCode() on SGH-T619, so that we can come to a conclusion soon. Thanks.

[indrakumar]

Hi Takeshi,
Regarding the Emulator - your talking about T-mobile emulator or Samsung emulator or general wtk emulator.
I am not able to find it out any T-mobile emulator, in Samsung emulator I have not find it out SGH-T619 emulator, but I tried in other device it works fine. If you know any T-mobile emulator then kindly share it out. Thanks.

[Takeshi]

Thanks for the clarification Indra,

Yes I forgot the simulator provided by the Samsung Mobile Innovator site doesn't have T-Mobile USA devices. You might try just a standard Java emulator, but that might not be worth the time since you've got it working on other devices in the past.

One thing I did notice is that you're using portal.truenorthservice.com instead of http://www.truenorthservice.com/tmobile.php. After discussing this with others here, we decided this is not likely your problem but you can always try to use the signing tool on that site so see if it provides results.

I'm having some other folks look at your code to see if there are any specific issues that might snag on the devices you've reported. Two questions they will probably want to know are:

1) On which devices did this App run successfully?
2) Which Channel/Aggrigator did you use to distribute the App? (You can send me a private message by clicking on my name if you'd like to keep that part confidential.)

Thanks for your help,
Takeshi

[indrakumar]

Hi Takeshi,
On which devices did this App run successfully?
=> The app runs on
With out T-mobile - All most all nokia, samsung, Sony, BlackBerry etc.
With T-mobile T series - Samsung SGH-T639 series works fine after Signing.

2) Which Channel/Aggrigator did you use to distribute the App?
=> Till not yet decided.

Thanks,
Indra..

[indrakumar]

Regarding the Signing URL - both are same.. means both are pointing to the same link internally.

[indrakumar]

Hi Takeshi,
Could you please confirm,

- Is the issue is with handset/T-mobile signing or with the Application. If it is with the app, then I will work on it. You can confirm this by running a simple app ( with just open and close internet connection ) on the these handsets and see if it able to make successful internet connections. If the app will fail to make the connection, then it is handset/T-mobile signing issue.

Thanks,
Indra.

[Takeshi]

Hello Indra,

I think I've narrowed down the issue to the OpenWave browser that is used on the devices you are having difficulties with like the T619. The T639 (and the Behold and Memoir and some other Samsung devices) use the Netfront browser instead. Even though your app may not be using the browser directly, the browser is much more integrated into the basic models and may be preventing the app from running that particular command.

Unfortunately, I don't have the facilities here to verify if a sample app works on the other devices but I'll keep looking into it.

Thanks,
Takeshi