Having a hell of a hard time texting and walking. How can I use text to speech instead?
I have installed the HTC_IME keyboard from Jonasl here on XDA and it has a microphone button on the bottom row, second from left but I think my phone was already configured for speech. I haven't done anything to set it up.
I am the UK and I know we have been having this discussion amongst ourselves on another forum, one chap on Rogers in Canada doesn't have this nor did a lady from South Africa (not sure what carrier she was on tho).
On your Google quick search widget do you have a microphone? Cos that seems to indicate whether its preinstalled on your phone or not.
Maybe others will put me straight if there are settings you have to enable, cos maybe I did in my initial burst of fiddling when I got the phone I just dont remember and I can't see anything that I could toggle it on or off looking at it now.
Has anyone noticed that when you put a pound key (#, aka number symbol, octothorpe etc) in a contact's number, it doesn't work? I.e. the # dtmf tone is not sent when you call the number, while other tones are sent properly.
For example, I set my voicemail number to *86,,5555# (the 5555 part is just for illustration, and should be filled in with the voicemail pin)
Whenever my phone calls voicemail, it says "Sending Tones 5555" but it doesn't mention the #, and I can tell that the # tone is not sent, because the voicemail system waits a few seconds after the password is sent, which is exactly what it does when I dial it manually and neglect to press #. When I do press pound manually, the system continues immediately without a pause.
Has anyone else experienced this? Or has anyone else been able to sucessfully send the # key?
hi, i haven't had this happen personally, but would puting space between the password and the # give the sytem time to receive it.? don't know if it will but i never had this happen either.hope this helps. hp
I don't think you can add spaces, but I added a comma (which indicates a pause) after the pin. That didn't help. Thanks for the suggestion though.
##7764726(spc=000000) and *#*#4636#*#* are hidden menus so the # may be handled special.
I actually noticed this today when I was trying to get through a damn automated menu. It kept asking me to hit the # key after things but kept telling me "Invalid Entry". I literally used every other button, to include * during the call and everything else worked. This is no bueno!
What version of Android and what Rom(if any) are you running? I am on 2.3.4 w/Eclipse v1.1
Thanks, AtLemacks, It's nice to know someone else has experienced the same thing (misery loves company I guess).
I'm using the same android version and ROM that you are. But I'm pretty sure I had the problem even back when I was using using P3Droid's Rooted Gingerbread without any ROM. I don't remember if I tried it when I was on stock Froyo.
I didn't have this problem before, I call/go through that menu fairly often.
did anyone figure it out?
I am suffering the same problem. Did anyone ever figure out how to send pound sign #?
Try a alternate dialer like Dialer One or the like.
Edit try voicemail *86, the # key skips to the next msg on my Milestone x2 port.
Found a solution
Found a solution, not sure if everyone can use it. I am using Motorola Photon with Sprint. My solution is to create a contact like this for google voice dial out
15125553010,,2,3235551110,#,,,1234,0118521234567,#
and it works for me. I can now use a direct dial icon on my home screen to call. The trick is the first pound sign. It needs comma before the pound sign and the three comma behind it.
Anybody else find a work around?
I am glad to hear that I am not alone, but a little dismayed to not see any answers to my days of searching for a solution. Has anyone else come up with an alternative work around? The direct dial method above didn't work for me.
Using a Galaxy S i9000 rooted with paranoid android 2.52 (although I did have this same problem with other mods as well)
Thanks!
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.
Hello all,
I have googled and googled and searched, and I can't find anyone with the same issue I have. I don't know if I'm using the wrong search terms or what.
I cannot seem to get a default dialer setting for ALL phone numbers.
- I have Dialer One installed because I like it better than the default.
- It installed no problem, though even when I was in the app, it would still switch to the default to make the actual call, I think. But that didn't bother me too much... at least I could use it to find the number I wanted.
- Then I installed Skype.
Now, every time I call a phone number that I have not called recently, the thing pops up AGAIN asking me if I want to dial it with "Phone" or "Skype." (Dialer One is never an option.) I can tell it to use the Phone always... but it will only set it for that phone number. I'm constantly calling new phone numbers, and I'm sick of having to continually tell it to always use the phone!
Soooo.... can anyone tell me how to do at least one of these:
- Either make Dialer One the default for all calls and phone numbers.
- Or make the default phone dialer the default for all calls and phone numbers... I can still open Dialer One to locate the number I want.
- Or somehow tell it to stop offering Skype to me. Ever. I'll open the Skype app when I want to call that way.
Note:
- In my Settings | Applications, there is no default dialer listed at all. Dialer One is the only thing listed. I may have tried to uninstall it back when I installed dialer one... which may be why I'm having issues. Maybe?
- Skype settings has absolutely nothing in settings to "Never offer" or anything of the sort.
- Every solution I've found says to clear the defaults, make a call, and choose always. Like I said... I do that dozens of times every week and it still keeps popping up.
***I do have the phone rooted, in case the solution requires that.***
Thanks in advance!
You can not replace the phone dialer..that will always be use whenever you are dialing some one. However installing a custom dialer will only give you a front end of the dialer but it will still use the default dialer software to dial some one.
Now try dialing any number thru SGS3 default dialer. It will ask you to dial thru phone or Skype. Choose phone and always.
Prior to the latest update to Google Search 3.5.16.1262550 a couple weeks ago, I used to be able to do a long press on my BT headset to bring up Google Now, which let me say, "Call Joe Blow home" and it would make the call to his home number. Now it brings up Google Dial which tells me to say "Call someone" but pops up with a numbered list of the cell, home, and work numbers on the screen that I either have to touch to choose the one I want, or say, "Select Two" to dial his home number. This requires that I either touch or look at the screen to make a call, which totally defeats the purpose of "hands-free" calling.
I have switched back to S-Voice for now, which I hate because she talks too much before I can actually make a call, but at least I don't have to dig my phone out to push or see which phone I want to call. I hope someone can help us get back to BT dialing the way it used to be.
This is on a Sprint Galaxy Note 3 running KitKat, but I imagine this is affecting all phones.
Yes I have a note 3 kitkat and Google search issue is affecting my phone as well. Instead of Google now voice prompt when pressing headset hard button on my LG bluetooth headset....Goople dial is not default which sucks!
Bump! Surely someone must use Bluetooth dialing from a headset and noticed this major change besides the two of us. Please help if you have any ideas to revert Google Search to work the way it used to.
Bump again! Doesn't anyone else use their Bluetooth headset to initiate calls?
I think I have finally found an acceptable workaround using Bluetooth Launch from the Play Store. Install the app and follow the directions as described in this thread: http://forum.xda-developers.com/showthread.php?t=2794883
Step one shouldn't be needed as when you long press, it will detect the new app and let you select Bluetooth Launch as the default.