Android Question PhoneSMS and generic failure

[HeX0R]

I've created an app to send sms-messages to GSM-Modules for configuring.
I'm using PhoneSMS to send them and check the deliverystate via PhoneEvents.

Anything worked as epected.

Now I had one customer who tried to send a sms under very bad conditions,
he said he had a bad connection to the mobile-provider where he was.

Whenever he tried to send a sms with my app, he got a generic failure as response.
Doing it directly with his phone, any sms was delivered flawlessly (but slowly...).

I'm a little bit confused now, shouldn't it be directly the same?
Or is there some kind of internal timeout for the confirmation?

 

[Erel]

There isn't any timeout and it should be the same. The default SMS app handles sending errors automatically. The message is queued and resent later.
You can turn airplane mode on to test it.

 

[HeX0R]

If I would use (optional for bad connections) the new send2-function without checking the confirmation, would it then be automatically send to this queue and handled by the phone?
Or should I do my own resending-procedure?
This could get tricky, I guess a Generic Failure could also be there for other reasons, so how should I know, that the bad signal is the reason?

 

[Erel]

The queue I wrote about it is maintained by the SMS app. It is not part of the OS. You can use Send2 and ask for the sent notification. If it failed try to send it later.

 

[HeX0R]

Thanks for your help so far, Erel.

I have now created a Messagequeue for the SMS using a timer and a List.
I'm wondering how things are working in b4a.
Is a timer working asynchronously, or in other words, should I secure the list access somehow?

 

[Erel]

The Timer_Tick event is raised on the main thread. You do not need to worry about synchronization issues.

However the activity / process life cycle may cause problems. Especially if the timer interval is large. In that case you need to use StartServiceAt instead.