Hi all!
now after thorough searches on the net for a couple days I could not find a solution for my problem or even who has something similar (maybe a thread exists but my searching skills are failing me )
now problem is as follows:
Any online messaging application on my phone will encounter a weird problem when sending messages, (KiK whatsApp etc). They all have a sending, delivered and read system next to the messages for me to see the state of my message. but suddenly my phone does not send messages at all and freezes at that point (for example, on kik i would send a message, and not even he "sending" icon is present, but rather 3 dots).
this problem is fixed by me force killing the app from the app manager, and upon re opening, hoping for the message to start sending.
after a few messages are finally sent, the problem would arise again, but also cutting away anything that is incoming. this problem has been present through 4 flashes, 2 restores that date back to before the problem arose, and 3 kernels, as well as about 3 radio flashes.
I am beginning to think it is a hardware problem (as i had just received it from repair a month back - motherboard and screen replacement) but i wanted to ask first.
thanks in advance for any help,and sorry for any mistakes as i am a little dizzy :0
Specs:
Intl model GT-i9100
CM11 snapshot M7
XXKDH modem from CM site.
Related
Can someone please help me with my long going problem?
Intermittently, when replying to a text message (either in stock messaging or handcent, etc) the phone does not send the text message, and refuses to send for up to a minute after retrying, then the message will eventually send.
This has been happening for MONTHS, and I have had my HTC hero replaced through orange several times regarding the issue, as they had identified it as a handset fault. I then got a replacement SIM from orange aswell to try and rectify the issue, but shortly after registering my new SIM, the issue still occurs.
It seems someone in this thread has the same problem:
http://forum.xda-developers.com/showthread.php?t=665932
I tried the "fix", ie. making sure all numbers were in international number format (+44...) but this made no difference.
As I said, this issue is intermittent and RANDOM, but happens around 3 times a day. It is very frustrating especially when trying to reply to a text urgently.
Is anyone else having the same issue?
Before anyone asks, yes my message centre number is correct (+447973100973).
It only seems to be when replying to a text message, well that is when i notice it anyway.
Any help is much appreciated!
Thanks
I started to get this when I rooted to VR12, it did it alot the first couple of days then didn't do it much. I've now unrooted to orange 2.1, its done it twice in a week. It didn't do it at all on 1.5, maybe a coincidence. Location doesn't matter either.
I noticed this issue. I updated to 2.1 and found im having the same problem. Its intermittent so i cant tell what is forcing it to "retry". Only noticed this since going from 1.5 ---> 2.1.
I installed Darkstone's Froyo Sense v1 and just today gave me the error. Friend of mine actually mentioned it earlier today. We tested it a few times. When I sent him an mms, I got the error, but he still got it. The little envelope icon remained on my message. Tried it again with another friend and same thing, but after 2min the message was sent.
I had the same problem.
I fixed it by entering the service number in the service-menu of the radio. DIAL *#*#4636#*#* and you will see the menu comming up. Take the upper option. Scroll down and update your servicenumber there. While you are there check if the prefferd network is " gsm auto prl" instead of "wcdma". It can save some power.
Goodluck.
Sent from my Hero using XDA App
Hi mcall_r
just wondering if any of these suggestions fixed your problem as I'm having the same issue. mach2005 where do you get the service number from to enter?
Me too!
Hi,
I've been having this issue too. Along with all the other bugs introduced with 2.1 it's been driving me nuts.
The issue seems to occur intermittently and with a variety of numbers. Normally I get the notification sound, a text icon with an exclamation mark in the notification bar and the text 'unable to send text message'. After a while it normally resolves itself and the message is sent however with one number, my mum's, the problem always persists.
Initially I tried checking the message centre number, ultimately I tried a master reset, without any joy. Then I got a new SIM from Orange, which still hasn't resolved the issue. I can pop the SIM into another phone and send messages to her number so it's definitely the phone.
Just today I noticed that I had an unread text from 'Anon' deep in my message thread, which apparently had come from nowhere (I have observed this before). After deleting the thread I was again able to text my mum, is this just a coincidence? Seriously pissed off with this issue but hoping it is now finally resolved. The messaging in Android/Sense seems fubar, I've also had issues with it resolving to the wrong contact when selecting 'Send message' from another contact. Anyone had these same issues in combination with the 'cannot send text message' error?
When I receive text messages from my contacts, their "sent time" is always behind by 5 hours. The messages were not delivered 5 hours late. It's just the time on the message is displayed wrong. The message I replied to them displays the correct time.
My brother's vibrant seems to have the same problem. It's not a big deal, but it's quite tedious to read messages when they are not lined up in the right order.
When I odin'ed back to stock ROM, this error disappears. However, when I flash Axura, Obsidian, the new Nero ROMs, they all produce the same messaging time error.
Is there anyone else experiencing the same problem? Could someone help me out here?
SELF reply
I fixed the problem by downloading "SMS time fix" app from the market.
Apparently this error only happens to certain Rogers users in Canada.
com.android.phone has stopped unexpectedly
ok i have done a search none of which are helping me at all....
i haven't edited anything at all, but yet i'm getting this new error and i can't seem to fix it, i send the odd message and i receive the odd message thanks to go SMS
but other than that my whole network doesn't work
i'm on 02 UK
everytime i receive a phone call i get the error, everytime i send or receive a message i get the error, the notifications aren't displaying i'm out of my whits end here like wth... help
Try this:
http://www.google.com/support/forum/p/Google Mobile/thread?tid=53d875e70942e732&hl=en
If no one has any other answers you can always repair it through PC Companion.
i understand what you are going thru. I am not sure if its the same , but i had this issue with mini pro and had tried all the things in the world to see if that gets solved. My issue only cropped up with INCOMING CALLs and that too randomly. i tried reset , repair multiple times but not solved. Then finally when SE updated to the last build (which is unfortunately not rootable so far) my problem got solved.
i am sure its a bug , but mostly you can try and rename or delete your contacts (like some people reportedly had issues due to contacts photo , or something in the contact name - maybe special characters etc). If you have not yet tried the factory reset , please try that at the first place.
hey guys, I searched the forum and so far no one has been able to give a clear answer. So here I am. I got my S3 about 10 days ago. And what I've noticed is that sometimes my message tone will play for no reason. Like the message tone will play, when I check my phone, nothing. Absolutely Nothing. Then my friend tells me that he messaged me. I'm like no you didn't. I've noticed that I don't get a lot of texts actually. I also noticed that while I was in a call, I received the message. Any ideas?
When I first read your title I immediately thought that it may be due to your 'Message Center' information (within the SMS settings) not being populated. However, reading your "symptoms" that's probably not the case. It might be worth checking either way though.
Are you using a stock rom?
Was this issue ever solved?
I have the same issue (Omega 34 rom)
The phone will vibrate and LED will flash, but no message is received. It only happens occasionally.
Any thoughts?
Hello folks.
I'm having an issue with my phone, S21 Unlocked SM-G991U1 (purchased directly from Samsung). This post might be long because I want to include all info to help answer questions that I might already have eliminated possible issues on.
I bought the phone March 18th and it's been working perfect up until exactly 4 days ago. What's been happening is that it will fail to send sms/texts randomly throughout the day. I can be having a conversation with someone then suddenly the texts I'm sending will begin to fail and they will get the ! or endless spinning circle depending which messaging app I'm using. I tried several apps (stock messaging, Google messages, textra) to eliminate the possibility of it being a specific one, it happens with all of them.
I then switched my sim card to another phone for several hours (S8) to see if it was a network issue... The S8 works perfect, no failed texts. As soon as I switch the sim back to the s21 the messages will fail again.
This happens at any given time, it will go from working fine for about 5 messages in a row then fail on every next message for about 10-15 mins then start working again.
This does not affect MMS or phone calls. Only SMS.
I'll also be able to receive any sms messages sent to me without issues at any time, even when outgoing ones fail.
I've tried resetting Network Settings to no avail.
I just did a complete factory reset, also no to avail. I'm lost here.
The phone has the latest update and had been working perfect up until 4 days ago. I can also say that I don't think the latest update was the cause because it started the day before I received the push notification for the update.
I'm on AT&T prepaid.
Please let me know if you have any questions I might not have covered or if you've encountered this issue before or what might be the fix. Thanks in advance!