b7610: keymapping and driver

[GoogleCodeExporter]

What steps will reproduce the problem?

1. Trying to open the wifi menu

What is the expected output? What do you see instead?

There is no hardware key corresponding to the wifi-menu.

What version of the product are you using? On what operating system?

Beta 1024

Please provide any additional information below.

Im running this Beta on a B7610. So I understand that probably there are 
incompatibility issues. But still, the B7610 is almost identical to the Omnia 
II, so this is more of a plead to the developers to fix some support for this 
phone :)

Original issue reported on code.google.com by wvandenb...@gmail.com on 19 Jan 2011 at 12:31

[GoogleCodeExporter]

The first step is to get a working version for I8000 phones. Check the faq ( 
http://code.google.com/p/omnia2droid/wiki/FAQ#Will_my_phone_xxx_be_supported? 
). I guess the current developers don´t own a B7610 phone, so they´ll have a 
hard time adapting android for your device. However, the sources will be 
released and after that there´ll surely be someone that will try his/her best 
to get this to work :)

Original comment by aleo...@gmail.com on 19 Jan 2011 at 12:46

[GoogleCodeExporter]

If a B7610 is needed, I will provide mine for testing and developing purposes.

Original comment by erikcas1972@gmail.com on 19 Jan 2011 at 4:43

[GoogleCodeExporter]

Original comment by nathrin...@gmail.com on 19 Jan 2011 at 4:56

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

is not a bug, is feature request (support B7610 keymapping). 

You could try some things yourself first ...
  * read some doc at http://source.android.com/porting/keymaps_keyboard_input.html
  * get keycodes from logcat (use adb setup or alogcat app)
  * search for simular .kl keymap files
  * try editing existing live keymap (terminal emulator app, adb setup, ext2 mount)
  * pse report/share findings here, we'll add to faq

If one wants to take on this little project, we can make you owner and turn 
status to "started"

Original comment by elbee1...@gmail.com on 19 Jan 2011 at 7:12

• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Other

[GoogleCodeExporter]

Original comment by elbee1...@gmail.com on 20 Jan 2011 at 8:11

• Changed title: B7610: hardware button mapping

[GoogleCodeExporter]

Original comment by elbee1...@gmail.com on 20 Jan 2011 at 8:12

• Changed title: b7610: hardware button mapping

[GoogleCodeExporter]

almar has this on medium prior now, but needs help from b7610 user (he does not 
own this phone). pse leave comment here if you want to take on some work to 
help out.

Original comment by elbee1...@gmail.com on 20 Jan 2011 at 9:58

• Changed state: Started
• Added labels: Priority-Medium
• Removed labels: Priority-Low

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I am a B7610 user and I would be happy to help with these. I am a kinda 
experienced linux user but new with android. Feel free to contact me if you 
still need help. (Email: sakisds.shinigami@gmail.com , msn: sakisds@mail.gr).

Original comment by sakisds....@gmail.com on 20 Jan 2011 at 1:41

[GoogleCodeExporter]

@elbee1972. You've got mail.

Original comment by erikcas1972@gmail.com on 21 Jan 2011 at 11:00

[GoogleCodeExporter]

sakisds&cas, thx for offer, Mosci and me are researching this (some progress), 
Almar is helping us out. Mosci found several scancodes, but still multiple 
scancodes for 1 key bug ...

Original comment by elbee1...@gmail.com on 25 Jan 2011 at 11:40

• Changed title: b7610: keymapping and driver

[GoogleCodeExporter]

I might be able to help out too :)

What do you need? I can work with adb logcat so it shouldn't be too hard?

Original comment by ErnstJan...@gmail.com on 26 Jan 2011 at 5:46

[GoogleCodeExporter]

at the moment it seems not to be a keymapping-problem the worst problem seems 
to be that we have multiple scancodes for most of the keys (and some keys ar 
dead - like T,Z,G,H, VOLUME UP ... and some more)
editing the drivers/input/keyboard/s3c-keypad.h makes some changes in resulting 
scancodes ... and some more key's working ... but  due to my less knowledge 
about c/c++ i can not get further here ... 
with the new kernelsource (rev 57) i'm not able anymore to get adb working ?!
lsusb hangs until i unplug usb.
with rev 53 there wasn't such a problem? any hints what causes this behavior?

Original comment by mosclamer on 27 Jan 2011 at 10:44

[GoogleCodeExporter]

