I don't know about you people, but I was so used to the automatic spelling correction of PCM Keyboard, that I found the Manila full querty to be a real step backwards. I also don't like the way the letter pop-up preview is actually covered by the fingers used to press the keys.
The only problem with PCM Keyboard, so far, has been the lack of a good VGA skin for it, so here is a Diamod themed skin I made for version .14 (the latest stable version).
The actual keyboard software is free and can be downloaded here: PCM Keyboard
-------------------------------------------------
Edit: I am also including my own layout, for those interested. You have to place it in the PCM Keyboard folder and select it from the options. here's what it does:
1. holding down the apostrophe brings up accented letters etc.
2. holding down the quote brings up the rest of accented letters etc.
3. holding down the 123 key brings up useful punctuation.
See thumbnails for details.
Looks good... would it be possible for you to post a landscape image?
Thanks.
Drybonz said:
Looks good... would it be possible for you to post a landscape image?
Thanks.
Click to expand...
Click to collapse
Crap, I never use landscape mode, and I can't find screen rotation in the Diamond?
edan said:
Crap, I never use landscape mode, and I can't find screen rotation in the Diamond?
Click to expand...
Click to collapse
You could just pop up the keyboard in Opera landscape... or try the new Gyrator2 app that just got released.
Well, I started using your skin and I love it.
I really like the keypad style number layout. Works so much better for me than the qwerty "numbers in a straight line" layout.
Also, this is the best landscape keyboard layout I have seen. I replaced Touchpal because the landscape is not so hot. Now that Gyrator is working on my phone I needed a good landscape keyboard.
I can type so much faster now.
Thank you. Thank you. Thank you.
edan said:
I don't know about you people, but I was so used to the automatic spelling correction of PCM Keyboard, that I found the Manila full querty to be a real step backwards. I also don't like the way the letter pop-up preview is actually covered by the fingers used to press the keys.
The only problem with PCM Keyboard, so far, has been the lack of a good VGA skin for it, so here is a Diamod themed skin I made.
The actual keyboard software is free and can be dowbloaded here: PCM Keyboard
All comments welcome...
Click to expand...
Click to collapse
Any chance you can upload DiamondSkin2? Or do i have to edit it myself? How?
Those two thumbnails refer to the same skin. One is simply showing it in an SMS and the other is in Word.
edan said:
Those two thumbnails refer to the same skin. One is simply showing it in an SMS and the other is in Word.
Click to expand...
Click to collapse
Weird cos this is what i'm getting on my Touch Pro. It's missing "," & "."
Just wondering.....any chance you can make the format like those i've attached?
Scann69 said:
Weird cos this is what i'm getting on my Touch Pro. It's missing "," & "."
Just wondering.....any chance you can make the format like those i've attached?
Click to expand...
Click to collapse
What you are talking about is affected by the keyboard layout file, not the skin. Look in the PCM Keyboard folder on your touch pro and you will see a file like "english.layout" or whatever you chose as your layout.
Open that up in notepad and change the keys to whatever you want. There is a lot of information on the PCM Keyboard site linked in the first post regarding layout customization. The skin will adapt itself to whatever you do with your layout file.
To place the comma and period on the sides of the spacebar as in my thumbnails change your "keyboard_layout_1=" in your file to:
Code:
keyboard_layout_1=qwertyuiop\nasdfghjkl'\n\2zxcvbnm\B\B\n\M\M, .\N\N
very nice !!!
thanks
I decided to include my custom layout. It's English, though it does have a ton of special letters and symbols. The numbers pad is pretty complete as well.
edan said:
What you are talking about is affected by the keyboard layout file, not the skin. Look in the PCM Keyboard folder on your touch pro and you will see a file like "english.layout" or whatever you chose as your layout.
Open that up in notepad and change the keys to whatever you want. There is a lot of information on the PCM Keyboard site linked in the first post regarding layout customization. The skin will adapt itself to whatever you do with your layout file.
To place the comma and period on the sides of the spacebar as in my thumbnails change your "keyboard_layout_1=" in your file to:
Code:
keyboard_layout_1=qwertyuiop\nasdfghjkl'\n\2zxcvbnm\B\B\n\M\M, .\N\N
Click to expand...
Click to collapse
Thank you so much for the explaination Managed to get it the way i like it already
Scann69 said:
Thank you so much for the explaination Managed to get it the way i like it already
Click to expand...
Click to collapse
Edan, I am interested in changing the "123" button to "abc" when on the number screen (a technicality, but would look nice). Just wondering if this can be edited in the layout file or if it is theme specific.
Also, have you tried your skin on the .15 version of PCM? I noticed they have more customization options in that version.
Thanks.
Drybonz said:
Edan, I am interested in changing the "123" button to "abc" when on the number screen (a technicality, but would look nice). Just wondering if this can be edited in the layout file or if it is theme specific.
Also, have you tried your skin on the .15 version of PCM? I noticed they have more customization options in that version.
Thanks.
Click to expand...
Click to collapse
I have managed to create a new key with an ABC button. The real problem lies in assigning an action (switch layout to layout 1) in the .ini file.
Almost everything related to customizing version .14 has been removed from the site. So, it's a little hard now... unless we can get some tips from the author.
Version .15 is not even beta stage, and is extremely unstable on the diamond. It's really just a big mess at the moment... not worth the headaches...
edan said:
I have managed to create a new key with an ABC button. The real problem lies in assigning an action (switch layout to layout 1) in the .ini file.
Almost everything related to customizing version .14 has been removed from the site. So, it's a little hard now... unless we can get some tips from the author.
Version .15 is not even beta stage, and is extremely unstable on the diamond. It's really just a big mess at the moment... not worth the headaches...
Click to expand...
Click to collapse
Yeah, I noticed they still claim .14 is the stable version but the tutorial is for .15. I wasn't able to get much further than changing a couple symbol keys in the layout file.
Anyway, thanks again for the great skin and please keep us updated if you make any changes.
Drybonz said:
Yeah, I noticed they still claim .14 is the stable version but the tutorial is for .15. I wasn't able to get much further than changing a couple symbol keys in the layout file.
Anyway, thanks again for the great skin and please keep us updated if you make any changes.
Click to expand...
Click to collapse
Some problem. After like 2 minutes of use, my diamond crashed (really badly with numerous report error windows popping up). Some of the keys were not showing and some of the keys showed gibberish (some nonsense chinese words) - check out the first screenshot.
I believe it's because of the encoding when the layout files (both English layout and the one OP made) is saved. I tried opening the layout file in notepad and lots of the key assignments were gibberish. So, I tried opening it in Word and found out the original file was saved with Turkish Windows encoding. I opened it in the right encoding (so that all the keys were shown correctly) and then saved it back with unicode encoding. Then I put the revised file back to the PCM folder and it did wonders - check out the second screenshot.
So, an advice. If you find the keyboard is not showing what should be shown. Check out the .layout file that the OP posted and try modifying it and save it with another encoding (can be done in Word but not notepad). For my case (diamond with English ROM), unicode works for me.
I have attached the modified layout file (saved with unicode encoding). You can try this one if the original one doesn't work for you. No guarantee though.
I tried using the Diamond skin but the period and comma buttons are missing on the keyboard? I have to press the "123" to access the symbols keyboard. Can someone help please?
clue11 said:
I tried using the Diamond skin but the period and comma buttons are missing on the keyboard? I have to press the "123" to access the symbols keyboard. Can someone help please?
Click to expand...
Click to collapse
Please read this thread. All the answers are here already.
Oops. completely missed that part. Sorry and thanks for the skin!
Edan, have you considered doing a PCM Contacts skin? VGA ones are hard to come by.
I have tried to modify the soft keyboard in cupcake, but with little luck... I thougth the easiest way would be to modify the existing code, but when I create a new project in eclpse based on that code, I get a lot of errors e.g. mScrollX cannot be resolved and com.android.internal.R cannot be resolved. It seems that eclipse doesn't recognize some of androids built in variables. I found a thread at google groups about the same problem, but I didn't understand the solution: "You need to change the code to use the public SDK (calling the View functions to get/set the scroll position etc).".
What I'm trying to do is modify the keyboard so that I don't have to long press a and o to get the norwegian letters æ, ø and å. I want them together with the english letters.
I have searched but can not find the answer...
I have installed T9 languages and it works. But I also need a different keyboard layout, with åäö. Where in registry do I fix this? Or do I need to use a third party input software?
Thanks a lot.
Not anyone?
Would be very thankful for answer.
the registry is not a general place where all program settings and options are stored
a program need not use the registry at all it all depend on how the programmer made the app
Dear all:
I have been able to convert my German X2 successfully into Dutch/Belgian language using the information contained in another thread.
However, I am now faced with Dutch/Belgian language, with a corresponding AZERTY keyboard layout.
The trouble is that the German hardware QWERZU keyboard is now also typing in AZERTY layout and the keys do not correspond.
Question: how can one change the hardware keyboard layout in such a way that it reverts back to the German QWERZU so that I can at least see what I type?
I have searched all over this forum and elsewhere on the net, but found no working solutions so far. The solutions that were offered, do not seem to work.
Has anybody managed in doing so succesfully? If so, I would greatly appreciate urgent feedback as this is really annoying right now. Thank you so much.
x2user said:
Dear all:
I have been able to convert my German X2 successfully into Dutch/Belgian language using the information contained in another thread.
However, I am now faced with Dutch/Belgian language, with a corresponding AZERTY keyboard layout.
The trouble is that the German hardware QWERZU keyboard is now also typing in AZERTY layout and the keys do not correspond.
Question: how can one change the hardware keyboard layout in such a way that it reverts back to the German QWERZU so that I can at least see what I type?
I have searched all over this forum and elsewhere on the net, but found no working solutions so far. The solutions that were offered, do not seem to work.
Has anybody managed in doing so succesfully? If so, I would greatly appreciate urgent feedback as this is really annoying right now. Thank you so much.
Click to expand...
Click to collapse
you should use the AE Keyboard Mapper to replace the hardware keyboard layout, for AE Keyboard Mapper intentionally a specially designed key mapping almost all external or built-in hardware keyboard or keypad is connected to a Windows Mobile device. You can use it for "localizing" keyboards (if there is no support from the OEM keyboard driver on your language) or just for the mapping of some keys (like the conversion from AZERTY to QUERTY, the addition function by disabling the Ctrl key or application key binding).
my advice, you just visit his WebSite to get more information and also download it ---> http://ae.inc.ru/aekmap.php
Thanks for the hint. Downloaded and tried it but somehow I cannot choose any other layout than Russian. Even if I type in "German" instead of English, nothing happens.
I also tried out hints pertaining to the X1 (changing the registry etc) but these do not work either as the relevant registry lines do not appear. I guess there must be a difference between X1 and X2 in this respect.
All very disappointing I should say.
Hello.
I want to make communicator from my android phone (like Nokia 9210, new Livermorium Cosmo or F(x)tec Pro1). I am working on usable slide-out mechanism, but I got problem with hardware keyboard layout remapping. It is difficult without root and probably impossible to be combined with any alternative software keyboard. Therefore I went to make own app as fork of kwx Hacker's keyboard https://forum.xda-developers.com/showthread.php?t=1088776 . I would try to contact kwx and publish the source codes on the original https://github.com/klausw/hackerskeyboard, also add HW keyboards support to the app on the marketplace https://play.google.com/store/apps/details?id=org.pocketworkstation.pckeyboard. Until then you can try the first beta version.
Features:
1. No root needed.
2. Alt + Left shift == Next language/locales (MS windows standard like).
3. Alt + Right shift == Toggle software keyboard (neded to see actual layout, to make any unusual characters, or to use Hacker's Keyboard on small devices).
4. Icon with language/locales identification in Android notify area (this works for switching between English and Czech keyboard only in beta 001 version).
5. Hardware keyboard remapping depends from software keyboard language/locales switching. For example: I have checked "English", "Czech" and "Czech-qwerty" layouts in Hacker's keyboard settings. When "English" is active, HW keyboard is not remapped. When "Czech-qwerty" locale is active, top keys row is remapped to "+1ě2Ěš3Šč4Čř5Řž6Žý7Ýá8Áí9Íé0É=%´ˇ", "úÚůŮ" keys are present etc. When "Czech" locale (QWERTZ) is chosen, also "Z" and "Y" keys are swapped.
Limitations of beta 001 version:
- Hardware keyboard original layout can be "English" only. I think the vast majority of the offered bluetooth keyboards has an English layout.
- Icons displaying "EN" and "CS" are now ready in this version, other languages/locales will get the icon in the next versions.
- Behavior Alt+Y and Alt+Z, as well as Ctrl+Y and Ctrl+Z are not exchanged on the QWERTZ layout keyboard (and similar cases on other layouts).
- I am not sure, if this application installation wil not reset previous Hacker's keyboard settings (when present on phone before). OK, beta is installed as Hacker's Keyboard actualisation in this case.
- Modificators "´", "ˇ" etc affect the previous, not the following character, even multiple times. I do not know why. It is still usable.
Beta testers are welcome for reporting other errors.
Please, use antivirus before downloaded App using. I am totally new in android development. I do not know, how to protect developed Android applications from viruses. I hope my Android Studio is not infected.
Beta 001 apk.