I c a problem that needs a solution - Touch Dual, MDA Touch Plus ROM Development

When typing text using the physical keyboard, XT9 will favour 'c' before 'a'
When typing text using the touch keyboard, XT9 will favour 'a' first
This is really irritating, can anyone suggest a fix?
Thanks

unfortunately it's not just that!
It's pretty lame that there are differences in XT9 using physical and touch keyboard. I've been noticing that a lot!

try this fix - a-to c link

Related

[Q] autocorrect/autocomplete with keyboard dock

im currently using thumb keyboard when just using the tablet and the auto complete/correct works great. however, when i use the physical keyboard, i cant get any kind of autocomplete or correct to work, it just leaves word misspelled and underlines them. is there any way i can have autocorrect function when the physical keyboard is being used?
thanks
chunkdude said:
im currently using thumb keyboard when just using the tablet and the auto complete/correct works great. however, when i use the physical keyboard, i cant get any kind of autocomplete or correct to work, it just leaves word misspelled and underlines them. is there any way i can have autocorrect function when the physical keyboard is being used?
thanks
Click to expand...
Click to collapse
unfortunately, when prime is being used with dock or even with Bluetooth keyboard, prime stops auto-correct. The only keyboard app that still has auto-capitalize and auto-correct option is Smart Keyboard Pro. but it doesn't recognize shift key on prime dock, so you can't use !()?: keys.
I just hope Smart Keyboard Pro fixes this issue asap.
use swiftkey works fine with dock.
Or ~.~
you could just learn to type better? :] not trying to start anything i promise you but i don't truly see a great reason for the autocorrect on a physical keyboard? Maybe for bigger words but this is where our human brains should push ourselves to think. :] I mean I'm not saying it wouldn't be a nice feature. But Party on! TFP ROOTED!
TheEnd94 said:
you could just learn to type better? :] not trying to start anything i promise you but i don't truly see a great reason for the autocorrect on a physical keyboard? Maybe for bigger words but this is where our human brains should push ourselves to think. :] I mean I'm not saying it wouldn't be a nice feature. But Party on! TFP ROOTED!
Click to expand...
Click to collapse
Have you ever thought about that people are not always typing in their native language and that correction can be a good Help?
For me exempel, My language is Swedish and for that I don't need predictions or correction. But when on XDA and i had to write in English the correction and predictions comes in use. I know what I want to type but don't know exactly how it's its spells. So I just type how it sounds in my head and gets predictions on what I trying to write.
Think it's helps everyone, the grammar is fick up but atlest the words is correctly. And it make it easier for everybody to understand what I trying to say.
And for the keyboard I think "Swiftkey Tablet X" does a good job with the dock.. You get a little line on the bottom of your screen with the predictions and suggestions.
https://market.android.com/details?id=com.touchtype.swiftkey.tablet
All buttons work, Haven't find any problems. Shift !()?: keys works as i should
Andreas527 said:
Have you ever thought about that people are not always typing in their native language and that correction can be a good Help?
For me exempel, My language is Swedish and for that I don't need predictions or correction. But when on XDA and i had to write in English the correction and predictions comes in use. I know what I want to type but don't know exactly how it's its spells. So I just type how it sounds in my head and gets predictions on what I trying to write.
Think it's helps everyone, the grammar is fick up but atlest the words is correctly. And it make it easier for everybody to understand what I trying to say.
And for the keyboard I think "Swiftkey Tablet X" does a good job with the dock.. You get a little line on the bottom of your screen with the predictions and suggestions.
https://market.android.com/details?id=com.touchtype.swiftkey.tablet
All buttons work, Haven't find any problems. Shift !()?: keys works as i should
Click to expand...
Click to collapse
very good point made. english speakers should take note. but in truth, it is harder for me to check the ''correction'' bar than it is to backspace when i see a mistake. i guess thats just the habit of using a physical keyboard for years on pcs
just wanted to bump this thread to see if anyone has a solution yet, as i havent found anything that addresses my original problem

