Welcome to SwiftKey VIP Community

Welcome to SwiftKey VIP Community - this community is no longer a place to submit feedback and bug reports. That community has moved over to here.


This forum is now dedicated for a private community - if you got the invite to join this community, create your account and we'll be in touch. 


  • Content count

  • Joined

  • Last visited

  • Days Won


Subliminal5oh2 last won the day on February 14

Subliminal5oh2 had the most liked content!

Community Reputation

323 Excellent


About Subliminal5oh2

  • Rank
    SwiftKey VIP Mod Team
  • Birthday 12/10/1987

Profile Information

  • Gender
  • Location
    Louisville, KY
  • Interests
    Android, Windows, XDA, XBOX360, my wife, and communication! I love being able to have social platforms to discuss similar interests in life! It's truly a wonderful time to be living!


  • Model
    SM-N920P {Note 5} [6.0.1]
  • Country
    United States
  • primary_lang
  • secondary_lang

Recent Profile Visitors

1,377 profile views
  1. It's all about how you post, if posts start off with version numbers and specifications between beta and market it makes a huge difference for us as the moderators and SwiftKey teams. I haven't had an issue regarding posting through mobile, using Chrome browser it has been substantially easier regarding notifications due to Tapatalk instability via multiple forum sources. It's much more streamlined for new users to find, which is ultimately the goal, more interaction and involvement is always better via public forums. Change is constant, and by far and away rarely received well, but I will say give it a chance and you will be surprised at the speed and clarity of the new community! Sent from my SM-N920P using Tapatalk
  2. Anything is possible Tagdan. What SwiftKey is trying to achieve (and according to the numbers, doing a fantastic job as such) is a better UX than its competitors. This means less intrusive permissions and the ability to zoom in on the keyboard that may be useful for some, if not most, of the users. I'm not saying this won't change in the future, that I cannot speak on as I'm not a developer. However, a feature request is the best way to go regarding this functionality. http://support.swiftkey.com is where you can find the feature request section. Happy typing! Sent from my SM-N920P using Tapatalk
  3. New beta released today, fixed the issue for me, please update and try it now ☺️ Sent from my SM-N920P using Tapatalk
  4. As a moderator, I was originally upset about this as well. I will say, however, that the mobile version of the Support site is very user friendly, and wonderfully formatted for mobile screens, so now instead of a third party app, you can use your favorite mobile browser to view, comment, and discuss different things over on the new U2U support site!
  5. This happens with the new beta in certain landscape applications and has been reported. For curiosity sake, what device, Android version and beta are you running? Sent from my SM-N920P using Tapatalk
  6. This is program (app) specific. For example the code used to bold in the forums through Tapatalk is very different from the code to bold in say Reddit. You're best, and more realistic option would be to take advantage of SwiftKey shortcuts through the clipboard and put the coding per application there. I'm not saying its impossible for a keyboard to make this function happen, so feel free to fill out a feature request at http://support.swiftkey.com Sent from my SM-N920P using Tapatalk
  7. SwiftKey doesn't remember, or add words to the dictionary on first tap. You can see this with email addresses, normally I have to enter the email, push the leftmost suggestion, then backspace and repeat about 3-6 times depending on complexity before it will predict the email address upon entering 3-5 letters. If you're only tapping the prediction once, that is most definitely the problem. Sent from my SM-N920P using Tapatalk
  8. I'm curious as to why you think this? There are 5 of us incredibly active in these forums and often times if we don't have a positive note to say we simply document and listen. Community feedback is more important than input from the long-time users and moderators of these forums we like to see the discussions posted and see a few sides of the issue before we come in with our reasoning and or responses. While we may not respond to every thread the day it happens they are all read. The SwiftKey team is growing, not shrinking and has very little to do with the ownership transfer as Microsoft kept the team intact. This app is always changing and always moving. In my experience Gboard has been on the come up, however SwiftKey still excels and saves me time communicating as well as adding features necessary to continue a wonderful, worldwide UX. Languages are tough, which is why we take this feedback very seriously regarding language usage and ease of use. Support for these languages take time, and it's still, all things considered, a new feature. Try offering a constructive criticism, or something youd like to see changed, feature requests are best filled out through http://support.swiftkey.com and documented by the development staff there. Happy typing! Sent from my SM-N920P using Tapatalk Thank you for the wonderful feedback, as you may be aware language models always change and improve over time, I can say it will get better because SwiftKey development is taking all of this information in on over 30 languages globally, we appreciate feedback like this because it gives our development staff a starting point, bear with SwiftKey, and from continued responses like this they should be able to improve greatly. Cheers! Sent from my SM-N920P using Tapatalk
  9. I have not had a limitation on mine so far, regarding shortcuts. The shortcuts on the clipboard as far as I know also don't back up to the cloud so, upon a fresh install, and some updates it may clear the clips. Sent from my SM-N920P using Tapatalk
  10. Quick reply is a feature of Android itself and your messaging app, with a native keyboard or gboard, or even swype (most times, unless it crashes), the permissions are there to allow full functionality. As SwiftKey doesn't control features of its phone, SwiftKey is not what allows quick reply. The Android permissions are what causes the lack of functionality, the keyboard still works, but doesn't have all the features such as flow or secondary (long-press) keys.
  11. So for clarification I said "lag can be somewhat device dependent". While the language switch may not work for you, it has not been an issues for millions of other users who have reported great things about the way the switch works, especially via a couple different layouts regardless of language used. Often times, just because a post isn't responded to or answered to usually relates to nothing constructive to say, or it being under review. I'm not dismissing your issues, I was referring to you speaking about SwiftKey "falling in love with itself" while not listening to users, when it could not be more the opposite. I was concerned as to where you got that inclination considering how much users like myself, and Alpert and Prad spend here. We do not dismiss issues, we simply catagorize and distinguish between issues that SwiftKey can and cannot fix as the limitations of a third party keyboard to how it interacts with your device is very device specific. As I said, I have never had an issue with lag, aside from running multiple instances of the different keyboards SwiftKey has to offer via Beta or Market. Again, not a dismissal, just simply an observation. None of the users here are victims, we are simply users, and sometimes somethings outside of anyone's control happens, SwiftKey and the development staff do everything they can to ensure a smooth GUI and a wonderful UX. It's what we all shoot for, and we're listening to EVERYONE along the way. Also, small note here, I purchased the app as well as the majority of theme packs before everything in this app went free. Multiple times for no less than 10 accounts. I've been using this app for 5 years, and have had issues since then, never have I thought that there wasn't a time that SwiftKey wasn't addressing my issues in a timely manner when you take in the scope of the things they do.
  12. Because there is still a swipe to unlock option. Which means there are Android security features in place, which in turn disables some functionality. Sent from my SM-N920P using Tapatalk
  13. Most of the changes made have been the culmination of a large numbers of users via feature requests, I'm confused as to why you believe SwiftKey "falls in love with itself" when they have maintained the most highly used third party keyboards and the best prediction algorithm/AI available on Android interfaces. Most of the new features come from users feedback, as is the purpose of these forums. You can also change the layout for each individual language depending on your personal usage and then swipe the spacebar to switch between layouts/languages. Lag is also somewhat device dependent. I've never personally had an issue with lag unless I had been swapping between the Beta and Market version regularly. There is a SwiftKey rep who spends the vast majority of his free time and work time on these forums listening to users, he relies on his team to address concerns and simple issues while partaking in a large portion of discussions regarding a variety of topics. While your post will be read, I believe its slightly shortsighted to say that the company doesn't listen to its users. That's been the driving force behind improvement of SwiftKey for many years.
  14. More depends on the permissions requested/granted by the keyboard. SwiftKey tends to be much less intrusive than most other third party keyboards.
  15. As far as I'm aware, this is an Android security system functionality, it also disables secondary keys and some other functionality from the keyboard. Not 100% on this, I will do some checking and update when I find out for sure. UPDATE: This is an Android issue for sure, I'm currently in a discussion with Android users on XDA, most native keyboards are NATIVE, and thus have all the permissions they need to continue platform functionality on every screen, any third party keyboard (with the exception of Gboard) will lose any extra functionality, or simply revert to stock on lock screen in order to make it easier to input passwords. This is not a SwiftKey feature, or anything that SwiftKey developers can "fix". Happy typing everyone =) Sent from my SM-N920P using Tapatalk