Hey, everyone. I recently obtained a Palm 3245WW bluetooth keyboard. The device works great, pairing is really easy and once connected it works fine without any glitches. The keyboard is really easy to use, and hiding the on-screen keyboard is easy in order to have more workspace. After a couple of day's use, I am satisfied with the build quality, it really feels like a real keyboard and it is quite responsive. Even some (not all) of the keyboard shortcuts work!
My question is if anyone who has used the keyboards knows how of a key combination to enter the alternative inputs (such as accents, etc). I could use them when writing Greek, where the vowels can be accented. Otherwise, is there some way to alter the key mapping in order to define how the system reads certain key combinations? I have tried several combinations, such as alt+key or control+key or Fn+key, but to no avail.
Any directions would be appreciated!
Thanks!
Sav
P.S. Apologies if this the wrong place to post this!
Why did U open a new thread. There is already an existing thread. Now this is when I don't read and jump on to post your cap.
However, I don't have any experience with this keyboard so I cannot help on this.
Sent from my GT-I9100 using XDA Premium App
I searched around and did not find any threads on this particular keyboard on SGS2. I found a few threads regarding other phones (mostly unsuccessful attempts with this particular keyboard), so I thought I'd ask if anyone has used it with this particular phone.
Again, sorry if this is the wrong place to post, I am new here.
Thats ok matey, just do a comprehensive search next time.
Related
There is a lot of speculation and conflicting reports of how voice-to-text was implemented on the Desire. After reading every thread related to v2t, Im still totally confused
If you already have a handset, could you please tell us what the real story is with voice-to-text? No speculation, rumours etc please! If you are lucky enough to already have one, please help by answering these 2 questions?
1) Is voice-to-text available as a 'general' text input (in place of the on-screen keyboard)? I know there is a thread on how to enable it using an alternative keyboard but that's not what Im asking.
2) Is it available on all versions (unlocked, T-Mobile, Orange??)
To assist with getting a definitive answer to the second question, please include the carrier/store you bought your handset from.
Thanks in advance for your help!!
initially i thought this thread was about how good voice to text was, but then read your post. So i'll comment on both.
I got my desire direct from t mobile, and voice to text was not a function i could find. It wasn't until i downloaded the keyboard app referenced in other posts, and then switched to android keyboard instead of the stock htc keyboard, that i could find and use speech to text. I presume that the speech to text button was always present on the android keyboard and the extra keyboard app only activated the function which wasn't working before. However, as i only found out how to activate the android keyboard after i downloaded the extra keyboard app, I can't be too sure.
I can only issume that it would be the same for the generic ROM and other network ROM users. But from hearing about the people who have received the OTA update it seems that speech to text function may be changing or being disabled. I definitely hope not, though.
I used speech to text for half of this message. It seems to be working really well for me, despite what a lot of other people are saying. It's definitely not perfect, but i can see it as a function i will use often. I look forward to it getting better, and hope it will stay on the desire.
Hello! Firstly I would like to say thanks for this wonderful forum, I have learned loads in the short time I've been here and I feel that life with my Touch Pro 2 would be a lot more difficult if it weren't for this site.
There is one thing though that's been bugging me very much. You see, I'm Latvian and I need to use special characters when writing. Unfortunately these characters aren't anywhere on the symbol list and I was wondering whether it is possible to somehow add them and if it is, how to achieve such a feat.
I did a bit of searching before creating this thread and I only found a solution for the Touch Pro 1 involving editing a sym.0409.txt file which didn't work for me.
I'm torn between the overall aesthetic of the Gingerbread keyboard and the usefulness of HTC's autocorrect. I've used both extensively, and while the GBread keyboard is average with autocorrect, HTC's somehow turns even the most drunken gibberish into exactly the word I was looking for. Half the time I have problems trying to find something it CAN'T fix.
Is there a way to somehow sideload HTC's autocorrect genius into the stock's library? Alternatively, I guess, I could theme HTC's to look just like GBread but I like too many things about the usefulness of the GBread keyboard's layout. Really, I just want it to be as good/sensory as the one that came with the phone. Is the keyboard's prediction/correction stored in a .lib file that I can mesh with stock's or something?
sobis1dm said:
I'm torn between the overall aesthetic of the Gingerbread keyboard and the usefulness of HTC's autocorrect. I've used both extensively, and while the GBread keyboard is average with autocorrect, HTC's somehow turns even the most drunken gibberish into exactly the word I was looking for. Half the time I have problems trying to find something it CAN'T fix.
Is there a way to somehow sideload HTC's autocorrect genius into the stock's library? Alternatively, I guess, I could theme HTC's to look just like GBread but I like too many things about the usefulness of the GBread keyboard's layout. Really, I just want it to be as good/sensory as the one that came with the phone. Is the keyboard's prediction/correction stored in a .lib file that I can mesh with stock's or something?
Click to expand...
Click to collapse
+1 I'd love to know this too. Plus, getting the "user dictionary" to work on a GB keyboard.
I think you can make a user dictionary just by double tapping the word up in the autocorrect suggestions that the GB keyboard DOES have. It'll just say "tap again to save."
sobis1dm said:
I think you can make a user dictionary just by double tapping the word up in the autocorrect suggestions that the GB keyboard DOES have. It'll just say "tap again to save."
Click to expand...
Click to collapse
It does, but very occasionally I'll do it too fast (type a word, double tap) and realize that it's spelled wrong. Then, I can't go back in and change the word. That and every time I flash a Rom, I gotta slowly input all my spellings back in (I'm a hockey fan, so there's a lot of Bryzgalov, Kostitsyn, Kovalchuk, Ovechkin, etc). I tried backing it up on Titanium, but restoring it never does anything.
Oh well. I hope you get an answer to your question though (kinda using our conversation as an excuse to bump for ya lol).
But go to Koni's Elite Series III and check out the keyboard his rom uses. it's kind of like GB but still has a superior auto spell. Could be the best of both worlds if this idea doesn't work.
Is it possible to remove the special accented characters from the stock (4.3) keyboard? I didn't have this issue before flashing 4.3, but now almost every time I try to do a long-press when swyping I end up with a special accented character instead of the , or ( or : or @, etc. I thought that if I removed the language (like Spanish) they would likely go away, but I can't even find a way to even do that through settings. I am rooted and really not afraid to delete stuff via a file manager if someone can point me to the right files.
I'd love to know how to do this too. The special characters are killing me. I don't mind the characters like ! and @, but I hate the others because, like you, I keep accidentally switching to them.
Thanks for the confirmation of sanity. I was thinking I was the only one. Never did figure out how to do it but it's still bugging the crap out of me.
Me three! Anyone know how to do this?
internetpilot said:
Thanks for the confirmation of sanity. I was thinking I was the only one. Never did figure out how to do it but it's still bugging the crap out of me.
Click to expand...
Click to collapse
You try this http://forum.xda-developers.com/showthread.php?t=2471321 I havent but did a little searching..
Sent from my SCH-I605 using xda app-developers app
Never thought to search for the reverse (adding languages) as a solution, but it might just work. I'm on vacation and don't want to hose my phone, but I'll try it when I get home this weekend.
Delved into the suggested solution above pretty deep, but couldn't get those characters to go away even after removing what I believe was Spanish languages/characters from that configuration file. I rebooted with each change, but still no go. I suspect the problem is that we're not actually using the stock Samsung keyboard config, but are using some sort of add-on SwiftKey keyboard that is built in to the stock ROM. I think the config file that needs the edited has something to do with SwiftKey instead of the OS. I don't really like Swype so I might try the paid version of SwiftKey to see if it has a way to remove those chars but have a similar keyboard layout that I'm used to. Hopefully they won't even be there by default.
I have the same problem. I try to end a question with? But end up with ñ
Fking maddening
Hey there!
I'm sitting here with a Z1 Compact with the latest official android (4.4.4).
For some time now, even after reinstalling, the keyboard has one flaw. When I hold down the backspace in certain fields, it doesn't continue to erase, nothing happens. I have to click on it continually and even then it's a bit jaggy/jumpy.
It's not all the time, but certain fields and boxes. If I do change keyboards, they work without this issue. Problem is, I've grown fond of the Xperia keyboard. It has everything I want and where I want it.
I'm just wondering if anyone has had this issue before. I can't seem to find anyting in other threads/google but that's cause people sually have bigger issues with their keyboards and they shadow the smaller ones. Is there some kind of fix? Does Sony know about this? Where can I make an official inquiry about my issue?
If I have overlooked a search result where this problem has already been fixed then please do link me that thread. It would be great help!
Thanks for reading!