Hello, since i unpgraded to the official lollipop SwiftKey just doesn't work as it should, it vibrates on some presses on others it does not, i feel like it lags a lot, i stoped using it and switched to google keyboard but i really miss the predictions of switkey(google keyboard ones are no even usabke) has any of you experienced the same problem? Or have a solution?
I have the same vibrate problem, and have had it for a long time, even when I had my '13 X. I never did find a fix. I emailed the developers several times and never heard back. I reinstall it every few months to see if it's working correctly but it never is. I've pretty much moved on to Google keyboard, too. The predictions probably aren't quite as good and I don't feel it learns as well as Swiftkey, but the vibration works every time and it has a couple other features I prefer.
Here's a fix. Disable vibration on the keyboard.
Wow, what a great suggestion.
This is happening with my moto x too. Unfortunately I had to turn off the vibrate option. It's better than using the google keyboard, I guess.
Related
I've used so many keyboards, and they all seem to have this problem:
When i first click on a blank text field and the keyboard pops up, the first key that I touch usually thinks that I clicked it twice. No matter how careful I am to touch it once it just lags and does it twice.
Nothing else is laggy at all. And it never does it except for when I first bring the keyboard up/the first letter I type. Even if I wait a few seconds after bringing up the keyboard.
I have used stock keyboard, smart keyboard, thumb keyboard, and probably a few others. I doubt it's a application problem...
Using CM9 Official nightly 3/27
Also happened on alpha 2 and unofficial nightlies
Does this happen to anyone else? It's really frustrating.
I sometimes have this issue as well. Only it can happen at anytime.
I am using cm9a2 with hackers keyboard.
Hello.
I have a strange problem with my Note. I noticed this a few weeks ago and thought it might just fix itself automatically. However, it hasn't.
The issue is when using YouTube or Play Store. When searching for something the keyboard will freeze but only when the word begins with "O".
So for example if I search for "Opera Mini" on Play Store the keyboard will lock up. Same happens if I search for "Call Of Duty" on YouTube, the keyboard will lock up when I go to type "Of".
I've restarted my phone and tried all the usual fixes but nothing has worked so far.
This problem didn't occur when I first bought the phone, it only came on a few weeks ago so I'm not sure what triggered it.
If anyone else has come across this issue or heard about I'd appreciate some feedback.
Thanks.
FYI - I am running stock Android 2.3.6 with the stock keyboard.
I'm not sure whether my trivial problem is similar to yours. But I have experienced, yet very infrequently, that my Swype keyboard wouldn't type the letter "w" when the word start with it. I was able to close the app and back again and the keyboard works fine.
Honestly, I don't know the reason behind your weird problem. But why don't you try using another keyboard?
I've tried other keyboards but I just prefer the stock one.
I'm currently using Swype keyboard until I can figure out my problem.
Has anyone seen this? All of a sudden can't get it to work on anything. Changed roms, worked for a bit and then this again. Thanks.
Never seen that before. Maybe try another keyboard. I use the Google keyboard and never have any problems.
Nope. Not that. This is lollipop. My last rom was RageOne. Different keyboards, everything and it works at first then starts doing this.
Just started doing this weird thing within the last few weeks. Maybe google voice typing updated something?
Basically as the title says, often when typing (I use swiftkey) the phone will incorrectly register a tap as a swipe from my last type. This often results in a word getting entered before I am ready (often the wrong word) and its just generally annoying. Never experienced this with my last phone on swiftkey so I would be surprised if it was a software issues with swiftkey.
Anyone seen this or know whats going on? Any fixes? Its really a minor annoyance, but still an annoyance I would like to get solved.
I've noticed this as well. I've been using the Google keyboard for months, but just downloaded SwiftKey because of that same issue. However, it looks like it's not the keyboard as it's happened with SwiftKey also.
Sometimes when trying to zoom in on a photo the pinch to zoom doesn't work. It's like the double touch isn't recognized. Wonder if they're related?
Sent from my Nexus 6 using XDA Free mobile app
Since the last Wear update (5.1.1) I noticed that the 'Ok Google" command is less responsive.
Sometimes I have to say it three times before it is recognized, I also stumbled on this thread: https://www.reddit.com/r/AndroidWear/comments/3784f5/anyone_else_notice_ok_google_less_responsive/ so it seems others are also experiencing this.
Before the 5.1.1 update it was almost always working the first time. Maybe they lowered the sensitivity cause of false positives. Does anybody else experience the same?
Would be nice to have an option to adjust the sensitivity.
For some reason the responsive time for my watch is completely random. Sometimes it works quick and other times its waiting and waiting and even at times it tells me its off line even though the phone is right next to me.
Ginxeng said:
For some reason the responsive time for my watch is completely random. Sometimes it works quick and other times its waiting and waiting and even at times it tells me its off line even though the phone is right next to me.
Click to expand...
Click to collapse
This also happens occasionally, but it's the initial "ok Google" that seems to be less responsive.
Same problem here, any idea? :/
The same here. The last update has pretty much ruined voice control for me
Even though I don't have a solution, it's good to know that more people are experiencing this.
Probably we have to wait till the next Android Wear update to fix this.