yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Apps and Games] lover:
v3 has some bugs when sending unsuccessful sms and doesnt close. also quick add function on screen in previous version seems better IMHO, but thanks for the great software. i have niticed that voipbuster.com linked your 2.2 version for download ;)
[Windows Mobile Apps and Games] Rhapsody:
Yeah, I'll send them a new version when it's done. (v3 is still beta :))

I'm gonna look at your suggestions. The quick add function is already mentioned. I understand that it was a handy feature, but since I want to support smartphones as well, i can't put a button on screen anymore. Smartphones don't support buttons.
[Windows Mobile Apps and Games] Rhapsody:
Hmm, the 'à' is replaced by 'a' at my phone...

This cannot be something device/language specific.
[Windows Mobile Apps and Games] A&A:
Rhapsody: Hmm, the 'à' is replaced by 'a' at my phone...

B&B: Strange! Did you try &, à, è, ì, ò, ù (in lower case) in other text input programs (Word, Notepad etc.) on your device/s?

Rhapsody: This cannot be something device/language specific.

B&B: I agree, it cannot be: Proof of it is that in all other text input programs these characters work fine and on the same PPC VoipSMS v.2.4 performs also fine... I hate to say this, but it really looks like it is because of something that doesn't sit right with the various v3x releases. :(

Hope you will soon find that damn bug and step on it :D
[Windows Mobile Apps and Games] nazbouh:
I have a problem with the interception.

I disabled the option (se below my config file) but it keep intercepting all messages ! So I phone wakeup on a new message, I see the "working cursor" of your app and then I wait ... wait ... wait sometimes many minutes till I finally see my sms coming. It's very frustrating :(

Why does the app try to intercept the message if I said I don't want to store any incoming message, I only want to send sms with it nothing more.

Is there anything I do wrong ?

had to remove the app because of this (always afraid to lose a sms, lost some when theree was the white window opened during intercepting before) :(

<?xml version="1.0" encoding="windows-1252"?>
<settings>
<setting key="Startup"><![CDATA[NewSMS]]></setting>
<setting key="Language"><![CDATA[en-US]]></setting>
<setting key="Countrycode"><![CDATA[33]]></setting>
<setting key="Autocomplete"><![CDATA[0]]></setting>
<setting key="AutocompleteDelay"><![CDATA[0]]></setting>
<setting key="DisplaySip"><![CDATA[0]]></setting>
<setting key="DefaultAccount"><![CDATA[VoipBuster]]></setting>
<setting key="Favorites"><![CDATA[1]]></setting>
<setting key="FoldersPassword"><![CDATA[]]></setting>
<setting key="StoreSMS"><![CDATA[none]]></setting>
<setting key="Interception"><![CDATA[none]]></setting>
<setting key="InterceptionDisplay"><![CDATA[none]]></setting>
<setting key="MyTexts"><![CDATA[1]]></setting>
<setting key="ExitAfterSent"><![CDATA[1]]></setting>
<setting key="FontSize"><![CDATA[9]]></setting>
<setting key="SoundSent"><![CDATA[]]></setting>
<setting key="SoundFailed"><![CDATA[]]></setting>
<setting key="SoundInterception"><![CDATA[]]></setting>
</settings>
[Windows Mobile Apps and Games] Rhapsody:
Very strange. Have you tried reinstalling the app?

I'm using v3 daily (also testing with and without interception) and I don't have any problems.

If you're able to, can you check the registry?

Under the key "HKLM\Software\Microsoft\Inbox\Rules" you can find all applications that intercept messages. I'm wondering if, and how many times, VoipSMS can be found at that location.

And B&B can you PM me your e-mail? I'd like to perform some character-tests. :)
[Windows Mobile Apps and Games] nazbouh:
I checked the registry. I found one key named VoipSMS with some subkey inside. I deleted it and reboot my phone. I reinstalled your application and now it's back to normal :)

thanks for the tips !

Note : Maybe when we save the options and say we don't want to intercept sms it's a good thing to delete the key (in case of it been created a long time ago).
[Windows Mobile Apps and Games] Rhapsody:
Normally it deletes the key automatically. :-) Maybe it was an old key from version 2.4.
[Windows Mobile Apps and Games] dodo34:
Does this work with Touch HD ?
[Windows Mobile Apps and Games] Rhapsody:
Not tested by myself, but it should work.

Works fine on Touch Pro and Touch Diamond for example. TouchHD doesn't differ so much (except screen size)
[Windows Mobile Apps and Games] A&A:
Hi Rhapsody,