Using physical keyboard to type accented words

Ok, so I've been searching around and trying different things but I still cannot get this to work like I expected: how can I use the physical keyboard on my Prime to type accented words without changing the keyboard layout?
On Windows I can get this done easily if I configure my keyboard layout as "US-International" and the input language as "Portuguese (Brazil)" (which is the language I want to type in). This way, when I press the single quote key, for instance, the system waits for the next typed letter to decide what to do: if I type a letter which accepts an accent (such as "a"), Windows will add the letter with the accent (in this case, "á"), otherwise it will just add the single quote.
On my Prime, if I change the default input language of the ASUS keyboard to Portuguese, I am able to type accented words but the keyboard layout is also changed to the Brazilian standard. This causes a problem: the positions of some keys are changed (about 8 of them). I could memorize the new positions of the keys, this would be fine except for the fact that I can't type question marks or slashes with this layout! (at least I didn't find any way to do so)
Then I tried using Swiftkey X, if I choose that as the default input method (with the Brazilian Portuguese dictionary enabled) and type using the physical keyboard I don't even need to type the accents because the auto-correct feature takes care of that for me, this is very good but there are some problems with this method:
- When typing question marks or exclamation points at the end of the sentences, the last word in the sentence ends up getting capitalized since I need to hold the "Shift" key to type those marks (I can work around this problem by typing the word, then a space and then the question mark or exclamation).
- If I need to type a word which is only one accented letter, depending on what the prediction engine does I might have to manually choose the right prediction by touching the screen (it gets the job done, but it's a little annoying). We have a few words like this in Portuguese, such as the word "é" which is used often (it means "is", while the word "e" means "and", that's why the prediction engine might suggest either of them).
Anyway, hopefully you guys understand the problem and have a good suggestion for me.
Currently I think the best solution is to use Swiftkey X and live with the small annoyances I mentioned (I'll e-mail them and maybe suggest they make improvements for this), but does anyone know of any other way I could make the physical keyboard on my Prime behave like the one on my Windows laptop?
Thanks in advance!
I re-posted this on the Q&A section (because that seems to be the correct one), please delete this thread and sorry about that
I don't know if this helps, but in Spanish, if you use a different software keyboard (like Swype, or others), this breaks the configuration of the physical keyboard and you can't use special spanish keys like Ñ. The solution is to root the device and edit a system file.
By the way, my keyboard is localized to spanish language, so I have no problems with it. Is your keyboard localized to portuguese?
Do you mean my physical keyboard? It's the US version, if I try to type "é" like I do in Windows (I type the single quote " ' " and then " e "), I end up getting " 'e ".
If I switch the language of the ASUS keyboard to Portuguese, it works like in Windows but there's the problem of the remapped key layout.
I read about the rooting solution you mentioned, perhaps that might work if I use it with the ASUS keyboard configured for Portuguese, I could change the layout to match that of the US keyboard. Problem is, I just bought the tablet and I'd lose my warranty, or is there a way to unroot it if I needed to?
Maybe you could type those letters by entering their ascii code.
I don't know if there's an unroot method, you should check in the development forums.
intre said:
Maybe you could type those letters by entering their ascii code.
I don't know if there's an unroot method, you should check in the development forums.
Click to expand...
Click to collapse
That's a good suggestion, but I don't know if it would be too practical since quite a lot of words in portuguese use accented letters, but thanks anyway!
I think I'll root my Prime and then use the ASUS Portuguese keyboard with remapped keys...

[Q] Using physical keyboard to type accented words

Ok, so I've been searching around and trying different things but I still cannot get this to work like I expected: how can I use the physical keyboard on my Prime to type accented words without changing the keyboard layout?
On Windows I can get this done easily if I configure my keyboard layout as "US-International" and the input language as "Portuguese (Brazil)" (which is the language I want to type in). This way, when I press the single quote key, for instance, the system waits for the next typed letter to decide what to do: if I type a letter which accepts an accent (such as "a"), Windows will add the letter with the accent (in this case, "á"), otherwise it will just add the single quote.
On my Prime, if I change the default input language of the ASUS keyboard to Portuguese, I am able to type accented words but the keyboard layout is also changed to the Brazilian standard. This causes a problem: the positions of some keys are changed (about 8 of them). I could memorize the new positions of the keys, this would be fine except for the fact that I can't type question marks or slashes with this layout! (at least I didn't find any way to do so)
Then I tried using Swiftkey X, if I choose that as the default input method (with the Brazilian Portuguese dictionary enabled) and type using the physical keyboard I don't even need to type the accents because the auto-correct feature takes care of that for me, this is very good but there are some problems with this method:
- When typing question marks or exclamation points at the end of the sentences, the last word in the sentence ends up getting capitalized since I need to hold the "Shift" key to type those marks (I can work around this problem by typing the word, then a space and then the question mark or exclamation).
- If I need to type a word which is only one accented letter, depending on what the prediction engine does I might have to manually choose the right prediction by touching the screen (it gets the job done, but it's a little annoying). We have a few words like this in Portuguese, such as the word "é" which is used often (it means "is", while the word "e" means "and", that's why the prediction engine might suggest either of them).
Anyway, hopefully you guys understand the problem and have a good suggestion for me.
Currently I think the best solution is to use Swiftkey X and live with the small annoyances I mentioned (I'll e-mail them and maybe suggest they make improvements for this), but does anyone know of any other way I could make the physical keyboard on my Prime behave like the one on my Windows laptop?
Thanks in advance!

Keyboard issue a bug??

Hy guys
My first post. Im a newbie to this android, learning new stuff everyday. Im facing a wierd issue in the keyboard when i change it frm qwerty to 3*4 keyboard in portrait keyboard option as i have got big thumbs, its damn hard for me to use qwerty on portrait style.
Once changed to alphabetic, its typing numbers in double. For eg if i press keypad number 9 for letter "z", it will type "99" in single press. If i change symbols to numbers, then it will again type numbers but in singular format. Can pls som1 tell me how to write in letters not in numbers in 3*4 keyboard?
Bump
Sent from my GT-I9300 using xda premium

Writing SMS with flesky - can't see what i'm typing

As you can see in this video, someone types a sms and sees what he's typing in the textbox obove the flesky input.
youtube.com/watch?feature=player_embedded&v=rxW7021o-Ac
But on my Omate, this textbox is overlapped with the flesky input, so i can't see what i'm typing. In comparison to the video, the upper address/contact box takes more space on my device.
Hiding the spacebar doesn't help either.
Any idea how to solve this issue?
That's known problem...
I saw one picture on G+ where's keyboard in only one row...
Don't know what's the name of that keyboard but try to check on market, maybe you find something.
BTW...for setting TS and all accounts you can use BT keyboard (bluetooth) but, of course, that could be useful only for that - I really doubt you'll take your bt keyboard with you all the time
Sent from my C6903 using Tapatalk
jediknight23 said:
As you can see in this video, someone types a sms and sees what he's typing in the textbox obove the flesky input.
youtube.com/watch?feature=player_embedded&v=rxW7021o-Ac
But on my Omate, this textbox is overlapped with the flesky input, so i can't see what i'm typing. In comparison to the video, the upper address/contact box takes more space on my device.
Hiding the spacebar doesn't help either.
Any idea how to solve this issue?
Click to expand...
Click to collapse
Try installing Flit keyboard
https://play.google.com/store/apps/details?id=com.locnet.flitkeyboard
Configure it to then have the first keyboard as being small alpha only, then set the second keyboard to be numeric etc....
Should give you some more screen space
I changed the system language to english, so the upper address field uses less space. So I can see the text input box.
It's just a workaround, but I can live with it.
In all other apps I use, the flesky input works fine and no input field is overlapped.
But maybe it would be a good solution if you can select a semi-transparent keyboard. In the flesky option you can select an invisible keyboard, but thats not useful for me.

Categories

Resources