In Viber text message typing, the google voice keyboard does not work for me. Sometimes it pops open and then closes immediately. Sometimes it's open, but does allow activation of the microphone. If I remember correctly, This also occurred before I installed the Android 6 ota last week.
Any one else having this?
Viber support has suggested uninstalling + re-installing, but that will lose the message history.
Thx
Could anyone with (latest) Viber app test this? Thanks!
Hi there! Yes, I've had this problem for a couple of months, too! It's maddening! I actually wind up dictating into the "notes" app, then copying and pasting from there into Viber!
When I contacted Viber support, they responded very quickly but asked me to send them a video of the problem. I never did that since I didn't know how to capture screen video on my phone. So, they just closed the support ticket.
Thanks for your response!
You do have the M9, right?
That must mean you've had the problem both with lollipop and (if you updated) marshmallow?
I have had my M9 for only 2 months now, and in my mind, I noticed it fairly early on, though as I don't always use Voice typing I'm not sure when I noticed it. I find that Voice typing works much better on this device then on my previous one - an HTC One X+
If you mention your ticket number, I can mention it in mine.
Anyone else can report their experience (working, non-working). Even on an M8 maybe?
I've additionally noticed that the feature d or "hold and talk" (*) in viber messaging does not work. it records silence
This lets you send short audio messages instead of written text
Does anyone have Viber working on the m9 and working correctly?
Related
Hello everyone, I would like to start by saying thank you to everyone here, all of your posts, info, etc has been excellent in helping me along my way to learning enough about this stuff to be dangerous to mine & my friends phones...we're all still using them so that's a "Win" in my book
Now, on to my problem. I've tried googling & searching posts here, and I don't know if it's just the terminology I've searched but I've found nothing similar to my problem except where a thread had to do with EMBS messages coming through incorrectly.
First off, I'm on a Sprint Branded Samsung Epic Touch 4g Galaxy S II (whew that's a mouthful already) It is on Verizon Prepaid Service.
When I first set this phone up, everything worked correctly - Talk, Text, Web, MMS, WiFi Hotspot, Etc - all working perfectly. I was able to send & receive picture mail through MMS, etc.
I am currently running CyanogenMod 9-20120416-SNAPSHOT-epic4gtouch-Alpha 3
Android Ver 4.04
Kernel Ver 3.0.15-SPH-D710.FD10-CL377892
This is the updates I installed to this phone originally:
gapps-ics-20120429-signed
StockCWM-EL26.tar.md5
update-cm-9-20120416-SNAPSHOT-epic4gtouch-alpha3-signed
mmsfix.zip (and made the correct changes for Verizon)
As I said, the phone was 100% functioning at this point for several days. The problem that came up happened out of nowhere, no changes were made to the phone whatsoever, not even a random app was installed from the market.
The only apps I have installed are
Wifi Tether (Rooted Users)
ES File Explorer
Facebook
GMail
Craigslist
Facebook Contact Sync
NFL Scoreboard
QR Droid
SuperUser
Rom Toolbox
Rom Manager
Terminal Emulator
Other than that, it's just what ICS & GApps Installed.
So here's the problem - whenever I recieve a text from anyone now, if it comes in multiple texts (ie 1/2, 2/2/ etc) it shows up as all special characters when I recieve it.
Here is the last one I got, I sent it from another phone on the same carrier - I just typed myself a message until I was sure it would be a 2 part message and this is what came through on my Epic
First Msg
ß<xp¿AcGÉ?üööysgOS&Læ;6lX9W/Ü<9rfEØΨ+FøÆ8xp¿A¥ìÅß<xqF<9$fÅz<EEggÜNixw¿
5¥rdåÆΩÖÅΠ'ålÄ3gF
3vø)rlyscW/Ü>ñzsbEKΨ/ÜÆ_gGEìgVLhurd1äñ2AÅZ#ΛC<z¡@@@@@@@
Second Msg
Ü=ävhPfOÉ?N3vlY1cnÖ<yreIΨ/Ü<9rfEØC¥ìÅÆ8xpaCì
Λ(XΔA$éZTGøΔHEwì/ÖrsOà#Ec=P
I put it in a hex/text converter and the text version came up all "?'s" so I'm pretty much at a loss at this point.
I apologize for a long winded message, but I wanted to include as much information about my phone, etc as possible to get the best answer I could.
Again, thank you all and if anyone has any insight to what might be causing this, I would greatly appreciate the info.
Oh, and in case I didn't make it clear - at this moment, text works fine (if its only 1 text at a time incoming) I can send multiple page texts & the recipient gets them no problem, and I can send/recieve pictures, etc as mms with no problems...the problem only exists if it's multiple pages of text coming in at once.
Thanks
What happens if you use a 3rd party messaging app like handcent?
someguyatx said:
What happens if you use a 3rd party messaging app like handcent?
Click to expand...
Click to collapse
I just tried a few diff versions of Handcent, with the settings Default, then again with the settings on "Default SMS/MMS App (Disables Stock & Other Messaging Apps) and got the same results...
The wierd character code that comes through is exactly the same, both with the stock app & handcent in case that might be a question...
**Update**
I have Google Voice number sending voicemail converted as text to my phone on a secondary number. I got one today, was 3 pages SMS and it came through perfectly, right after that, I got a reg text from someone elses phone that was 2 pages, and it was the same type characters, and a few more since that were all the same special characters.
I've tested the Google Voice translation a few more times, and it comes through perfectly. I also tested just sending a multi-page text to my google voice number, which just forwarded the texts to my phone via SMS and they also come through perfectly.
So SMS from Google Voice in multiple texts works great, but from another phone do not.
If anyone has seen anything like this, I would love to know I'm not alone.
I'm having this exact same problem too. I noticed multiple texts incoming from certain people are fine, but when I receive multiple texts from a few others or a group sms from an iphone I get this really wonky characters. Any help would be appreciated. I am using this phone through pageplus.
I've been using Textra for SMS for a few days now with my new HTC One M8, and have been quite pleased. But some time this afternoon I noticed that when I try to use the voice to text function within Textra, which had been working just fine, my phone makes the sound as if the function is starting, and I think the screen appears for a split second, but is then replaced by the Textra messaging screen, and there is no way to record my voice. The function still works in other apps where it worked before. I tried uninstalling and reinstalling Textra, without any luck. Then I looked at the update history and saw that Textra pushed out an update today, so I’m wondering if this update could have broken this functionality on the HTC One M8.
Anyone else with this phone using Textra and experiencing the same thing?
I have already written to Textra support.
Andyw2100 said:
I've been using Textra for SMS for a few days now with my new HTC One M8, and have been quite pleased. But some time this afternoon I noticed that when I try to use the voice to text function within Textra, which had been working just fine, my phone makes the sound as if the function is starting, and I think the screen appears for a split second, but is then replaced by the Textra messaging screen, and there is no way to record my voice. The function still works in other apps where it worked before. I tried uninstalling and reinstalling Textra, without any luck. Then I looked at the update history and saw that Textra pushed out an update today, so I’m wondering if this update could have broken this functionality on the HTC One M8.
Anyone else with this phone using Textra and experiencing the same thing?
I have already written to Textra support.
Click to expand...
Click to collapse
I received a response from Textra support. Turns out they --did-- break it. Here's what they wrote:
--
Just issued an update for that in Google Play, should appear in the next hour or so. Apologies.
Max - Textra SMS Team
--
Wow, I must be the first one with a Zen Watch problem... or at least the first one with a Zen Watch... lucky me. Also, first time poster, so I hope I'm doing this right!
The issue I have occurs when I try to send a text message from my watch. When I do, I use voice to select a recipient as I would with Android Wear on any other device. While it looks like the message is sent from my phone (i.e it shows up in my message history with the selected recipient), the person never actually receives it. When I click on "Message Info" in the conversation history, it looks like the watch is adding "01" to the beginning of the phone number. The only thing I can think of is that this additional "Country Code" is screwing up the text.
I'm using a brand new S5, and it occurs in the stock messaging app, the Verizon messaging app, and Google Hang Outs. Any one have any ideas?
carlso.aw said:
Wow, I must be the first one with a Zen Watch problem... or at least the first one with a Zen Watch... lucky me. Also, first time poster, so I hope I'm doing this right!
The issue I have occurs when I try to send a text message from my watch. When I do, I use voice to select a recipient as I would with Android Wear on any other device. While it looks like the message is sent from my phone (i.e it shows up in my message history with the selected recipient), the person never actually receives it. When I click on "Message Info" in the conversation history, it looks like the watch is adding "01" to the beginning of the phone number. The only thing I can think of is that this additional "Country Code" is screwing up the text.
I'm using a brand new S5, and it occurs in the stock messaging app, the Verizon messaging app, and Google Hang Outs. Any one have any ideas?
Click to expand...
Click to collapse
I tried a couple of times and it worked for me. Sprint HTC One Max Stock. Stock messaging app. Not using hangouts. That probably doesn't help much but at least lets you know it 'can' work.
I think your theories about country codes, etc may be right, but I would think you'd have the same issue if you do it via 'Ok Google' from the phone itself?
Faxman said:
I tried a couple of times and it worked for me. Sprint HTC One Max Stock. Stock messaging app. Not using hangouts. That probably doesn't help much but at least lets you know it 'can' work.
I think your theories about country codes, etc may be right, but I would think you'd have the same issue if you do it via 'Ok Google' from the phone itself?
Click to expand...
Click to collapse
Hey Faxman,
Thanks for the response! Actually, you're right. I just tried it, and the same thing occurs if I try to send a voice text directly through Google Now on my phone. The message shows up in my conversation history, and looks like a normal text from my end. But it is never received at the destination. I still think that my country code analysis is the root of the issue, but I have no idea how to change it without attempting a 3rd party message app. I don't have a problem doing that inherently, but I would rather fix the problem then bandaid it
Any ideas from the massess would be awesome!
Hi all, was working nicely for a long time.
Now it either just says "Something went wrong" or "There are no new messages."
I've spent multiple calls with Google tech support, nothing. Still same problem.
Pixel 3 XL, about 4 month old phone.
Would have used the default text app but I really use the scheduler function that Textra has, along with the 9-second delay.
Per Google tech support I also tried downloading another third-party app, like Pulse. Having same problem of not being able to read new text messages. It's one of the most important functions for me especially driving around, and being able to hear new messages & respond hands free!!
THANK YOU!
91709jack said:
Hi all, was working nicely for a long time.
Now it either just says "Something went wrong" or "There are no new messages."
I've spent multiple calls with Google tech support, nothing. Still same problem.
Pixel 3 XL, about 4 month old phone.
Would have used the default text app but I really use the scheduler function that Textra has, along with the 9-second delay.
Per Google tech support I also tried downloading another third-party app, like Pulse. Having same problem of not being able to read new text messages. It's one of the most important functions for me especially driving around, and being able to hear new messages & respond hands free!!
THANK YOU!
Click to expand...
Click to collapse
I know this isn't exactly the answer you're looking for, but you mentioned replying hands-free while driving. Android Auto has this functionality. You can listen to and respond to messages with just your voice. It even works with facebook messenger! I do 95% of my communicating through messenger, all that was really important to me. Anyways, hope this helped some.
Sent from my Pixel 3 XL using Tapatalk
I use the native Samsung Messages text app that came with the Fold 3 (can't use Google Messages even if I wanted to because it doesn't show a bunch of past texts from my previous phone that I need access to). For the past week or two, a few contacts who also use RCS Chat texting have the blue/green dots on the Contacts list in the app, but not on the Conversation list, and it won't send Chat texts, only SMS/MMS, to them. But, their texts often come to me as Chat texts. This app has no way to toggle Chat on/off to reset it, but neither Airplane Mode nor restarting my phone (including after the T-mobile update with the eSIM/dual-SIM additions) fixed the problem.
Is anyone else having this problem? Is there a way to fix it from my end? Or is it a Google server issue (it began with one of those times everyone's dot flashes off and then back on when you tap on them)? I know the person uses Google Messages because they don't have a Samsung phone (I think they have an LG). It is pretty important for one contact it isn’t working for to see if/when they read their texts. (Thankfully, for the other important one, theirs is working, and that's a Google Pixel phone.)
Anyone have an answer or also have this problem?