I use my device for work. I coordinate/schedule jobs in which there are many people who can work certain slots. So, I'll send out one text message to about 75-84 individuals. Then the ones who can work reply. Later, I send out another mass SMS advising of remaining slots to be filled.
My issue is this. In the Android code a section checks for the number of text messages send within the last hour. If you exceed 100 messages - then, Android throws an error for every message afterwards within that hour and the user has to select "OK" to send an SMS. So, at times I have to sit there and select "OK" over and over again for several minutes while the over limit SMS's are sent....
I found an old record on how to fix this issue here.
However, this APPEARS to be an old solution. I was unable to find this setting or the table "gservices" in "/data/data/com.android.providers.settings/databases/settings.db
Does anyone know where this was moved or how to change this setting?
My device is a an LTE Galaxy Nexus.
I'm running AOKP-build 33. But, I would think this setting would be generic to all of the current ICS ROMs.
Thanks for any advice.
BTW - I found some very old posts related to this same issue. Note:
1) Using an app will not address this issue (I use Chomp SMS) as this is coded within Android.
2) Google Voice will not work as it doesn't recognize "groups" for the "to" box.
3) Pulling the battery will just prevent all the texts from going out.
I'm just hoping someone knows where the file/code is located that I need to modify.
All other suggestions will not resolve this issue.
Related
I have a Mio A701 with WM5, the latest official ROM.
Whenever you write more than 160 characters (or 80 in Unicode, I've disabled the Unicode option anyway), that message will be sent in multiple sms.
The thing is, whenever I pass that limit (160 characters), aka need to send a multiple sms message, I just can't send it. I always get the error "Your text message cannot be sent".
So, is this a bug, an option that can be checked/unchecked? The logical thing would be windows sending it automatically, wouldn't it?
yeah it should auto split it into 2 and send them both it works for me
so it could be an issue with the rom you are using or the operator but then
people with other phones would get the same prob
I also thought that maybe was some kind of configuration I had to do because of the operator, because with other cellphones I could always send text messages like that without any problem. I've asked this in many places but never got a reply
No one really knows a solution to this? Or at least that it happened to someone here? I'm still stuck with splitting the messages manually I've changed my rom to WM6.1, but it's still the same! With generic cellphones this never happened, so I don't really know where the problem is coming from.
I've thought that maybe it's because the sending timeout is too short... Can that be changed in the registry?
I'm back again! And still with the problem
I've found out that with SMS Chat v1.05, I can send messages normally. With any more recent version, or any other program, the same problem occurs. Any idea on why?
Hi all, A co-worker has the Droid 2 and is about to receive her 3rd one in the mail tomorrow. The problem is that text messages are randomly cut-off or garbled to SOME people. I cannot seem to find anything to help her. The issue is not related to the size of the message (i.e. SMS converting to MMS) as it has occurred with one word texts as well as larger messages. Her D2 is stock. The recipients with issues have older (1 or 2 year old VZW phones. Guessing they are dumb or feature phones, but not sure). Here is what we've tried:
Example of a 1 word text: So I sent a text that said “busy?” and it came through to the recipient as “bus”
1. Turn off auto-correct in settings
2. Auto-Signature in settings is not checked (thought that might auto convert to MMS)
3. Switch to Handcent from stock messaging app. Same problem
4. Delete the contacts having trouble and then soft re-set the phone. Then add the contacts back in.
5. Replaced phone; same problem new phone.
6. Remove apps and replace one by one. Thought she had some luck with a camera app, but no go. The issue recurred without the camera app on the phone (have told her to check the camera apps settings to see if there is anything that could be adding pics to text messages without her knowledge. That would turn the message into an MMS. Long shot but worth a look.)
I feel like somehow all of her text messages are being converted to MMS but I cannot find any setting that would be causing this to occur. Cannot think of anything else. Anyone have any ideas?
I would try doing a factory reset without installing ANY extra apps, and see if it still happens. If it works, then slowly start installing apps until it starts again and you've found the issue. If it doesnt fix it at all, then I'd SBF and try as above. If still doesnt work then it's likely an issue with your carrier or maybe their carrier. (Person getting them)
I've tried many ROMs, and except the stock ROM, mms always locks up with an endless upload- I've come back next day to see that the phone is still 'sending' the mms. Has anyone else had this problem? Is there a fix to this?
A couple of possible clues to the problem:
I cannot include even a partial example below since xda interprets it as an attempt to add a web link in my posting. So I merely spell ampersand in the hope that I can get this question posted. Arggh!
I commonly send a sms to a page plus dealer to get my current account status, and I see that as soon as the phone detects that I am sending a sms to a website (meaning that when I include an ampersand in the "To:" field...), the phone gives me a popup 'converting message to mms'. It 'converts' regardless of any/no content in the sms.
I can send sms endlessly with no problems, so long as I dont include the ampersand in the "To:" field.
I'd appreciate any help with this issue. I love running GSB 2.1 GingerShedBread and some of the other roms, but kindof need sms working properly.
I hope this is in the right forum...
Thanks.
Wileyworld
I'm on the AT&T network and can't send texts anymore after flashing to ICS. I can make calls and use my data plan but am unable to send SMS for some reason. I've tried almost every APN setting recommended by others and still nothing. Does anyone have any suggestions or has had a similar problem that they resolved?
rev3la7ion said:
I'm on the AT&T network and can't send texts anymore after flashing to ICS. I can make calls and use my data plan but am unable to send SMS for some reason. I've tried almost every APN setting recommended by others and still nothing. Does anyone have any suggestions or has had a similar problem that they resolved?
Click to expand...
Click to collapse
Correction. I can receive text messages but not send them.
*UPDATE 9/11*
So I found out the issue is related to the Message Center which you can access from "Messaging" -> hit the option button -> Settings.
After flashing to ICS I noticed that this option has been removed so I can't edit the message center. Are there any ICS or JB ROMs that still have this option available to the user? I need to change the message center number back to what it needs to be in order to send SMS texts.
27 views and no responses? Anyone?
After a BUNCH of research I finally found out how to fix this. Instead of posting a to the thread I found (since I'm still under 10 posts) I will post my copied instructions.
Go to google and search for your SMS center number which should be based on the carrier you have.
Next, go to twit88.com/home/utility/sms-pdu-encode-decode
Scroll down to where you see SMSC, Receiver, and Alphabet size.
Put in the entire SMSC number, including the + sign into the box, leave receiver blank, change the Alphabet size to 8, and delete whatever is in the message box under Alphabet and hit Convert.
Now, on your phone go to the Phone info menu described above and scroll to the bottom and find the SMSC field.
Enter the first 16 numbers into that field and hit update.
Reboot your phone and you can now send SMS.
This fix is for people who have the proper modems flashed on there phones and can still receive texts but not send them.
I've been having a recurring problem with SMS which I think might be related to the ongoing Lollipop memory leak problems. I have tried trimming back old messages but it's still happening at least a few times a week.
Basically at some point I get a text message and when I go into my SMS client - currently EvolveSMS but the same thing happens in all clients - the conversation list is either blank or only contains 1-3 entries. Any attempt to access text messages in any app fails and it just shows no conversations. When I do a logcat search for SMS I find this message:
The connection pool for database '/data/data/com.android.providers.telephony/databases/mmssms.db' has been unable to grant a connection to thread 100 (Binder_A) with flags 0x1 for 180.01302 seconds.
And it keeps showing up again and again with the number of seconds incrementing. The thread number and binder letters change as well as perhaps multiple different processes are trying to access the texts.
If I reboot it continues happening but eventually goes away on its own and I can see my whole conversation list again. Sometimes if I swipe away every recent app and wait a few minutes it goes away too.
I once had this problem in KitKat after restoring a large number of messages to a newly purchased Nexus 5. However it only occurred once - after I allowed the error to resolve itself over some extended period of time, the problem went away and never came back. On Lollipop I am experiencing this with quite some regularity and it's very disruptive because I'll receive a text and then find myself locked out of being able to respond to it for 10 or more minutes.
Any thoughts, ideas etc?