Related
Since the update to GB... my voice-to-text has not been working properly in the car. I first thought it might be background noise like the A/C or something but it appears to only happen when the car is moving.
Isn't this the whole point of voice-to-text? To keep you safe while driving so it doesn't require typing. Am I the only one with this problem? Is there any kind of workaround? I depend heavily on this feature. This is a big negative for me.
Same issue here. Voice to text has been broken for me since the first GB update on a stock unrooted EVO.
busted here too.
sucks.
Yes this happens to me too.
Just quit using your phone in the car so i can quit flipping you people off!
Have y'all tried updating voice search from the market? I noticed there was a recent update for it mentioning bug fixes.
Tried updating everything. Full factory restore on Unrooted GB 2.3.3 both the first release and with the maintenance fix. Changed Voice Input and Output settings. Changed the Google account dashboard and personalization. Everything and even rolling back to 2.2 which doesn't work because of the new Hboot.
It is completely broken. You get going 20-25mph+ and the mic does not respond.
Hope that it is address in a future release update (not likely), but will have to root and roll back.
Can any one that is rooted and on the stock 2.3 or different rom confirm if voice search is working for them?
AudioJerm said:
Have y'all tried updating voice search from the market? I noticed there was a recent update for it mentioning bug fixes.
Click to expand...
Click to collapse
Yeah... I updated Voice Search and I will find out later if it works when I get in my car.
Well, I did the Voice Search update and still can't do voice to text in the car while it's moving. This is ridiculous! I love using HeyTell especially when driving and now it has become useless.
A guy at work asked me today if i knew anything about this problem. He has had this problem since the GB update and his EVO is stock and not rooted. I told him I would look into it. Looks like I found the answer.
Sent from my HTC EVO 4G with Tapatalk
I did; however, find out that the voice search does work in the texting mode once you've hit the car in front of you wondering why it wasn't working during the driving process. Once stopped, it is amazing!
EDIT: OK..couldn't resist, but reminds me of the little "Don't use this while your driving" disclaimer in the gps units turning them on.
I've had issues with it when not moving.
I'm not sure where this connection to driving comes into play?
dpilcher said:
I did; however, find out that the voice search does work in the texting mode once you've hit the car in front of you wondering why it wasn't working during the driving process. Once stopped, it is amazing!
EDIT: OK..couldn't resist, but reminds me of the little "Don't use this while your driving" disclaimer in the gps units turning them on.
Click to expand...
Click to collapse
The whole advantage of voice-to-text is so you don't text while driving. My phone sits in a dock in the car. If someone texts me, I can verbally respond without taking my hands off the wheel. You know... kinda like talking on the phone hands-free. That's why voice-to-text is so valuable to me.
Earlier tonight I discovered the problem is worse. I was outside taking a walk and decided to use voice-to-text and nothing. Would not recognize. But once I stopped walking and used it... it was fine. So it's not just limited to driving. They need to fix this problem!
I did some looking around on Google and this issue has been reported on multiple different sites. However, it seems that it's more related to background noise rather than being in a moving vehicle. If there is any amount of background noise, voice to text seems to not work properly. It seems that it works fine if you are in a completely silent environment.
Sent from my HTC EVO 4G with Tapatalk
kd0axs said:
I did some looking around on Google and this issue has been reported on multiple different sites. However, it seems that it's more related to background noise rather than being in a moving vehicle. If there is any amount of background noise, voice to text seems to not work properly. It seems that it works fine if you are in a completely silent environment.
Sent from my HTC EVO 4G with Tapatalk
Click to expand...
Click to collapse
Yeah... I read the same thing but my tests did not ring true. When I was stopped at a light, I put the AC on at full blast and the voice-to-text worked flawlessly. But as soon as I moved and even with the AC off... nothing. For me, there didn't seem to be any connection with background noise... only movement.
My only other suggestion is to try an app called Vlingo for the mean time. The In Car mode is amazing. Just say "hey vlingo" and it starts listening to commands. It really is completely hands free. You never have to touch your phone to send texts and it even reads your message back to you to confirm before sending. I've never had problems with it although the in car mode is still in beta. Good luck!
I just spoke this entire post while driving 45 miles an hour down the road using Google voice search.
I had same issue on stock Rom. I believe if u look at main settings, voice input and output, text to speach settings, and in there it should say something about downloading something. If it needs updating u can press it and market will open with what u need
Sent from my PC36100 using XDA App
So I tried going through the text-to-speech settings but no luck. The issue doesn't seem to be with text-to-speech but with voice-to-text. It's like the microphone stops picking up audio when in motion.
Nevertheless... got this today from HTC...
Dear Jack Storm,
We are sorry to hear that you are experiencing issues with your Voice to Text after the recent update.
We are aware of the issues surrounding the update to your Evo and are currently working on addressing these issues. We do not currently have an exact timeframe as to when all of these issues will be resolved. Please check our official media outlets and/or your device for any change to the update status.
We do apologize for any inconveniences that this may have caused, Jack.
To send a reply to this message or let me know I have successfully answered your question log in to our ContactUs site using your email address and your ticket number 11USCW26ENA0065.
Sincerely,
Reisa
HTC
Works fine on CM7
Sent from my PC36100 using XDA Premium App
So this is the second S5 I've had and same issue. First one, people could hear me if I called, but if they called me 90% of the time they couldn't hear me on the 1st call. If they called right back or I called them it was fine, usually. I've seen a lot of complaints about this on the S5 online. I even have a copy of the my youmail voicemail that I made on my S2 that was crystal clear and more louder/pronounced if that makes sense, and the voicemail I made on my S5 was all fuzzy and kinda garbled like I was talking 4 feet away from it. Replaced with another S5, and it started happening again except now I'm rooted so no more warranty and they can't/won't do anything. Stock or rom, it happens. So I know a few S5 owners, 3 of them have the same problem. All different networks so not specific to any provider (like if it were an at&t issue etc).
I tried clearing the pin hole at the bottom but didn't seem to make a difference. People think the S5 does this maybe b/c it's water resistant and theirs a membrane inside that hole for the mic that makes it garbled. Speaker phone it works fine. Just pissing me off, I love the phone otherwise, but this is my work phone as well and it's so nice and professional to keep playing phone tag with clients .
This doesn't make a lot of sense. You say that this is a well known, widespread problem that happens on various carriers. Which is hard to reconcile with the fact that I haven't heard of the issue and few people here or anywhere else are complaining of it? We have over 500 S5's deployed in my workplace and zero reports of this nature. XDA has 6 million members and we don't see a trickle, let along surge of reports here either.
This is highly unlikely to be a hardware issue or we would be hearing about it a lot. Likewise if the issue showed up with any frequency due to a specific firmware version. It's most likely user settings and you provided zero details about your configuration. Or I would have said a carrier issue, but you not only didn't tell us who your carrier was but you dismissed this out of hand saying that you see the problem all over, including three S5 owners that you know yourself using different carriers.
Making user settings, how you use the phone the most likely cause.
There isn't much to work with unless you provide detailed information about your configuration. How about some links to the frequent occurrences of this problem that you said you see all the time. Link us to a recording of a representative call where the problem occurs. And any information that might suggest or exclude patterns, e.g. what carrier you use, what carriers your other 3 friends use, what time of day does this happen. Does it happen only in fringe areas, only with strong signals, only with wifi calling, et cetera.
.
fffft said:
This doesn't make a lot of sense. You say that this is a well known, widespread problem that happens on various carriers. Which is hard to reconcile with the fact that I haven't heard of the issue and few people here or anywhere else are complaining of it? We have over 500 S5's deployed in my workplace and zero reports of this nature. XDA has 6 million members and we don't see a trickle, let along surge of reports here either.
This is highly unlikely to be a hardware issue or we would be hearing about it a lot. Likewise if the issue showed up with any frequency due to a specific firmware version. It's most likely user settings and you provided zero details about your configuration. Or I would have said a carrier issue, but you not only didn't tell us who your carrier was but you dismissed this out of hand saying that you see the problem all over, including three S5 owners that you know yourself using different carriers.
Making user settings, how you use the phone the most likely cause.
There isn't much to work with unless you provide detailed information about your configuration. How about some links to the frequent occurrences of this problem that you said you see all the time. Link us to a recording of a representative call where the problem occurs. And any information that might suggest or exclude patterns, e.g. what carrier you use, what carriers your other 3 friends use, what time of day does this happen. Does it happen only in fringe areas, only with strong signals, only with wifi calling, et cetera.
.
Click to expand...
Click to collapse
Pry exaggerated as a bit frustrated. Away for business and on phone right now. I just googled various call issues and saw same/similar on other phones, quite a few S4 reports (like googling S5 can't hear me, or can't hear calls, or android can't hear calls etc). Again not exactly the same but similar, found older Android phones people talking about the same. S5 people I saw post in various threads on different forums, not necessarily made a thread of theirs (like they found an issue like that and bumped thread even if it was a different phone). I'm on AT&T, 3 friends one is T-Mobile and others are Verizon. Though theirs isn't near as bad as mine, theirs happens infrequently on both ends which makes me think maybe carrier related, whereas mine is almost always the caller on my end not hearing me well on the first call. I have two employees with S5s as well and no issues with theirs like this.
I don't know what user config info you want? I've rooted and flashed android for years, I hardly ever touch anything volume/call mod related. I don't know what settings you'd be talking about, stock or rom is the same (didn't install viper, didn't do anything with volume controls on DK as their borked on this version etc). Changed background noise on/off but didn't do anything.Not sure how I use the phone would do anything, they call, I answer, I call, they answer? Happens anywhere no matter signal, whether full bars at house, or office, or lose a few bars when traveling, time of day doesn't matter happens anytime. I just had a conference call where I ended having to use speaker phone for them to hear better but they still said it wasn't clear. Wife just called me and she said through the phone or speaker it's like I'm talking through a towel (speaker not as bad). My AT&T store said they've had a few people come in with complaints of call issues on their S5 but in various ways, and sometimes a factory reset worked, sometimes not. Which didn't work for me, and I blew a canister of air and use a small pin like some said they did to see if anything was clogged in the Mic port but no difference.
I'll be back in a bit, but I could try to record a call with my wife. And I'll upload the files from youmail voicemail where you can hear how loud/pronounced and clear my message is from my S2, and the garbled message from both S5's.
Think I fixed it, let's hope. So I went into safestrap, tried a few things, fix permissions etc. No difference. Restored a few times, no difference, did 3 factory resets, no difference. Each time I either message someone to call me to test, or I logged into youmail to record a new greeting and heard it fuzzy/garbly. Did one more factory reset, msg'd wife to call again, she called and first thing she said was omg it's way louder and cleaner sounding like I'm not muffled. I logged into youmail, did a new greeting and yup it's 100% normal sounding. So no clue why this worked all of a sudden with all my other tries today and before. My first S5 they tested at the AT&T store and it luckily did the issue there so they could hear what I meant and note it. They gave me a loaner and it was sent in, and I guess luckily it was reproducing that same issue when it was checked as they did a replacement since the phone was only 2 months old. And now that I think about it I doubt the tech or whomever was checking it out sat there and did multiple restores/resets like I did, and I guess I was really lucky they didn't get it and test only to have it operate normal like the 10% of the time or whatever it did.
Being rooted now sending in was pointless, as knowing people over the years that have even if sent with stock rom, warranty was denied. F'd up thing is they have to prove rooting caused the issue, I don't have the time nor want to deal with that crap. Example I love cars/trucks and mod everything we have, and with the Magnuson-Moss Act they have to prove your "mod" directly affected the failed part/problem. In the phone world you end up just getting transferred around and dealing with crap trying to sort that out. I have one of my cars modded (ctsv) with pulley swap, full exhaust with lt headers etc, custom tune yada yada, one of my trucks has custom tune/intake/headers/no cats/custom exhaust etc and neither had problems with getting warranty work done, b/c doing a custom tune and pulley etc isn't going to make your radio or nav fail. In the phone world on the other hand they'll tell you to pound sand, root and mic fails, oh that'll be our diagnostic fee part replacement $ have a nice day. lol
i'll try to upload audio files from youmail showing the sound quality difference when I get a chance. I know one of my friends tried a factory reset and didn't work. Guess I'll tell him and the other two to keep doing resets over and over till it works lol, whether that means 5 or 10 times. Why it didn't work on the 1st or even 2nd try is beyond me
I'm currently running Temasek's 12.1 ROM, but have flashed the nightly cm-12.1-20150528-NIGHTLY-hlte and there seems to be a problem with Emergency calls. It's not just Australia, but USA, Brazil and several other locations have all got the issue. We've tried a wide variety of possible ROM's but the problem appears to be generic to CyanogenMod.
Can people please check if they can actually make an emergency call to their local country number? Specifically those running AOSP ROMs, but also those with Custom stock-based ROMs. Emergency calls work on firmware from Sammobile so it is either only CM base or perhaps custom ROMs as well.
Symptoms are, the normal emergency number says 'Dialing' but nothing happens - a soft reboot is required to hang up the call, even though it SAYS 'hanging up' It doesn't seem to matter if you dial from the phone app or do Emergency call from the lock screen.
Putting the country dial code in front of the emergency number brings a response that the number is incomplete.
e.g. In Australia, 000 fails, 61000 and +61000 all bring the error.
This is a fairly serious issue if it is generic and not just those of us who have flashed Temasek. You may not use Emergency call often, but when you need it, it is likely to be literally life or death.
Can people please note if they succeeded or not and which ROM, Phone model and kernel they are using?
Also if anyone knows just which file deals with emergency calls that could be useful.
Bump...
No CM/AOSP users have read this?
No one cares because everybody dies eventually.
I am having the exact issue you have described. Tried running Tamasek 12.1 on Sprint Note 3. Could not connect to 911 or different variations of the number.
kenny1991 said:
No one cares because everybody dies eventually.
Click to expand...
Click to collapse
- it's HOW we die that matters...
Plus it may not be Self but significant other that needs the emergency help.
supra2121 said:
I am having the exact issue you have described. Tried running Tamasek 12.1 on Sprint Note 3. Could not connect to 911 or different variations of the number.
Click to expand...
Click to collapse
I've raised an 'issue' over on the CM forum site - so far it appears to have escaped notice. I wonder how they'll feel if peiople start posting about the injured, mugged, assaulted etc. that can't be reported?
Strangely I thought it would be seen as an urgent issue. Go figure...
I was told by Zelendel that all CM ROM's have the issue but it is OK on AOSP ROMS. I have now tried SlimROM and BlissPop ROMs, both AOSP and neither of them can call Emergency.
Given some countries have legislated that all phones must be able to dial Emergency, there comes a question of whether we are committing illegal acts in modifying a phone so it cannot call Emergency...
For anyone that finds no emergency calls to be a deal breaker, the Alliance ROM works and is a very good ROM for being able to set it up how you like - very configurable and with good support.
I am having the exact issue you have described.
sseuorosal said:
I am having the exact issue you have described.
Click to expand...
Click to collapse
Valid point! You can only check by making a real call. And what I am going to tell the police or the fire department? “Sorry I was just wondering if my ROM is supporting emergency calls!” And that’s the deal breaker why nobody dares to make a call
dnize77 said:
Valid point! You can only check by making a real call. And what I am going to tell the police or the fire department? “Sorry I was just wondering if my ROM is supporting emergency calls!” And that’s the deal breaker why nobody dares to make a call
Click to expand...
Click to collapse
Update re the Emergency call issue - at CYAN-6622 - issue has been upgraded to major and apparently people can vote on it so if you're concerned that you don't have a phone that can be used to save your (or others) life in an emergency, please vote there.
Also apparently the issue goes back to at least CM10 and possibly CM7 days and it is on multiple phones, not just Note 3's.
Anyone got access to a nexus? If the issue is so widespread it would almost have to be in the base from Google. So maybe if it also happens (or doesn't happen) on a Nexus we can get Google to fix things.
For Americans concerned about dialling 911 you can call your local station and ask to make a test call, then when you do you can tell 911 you have the Despatch permission for a test call - so no fines.
Thanks to all those who got involved in the Jira issue - apparently it is now resolved and Temasek will have the fix in his update due today. Those on other AOSP/CM ROM's might like to nudge your devs about getting the fix. Should be in CM nightlies today I think.
I have been having an issue with people having trouble hearing me or saying that I am breaking up while on a phone call. This issue started after the latest update which came out about 2 weeks ago. I think it was a security update.
When on a phone call where people are having trouble hearing me, I can either put a headset on or put it through the speaker then the person on the call can hear me normally. I have tried a factory reset, deleting the cache, removing the sim card and put it back in but nothing has fixed my issue.
I do not think that it is a signal problem because of what I said about having no issues if I am using a headset or the speaker phone. Also, I have ruled out a mic problem by taking a video and talking normally then playing the video back. When playing the video back, I can hear myself without a problem (this suggestion was made the Huawei itself).
Does anyone anyone know what is going on? Or is having similar issues? I really don't want to be without a phone if I have to RMA my phone. Huawei's customer service said that they would not send a replacement phone prior to them receiving the RMA (if there is an issue with the phone of course).
I am on the Verizon network. Any suggestions is welcomed. Thank you.
I too am on Verizon and seem to have call quality degraded in the past month. I have no idea why. I live in southern Md.
Same here. Thought it was my case as it started about the same time i got the case. I'm in Central Florida, in a good coverage area. Phone was fine until last update. Now having bluetooth issues and this call issue.
Maybe this is just the noise cancelling mic issue that so many reported when it first came out? I may try to root and turn off the mic as suggested to see if its better, unless one of you guys are rooted and have done that already?
Can I roll back to pre-may update somehow?
yes
I too am
I'm still having the muffled / echo voice issues - putting my finger over the noise cancelling mic seems to "fix" it for me but I'm desperate for a proper fix - otherwise I can see myself jacking in the 6P for another phone soon
Hepperz said:
I'm still having the muffled / echo voice issues - putting my finger over the noise cancelling mic seems to "fix" it for me but I'm desperate for a proper fix - otherwise I can see myself jacking in the 6P for another phone soon
Click to expand...
Click to collapse
Have you tried (or are you) root and disable the noise cancelling mic? Think I may go this route if it continues (which I expect it will)
Unfortunately I use my phone for work, and the software will disable if it detects the phone is rooted - so that's a no go for me.
I had some issues with mine on Verizon. Turning off Enhanced 4G LTE Mode in cellular networks fixed my problems.
shiftr182 said:
I had some issues with mine on Verizon. Turning off Enhanced 4G LTE Mode in cellular networks fixed my problems.
Click to expand...
Click to collapse
Same for me
Sent from my SM-T320 using Tapatalk
Turning on enhanced Lte fixed my call quality issue actually, I had the same breaking up issue with it off. I still have the noise cancellation issue where people can't hear me unless I'm talking right next to the mouth piece though. Did you try wiping your cache partition in the boot up menu?
Wow, no issues for me from the latest update at all. I am in a crappy reception area so needed to turn off enhanced 4g when I got the device about 4 months ago but it's been nothing but great with VZW despite crappy reception.
Hepperz said:
Unfortunately I use my phone for work, and the software will disable if it detects the phone is rooted - so that's a no go for me.
Click to expand...
Click to collapse
Using root cloak is an option.
Had issues again last night. Seems when there is any background noise is when the issue presents itself. I'd venture to say this isn't just with VZW. I was able to stop it by placing my finger over the noise cancelling mic on the back of the phone. Guess its time to root and disable it...ugh
See the 800 and counting posts on the Google Help forum. Search "Muffled Voice 6P" and you'll see what I'm talking about. Basically, a bunch of these phones don't work as phones, and Huawei either doesn't want to pay to fix all of them, or more likely, doesn't know how to fix them. The problem with Chinese companies is the same problem Mao had back during the Great Leap Forward. He demanded enough grain to beat Great Britain, the demand was unrealistic so all of his lieutenants made up fictitious yield reports, and they spent all of their budget on farm tools and farm labor, and not enough on train cars to take the grain into town, and a ton of people starved to death as a result! I'm sure something similar to this happened at Huawei: "Boss, the call quality on this 6p is absolutely stupendous". "Well done vice president, here's your bonus". Sales of Huawei 1-2 years later: not up but way, way down. Layoffs. People hungry again...
Hi,
I just read somewhere that the OnePlus 5 reboots when calling 911. Can anybody confirm on OOS 4.5.5?
http://www.androidauthority.com/oneplus-5-reboot-911-788049/
Thanks!
Yeah read that too. Very odd. How the hell do you year that without a false call to 911? You can get in trouble calling 911 without an emergency.
This seems like pretty natural behavior
Damn this is something hard to test, as you can't call 911 and say, oh sorry, I was just checking to see if my phone is working.
Probably not true.
worldsoutro said:
This seems like pretty natural behavior
Click to expand...
Click to collapse
How is that natural?