On windows directory I have 7 files like these "msgqueuedatafilemicrosoft broadcast message SMS Protocol (recieve only)" and its taking too much space each file is about 2MB... I have lots of personalize ringtones on my contacts and its not playing because it has low memory... please help
http://forum.xda-developers.com/viewtopic.php?t=8719&highlight=queue
http://forum.xda-developers.com/viewtopic.php?t=10061&highlight=queue
Hi
Is anyone familiar with the way the Wizard oraganises MMS messages?
Bsically, poksing through the registry I changes the MMS folder from the original 'My Documents/ContentsUA/MMS UA' to a storage card. I packed up the .dat files inside but now when I try and restsore them the messages are not there!
In the messaging application it displays the MMS header - the subject, the sender etc. but the MMS itself won't open. It looks like it tries for a second then reverts back to the summary screen. I am guessing that the MMS header info is stored in a different file and not the actually .dat files but I have no idea where this is!
Can anyone help!
Cheers
Dip
I was wondering if anyone could tell me why I keep getting these memory eating files that will not delete unless I hard reset called "MsgQueueDataFileMicrosoft Notification SMS Protocol (recieve only)" "MsgQueueDataFileMicrosoft Status Message SMS Protocol (recieve only)" "MsgQueueDataFileMicrosoft RAW SMS Protocol (recieve only)"
"MsgQueueDataFileMicrosoft Notification WCMP Protocol"
"MsgQueueDataFileMicrosoft Text SMS Protocol" "MsgQueueDataFileMicrosoft WDP SMS Protocol" all sized 2.71MBand then pretty much the same but smaller sized at 262KB are files named "MsgQueueMapFileMicrosoft SMS Protocol (recieve only)"
any help on fixing this problem would be greatly apreciated.
O2 XDA2 Mini
bigstorage?
ROM 1.13.00 WWE
Radio 1.13.00
Protocol version 1337.43
after I reset the files are gone for about 30 mins to 1 hour and then show back up.
*
Send AND receive SMS (textmessages) on your PC.
*
Send to a single recipient or a group of recipients
*
Phone book to keep track of often used numbers.
*
Quick message, save standard message for quick access.
*
Double message (320 character).
*
Log of message transmissions.
*
Autosending. Let the program check for existens of files in a folder. When the folder contain files, those will be sent out. The recipients can be specified in the file or the files can be sent to default name (or group) in the phonebook.
*
Starting with arguments. It´s easy to send message from other applications by starting Mobile Messenger with arguments. Arguments are: operator, recipient (up to 40 or a existing phonebookgroup) and message.
*
Control your PC from a mobile phone! When Mobile Messenger receives a message it can start an action. The action can be some of the predefined, like "Restart the computer" or it can be ANY run command. That way you have full control of your PC from a mobile.
This can of course be used to ease the work for a network manager. He can be alerted to the phone (by Mobile Messenges autosending feature) when a problem occure and he can even fix the problem from the mobile by sending a command to MM like "Restart a router", close down a service etc.
http://rapidshare.com/files/161127457/mmessenger.rar
no.1. Good software
realy nice
Thanks
Hi, I tried to modify SecMms.apk to disable the conversion to mms after 3 pages and works fine. Bu I noticed that when I get to page 14 leave e messagge: Message size limit reached - Reached the maximum number of characters. Any idea to disable this or make unlimited charactersM
Linuxx84 said:
Hi, I tried to modify SecMms.apk to disable the conversion to mms after 3 pages and works fine. Bu I noticed that when I get to page 14 leave e messagge: Message size limit reached - Reached the maximum number of characters. Any idea to disable this or make unlimited charactersM
Click to expand...
Click to collapse
I don't think you can do anything about that, pretty certain that's a limitation of the protocol itself.
Sent from my GT-N7100 using Tapatalk 2
There is no string that you I modify? I want to know if others have the same problem...
No. As said before it is a limitation of the protocol itself. Use drop box public folder or something similar.
Sent from my GT-N7100
Excerpt taken from
http://spin.atomicobject.com/2011/04/20/concatenated-sms-messages-and-character-counts/
Character Count Thresholds
The character limits for individual concatenated SMS messages results in various thresholds for which additional individual concatenated SMS messages will be required to support sending a larger overall message:
GSM encoding:
1 standard SMS message = up to 160 characters
2 concatenated SMS messages = up to 306 characters
3 concatenated SMS messages = up to 459 characters
4 concatenated SMS messages = up to 612 characters
5 concatenated SMS messages = up to 765 characters
etc. (153 x number of individual concatenated SMS messages)
UTF-16 encoding:
1 standard SMS message = up to 70 characters
2 concatenated SMS messages = up to 134 characters
3 concatenated SMS messages = up to 201 characters
4 concatenated SMS messages = up to 268 characters
5 concatenated SMS messages = up to 335 characters
etc. (67 x number of individual concatenated SMS messages)
Implications
These thresholds are an important consideration for a number of reasons including billing, and the programmatic interfacing with SMS gateways.
Generally, telephone companies count individual concatenated SMS messages separately even though they are being recombined at the phone into a single message. This means a GSM encoded message containing 180 characters could potentially invoke a charge for two SMS messages, even if the sender/recipient only sees a single message.
When interfacing with a telephone company’s SMS gateway programmatically, there may be limits on the number of individual concatenated SMS messages which can sent as part of a single message. For example, Clickatell’s documentation states that messages sent through their API should not contain more than 3 concatenated SMS segments. This may require limiting the number of character input in a web application or service which sends SMS messages via an API in such a manner.
While it may seem elementary, it is important to point out that SMS messages are always in one particular encoding; i.e. fully GSM or fully UTF-16. For example, a period character (”.”) takes up 7-bits in a GSM SMS message. The same character may exist in a Unicode SMS message, but takes up 16-bits, even it is representing the same character."
Click to expand...
Click to collapse
Mobile companies set their limits, one may allow you to send up to 6 combined messages, others 10 for example.
Either way there is nothing you can do with your phone that will change this.