Using the stock keyboards voice input option defaults to Samsung Voice Input instead of Google... no problem right? I just go in and turn off the Samsung voice input and voila! google becomes the voice input! See image
Then with out warning or notifying, by the end of the day it is turned on again and becomes the default voice input for the keyboard..
And, right now it SUCKS, not even close! see the 2 screenshots.
any how is anyone else noticing this?
dave
Same here. I was able to solve it by using Package Disabler Pro and disabling Samsung voice input. It stays off that way.
This is not new. It's been the case for a few years now. I could never disable voice input or the Samsung keyboard.
Related
Hi everyone,
I have noticed hitting the mic button does not do anything on swype, but on the regular multitouch keyboard i can dictate messages using the microphone.
Does anyone else having this? I did root my phone and deleted some bloatware apps but don;t think it can cause this.
Is it turned on? I turned mine off and it doesn't do anything when I press on the microphone button.
needs vlingo crap
Found other posts that the swype provided by motorola is hard coded to use vlingo.
DroidX w/CM9-20120809
Working great but...
I got no mic on the keyboard for voice input.
Is this a known issue or, as I suspect, am I a dumba$$ running the wrong kb or something?
Poking through the various settings I see I have only the Default Android Keyboard? Should I be using a different one?
Also found the option "Voice Input Key"; "on Main Keyboard" & "on Symbols keyboard" are there. Seems functional, lets me select either one but it never shows up.
I know I overlooked/missed something. Jumping out at anyone?
Voice recog is working fine from the Google search widget, btw.
ASMx4 said:
DroidX w/CM9-20120809
Working great but...
I got no mic on the keyboard for voice input.
Is this a known issue or, as I suspect, am I a dumba$$ running the wrong kb or something?
Poking through the various settings I see I have only the Default Android Keyboard? Should I be using a different one?
Also found the option "Voice Input Key"; "on Main Keyboard" & "on Symbols keyboard" are there. Seems functional, lets me select either one but it never shows up.
I know I overlooked/missed something. Jumping out at anyone?
Voice recog is working fine from the Google search widget, btw.
Click to expand...
Click to collapse
The voice input with SwiftKey seems to be working perfectly for me with the same setup. Love this rom!
I just received my phone today.I know that there is "Voice Search" and "Google Now" built in, but I cannot seem to launch them from the lock screen using a headset.
I have also tested the headset (3 button), and it does work; I can play and stop music both locked and unlocked screen and Google Now activates when I hold middle button unlocked, but nothing happens when the phone is on lock screen.
As far as I am concerned, "Google Now" & "Voice Search" are useless unless I can activate them while they are in my pocket, for driving and walking. Furthermore, when I ask it to send a message to someone, it simply displays the message, not repeating it to me, or asking me if I would like to send. I see lots of reviews, claiming "Google Now" is far superior to S-voice and Siri (iPhone) but in my opinion, they should not be categorized together, "Google Now" simply does not do the things I need it to do. If at any point, I need to look at the screen, or press something on the screen, the whole purpose of Voice activation is rendered useless. I cannot be the only one out there with this problem. I am open to any suggestions to solve this issue, or else I must go back to iPhone for the sake of the voice dialing that is headset activated, as well as the ability to read out my messages and send them.
I have tried 3rd party apps like Headset Button, with no luck and it still does not allow Google Now to run in the background with screen off, and requires another third party app, Screen Off & Lock to do just turn off the screen with a different combination of presses on the headset. The lack of any sort of physical button on the N4 is also another problem.
I am open to any suggestions or comments if I am simply just missing something from the features. Please excuse me if I sound rude or a hater, all I am trying to do is find out the problem to my issue, and potentially inform others if they have the same needs as me.
Cheers. :good:
So because it doesn't do the things YOU need it to do, they shouldn't be categorized together?
If you want to access Now with your headset then turn off the screen lock function.
AFAIK, I don't think Google Now will do the things you want it to do out of the box. If you're willing to use third-party apps, though, I think you may be able to get the behavior you need by using Tasker (https://play.google.com/store/apps/details?id=net.dinglisch.android.taskerm). A quick search also turned up this app (https://play.google.com/store/apps/details?id=com.sonalight&hl=en), which supposedly can read/send text messages by voice alone.
As far as physical buttons go, well .. that's something you're just going to have to get used to, sorry
tengen said:
AFAIK, I don't think Google Now will do the things you want it to do out of the box. If you're willing to use third-party apps, though, I think you may be able to get the behavior you need by using Tasker
Click to expand...
Click to collapse
How would Tasker accomplish this?
thanks for all the responses
is there itleast a way i can activate voice dialing from my headset button, i feel like that must be a feature for driving
i now have no lock screen, and when holding down the middle button of my headset, still get nothing
please help.
vicson88 said:
thanks for all the responses
is there itleast a way i can activate voice dialing from my headset button, i feel like that must be a feature for driving
i now have no lock screen, and when holding down the middle button of my headset, still get nothing
please help.
Click to expand...
Click to collapse
I have the same issue , headset button doesn't start voice while screen is off even if there is no screen lock ... Bit daft
Sent from my Nexus 4 using xda premium
Anyone getting WACKY voice to text translations using Moto X pure, with Swype &dragon
Interesting problem.
When I use swype and dragon, (my keyboard and voice to text engine) I am starting to get some wildly inaccurate translations of my speech where there were none before.
Around 50% error rate.
Strangely this only happens when I am in my text window (currently using chomp, with a dark night theme), and using the same apps in a gmail message, do not produce the same level of errors, but rather more in the range of 25% errors.
I looked at chomp, and saw no options for any language input, and there do not appear to be a bunch of language input options in swype&dragon either.
I am interested in improving the accuracy, in general. Any ideas on how to do that?
Is there a way to use swype without dragon and use the google default voice recognition instead?
Any ideas? Thanks!
PM
papamalo said:
Interesting problem.
When I use swype and dragon, (my keyboard and voice to text engine) I am starting to get some wildly inaccurate translations of my speech where there were none before.
Around 50% error rate.
Strangely this only happens when I am in my text window (currently using chomp, with a dark night theme), and using the same apps in a gmail message, do not produce the same level of errors, but rather more in the range of 25% errors.
I looked at chomp, and saw no options for any language input, and there do not appear to be a bunch of language input options in swype&dragon either.
I am interested in improving the accuracy, in general. Any ideas on how to do that?
Is there a way to use swype without dragon and use the google default voice recognition instead?
Any ideas? Thanks!
PM
Click to expand...
Click to collapse
I had this issue appear suddenly for a bit and tried everything to fix it. Nothing worked. I was scheduled to have a tech look at my phone and possibly replace the microphone. The issue turned out to be the ROM. I don't know if it was a bad flash or what but things are good now.
papamalo said:
Interesting problem.
When I use swype and dragon, (my keyboard and voice to text engine) I am starting to get some wildly inaccurate translations of my speech where there were none before.
Around 50% error rate.
Strangely this only happens when I am in my text window (currently using chomp, with a dark night theme), and using the same apps in a gmail message, do not produce the same level of errors, but rather more in the range of 25% errors.
I looked at chomp, and saw no options for any language input, and there do not appear to be a bunch of language input options in swype&dragon either.
I am interested in improving the accuracy, in general. Any ideas on how to do that?
Is there a way to use swype without dragon and use the google default voice recognition instead?
Any ideas? Thanks!
PM
Click to expand...
Click to collapse
There is no way to use Swype without Dragon. It's the worst thing ever because that keyboard is really great, but Dragon is friggen terrible. Nothing beats Google's voice integration. There used to be an xposed mod for Swype to use Google, but it's long outdated. Until they change that app to allow Google as an option or remove Dragon altogether I will keep my 1 star rating in the Playstore. Honestly though, the latest Google Keyboard is really hard to beat, it's really come a long way. The number row and themes really make it hard to use anything else - not to mention that it's prediction seems to be the best out of all of them now, including Swiftkey.
So I have found the keyboard to be somewhat fraustrating. Not because it is virtual, but because of the software behind it.
First of all, it is rather strange that you cannot set more than one keybaord. Essentially, the device can have two keyboards that you might regularly swap between: the hardware keyboard and the one screen keyboard one might use while in tablet mode. The hardware keyboard uses the autocorrect of the keyboard you have set as your software keyboard. You cannot set seperate keyboard engines for the hardware and software keyboard.
As I said, the autocorrect/engine behind the hardware keyboard is dependant on your choice of software keybaord. However, as far as I can tell, only the defualt TouchPal keyboard provides any autocorrect for the hardware keybaord. The stock android keyboard offers no autocorrect with the hardware keyboard.
On a related note, TouchPal is awful. The autocorrect works pretty badly and is basically very annoying to use. I won't bore you with the details, but things like autocorrecting to a new word when you go back to edit a mistake. This makes it almost unusable.
Also the touch pad is very bad. No two funger scrolling means that again, it is pretty much useless.
I think the Yoga Book is a great device in most respects. Its intersting that all of these problems relate to the software and could potentially be fixed by Lenovo or there may even be fixes out there now.
Has anyone found any solutions to these problems? Thanks, Liam
I completely agree with you and am having the same frustration with the software behind the keyboard. So far the best solution I have found is to use SwiftKey or Swiftkey Beta (not sure which is best yet). With a bit of tweaking you can get decent auto complete and auto correct using both the halo and on screen keyboard. Much better than Touchpal at least. A couple of issues I have found using Swiftkey and halo keyboard: 1) auto complete seems to turn off when resuming from sleep mode (tapping the keyboard button on the top row reactivates it) 2) in WhatsApp Tablet app, after pressing Enter to send a message, the next message gets double words - I. E. Auto correct adds to what you type, doesn't replace it.
I can confirm that switching to SwiftKey makes the hardware keyboard usable! I'm actually using the keyboard to type this now. Naturally, I'm making tons of mistakes but it is catching and correcting almost all of them!
Can confirm that SwiftKey easily switches between physical keyboard and on-screen keyboard when the physical keyboard is toggled on and off.
If anyone is still using the default software keyboard, switch now!!!
Thanks for the tip! This makes a big difference! Have either of you found a way to get auto capitalise to work? The setting is enabled but it doesn't do anythig.
My issue with SwiftKey is that there is no good ways to select a suggested word. You always have to click with your finger on the screen which completely ruins ten finger typing for my.
So I ended up with disabled word correction as it's faster to remove some mistyped words and type again, than to click on the screen.
How do you handle suggestions made by SwiftKey?
faeArai said:
My issue with SwiftKey is that there is no good ways to select a suggested word. You always have to click with your finger on the screen which completely ruins ten finger typing for my.
So I ended up with disabled word correction as it's faster to remove some mistyped words and type again, than to click on the screen.
How do you handle suggestions made by SwiftKey?
Click to expand...
Click to collapse
I have found that SwiftKey enters the main suggested word when I press space. This is good for most of the time, but annoying when:
-I want to select a suggestion that is not the main suggested word (particularly a new word that it doesn't recognise)
-I want to add punctuation directly after the main suggested word (here, because I input the punctuation rather than pressing space, the suggested word is not entered)
I have certainly found using SwiftKey to be the best experience. It's quite a passive autocorrect that doesn't get in the way too much. I got so sick of TouchPal which really gets in your face with its incorrect predictions.
But still there is a lot of room for improvement. It's such a shame that it's terrible software that lets down this keyboard. In particular I don't understand why:
- Some keyboards (like the Google Keyboard) don't offer any correction or prediction when enabled. Does Android maybe treat the Halo keyboard as an external keyboard (which I suppose you wouldn't want predictive features for)?
- Keyboards that do offer prediction don't seem to respond to changes to their settings (I can't get SwiftKey to auto capitalise the first letter of a sentence for example). @thespinner02 mentioned tweaking with SwiftKey settings- I assume they meant for the onscreen keyboard because these settings don't do anything for the Halo keybaord.
I wonder whether there is a keyboard out there in the Play Store that works better with the Yoga Book. I'll try a few and let you guys know if I find one.
I tried several solutions but couldn't find anything good. Hardware keyboards are not that common on Android platform, I guess.
Even using Swiftkey I sometimes get different results depending on the app being used. Auto capitalise is working OK for me, in Word for example.
There are specific options in Swiftkey for Physical Keyboard: in settings, Typing, Voice & Other Input. In Physical keyboard section I have Autocorrect and Auto capitalize on. Everything else off.
thespinner02 said:
Even using Swiftkey I sometimes get different results depending on the app being used. Auto capitalise is working OK for me, in Word for example.
There are specific options in Swiftkey for Physical Keyboard: in settings, Typing, Voice & Other Input. In Physical keyboard section I have Autocorrect and Auto capitalize on. Everything else off.
Click to expand...
Click to collapse
Thanks! I didn't notice that- smart spacing etc makes a massive difference!
Pretty much my only problem with SwiftKey now is that it sometimes creates its own weird textbook instead of typing directly into the text field. But that's not a massive problem.
Also I sometimes accidentally change input method. Maybe I'm using a keyboard shortcut by mistake?
thespinner02 said:
Even using Swiftkey I sometimes get different results depending on the app being used. Auto capitalise is working OK for me, in Word for example.
There are specific options in Swiftkey for Physical Keyboard: in settings, Typing, Voice & Other Input. In Physical keyboard section I have Autocorrect and Auto capitalize on. Everything else off.
Click to expand...
Click to collapse
In settings for hardware keyword I get no harder key found?
Went into Swift settings in onscreen. How to get settings for Halo?
With Yoga Book in laptop mode. Settings / Language & input / SwiftKey Keyboard / Typing / Voice & Other Input
You also need to make sure 'show input method' is not enabled in the keyboard settings/selector popup.
Does anyone else experience a problem with SwiftKey where in some text fields your text goes into a little popup text box at the bottom of the screen as well as the intended text field? And then to get rid of the popup text box you have to tap 'next'. This occurs in the Facebook messenger app for example.
Any way to disable it?
It seems to do this when the text field is small, but other keyboards just expend the text field as you type. The popup text box it creates doesn't expand anyway, so it doesn't offer extra functionality and is just an annoyance.