Set Up Your MediaTek Device with Comprehensive Beginner’s Guide

As can be seen with the use of MediaTek chips in Android One devices … more

Sony Updates AOSP Sources to Android 5.0.1

Just a few days ago, Sony did an utterly fantastic job by pushing out numerous device trees for … more

Stop Your Screen From Turning Off with KeepItOn

We all know the feeling of reading a news article orrather longdocument, when our screen … more

The XDA LG QPair Developer Challenge Voting Has Begun!

It seems like it was just yesterday that weannounced that we had paired up with LGto … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[How To] Keyboard Physical AZERTY

OP Meelouw

15th February 2012, 09:59 PM   |  #1  
OP Senior Member
Thanks Meter: 7
122 posts
Join Date:Joined: Dec 2010
Hi !

i have modified Generic.kcm and Generic.kl to have my physical keyboard like a azerty and no qwerty.


Don't forget to modified your build.prop if you have a problem. I am not responsable if you brick your tablet S.

Delete ".txt" of the two files

Push "Generic.kcm" to /system/usr/keychars with permissions : Read for all and write for Owner.

Push "Generic.kl" to /system/usr/keylayout with same permissions

Reboot system and it's done

Enjoy !
Attached Files
File Type: txt Generic.kl.txt - [Click for QR Code] (9.2 KB, 936 views)
File Type: txt Generic.kcm.txt - [Click for QR Code] (15.0 KB, 463 views)
Last edited by Meelouw; 20th February 2012 at 06:17 PM.
The Following User Says Thank You to Meelouw For This Useful Post: [ View ]
9th March 2012, 11:30 PM   |  #2  
hhenault's Avatar
Flag Paris
Thanks Meter: 6
78 posts
Join Date:Joined: Oct 2009
Hello Meelouw,

I tried on a Galaxy Note, Android 2.3.6, with a 'generic' KeySonic bluetooth keyboard+mouse from the 'Surcouf' area ...

Does not work for me; Kbd stays 'QWERTY'

I have pushed your two files 'as is' in their respective directory (note that they were not there before) :

# ls -l /system/usr/keychars
ls -l /system/usr/keychars
-rw-r--r-- root root 896 2011-11-11 07:04 Broadcom_Bluetooth_HID.kcm.bin
-rw-r--r-- root root 896 2011-11-11 07:04 Vendor_04E8_Product_7021.kcm.bin
-rw-r--r-- root root 896 2011-11-11 07:04 qwerty.kcm.bin
-rw-r--r-- root root 896 2011-11-11 07:04 qwerty2.kcm.bin
-rw-r--r-- root root 896 2011-11-11 07:04 sec_e-pen.kcm.bin
-rw-r--r-- root root 896 2011-11-11 07:04 sec_jack.kcm.bin
-rw-r--r-- root root 896 2011-11-11 07:04 sec_key.kcm.bin
-rw-r--r-- root root 896 2011-11-11 07:04 sec_touchkey.kcm.bin
-rw-r--r-- root root 17996 2011-05-15 00:15 Generic.kcm
# ls -l /system/usr/keylayout
ls -l /system/usr/keylayout
-rw-r--r-- root root 349 2011-11-11 07:04 AVRCP.kl
-rw-r--r-- root root 2043 2011-11-11 07:04 Broadcom_Bluetooth_HID.kl
-rw-r--r-- root root 2375 2011-11-11 07:04 Vendor_04E8_Product_7021.kl
-rw-r--r-- root root 1834 2011-11-11 07:04 qwerty.kl
-rw-r--r-- root root 117 2011-11-11 07:04 sec_e-pen.kl
-rw-r--r-- root root 166 2011-11-11 07:04 sec_jack.kl
-rw-r--r-- root root 328 2011-11-11 07:04 sec_key.kl
-rw-r--r-- root root 44 2011-11-11 07:04 sec_touchkey.kl
-rw-r--r-- root root 8038 2011-05-14 23:48 Generic.kl

Looks like my Android and yours do not use the same default files for the keyboard.

Were your generic.kl/kcm files in QWERTY before you changed them ?

If yes, I should probably rename them to 'qwerty.kl/kcm', which seem to be my default files.

Or maybe should I find a way to compile Generic.kcm to obtain Generic.kcm.bin ?

If you have the answer ...

In any case, thanks for the job.
Last edited by hhenault; 9th March 2012 at 11:33 PM.
12th March 2012, 06:58 PM   |  #3  
OP Senior Member
Thanks Meter: 7
122 posts
Join Date:Joined: Dec 2010
si j'ai bien compris, en mettant mes fichiers ça ne change rien ?

alors je sais qu'ils marchent sur une Xoom, sur un Gn (moi qui ai testé) et la tablet S donc je sais pas si c'est à partir de 3.0 car je n'ai pas les mêmes fichiers que toi.

De mémoire j'ai Generic.kcm qwerty.kcm qwerty2.kcm tuna-gpio-keypad.kcm virtual.kcm dans keychars et Generic.kl qwerty.kl tuna-gpio-keypad.kl et d'autre dans keylayout

donc à voir si ton clavier bluetooth se fait pas "diriger" par un autre fichier, peut être par le brodcom-bluetooth ? en tout cas non il faut pas les mettre en .bin, même pour les modifier, personnellement je modifie sans toucher l'extension du fichier avec notepad++
7th May 2012, 07:40 PM   |  #4  
Junior Member
Flag Chinon
Thanks Meter: 3
21 posts
Join Date:Joined: Aug 2010
Une application fait ça très bien External Keyboard Helper Demo" sur le Google Play ! elle gère les différents types de langages pour les claviers périphériques.
Du moins pour moi ça fonctionne très bien sur mon netbook avec Androidx86
16th October 2012, 10:45 PM   |  #5  
CoolApps's Avatar
Senior Member
Thanks Meter: 603
3,344 posts
Join Date:Joined: May 2011
Donate to Me
English please!, its in the rules

Sent from my Sony Tablet S using xda premium
1st November 2012, 06:48 PM   |  #6  
Senior Member
Flag Schkeuditz
Thanks Meter: 72
122 posts
Join Date:Joined: Dec 2009
Donate to Me
the App "External Keyboard Helper Pro" help you Find on Google Market or Aptoide (non Root permissions!)
Last edited by xxliftsupxx; 14th December 2012 at 04:43 PM.
18th March 2014, 10:57 PM   |  #7  
Junior Member
Thanks Meter: 6
11 posts
Join Date:Joined: May 2013
This fix works for BlueStacks App Player.. Sorry off-topic, but confirmed, works!

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes