Customized Finnish/Swedish keyboard layout and character maps for Xperia X1
WARNING!: If these keymaps don't work for you for some reason or if you miss some steps by accident, then your keyboard might no longer work. Make backups and preferably have a SDCard reader close by and a way to modify files on ext2-partitions. Proceed at your own risk; no guarantees whatsoever.
I've attached to this post some customized Finnish/Swedish keyboard layout and character maps for use with Android. These have only been tested with CyanogenMod 6.0 build from neopeek with seandean's v4b "advanced" kernel.
These maps enable åäö and other characters printed on the "FISE" physical keyboard. In addition there are some extra bindings that make life in e.g. a ConnectBot terminal hopefully a bit easier. Not all Android's terminal apps support the Scandinavian characters.
Extra bindings:
(Fn means the blue key on the bottom left of the keyboard. Shift+Fn means that both of those modifier keys must be pressed at the same time.)
Key = character, character w/ shift, character w/ Fn, character w/ shift+Fn
Win = Camera (Useful as ESC in ConnectBot)
Sym = DPad Center (Useful as CTRL in ConnectBot)
àü = Search
e = e, E, &, €
r = r, R, /
y = y, Y, ), ¥
p = p, p, ?, Delete
a = a, A, \
s = s, S, $, §
d = d, D, [, {
f = f, F, ], }
g = g, G, ', "
h = h, H, -, _
l = l, L, 6, £
@ = @, |, <
z = z, Z, >
x = x, X, %
c = c, C, ~
v = v, V, ^
.; = ,, ;, *, `
.: = ., :, 0, ´
The € symbol doesn't show up for me in ConnectBot, but works in e.g. Browser. Some terminals seem to accept Fn+Space as ^A but this hasn't really been tested.
Backup your /init.etc/keymaps/kovsky-qwerty.kl and /init.etc/keymaps/kovsky-qwerty.kcm.bin files and place the included replacements to /init.etc/keymaps on your root partition overwriting the existing files. Reboot the device. Note that there might be some caching, but rebooting should take care of it. QWERTY-layout (kernel parameter "physkeyboard=kovsq") should be selected in most builds inside HaRET's STARTUP.TXT by default, but double check if you have problems.
BTW: http://code.google.com/p/scandinavian-keyboard/ is a nice replacement for the on-screen software keyboard, but there are alternatives.
Häv fun!
I would like to get this working but I haven't found a way to edit data.img where the files are found. Any tips?
cage85 said:
I would like to get this working but I haven't found a way to edit data.img where the files are found. Any tips?
Click to expand...
Click to collapse
On windows I use a combination of Ext2 IFS
and ImDisk.
Install both of these and you can mount and unmount data.img, rootfs.img etc by
right-clicking the files.
They will appear as normal disks in explorer. You should use a text editor that is compatible with unix line-endings.
A german keyboard layout (with ß,ä,ö,ü) would be nice. Can you tell me how to adopt this files for german language. The kovsky-qwerty.kl can be edited, but how can the kovsky-qwerty.kcm.bin be edited?
Does anybody have an idea how to write to an ext2 partition in windows when there are several primary partitions on the same drive as in the case with Android?
Related
hello
i patched my ba several times but yesterday i got the failure message country code wrong.
i run getdivicedata and get this info:
P H 2 0 B W W E AT%CID? 5 . 0 3 . 0 2 0.0 1.13.00 % 4
how can i "repair/fix" my operator code
thanx
Your operator is 'T%CID?'
It is fine - same as mine
This proceedure is all over the forum.
This is what I do:
1) create a new file on ur desktop C drive - call it ROM
2) copy and paste NK.nbf and setoperator files to this new file
3) start - run - type 'cmd' - ok
4) type 'cd\'
5) type 'cd rom\'
6) type 'setoperator T%CID?' - enter
7) your NK.nbf file is now changed to your operator code
8) copy and paste NK.nbf back to your file
9) and flash your ROM using BaUpgradeUt
to flash your ROM:
1) press softrest+pwr+record button at the same time
2) you will see a white screen on your BA with 'SERIAL' letters on top
3) put BA in cradle and allow few seconds for the computer to pair with it
4) run BaUpgradeUt to flash your ROM
Should work
No dude, its not your operator code thats gone wrong...How did you set the operator in the first place? if you used the setoperator, did you enter the 8 digit alpha numeric code, ie. T-MOB001 or XGULA001 or whatever ur code is?
Well, what i would suggest is that you open the Setoperator.bat file using Notepad, make sure it is for you device and language. Then change the operator code using the normal procedure.
Now, use xda3nbftool to check that the values have been set correctly (hint: see how the commands display in DOS when you do the setoperator procedure)
Hopefuly this might help! Good Luck!
Yaantra
all my device data became scrambled during a rom update once, i just reflashed again, using the no_id tool and it went back to normal.
http://discussion.treocentral.com/showthread.php?p=1221514#post1221514
CTRL key is very important for all keyboard based devices, not just copy/paste/cut/select all. There is no CTRL key in treo 750, EVIL Palm, screwed us again.
Fortunately it is no so difficult to add the CTRL key.
Installation: Please download the attachment and install the cab file. Reset your device. After reboot, You will find an indicator (blue) in Start, which is CTRL key.
Clicking CTRL Key. It is easy, just click the option key three times. You will notice the indicator turns into RED, which means the CTRL Key is ON, you can then click A, which will be "ctrl + a" (select all).
Copy: Ctrl +C
Paste: Ctrl +v
Cut: Ctrl + x
Select ALL: Ctrl +A
The original program is written by GSH and called PQZII. I stripped it and repacked. You can find more information here: http://www.nicque.com/PQz/PQzII.htm
For advanced user, I encourage you go to download the full version, which has much more features, such as:
System: close, close all, restart, suspend (ctrl + some char you like)
Setting: all settings applet using ctrl + char
Programs: any programs using ctrl + char, now you can use your keyboard to launch programs
Power words: your most frequently used sentence can be saved and retrieved by ctrl + char
For Chinese/korean/Japanese users, this program can also switch your input method with one key combination.
Good luck.
New Ctrl Key Pro with more features
http://discussion.treocentral.com/showpost.php?p=1224511&postcount=110
this may be a lame-o question, but...
i tried expanding Ctrl Key Cab.zip, and StuffIt Expander (Mac) gave me an error message, saying: "An error occurred attempting to expand 'Cellneuron_GSH Ctrl Key.4.cab'. Format error. Error #17540"
Any suggestions?
Thanks!
atavacron said:
this may be a lame-o question, but...
i tried expanding Ctrl Key Cab.zip, and StuffIt Expander (Mac) gave me an error message, saying: "An error occurred attempting to expand 'Cellneuron_GSH Ctrl Key.4.cab'. Format error. Error #17540"
Any suggestions?
Thanks!
Click to expand...
Click to collapse
You need copy the cab to your ppc to install.
CRTL KEY did not work for my Xperia 1
ah.... I am still in need of a CRTL KEY on the physical keyboard ... heeeelp
bhardjono said:
ah.... I am still in need of a CRTL KEY on the physical keyboard ... heeeelp
Click to expand...
Click to collapse
for Xperia X1, you can use X1BC (X1 Button Controller)
This is the bug fixed version of the “v4a” kernel that should work for all Android distributions for Kovsky (Xperia X1).
Change log:
+ Upgraded to GIT commit e83e7c3fccf8423bd0cf489f852f830ca6e80259
+ Kernel debugging and certain associated options for OS compatibility
Release Notes:
I’m providing two versions of “v4b” for regular and advanced users. At this time the only difference is the keyboard and buttons driver either being build inside the kernel (regular version) or outside in the modules (advanced version). In future versions there may be additional differences, but they will be detailed in my release notes.
Keyboard and buttons modules HOW-TO has been explained in other threads, if you’re thinking to yourself that you have no idea what I’m talking about I suggest sticking to the “regular version”.
Known Issues:
You will require the November 29 3D driver found at this thread: http://forum.xda-developers.com/showthread.php?t=852937. If you don’t install this your device will function completely normal outside of 3D games and applications. IMPORTANT NOTE: don’t install the gralloc driver as it will cause the screen driver to eventually lockup (otherwise known as SoD).
The camera has been fixed in the kernel source code, but the libraries in Android have no support for it. It’s not an easy fix, and it’s not going to be fixed anytime soon so support has not been built into the kernel.
Keyboard and buttons will eventually fail, this isn’t new but using a method posted in this forum for reloading the drivers (advanced version only) works!
The battery driver is very accurate up until about 50% left being reported in Android. After which it becomes somewhat unstable, reports incorrectly and may force shutdown (softly) your device. My best suggestion; consider 40-50% left as 0.
Smart feedback is appreciated.
thanks alot i will tested and back with feedback soon
are android camera libraries particular to each device or can we use libraries from other devices?
Here is the guide for advanced kernel, which allows you to wake keyboard with 1 click instead of rebooting the device. Guide is for freshly installed android (so no just updating the kernel).
1. Extract autostart.sh from the included archive and place it to your SD card
2. Install android like normal.
Until step 9, keys won't work, except for camera and power button. If you screw up, press camera button to return to the home screen.
3. If you don't have it in your release, install "Terminal Emulator" from market
4. Launch "Terminal Emulator". Soft keyboard should pop up.
5. Type "su" (everything without quotes from now on). Press enter. Symbol on the left should change to #.
6. Type "mkdir /data/opt" and press Enter.
7. Type "mv /sdcard/autostart.sh /data/opt" and press Enter.
8. Type "chmod 777 /data/opt/autostart.sh" and press Enter.
9. Type "sh /data/opt/autostart.sh" and press Enter. Software keyboard should disappear now and keys should be working.
10. Go into the market and search for "Autostart (Root)". Install that application
From here, your android is working. If you wish to add 1-click keypad fix, then continue reading, otherwise you can close this page.
11. Install application "GScript Lite" from market.
12. Open GScript Lite.
13. Press left softkey (menu) and select "Add Script".
14. Type any name, like "Fix Keyboard".
15. Tick "Needs SU?" and press "Load File".
16. Type this into bottom window:
Code:
#!/bin/sh
rmmod microp-keypad
rmmod microp-ksc
insmod /lib/modules/microp-ksc.ko
insmod /lib/modules/microp-keypad.ko
17. Press save.
18. Return to the homescreen
19. Hold your thumb to get "Add to home screen" menu.
20. Select Shortcuts --> GScript Lite --> Script that you just created.
And now, each time your keyboard or front keys stops working, simply press camera key and tap on that icon you've just created
P.S.: this is not my work, i have just adapted what users seandean and yaana created. All credits go to them.
For the kernel, first impressions are OK. Testing with release "Only T E S T E R S [New CM6.0 Full + Barebone][29-11-2010]" release + nov29 3D driver. Artefacts still present when turning device on. I will report more after testing it out a bit more.
Camera Libraries
CowMix said:
are android camera libraries particular to each device or can we use libraries from other devices?
Click to expand...
Click to collapse
HTC Touch Diamond Camera library is pefect.
http://gitorious.org/~jbruneaux/linux-on-qualcomm-s-msm/linux-msm-home-work
http://www.youtube.com/watch?v=vhz0sPjT2UA
Im testing it now on CM6.1 Barebone with 3D drivers and autostart.sh
Wifi works
GSM works
fps2d: 28FPS
Neocore-no sound: not tested
Camera is not working
3G works
Bluetooth not tested
GPS works
Notification leds work with charge state (when start android attached charger)
i cant use this kernel..
when run haret, it comes error and then boot to WM back..
it said "can't mount fs......"
help me..
is it something wrong??
im using CM6.1
are you using windows 7 OR vista ?
if use this OS , you need to remove SD card and use card reader then recopy the kernel files , use v4b advnaced with autostart.sh
regards
im using ubuntu 10 and win xp..
i try to port it same as i port the other kernel..
but the other kernel work and not getting error when running haret,but with this one i got error..
thanks for quick reply..
matejdro said:
Here is the guide for advanced kernel, which allows you to wake keyboard with 1 click instead of rebooting the device. Guide is for freshly installed android (so no just updating the kernel).
1. Extract autostart.sh from the included archive and place it to your SD card
2. Install android like normal.
Until step 9, keys won't work, except for camera and power button. If you screw up, press camera button to return to the home screen.
3. If you don't have it in your release, install "Terminal Emulator" from market
4. Launch "Terminal Emulator". Soft keyboard should pop up.
5. Type "su" (everything without quotes from now on). Press enter. Symbol on the left should change to #.
6. Type "mkdir /data/opt" and press Enter.
7. Type "mv /sdcard/autostart.sh /data/opt" and press Enter.
8. Type "chmod 777 /data/opt/autostart.sh" and press Enter.
9. Type "sh /data/opt/autostart.sh" and press Enter. Software keyboard should disappear now and keys should be working.
10. Go into the market and search for "Autostart (Root)". Install that application
From here, your android is working. If you wish to add 1-click keypad fix, then continue reading, otherwise you can close this page.
11. Install application "GScript Lite" from market.
12. Open GScript Lite.
13. Press left softkey (menu) and select "Add Script".
14. Type any name, like "Fix Keyboard".
15. Tick "Needs SU?" and press "Load File".
16. Type this into bottom window:
Code:
#!/bin/sh
rmmod microp-keypad
rmmod microp-ksc
insmod /lib/modules/microp-ksc.ko
insmod /lib/modules/microp-keypad.ko
17. Press save.
18. Return to the homescreen
19. Hold your thumb to get "Add to home screen" menu.
20. Select Shortcuts --> GScript Lite --> Script that you just created.
And now, each time your keyboard or front keys stops working, simply press camera key and tap on that icon you've just created
P.S.: this is not my work, i have just adapted what users seandean and yaana created. All credits go to them.
For the kernel, first impressions are OK. Testing with release "Only T E S T E R S [New CM6.0 Full + Barebone][29-11-2010]" release + nov29 3D driver. Artefacts still present when turning device on. I will report more after testing it out a bit more.
Click to expand...
Click to collapse
you can skip the steps 14 to 16 by downloading the attached file and pressing load file when you are in the new script page. so instead of typing all those comands you can just load this file and save it.
I have tried that, but for some reason it showed me blank screen instead of script file browser.
matejdro said:
I have tried that, but for some reason it showed me blank screen instead of script file browser.
Click to expand...
Click to collapse
it works for me most of the times but it sometimes restart the device maybe typing it out is the best way
im testing the android right now and it is a good one but i got one problem.
when i unlock my screen i got a rare screen sometimes whit green dots and sometimes whit stripes. anyone knows how to fix that?
xorium said:
im testing the android right now and it is a good one but i got one problem.
when i unlock my screen i got a rare screen sometimes whit green dots and sometimes whit stripes. anyone knows how to fix that?
Click to expand...
Click to collapse
its a known issue no it hasnt been fixed yet this problem started from v4a
kerfooly said:
its a known issue no it hasnt been fixed yet this problem started from v4a
Click to expand...
Click to collapse
okey tanks for the info
how van i connect from in android to my pc for data exchange between my sd card?
when i plug it in my computer says that i dont have the driver?
Hi!
I have been testing Android and various Kernels for a while. And I have got no good answer to a question I have. I cant get bluetooth headset to work. Cant pair them. The answer I got is that its not fixed and that it is kernel issue. Bluetooth seems to work but not to connect pheriperals.
Is there a plan for this to work or is it a thing for the future?
Its the one thing before it can actually be used for day to day work. Lotus Traveler is now released for Android so sync should work.
today i got a isseu i runned android from yesterday evening until this afternoon that my buttons dont work again. only the camera button. how can i fix this? or is it retyping the codes again?
Here working very good on CM6.1
During boot there is a line containing something like:
[KOVSKY]: is ac online == 0
or (if charger is plugged in)
[KOVSKY]: is ac online == 1
Maybe it is possible to set this parameter to be '1' at boot? So the charger would work either it is connected or not while runnig 'haret.exe'
why its not going to work for me!!!!!?????????
why it is so hard to port????
its say cannot mount partition,cannot mount fs....bla...bla...bla...
HELP ME PLEASE WITH THIS V4B KERNEL..
IM STUCK AT HARET AND THEN BOOT TO WINMO BACK..
TRYING 10000000000000 TIMES TO PORT IT..
EDIT: Attached is a zip of my current qwerty.kcm.bin and qwerty.kl files.
IMHO, my qwerty.kcm.bin should replace the current version in CM7 as it only affects external keyboards, not the soft keyboard, and every US keyboard I've ever seen has <> above ,.
Now that we have bluetooth keyboards and finally have more than 4 keys to play with, maybe it's time to address this!
/system/usr/keylayout is a directory with the key layout files. These are plaintext files.
A few things to know going in:
It is probably easiest to use adb to push the files. You need a working ADB. "adb push <local file> <remote path>" is the format.
If the keyboard layout has any unrecognized stuff in it (When I tried VOLUME_MUTE, and MUTE keycodes) it will stop loading at that point, disabling all keys after it in the keylayout file. I highly recommend adding your test stuff at the bottom of the screen unless you are using ADB to push the files.
adb shell <command> will let you launch commands remotely. If you don't put in a command, it gives you a remote shell which is both epic and awesomely useful.
To push a qwerty.kl file to the device, this may be a way for you to do it:
Code:
cd <directory with your custom keylayout>
adb shell mount -o rw,remount /system
adb push qwerty.kl /system/usr/keylayout
adb reboot
You have to remount /system to be read-write because it defaults to read only.
Here is a sample of some keylayout:
Code:
key 399 GRAVE
key 2 1
key 3 2
key 4 3
key 5 4
key 6 5
key 7 6
key 8 7
key 9 8
key 10 9
key 11 0
key 158 BACK WAKE_DROPPED
key 230 SOFT_RIGHT WAKE
key 60 MENU
Here is the code I currently put in:
Code:
key 172 HOME WAKE
key 115 MENU
key 114 BACK
key 165 VOLUME_UP WAKE_DROPPED
key 164 MEDIA_PLAY_PAUSE WAKE_DROPPED
key 163 VOLUME_DOWN WAKE_DROPPED
Best I can figure, android documents a capslock state but doesn't natively support it? Maybe only in 3.0? I have no clue, but I can't get any capslocks working. The Motorola Xoom keyboard has a caps lock, but it may be a custom app. Trying to get thier keylayout files...
MORE TO COME:
links:
lots of KEYCODEs in here to play with: http://developer.android.com/reference/android/view/KeyEvent.html#constants
I think they correlate to our keycode names, but you don't use the KEYCODE_ prefix in the keylayout file.
If I sent you the needed files and an image of a keyboard with the codes on it, is there anyway you could edit the .kcm files for me. I currently am without a computer that I can do this on and it would be a big help. If you do decide to help I will be sure to credit you for the work in the OP on Evo Desktop PC thread.
Thanks
Lokifish Marz said:
If I sent you the needed files and an image of a keyboard with the codes on it, is there anyway you could edit the .kcm files for me. I currently am without a computer that I can do this on and it would be a big help. If you do decide to help I will be sure to credit you for the work in the OP on Evo Desktop PC thread.
Thanks
Click to expand...
Click to collapse
I would be happy to. This thread is depreciated in a sense. I've been using the dev thread in my signature.
PM me the info and I'll take a look at it.
Al Credits Goes TO Perceval from Hyrule
Perceval from Hyrule said:
** Currently writing this, please wait !
Hello there,
here is a new tutorial I'm sure you'll like. As usual it took me LOTS of work to get all info and make this to work, so now I share it with you and show how to run custom ROMs within Android SDK Emulator.
Please note it's mainly for XPERIA X10, but process is the same for other Android-powered devices. It will show you the process for Linux.
1. Download the latest Android SDK.
2. Open the archive, and copy the folder android-sdk-linux-x86 to a safe place. You can also rename it to an easier name. Example : I placed it in ~/Home and renamed it androidsdk.
3. Go to the SDK folder, then in the folder Tools/. Double-click on Android and choose Run.
4. Go to Available packages, and choose to install (choose at your will !)
Android SDK Tools, revision 8
Android SDK Platform-tools, revision 1
SDK Platform Android {VERSION(S) YOU WANT} (!) You need at least one Platform. For X10, you can download 1.6, 2.1. You can also add 2.2, 2.3.
Once it's done, close the window.
5. Download Xperia X10 add-on for SDK. (?) Read the PDF add-on guide, it is helpful !
Copy the folder (from the archive) XPERIA-X10_r1 inside the folder add-ons of your Android SDK folder ({androidsdk}/add-ons/).
6. Run terminal, go to your Android SDK folder, then in tools folder, and run
Code:
./android list target
.
Note the id number of the Android you want to develop (ie for me, Android 2.3 is
Code:
id: 3 or "android-9"
). (?) You might also want to note the name ("android-X") as it might be useful later.
7. Now, create AVD (a profile for emulator). Usual command (assuming you are INSIDE the /tools/ folder !) is
Code:
android create avd -n NAMEYOUWANT -t {ID}
So, for us, it will be
Code:
./android create avd -n myx10 -t 3
8. To generate the AVD, you will be prompted several info. Type these for Xperia X10 :
Create custom hardware profile : yes
SD Card support : yes
Asbstracted LCD density : 160 (correct if I'm wrong ?)
DPad support : no (?)
Accelerometer : yes
Max camera pixels (H) : 3264
Cache partition size : 66 (?)
Audio playback : yes
Trackball : no (?)
Max cam pixels (V) : 2448
Camera support : yes
Battery support : yes
Touch screen : yes
Audio record : yes
GPS : yes
Cache partition : yes
Keyboard : no
heap size : 32
RAM : 280
GSM Modem : yes
(?) I recommend you to create one profile for each Android version you want to run (so : you just have to change the ID, and create same profile). If you don't, you won't be able to run custom ROMs using other versions of Android (ie your AVD profile is 2.3 and you run a 2.1 custom ROM).
9. Done ! Take your custom ROM (downloaded, compiled... In this case, files are in {YourAndroidRepoFolder}/out/target/product/generic/. It comes with about 3 files, including a file called system.img. Copy this file into the folder (hidden) .android/myx10{In fact, the name you've chosen earlier "NAMEYOUWANT"}.avd/
10. Run terminal, go to Android SDK folder/tools/ (if you didn't close your current terminal, you're already in and run this command to run emulator WITH your custom ROM :
Code:
./emulator -avd myx10{again the "NAMEYOUWANT" you've chosen before}
Wait and enjoy !
(?) First boot is long - it's NORMAL. Just like on a real device, the OS will be cached and will work faster and faster.
Click to expand...
Click to collapse
8. To generate the AVD, you will be prompted several info. Type these for Xperia X10 :
Create custom hardware profile : yes
SD Card support : yes
Asbstracted LCD density : 240
DPad support : no
Accelerometer : yes
Max camera pixels (H) : 3264
Cache partition size : 100
Audio playback : yes
Trackball : no
Max cam pixels (V) : 2448
Camera support : yes
Battery support : yes
Touch screen : yes
Audio record : yes
GPS : yes
Cache partition : yes
Keyboard : no
heap size : 64
RAM : 403
GSM Modem : yes
works with the LG O2X roms?
sjcunha said:
works with the LG O2X roms?
Click to expand...
Click to collapse
hasn't been tried yet