I tend to message alot on my phones whether its texting, emailing or gtalk. I will start to type out a message then the composing field will stop entering letters although the keyboard still registers that im typing on it. the only way to solve this issue is to kill the application in the recents menu and reopen the app. I've used Aokp roms on a few of my phones now and I've noticed that this may be a common bug, am i crazy or does any else sometimes experience this?
Related
Quite often I am experiencing an issue when the keyboard doesn't accept any input. For example, I go to reply to a text message, but when typing, nothing comes up in the message box. The predictive text shows up and suggests the word, but even clicking on it doesn't enter the text.
Then after maybe 3 or 4 attempts, suddenly it works. This issue arrises in various applications. Internet, email etc..
Anyone else had this issue or know of a fix?
I'm not routed and don't really plan on it for a while.
So this happened in two roms that i tried, speed rom 7.8 and Fourth Bar: Infusion.
When i type up a message and hit send , it automatically says it could not send, and so it sends the notification at least 3 more times and THEN it actually sends it. Sometimes when i hit the send button, it actually force-closes the stock messaging app that came with these apps.
It get's annoying, and its not the signal strength because this happens EVERYWHERE i go. This never happened when i was using the stock roms , but i do not wanna go back to those roms, so is there a solution out there for this problem?
Will downloading a messaging app like Go SMS fix this problem?
Hi Guru's,
I'm getting frequent Text Msg failure notices, a pop-up saying Text Messenger has stopped, with an "OK" button that must be clicked or the screen stays locked on that pop-up. It was only happening in group texts with rapid texting between multiple people at one time, but now it's happening randomly, even when texting with individuals.
In addition to this error, there are some cases when pictures or attachments will show they're loading (downloading with the spiraling circle), yet the download never comes in and the spiral never stops spinning. I end up deleting that text to make it go away. It never attempts to reload.
In an effort to help with diagnosis, I've closed all apps when texting and I still get these errors. The only two apps open when I'm texting is the stock texting app that came with the phone - with Swift-Key ... and as stated, I'm on Verizon with a phone bought at the Verizon store.
I've done everything I know to do, except a Factory Reset.
Anyone have any helpful answers/solutions?
Thank you in advance for your help.
Gregory
Are you using the Verizon messanger? What is the specifics on that?
Not using Verizon's text app.
Mostly because Verizon keeps secondary copies even after I delete them.
Since I wrote that and having surfed every thread on similar topics, I decided the best course of action was to back up and do a Factory Reset.
It worked, but I've got issues with notification settings that I'm working through.
First-World problems. ;- )
Every time I reconnect to the AT&T network I receive a notification like the one in the attached screenshot. I do not have any new voicemail and even when I have tried to use Google Voice to manage my voicemail that notification keeps on showing up. I have had this issue on every custom rom (CM, LOS, NOS) I have used on my Note 3. Has anyone else had this issue happen to them or have an idea about what I should do. I understand that I can just swipe it away every time but that is annoying and if there is a way to prevent it from showing up that would be preferred.
Can't say I've ever seen this myself, but it could be something messed up network-side, if it happens to all ROMs, so maybe try giving AT&T a call and asking them to reset your voicemail, that might just do the trick for your issue. If not, then I can't think of anything else that might cause it.
I've got an Ulefone Armor 9 I recently purchased. As part of setting it up to work as desired, I swapped away from the default messaging app to one that supports dual SIM operation a bit more gracefully.
I've since noticed that after a prolonged idle, such as sleeping, the phone drops all SMS messages. It isn't that they don't send notifications -- they simply don't exist as far as I can tell. I tried a different messenger, and while it displayed the texts received with the other one, the missing messages weren't there either.
This doesn't appear to be an issue between the carrier and phone. Or, rather, if it is it's impacting both carriers at the same time, because sending text messages to both numbers when the problem is present results in neither being delivered. The carriers don't buffer the messages for later delivery as if the phone was offline, and calls come through okay but do not resolve the SMS issue.
I can reboot the phone or manually open the SMS app/bring it to the foreground, after which point I will start receiving messages again. Only ones sent after performing this activity, however. The prior ones are lost.
I've checked to ensure that the app itself is running in the background and Android says that it is. I've not got anything that should be pausing it (that I'm aware of), so I'm not sure why Android would stop sending it messages. I'm also not familiar enough with Android to know how the OS handles texts. Clearly there's some sort of storage & OS management, because the alternate app I tried as part of troubleshooting was able to pull my message history.
Has anyone got any ideas on further troubleshooting steps, or insight into how Android handles texts in general that might help narrow down the point of failure?
GV00 said:
I've got an Ulefone Armor 9 I recently purchased. As part of setting it up to work as desired, I swapped away from the default messaging app to one that supports dual SIM operation a bit more gracefully.
I've since noticed that after a prolonged idle, such as sleeping, the phone drops all SMS messages. It isn't that they don't send notifications -- they simply don't exist as far as I can tell. I tried a different messenger, and while it displayed the texts received with the other one, the missing messages weren't there either.
This doesn't appear to be an issue between the carrier and phone. Or, rather, if it is it's impacting both carriers at the same time, because sending text messages to both numbers when the problem is present results in neither being delivered. The carriers don't buffer the messages for later delivery as if the phone was offline, and calls come through okay but do not resolve the SMS issue.
I can reboot the phone or manually open the SMS app/bring it to the foreground, after which point I will start receiving messages again. Only ones sent after performing this activity, however. The prior ones are lost.
I've checked to ensure that the app itself is running in the background and Android says that it is. I've not got anything that should be pausing it (that I'm aware of), so I'm not sure why Android would stop sending it messages. I'm also not familiar enough with Android to know how the OS handles texts. Clearly there's some sort of storage & OS management, because the alternate app I tried as part of troubleshooting was able to pull my message history.
Has anyone got any ideas on further troubleshooting steps, or insight into how Android handles texts in general that might help narrow down the point of failure?
Click to expand...
Click to collapse
I'm not sure if this would help but try messing w/ "App Blocker's" settings for your SMS app or even disabling App Blocker altogether (in the settings menu under "smart assist" I think).
BigBossPlaya said:
I'm not sure if this would help but try messing w/ "App Blocker's" settings for your SMS app or even disabling App Blocker altogether (in the settings menu under "smart assist" I think).
Click to expand...
Click to collapse
Unfortunately, it was already off, so no dice there. Ulefone pushed an update I thought might have fixed it, but after about 18 hours of idle I sent a test message and it fell into the void. Opened up the messenger app again and sent another and that one arrived without issue, but no sign of the first.