I've seen a couple of threads that make a separate reference to this issue, but none that express the same issue I am having. I am currently running PacRom 4.4.2 but I was also having this issue on PacRom 4.3 (December nightly). Basically, text messages are hanging on "SENDING..." and then after a couple minutes I get an error that the message was not sent. If I hold down on the unsent message and select View Details it states "Error Code: 201" Typically the first text I send during the day goes through fine, but then when I try and send another text it hangs. If I wait awhile and try sending a text later, it often goes through, but anything immediately after that hangs on sending... Needless to say, this has gotten rather frustrating. Even now I had a text go through after not using my phone for a while, and the next 5 attempts to send another text to the same person have failed to send.
I posted this issue in the PacRom thread and did not receive any response, although someone stated they were having the exact same issue on their CM Rom. That user made reference to Voice+ possibly causing a background issue. I do not use Google Voice (use standard SMS app), but I did try freezing Voice+ in Titanium Backup, which did not make a difference. My software is as follows:
Android Version: 4.4.2
Baseband version: I605VRUEMJ9
Kernel version: 3.0.64-CM-gb1c5069 [email protected] #1
PAC version: 4.4.Alpha-1
AOKP version: i605_kitkat
CyanogenMod version: 11-20140303-UNOFFICIAL-i605
ParanoidAndroid version: 4.0
Is anyone else having a similar problem, or has anyone discovered the underlying cause/solution to this issue?
Thanks for taking the time to read this and thanks in advance for responding.
AOKP is not PAC. Might want to edit your title.
fujimoh said:
I've seen a couple of threads that make a separate reference to this issue, but none that express the same issue I am having. I am currently running PacRom 4.4.2 but I was also having this issue on PacRom 4.3 (December nightly). Basically, text messages are hanging on "SENDING..." and then after a couple minutes I get an error that the message was not sent. If I hold down on the unsent message and select View Details it states "Error Code: 201" Typically the first text I send during the day goes through fine, but then when I try and send another text it hangs. If I wait awhile and try sending a text later, it often goes through, but anything immediately after that hangs on sending... Needless to say, this has gotten rather frustrating. Even now I had a text go through after not using my phone for a while, and the next 5 attempts to send another text to the same person have failed to send.
I posted this issue in the PacRom thread and did not receive any response, although someone stated they were having the exact same issue on their CM Rom. That user made reference to Voice+ possibly causing a background issue. I do not use Google Voice (use standard SMS app), but I did try freezing Voice+ in Titanium Backup, which did not make a difference. My software is as follows:
Android Version: 4.4.2
Baseband version: I605VRUEMJ9
Kernel version: 3.0.64-CM-gb1c5069 [email protected] #1
PAC version: 4.4.Alpha-1
AOKP version: i605_kitkat
CyanogenMod version: 11-20140303-UNOFFICIAL-i605
ParanoidAndroid version: 4.0
Is anyone else having a similar problem, or has anyone discovered the underlying cause/solution to this issue?
Thanks for taking the time to read this and thanks in advance for responding.
Click to expand...
Click to collapse
Known Verizon issue. Call them or hang tight. This is not a rom issue. If you need texting until it's fixed go back to TW.
DreamFX said:
Known Verizon issue. Call them or hang tight. This is not a rom issue. If you need texting until it's fixed go back to TW.
Click to expand...
Click to collapse
Thank you for the response. I am curious though, if it is a Verizon issue and not a rom issue then why is the problem resolved with a TW rom? What is it about AOSP that is creating an issue with SMS services?
fujimoh said:
Thank you for the response. I am curious though, if it is a Verizon issue and not a rom issue then why is the problem resolved with a TW rom? What is it about AOSP that is creating an issue with SMS services?
Click to expand...
Click to collapse
Very good question that I nor anyone else can answer right now it's very bizarre.
Related
Hello everyone. I recently ran into a problem, my text messages stopped sending. I am running the latest version of the community rom with the latest OTB kernel from nemesis2all. I have been running this setup since release and have had absolutely no problems. Until today.
Earlier this morning I was texting a couple people as usual. I use chompSMS as my messaging application. Sitting there writing a text when I get the "updates are available" notification from the market. I finish my text and start to update my apps. Everything seems to update just fine so then I reply to another text. It won't send. I try sending it again. No dice. Send like 5 other people a text. Nothing happens, besides "send failed" notifications. All of a sudden I get the crash vibrations and then my phone reboots, and I still can't send texts.
Any help or suggestions would be greatly appreciated. I have had this phone since September and have been flashing roms since before that. I know a pretty good amount of information but have never ran into a problem quite like this.
Does the stock messaging give you the same errors? If so revert to the last known working version of chomp with titanium.
good day.
chopper the dog said:
Does the stock messaging give you the same errors? If so revert to the last known working version of chomp with titanium.
good day.
Click to expand...
Click to collapse
Yes, the stock app gives me the same errors. I have tried reverting back to an older chomp and that doesn't work either. Everything else works, like calls, 3g data, gps, and I can receive texts. I just cannot send anything. It will try to send for like 5 minutes or so before I get a "send failed".
EDIT:Got it working. Didn't realize TiBu had latest version of chomp. Found an earlier version and everything works as it should. Thanks chopper.
I have searched the web and found no discussion about it anywhere, leave alone xda-developers forum.
I have an X10i running on an Android custom ROM - CM 6.3.1.
I have a very unique and strange problem in my phone which is very annoying and causing inconvenience.
All the messages (SMSes) are being threaded wrongly and randomly. That is, an SMS coming from 'A' threaded to 'B'. B's SMSes threaded to 'C'. C's SMSes threaded to sometime A and Sometime B. And A's SMS create a new thread sometimes. An SMS coming from a totally new person or source threaded either A, B or C whereas they are not at all related anyhow etc.
This may sound unique and unbelivable but i am really facing this problem since a couple of months. Before that it was working fine.
The various steps which i have already tried but got no success are :
1) Wiped out the entire depository of SMSes and started afresh.
2) Reset my phone to factory default.
3) Tried different custom ROMs or different version of a custom ROMs.
I do not understand why the phone is behaving so strangely. A help from someone will be greatly appreciated.
Don't know if this would help but did you try using Stock super vanilla 2.1 just to see what happens?
NJFM said:
Don't know if this would help but did you try using Stock super vanilla 2.1 just to see what happens?
Click to expand...
Click to collapse
Sorry.... but would u mind explaining what is Stock super vanilla 2.1?
1. Installed History Eraser app and erased app cache, search histories, SMSes, and call logs.
2. Uninstalled native Messaging app through Titanium Back up app.
3. Rebooted and then installed another popular SMS handling app - Handcent SMS.
The problem still remain as it is.
Anyone there to take the challenge.
First off, I'm sorry if it seems like this has been answered before, but I did a good deal of searching and couldn't find anyone who had quite the same problem I do.
I've been using Agrabren's CM10 - Disarmed Toaster for CDMA since Friday. But I ran into a "storage running low" problem this morning (after I let my phone go dead last night and then put it on the charger overnight) which caused me to do a full wipe and re-flash with his latest version (0.2.2). Since then, I haven't been able to receive texts at all. I have Google Voice, and I was getting the texts there, but not in the actual messaging app. I have since tried disabling and re-enabling Google Voice to no avail, and it is currently disabled to remove extra variables. I haven't been very scientific about my troubleshooting process, which has mostly involved a lot of flailing around, wiping, and re-flashing. But I've re-installed the ROM countless times and twice now have flashed a Sense ROM (MeanROM 2.6) to update my PRL and Profile and then flashed back to CM10. I suddenly got a flood of all my texts when I flashed to Sense, but still don't get any texts after flashing back to CM10.
I tried Paranoid Android and AOKP variants and have the same problem. I even tried Team DIRT's CM10 Codename Android and texts still didn't come in. I should also mention that I had the same problem a while back with Disarmed Toaster 0.1.6, and it probably started the same way with running out of battery and then having the storage low issue and re-flashing. I never figured out exactly what the issue was, but I think at the time I was able to fix it by flashing a Sense ROM and updating profile and PRL.
Sorry for the long explanation. Let me know if there is any other info I can provide to help. I really didn't want to go back to MIUI, but that might be only option at this point.
Also, for reference:
HBOOT - 1.40, S-Off
Recovery - 4ext 1.0.0.5 RC5
THANKS
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
efan3719 said:
you might wanna try looking here.
http://forum.xda-developers.com/showthread.php?t=1818387
Click to expand...
Click to collapse
Thanks. I already asked there and I've been following the thread. I don't think anyone else has mentioned this problem.
Sent from my PG86100 using xda app-developers app
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
coal686 said:
I think it's the 4g logs growing exponentially and filling the space. You need to periodically clear the logs.
Click to expand...
Click to collapse
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Jsparta26 said:
It could be the apn xml file in the cm10 rom. The settings are probably not set correctly. Have you looked through the thread where you got the rom to see if anybody else was having the same problem? If not you could always address this issue to the dev. Ask him if you can provide a logcat to him on the thread or pm him the logcat.
Click to expand...
Click to collapse
That's an interesting thought, but it doesn't seem to explain why no one else is having the same problem, or why it worked at one time, and then didn't work after I re-flashed.I guess there could be something wrong with the flash process that was corrupting that file on my phone. But I was able to *send* sms without a problem, so I'm not sure.
As I mentioned before, I've been following the threads for the ROM and no one else has mentioned the same problem. I asked the question in the thread, but I didn't get an answer.
Anyway, as I mentioned above it's working now, so I wouldn't be able to provide a logcat unfortunately. For anyone else with the problem, I guess the only suggestion I can give it to make sure you keep a backup of a working ROM handy if you're going to re-flash a lot.
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
mastadave99999 said:
I have had the same problem its agrabating get it
But it seems as the issue is inconsistent at best. I found out how to clear the 4g logs why are those logs even kept anymore?
The messaging this is the worst part I too use google voice
We need to find a better solution to this
Click to expand...
Click to collapse
Haha...
Just so you know, once you've cleared out the 4G logs, you can make that directory "immutable" so that the logs don't get created anymore. Just run this command in terminal emulator:
chattr +i /data/wimax/log
I'm obviously not an android developer, and I have no idea why the logs are still created. I also have no idea what caused the text message issue, but if you are currently not getting texts, I would suggest you restore a working backup and then re-flash Agrabren's ROM like I did.
SMS Help!!
soldierforchrist2 said:
Yeah, I think that's what caused the "Storage space running low" that started the whole thing. But the real issue is why I was no longer able to receive texts in any CM10 ROM since I re-flashed to "fix" the storage problem....
Thanks for the tip.
Anyway, it seems as though the problem has been resolved. So far I'm receiving texts okay - here's what I did:
1. Called Sprint while on CM10 Disarmed Toaster, they said provisioning looks okay, and the did a "refresh" on their end - didn't help anything
2. Flashed MIUI - received texts fine
3. Flashed CM10 again - still not working
4. Restored backup of MIUI - received texts fine, used for a little while
5. Flashed CM10 again - now able to receive texts
I think there's something going on behind the scenes that I am not aware of. Somehow it looks like restoring my backup and using it for a while fixed whatever the issue was.
Click to expand...
Click to collapse
Has anyone figured out why SMS stopped working? I am running AOKP JB ROM and I can send text messages but I am not receiving them. Thanks for your help.
Still not working
I've been having the same problem with the sms, it works if you re-flash something else a couple times then flash CM10 back on but sms will only work for so long. I would like to pick apart the problem and see if we cant find the source of the problem, it could be a temp file that CM10 has been saving that interferes with the sms, but that's just a guess. any help on this is greatly appreciated
Just wanted to say I too have encountered this. I have tried flashing unofficial aokp 3.5 and unofficial slimbean 1.1. Getting ready to flash an MIUI rom like mentioned above.
Some Experimenting....
I did a small experiment just now (to try and get incoming SMS working) because I had essentially experienced the EXACT same problem, except that it was with P.A.C.MAN v.23 instead. What I did was installed a stock-based rom (I used unSENSABLE), which obviously allowed all my SMS to come flooding in, and stayed on that rom for about a day. After that I made a nandroid backup (of unSENSABLE) in 4ext, wiped everything except sd (not using the superwipe, and including caches) and then restored the backup. After that I booted up, let it sit for a while, then restarted into recovery. Again I wiped everything without using the superwipe, and flashed P.A.C.MAN v.23.0.0 and then GAPPS and booted. After all that, SMS was working again. We'll see how long it lasts...
I don't know if these issues are related or not, but I'm having issues with making phone calls and reading texts. This has persisted for several months. I've updated the ROM (MeanROM) hoping it might fix it, but I don't know if it's related or not if others aren't experiencing the problem. I did a factory reset and it fixed the issues temporarily, but I'm not even sure if it worked for a day.
The text problem:
Texts come in and I usually get them right away. Meaning, my notification sound is made and a preview is displayed on my lock screen and in my notification bar. But when I try to open the full message, it takes several minutes to load. When I send messages, it seems to be fine. It's almost like it's loading all of my texts in the thread when I open it. I used to use Handcent, but have since switched to the stock messaging application. The problem exists with both.
The calling problem:
I seem to receive calls fine, but I can't always make calls. I can open up the calling app and most times it will show my recent calls, but I have to click "Call" (to call the last person) or click on one of the recent contacts to call and then wait a minute or two before the phone shows any response that it's calling. There are other issues involved like it not finding people or numbers that are in my address book when I try to search for them with the number pad.
I would appreciate ANY help that anyone can provide. Let me know if I can provide any other information.
Thanks!
Have you tried a new Jelly Bean based ROM? I had the contact lag issue, same as you, on ICS. Going to JB has seemed to fix it entirely for me.
Can you provide some add'l info...?
What Radio/firmware? S-on/off?
What version of MeanROM?
Did you do a clean install and if so, did you restore any apps/data from a nandroid or manually re-install everything?
All of my info is in my sig. But, any Jelly Bean based ROM should fix the issue. It was an issue with HTC, and they fixed it with the recent update. I have not tried MeanBean, but it may be what you are looking for.
Yes, I did a clean install of mine, and I used "Titanium Backup" to restore some of my Apps. As well as "SMS Backup and Restore" to backup all of my texts before the wipe. I didn't restore my texts though, just kept the backup.
ThrowingKs said:
Have you tried a new Jelly Bean ROM. I had the contact lag issue, same as you, on ICS. Going to JB has seemed to fix it entirely for me.
Click to expand...
Click to collapse
I have not? What were your running previously? How long have you been running the new ROM? As I said, I did a factory reset and it seemed to fix things temporarily, but it's back again.
rpenrod23 said:
Can you provide some add'l info...?
What Radio/firmware? S-on/off?
What version of MeanROM?
Did you do a clean install and if so, did you restore any apps/data from a nandroid or manually re-install everything?
Click to expand...
Click to collapse
Sure!
S-Off
PRI Version: 2.28_003
PRL Version: 25010
MeanROM ICS 6.5
Am I missing anything? If so, how do I find it?
I did a factory reset and then installed from the 6.5 ROM that I downloaded. I did restore apps from Titanium backup, but tried to avoid anything related to text or calling. I use SMS backup and I restored my most recent texts, but probably less than 10 per user from less than 10 users.
I had been following MeanROM ICS and didn't realize that the MeanBean ROM was out. I guess I'll try that next.
Thanks!
JB update
ThrowingKs said:
Have you tried a new Jelly Bean based ROM? I had the contact lag issue, same as you, on ICS. Going to JB has seemed to fix it entirely for me.
Click to expand...
Click to collapse
Im wondering if you are having any issues with the jb update?- I've read that there are.
Thanks,
Tj
It's been a week now and I still can't send any text messages.
I receive msgs but unable to respond back...
I thought it was because I finally updated to Jellybean (I've had ICS for awhile so I thought I should just stick to that) but then I downgraded last night to ICS and I still can't send messages.
well today I tried fixing it but still no luck, although I tried sending an MMS instead, I sent myself a picture and it worked! even tried it to other numbers and they received it. I also tried adding a text with the picture and it did work. but it's still not working when I just type in a text...
so anyway in short, I can't send SMS but can send MMS (and receive messages as well)
also extra: I can call people but whenever they call me it comes up as unknown number...
Does anyone of you know what might be the problem? How can I fix it? Thanks
EDIT: and btw I already checked the message centre number and it has the right number in it so I don't think the issues w/ that
I suggest using titanium backup to store user apps and data, then using mr.cook's rom wipe script to allow you to start from a blank slate, then re-install the desired firmware (whatever version)
You could work at fixing this issue individually, but (to me) it's a sign that something more fundamental went wrong, and that other issues may be soon to follow.
It isn't clear whether you upgraded to a stock jellybean, or maybe a 4.1.2 custom jellybean, or maybe a 4.2.2 custom jellybean, or a 4.3 jellybean. The latter, a 4.3 upgrade from ICS has the highest potential for weird issues if a thorough rom-wipe isn't conducted... whichever path was taken, The i777 runs all versions of jellybean well, and something like this suggests that the "upgrade" was not conducted from a clean slate, hence the suggestion for a rom-wipe and re-install.
-Cyril
can't text
Are you unable to text because a keyboard won't open? My daughter couldn't text (never figured out why - she always had a keyboard appear) so she got a replacement, and when I inherited her phone because mine has battery issues, I go through periods when I can't text because no keyboard appears. I have to into settings and play around with assigning a default keyboard before it will finally appear. Doesn't matter if I'm using the stock keyboard or one I've downloaded from a VERY reliable source - I still have to reassign and reassign and reassign to make it work. Powering off the phone doesn't do a thing.