Please take a look at the uploaded (zipped) .gif to see the error's details I get when I receive a SMS that contains symbols.

The inbox folder gets corrupted and all its content becomes inaccessible.

This workaround fixes it: Edit with Notepad the inbox.txt file by removing all symbols (they look like small square shaped outlines). Inbox.txt must be then saved back in the VoipSMS installation folder.

In your opinion can this have anything to do with the fact that v.3 (at the present stage) does not really seem to "digest" special characters? :D

Thanks in advance for your feedback :)
[Windows Mobile Apps and Games] nazbouh:
When I write a sms I can't PASTE the number in the 'To' section. I can only write (it's annoying if I have the number from an email or internet, I need to switch all the time to write it down)

if I send a sms with a number I wrote myself, it isn't store in the sent item box. I see the date of the message but the recipient is lost.
[Windows Mobile Apps and Games] Rhapsody:
I'm gonna take a look at it next week. (B&B and Nazbouh)

Thanks for reporting!
[Windows Mobile Apps and Games] Rhapsody:
Can you send me an example inbox.txt containing some special chars? (don't forget to filter out the private messages :P)
[Windows Mobile Apps and Games] dodo34:
which version should i use for the Touch HD ?
[Windows Mobile Apps and Games] Rhapsody:
You can try the last (beta) version which is posted a few pages ago. (version 3.0)

Or you can use the stable 2.4.0 version which can be found in the very first post. You need the PocketPC version (not the SmartPhone version)
[Windows Mobile Apps and Games] dodo34:
which version should i download for touch hd ? PDA or smartphone ?
[Windows Mobile Apps and Games] Rhapsody:
See above ;)
[Windows Mobile Apps and Games] A&A:
Hi Rhapsody,

Sorry for the late reply!

Here you have a (smudged for privacy reasons) screenshot of the corrupted inbox.txt

Unless you delete (with Notepad) the square shaped outline (which you can see in the attached thumbnail) VoipSMS inbox remains completely inaccessible!

By the way I just received 2 SMS's right after each other:

- The 1st one corrupted my inbox (it's the one in the attached thumbnail)

- The 2nd one could not be taken into the (just corrupted) inbox and I lost it :(

Frankly the & à è ì ò ù issue is much more disturbing than the above problem, which seems to occurr only once in a blue moon and can be fixed anyway with Notepad in no time!

I really hope you can do something... :D
[Windows Mobile Apps and Games] Rhapsody:
Ok, thanks.

I want to look at it this week. Already tested with sending a message via VoipBuster to my mobile. Special characters are simply removed. (più grande becomes pi grande) But further, no crash of VoipSMS.

Now I want to test it with two mobiles.

About the character replacements. I was thinking about making it configurable. That should fix all problems I think...
[Windows Mobile Apps and Games] Rhapsody:
Ok, back again.

I'll contact you about this via PM. That's a little bit easier I think :)
[Windows Mobile Apps and Games] A&A:
That sounds just great!!! I àm rèàlly lòòkìng fòrwàrd tò thàt :D :D :D

PS: Hope you had the chance to see my reply to your PM.
[Windows Mobile Apps and Games] Rhapsody:
Good evening,

Here's a new version with some small fixes:

- Recipients field has clipboard support now.

- Inputpanel will be hidden when you close the application.

- Replacement of special characters (part XVI :))

Edit: Due an error your inbox/drafts/sent items can be emptied. Therefore download link removed. New version will be published soon.
[Windows Mobile Apps and Games] A&A:
Hello Rhapsody,

DISREGARD THIS POST - FALSE ALARM - SORRY

I am sorry that I have to say this because I am sure that you worked really hard to achieve some improvements, but beside not functioning this version crashed TWICE my device and I resorted in a hard reset :(

Are you sure that this is the file you wanted to upload?

Kindly double check on your device/s and eventually reupload the right file.

Tnx
[Windows Mobile Apps and Games] Rhapsody:
That's very strange and frustrating B&B.

I installed this version on my phone as well and it works just good. No crash, no error.

You didn't get any error message?

Edit: when I go to Folders -> Inbox or Folders -> Sent items I get an error. I'll look at this this afternoon. Is this what you meant?
[Windows Mobile Apps and Games] A&A:
I gave it another shot today and reinstalled the same cab... I must admit I was a bit skeptical after yesterday's (very unusual and irresponsive) behaviour of my PPC.

This time no crash: Yesterday's freezing must have been due to something else but since it occurred

exactly

in coincidence with the new VoipSMS installation I assumed that to be the culprit. My apologies for the false alarm! I will edit my previous post right away.

Regretfully I see that the famous characters are still not working. Do they work on your device?

Since I had a gut feeling that some other applications and/or registry tweaks might have interferred and caused conflicts (to avoid posting another stupid FALSE ALARM) I hard reset and reinstalled your latest VoipSMS cab in a "clean" environment... Unfortunately, same result :confused:

Awaiting instructions... Over and out :)
[Windows Mobile Apps and Games] Rhapsody:
Good to hear B&B.

