I have a rather specific issue with the keyboard dock that is a bit of an annoyance. Here's how the issue comes up:
1. With the keyboard dock attached, open the YouTube app and watch a video.
2. In the search box of the video screen, type anything that has a space in it (example: "Asus Transformer")
3. The "Asus" bit shows up in the search box, but when I hit the space key, the first "Related video" is highlighted and I am unable to type any further.
The only solution I have so far is to toggle the "Use physical keyboard" option to "Off" and type using the on-screen keyboard.
Am I the only one with this issue?
Lani Kai said:
I have a rather specific issue with the keyboard dock that is a bit of an annoyance. Here's how the issue comes up:
1. With the keyboard dock attached, open the YouTube app and watch a video.
2. In the search box of the video screen, type anything that has a space in it (example: "Asus Transformer")
3. The "Asus" bit shows up in the search box, but when I hit the space key, the first "Related video" is highlighted and I am unable to type any further.
The only solution I have so far is to toggle the "Use physical keyboard" option to "Off" and type using the on-screen keyboard.
Am I the only one with this issue?
Click to expand...
Click to collapse
I had experienced this as well. My solution used to toggle On/Off of the physical keyboard. But I had come to realize that this can be easily rectified. You just need to go back to the very 1st page to type in your search. Seems that the keyboard issue only surface when u have gone through multiple search pages (3 or more). Try my solution & let us know the outcome.
Thanks for reading.
OnceHeaven said:
I had experienced this as well. My solution used to toggle On/Off of the physical keyboard. But I had come to realize that this can be easily rectified. You just need to go back to the very 1st page to type in your search. Seems that the keyboard issue only surface when u have gone through multiple search pages (3 or more). Try my solution & let us know the outcome.
Thanks for reading.
Click to expand...
Click to collapse
Yeah, that's always worked for me as well, but it's just annoying to go all the way back sometimes.
Related
I've disabled all of the auto-correct and suggestion SIP options on the TP and that works great, HOWEVER (heh, heh)...
Is there any way to turn off that annoying "what-you're-typing-preview" that always appears on-screen as you type? It is such a waste of screen real estate.
Do you know what I mean? I'll explain...
For example:
Code:
PREVIEW STYLE 1
1. Start a new text message.
2. Pop out your physical keyboard
3. Start typing!
You will see what you type appear in a little "preview window" at the bottom of your screen.
Now here's the REALLY annoying one...
Code:
PREVIEW STYLE 2
1. Open an existing SMS message (threaded view)
2. Pop out your physical keyboard
3. Start typing...
You will see the preview appear *above* your text this time. Even MORE annoying since it's taking up real estate in the typing area this time around.
I've been scrounging for a solution to this and really hope one exists.
Thanks for everything, guys!
press ctrl + space and choose abc
Thank-you VERY MUCH, Brendo!
I thought that I had already done this but I realize now that it was probably in my dreams.
(YES -- I dream about my TP -- don't lie -- YOU DO, TOO!!!).
Lol.
Take care.
Hi Guys, probably very silly of me, but 'choose abc'. Do we have a 'abc' button? I can't seem to find out what you mean with this. Also pressing cntrl + space and typing abc does nothing (obviously). Help me. I also find the typing preview window quite annoying, especially since I have been so happy to be able to turn the auto correct options off.
It can be found on the SIP - pop up keyboard, providing you have "full keyboard", phone keyboard etc selected and not the windows default keyboard. You will see a button marked ABC->T9. Make sure T9 is not selected.
Gee thnx ardsar, this was clear and worked. Indeed I had to change the layout of my pop up keyboard, as I hardly ever use it and had it in the default keyboard mode.
THANK YOU, THANK YOU, THANK YOU (yes, I'm shouting )
If there was anything that pissed me off on this phone, it was the goddamn useless preview!
Why do they expect that you're a retard, if you bought HTC phone? I thought these phones were for smart people
That's kool that it will take the dialog away but while I'm in programs it still types the letters in the background and causes them to skip. Is there any way to disable the typing of keys in the background while still reading the keystrokes. Let's say I'm using PocketNES while I'm in the game it reads the hardware keyboard as typing letters when I'm not trying to type any message. I would just like to use the letters as buttons instead. Hopefully someone has found a solution to the problem!
I posted this in the other Auto Correct thread (found here). That thread got so long that it was requested that I start a new thread with this info so it is easier to find this fix and how to do it.
I have a FUZE and mainly ONLY use the actual physical keyboard and not the onscreen keyboard. The fact you can not set up normal Auto Word Correction words was driving me crazy. So through a lot of people a fix was found. Credit goes to a lot of people who suggested different things (like Bugsykoosh), and then I put a few different programs/tweaks together and it works very well.
Here is how you do it.
1) Disabled T9 completely by installing the cab found at http://forum.xda-developers.com/showpost.php?p=2914474&postcount=8 . After installing the T9 button will no longer work.
2) Change your onscreen keyboard to "keyboard" as the default. You will no longer be able to use the QWERTY keyboard, but that was fine for me since I mainly use the actual keyboard. For this to work you MUST switch your on screen default keyboard to "keyboard" or install the Happy Tapping keyboard.
3) Install DictMgr for Windows Mobile that can be found at http://mobile-sg.com/software/?p=DictMgr&platform=ppc . It is FREE. This program is the key to making this work.
4) Only parts of DictMgr works with our version of Windows Mobile. After installing open up the program and launch the Word Corrector part of the program. It looks exactly like the traditional word replacement entry screen you see on your PC. SEE ATTACHED PICTURE.
5) Add the words you want to auto correct and hit save. It requires a soft reboot.
10) After the reset try to type something using the actual keyboard and you will see the word correct work the way it is supposed to.
I am VERY positive right now about this working so far.
Some other Feedback/Notes:
1) I use MyMobiler so when connected to my PC I can view my phone screen on my desktop. This makes entering all the auto correct words I want MUCH easier since I can use my normal keyboard.
2) I entered as MANY as I could at one time because a soft reset is required each time you save the file.
3) I have started entering all the basic ones like
i --> I
monday --> Monday
mon --> Monday
tuesday --> Tuesday
tues ---> Tuesday
(and all the rest of the days)
jan --> January
feb --> February
(and all the rest of the months)
4) on the onscreen keyboard I did go to the Touch Input Setting and check all options. See attached image.
5) I also went to the Options-->Word Completion Tab and checked "Enable Auto Correct. See attached image.
Everyone, this SEEMS to be a real EASY fix for this issue I am happy to report.
There is a solution to still use the Full QWERTY Keyboard. The complete text is located here: http://www.fuzemobility.com/?p=1527
After disabling T9 you must toggle the T9-ABC button back on. To do it press the button then hit the ABC123 button and keep going until it stick. If that fails go into landscape mode and try toggling. Once you get it to change it will stay that way. The one downside is it only works for odd numbers so it works on the first, third and fifth letter you enter and on the second letter no autocompletion appears on screen. The autocorrection (ex spell check) still occurs either way that.
Thanks TVDinner -that was fun
sweet! This issue now has 2 solutions. I love when a plan comes together!!!
So with this fix can I still use the physical keyboard/Full QWERTY soft keyboard/Phone Keypad like normal?
NeroDan said:
So with this fix can I still use the physical keyboard/Full QWERTY soft keyboard/Phone Keypad like normal?
Click to expand...
Click to collapse
Hi NeroDan;
With bugsykoosh's fix you can still use the on screen Qwerty keyboard.
With my fix you have to choose the onscreen "keyboard" option, or install the happy tapping onscreen keyboard. You can not use the qwerty keyboard with the fix I described.
If you do not use the onscreen keyboard then either fix will work fine.
Hi everyone
I first dismissed this error as another manifestation of the N1's touch screen drawbacks; but since I owned the Nexus S, the same error reappears, and it’s driving me nuts:
All signs point to the fault being caused by the Gingerbread keyboard. This is how you reproduce it:
1) Use more than one keyboard layout / input language
2) Type anything, switch to the first symbols keyboard
3) Hit any key from the symbols keyboard, and afterwards, directly the space bar
4) The keyboard switches back to letter mode, all good up to now
5) Hit the symbols button again
6) The input language automagically changes to the adjacent one, the keyboard switches back to ABC mode
Suffice to say, this is quite an annoyance. There’s a workaround, though: this doesn’t happen if you hit the ABC key before hitting space, but that’s not how I expect my keyboard to work.
Is anyone else able to reproduce this issue, and if yes, does anyone know how to fix this? Unfortunately, extensive research throughout last week didn’t bring back any usable results.
Thanks for your help!
thenoo said:
Is anyone else able to reproduce this issue, and if yes, does anyone know how to fix this? Unfortunately, extensive research throughout last week didn’t bring back any usable results.
Thanks for your help!
Click to expand...
Click to collapse
Hey!
this happens also on my Nexus S...really disappointing (
I played around in the Keyboard settings but couldn't find a way to fix this (unless you remove multiple languages....but that's not the point :S).
I've found two more keyboard issues, and I'd like someone else to try to replicate them see if they have the same issue.
1) In the Youtube app: when you click the search button (magnifying glass keyboard button) you can type in your search with no problem, but if you touch the screen in the search field, the space bar will not work while typing in a search query.
2) In Google Maps the magnifying glass keyboard button will not bring up the search prompt. You can touch the search field and enter a query with the keyboard with no issues, but the keyboard button will not activate the search field.
Does anyone else have these issues? I have installed all OTA updates, including the one for the keyboard.
1) can't replicate this fault on mine. If I touch the search area, the space bar still works
2) yes, I have the same issue
czm said:
1) can't replicate this fault on mine. If I touch the search area, the space bar still works
Click to expand...
Click to collapse
try playing a random video, then searching from that video's page
kingwp1 said:
try playing a random video, then searching from that video's page
Click to expand...
Click to collapse
yes - I see the same behaviour. Pressing the space bar seems to scroll the videos on the right (much in the same way that it scrolls the forum page down in the browser).
Other quirks
Some things I find annoying:
Ctrl+arrow key doesn't move to next word
Ctrl+Shift+arrow key doesn't select text
Ctrl+End(or Home)+arrow key doesn't go to end or beginning of document.
Are there more keyboard combinations we are used to that doesn't work?
First, just want to say thanks for the development on the Note Pro. CM on this thing is awesome. That said, I still have a couple of lingering issues, hoping someone may have found some work arounds/solutions. Inevitably there will be someone that will reply with "USE THE SEARCH!". For those that do, I will offer you my sincere admiration. Your search foo is only exceeded by your wit. For those that are still willing to read on and assist, know that I've come up empty in my search attempts. Believe me, I'd rather have found a simple search result than to have typed all this up... In any case:
1. Hardware keys and navbar -
CM has a setting for "Enable on-screen navigation bar and disable hardware buttons". Checking this box enables the navbar, but fails to actually disable the capacitive and physical buttons. This causes me some grief when using the tablet in portrait mode. I've tried hacking around in the build.prop and the Generic.kl files, but haven't found that magical combination of new lines/commented out lines. Maybe CM does this differently than other roms? (I've not observed a difference in these files when toggling back and forth in the settings, so there must be something else I'm missing.) Any pointers?
2. Key Mapping -
I have the Logitech Pro Keyboard Case. Seems to work well, for the most part. (I'm typing on it now...) However, not all of the keys work. Example - there are keys on the top left row for "back", "menu" and "task switching". Nothing appears to happen when pressing these now. Again, probably something in a .kl file somewhere, but I'm coming up empty. There doesn't appear to be a Vendor-Specific.kl file, but Generic.kl doesn't seem to cut it either.
3. On-Screen keyboard still displays when using bluetooth keyboard.
Well, that about says it all really. I've tried using both the Google keybard, and SwiftKey. Both continue to show up on-screen, even though I'm typing on the bluetooth keyboard. Swiftkey even tells me that it cannot detect a physcial keyboard. Probably related to the key mapping issue from above, but...
Again, thanks for all the work on this. Having CM saved my tablet from it's date with eBay.
Thanks!
- Bri
1. i thought about it but now i haven't spare time to implement. next week maybe.. but i dont promise
2. and 3. try this programm https://play.google.com/store/apps/details?id=com.apedroid.hwkeyboardhelper
171
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
bribash said:
Thanks! I'll give the app a shot. I'm concerned that it seems to replace any other keyboard though. I'd like to find a way to keep SwiftKey's corrections/prediction functionality. Nevertheless, I'll give it a go.
- Bri
Click to expand...
Click to collapse
Hey, try going with Null Keyboard, enable all your keyboards, and switch between them depending on whether the device is connected or not