Related
I know that there was a little conversation in another thread somewhere about it, but I've searched and cannot remember where it was. I was just wondering again if there is any program that will be able to load a skin that takes up half of the screen, to make a bigger more iPhone like keyboard.
Although I don't actually have SPB full screen keyboard, it looks like it may be the sort of thing needed, but I am not sure if it only does full screen or not.
Any comments/help appreciated
Thanks,
James
Are you talking about the Happy Typing Keyboard? I use it for short typing but I still use SPB Full Keyboard for longer messages. Search it by name and you should find it.
Try this: http://forum.xda-developers.com/showthread.php?t=317962 , still in development, but when skinned and tweaked, it will be really cool.
I love the HTC keyboard and the phone, however one noticable problem on the phone is the lag on the KB, which is horrible because it is the most used component of a phone with a software KB.
Anyway, I took off autocorrection, and prediction and also On DC v2.05's rom their is a customized KB I took off the setting that highlights a key when it is selected. The KB is running much smoother.
The iPhone has the best onscreen KB and correction and the main reason is it is not cluttered.
What I am requesting is an app that enables auto correct and prediction, but hides the corrections. I know this will stop us from being able to push the space bar to complete a word, but it would also keep the screen less cluttered, I understand their still might be lag. But i Hate it that all the words you are typing show up, that causes lag.
For example if I were to type in "JTC" instead of "HTC" I want the keyboard to correct it but not show the correction on the screen, like the iPhone.
Is this possible?
in your case at the bottom, what if you MEANT to type JTC though? Would it still correct it to HTC? Because that would be extremely annoying
I would have to manually go back and fix it. but the autocrrection should stay the same meaning it will correct it in most cases it just doesbt show up.
i understand what ur saying how the kb gives you it suggestion of what you meant and then the next guessed word is what you actually typed. but i would be willing to give that up to hide the kb corrections.
tatonka_hero said:
in your case at the bottom, what if you MEANT to type JTC though? Would it still correct it to HTC? Because that would be extremely annoying
Click to expand...
Click to collapse
I'm not here to rain on your parade (although this forum isn't really the right place to be asking for Android application requests) but this is the thing that makes me lol every single time I'm texting with someone on an iphone. Their auto-correct is constantly picking wrong words and it's hard to figure out what they are even saying.
With that said the custom keyboard in damage control is the one made by some xda guys. Go put in the request. http://www.xda-developers.com/android/htc_ime-keyboard-v19/
flipzmode said:
I'm not here to rain on your parade (although this forum isn't really the right place to be asking for Android application requests) but this is the thing that makes me lol every single time I'm texting with someone on an iphone. Their auto-correct is constantly picking wrong words and it's hard to figure out what they are even saying.
With that said the custom keyboard in damage control is the one made by some xda guys. Go put in the request. http://www.xda-developers.com/android/htc_ime-keyboard-v19/
Click to expand...
Click to collapse
lol............
Ok so I posted some bit's of this already but I have refined the original "Proof of concept" design to something a bit more useable.
It annoyed me that I could not see the buttons in Landscape mode but I could see the sides of the screen when it is set to Autoscale. This set me to try and make a pad that would fit into the tiny slivers of screen left in landscape mode with "Autoscale" set.
This pad needs to be used in "AutoScale" mode on a WVGA screen such as an HD or HD2 This setting leaves a slither of screen each side of the screen that I have used to show the button placement. Don't get me wrong, you can't fit a Dpad in that area BUT you can easily mark top and bottom left of it and that's a start.
I find that my thumb is a bit lazy and I struggle a bit to use a square DPad, because of this I have squished it a bit to a more suitable rectangular shape, have a go and tell me if it's no good - If you imagine that the visible "strip" at the side is 1/4 of the DPads width then you should get it pretty easily. Please take a look at the attached picture though, I have made this pad a slightly odd shape because I find that I use left and right a cack load more than I use up and down. It may not be great for all games but I have found that it suits my thumb better than a standard equal layout. If you hate it then try using my original pad found here: http://forum.xda-developers.com/showthread.php?p=6339454#post6339454
Other than this the Start (ST) Select (SE), A, B, R1 and R2 buttons are all visible at the edge of the screen!
Currently the GBA pad is the only one I have done but I could easily modify this concept to cover all of the different systems - The only reason I haven't is that I only really play GBA games on my phone.
There is a readme included but I'd like some feedback so please bring it on!
Hey man, good job. I like the v1 rather than this, i find it harder to hit the up arrow with the new one, but it's not the reason why i'm wiriting this.
Both your pads makes the game laggy when i tap the white (unassigned) space. Other pads I've tried never did that. Any idea how to selve this? Or am i the only one experiencing this lag?
is multitouch available for morphgear?
Phenomenon said:
is multitouch available for morphgear?
Click to expand...
Click to collapse
It sure is you just need to download the tweaked version by blutz
xZdenis said:
Hey man, good job. I like the v1 rather than this, i find it harder to hit the up arrow with the new one, but it's not the reason why i'm wiriting this.
Both your pads makes the game laggy when i tap the white (unassigned) space. Other pads I've tried never did that. Any idea how to selve this? Or am i the only one experiencing this lag?
Click to expand...
Click to collapse
Hi I find that they all lag a bit, it seems to be the way that the Multitouch is implemented (I don't think it's Blutz, rather the original Morphgear crew), I find that when I have 2 buttons pressed all is fine but if I press NE and A (so 3 buttons reported to Morphgear) it lags until I release all buttons. This is just my laymans observation.
I could try producing an ultra light version to see if that helps... I think my skin is >2mb
Could you give me some examples of ones that don't cause it and I'll have a look, I wouldn't be overly surprised to find it was something I had done wrong. What we really need is the capacity to set white = NULL!
Note (nov 30, 2010): By now there are two versions: a lite version, published here (free) and a full version (paid) on the market. The full version will be continuously updated with new features, layouts, styles and more. The lite version will get no more updates.
(feb. 16, 2011) New thread for the full (paid-for) version created here: http://forum.xda-developers.com/showthread.php?t=948179 . Please post your requests, questions, comments etc in that thread. Thanks
------ initial announcement ----------
New thumb keyboard for easy thumb typing. The idea is simple. I've split the keyboard in two halfs, took them apart and placed them above each other (see screenshots). Result: much wider keys...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Somehow the brains does the remapping remarkably well. Left/right to up/down doesn't seem a problem. The result is that the keys can be defined with a greater width and that for thumb typing the phone can be hold in much more natural way.
Press-and-hold the keyboard icon for switching between layouts, settings and selecting another input method:
I'm very curious what other users think about this concept... Also I'm very interested in getting feedback on the usability of this concept.
Site
App blog: http://thumbkeyboard.blogspot.com/
Little FAQ
Q: I don't see the keyboard after installing it
A: The procedure of selecting the keyboard is described in the screen you see right after you have installed the keyboard. It's described in the section "Selecting the Keyboard". You can consult this info at any given time by tapping on the Thumb Keyboard app in your app drawer.
Basically the procedure is as follows: go to the Android keyboard settings menu by selecting "Settings" or "Preferences" in your app drawer and then "Keyboard ...". In this menu check "Thumb Keyboard". Now, when you want to edit something and your normal keyboard pops up, long tap in the edit field and select "Thumb Keyboard" from the "Input Method" menu.
Q: How can I switch to another layout or set up my preferences for the keyboard
A: Also described in the info screen under the header "Setting up the Keyboard". Anyway... long press on the keyboard icon in the left corner at the bottom of the keyboard to access the settings menu and to switch layouts.
Q: I can't download the file that is attached to this post.
If you try to download it from your Android phone keep in mind that not all browsers support downloading apk files directly. You can either try another browser, use a download helper or download it from your pc/mac
Q: Will this keyboard help me to find answers to some urgent existential questions?
A: No. But you can always read a good philosophy book and make notes with this keyboard.
Q: Huh?
A: kidding
Changelog
v1.5.1 * missing accented characters added * solved spacing issues in the accented character popup keyboards * added a numpad popup keyboard (press and hold [email protected]) * Some additions to the help/info screen"
v1.5 * New Style * International (accented) characters * Popup Smiley Keyboard * Option to mark keyboard blocks with different colors * Numbers on the compact keyboard * Checkerboard Vibrate Pattern * option to set vibration strength * etc (Compatible with Android 1.6 and higher)
(Users who already downloaded the 1.5 version are adviced to download the (new) attached version again)
v1.4.1: Small update: * added a extra, redundant "g" to the "asdf" row to address more typing habits. * made the keyboard suitable for all possible screen densities
v1.4: *finally adapted the landscape keyboards for thumbtyping (see screenshot) *added new portrait layouts with a squeezed q for better accessibility of the t (see screenshot) *changed the layout of the symbol/num keyboards
v1.3: Added help info + caught a bug or two
v1.2.1: = 1.2 + little bug fixed (and . added to the first symbol screen)
v1.2: Changed the behavior of the Shift-key: *Double tap on Shift key to turn on/off Caps Lock * auto capitalize after period (can be turned off in preferences)
v1.1:
New additional small layout
QWERZ keyboard layouts (Big and Small)
(1 Gesture added) Swipe back for backspace
Sound bug fixed
Remember: long press menu icon for options and settings
v 1.0 release
Distribution
I will not allow any distribution of this keyboard without a explicit permission by me.
Full Version
The full version (with text prediction, themes, tablet layouts, resizable height, sound selection, auto quick fix, etc. etc.) is available on the Android Market and on AndroidPIT (paypal)
Like the concept. It is almost like my left and right thumb knew which keyboard to use. Maybe you can try changing one of the space keys for special characters or hard press on letters for special characters. I like the idea although I have to trade it for screen real-estate. Not bad, indeed a lot of work need to be done but I'm definitly keeping my eyes on the this. Thank you.
I'm an idoit I just notice the special character key is next the "g".
Sent from my T-Mobile G2 using XDA App
niscrome said:
Like the concept. It is almost like my left and right thumb knew which keyboard to use. Maybe you can try changing one of the space keys for special characters or hard press on letters for special characters. I like the idea although I have to trade it for screen real-estate. Not bad, indeed a lot of work need to be done but I'm definitly keeping my eyes on the this. Thank you.
Click to expand...
Click to collapse
thanks for your feedback. I've changed the layout a bit (concept remains the same). After some testing and some feedback from others I decided to place the spacebar, backspace key etc on the default location.. The result is much better.
this new version looks better!
i will try it very soon but is very unlikely for it to replace swype or swiftkey.
still, as soon as i try it i can give you some more feedback (will be about portuguese writing, i'm afraid)
Im testing this keyboard right now.
I just found a few bugs.
1. When starting writing caps lock is on and doesnt go off after the first letter.
2. Every time i use backspace it erases two lettrrs instead of one.
3. It may be me but im missing so much more lettrrs.
i believe most of my writting is done with one hand.
edit:
i gave up writing in my nexus. its too hard for me
i'm sorry and i hope you dont get mad at me but i'm not very confident in this keyboard. at least i tried it. hope you understand. stil... good luck
Sent from my Nexus One using XDA App
nutweevil said:
Im testing this keyboard right now.
I just found a few bugs.
1. When starting writing caps lock is on and doesnt go off after the first letter.
2. Every time i use backspace it erases two lettrrs instead of one.
3. It may be me but im missing so much more lettrrs.
i believe most of my writting is done with one hand.
edit:
i gave up writing in my nexus. its too hard for me
i'm sorry and i hope you dont get mad at me but i'm not very confident in this keyboard. at least i tried it. hope you understand. stil... good luck
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Don't get me wrong. I write this stuff because I need it myself and I share it because, you know, maybe others can use it too. So how can I be mad... I myself like and use this keyboard very much.
As for the bugs you reported. Yes, I can reproduce them and fix them asap.
BTW what makes this keyboard hard to use for you, the bugs or the layout
What does it look like in landscape orientation?
Edit fixed backspace bug. Shift key functionality is under review and reconstruction.
my biggest problem with the keyboard is that i'm missing too many letters. its like i was trying to say. i dont know why but i believe i dont miss as many with other keyboards, or they correct me, i dont know :\
the keyboard layout seamed like a really good idea but first i noticed i'm not using that much the two hands to write in my everyday writing. neither swiftkey, neither swype need two hands so i guess that may be my second problem. i dont get extra speed for using two hands with either of these two keyboards i'm used to.
Also, i believe you're taking too much of useful space for the keyboard. 2/3 of the screen is too much i think. maybe a solution with less used space? Another thing: at first i did understand the idea: get bigger and better letters. but now you have reduced the size of them again and they are just in a different position than the regular keyboards. why dont you try a little bigger than atm? you can remove the arrows and redistribute the numbers in the left overs. i will try to make a draw of my idea.
the two small bugs i reported are less of it
why dont you try to implement Dvorak keyboard. That keyboard was designed to increase the speed writing and the letters position was carefully selected. Also, it already has many languages configuration already selected so it would be only needed to change this configuration for each language.
more about it: http://en.wikipedia.org/wiki/Dvorak_Simplified_Keyboard
vezquex said:
What does it look like in landscape orientation?
Click to expand...
Click to collapse
i would have to say... it looks bad in my opinion it needs some reorganization in this landscape orientation
nutweevil said:
my biggest problem with the keyboard is that i'm missing too many letters. its like i was trying to say. i dont know why but i believe i dont miss as many with other keyboards, or they correct me, i dont know :\
the keyboard layout seamed like a really good idea but first i noticed i'm not using that much the two hands to write in my everyday writing. neither swiftkey, neither swype need two hands so i guess that may be my second problem. i dont get extra speed for using two hands with either of these two keyboards i'm used to.
Also, i believe you're taking too much of useful space for the keyboard. 2/3 of the screen is too much i think. maybe a solution with less used space? Another thing: at first i did understand the idea: get bigger and better letters. but now you have reduced the size of them again and they are just in a different position than the regular keyboards. why dont you try a little bigger than atm? you can remove the arrows and redistribute the numbers in the left overs. i will try to make a draw of my idea.
the two small bugs i reported are less of it
why dont you try to implement Dvorak keyboard. That keyboard was designed to increase the speed writing and the letters position was carefully selected. Also, it already has many languages configuration already selected so it would be only needed to change this configuration for each language.
more about it: http://en.wikipedia.org/wiki/Dvorak_Simplified_Keyboard
Click to expand...
Click to collapse
You noticed that you don't thumb type, it that case I understand all of your points. I designed the keyboard for use with two hands. The keys are wider (maybe as wide as in portrait mode and the height is, I think enough. So yes there is a big difference: look at the first row (qwert) and the 4th (yuiop) and picture them as 1 row, then you see what I mean.
Nevertheless, thanks for your comments. I'll see if I can use it.
Dvorak is a great keyboard layout btw, but a solution to a different problem.
i understood in the process that in order to help you, or in order to try to help you i need to use both thumbs. i'm doing it now.
its indeed easy to see that your keyboard is wider than default by looking at the qwert-yuiop.
i still believe the arrows arent needed. we have a finger to select where we want the cursor or a trackball... so... its just space used in my opinion.
i also believe that the shift isnt at the best spot. why do you require shift at such a great position? It isnt used that much.
the "?" should be near the "enter key". maybe instead of the backspace? i would place backspace in the "3" area, in top the the "op". maybe a little bigger than the others?
isnt the "t" too fair away from the left thumb?
nutweevil said:
i understood in the process that in order to help you, or in order to try to help you i need to use both thumbs. i'm doing it now.
its indeed easy to see that your keyboard is wider than default by looking at the qwert-yuiop.
i still believe the arrows arent needed. we have a finger to select where we want the cursor or a trackball... so... its just space used in my opinion.
i also believe that the shift isnt at the best spot. why do you require shift at such a great position? It isnt used that much.
the "?" should be near the "enter key". maybe instead of the backspace? i would place backspace in the "3" area, in top the the "op". maybe a little bigger than the others?
isnt the "t" too fair away from the left thumb?
what do you think? any valid thoughts now?
Click to expand...
Click to collapse
Yep, very valid thoughts Like this feedback. I have to say that some of your points crossed my mind when designing the keyboard.
Some points I want to address:
First, I think the shift key and backspace key are on the wright position because one expect those keys there while typing. I did some tests with some fluent thumbtypers with a previous version in which I moved the backspace to another position and they all, without exception were a bit disoriented. I think the same will be the case with the shift key.
Concerning the postion keys: I don't think they are a waste of space, but I really like more feedback on this. To go to a exact position by touching the location is not that easy is my experience. (For example: misspelling the word imagene and then going back to the e is much easier by pressing 3 times the left key than to select that position with a finger)
Thanks for your feedback.
EDIT: your point about the "t" being too far from the edge is a very good point. But then again it's better than in the landscape scenario.
Pure genius ! I am surprised no one has thought of this before. Just a questions
Is there a way to turn off the clicking noises ? My phone is on silent and I don't see anything wrong in the Sounds menu but yet the noises are there
MeOverTrance said:
Is there a way to turn off the clicking noises ? My phone is on silent and I don't see anything wrong in the Sounds menu but yet the noises are there
Click to expand...
Click to collapse
(Press-and-hold the keyboard icon for settings and fast selecting another keyboard)
here you have the option to turn it off but actually the keys keep making the sound =P
@appelflap
have you noticed you have 5-4-3 letters in the top left and 5-5-4 letters in the right bottom? what if you removed one line and got that "shift-z-x-c" in the same line as "y-u-i-o-p"? to extra "help", you could change the color of the keys. This way it would be a suggestion of which thumb (left or right) to be used.
i keep my idea: the arrows arent that great =P by removing those you could try this, i believe.
I love the idea but I really don't understand the point of it in it's current configuration. The keys seem to be the exact same size to me except they've been moved around. I mean, the keyboard isn't THAT small to begin with so unless the new configuration makes them bigger the only thing that seems to be accomplish is making my hold my thumbs in staggered positions... I don't see the benefit in that. (Maybe because I'm on an evo with a larger screen and therefore with a larger keyboard to begin with?)
I'm not going to refund since I want to see where this goes but I don't think it'll be my every-day keyboard for now. Good job though!
nolageek said:
I love the idea but I really don't understand the point of it in it's current configuration.
Click to expand...
Click to collapse
So you like the concept but you don't like the way it is implemented in the current configuration. That is something you must elaborate on, because it looks you have a interesting, implicit (not tacit) intuition.
The keys seem to be the exact same size to me except they've been moved around. I mean, the keyboard isn't THAT small to begin with so unless the new configuration makes them bigger the only thing that seems to be accomplish is making my hold my thumbs in staggered positions... I don't see the benefit in that. (Maybe because I'm on an evo with a larger screen and therefore with a larger keyboard to begin with?)
Click to expand...
Click to collapse
The keys are much wider. Just take the "qwert" of the first row and the "yuiop" of the fourth and picture them together in one row. The reason you think they aren't that much bigger is maybe because in comparisson to regular keyboard the height is smaller. The result is square keys with a simular height and width.
(I had to reduce the height because of the fact that I had to introduce more rows)
With regular keyboards I concluded that much of my typing errors were caused by hitting adjacent keys on a same row. That's what this layout is supposed to prevent and in my opinion it does a good job in that. The reducing of the height has no influence on the amount of errors I make. (I always thought that the extra height on regular keyboards was mere a suggestive thing)
In the end, what I'm trying to accomplish (and this is the most ambitious part), is to make blind thumb typing possible. I think with this layout that must be possible, only thing I have to introduce for this is a way to give thumbs some feedback so they can return to a fixed, initial position from where they can start of.. (like with a normal keyboard with markers on the "j" and "f")
I'm not going to refund since I want to see where this goes but I don't think it'll be my every-day keyboard for now. Good job though!
Click to expand...
Click to collapse
I hope you didn't feel obliged to donate. But thanks, also for your feedback. And please let me know if you have any suggestions, request etc. I hope with the comments and "thumb on" experience of users I can make this keyboard better.
nutweevil said:
(Press-and-hold the keyboard icon for settings and fast selecting another keyboard)
here you have the option to turn it off but actually the keys keep making the sound =P
Click to expand...
Click to collapse
****, you're right! In theory it worked remarkably well Expect a little bug fix real soon.
@appelflap
have you noticed you have 5-4-3 letters in the top left and 5-5-4 letters in the right bottom? what if you removed one line and got that "shift-z-x-c" in the same line as "y-u-i-o-p"? to extra "help", you could change the color of the keys. This way it would be a suggestion of which thumb (left or right) to be used.
Click to expand...
Click to collapse
What a great idea!!! Really, brilliant. Thanks, I will definitely implement this idea.
i keep my idea: the arrows arent that great =P by removing those you could try this, i believe.
Click to expand...
Click to collapse
I guess that everyone has his own preference in this respect. My plan is to make the non-qwerty characters configurable. (But maybe I sacrifice those keys when moving the upper keyblock one row down)
MeOverTrance said:
Pure genius ! I am surprised no one has thought of this before. Just a questions
Is there a way to turn off the clicking noises ? My phone is on silent and I don't see anything wrong in the Sounds menu but yet the noises are there
Click to expand...
Click to collapse
tapping-and-holding the keyboard icon will bring you to a setting menu in which you can not turn off the sounds (Kidding, It's a bug, but there you should have the possibility to turn off the sound)
I would like to keep the stock keyboard because it offers many things such as easy access to handwriting recognition, clipboard etc. However I find the text prediction maddening.
It clearly does not comprehend basic English usage.
For instance, a common word like "in". If I attempt to type "in" it will default to the much longer and rarely used word "instance". I have to manually select "in" if that is what I want. This is just one example. It seems to always default to the longest possible word. This is counter intuitive. It should default to the shortest possible word and build from there.
It also hasn't a clue as to basic spelling or punctuation.
I'd like to use this keyboard but this is intolerable. Any ideas one how to make this work better? Please no suggestions of other keyboards. I am aware of those. I just wish to make this one work.
Thanks
Sent from my GT-N8013 using Tapatalk 2
I have to admit, this is a real pain in the behind! It can be rather temperamental with things. But, I have a feeling that the way it's made is that it actually adapts to your handwriting. Mine is terrible yet it seems to get it right quite a lot.
From what I'm able to gather, the predictive text for the touch input keyboards does not apply. But, if you go into your keyboard settings > Handwriting. You can see that there are a few options. If you haven't been into this bit at all I recommend you take a look at it. You can change things such as recognition time, pen thickness, colour and the recognition type.
This type of thing is just something you need to keep practising at. I do agree with you that the punctuation is rather awful, though. Trying to put an exclamation mark in and constantly getting "i." is a pain! But, as far as handwriting recognition goes, this is the best I've seen in a long time. It's one of those things where developing something like that is really complex and needs to be incredibly fine tuned.
My handwriting is so horrific it would take a quantum computer a week to decipher. I can barely read it and I wrote it.
I miss the old days where you could change your keyboard in app. Having to go to Settings to change it seems like an odd design choice to me. If it were the old way I would just use Thumb Keyboard most of the time then switch over on the fly when I needed stock features.
** Update: Yes there is a way to change the keyboard in app. Just click the little keyboard icon on the status bar next to the clock. Cool
Sent from my GT-N8013 using Tapatalk 2
I change my keyboard in app all the time.
mitchellvii said:
My handwriting is so horrific it would take a quantum computer a week to decipher. I can barely read it and I wrote it.
I miss the old days where you could change your keyboard in app. Having to go to Settings to change it seems like an odd design choice to me. If it were the old way I would just use Thumb Keyboard most of the time then switch over on the fly when I needed stock features.
Sent from my GT-N8013 using Tapatalk 2
Click to expand...
Click to collapse
There's an 'input method switcher' hot button next to the clock whenever you're typing... it looks like a little keyboard, but you actually press the icon as opposed to it being in notifications like it does on a phone...
Sent from my SCH-I535 using xda app-developers app
Lol shockingly I never noticed that. I suppose I was just used to the old way and wasn't looking for it.
Thanks
Sent from my GT-N8013 using Tapatalk 2
So, some of you actually use the predictive text on the stock keyboard? I tried it for a couple of days and found it intolerably bad -- more often than not, I found myself absolutely fighting with the predictive text to actually type what I wanted, and so gave up on it.
I miss having just the word suggestions as I type that I can select so I don't have to finish typing each word -- I don't really need predictive text, as I can actually type pretty fast on the Note 10.1, but the word suggestions would be nice to have without needing to use another keyboard.
I use 7notes with mazec for HWR and Swiftkey for text prediction. Very satisfied with both.
toenail_flicker said:
I use 7notes with mazec for HWR and Swiftkey for text prediction. Very satisfied with both.
Click to expand...
Click to collapse
Swiftkey has never typed anything but gibberish for me on any device I have tried it.
You mentioned that before. I find that so odd. It does a great job for me. I have a lot of friends who use it, too, and they get excellent results. I doubt SwiftKey would have the sales and ratings they have if everyone had that experience. Have you emailed them about it?
wingzero2085 said:
So, some of you actually use the predictive text on the stock keyboard?
Click to expand...
Click to collapse
It's not the greatest I've used but it's fine. It does seem to learn and gets better over time. In Mitch's example for "in" all you have to do is hit the space bar when "in" is highlighted in blue and it inserts it with a trailing space. Also, you can add words to the custom dictionary yourself which makes things a lot faster and more accurate.
wingzero2085 said:
So, some of you actually use the predictive text on the stock keyboard? I tried it for a couple of days and found it intolerably bad -- more often than not, I found myself absolutely fighting with the predictive text to actually type what I wanted, and so gave up on it.
I miss having just the word suggestions as I type that I can select so I don't have to finish typing each word -- I don't really need predictive text, as I can actually type pretty fast on the Note 10.1, but the word suggestions would be nice to have without needing to use another keyboard.
Click to expand...
Click to collapse
Exactly! I find it giving me nonsensical predictions and I get kinda mad at it (sounds silly I know) but if you have ever used like for say, an original Asus Tf, you will find the responsiveness of this keyboard a godsend.
But one thing, this keyboard is actively learning our typing habits right? I'm using it as I speak and it seems more tolerable and accurate to my intentions. It's only really bad when I type something slighty off.
the whole GALAXY to NOTE about...counting down from 10 to 1.
BarryH_GEG said:
It's not the greatest I've used but it's fine. It does seem to learn and gets better over time. In Mitch's example for "in" all you have to do is hit the space bar when "in" is highlighted in blue and it inserts it with a trailing space. Also, you can add words to the custom dictionary yourself which makes things a lot faster and more accurate.
Click to expand...
Click to collapse
My point is that it never highlights "in", it highlights "instance" by default. If I press the spacebar after typing the letters "in" it enters "instance". Very very odd default action to prefer the longer word. If I keep correcting "instance" to be "in" it finally seems to learn in that session. However, if I close the app and re-open it later it has forgotten and goes back to the old way.
Sadly, like so much Samsung software, it seems like they turned it in on the day it was due and not when it was done.
I love Samsung hardware. Like HTC, their software pretty much gets an incomplete.
mitchellvii said:
My point is that it never highlights "in", it highlights "instance" by default.
Click to expand...
Click to collapse
That's wierd. On mine, the box on the far left tracks what I'm typing in blue. In your example I'd see "in" in blue while a bunch of suggested words would appear to the right. If I hit space bar or tap "in" while it's highlighted it inserts (only) what I've typed. The space bar turns blue (on mine) to show it's set up to bypass prediction. It's black normally. Are your settings set up like mine?
I don't know get predictions on my stock board only on SwiftKey
Sent from my GT-N8013
Mine works like Barry's. Confess! What did You change?
BarryH_GEG said:
That's wierd. On mine, the box on the far left tracks what I'm typing in blue. In your example I'd see "in" in blue while a bunch of suggested words would appear to the right. If I hit space bar or tap "in" while it's highlighted it inserts (only) what I've typed. The space bar turns blue (on mine) to show it's set up to bypass prediction. It's black normally. Are your settings set up like mine?
Click to expand...
Click to collapse
Yeah I know, it is bizarre. That's why I said at the start that I don't exclude the idea I have done something wrong here.
For some reason when I type, it is defaulting to the SECOND word on the list instead of the first. I know, right? Weird.
Ok, I just returned all settings to stock and this is what I get.
If I type "the" I get:
the | then | They | they | Then | there
It is highlighting the second word, not the first. Freakin WEIRD.
mitchellvii said:
Yeah I know, it is bizarre. That's why I said at the start that I don't exclude the idea I have done something wrong here.
For some reason when I type, it is defaulting to the SECOND word on the list instead of the first. I know, right? Weird.
Click to expand...
Click to collapse
Do you have any other keyboards installed? Maybe there's a conflict.
BarryH_GEG said:
Do you have any other keyboards installed? Maybe there's a conflict.
Click to expand...
Click to collapse
Yeah I have Thumb Keyboard. That is my preferred keyboard anyway. I'll just go with that and switch over to the stock keyboard when I need to use any of the custom features.
We'll just file this one under weird and leave it at that.