I've found a possible bug:

messages are now saved in Unicode format. (Unicode is a encoding style which supports all characters in the world.)

Required: open your inbox/drafts and/or sentitems files (can be found in the VoipSMS directory) with Notepad and save them in unicode format.

If you don't do this, messages can be lost.

So make a backup to be sure!

A new version is attached:

- Selected folder fixed in Folders screen (menu -> go to)

- Recipients field has clipboard support now.

- Inputpanel will be hidden when you close the application.

- Replacement of special characters (part XVI :))

@B&B: Check the screenshot attached...
[Windows Mobile Apps and Games] A&A:
Screenshot of v.2.4

Take a look...
[Windows Mobile Apps and Games] Rhapsody:
As far as I know, VoipBuster does not support these characters. So therefore these are replaced by VoipSMS. That's what I intended to do.

When I send a message with the Windows client these special characters are removed from the message...

So what I want is:

You type: Riuscirà il nostro eroe a ritrovare il più grande diamante del mondo?

You send: Riuscira il nostro eroe a ritrovare il piu grande diamante del mondo?

Recipient receives: Riuscira il nostro eroe a ritrovare il piu grande diamante del mondo?
[Windows Mobile Apps and Games] A&A:
If you do not mind (and if it is technically possible) I would rather have the same (v.2.4) situation as shown in the screenshot I uploaded yesterday.

I would prefer this scenario:

I TYPE: B & G porrà più perchè così otterrò (

all is correct

)

I SEND: B & G porra piu perche cosi otterro

RECIPIENT READS: B & G porra piu perche cosi otterro

instead of this one:

I TYPE: B & G porre piu perche cosi otterro (

pretty screwed up

)

I SEND: B & G porre piu perche cosi otterro

RECIPIENT READS: B & G porre piu perche cosi otterro

Hope above example is clear.

"...As far as I know, VoipBuster does not support these characters..."

I don't suppose VoipBuster changed this recently just in coincidence with the new release of VoipSMS v.3x, right?

"...So therefore these are replaced by VoipSMS..."

I wonder why v.2.4 did not replace them if VoipBuster never supported these characters.

It would be logical (as implemented in v.2.4) that the client (VoipSMS) should (at the stage of composing text) remain unaffected by the encoding standards of the service provider (VoipBuster).

Frankly I would prefer that at least on my end of the SMS I don't have to struggle with text input, especially considering that I use predictive keyboards... Never mind if the recipient misses a couple of accents.

I write often in foreign languages (not only Italian) so for me this function is really crucial and if it wasn't because of the new (very nice) features you introduced in v.3 I would continue using v.2.4 which had zero problems with chars.... Would it be a totally absurd idea to modify v.2.4 (by adding the new v.3 features) rather than going nuts over fixing the current version? :eek:

Please don't kill me for suggesting this. :D
[Windows Mobile Apps and Games] Rhapsody:
I'm gonna think about this. I feel we're close to a solution so that makes me happy.

It will take some time because I have to write it down and do some tests. I'm sure I tried it before but in fact: no replacements should work then...

When this subject is ready I will start on the Smartphone compatibility to work towards a final release. Most issues are fixed I think. I use it every day and haven't found any issues lately.
[Windows Mobile Apps and Games] A&A:
Rhapsody: I'm gonna think about this. I feel we're close to a solution so that makes me happy. B&B: I share the same feeling: One way or another this is soon going to be fixed. I repeat, if for you it is easier/quicker to "throw in"

only

a couple of the new features in the "good old v.2.4" it is very fine with me :p... So I could finally get off your back :D... PLUS, I get to keep the famous "Add" button, which I really enjoy!

Rhapsody: It will take some time because I have to write it down and do some tests. I'm sure I tried it before but in fact: no replacements should work then...

When this subject is ready I will start on the Smartphone compatibility to work towards a final release. Most issues are fixed I think. I use it every day and haven't found any issues lately. B&B: Yes, I also use it every day and beside the annoying issue of the & à è ì ò ù (which, as you noticed, can pop up in every second word) I cannot report any other bugs. Final v.3 should be soon unveiled. :)
[Windows Mobile Apps and Games] Rhapsody:
No v 2.4 will soon be history ;) version 3 contains way to much new features (visible and invisible) to be thrown away.

