Accidental discovery

[rkuppala]

Hi,

It seems to me that BREW 2.1 saves the socket connections during a voice call. I was able to continue using my socket related functions after I end my voice call (from BREW).

Does anyone know more about the specifics of this behaviour?

Thanks

[ruben]

Are you using MSM6100 phone? In MSM6100 (may require 1xEVDO network, I am not sure about that) Qualcomm says that you can have simultaneous voice and data call.

Usually, as far I know, if your application is using socket connection, it will not be destroyed even after it gets pushed into the background, unless other active application tries to use socket.

Qualcomm techsupport may be able to fill-in.

ruben

[Louie]

I suspect this really depends more on the network side than the BREW version. You have been able to do this since at least BREW 1.1 (maybe even 1.0, but I have never tried that version).

The key is the underlying network technology, whether you are using a packet service (eg 1x) or cicuit switched data (eg QNC). With 1x in dormant mode, there is no problem keeping socket connections open will making/receiving voice calls - I suspect this is what you are seeing. This should not be possible with CSD.

[rkuppala]

Louie,

When I saw the bhaviour on my 2.1 phone, the explanation you gave was exactly what I expected. But then the same code which ran w/o problem on the 2.1 handset did not run on the LG VX 6000. I was not able to just re-use the socket connections after the voice call w/o re-connecting sockets. May be I should look at the scenarios more carefully. Unfortunately I had to ship my only LG phone to a partner for demo. So I will not be able to investigate further till I get back the phone in a few days.

Coming to the phones, I have a BREW 2.1 curitel DD 500 phone but I have a spec sheet for this phone with a BREW 2.0 build which states that it is a MSM 5100 chipset.

I am not sure if there are any phones with EVDO capabilities yet.

Thanks

[Louie]

Sounds like a problem with the LG VX6000 then. The making/receiving of a voice call should not impact on your socket resources unless your suspend/resume logic does it.

[rkuppala]

Louie,

You are right. The data spec sheet for the LG VX6000 specifies that there is no support for Dormancy. Some of the upcoming phones (for eg: LG VX4600) seem to be having this feature.

Thanks

[Louie]

Even if the handset does not support dormancy, this should still have no impact on the socket connections. The "support for dormancy" means that the handset has the ability to see dormancy events as well as control the dormancy state of the handset. If the handset does not support this, then the application should unaware of the underlying network dormancy events, and thus socket connections should be unaffected.

This issue should be communicated back to LG through your carrier.

[flarb]

A bug in the LG6000? How could that possibly be! :)

[charliex]

i know i'm shocked

[kUfa]

Hehehe one more :rolleyes:

[rkuppala]

Hey guys,

Sorry to have mis-lead you guys.

The LG phone does not have the problem with continuing usage of open sockets after a phone call. I got my phone back and was able to do some tests and realised that the problem was with my server.

My apologies.

Thanks