Related
Guys, about 90% of the time when i send a text message, of any size, to anyone, i get a 'message can not be sent' notification and the phone vibrates, this happens about 2-7 times before the text message is sent, and for each time it tries to send the text again, this amount is send to the recipient, for example if it retries 7 times i will send the message 7 times - very annoying
when using the froyo rom from both paul and richardtrip i did not have this issue, although i am almost certain this was due to the stock messaging app, i even tried using handcent on the froyo which i used on the stock and on the froyo it worked perfectly too, but handcent will not work on the stock rom.
so it seems to me that it is an issue with either the stock (sense based) rom or the htc messaging app
im on tmobile UK on a branded phone, this happens on any radio, both rooted and unrooted
does anyone have any advice, or know of a way to replace the htc messaging app with the stock android messaging app?
if i could get this sorted id be very happy, so i appreciate any help
thanks in advance
I've had this issue happen a couple of times aswell, not sure how to replicate it, it seems totally random, but i haven't seen a 90% change of getting it!
try a new radio lol
This happens to me if I use any messaging system other than the default one (e.g. handcent or chomp) and the signal changes whilst sending the message (i.e. H to 3G or E to G etc. etc.)
I am still using the default rom with the latest update as I am waiting for 2.2 before rooting
turn off GRPS/EDGE/ 3G Data
cgrec92 said:
Guys, about 90% of the time when i send a text message, of any size, to anyone, i get a 'message can not be sent' notification and the phone vibrates, this happens about 2-7 times before the text message is sent, and for each time it tries to send the text again, this amount is send to the recipient, for example if it retries 7 times i will send the message 7 times - very annoying
when using the froyo rom from both paul and richardtrip i did not have this issue, although i am almost certain this was due to the stock messaging app, i even tried using handcent on the froyo which i used on the stock and on the froyo it worked perfectly too, but handcent will not work on the stock rom.
so it seems to me that it is an issue with either the stock (sense based) rom or the htc messaging app
im on tmobile UK on a branded phone, this happens on any radio, both rooted and unrooted
does anyone have any advice, or know of a way to replace the htc messaging app with the stock android messaging app?
if i could get this sorted id be very happy, so i appreciate any help
thanks in advance
Click to expand...
Click to collapse
Had exactly the same problem on stock/sense based verions of romms. NEver had an issue on stock android messaging app, only with the sense one. Think it must be a bug with that app. I'm T-mo in UK to but have an unbranded phone.
dont resend it, just wait until the message is sent, the phone resends automatically, because if you click the resend, it will send another message. what i do is when i get that error message i just wait.
I'm getting this problem on my o2-uk Desire; they are sending me a replacement handset
ugmeme123 said:
dont resend it, just wait until the message is sent, the phone resends automatically, because if you click the resend, it will send another message. what i do is when i get that error message i just wait.
Click to expand...
Click to collapse
Thanks everyone for your replies
So it is confirmed that it is an issue with the HTC messaging app but not with the stock android messaging app, and no messaging clients can fix this as they use the default messaging app.
Is there anyway to change the HTC messaging app with the stock android? I prefer it anyway it works much better, the official froyo release will also contain the stock messaging app which I guess will have the same problem.
I will try flashing a different radio
Setting the phone to WCDMA only does not fix the issue
I am having this problem, and also another which I feel might be related, it tries to resend the message, and it eventually goes. I have also noticed that quite a number of times when I try to make a call, it doesnt dial, it just goes silent and returns to the call register screen. Maybe both related to a siganl problem . Somebody suggested switching off Edge or whatever, but thats not really a fix, and why should you have to do this to send a text. ?
melhookv12 said:
I am having this problem, and also another which I feel might be related, it tries to resend the message, and it eventually goes. I have also noticed that quite a number of times when I try to make a call, it doesnt dial, it just goes silent and returns to the call register screen. Maybe both related to a siganl problem . Somebody suggested switching off Edge or whatever, but thats not really a fix, and why should you have to do this to send a text. ?
Click to expand...
Click to collapse
I agree, and I also experience the same problem, sometimes during a phone call the most strange sounds happen and then the call cuts out, I'm guessing is interference. Problems with calls, text messages, and the connection repeatedly drops when using the mobile internet, exactly the same problems as the hd2, they will not get fixed by HTC, speaking from experience.. very basic requirements of a phone still not being met
I have the exact same issue with both texts and calls that seem to take ages to connect and then just dump me back to the dialer. I've put it down to O2 being so awful but of people have the same issues on other networks id love to know
-------------------------------------
Sent via the XDA Tapatalk App
I get it off and on, but I let it be and the messages eventually get sent out.
r47z said:
I get it off and on, but I let it be and the messages eventually get sent out.
Click to expand...
Click to collapse
Same here. I did the resending thing for a while, but now I just ignore those error notifications. The text messages arrive anyway
r47z said:
I get it off and on, but I let it be and the messages eventually get sent out.
Click to expand...
Click to collapse
same. I get it 10% of the time. On a unlocked Desire with a UK T-Mobile contract. just leave it to send a couple times, put your desire on a window sill and it should be okay.
but i think the message is not automatically sent if you lock the phone. can anyone confirm this? my unsent message was still not sent when i locked my phone.
As mentioned earlier in this thread, i used to get this issue all of the time when using handcent or chomp. However, since doing the following i've not had it happen once in 2 weeks (where it would happen 10+ times a day before)
1) uninstall any messaging software you have downloaded from the market
2) download sms unread count and sms popup from the market
3) put the sms unread count widget on the homescreen
4) configure sms popup to your liking
5) send messages to your heart's content
This uses the default 'messages' app rather than anything else and works perfectly
spud_work said:
As mentioned earlier in this thread, i used to get this issue all of the time when using handcent or chomp. However, since doing the following i've not had it happen once in 2 weeks (where it would happen 10+ times a day before)
1) uninstall any messaging software you have downloaded from the market
2) download sms unread count and sms popup from the market
3) put the sms unread count widget on the homescreen
4) configure sms popup to your liking
5) send messages to your heart's content
This uses the default 'messages' app rather than anything else and works perfectly
Click to expand...
Click to collapse
Thanks very much for your reply
I will try this right now
i also have the problem with the unsent messages and undialled calls, tmo uk contract phone.
Had Evo since day 1. Rooted right away and have been ROM-happy, flashing my favorite as developers release them. Went from Fresh to Myn to MIUI and am now on my favorite, most stable and reliable rom: Deck v1.
Problem:
9 days after switching to Deck I stopped receiving sms messages completely. This is not an issue of the notifications for sms being turned off, nor is it a ringer issue. The text never comes through. I can send texts without issue, no problem.
Tried to fix this in these ways:
•*I made sure I wasn't blocking any texts; this can be done at sprint.com > my account.
• I called sprint so they could remove/re-add my sms messages which usually fixes this type of issue.
• I restored a nandroid backup taken at a point when texts were working.
• I tried restoring the stock image - then updating profile. Still wouldn't receive.
• Obviously rebooted 35 times throughout the course of all this (i have to say it, somebody will ask )
• Full wipe etc.
Nothing worked.
Called Sprint knowing they couldn't do a damn thing and would probably stop listening if they knew my phone was rooted. Long story short they sent me in to get a new Evo. Was worth a shot, I wasn't convinced it was a hardware issue (how could it be, sms is not dedicated to a particular piece of hardware in the phone) but I went in and did the swap.
New Evo, unrooted, texts worked! but wait, that's not all.
9 days after rooting again and installing Deck v1 - poof - no incoming texts. The exact same issue.
WTF is going on here?? There is nothing in logcat, absolutely nothing happens on my side when somebody sends me a text.
Google voice texts are a good emergency workaround but I want my native texts. Is this a deck issue?? anybody else getting this? i;ve ggogled for weeks now and nobody has come accross this particular issue. Also this issue wont fix itself. i went a almost a week the first time without noticing i wasn't getting texts.
Have you tried a ##786# reset? You will need your MSL code. Also, it will wipe all data from your phone, so take that into account. When you ##786#, let the list load and then hit "menu", and "reset".
When I first flashed to a GingerSense rom, I lost the ability to send/receive MMS and I was not able to connect to 3G at all. 4G and WiFi worked, but the 3G was nonexistent to my phone. After calling Sprint several times, one tech told me to reset my phone this way. I told him I would have to call back because if my phone was going to get wiped, I had to back everything up first and it would take a while. After I backed up all my app/data with Titanium and made a NAND back-up, I did it and it got my phone working right.
Hopefully you get the same result. Good luck.
rugedraw said:
Have you tried a ##786# reset? You will need your MSL code. Also, it will wipe all data from your phone, so take that into account. When you ##786#, let the list load and then hit "menu", and "reset".
When I first flashed to a GingerSense rom, I lost the ability to send/receive MMS and I was not able to connect to 3G at all. 4G and WiFi worked, but the 3G was nonexistent to my phone. After calling Sprint several times, one tech told me to reset my phone this way. I told him I would have to call back because if my phone was going to get wiped, I had to back everything up first and it would take a while. After I backed up all my app/data with Titanium and made a NAND back-up, I did it and it got my phone working right.
Hopefully you get the same result. Good luck.
Click to expand...
Click to collapse
Flashed back to a Sense/stock rom to do just that. Didn't help.
Whenever somebody has issues like mine it usually involves sending AND receiving. For me it's strictly receiving.
People also center these issues around MMS. Sending MMS is not an issue for me. I can send everything. I can't receive a damn thing.
That certainly is an oddity. I've been using decks 1.2 since C, and am currently on Z. I've never had any issues with not receiving sms messages (as far as I know...I suppose it would take someone to tell me that they sent me a message and I never replied, which I haven't got yet) I have never really seen this issue, except on my buddies stock hero a couple weeks. His problem was that he had never deleted any of his texts, so literally had like 10k messages or more in there. Once I was finally able to get all his damn messages cleared out (took forever...he wouldn't let me factory reset it) he was able to start receiving texts again. I'm sure that's not your problem, because you've been flashing and wiping, surely your texts have been cleared out...unless you restore them all. That's the only time I've seen that. I would've suggested maybe it was an issue on sprints end, which would not be unheard of, but if that was the case it wouldn't have worked on your new unrooted evo when you got it.
I saw in deck's thread that you already deleted the telephony.db directory, and that had no affect for you. I really wish I had some suggestions for you, but that is just odd. My first guess would've been a problem with sprint.
EDIT: Also, are you using the GV and Sprint integration? I don't use it, but I saw that if some settings weren't correct with that (from the google voice website) that all messages will go thru google voice, and not thru the native messaging app. Could that possibly have anything to do with it, maybe?
If you have Sprint/Google Voice integration, that is the problem. There are some funky things going on with Google Voice lately. Can't send messages from Gmail to a Google Voice number and have it register as a cell sms. The message is automatically sent to and only goes to the Google Voice Inbox.
I've had some sms trouble with all ROMs, not simply Deck's. It sounds identical to your issue. Google is the only constant between all ROMs. My problem was resolved by going into Google Voice settings, unchecking "Receive text messages on this phone," saving changes, then rechecking it and saving those changes.
I have lost the ability to receive sms numerous times. I am convinced it is a Google/Sprint integration issue.
I cant get text messages either. I can send all day and im testing, flashing roms, recoveries, I just unrooted as a final solution (so i thought) and nothing. Same crap. If anyone has a fix or if the fix is on another thread let me know please, thanks. Other wise im just gonna root back and say F! text messages
If you're on MIUI and didn't wipe, when you flashed it can cause these issues. Try to reflash, after doing a full wipe.
The issue that I'm having is that I can send out text messages but am not able to receive them. Had no issues today until I upgraded to deodexed stock EG22 with the purple CWM 3.1.0.1, root and Busybox 1.18.4. I've got Google Voice set up with my account so I know that texts are coming back but they aren't going to my phone. Any ideas as to what I can do? I've odin'd a few times and tried airplane mode and back to data to no avail. Please help!
Casto1093 said:
The issue that I'm having is that I can send out text messages but am not able to receive them. Had no issues today until I upgraded to deodexed stock EG22 with the purple CWM 3.1.0.1, root and Busybox 1.18.4. I've got Google Voice set up with my account so I know that texts are coming back but they aren't going to my phone. Any ideas as to what I can do? I've odin'd a few times and tried airplane mode and back to data to no avail. Please help!
Click to expand...
Click to collapse
It's because of Google Voice (I had this problem too).
Go to: https://www.google.com/voice, and then hit Voice Settings in the top right corner.
When you see your phone's number, they should be 2 options under it.
Check the one that says "Receive Text Messages on this phone"
As long as you have that checked, you should be able to receive text messages again without Google Voice.
Hope this helps! This problem was very annoying for me as well!
Looks like this was the issue. I didn't have issues before changing roms, do the settings change when you root the phone you think?
Casto1093 said:
Looks like this was the issue. I didn't have issues before changing roms, do the settings change when you root the phone you think?
Click to expand...
Click to collapse
Nah, had nothing to do with the rom. Google Voice intercepts sms on your phone for some reason. Most likely you had just noticed it now.
So i flashed MIJJz BLEND ICS [FB21] about 2 days ago, ran into the known bug about messaging, where you can send but they will not receive, flashed the Steady kernel to get my recovery back and reverted back to my FB17 nandroid backup, everything restored fine and was working with the exception that i still could not receive any text messages, the strange thing is i can still receive picture messages just fine. so today i decided i'd had enough of using G-Voice and used Sfhubs EL29 Odin-OC restore to revert back to EL29 Rooted (as ive done to fix so many issues in the past) heres the kicker, i STILL CANT receive text messages while picture messages still work. Any input or suggestions here would be awesome. (sorry for long post but i wanted to be as detailed as possible)
Fixed - it was the "Receive text messages on this phone" setting in google voice, ive never ran into that problem before, thanks to kthejoker20 for saving my butt
Don't apologize for being detailed lol, it helps alot, but update your profile, PRL, reboot your phone. If not call Sprint and complain, they'll probably provision your phone (or whatever its called). Its possible its on the carrier end.
Vael said:
So i flashed MIJJz BLEND ICS [FB21] about 2 days ago, ran into the known bug about messaging, where you can send but they will not receive, flashed the Steady kernel to get my recovery back and reverted back to my FB17 nandroid backup, everything restored fine and was working with the exception that i still could not receive any text messages, the strange thing is i can still receive picture messages just fine. so today i decided i'd had enough of using G-Voice and used Sfhubs EL29 Odin-OC restore to revert back to EL29 Rooted (as ive done to fix so many issues in the past) heres the kicker, i STILL CANT receive text messages while picture messages still work. Any input or suggestions here would be awesome. (sorry for long post but i wanted to be as detailed as possible)
Click to expand...
Click to collapse
but you can send mms and sms? you can recieve mms but not sms? have you wiped data and cache? did you restore via tb? i havent ever seen such an issue that wasnt related to sprint doing work on my nearest towers but there may be better responses. I suggest clearing data/cache from mms app and try sending sms to yourself.
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
phatmanxxl said:
Don't apologize for being detailed lol, it helps alot, but update your profile, PRL, reboot your phone. If not call Sprint and complain, they'll probably provision your phone (or whatever its called). Its possible its on the carrier end.
Click to expand...
Click to collapse
that too! is probably the fix needed as well
thanks for the quick responses guys, i've tried what was suggested, @justlovejoy, thats whats blowing my mind, the fact that i can send mms and sms perfectly fine and receive mms just not sms (i even get the "test" messages sent to myself on g-voice) im starting to think it might be something on sprints end. but before i call and try dealing with them i wanted to ask the community which seems to know more on a bad day than sprint ever has
//edit
Maybe i should read everything first too. Sorry.
Sent from my SPH-D710 using Tapatalk
called sprint, according to the rep they were gonna "re-trigger" the phone (id imagine this is what phatmann meant when he said provision) but it doesnt appear to have had any effect, still not receiving these sms's.
Been through this a few times since flashing to ics. I know its aggravating.
Mine stopped after installing the ICS4ICS them and freezing the stock messaging app with titanium. I trieddefrosting but the app would hang.
Had to uninstall tbu, then reinstall the theme. Brought everything back and worked.
Not sure why tbu hangs but ivee a suspicion that having the stock and ics messaging apps together with the build being a leak has something to do with it.
I use GoSMS and it usually doesntt give issues.
Hope this helps in some way.
Vael said:
called sprint, according to the rep they were gonna "re-trigger" the phone (id imagine this is what phatmann meant when he said provision) but it doesnt appear to have had any effect, still not receiving these sms's.
Click to expand...
Click to collapse
have you tried sending from mobile sms? as in device stock messenger? or trying without google voice? maybe theres some interference going on between the two?
well the only two things I can think of are these. either its sprint towers or your phone has leftover stuff messing with it. try using calkulins format all then clean install the rom. also remember in titanium backup to only restore user apps not system.
Are you using google voice?
Install the GV application. If you recieve the texts with it installed, then you have "send texts to phone" off in google voice website.
kthejoker20 said:
Are you using google voice?
Install the GV application. If you recieve the texts with it installed, then you have "send texts to phone" off in google voice website.
Click to expand...
Click to collapse
are you refering to the "Receive text messages on this phone" option, because i think you just pulled my a$$ out of the fire
@kthejoker20: you are the f-ing man, that fixed it. god i feel like a noob again.
Hey everyone. I'm having a big problem w/ my 16GB GSM Galaxy Nexus running bigxie's rooted, deodexed 4.1 rom, and I'm hoping you guys can help me.
Whenever I send a message, I get a "Message not sent" error in the notifications bar, and a red triangle w/ an exclamation point appears under the text of the text message. I have T-Mobile and I have FULL signal bars. I can make calls and this texting issue is the only problem I'm having. I installed this rom a few days ago and this problem just suddenly started today. When I send a text with the "Messaging" app, the area code (I live in the US) of the phone number disappears. So if the number in my phonebook is stored as:
"1 (areacode) sevendigit-phonenumber"
It instead shows up like this after I select the contact:
"1 sevendigit-phonenumber"
If I try and send a text by selecting the contact from the "People" app, it works just fine.
Last night I flashed the Popcorn kernel, but I then I also sent a text and it worked. I thought maybe somehow this might have something to do w/ the kernel or a rom (both unlikely), so just in case I re-flashed the STOCK 4.1 this time (the first rom, the one that appeared on ROM Manager the day of the Google I/O). Now I'm back to stock Jelly Bean everything (including kernel, and also the Jelly Bean baseband) but I'm still getting the problem. I tried clearing the "Messaging" app's data and cache, but nothing fixes the problem. I have a strong feeling that the cause of the error is because the "Messaging" app removes the area code from in front of the phone number, but now I can't remember if that's normal (did that happen in ICS?, did it happen before in JB?, I don't remember).
Has anyone else encountered such an error? Please help me.
I too am experiencing this issue running bigxie's 4.1 ROM on my 16 GB Galaxy Nexus.
I hope someone has a solution!
I think I may have fixed the problem for myself. It seems like in both the stock JB and also bigxie's rom, the "Messaging" app is doing some sort of mishandling of the phone numbers. Try changing one or some of your phone numbers in your contact list to this format: "(307) 456-7895" <-- parenthesis around the area code, then a space after the parenthesis, then the seven digit number with a dash (-) after the third. Try changing this format on Google Contacts, not on your phone. Then sync the contacts on your phone.
Try this with just one contact that wasn't previously working and please let me know what happens.
I'm having the same problems with the same rom and tried the same steps to fix it but it didn't work for me. Also tried going back to cm9, no luck.
Search for the setting for something like ##info#* or whatever. I blew mine out when I flashed a new rom (not the roms fault i did it not knowing better). Don't have time now to look but there are important settings for sending sms.
Jeff
[email protected] said:
Search for the setting for something like ##info#* or whatever. I blew mine out when I flashed a new rom (not the roms fault i did it not knowing better). Don't have time now to look but there are important settings for sending sms.
Jeff
Click to expand...
Click to collapse
Thanks I figured it out. I had a hard time finding this info so ill re post it here for any one who needs it. It solved all my problems.
http://rootzwiki.com/topic/14916-howto-sms-centre-numbers-if-your-gnex-wont-send-messages/
Hi
This damned *#*#4636#*#* menu!!!
I know, I shouldn't be messing with what I don't know but I moved from an iphone so that I could 'fiddle' with a phone hence the GNex.
Anyhow. I have been having serious issues in sorting this out until I pieced the information together in this post. None of this I can take credit for - as it is built on others work - I just put it together in one easily accessible place.
The problem is that this menu somehow wipes the SIM card's record of the SMSC number.
You can't just enter the SMS Centre number as it is, you have to convert it into something called PDU format (no idea what this is)
I have converted a number of UK SMS Centre numbers into the correct format below.
Method:
1. Go to phone dialpad.
2. Enter *#*#4636#*#*
3. Scroll down to the bit that says SMSC
4. Type your sixteen digit number in from the table below.
5. Press Update
6. Press Refresh
7. Press Back button to exit the app.
8. Test by sending an SMS
Hope that helps. The GNex doesn't give an option which is easily accessible from anywhere to change the SMSC number, downright silly as my 10 year old Nokia would let me do that.
Click to expand...
Click to collapse
PDU Decoder
http://www.twit88.com/home/utility/sms-pdu-encode-decode
I couldn't quite follow those directions, but my problem fixed itself without doing any of that. It just suddenly started working after I changed the format of the numbers in Google Contacts.
i tried these steps but no luck.. its simply the format of phone numbers.
this format is no good: +1 (123)-456-7891
this format is good: +1 123-456-7891
another solution is just to manually update each contacts.. i wish there was an app that does it automatically
install handcent sms app...go to undelivered SMS in menu...delete in any undelivered sms is there...it worked for me...
u can uninstall Handcent post that
I had the same problem , Can't send but can recieve sms ,
the problem presents since updating to jb 4.2.2 ,but it was working in 4.1.2
I tried the smsc solution but no luck at all ,
I think it's not a carrier problem cause i can send from Moto Defy "CM7.2 " ,but no luck with JB
Plz help
Another Fix
Tried all the fixes I could find with no luck. Then found out that I had enabled Google Voice+ to send SMS messages through Google Voice. After I disabled this everything went back to normal.
Just another thing to try that worked for me.
I know this is somewhat old but wanted to say for me, that the messages were being sent but there was one stuck in the queue. I followed the directions of installing handcent and found the empty text sitting in the queue... like a draft message. Once removed the message went away. I uninstalled handcent and all is good. It sucks that the stock JB 4.2 messaging app doesn't have a outbox and draft box to find stuff like this. Thanks for the help!
hellandj said:
Tried all the fixes I could find with no luck. Then found out that I had enabled Google Voice+ to send SMS messages through Google Voice. After I disabled this everything went back to normal.
Just another thing to try that worked for me.
Click to expand...
Click to collapse
THIS all the way!! I was trying everything to get my sms to work but it ended up being google voice+
Thanks for the reminder