Is there any solution for postponing SMS sending when the GSM signal is not strong enough?
In other words - on the symbian platform the SMS is taken into the queue like Outbox and the system or app then performs a signal check on regular basis and send out the SMS once the signal is at adequate level. So you no longer have to worry about the SMS once you hit the SEND button. Is there something like that available on WM platform too?
id love to see a solution for this one too!
also if there's any programable sms sender so that you can send the date and time for an sms to be sent.. i think this one also falls under the category of sms postponing
Come on guys, no one knows a solution? What about sophisticated 3rd party applications supporting SMS scheduling like AdvancedSMS or InfoSharp are, (actually had no chance to try them out), anyone expirienced who can advice?
Hope this helps guys!
@xan:
how will this help?
http://www.freewareppc.com/communication/rahsmsii.shtml
Related
Hi there
For a while nowI've been experiencing problems with text messages not arriving, but they do end up in my sent items.
There is no real pattern to which messages do and do not arrive at the cellphone I'm sending them too, although I do notice that it ussualy are longer messages (i.e. a couple of lines of text instead of just 1 or 2).
I've tried 5 or 6 different roms in the last couple of weeks but I have the same problem with each of them so it is not the rom.
I've read somewhere that too much reflasig of your device can cause strange problems could this be what I'm experiencing? any help would be very much appreciated!
ive noticed this too! usually its quite a large text, along 3 sms amounts in one go. the recipent doesnt recieve the text but it is in my sent items. i didnt know whether it was the rom i was using , my operator or even a hardware issue but i know its damn annoying when sending important messages.
im on O2, which provider are you with?
I'm also on O2 and have occaisionally had this problem on my diamond, atom life and wizard. The way to avoid it seems to be....
1. Use Advance Config to turn on both Message Sent and Delivery notifications
2. When sending a message DO NOT close the messaging app until the notifications have been received. (if the message is more than one SMS long you will get multiple notifications)
For some reason, if you close the app too quickly, the message fails.
I'm on Vodafone NL
Thanx for the replies, I'll try your suggestions! hope it works, it's really irritating not knowing if my GF received my sms
Hi to All,
I have few questions to you regarding messaging – sending SMS and emails. I miss form my previous phones confirmation that SMS was delivered to the recipient. In Nokia it works like that the info is being displayed 5 seconds and then disappears. Quite similar it works in Sony Ericsson. In TP 2 I’ve manage to have so called report that the message was delivered which has form of SMS, which must be deleted like a regular SMS. Is there any other option to know that the message was successfully sent or was delivered?
Next issue I have encountered is lack of progress bar while I’m sending emails. If the email has attachment the sending process might take a while. In all phones I used to have there was some kind of progress bar while I can’t find anything like that in TP2 email application. This is annoying because I don’t know if there is progress of sending. Anyone has solved that problem?
And the last thing which I have noticed when using email application is attaching files. If the file is located in subfolder of the main folder it’s impossible to get access to it. Then it’s necessary to start operation with File Explorer (with which I have access to all folders) and use of Send as email function and then edit the email content. Not very logical.
All you thoughts and ideas are very welcome!
Have a nice day!
Max
PS. I’ve started to thinking about switching to Nokia N900 which seems to be more logical and intuitive in terms of software.
The way Windows Mobile handles sending SMS when in low or no signal areas is very annoying. If it fails to send the message it stores it in the drafts with a link to try resending it in the conversation view. You can tap the retry link but if it fails again it will store it in drafts AGAIN and now you have multiple retry links. When it succeedes it doesn't even remove the failed ones.
If someone could change it so that it will keep auto-retrying and wait until signal is back to send it, it would be great.
If that is too hard, is it possible to make it just show only 1 retry link in the conversation view and then auto-remove it once it successfully sends? I hate having to go to drafts and delete multiple messages.
Dear petard,
it seems as if nobody is intersted in developping such an useful hack in order to remove one of the most annyoing bug our PDA are provided with.
I'd like my PDA to look like a Nokia phone sometimes, even though I wouldn't need to..... but I wonder why such an advanced device as a PDA phone can't have a similar feature. It's really weird, I didn't expect Microsoft not to solve the problem
Agreed, this is highly annoying...
Worse yet is that if an SMS fails to be sent from HTC's TF3D SMS app, it actually appears in the stock WM SMS app's conversation view without a resend link, so you don't even know that it hasn't actually been sent.
this is so annoying and has drove me crazy since i got my phone back in april. i dont understand why all my older cell phones did this but my SMARTphone does not. i am constantly needingt this feature
Not sure what phone you are using, however with my HD2 if you use custom message client made by Death Angle then he has a built in auto retry sending message. It is quite a nice message client.
http://forum.xda-developers.com/showthread.php?t=741179
Hello chaps,
Part of the app I'm writing sends SMS messages to those in a contact list that the user chooses. I could select as many in a list as possible, and I've got the list in a ListView component on a form.
In another form, I've got the function to send the SMS, and it all works well - sending SMS's is quite easy!
But the trouble is that it takes a while, and stops my application from operating while its working. It may take something like 5-10 seconds to send two text messages.
I'm not so worried about the time it takes, but I would like to send the SMS as a background task - perhaps start a thread going with the function to send the SMS. This *almost* works, but I've now got the problem that I'm trying to access this ListView component from a thread inside another form - it doesn't work. I since realise that threads treat global variables as local.
Has anyone come across this problem? Has anyone found a way of sending SMS's as a background task?
This is all using VB.net.
Many thanks in advance,
Paul.
Thanks to all that replied...
I've managed to work it out, and it now sends as a background task. The solution was to have the functionality of the SMS sending as a new class, with all the data it requires within the class as public variables. Then, when you create a new class of that SMS sending functionality, you then populate all the stuff it needs to run, like the text message itself and so on, and set the thread going as before.
If anyone wants any more information, I would recommend this site which was most helpful:
http://www.devx.com/DevX/10MinuteSolution/20365/1954
MrPloppy.
I have Samsung galaxy S2 upgraded to 4.1.2 … Tests here apply to my machine, but you can be sure, they can be repeated on a lot of other phones. I can not be sure on which one.
When you have several SMS apps, if you sent SMS by one app, randomly one of the other apps sent same SMS again. Each app sent once… but phone sent in double, so network operator charge in double.
In table bellow in red I mark, where this issue is very likely. Example: You sent SMS with the stock ‘messaging’ app… then … these apps will potentially try to sent the SMS too… zero sms, chomp sms, go sms pro, kk sms, easy sms, messenger.
(The image will be added in some different time.)
It is likely, in different times, different programs to be activated. On more modern phones, downgraded to older android, it will be no odd; single SMS to be sent in triple, four times or more.
Usually, if you have bystander apps what sent SMS, they can try to be in service for you and turn on your 2G by themselves and promptly do them job. They no care if SMS created in other app. They just want to be in service to you. This is serious bug in most SMS apps, I know how to fix it, but let SMS apps developers contact me for details.
I notice odd cases. Here described.
Textra mark messages by other programs like sent. But they are not sent. The message sent by textra is invincible to other programs, before sent.
Inside the chomp program, messages sent over chomp are well… but other SMS apps see these messages like sent by the receiver. Some apps detect these messages like not sent, and it is unclear how they’ll send them. This research, I do it without to send SMS, because it is difficult to hunt this problem down to minimal details. Each time, different apps are activated. We are in multitask environment.
Go SMS pro import spam in the conversations. Textra filter this spam in separate conversation.
Next SMS is jealous. It do not love SMS composed in competition app. But SMS by Next are well accepted by these other apps. And they kindly can try to be in service.
Other apps see messages composed in Messenger like already sent.
Resume. SMS apps are not well designed to work cooperatively each with another.
Solution. Chose your favorite SMS app, only disable the stock SMS app, and leave single active SMS app in the phone.
Do you know better way to upgrade SMS functionality compared to replace the stock app with other one? ( Example: how to replace it with two apps? ) Let me know, in reply to this post.
Just now, chomp complained with special notification to me that it wasn’t able to sent the SMS composed in five other programs. All doubts are definitely gone. Once again: SMS apps are very friendly, industrious in care for your job, they do it in double. You compose in one… SMS sent by other, etc…