[bell]

Hi,

I have a server-client application, which works fine on most terminals, including the 7650. However, there are a few issues with the 7650 which are really annoying. (I am testing this on FW3.12 since this is the most widespread FW-version in Norway.)

1) App freezes every time the GPRS connection must be set up. Once the phone is connected on GPRS HttpConnection() calls work fine and does not cause the application any trouble. I do all http-calls in a thread to have the application running properly while waiting for more data. This behaviour is really annoying, since the application does a poll every X minute. Which is just long enough for the connection to be dropped on the default configuration. Since the connection has been dropped, it must be set-up again to connect, and thus the app freezes again. The freeze lasts for the entire set-up period. Once the G gets a square around itself, the app responds normally again.

2) Every time the application must set up a GPRS connection, the user is asked which connection to use. I have set a default connection both globally and for the specific midlet. I have also configured the midlet so it is allowed to connect without asking the user first.

3) How to use the vibra-functions? I have read one thread suggesting to make a silent ringtone which only vibrates, and call the ringtone. I am not very familiar with ringtones and would like a confirmation that this will work before delving to deeply into the problem.

NB! I have never experienced any of these problems on any other device I have tested this application on. (3410, 3510i, 5100, 6100, 6610, 6800, 7210, 7250)


Thanks in advance :)

[bell]

You don't have to know the answers to all my questions to answer, I am happy with any kind of reply. I just find it strange that nobody else have experienced (and solved?) any of the problems I describe below?

Or are these problems fixed with higher FirmWare versions?

[Juggle4Evr1]

Hi,

about your problems 1) and 2):

maybe you should consider to make the time between your polls shorter. This may also be much cheaper for the user considering the GPRS costs. Here in Germany most providers charge GPRS in 10kB blocks and if the GPRS connection is closed and re-opened, a new 10kB block is started and also charged. So it's much cheaper to make requests more often to prevent closing of the connection.

I.e. the default timeout of many phones is set to 120 sek for GPRS conn. So, if you set your time between polls to 100 sek., it is still cheaper compared to setting it up to 10 min. Of course this is only the case if your amount of data to transmit is relatively low.

It may also solve your problems with freezing and having to set up the connection all the time.

Regards,
Juergen

[bell]

Hi, and thanks for the advice! :) I was not aware of the fact that most operators charge in 10kB blocks. Our application uses about 200 bytes for each poll. Quite a bit to save there :)

The problem is that the timeout varies from phone to phone. The 7650 I've been using now has a timeout (default) set to 25 seconds.

But you are right, this is a good way to solve my problems. Thank you very much! :)

I don't suppose there is a way to discover the timeout for the connection?

[Juggle4Evr1]

Hi,

no, I think there's no way to get the timeout to the Java application.

This 25 sec. Timeout is very strange (seems to be very short!). I have a setting here in my 7650 at "Tools->Settings->Data Call->Online time" which is set to 5 Minutes. It can also be set to "Unlimited". It can be set to a minimum of 1 minute. But I'm not sure this is the correct setting for GPRS.

For the 10kB blocks: YOu hav to look into the GPRS price tables of the providers. There you can find details. It different for each provider.

I have also experienced that there is a huge overhead of data when using HTTPConnection. When I transmit only 5 bytes, around 500 bytes are really transmitted over the network and maybe also charged.