Softkeys not working on Samsung D900

[GoogleCodeExporter]

Using the example, the left and right soft keys don't work.

Original issue reported on code.google.com by ianstr...@gmail.com on 13 Dec 2007 at 2:14

[GoogleCodeExporter]

Since I do not have that phone I need you to collect some information for me:
  # Open the "UI Demo" example midlet
  # Select "Key Code" from the menu
  # Press the right soft key and write down the number that appears
  # Press the left soft key and write down the number that appears
  # Post them to this issue

Thanks!
-D

Original comment by deanbro...@gmail.com on 13 Dec 2007 at 6:39

[GoogleCodeExporter]

Right softkey is -8
Left softkey is -8
as is the middle button????

Samsungs are terrible phones, anyone usually planning on developing for them 
ends up
scrapping them so don't worry to much about this. I may look into myself if I 
get the
time

Original comment by ianstr...@gmail.com on 14 Dec 2007 at 9:54

[GoogleCodeExporter]

There is no way to fix this if all the key codes are the same.  Other Samsung 
phones
work including the D907 which is AT&T's branded version.  Therefore I suspect 
there
is a firmware update for the D900.

Original comment by deanbro...@gmail.com on 10 Jan 2008 at 5:05

• Changed state: WontFix

[GoogleCodeExporter]

Hi 
I heard that getGameAction returns FIRE for softkeys on many Samsung Devices.
This explained why J4ME got the wrong code (-8 for both softkeys).

Please find attach a J4ME patched binary for test purposes. 
This should fixed the problem on your Samsung.
If not , will you please  run the UIDemo / move focus to Log menu item / Press 
Right
soft key - Ok (should do nothing) and then press fire.

You will get into a log, will you please tell us what are the last two lines
beginning with [Debug Key[.....]

Original comment by jmherme...@gmail.com on 15 Jan 2008 at 4:48

Attachments:

• j4me.jar

[GoogleCodeExporter]

Re-opening utnil ianstrain tries the attached j4me.jar.

Original comment by deanbro...@gmail.com on 15 Jan 2008 at 4:56

• Changed state: New

[GoogleCodeExporter]

Marking this issue as "Invalid" because we haven't heard back from ianstrain.

Original comment by deanbro...@gmail.com on 25 Feb 2008 at 8:36

• Changed state: Invalid

[GoogleCodeExporter]

This is bug is confirmed by a end user

Original comment by commedan...@gmail.com on 23 Jun 2008 at 4:35