Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
Try to replace files "eve_qwerty.kcm.bin" and "qwerty.kcm.bin" in folder
"/system/usr/keychars/" with same files from 2.2 firmware with qwerty
Original comment by 2gel...@gmail.com
on 9 Apr 2011 at 12:47
Thx. But this method caused my keyboard to stop responding. I found a rar file
of the gw620 and I manually remapped the eve_qwerty.kl. Here is the archive
file if anyone encounters the same ;)
Original comment by amaury.l...@gmail.com
on 9 Apr 2011 at 1:20
Attachments:
do i have to replace only the eve_qwerty.kl file? cause i replaced all the
files and my layout was worse!
Original comment by jjcastil...@gmail.com
on 9 Apr 2011 at 8:07
ok i replaced only eve_qwerty.kl but now i cant put any symbol! any suggestion?
Original comment by jjcastil...@gmail.com
on 9 Apr 2011 at 8:14
I replaced base file by the six ones provided by amaury.l...@gmail.com, it
works very well. A bit long to do with adb, but efficient.
Original comment by m.pluvin...@gmail.com
on 10 Apr 2011 at 8:42
how did u did it man? cause i used root explorer and replaced those files and
my keyboard went nuts!
Original comment by jjcastil...@gmail.com
on 10 Apr 2011 at 4:31
jjcastil did you set the right permissions?
Original comment by omarbeko...@gmail.com
on 10 Apr 2011 at 5:09
Just use root explorer to set r/w permissions (mount r/w), extract the file to
your computer. Use adb shell with these commands:
adb push eve_qwerty.kl /system/usr/keylayout
adb push qwerty.kl /system/usr/keylayout
adb push AVRCP.kl /system/usr/keylayout
adb push eve_qwerty.kcm.bin /system/usr/keychars
adb push qwerty.kcm.bin /system/usr/keychars
adb push qwerty2.kcm.bin /system/usr/keychars
adb reboot
everything should work fine, even the symbols. Hope this helps ;)
Original comment by amaury.l...@gmail.com
on 10 Apr 2011 at 5:39
thx man now its working... but i got a problem, my q is a, and my a is q... how
can i change this?
Original comment by jjcastil...@gmail.com
on 10 Apr 2011 at 6:14
and my w is z, and z is w... hahaha its better than before, but still, any fix
for this?
Original comment by jjcastil...@gmail.com
on 10 Apr 2011 at 6:16
This is the fix. Maybe you should try deleting the original files and replacing
them with the files from usr.rar ;)
Original comment by amaury.l...@gmail.com
on 10 Apr 2011 at 6:57
i did that and the i keep getting the same problem
Original comment by jjcastil...@gmail.com
on 10 Apr 2011 at 7:31
OpenEtna or LG official keyboard layouts are not compatible with the GB Alpha
test version.
Some patch sets of the OpenEtna froyo (by Polytheus) are not applied to this GB
like as
https://github.com/OpenEtna/android_packages_apps_Settings/commit/0d9a4e7d951d0b
cd5b3178427f28bf02fcdc3c0f
Original comment by wkp...@gmail.com
on 11 Apr 2011 at 10:51
In that case, can you provide the correct files for QWERTY in GB as well?
Several of us are anxious in this forum:
http://forum.openetna.com/index.php?topic=1139.195
Original comment by rais...@gmail.com
on 11 Apr 2011 at 11:54
this is fixed libui.so
It will fix keylayout compatibility issue.
(https://github.com/OpenEtna/android_frameworks_base/commit/8182915bb58e19b00ba3
51b193974bc95f3164e2 by Polytheus)
It ignores ATCMD* etc. symbols.
you can push libui.so as following
adb remount
adb push libui.so /system/lib/
----
And I also fix to support persist.sys.kcm.eve_qwerty property to change kcm
file using System Settings.
ref:
https://github.com/OpenEtna/android_packages_apps_Settings/commit/0d9a4e7d951d0b
cd5b3178427f28bf02fcdc3c0f by Polytheus
(this patch support persist.sys.kl.eve_qwerty property.
but I think it is more flexible to change kcm (keyboard char map) rather then
kl (key layout)
----
attached eve_qwerty_gw620.kcm.bin is the original OpenEtna kcm file.
----
You can change your keyboard map file (kcm) like as following
Settings => Language & keyboard settings => Built-in keyboard => Keyboard Map(kcm)
currenty only two kcm files are supported
qwerty(KH5200. default) / qwerty(GW620)
after change your default kcm you have to reboot
(or adb shell killall system_server)
----
Original comment by wkp...@gmail.com
on 12 Apr 2011 at 1:06
Attachments:
patch set against CM7.0
Original comment by wkp...@gmail.com
on 12 Apr 2011 at 1:37
Attachments:
when you can complie an image that fix all those bug for us? thankyou :)
nice working
Original comment by vu.thaia...@gmail.com
on 12 Apr 2011 at 1:41
patch set against CM7.0 package/app/Settings
Original comment by wkp...@gmail.com
on 12 Apr 2011 at 1:42
Attachments:
Thanks! It works pretty well, there are even extra charaters from keys that are
not labeled with special characters.
Sorry, but I don't know what to do with the .patch and the .diff files though.
Original comment by rais...@gmail.com
on 12 Apr 2011 at 6:52
patch sets are just for developers :)
Original comment by wkp...@gmail.com
on 12 Apr 2011 at 7:18
please give us which command we can use to push your file to phone?
thankyou
Original comment by vu.thaia...@gmail.com
on 12 Apr 2011 at 7:34
Ah, developers.
Thanks again, and keep up the great work, I can't wait till the next release!
Original comment by rais...@gmail.com
on 12 Apr 2011 at 8:24
This is all-in-one update package. you can install it under RecoveryMode
Original comment by wkp...@gmail.com
on 12 Apr 2011 at 10:08
http://code.google.com/p/openeve/issues/detail?id=3 #3 #10
also include libaudio.so patch
Original comment by wkp...@gmail.com
on 12 Apr 2011 at 10:36
oops!
Please see also http://code.google.com/p/openeve/issues/detail?id=10
Original comment by wkp...@gmail.com
on 12 Apr 2011 at 10:40
wkpark i think that we must have an official way to update, because uploading
those update packs can create confusion...
Thanks a lot for this patch ;)
Original comment by andreabe...@gmail.com
on 12 Apr 2011 at 11:02
Don't forget to tell the truth. it is just A *ALPHA* test version.
I don't want to make you all as testers :>
Original comment by wkp...@gmail.com
on 12 Apr 2011 at 11:10
Maybe, the next update: QWERTZ(GW620)???
Original comment by faddil...@gmail.com
on 12 Apr 2011 at 3:54
[deleted comment]
[deleted comment]
faddil//
It contains QWERTZ(based on QWERTY(GW620))
and AZERTY(also based on QWERTY(GW620))
Please see http://forum.openetna.com/index.php?topic=1139.msg10974#msg10974
Original comment by wkp...@gmail.com
on 13 Apr 2011 at 1:00
Original comment by wkp...@gmail.com
on 13 Apr 2011 at 1:22
Maybe I'm lame, but it does not work. The symbols on the QWERTY (GW620) work
fine. But the "Z " -> "Y" and "Y" -->"Z"
Diferent mapping: the symbols is incorrect. And the "Z" -->"Y" ...
I did installed the update-gb-110412a.zip
Any idea?
Original comment by faddil...@gmail.com
on 13 Apr 2011 at 2:49
change QWERTY >>>>> QWERTZ
Original comment by justsad.eng@gmail.com
on 13 Apr 2011 at 2:52
Then the symbols is incorrect!!!
Original comment by faddil...@gmail.com
on 13 Apr 2011 at 3:12
are you sure ? someone says it works. the others says it doesnt
It means that you have changed your /system/usr/keylayout/eve_qwerty.kl
restore your eve_qwerty.kl and try again.
Original comment by wkp...@gmail.com
on 13 Apr 2011 at 3:54
I made it!
I rewrote the eve_qwerty.kl key21 - Z ; key44 - Y
THX for help!
Original comment by faddil...@gmail.com
on 13 Apr 2011 at 5:14
I must be missing something obvious here but I couldn't seem to get my azerty
physical keyboard recognized as such. Here are the steps I performed, please
tell me where it went wrong.
I upgraded from openetna cyanogen 6. I've installed update-gb-110412a.zip (I
did a fastboot -w before and after) from gb-recovery.com.
In Settings => Language & keyboard settings => Built-in keyboard => Keyboard
Map(kcm) I chose Azerty (I had QWERTY, QWERTY(GW620), QWERTZ, AZERTY, CUSTOM).
But the keyboard remained qwerty, despite many reboots...
I finally found a way, I post it here in case it helps someone else :
* adb pull /system/usr/keylayout/qwerty.kl
* edit this file, swap A for Q, Z for W, save as qwerty-modified.kl
* adb push qwerty-modified.kl /system/usr/keylayout/qwerty.kl
(At this point, the characters were ok but the symbols were all wrong because I
still had the AZERTY layout chosen from the menu)
* Choose the QWERTY(GW620) layout from the menu
All characters and symbols are now ok. What did I do wrong at first ?
Original comment by j.cubizo...@gmail.com
on 13 Apr 2011 at 10:19
Attachments:
oops!! Settings.apk has wrong information for eve_qwerty_azerty.kcm / qwertz
sorry. (eve_qwerty_(underscore)azerty was miss typed as eve_qwerty-(dash)azerty)
Please see issue #21
http://code.google.com/p/openeve/issues/detail?id=21#c7
and... It is not recommended to modify the default eve_qwerty.kl
(OpenEtna's method)
Original comment by wkp...@gmail.com
on 13 Apr 2011 at 11:35
This update include fixed Settings.apk and default eve_qwerty.kl
Original comment by wkp...@gmail.com
on 14 Apr 2011 at 3:12
Attachments:
[deleted comment]
Check this,
can you make a keyboard file if possible?
Original comment by PoweredB...@gmail.com
on 14 Apr 2011 at 4:33
Attachments:
PoweredB // You can make your KeyboardMapping (please see this Wiki page)
but It seems like that this is a Chinese keyboard mapping and
you have to use XIM application to combine it's characters.
you can use *.kcm but direct input method does'nt combine its chars.
Original comment by wkp...@gmail.com
on 14 Apr 2011 at 7:10
The new update (update-gb-110414.zip) contains the same eve_qwerty.kl, so I
guess it won't fix the problem I had with my azerty keyboard.
Also, what problem has been addressed with the fixed Settings.apk ?
Finally, is there a way to change the keyboard layout without rebooting the
phone, maybe from adb shell ? It's taking an awful lot of time to reboot
everytime...
Original comment by j.cubizo...@gmail.com
on 14 Apr 2011 at 9:10
j.cubizo // don't try to fix eve_qwerty.kl and please see KeyboadMapping.
In Settings => Language & keyboard settings => Built-in keyboard => Keyboard
Map(kcm) I chose Azerty (I had QWERTY, QWERTY(GW620), QWERTZ, AZERTY, CUSTOM).
1. check persist.sys.kcm.eve_qwerty property.
adb shell getprop persist.sys.kcm.eve_qwerty ("eve_qwerty" is device name)
eve_qwerty_azerty (this is kcm name)
2. you don't have to reboot. just try to kill some application like as ADWLauncher
adb killall com.android.launcher (launcher is automatically restarted)
3. try to type keyboard.
Original comment by wkp...@gmail.com
on 14 Apr 2011 at 9:58
I found how change QwERTY in AZERTY
For beginning download and install Root explorer on your GW620
http://www.megaupload.com/?d=LMYBRCCZ
- After with root explorer go in system/usr/keychars rename eve_qwerty.kcm.bin
to eve_qwerty.kcm.bin.old and eve_qwerty_azerty.kcm.bin to eve_qwerty.kcm.bin
- Go in system/usr/keylayout rename eve_qwerty.kl to eve_qwerty.kl.old and
eve_qwerty_azerty.kl to eve_qwerty.kl
For me it works nice.
Original comment by frchas...@gmail.com
on 14 Apr 2011 at 11:26
frchas // that way is not recommended Please see KeyboardMapping
Original comment by wkp...@gmail.com
on 14 Apr 2011 at 11:31
HOME or BACK is touch keypad.
when this device initialized it search "synaptics-touch-button.kl"
KeyboardLayout
but "synaptics-touch-button.kl" is not exists, so the "qwerty.kl"
KeyboardLayout loaded.
....
04-14 20:33:39.272: INFO/EventHub(3480): New keyboard: device->id=0x10002
devname='synaptics-touch-button' propName='hw.keyboards.65538.devname'
keylayout='/system/usr/keylayout/qwerty.kl'
....
Please check your qwerty.kl
...
key 102 HOME WAKE
...
key 158 BACK WAKE_DROPPED
Original comment by wkp...@gmail.com
on 14 Apr 2011 at 11:54
@ wkp. Don't know what changed but now it's working, characters and symbols.
* I applied update-gb-110414.zip
* chose azerty layout (qwerty-gw620 works too).
and now my keyboard is azerty. The only difference with my previous attemps is
that I checked persist.sys.kcm.eve_qwerty, killed ADWLauncher from a adb shell
as you suggested but I don't think it could have made a difference.
Thanks a lot for your help.
Original comment by j.cubizo...@gmail.com
on 14 Apr 2011 at 12:18
Original issue reported on code.google.com by
amaury.l...@gmail.com
on 9 Apr 2011 at 9:06