HowTo: Modify Swype (new dictionaries; new keyboard layouts) - Desire Themes and Apps

Hi,
a few people asked me to post a how-to for swype.
First of all: i am a noob, my first contact with android was just a few weeks ago and i saw my first apk from the "inside" a couple of days ago. So there is for sure a much easier way (push the files directly to the phone) and a better way. Anyway, this works for me 100% and maybe this guide helps a bit.
Second: Sorry for my english, i hope it is understandable
Here we go:
What you need first:
- the newest Swype beta (currently it is Ver. 1.25.16.5612.t100 i think, which is only available with english and spanish language). -> swype-new
- an old beta with the desired language or keyboard style (f.e. german dict, french dict..). -> swype-old
The bigger the swype file, the more likely it has your desired languag, a 2,2mb file has mostly only English and Espagnol
- Winzip (http://www.winzip.com/prod_down.htm)
- Java SDK for signing the new apk (f.e. http://www.chip.de/downloads/Java-SDK_12992754.html)
- this guide for signing an apk (http://www.anddev.org/viewtopic.php?p=11105) -> some "\" are missing in this guide, you'll see it..
1. Download Winzip, Java SDK and install it
2. Download the current and the old swype beta versions
3. rename both .apk files to .zip
4. open both zip files with winzip
5. go to the folder assets/files @ swype-old and search for your desired dicitionary, for example "German.zdb.le". Open swype-new and go to the same directory, delete for example the Spanish.zdb.le file. Now copy the German.zdb.le from swype-old the swype-new and rename it to Spanish.zdb.le.
6. got to assets/keyboards @ swype-old. Copy your keyboard layout (AZERTY, QWERTZ, Russian) to swype-new. If you don't know exactly which files you need, just copy all missing files from the old to the new one. There should be a bunch of files called for example Qwertz_PT_* and Qwertz_LS_*
7. Delete the META-INF folder from the swype-new version.
8. rename the swype-new.zip to swype-new.apk
9. Open a command prompt (cmd) and follow this guide:
http://www.anddev.org/viewtopic.php?p=11105
Obviously >DrogrammedevJavajdk1.6.0_07binkeytool -genkey -alias anddev.keystore -keyalg RSA -validity 20000 -keystore keys/anddev.keystore
should look like this:
D:\Programme\dev\Javajdk1.6.0_07\bin\keytool -genkey -alias anddev.keystore -keyalg RSA -validity 20000 -keystore keys/anddev.keystore
you need "keytool -genkey -alias anddev.keystore -keyalg RSA -validity 20000 -keystore keys/anddev.keystore" for the key and
"jarsigner -verbose -keystore keys/anddev.keystore -signedjar AndOpenStreetMap_signed.apk AndOpenStreetMap.apk anddev.keystore" for the signing process.
The apk should be signed now.
10. copy the swype-new-signed.apk to your sd
11. uninstall all previous swype versions and reboot.
12. install swype
13. activate swype via settings -> keyboard -> check swype
14. go into an EMPTY input field and do a long press -> input method -> swype
15. just to be 100% sure.. reboot
16. switch to Espagnol language (which has been replaced) by pressing the Q button
17. done
If you can not switch the language or if you have multitouch-problems, a reboot will fix this for sure (or 99.9% ..)
You can also edit your desired keyboard to the look you like, just open the corresponding *png and do what you want. The glow.png contains the color for the "highlight" when you press a button.
Do it at your own risk, this is really easy. As said: there are much easier ways to do this, but this works for me. There are some autosigning scripts for apk out there but for some reason they did not work for me (mainly cause i have no clue what i am doing here).
Here are some (veery simple examples):
edit: if anyone knows how to change the tracer color from blue to ??? please let me know, and how to edit the language dialog so we do not have to chose Espagnol to get the desire language
edit2: Tracer color: open the libSwypeCore.so with a hex editor, search for DDA25BFF, take your desired ARGB code and enter it there but reverse the pairs! so if you like FF00A5BF you have to enter BFA500FF.

I am interested in just changing the color of the Keyboard but your instructions here are not for a nob like moi.

HOW to Sign is really hard to understand, please a step by step maybe in english would be appreciated.
THX!

I have made an Italian dictionary Swype apk if you are interested contact me in pm.

Any1 know where i can get and copy of swype with Danish dictionery?

can you post the apks of the ones you modified already, I love the brown color, and the white too!

le3ky said:
can you post the apks of the ones you modified already, I love the brown color, and the white too!
Click to expand...
Click to collapse
yeah could u post sum edited apks please?

i can't even find swype in the app store ? was it removed ?

554321 said:
i can't even find swype in the app store ? was it removed ?
Click to expand...
Click to collapse
Swype still hasn't "officially" been released. We are using leaked versions from devices that ship with Swype.

please pm me, no links will be postet
@ signing guide:
this guide is in english, what is the problem?
http://www.anddev.org/viewtopic.php?p=11105
-download the java sdk
- create a folder c:\workspace
- create a folder c:\workspace\keytools
- create a folder c:\workspace\keytools\keys
- open a command (cmd) and change to folder workspace\keytools
- type in the following: C:\Program Files\Java\jdk1.6.0_20\bin\keytool -genkey -alias anddev.keystore -keyalg RSA -validity 20000 -keystore keys/anddev.keystore
- answer the questions
- copy your .apk to c:\workspace\keytools
- change again to workspace\keytools
- type in: c:\Program Filex\Java\jdk1.6.0_20\bin\jarsigner -verbose -keystore keys/anddev.keystore -signedjar yourapk_signed.apk yourapk.apk anddev.keystore
yourapk.apk = the filename

watercool said:
please pm me, no links will be postet
@ signing guide:
this guide is in english, what is the problem?
http://www.anddev.org/viewtopic.php?p=11105
-download the java sdk
- create a folder c:\workspace
- create a folder c:\workspace\keytools
- create a folder c:\workspace\keytools\keys
- open a command (cmd) and change to folder workspace\keytools
- type in the following: C:\Program Files\Java\jdk1.6.0_20\bin\keytool -genkey -alias anddev.keystore -keyalg RSA -validity 20000 -keystore keys/anddev.keystore
- answer the questions
- copy your .apk to c:\workspace\keytools
- change again to workspace\keytools
- type in: c:\Program Filex\Java\jdk1.6.0_20\bin\jarsigner -verbose -keystore keys/anddev.keystore -signedjar yourapk_signed.apk yourapk.apk anddev.keystore
yourapk.apk = the filename
Click to expand...
Click to collapse
wow... that is way more complicated than how I sign files. There are several easy tutorials on this process, and a program called autosign. search it and you will see several postings about it...

i know but autosign does not work for me, no idea why. Please read the first post, i have already said that there are much easier ways but this is the only way which works for me.
so if you do not like it, just leave this thread please.

This doesn't seem to wortk in the latest releases.
I tried upzipping without altering it, then remove metainf and resigning...but at runtime I get errors. Installing went ok though.
Any ideas?
Thanks

Could Anyone please comment if they succeeded or not?
thx

Drane said:
Could Anyone please comment if they succeeded or not?
thx
Click to expand...
Click to collapse
Didn't work for me. I used this method: http://forum.xda-developers.com/showthread.php?t=473580
But it still gives trouble after replacing the dictionary.

How did you find the location of the tracer line? I was looking through source code files, never would have figured that out! Thanks!

I've successfully changed the tracer color and resigned the apk, but after I install swype, I get the blue box around the keyboard problem and am unable to swype. Tapping works though.

A greek dictionary would be really appreciated

I tried this with the Sept. beta, signing and installing went fine. But it force-closes. I even tried to just re-sign the original IME from Swype with no other changes, and it still force closes. The keyboard appears for a brief few seconds before FCing.
Dang it.

also trying to mess with the new beta, color is changed or handeled different, the sting you state in your original post isnt found....
Any one figure out what it was changed to ?
scratch that, its there. It colors it a few shades darker than what you want, anyone changing it choose a color a few shades lighter, and odds are it will come close to what you need.

Related

Way to make your Language OS for Universla

the way to OS Localize your Universal
*****the files and tools you need*******
*imgfs_tool by mamaich
*boot_hv_tool by mamaich
http://forum.xda-developers.com/viewtopic.php?t=34171&start=0
*HTC-64 Encodetool by bal666
http://forum.xda-developers.com/viewtopic.php?p=191164#191164
*hex editor (i used Heiw32 accroding to suggestion of Mamaich)
*NotePad in Windows
*Other high performanced Editor(if you have)
*Resource Hacker or PE Editor + Resource Tunner to edit mui
*Signcode.exe and sign with certificate
-----sorry can not write all in here,,, pls go to link---
http://www.asukal.jp/WM5_MUI/the way to OS Localize your Universal.mht
***********additional information 2006-May-15**********
regarding to initflashfiiles.dat and initboji.dat
i tired to write initflashfiles.dat in Japanese chalachtor, but not in CODE,
seems to work.
*write initflashfiles.dat in Japanese to specify Japanese Localized shell folders and Japanese re-named Short cuts. then add into rom.
also deleate both of 2 old dat files from rom.
then flash it back to my Uni, the localized shell folders were created!
this can save a lot of time to create the Localized ROM :shock:
But,,, still testing that ROM can work correctry.......or not.
<some appurication buttons can not assained if without initboji.dat>
*************2006-May 22 aditional********************
@ to edit the dll or exe from AKU2 rom, they have some difference.
Strings can be edited only with Platform Builder now.
pls reffer to this thread
http://forum.xda-developers.com/viewtopic.php?t=49423&highlight=
Can I have your instructions?
Hi Asukal(sama):
I'm trying to localize my Universal to my local language.
I'm stuck now before boot set-up process after hard reset.
So, I would like to ask you several questions.
Could you show me your instructions / suggestions?
1) Certification Store (way 2-1)
You said I have to take out CertificationStore from registry file.
I could not find any key of "CertificationStore", so I compared my registry before and after SDK_Cert installation.
I found there are some differences in registry file, which are:
HKEY_LOCAL_MACHINE\Comm\Security\SystemCertificates\SPC\Certificates\XXXXX] –- 3 keys
HKEY_LOCAL_MACHINE\Comm\Security\SystemCertificates\Privileged Execution Trust Authorities\Certificates\XXXXX] – 3 keys
[HKEY_LOCAL_MACHINE\Comm\Security\SystemCertificates\Unprivileged Execution Trust Authorities\Certificates\XXXXX] – 2 keys
I removed "\" that locates on each line of hex data and write these keys on default.hv file.
However, the start-up process just after hard reset didn't start...
I also found some other differences on registry files, which seems certification file update time.
Do I have to put update time keys on default.hv file?
Or am I still missing something?
2) MUI (way 2-2)
I could sign *.mui files with SDK_Cert.
You said PE header must be corrected if I cannot sign *.mui.
In other words, you mean I don't have to correct PE headers because I can sign my *.mui?
As far as I checked my *.mui files, it seems OK.
3) iniboj.dat (way 3)
I could dump iniboj.dat and initflashfiles.dat and translated them to my language.
Of course I saved in Unicode (UTF-16) and removed the first 2 byte "ff fe".
When I run "delfile.exe", I noticed "delfile.exe" showed the error message that "delfile.exe" could not find iniboj.dat.
But I could add iniboj.dat with "addfile.exe".
Is this a normal message from "delfile.exe"? FYI, my base ROM is Qtek's AKU2; 1.30.77.
4) *.hv files (way 4)
I think the following is the keys that I must change.
[HKEY_LOCAL_MACHINE\System\Explorer\Shell Folders]
"StartUp"="\\Windows\\StartUp"
"Recent"="\\Windows\\Recent"
"Programs"="\\Windows\\Programs"
"Favorites"="\\Windows\\Favorites"
"Desktop"="\\Windows\\Desktop"
Even I changed these keys, I cannot start my start-up process...
Are these keys enough to start start-up process?
I appreciate any suggestions / supports / instructions!!
Thank you.
hi! Camrade!
Re Qeuestions
1;certificate sotre. 3 entries are correct.
@But i am not sure what you removed???
i did not remove any thing and copy it to HV.
@yes update time must be in HV also.
like follows.
without this. no work as sertificate authentification.
[HKEY_LOCAL_MACHINE\Comm\Security\SystemCertificates\Privileged Execution Trust Authorities]
"UpdateTime"=hex:\
00,e0,46,50,1c,96,c5,01
2;if your mui can be signed, they should be workable.
but i am afraid your mui of core-dll Strings Table were broken.
PLS reffer this thread about that!
http://forum.xda-developers.com/viewtopic.php?t=49423&highlight=
if you are not sure, pls send me one of them to check it.
3:re-iniboj.dat, as you told me the eror message of delfile.exe will notice you, because i doesnt exisit in rom files. it was in XIP area.
But dont mind that. procceed it!
4;Shell folders; that is enough in hv, to just specify the loaction of Shell folder.<this also discribed in shellres.dll.
But no start up menu if there were localized Shell folders by failed initialized 2 dat files.
@the os can boot even the shellres.dll.xxxx.mui is not worked,
just missing Programs in StarMenu.
Now i am afraid your shellres____mui is read by OS, but it was incorrect.
@to change the Dr.Johnson screen to Japanes one, replace "stylus2.192.gif" and "stylus1.192.gif" with ones from JP os.
But the fisrt sentence before Stylus work for Dr.Johnson is from Shellres.mui, so your are failed in to read shellres_mui if it was still english.
Good luck!
Almost completed
Thank you, Asukal!
With your responses and instructions, I can finally boot my Universal with my language from boot screen!
I’ll make init*.dat file and try to make more localized ROM.
It seems a little difficult (complicated) to make initflashfiles.dat file translating to Unicode character code. But I’ll try!
Again, Thank you very much!!
shugoh
pls try to write iniflshfile.dat in Katakana, instead of Code,
i did try this some part of them just now.
Seems to be worked. But not sure .........didnt test all of in this dat,
just a part of it.
if the Katakana written dat was workable, it will be so easy to create
the Shell folders in Japanese................ :lol:
Hi Asukal,
I also want to join but I don't have the hex editor....the process is so complicated and the "key" is we have you on this website that do cook the ROM for us. Thanks a lot again.
If you have invented some easy installation files that want me to try, please let me know. I tried to edit the latest O2 ROM but unsuccessful....
Cheers,
chris_khho said:
Hi Asukal,
I also want to join but I don't have the hex editor....the process is so complicated and the "key" is we have you on this website that do cook the ROM for us. Thanks a lot again.
If you have invented some easy installation files that want me to try, please let me know. I tried to edit the latest O2 ROM but unsuccessful....
Cheers,
Click to expand...
Click to collapse
free hex editors can be downloaded.
many kinds of hex editors were in web.
Anyway, if i need something need test, i will call u! :lol:
Hi, Asukal:
This my be very stupid question...
I could translate html portion of shellres.dll with your instruction.
However, I still cannot do of tapres.sll and tshres.dll.......
Maybe this is because the type of resouce is different from shellres's.
So I tried to move html of tapres and tshres to another resources using PB because the other tools I have doesn't work...
When I wanted to save modified resource on PB, PB said I could not save the new resource because PB could not load resources from executable file...
I know this question is the basic one if I want to use PB.
But if you can show (a) hint(s) to me, I would appreciate your support very much.
Thank you!
shugoh
i guess PB can only save the files as "*****.exe" or "******.dll",
but not as a "******.dll.xxxxx.mui"
so you must save it as "anyname_you_want.dll" with out xxxx.mui to other folder.
then go to next step, because files edited with PB can not to be signed.
To enable to be signed, go following steps.
1;Open "any dll" or exe which havs correct PE header with Restorator.
2;Dlelete all of resources from this dll or exe.<make empty dll>
3:On another window of Resotrator ,
Open "anyname_you_want.dll" edited and save by PB
4rag and drop all resources exept "255" resource from
"anyname_you_want.dll" to "empty.dll"
5;save this empty.dll filled with resources of "anyname_you_want.dll",
as the name of your tagert xxxx.mui
6:Close all windows of resotrator.
7;try to sign on that mui, you may able to sign on that!
Good luck
Thank you for your instruction about PB and html.
however, I still cannot save modified file even though I put file name with *.exe or *.dll.
As my test, I opened x86 file and modified its file and I can save the modified. But still cannot tapres and tshres.......
I also tried some WM5 files, but not succeeded in saving it...orz
I installed all PB functions but for MIPS or SH4, which should not necessary for WM5.
The attaced is the error massage appreared when I wanted to save modifed WM file. (I installed Japanese PB, so error message is in Japanese)
"ta.dll" is only a temporary name for modified tapres.
I appresitate your any comments.
Thank you.
shugoh
I did it!!
Asukal:
I finally can make localized tapres and tsh with your recommended tools!!
Please see my blog at your convenience!
I'll try to localize folders with init*.dat files!!
Thank you very much!!
(If I have difficulties on making init*.dat files, I may ask you suggestions after I make every effort I can make,)
Thanks again
shugoh
Hi, Asukal
I can localize init*.dat file according to your post on May-15.
As you said, it seems OK that we can describe folder names on both *.dat file, not Unicode Code #.
So far I have no trouble with these *.dat files.
Thank you.
shugoh
Glad to here that!
You have done! you r a MAN!
Keep on going Dark Side!
Hello, Asukal
I'm back...
I have had a strange problem. As a matter of fact, I haven't solved this problem even though I could make Universal ROM in my language.
When I make my Universal hard & soft reset, I always see 2 white bold lines above and below "Windows Mobile" on 2nd splash screen.
I found these lines don't appear when I change mui regional setting. I mean no white lines on 2nd splash when I change:
1) shellres.dll.0411.mui to shellres.dll.0409.mui
2) shellresapps.dll.0411.mui to shellresapps.dll.0409.mui
(I'm trying to change English ROM to Japanese.)
0411 and 0409 have exactly same contents; I just change their name and place them on "windows" folder.
3) Change mui setting both of the following from 411 to 409.
[HKEY_LOCAL_MACHINE\MUI]
"SysLang"=dword:00000411
[HKEY_CURRENT_USER\MUI]
"CurLang"=dword:411
With these changes, I can boot my Universal without white lines and Uni seems working well. (Of course, all letters except for the ones in these 2 mui are in English. But I suppose I can see Japanese if I change all 0411.mui to 0409.mui. (Haven't tested)
I also noticed I didn't change the region code in init*.dat. (i.e. LOC_0409_DIRWINDOWSHELP, not LOC_0411_DIRWINDOWSHELP)
So I changed init*.dat files and made new ROM with 0411.mui (incl. shellres & shellresapps).
However, there were still 2 white bold lines on 2nd splash...
I haven't added:
[HKEY_LOCAL_MACHINE\Security\ColdInit]
"Locale"=dword:00000411
"ColdInit2Done"=dword:00000001
"ColdInit1Done"=dword:00000001
Because my Uni has always stuck before the initial setup (screen alignment and Dr. Johnson etc.).
This time, I added these keys per your instruction, but I'm stuck again...
Do I have to add [HKEY_LOCAL_MACHINE\Security\ColdInit] ?
This would not directly relate to my experience, but I think I can find where I made mistakes.
I appreciate your response.
Thank you.
on my rom, i changed
LOC_0409_DIRWINDOWSHELP, to LOC_0411_DIRWINDOWSHELP
also i added folows
HKEY_LOCAL_MACHINE\Security\ColdInit]
but i dont think those are not reason of your problem,
did you tried to edit new one from versin nbf??
i guees the ROM was crashed,,, i never happend,
you think some reason of registry,,,
how about htis,,,
[HKEY_LOCAL_MACHINE\ControlPanel\Stylus\192DPI]
"FontArray"="500,600,900,1000,1200"
"CurFont"=dword:384
this is the for Screen resolution.
But in my case,,without this,, not happend problems like you,,,,
strange,,,,
Hi, Asukal:
I finally find the root cause of 2 bold lines on welcomehead screen!
the mui file taking charge of screen alignment on start-up set-up process causes this problem. I made the new one with PB and solved this problem!!
(I made the previous one with another tool...)
I'm very glad to inform you this and appreciate your supports very much!!!
P.S. However, I'm still stuck with Coldinit... But this is not an issue.

HELP Translating Apps Tutorial

I've seen that many apps comes with AppName.0409.mui installed in the same folder of the app, usually \Windows.
For who don't have an english OS, usually miss app dialog box string.
I've seen that if u want to have back dialog box string u have to make a copy of AppName.0409.mui and reneme it into AppName.xxxx.mui where xxxx is your contry code (for me, italian, 0410).
But how to have dialog box string in native language?
I've tried with a recent app extracted from touch dual (Action Screen) which have a mui file with only one string. I've used Resource Hack, changed the string, compiled and saved. But... nothing.
In second instance i've changed not only the string but also the language code, compiled, saved and...
So can someone who is skilled make a tutorial for changing app strings?
Sorry for my bad english and thanks in advance for reply.
P.S.: i've read this http://forum.xda-developers.com/showthread.php?t=311078 and also this http://forum.xda-developers.com/showthread.php?t=307968 but talking about rom, not apps...
I do it like this:
1. Copy the program's executable file to pc.
2. Open the exe with Resource Tuner. I delete all other folders exept Menu, Dialog and String(in these are all the strings for translation) and save the file.
3. Then I open it with resource hacker and push action -> save all recources
4. I open the generated rc file with notepad and replace all the:
LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US(or maybe this is another language)
lines to:
LANGUAGE LANG_GREEK, 0x1 (this is for greek language)
and save the file.
5. After that I open the rc file again, but now with resource builder and I push tools -> Create resource-only dll and I save the file as name_of_file.exe.0408.mui(for greek).
6. Finally I open this file with resource hacker and I translate it
I used to do it in this way cause I have all these three progrs(resource hacker, resource tuner and resource builder)
Maybe there are other progs or ways but this works fine for me until now. If someone knows easier and faster methods I also want to know.
First, thanks for reply.
I was trying to make an easier thing... but maybe i can try this way for my scope.
I've installed HTC Action Screen, you can found it at: http://forum.xda-developers.com/showthread.php?t=336587
It's a cool launcher, nothing more. After installation i can find in \Windows folder two files:
HTCActionScreen.exe
HTCActionScreen.exe.0409.mui
Well in the mui there's only one string that is the top of the launcher screen, that i don't see. I've renamed 0409 into 0410 and now i see the string, the original one in english (some like that "Dial phone number or select a task below:").
I'd like to change in italian, so, i've used resource hacker ONLY for translate the string (as in your 6.) but... i don't see anything once again!!!
Any suggestion?
Have i to start from exe as in your reply?
Thanks again.
This is happens because you cannot change the LANGUAGE line with resource hacker. For this I save the resources in a rc file and adit it with notepad. I had similar problems with some muis that cannot translated before use the method that I described above. You only need resource builder to recompile the rc file to mui again. I don't now in what must change the Language line for Italian, but I think you can find out if you open an italian mui file.
So, i describe my step:
1) open HTCActionScreen.exe.0409.mui with Resource Hacker and and push action -> save all recources
2) open the .rc just created with notepad and changed LANGUAGE LANG_ENGLISH, SUBLANG_ENGLISH_US into LANGUAGE LANG_ITALIAN, SUBLANG_ITALIAN
3) open this .rc with resource builder and push tools -> Create resource-only dll and I save the file as HTCActionScreen.exe.0410.mui
4) open this file with resource hacker and translate it
it doesn't work
Where's my fault?
Maybe have i to sign the file?

suggest word(s)

hi
I am sorry if this has been asked before (but I did search)
Is there any way to add suggest word(s) when typing in text, I have to type the same sentence over and over again every day and on my old phones/PDA this was not to bad as you could set the suggest word(s) to give you the next 4 works, I can't find this in the HD2 is there any way to add it
Thanks for any help
according to hint 19 in this thread:
19. Improve Suggested T9 Dictionary With Custom Words
The Leo has a very useful hidden application in the Windows directory. You need to unhide hidden system and Rom files in order to find it. Find the file "eT9MyWords.exe" in the Windows directory and add a shortcut to this file in your Windows/Start Menu folder.
When in the application, add the most common words you use when using the keypad such as names, locations, user names, email addresses and other words not common in the standard T9 dictionary. For example if you are based in London, UK you could add the following locations:
Leicester, Piccadilly, Tottenham, Soho, Charring, Euston, Trafalgar, Clapham,
and words such as BRB, DVD, coz, lol, xoxo, [email protected], ciao, etc.
Click to expand...
Click to collapse
I have read these tips and know about adding custom words.
What I want is for three to four words to come up to complete a sentence.
This has been in the input tap on old PDAs suggest word(s)
Hi
Is there no one Who can help with this?
Really with all the clever people on this site can no one help me
Please someone help me
Hi, i did a few tests and found...
et9mywords wont accept spaces, and although you can sneakily paste sentences into the input box, it wont save them, so that method is out.
Custom words are also found in HTCMDB.txt, and the good news is it works!
(See image)
The line 'this is a test' i hard coded into the file using my kitchen, then the 'this is a second test' i added as follows....
(I use resco explorer, i suspect the normal file manager wont do what is required, total commander probably will)
find /windows/HTCMDB.txt (it will be hidden, so show all files)
copy it to your sd card, and from there to your desktop.
(I tried editing it on the phone using windows mobile notepad, but it didnt work right)
On the PC, right click the file, properties, and untick 'read only', apply.
Open it and edit it as required.
Save it, and again right click, re apply 'read only'
Copy back to your sd card, and from teh phone use commander or resco to move it to /windows/
You will probably get a warning about rom files and what not, thats ok.
Reboot, and you should now be able to see your sentences.
PLease let me know how you get on.
EDIT - just for clarity, every entry inside HTCMDB.txt must be on its own line.
thanks for your help with this I have done as you posted and it works, it's a bit long winded but it works
thanks jason

[GUIDE] Rom Translation Tutorial, Translate Roms and Apps on your own!

THIS GUIDE IS FOR PEOPLE THAT KNOW WHAT ARE DOING! DO NOT TELL ME THAT I BRICKED YOUR PHONE OR STUFF LIKE THAT, YOU ARE RESPONSIBLE OF WHAT HAPPENS TO YOUR PHONE, BE CAREFUL!
I wrote this guide studying the system of Motorola Droid 3, but it is good for nearly every phone, (or single application!!), maybe with advent of android 4.X this is becoming useless, because usually every rom has already all languages into it, but you could use this even for correcting translations, or translate yourself some application
If you want the Italian versions of Minimoto 1.7 and MavROM 4.5 go to this thread: http://forum.xda-developers.com/showthread.php?p=47857497#post47857497
Every Droid 3 owner out of the English/Spanish area knows that every D3 ROM comes out with only two languages preloaded in it, right? well...if you know well english (or spanish!) maybe i have something for you!
Ok, i hope this guide could be helpful to everyone like me that wanted to find a non-english, non-spanish Gingerbread ROM for Droid 3.
After some studies, and a lot of searching too, i've found the best (i think) way to translate roms. Oh and this guide is good for every android phone out there! Let's start!
Part 1 - Download all the stuff! (plays Monkey Island music )
Our needs are very few, what you need with this is a lot of patience, and knowing some english could help.
- A rooted Droid 3 (or any other phone)
- The ROM you want to translate
- WinRAR / 7-Zip
- Notepad / Notepad++ (Highly recommended!!!) http://notepad-plus-plus.org/
- Java Development Kit www.java.com
- APK Manager/APK Multi-Tool, since now i will call them APKM and APKMT ( i used APK Manager, but multi-tool should be fine anyway) http://apkmultitool.com/?q=node/5
- Google Translator Toolkit http://translate.google.com/toolkit/
- Safestrap (optional, but very, very recommended)
- MoreLocale2 or another language changing program
Note 1: If APK Manager/Multi-Tool bother you with something about java not found do this: http://wiki.answers.com/Q/How_do_you_stop_the_error_%27java%27_is_not_recognized_as_an_internal_or_external_command_operable_program_or_batch_file
Note 2: In APKMT, the commands are a little different from APKM, e.g. in APKM the "set project" command is listed as 22 and in APKMT is listed as 24....the functions we'll use are the same, just read the description if you're not sure and you'll be fine
Ok, let's take the stuff out of the box!
Part 2 - The extraction point
Open the .zip containing your ROM's files with WinRAR / 7-Zip and extract the folder "system" somewhere (i recommend to create a folder for your translation project) once the process is done, we can basically do two things: Decompile the apps or decompile the frameworks, the process is the same, but you have to go really really REALLY careful with framework apks, or once you flashed the ROM what you've got is a translated BOOTLOOP. So be careful. With apps you can mostly screw a functionality up, like SMS or Phone, but nothing too messy.
Anyway you can solve the problem with a new flash with the corrected ROM, or the original, untranslated ROM.
Ok let's start with the frameworks: we've usually got 3 differents frameworks and those are
framework-res.apk
blur-res.apk
moto-res.apk
Those apks contain mainly everything written all around the phone, like pop-up messages, status bar, app permissions and a lot of other stuff.
We'll use framework-res.apk.
If there isn't, create a folder in the same folder where you have installed APKM/APKMT, called "place-apk-here-for-modding" without quotes, then copy inside it the framework-res.apk.
Now you have to open the Script.bat file, and once you get into the main window, digit 22 (APKM) or 24 (APKMT) and press enter to select the current project, now digit the number corresponding to the desired apk (it should be 1 if you have only framework-res.apk) and press enter. now digit 9 (APKM/APKMT) and enter and you'll decompile the apk. Now you should have a folder, inside the "projects" folder of APKM/APKMT named just as the decompiled apk. Inside it, you'll find a folder called "res" open it and you'll be right into the core of the translation:
Note: if you get an error after decompiling, try with option 10 (APKM/APKMT), and drag and drop the necessary framework over the prompt when APKM/APKMT ask, press a key, and if you get another error try with another framework (D3 has 3 of them) until you get the job done. If nothing works, probably there's a problem with the apk you want to decompile.
Note 2: You could need to have frameworks installed into folder C:\Users\YourPCUSername\apktool\framework. You can do this either with apktool via cmd or manually copying the 3 frameworks into this folder (create it if needed) and renaming them this way:
- framework-res.apk => 1.apk
- moto-res.apk => 2.apk
- blur-res.apk => 3.apk
Then you should be able to decompile 99% of apks with option 9.
You'll find a bunch of folder, but we are interested in the "values" ones, if you have to translate the app, you'll see something like this:
- values
- values-es
- values-es-rUS
the first folder contains the english files, the second contains the spanish files, and the third contains some other files for spanish variants.
Open the "values" folder and inside it there are some .xml files, we will always use only 3 of those at most:
- strings.xml (the file containing mainly all the text strings of the apk, if you find this, then you have to translate it, if not, just pass over this apk, it doesn't contain text)
- arrays.xml (the file that contains some text data for drop lists, you'll not find this often, but if you find it, translate it)
- plurals.xml (the file that contains plural words, this is very rare to find, but if you want to make good translations, then, translate!!)
Now get back to "res" and create a folder called "values-xx" where xx is your language code, for example i made a values-it folder, but you'll write values-fr, values-de, values-idunno etc.
You'll put here, all the XMLs we're gonna translate now!
Part 3 - Bring out the dictionary!
The game is getting harder, now you have to use your better weapon: Google Translation Toolkit. But first, let's look into XML!
Open the "strings.xml" file with Notepad++, and look at the records structure:
<string name="aerr_application">The application %1$s (process %2$s) has stopped unexpectedly. Please try again.</string>
You have to change ONLY and i repeat ONLY the text between "<string name="aerr_application">" and "</string>"!
Now some rules:
- See that "%1$s" weirdness? that is a jolly word that Android replace with a variable data, in other words DO NOT TOUCH IT! just imagine that you'll see there something like "The application *Temple Run* (process XYZ) has stopped etc. etc.
- If you have to put an apostrophe or some other weird character, always put quotes at the beginning and at the end of the string just like in the translated string down there, it's good to always put them, And GTT (Google Translator Toolkit) does that.
- If the string you have to translate looks like code stuff, probably you should leave it untranslated, something like:
<item>@string/resolutionSummaryWideScreenTV</item>
<item>MOTOCAMSETTING_REVIEW_TIME_4_SEC</item>
see? DON'T TOUCH IT! BAD TRANSLATOR! BAD!
This is the resulting, translated string:
<string name="aerr_application">"L'applicazione %1$s (processo %2$s ) si è fermato in modo imprevisto. Si prega di riprovare."</string>
Ok, now we can translate without detonating the phone, but framework-res has something like 1300 rows of text!
WHOA! let's use GTT!! http://translate.google.com/toolkit/
Once you are on the main screen of the tool, click on the red "Upload" button on the upper left, then in the page you found after, click on "Browse..." and select your file inside your PC.
Set all the stuff down there, like the name, the language and everything else, and click "Upload for translation"...here comes the magic...
The XML is translated! sort of...
You now have to look if GTT has done the work well...let's look into this page:
- You can see that now the entries are divided in boxes, you can click onto the left panes' boxes and edit the content.
- Play a little with the interface, you have to get familiar with it if you want to translate a ROM!
- Look to spaces and returns, GTT mess them, and you should correct the format.
- Text is coloured: i'll tell you what those fancy colours ACTUALLY mean
- Orange: this means you've edited the text into the box
- Red: text coloured in red came right out of Google Translate, and 70% of times, it will be gibberish, so look carefully into it, this will be the work where you'll spend more time.
- Blue: this is a sneaky bastard, it says that he found a "100% matching" translation in his database, but it has a 30% chance to be total nonsense, be careful with it.
- Green: this colour is fine, you probably have translated this in past, or someone did it for you, anyway, it will be 99% correct, if the past translation was correct.
- Brown: this happens rarely, usually where it founds a colon (the symbol ":" ok?? :angel: ) and for some reason, it goes random, usually you need a very little effort to correct it.
- Purple: THIS is a funny one. when purple comes out (usually with a wildcard character like "%1$s") the translator often goes TOTALLY random and write some idiocy. rewrite the text from scratch.
Once you've managed to translate everything, and if you're sure to have completed everything, click (if you want) on "Complete" in the upper right corner of the page, and then we need to download our work, to do that, click on "File" (upper left) and then "Download". Save the .xml file in your values-xx folder, and check one last time with Notepad++ the number of lines, the spaces and the format in general, at this point we're ready for the final part!
Part 4 - Repack everything!
Now the situation is this: you have the "project" folder containing all the decompiled apks folders, with the "values-xx" directory in it, we now have to recompile everything and put apks into the ROM. Let's see how:
- Open APKM/APKMT and select the project you want to recompile
- digit 11(APKM/APKMT)
- Look if you got errors, if yes, look into the log 20(APKM) or 23(APKMT) and see what the problem is, if you look carefully you will identify where is your error log, probably it's a messed tag, or something easy to resolve, correct the issue, and go ahead, restarting from digiting 11 (Compile)
- Press Y and enter
- Press Y and enter (yes, 2 times)
- Now wait for APKM/APKMT to stop spitting lines out and it'll tell you something. Read it, but the substance is: go in the APKM/APKMT folder, look for a "keep" directory, delete the "resource.arsc" file, get back on the APKM/APKMT prompt window, and press a key.
- Once everything is completed, you now have a file called unsignedframework-res.apk (or unsigned*nameoftheapkyouhavecompiled*.apk)
- The next, is the point i still didn't get, but it works...maybe XDA guys can explain better this...anyway, we now have to sign apks...i saw that this shouldn't be necessary, but otherwise i've got a lot of errors and force closes and stuff like that...soooo, at least for D3, sign it!
- We have 2 choice for signing...if you have only a few apks to decompile, you can just select the project and digit 12(APKM) or 13(APKMT) and sign it but if you have translated a whole ROM and you want to sign all the apks at once, create, if not exists, a folder called "place-apk-here-for-signing" and put all the unsigned apks there...you now have to digit 16(APKM) or 18(APKMT) and the apks will all be signed automatically.
- Rename the apks removing the "signed" part from the name.
We're now ready to pack the ROM: i usually create a "system" folder somewhere else that i will put directly into the ROM's zip, but you can do it by hand (boring). I'll show you my method for now:
- create a "system" directory
- inside it, create a "framework" and an "app" folder
- put into the framework one, all the frameworks (easy, huh?) and into the app directory, put all the other apks.
- open the ROM zip and drag and drop the system folder into the ROM in order to overwrite the existing one.
Our freshly translated ROM is ready to be flashed and brick or burn your phone! (ok, no, this is not true...maybe...)
Anyway, download the zip on your phone and flash it with the recovery you want.
I RECOMMEND TO DO THE FIRST TEST ON A SAFESTRAP, AND ONLY IF YOU'RE SURE THE ROM IS SAFE, INSTALL IT ONTO YOUR MAIN SLOT! I'VE WARNED YOU!
Part 5 - Polish your creation!
When the ROM is installed, and if it boot correctly, First install MoreLocale2 or other similar apps, and add, your language, with the correct ISO codes and look around to see if something is untranslated...if yes, go back, to APKM/APKMT and find the apk you need to modify, translate, repack, flash the ROM and again until you've got a perfectly translated ROM!
The tutorial is ended, i hope you liked it, and if you want to correct, critic, ask, or anything, just tell me!
Tips: If you want to avoid the MoreLocale stuff, you can edit the build.prop, into the folder "system" of the ROM you'll find this file, open it with Notepad++ and look for these lines:
ro.product.locale.language=xx
ro.product.locale.region=YY
You have to put here your ISO language code, but i noticed that on D3 it doesn't always works...so, try but i don't guarantee success.
If i remember something, i'll integrate the post
Coming Soon:
Screenshots!
Corrections!
Test reply (i can't see the thread in the forum) It's fine now

(Q) mapping hardware keyboard, polish layout

Hello everyone
I am trying to acheive the right method for mapping hardware keyboard. Usb host works perfectly, always does what it should on firmware 1.21 with nook manager, kernel version 176. I found some polish keychar kcm file on the net, then I renamed that file with right vendor and product id for my keyboard (terminal, keyboard connected in host mode, typed: lsusb) and placed it in system/usr/keychars... But that didn't make any effect on keyboard mapping, looks like that file is ignored. I could try to edit qwerty.kl in system/usr/keylayouts but from what I know, you cant add there symbols like "ą" or "ś". What I am going for is just these few polish letters : Ą,Ę,Ś,Ó,Ż,Ź. Normally you get them by pressing modifier (alt) and for example, " A", what gives you "Ą" etc. Usb mode ultilty, and little app avaible on net - Key Test, both will show you the same keycode when you pressing a letter or letter+modifier. That makes hard to find out how to edit keylayout file (qwerty.kl) as you cant guess that needed keycode. I was looking quite a lot for answers on xda before I decided to ask, but what I finds does'nt look like exact sollutions. Hopefully I didn't miss anything. Adb is working fine for me, any hints appreciated, Thanks
Step one, determine what .kl and kcm.bin the Nook is trying to load.
You will see this if you have ADB and logcat running when you connect.
It will try to load one based on the VID/PID.
It will tell you the exact name of the file.
Probably your naming is different.
I ran into this already.
I didn't bother, I just use qwerty.kl and qwerty.kcm.bin
These are the defaults when there is no VID/PID specific files.
If your kcm.bin is correct it should have the UTF-16 values inside.
The format is pretty simple. After the header (32 bytes) it's like:
Code:
{
uint32 keycode;
uint16 label;
uint16 keypad;
uint16 normal;
uint16 shifted;
uint16 alt;
uint16 altshifted;
}
You can just enter the little-endian UTF-16 values using a hex editor.
Ok I got it! It is easy to find some proper tutorials for hex editing qwerty.kcm. But before I did that effort and started learning about it, I searched for some very lazy sollution: qwerty.kcm.bin already prepared by someone else. I found one (obviosly with polish layout),I swapped the original file with it, set the permissions to be the same as in original file, reboot (don't know if absolutely necessary)... thats it, easy. All that thanks to some hard working man who (as he has mentioned on other forum) spent the whole night learning on how to edit qwerty.kcm in hex editor.
Anyway, thank you very much for directing me in the right way. Knowing which files should be edited helped me to resolve the problem. Also logcat is very interesting tool, as it might give some image of how the system works. Thanks
hi, I have the same problem but i can't find the qwerty.kcm.bin with polish letters. Could you provide the file ??
bartbrudz said:
hi, I have the same problem but i can't find the qwerty.kcm.bin with polish letters. Could you provide the file ??
Click to expand...
Click to collapse
Hi, I'll try to copy it from my nook directory, once I have some time.
hi, here is my whole keychars folder (/system/usr/keychars). You can make a backup of your keychars forder and then overwrite it with mine. You can let me know if it works for you. Find attachment below. Powodzonka.
Awesome!!! works perfectly. :victory: Thank U !!!
bartbrudz said:
Awesome!!! works perfectly. :victory: Thank U !!!
Click to expand...
Click to collapse
cool, I am glad I could help! : ) (although real credits goes to someone who created this qwerty.kcm file)

Categories

Resources