The Add button will not return. Instead a menu item is added for it. This is for Smartphone compatibility. Having two interfaces to maintain is not an option. I'm sorry about that. Don't forget that there's autocomplete. I use it a lot and normally I don't even use the contacts-combobox.
[Windows Mobile Apps and Games] Rhapsody:
ok B&B

I moved the replacement of special characters to the background. So it will replace them when you hit the send button.

Let me know if this is what you meant :)
[Windows Mobile Apps and Games] A&A:
YEEEEEEESSSSSS you did it man!!!! :D

I guess this ends the beta period of v.3, right?

Thanks again :)

Too much enthusiasm expressed too soon! ... The local display is PERFECT but after sending a SMS to my other PDA (also running the same version of VoipSMS) Inbox, Drafts and Sent items on

both devices

are no longer accessible and on both displays popped up this error... :mad:

Hopefully you can resolve this situation,

Tnx :)
[Windows Mobile Apps and Games] Rhapsody:
Did you convert the inbox.txt (and the others) to unicode format?
[Windows Mobile Apps and Games] A&A:
Either way I get errors! :mad:

Did you not get errors on your PDA when you tested this release? :confused:
[Windows Mobile Apps and Games] Rhapsody:
Nope.

I sent several messages (with and without special chars) and all is accessible.

The error looks equal to the error I had when I did not convert my files to unicode so therefore I asked. But it's a general error.

Can you examine your inbox.txt. If it was not unicode, the last message is added as unicode, so it might look a little bit strange.

What you can try as well is to remove (that means backup) your textfiles and start with an empty inbox.
[Windows Mobile Apps and Games] A&A:
Ok, this is what I did:

1) I reinstalled (on a freshly hard reset device) from scratch the latest release

2) I completely reconfigured the latest release from scratch all options, accounts, favorites etc.

3) I sent a normal SMS (without special chars): It went fine and was received fine

4) I sent a SMS with this text: "& à è ì ò ù" (without "quotes") and it produced errors aborting the sending. I tried several times and the message was never sent/received, only errors where displayed.

5) I went to the installation folder to check out the various elements, here is what I found:

The txt files are in Unicode format.

The SMS indicated above (point 3) is listed as I wrote/sent it.

The SMS indicated above (point 4), was NOT sent, was correctly displayed in VoipSMS input field and is (wrongly) showing (in sentitems.txt) as following:

^12032009^1054^Private Name (+Private Number);^& a e i o u^0^1

6) I reproduced the exact same situation but using VoipSMS v.2.4, read the results below:

The txt files are in UTF-8 format.

The SMS indicated above (point 3) is listed as I wrote/sent it.

The SMS indicated above (point 4), was sent without errors, was correctly displayed in VoipSMS input field and it is (also correctly) showing (in sentitems.txt) as following:

^12032009^1124^+Private Number^Private Name^& à è ì ò ù^1^1 Please note that in v.2.4 the number comes before the name and it is NOT in parenthesis... I guess that this difference between the 2 versions is irrelevant.

The recipient however received for each accentuated vowel this: A (letter "a" in upper case without accent) and the symbol & was simply omitted.

7) I launched (from the laptop) VoipBuster and I sent a SMS with this text: "& à è ì ò ù" (without "quotes"). The SMS was sent and received without any problems and showed on both ends the text exactly as it was input. This would indicate that VoipBuster does support symbols and accentuated vowels.

The SMS was (also correctly) showing (in inbox.txt) as following:

^12032009^1209^Private Name (+Private Number);^& à è ì ò ù^0^1

Frankly at this point I do not know anymore what to tell you.

The only thing I can say is that whenever my PDA's predictive input software, which contains several hundred words with accentuated vowels in its database, will suggest a word with an accentuated vowel I will not choose it and instead I will finish to type the word without accentuated vowel. I will stop using symbols in my SMS's.

Bearing in mind the above I really hope that you will manage to do something in order to resolve this very inconvenient situation.

Thanks again for your patience and valuable support :)
[Windows Mobile Apps and Games] Rhapsody:
I'll try to work on it this weekend, but it will be hard.

The layout of the messages has changed in version 3.0. (mostly about the recipients part)

The textfiles are saved in UTF16. (UTF 8 is not full unicode as far as I know)

I'll test with the messages you mentioned and maybe I have to turn the character replacement off...

So for my understanding:

What you would like:

1. You compose a message

