[Touch HD Themes and Apps] Rozenthal:
[ FAQ - frequently asked questions ]

This will be the place where we'll try to answer some of the common questions and suggest solutions for people who have problems.

DEBUG LOGGER! PLEASE USE IT IF YOU HAVE PROBLEMS!

Attached below, you will find Fingerkeyb_debug.dll file. This file will create a debug log which you can then send to us, so we can detect problems and try to fix them in the next release. It is mostly aimed at solving the problem that some people have with landscape mode, but it can be used to track any other problems as well.

To start using this, you will need Resco Explorer or Total Commander CE.

Go into FingerKeyb folder (Program Files).

1. rename Fingerkeyb.dll to something else (example: Fingerkeyb_.dll)

2. Copy FingerKeybd_debug.dll to Program Files/FingerKeyb directory.

3. Rename FingerKeyb_debug.dll to FingerKeyb.dll

4. Softreset the phone

5. Open the FingerKeyboard, press 1-10 keys on keyboard.

6. Minimize the keyboard, rotate the phone and open the keyboard again, after the phone is in landscape mode. Try to press 1-10 keys again.

7. If you encounter the landscape bug, switch to HTC keyboard, making sure that it shows in landscape correctly.

8. Rename file FingerKeyb.log in working directory to FingerKeyb_test1.log and after that select FingerKeyboard again.

9. You will now have 2 log files in Program Files/FingerKeyb. Send Fingerkeyb.log and Fingerkeyb_test1.log to Exidler or Rozenthal.

If you do not have Resco File Explorer or Total Commander CE, you can try this procedure:

0. Unregister keyboard using the old Fingerkeyb_register.exe (found in v1.4 thread) and then softreset

1. same as above

2. same as above

3. same as above

4. Register keyboard with the Fingerkeyb_register.exe

5. same as above

6. same as above

7. same as above

8. same as above

9. same as above

The log files can be sent to us via private messages here on XDA.

The logging tool will seem very slow, that's normal - it needs to write a bunch of info on every keypress, so take it easy. After you're done, you can simply reverse the procedure: remove the debug.dll, rename back the original Fingerkeyb.dll, and continue using the keyboard normally.

------------------------------------------------

First of all, many of the questions have already been answered and explained in release info. For example, how to make the keyboard stick as default even after soft reset.

How to switch to full CAPS

Press and hold the shift button.

How to use text selection

To select text, switch to full CAPS mode and then use arrow buttons to select text.

How to use cut / copy / paste

Switch to full CAPS mode, select the text you want to cut or copy, and press and hold ^c or ^x characters. Then press and hold ^v to paste. On some layouts these are named "cut", "copy" and "pst" (V, B, N).

How to use Backspace delete functions

- short press on Backspace will delete a single character.

- long press on Backspace will delete a whole previous word.

- going to CAPS lock mode (or just pressing shift) + short press on Backspace will delete one whole line of text

- going to CAPS lock mode (or just pressing shift) + long press on Backspace will delete whole text

How to minimize the keyboard

Short press the keyboard toggle button (the one with small keyboard on it). Long press on this button will switch the FingerKeyboard to default WinMo keyboard.

How to disable click sound

Go into FingerKeyboard folder, open up Skin-01-global.txt (in Notepad preferably) and delete the following line:

ClickSound click-0.wav

You can also add ";" at the beginning of the line - it will have the same effect.

About problems with landscape mode:

- after installing the keyboard, if you notice a bug with portrait skin being used in landscape mode, please try to soft reset the device. Also, try to minimze the keyboard before rotating (there is a dedicated button for this on all layouts - use it!). Open the keyboard back after you rotate to landscape mode. This should work (at least this is how it works for me, on the latest Dutty ROM without any aditional rotation software).

Installation problems:

If you encounter the following message while installing the FingerKeyboard: FngKbdConfig.exe NullReferenceException, one possible solution is to unpack the cab file (use WinRAR or similar software), makes necessary folders manually, copy the files inside and register the new .dll file by using the old Register.exe from version 1.4. You only need to use old Register.exe, not the old .dll file.

If you're upgrading from v1.4 and have problems removing the old version, you will also need to use Register.exe, unregister the keyboard, soft-reset, delete the complete FingerKeyboard folder, soft-reset and then make a fresh install from the latest v2 cab. Deleting the FingerKeyb folder is the safest way of making sure you unregistered the old version!

Editing instructions:

You can use the existing layouts to make it custom layouts! The easiest way is to open one of the layout skin txt files and replace the existing characters with your own. Experiment a bit, and you will soon get the hang of it. Same applies if you want to make your own skin - edit the included bitmaps, and change the appropriate lines in txt files.

You can also change the behavior of the keyboard (such as shorten the long key-press delay, or change how backspace work etc.). This will require a little bit of more effort, but it's nothing too complicated.

Everything you want to know about FingerKeyboard actions, layouts, colors and resolutions is explained in "doc-about-skin.txt" that is located in the root of the FingerKeyb folder. Read it first before asking for help!

"Where is XYZ language layout? Why is it not included!?"

If your language layout isn't included, it is simply because nobody volunteered to make it when we were in Beta testing of v2. If you want a certain language layout, first check this thread if someone maybe already made an additional layout and posted it here. If not, the best thing you can do is to make your own layout and share it here with other people. If your layout is good, we'll probably include it in next version cab. Please do not spam us with "I WANT THIS LANGUAGE!!!" messages. All language layouts depend exclusively on the community to produce them. If no one can't be bothered to make your language layout, we can't really help you.

For Samsung OMNIA users

If you're using FingerKeyboard2 on Samsung Omnia, you've probably noticed there's a font-size bug in 3 out of 5 available skins. This bug has been fixed, you can download the updated Skin txt files HERE.

Other stuff

About some errors or missing letters in some layouts - we jumped from 2 layouts to 17 layouts, from 1 screen resolution to 3, from 1 skin to 5... I didn't honestly expect it will all be error-free. The language layouts were made by our beta testers (and I thank them once again for their work!) so I really can't help with requests "can you please put letter XYZ instead of ZYX" because I don't have a clue as to how all of these different language keyboards should look like. I can help with English and Croatian and Exidler can help with Russian, but that's it. These 3 layouts are most bug-free, anyway.

It's now up to you, the users to try to fix errors in layouts and share them here with others. I think it's really not hard to edit layout txt files, and I'm glad many of you already started playing around and sharing your custom txt files. If there's a character missing you can't live without, the easiest solution is to open your language skin txt file and simply put it in yourself.

Some layouts having square boxes instead of characters - I'm assuming it's simply a matter of regional settings and localized versions of devices. I would guess that, for example, the Arabic layout will look normally for people who have set their regional settings accordingly.

It would also help that when you write about problems, to tell us what device are you using, what ROM and if you have any 3rd party rotation programs installed. Be precise! Describe the problem in as much detail as possible. I will not be bothered to answer posts such as "it don't work for me, help!".