within the s3c-keypad.h (i guess modified by almar) there are only 9 key's 
defined
my (me = mosci) logcat ends up with 8 different scandodes for all working keys 
in various combinations ...
i tried to edit the s3c-keypad.h-matrix (rows,cols kyp_nr and so on) that 
changes a lot ... but due to missing knowledge it was just fishing in the dark.
and i always had to recompile the kernel ofcause - just to see there is some 
difference. if someone can point me in the right direction ... i will go on 
(with rev 53 where my adb still works :-)) 

Original comment by mosclamer on 27 Jan 2011 at 11:30

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

ok ...little progress:
multiple scancodes have gone whith uncommenting some code on omnia_ii.c
but i have only 32 uniqe scancodes for 47 keys now and the
Power/EndCall-button does not work at all

Original comment by mosclamer on 1 Feb 2011 at 12:00

[GoogleCodeExporter]

after some hours with 'try and error' and some study on the sph-m920 code 
(thanks to eblee for the hint) i was able to get 44 unique scancodes.
but afterwards some more gpios have to used for keyscan - some of those gpios 
are triggert for other functions .. so the phone produces a lot of eroors in  
S3c2DRender::DoG2D

so ... there has to be done more than expected ... first we need to know the 
exact gpio-mapping of the b7610 wich is definitively differing.
due to this unfortunatly the haret can not do the gpiotrace out of the box - we 
need a b7610-patched version - wich seems not to available yet.

Original comment by mosclamer on 2 Feb 2011 at 8:05

[GoogleCodeExporter]

Original comment by omnia2dr...@gmail.com on 2 Feb 2011 at 11:32

[GoogleCodeExporter]

Keyboard works almost
ToDo:
alt-characters do not work
Power-Button  only locks the screen but does not gives the possibility to 
shutdown

Original comment by mosclamer on 3 Feb 2011 at 5:36

[GoogleCodeExporter]

here is what i have changed so far ...

Original comment by mosclamer on 4 Feb 2011 at 4:48

Attachments:

• b7610_rev68.patch.tar.gz

[GoogleCodeExporter]

will try this out! thanks for the work so far, sorry i cant help but i will 
test it for ya XD

Original comment by l.rijsew...@gmail.com on 4 Feb 2011 at 7:33

[GoogleCodeExporter]

