Anyone using Swiftkey on your Pixel?

I use it, and noticed that after I first installed it, but it doesn't do it now. I assumed that it learned how I space things and adjusted accordingly.
 
I use it, and noticed that after I first installed it, but it doesn't do it now. I assumed that it learned how I space things and adjusted accordingly.

Interesting. I wouldn't think it would need to learn how *I* use space characters as they are a basic part of writing style, no?

I mean, does it need to be taught that this < This is a"test " > is wrong?
 
Interesting. I wouldn't think it would need to learn how *I* use space characters as they are a basic part of writing style, no?

I mean, does it need to be taught that this < This is a"test " > is wrong?

Maybe, but not everyone who uses the keyboard is literate enough to know to use a space there. And I just don't think it's that big of a deal for me. If it was, I would switch to a different keyboard that met my needs better.
 
Yes, that happened to me.. The keyboard thinks you are closing the quote and attached it to the last word... I'm on the SwiftKey neural.. For some reason it is just better at a lot of things... This included.
 
I can't swype anymore. I have to text manually or I am correcting most of the words. I have never had that issue before this phone.
 
I can't swype anymore. I have to text manually or I am correcting most of the words. I have never had that issue before this phone.

True, swyping is not working well. But to be fair, I don't think it is the phone per se, but more likely that Swiftkey is not fully Android 7.1 compliant yet. Or, some other Swiftkey bug.
 
I can't swype anymore. I have to text manually or I am correcting most of the words. I have never had that issue before this phone.

Hmmm, swyping on SwiftKey works fine for me. It stopped once but a reboot fixed it
 
Hmmm, swyping on SwiftKey works fine for me. It stopped once but a reboot fixed it

I think Amb312 meant - and, certainly, it is what I meant - that swyping seems to generate far more incorrect word choices than it used to. I've used Swiftkey for a couple of years and don't recall ever having to do as much manual correcting of text as I have been doing lately. And, as noted at the start of this thread, it is totally messing up the space characters before and after punctuation marks.
 
I think Amb312 meant - and, certainly, it is what I meant - that swyping seems to generate far more incorrect word choices than it used to. I've used Swiftkey for a couple of years and don't recall ever having to do as much manual correcting of text as I have been doing lately. And, as noted at the start of this thread, it is totally messing up the space characters before and after punctuation marks.
Same for me.. I keep hitting the enter button instead of the back space and I'm wondering if it's because I'm used to the smaller chin on the n7 and my hand placement is off....
 
I had a ton of spacing and period issues with the last several updates on my LG G3 running marshmallow.

But since moving to the pixel it has vanished and is working perfectly.

There were literally thousands of complaints about SwiftKey and marshmallow issues.

I would assume it is a Swiftkey/android issue, not a SwiftKey/phone issue
 
Not really related, but I like using super Swiftkey for the themes, but can't login to my Google account so it can access my account. App would freeze Everytime it asks me to enter my email address. Not having that problem with official Swiftkey via play store. Currently using google keyboard and mistyping like crazy.
 
Same for me.. I keep hitting the enter button instead of the back space and I'm wondering if it's because I'm used to the smaller chin on the n7 and my hand placement is off....

Minimal spacing changes can throw you off big time... I'm used to Swype (the keyboard) and my Nexus 5's chin, when I grab a larger or smaller phone and/or one with Swiftkey instead I can't swipe worth a damn (slightly different kb layouts and spacing, vastly different if it's become second nature).

I only use SwiftKey to thumb type on my tablet...
 
Just as a SwiftKey PSA...

In the event you open a document that is more than a page or two in length, it's likely that the app will grind to a halt, then totally freeze. If your doc is longer than that, I'd give it a 0% chance of working.

I realize that most people only type a sentence or two in their message apps and never use their phones for anything more involved. But some of us do. If you are in that camp, don't be surprised if SK freezes and stops working.

The rub is the way SK was designed. It's been this way for years, it's been reported a million times and the SK devs have never addressed this problem. Too bad. The app has a wonderful prediction engine.
 
Just as a SwiftKey PSA...

In the event you open a document that is more than a page or two in length, it's likely that the app will grind to a halt, then totally freeze. If your doc is longer than that, I'd give it a 0% chance of working.

I realize that most people only type a sentence or two in their message apps and never use their phones for anything more involved. But some of us do. If you are in that camp, don't be surprised if SK freezes and stops working.

The rub is the way SK was designed. It's been this way for years, it's been reported a million times and the SK devs have never addressed this problem. Too bad. The app has a wonderful prediction engine.
Have never had this happen.. And Neural gives me less issues than the regular SwiftKey... I type long emails and documents more than rarely. Give me an example of how to reproduce this problem and I'll try.
 
K.
Open a Google Doc that's more than a page. If if works for you, try a longer one. It'll grind to a halt at some point.

The issue is that SK apparently has a RAM management issue. Larger files cripple the app.

In full disclosure, I haven't tried the latest version, as I've wasted so much time over the years working with SK, installing their newest versions (new Dev versions sometimes), having it crash, uninstalling and reporting back to them. Then having them do nothing about it. Go on their "help" forum. You'll find lots of reports of this issue - never resolved. That said, some do not (somehow) see this problem. If you are in that group, then life is good. If you do see this issue, don't be surprised.

In every case, and for everyone who weighed-in (IIRC) on this issue over the years, Google Keyboard works in all cases.
 
Minimal spacing changes can throw you off big time... I'm used to Swype (the keyboard) and my Nexus 5's chin, when I grab a larger or smaller phone and/or one with Swiftkey instead I can't swipe worth a damn (slightly different kb layouts and spacing, vastly different if it's become second nature).

I only use SwiftKey to thumb type on my tablet...

I don't disagree with this hypothesis; the Pixel XL is a bit smaller than the Nexus 6P that I used for the past 11 months, so the tighter keyboard layout may be an issue when swyping.

But, that doesn't change the fact that the implementation of space characters before and after punctuation marks is totally messed up. :)
 

Forum statistics

Threads
954,328
Messages
6,961,320
Members
3,162,993
Latest member
glucovyreviews