I have been seeing this message when using OK Google to send a text message. All works fine...contacts lookup, text composition and send. Then I see:
"try again on phone"
BUT it Actually sends text message?!?
Any idea how to fix this. It's annoying.
I have had it happening on Android 6, 7 and 8 (8.1) all with my Zenwatch 1
Thanks,
Rich
No one has seen this?
Related
For some reason my device tells me I have a unread text message, ALLLL THE TIME.
I've deleted every message out of my inbox and email inbox, but it still says I have a message.
Is there a quick fix for this?
If not, its not big deal, it gives me more of an excuse to flash to the new beta touchit for wings, but if there is a fix I'd like to know what it is.
Thanks in advance.
Hello everyone. I apologize if this question has been asked already.
On my "dumb" phones like LG etc. in Verizon network, I can send text message by 1,000 characters w/ extended text message. I think it sends multiple messages encoded in a special way to get past the 160 character SMS limit.
But, on my Windows Mobile devices, I can only send/receive 160 char messages, and when I receive 161+ char message, I receive a notice saying that the text message has been modified to be compatible with this device.
Why is "dumb phone" so much better to handle extended text messages but Windows Mobile cannot receive? It's a little bit oxymoronic, don't you think? Is there any way to enable extended text messaging functionality to windows mobile devices? Thanks in advance!
odd when i go over 160 it tells me that 2 sms's will be sendt maybe it's a setting
or something in your rom
I can send, but it doesn't compile them all into one single extended text message. So recipient receive many text message all at one time... they say it's annoying.
Then, if they send me extended text message, I receive 160 char, and after that.. it break away and say "extended message has been truncated due to a lack of support for enhanced messaging on this device."
I just got my Verizon Galaxy Note 3 yesterday and so far loving the device. I've noticed one thing that is a little odd though and wondering if anyone else is experiencing this. When I sent SMS messages, the "read receipt" doesn't work properly. If you press and hold an individual sent message and then select "view message details", it says "Error code:Addr.Vcnt.". The message however are delivered just fine and nobody on the other end notices. I use Chomp SMS as my SMS app, and because of this error code the messages always say they are "pending" instead of checking off with a green check box to indicate that they were received. I don't think it's a Chomp SMS issue because the same error code comes up if I sent my messages through the stock SMS app.
MMS messages work just fine, so the issue only occurs with SMS messages. Has anybody else experienced this and know of a fix?
pdykstra said:
I just got my Verizon Galaxy Note 3 yesterday and so far loving the device. I've noticed one thing that is a little odd though and wondering if anyone else is experiencing this. When I sent SMS messages, the "read receipt" doesn't work properly. If you press and hold an individual sent message and then select "view message details", it says "Error code:Addr.Vcnt.". The message however are delivered just fine and nobody on the other end notices. I use Chomp SMS as my SMS app, and because of this error code the messages always say they are "pending" instead of checking off with a green check box to indicate that they were received. I don't think it's a Chomp SMS issue because the same error code comes up if I sent my messages through the stock SMS app.
MMS messages work just fine, so the issue only occurs with SMS messages. Has anybody else experienced this and know of a fix?
Click to expand...
Click to collapse
Just as an update in case anyone else ever runs into this problem, I uninstalled Chomp SMS and read receipt started working again.
I just upgraded my Nexus 7 3G (2012) to 4.4. It used to be on 4.3 that, despite not coming with a proper SMS client, I could install one third-party and send/receive.
Here is what happens now. I can install 8sms and it will tell me it is not my SMS app. However when I tap "SMS Disabled" in Settings, nothing happens. There does not appear to be an SMS system setting on this stock ROM. So I can't seem to get it out of "Sending disabled" mode.
When I text from my phone to my tablet, I get a messaging notification in my tray from Android itself, but tapping it opens up just a toast notification. The message does not actually seem to get recorded anywhere. In 8sms it just appears as (No subject).
Any thoughts on whether this may be surmountable?
I can't answer you but I have a question: where can I find incoming messages? I'm on prepaid and there are incoming messages from the carrier but I can't read them.
bigsee said:
I can't answer you but I have a question: where can I find incoming messages? I'm on prepaid and there are incoming messages from the carrier but I can't read them.
Click to expand...
Click to collapse
They come into the notification tray for me when they arrive, but after reading them they are not stored anywhere. The information just vanishes.
I got the Samsung Gear at IO (yea) and have been going through the user adjustment phase, happily have pretty much everything working (I use a Galaxy Nexus as the phone stock. I receive text and I can send emails (from the watch) but for some reason I can't send text from the watch. It says it is sent, goes through all the motions, asks for recipient, clarifies to send to the mobile number and gets the text via voice and then says it is sending and gives a success green check, but the message is lost does not show on phone hangout or messaging log, nor does the recipient get it.. Anyone have any ideas?? or is my problem unique to me?
Hidden choice message on Phone for sending text
Finally found my "missing texts.. when I was sending, the phone was opening a choice dialog to choose between Google voice or messaging, I chose messaging and checked always and all is now working, buy the way retweeting to twitter using the bunting app has a similar issue, it opens the native vs edit retweet chice, which cannot be set to default one way so you need to pull the phone out...