*.kcm.bin recompiled so ...
alt-characters for qwertz-layout working also fine
todo:
build *.kcm.bin for different keyboardlayouts 
(if alt-characters differ otherwise it's enough to edit the *.kl file)

Original comment by mosclamer on 4 Feb 2011 at 9:42

[GoogleCodeExporter]

b7610_rev68.patch.tar.gz 

is that QWERTY or QWERTZ?

Original comment by kasperle...@gmail.com on 4 Feb 2011 at 9:49

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

it is both & azerty too ;-)  
no ... this are only the patches / differs from original kernerlsource.
qwertz/qwerty/azerty will be defined in android *.kcm.bin /*.kl file.

Original comment by mosclamer on 4 Feb 2011 at 10:51

[GoogleCodeExporter]

Will test this weekend and see if I can help you out with alt-characters

Original comment by erikcas1972@gmail.com on 4 Feb 2011 at 11:38

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

all keys working - even alt-characters ;-)
thanks

Original comment by mosclamer on 4 Feb 2011 at 11:47

[GoogleCodeExporter]

bad reading :) will test!

Original comment by erikcas1972@gmail.com on 4 Feb 2011 at 3:26

[GoogleCodeExporter]

How does one install this patch ? Rename to o2bupdate and place in rootfolder ?

Original comment by wvandenb...@gmail.com on 4 Feb 2011 at 11:18

[GoogleCodeExporter]

I STRONGLY RECOMMEND TO DO A BACKUP BEFORE!!

use like any other update
unzip
replace zImage with new one
place o2bupdate.tar.gz next to your haret.exe & zImage
run ... mabe reboot

keylayout:
CALL: Open Call-APP
CENTER: MENU / WAKEUP
POWER: LOCKSCREEN / CALL-END
CAM: HOME
VOLUP/DOWN: VOL UP/DOWN
W&L: POWEROFF/AIRPLAIN/SILENT

QWERTY-Keyboard
changable to QWERTZ by change links in /system/usr/keychars/s3c-keypad.kcm.bin 
& /system/user/keylayout/s3c-keypad.kl

Original comment by mosclamer on 6 Feb 2011 at 11:04

• Changed state: prealfa

Attachments:

• B7610_Keyboard-Vibration_support.zip

[GoogleCodeExporter]

Original comment by mosclamer on 6 Feb 2011 at 11:05

• Changed state: Started

[GoogleCodeExporter]

LOCK: BACK   ;-)

Original comment by mosclamer on 6 Feb 2011 at 11:31

[GoogleCodeExporter]

hmm not able to wake up again after lock using the power-off key? Or am I 
missing something?

Original comment by erikcas1972@gmail.com on 6 Feb 2011 at 1:22

[GoogleCodeExporter]

working now. out of the blue :P

Original comment by erikcas1972@gmail.com on 6 Feb 2011 at 1:27

[GoogleCodeExporter]

Seems to be working here too, certainly makes things much easier. Seems to need 
a reboot or two before things settle down.

Original comment by vabb...@gmail.com on 6 Feb 2011 at 1:50

[GoogleCodeExporter]

Should be perfect if screen was rotating when pulling out keyboard. Searched 
for it but can't find anything on screen rotating. Is this an issue or is this 
my problem?

Original comment by erikcas1972@gmail.com on 6 Feb 2011 at 2:29

[GoogleCodeExporter]

issue ;-)

Original comment by mosclamer on 6 Feb 2011 at 2:32

[GoogleCodeExporter]

So we can change it to QWERTY :)
But I cannot edit BIN files? 

Original comment by ErnstJan...@gmail.com on 6 Feb 2011 at 3:17

[GoogleCodeExporter]

thats right  
 /system/usr/keychars/s3c-keypad.kcm.bin is a just symbolic link
wich points to the needed bin-file
 /system/usr/keychars/qwerty.kcm.bin
OR
 /system/usr/keychars/qwertz.kcm.bin

Original comment by mosclamer on 6 Feb 2011 at 3:26

[GoogleCodeExporter]

So if I change qwertz.kcm to qwerty.kcm  it works? :)

One more thing: The 'lock' button now functions as a 'back' button.. would love 
to have it as a lock button and W&L as the 'back' button.. lol :P

Then there's one more thing (don't know if you guys can change it..), when 
taking the keyboard out the screen doesn't rotate. (Don't know how much work it 
is to make this happen? :))

Original comment by ErnstJan...@gmail.com on 6 Feb 2011 at 3:31

[GoogleCodeExporter]

@ moscla...@googlemail.com, one more question. If zImage is replaced by future 
update, this won't work anymore? Maybe no key is working anymore?

I'm asking, because on i8000 Modaco thread is a rumor that Sandor might 
(almost) have fixed battery drain. And I think that is, just like this one, a 
must-have update when it is there.

Oh, by the way, did I already mention? Great job! Thanx very much for this! 
Working well here.

Original comment by erikcas1972@gmail.com on 6 Feb 2011 at 3:34

[GoogleCodeExporter]

thats rignt @ErnstJan
if you change the kernel, you have to switch back to backup
i think it will find its way in the main-kernel ...
but for now it's slightly different to the main kernel
und you will have strange reaktions on the keys.

Original comment by mosclamer on 6 Feb 2011 at 4:08

[GoogleCodeExporter]

keymapping / changeing  can be done by editing 
/sytem/usr/keylayout/s3c-keypad.kl
this is a textfile
changes will first have effect after rebooting

Original comment by mosclamer on 6 Feb 2011 at 4:10

[GoogleCodeExporter]

Hey mosclamer. Are you able to tell us if it is possible to get two different 
scancodes for the lock and the hangup/power button ?

Original comment by nathrin...@gmail.com on 7 Feb 2011 at 10:43

[GoogleCodeExporter]

sure you can ... at least by missconfiguration or if the button has 2 different 
values.
:-)

Original comment by mosclamer on 7 Feb 2011 at 11:04

[GoogleCodeExporter]

I'm talking about dissociating the lock and the hangup/power button. I haven't 
been able yet to assign a different function to each of them (probably because 
the driver returns the same keycode for both).

Original comment by nathrin...@gmail.com on 9 Feb 2011 at 1:29

[GoogleCodeExporter]

powerbutton is handled in a special way through the kernel ... thus he can't 
act as 'powerdown'... but .. maybe you will change this in the kernelsource.
to change the actions of the keys you simply have to edit the right *.kl file
in /system/usr/keylayout/ (should be this one to which the symbolic link 
s3c-keypad.kl points to).
a more detailed info can be found behind the link in post 4 of this issue.

Original comment by mosclamer on 9 Feb 2011 at 10:36

[GoogleCodeExporter]

Thanks, I've already been playing around with those. I'll give a look to the 
kernel sources when I get a chance.

Original comment by nathrin...@gmail.com on 9 Feb 2011 at 10:57

[GoogleCodeExporter]

same scancode or keycode? same scancode: should not happen if it is a b7610 
with the files from post 31.(if it's not a b7610 - you are in the wrong issue 
:-))
same keycode -> edit *.kl file

Original comment by mosclamer on 9 Feb 2011 at 10:58