2. You send the message

2a. Message is checked and special chars are replaced

2b. Message is saved in original form.
[Windows Mobile Apps and Games] A&A:
I) I would like to be able to type a SMS which contains also: & à è ì ò ù.

II) These characters (& à è ì ò ù) should show on my display as such, so like this: & à è ì ò ù

III) The SMS should be sent without errors

IV) The recipient should receive & à è ì ò ù (IDEAL) but it would be acceptable if the recipient could receive & a e i o u

V) Message should be saved in VoipSMS with chars shown like this: & à è ì ò ù

Thanks again for your efforts Rhapsody, I really have no words to show you my appreciation :)
[Windows Mobile Apps and Games] Rhapsody:
Try this one B&B
[Windows Mobile Apps and Games] A&A:
Here are the results:

I type this SMS: & à è ì ò ù.

EXCELLENT!!! The characters on my display look like this: & à è ì ò ù!!!

But... the SMS will NOT be sent!!! Error - Error - Error - Error and so on.

The funny part is that when I try to send a SMS without any of the above chars (so just regular text) I get the same sort of (mis)behavior!!! :confused:

Is this a "special" edition of VoipSMS (which keeps the VoipBuster credit unaltered) inspired by the current economical crisis? :D

Ever heard of the "zoutvaatje zonder gaatjes voor zoutloos dieet"?
[Windows Mobile Apps and Games] Rhapsody:
Hmm strange... I've tested this and it does exactly what you said in your previous reply. (not the IDEAL situation but the acceptable one :P)

what kind of error do you get?
[Windows Mobile Apps and Games] A&A:
Well, the acceptable situation would really be acceptable... Looking forward to seeing that on my device :D

... Hope the attached screenshot will be of help to identify the problem... Good luck :)
[Windows Mobile Apps and Games] Rhapsody:
These are situations that I'm happy that the errormessage is clear! :D

The error is the 'famous' voipbuster error. It reports error, but the message is delivered. (can you verify this?)

As I can conclude, the message is succesfully sent to the VoipBuster service. This service returns the xml-fragment you can see at the bottom. It says result = 0 and the description is 'failure'. In the past I simply ignored this message since the sms was delivered anyway... Maybe I've to ignore it again...
[Windows Mobile Apps and Games] A&A:
I wish I could share your happiness, but since I sent the SMS to my other number (from right hand to left hand) I can sadly assure you that the SMS's (I tried several times) were NOT delivered :mad:
[Windows Mobile Apps and Games] Rhapsody:
Can you try to send a message without the & sign?
[Windows Mobile Apps and Games] A&A:
Ok I type this SMS (without the "quotes"):

"saprà perchè partì avrò più & questo è tutto?"

I send (I am amazed that today I actually managed to send a SMS) and what is received looks like this:

"sapra perche parti avro piu"

It looks like whatever is after the "&" sign is simply omitted (along with the "&" sign itself!) :(

In the meantime I found another bug :eek: (which sadly is also on previous versions but I never noticed it): If you select and copy one single word out of the text you typed and paste it within the same input field (say in case you need to move one word from one sentence to another) the

entire

SMS text -instead of the single word which was selected/copied- gets pasted!!! :(
[Windows Mobile Apps and Games] Rhapsody:
Thanks for the quick respond.

I'm sorry that I have to ask you to send so many test-messages. This is because I'm not able to test it at my work over here.

I'll look at the copy paste function :)

And it seems like the & sign is causing the trouble. I do understand why, so I'll try to find a fix this afternoon/evening. (evening will be hard, since there's soccer on the tv :P)
[Windows Mobile Apps and Games] Rhapsody:
About the & sign. For now I only have a work around. Simply don't use the & sign.

I haven't found a better solution yet. (though I did not have a lot of time to look after it as well) The problem is simple. A url can look like this: www.nu.nl?var1=1&var2=2

then it contains to variables. (var1 & var2)

But if var2 contains 'Left&Right' then Right is considered as another variable and not as a value of var2.

Note to self: try %26 as a replacement.
[Windows Mobile Apps and Games] A&A:
Ok, noted... I will avoid using the & sign until you find a solution... Nice workaround dude! Did it take you long to figure it out? :D:D:D

What about the copy & paste bug? Did you have the chance to test if that happens on your device too?
[Windows Mobile Apps and Games] Rhapsody:
It took me a few days and nights, but finally I was able to show this workaround in public! :D

but I've got some good news. My 'note to self' worked.

The cut/paste bug is fixed as well. Thanks again!

Those are the only changes in the new version attached.