Hi,
So I have a Moto X (2nd gen) with marshmallow and root and I use google messenger. Sometimes when i text something and press ''send'' after a few seconds while it is sending the message, It then shows that ''not sent, tap to try again'' and when i tap again it sends the sms just fine. I have the same problem while using stock sms app.
It's really annoying and I always have to make sure that my sms is sent because i never know when it is going to happen. It happens really randomly. Maybe somebody got an idea what could be the cause of this ?
Thanks.
Related
It's been almost a week since the stock Messages app started acting up.
If I try to open the app by tapping the icon, it will start, briefly show the messages and close itselt with an error prompt that allows me to close it or send an error report. If I receive an SMS and tap the notification, the app opens and shows the message, I can reply and it works fine this way.
Restarting the phone sometimes solves this right away but it appears at random times. I don't text that much via SMS (mainly WhatsApp and Skype) but it's annoying to not be able to open the app to send an SMS on the rare occasions I need to.
I have an unlocked US model, I'm not rooted or anything. Using stock with Nova Launcher Prime and a couple icon packs.
Has anyone experienced this problem with the Messages app?
I'm currently waiting for the 4.2.2 update to show on the phone. I hope this is fixed in this update.
If the update doesn't fix it, I will try Textra or SMS Now. I've read good things bout them but I really didn't need an extra messaging app since I received or need to send 1-3 SMS a day.
Having a 3rd-party SMS apps will interfere with the stock Contacts and Dialer apps in some way?
ajua said:
It's been almost a week since the stock Messages app started acting up.
If I try to open the app by tapping the icon, it will start, briefly show the messages and close itselt with an error prompt that allows me to close it or send an error report. If I receive an SMS and tap the notification, the app opens and shows the message, I can reply and it works fine this way.
Restarting the phone sometimes solves this right away but it appears at random times. I don't text that much via SMS (mainly WhatsApp and Skype) but it's annoying to not be able to open the app to send an SMS on the rare occasions I need to.
I have an unlocked US model, I'm not rooted or anything. Using stock with Nova Launcher Prime and a couple icon packs.
Has anyone experienced this problem with the Messages app?
I'm currently waiting for the 4.2.2 update to show on the phone. I hope this is fixed in this update.
If the update doesn't fix it, I will try Textra or SMS Now. I've read good things bout them but I really didn't need an extra messaging app since I received or need to send 1-3 SMS a day.
Having a 3rd-party SMS apps will interfere with the stock Contacts and Dialer apps in some way?
Click to expand...
Click to collapse
First thing I would do is go into settings > apps >all. Go to messages then force stop. Reset defaults and delete data.. That should reset anything you may have changed on error. If that doesn't work do a factory reset. If that doesn't work then I would say your launcher has a conflict
Sent from my HTC One using xda app-developers app
I already deleted its cached data and reset default options. Could be Nova Prime Launcher having a conflict with Messages, but the strange thing is that it started to happen long after installing Nova.
I'm waiting for the 4.2.2 update. When it shows I will update and do a factory reset.
Thanks
So I say "text..." and Google now prepares my message but still makes me hit "send message" on the screen. I just want it to send without me touching it help?
Sent from my XT1056 using Tapatalk 2
I don't think there is a way, the fault is on Google now and not touchless controls. I was a little bummed about this to, with my sgs3 I was able to send texts through voice command and say "send"... Though, vice command was pretty useless on it, if I wanted to text anything longer than 4 words it would take me 10 tries to get it right... At least with the moto x, it gets it deadnuts 99% of the time. For now, I'll take the trade off of having to do one click and it actually working. Hopefully some day it will work the exact way that we want it... Until then, I am content.
Sent from my XT1058 using XDA Premium 4 mobile app
Semi-related but didn't want to start another thread about touchless control.
When using touchless control to send a text, I assume that because it is being routed through GoogleNow, the actual text that is sent out doesn't save in the proper threaded message history? Is there a setting or a way to keep the text in a running conversation?
I'm on Sprint stock.
Mine gets added to existing text conversions... Though, I haven't used it since I updated to hangouts 2.0 and I think there may be a bug when using hangouts as default SMS.
AT&T Moto X rocking 4.4
deanwoof said:
When using touchless control to send a text, I assume that because it is being routed through Google Now, the actual text that is sent out doesn't save in the proper threaded message history? Is there a setting or a way to keep the text in a running conversation?
I'm on Sprint stock.
Click to expand...
Click to collapse
On Verizon stock it shows up in my threaded message history. Strange.
it's not every time.. id say a good half of them don't show up.
deanwoof said:
it's not every time.. id say a good half of them don't show up.
Click to expand...
Click to collapse
the commands are being ran by different things. Don't know which one is putting it in the thread and which one isn't. But from the moto site, it says that moto trys to run any command you say into google now, if it recognizes it, it acts on it, if it doesn't recognize it, it sends it to google now to recognize it. Basically, even though it looks like google now is the app running, after you say something, moto trys to recognize the voice command. So sometimes moto recognizes it and sends the text itself, sometimes it doesn't and sends it to google services that then sends the text. You can try saying like send text message instead and see if that always sends it to google or always sends it to moto. Like i said, idk which system is the one that is showing the text correctly, but if it is google, then saying something that moto won't recognize but google will should solve your problem. If it is moto that is running the command correctly, than i guess you just have to be extremely clear when saying "text" for moto to pick it up.
pathtologos said:
So I say "text..." and Google now prepares my message but still makes me hit "send message" on the screen. I just want it to send without me touching it help?
Click to expand...
Click to collapse
I originally had the same experience; however, this behaviour _just_ changed for me over the past couple of days. As of today, when I ask Google Now to send a text, it performs all steps (from beginning to send the text to actually sending the text) via voice prompts. I assume that this is thanks to the recent updates that have been sent out over the past couple of days. Regardless, WHOO HOO!
[Q] Can't reply to texts using "reply" button and voice; everything else works
I've encountered a really strange problem on my watch (Samsung Gear Live) lately. Not a single texting app will let me use the "reply" button with voice.
Example: Friend texts me, text pops up on my watch. I swipe it and click "Reply" and try to reply using my voice. The text will write out on my watch screen, but the red Google mic icon just sits there for about 10 seconds as if its still thinking it's receiving input, and then it takes me to the "disconnected/watch is offline" screen.
But the watch is obviously not disconnected: I can exit that app and tap the screen and say "Okay Google" and then say "Text friend 'hi how's it going'" and the text will send without a problem.
I've encountered this error when using Coffee SMS, WearResponses, and Google Messenger. I've reset the watch, and cleared Android Wear data, and the problem still persists. This makes no sense. Any ideas/suggestions?
I just got my Zenwatch 3 today. Everything is fine but using whatsapp is inconvenience... there is no dedicated app...
If I keep swiping in the home screen to right eventually I will reach a contact page, after selecting a person there is some options like make a call, send a sms, and "whatsapp". However the whatsapp action is not working, everytime I press that there is a loading circle appears for a few seconds, then saying unable to reach Google...
Receiving notification and replying a whatsapp message has no issue, but I just can't initiate whatsapp from the contact page... tried to start whatsapp in phone but not helping...
I tried to search for solution but seems no one has this issue.. can someone give some tips on this? Thanks.
I just checked it with my watch and can confirm the message. I can't remember if it worked when I first set up my ZenWatch. It's my first Wear Device and I just have it for three weeks, so I don't know if it should work in general.
When I choose that option on my watch it gives me speech recognition to write a message. I am not having any problems whatsoever. It just doesn't work too well if my phone is dozing.
Hi,
I was wondering if anyone has encountered this nonsense issue:
When trying to send a sms or Whastapp message with ok google assistant, when you specify who you want to send it and what is the message, then the watch forces you to press the screen for send or cancel the message. Whats the use of saying everything out loud if you need to confirm the sending of the message with your finger?? If you are using voice commands it's because you cannot press the screen!
When adding a new reminder it does not do that. It shows a button with an x and a circle counter line so if you don't stop it, it will save the reminder. That really makes sense and its the way I usuallty send messages on wear 1.5.
Is it the Ok Google app?
Thanks!!
I thought it was confirming it's transcription of my message
roebling said:
I thought it was confirming it's transcription of my message
Click to expand...
Click to collapse
Yes of course, but it does not make any sense to have to press the screen to send it. When talking to the watch it´s because you can not press the watch screen. For example: biking. I think some developers design and develope software that they don´t use and that´s a shame.