Samsung Q210 brightness keys do not work

Bug #333352 reported by Stephen Brandwood on 2009-02-23
This bug affects 3 people
Affects Status Importance Assigned to Milestone
hal-info (Ubuntu)
Martin Pitt

Bug Description

Binary package hint: hal-info

Running Intrepid on a Samsung Q210 laptop. The brightness keyboard keys have no effect (FN + Up/Down arrows).

xev shows no events when these keys are pressed.

Sleep, volume, mute, touchpad on/off all work as expected, including on-screen graphics where appropiate.

Related branches

Stephen Brandwood (sbrandwoo) wrote :
description: updated
Martin Pitt (pitti) wrote :

Please do the steps on to figure out the scan codes of the non-working keys, and give a table of scan codes -> intended functionality. Thank you!

Changed in hal-info:
status: New → Incomplete
Stephen Brandwood (sbrandwoo) wrote :

I'm having trouble with this step:

"attach to the devices one by one using sudo input-events <devnum> (in the input-utils package), using the number returned by lshal as part of input.device, and press the hotkey to see if an event is generated"

It's quite clear which device is which, but no matter what I press (normal key, function key, whatever), input-events never picks up anything:

> waiting for events
> timeout, quitting

All the beforehand steps have been fine until this point (including disabling gnome-power and gnome-settings).

Martin Pitt (pitti) wrote :

You mean it doesn't pick up Fn+Up/Down, or no key at all? In the latter case, you are using the wrong input device. Are you trying this from a text console (Ctrl+Alt+F1)? Are you sure you got the right input device? In it should be number "1".

Stephen Brandwood (sbrandwoo) wrote :

Sorry, I was using a terminal rather than the console. Here are the expected key mappings:

code=4, value=136 => brightness up
code=4, value=137 => brightness down

  system.hardware.primary_video.product = 1768 (0x6e8) (int)
  system.hardware.primary_video.vendor = 4318 (0x10de) (int)
  system.hardware.product = 'Q210' (string)
  system.hardware.serial = 'CV7893EQ700048' (string)
  system.hardware.uuid = 'A0F81071-D21D-B211-8000-D7586BB60F5B' (string)
  system.hardware.vendor = 'SAMSUNG ELECTRONICS CO., LTD.' (string)
  system.hardware.version = 'Not Applicable' (string)


Martin Pitt (pitti) wrote :

Committed upstream.

Changed in hal-info:
assignee: nobody → pitti
status: Incomplete → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package hal-info - 20090227-0ubuntu1

hal-info (20090227-0ubuntu1) jaunty; urgency=low

  * New git snapshot:
    - Hotkeys for Fujitsu Siemens Amilo Si 1520 (LP: #317505)
    - Fix Fn+Arrow "Brightness Up" key on Acer laptops (LP: #327707)
    - UM175 modem (LP: #328309)
    - Sleep quirks for HP nw8440 (LP: #328522)
    - Samsung YP-S2 audio player (LP: #331538)
    - Samsung YP-S5 audio player (LP: #332913)
    - Fix Samsung Q210 brightness keys (LP: #333352)
    - Sony Ericsson w880i/3G mobile modem (LP: #334327)

 -- Martin Pitt <email address hidden> Fri, 27 Feb 2009 11:14:51 +0100

Changed in hal-info:
status: Fix Committed → Fix Released
gutek8654 (gutek8654) wrote :

hi, i'm new here :) and sory for my english
i've update this package but bug isn't fixed.
under console 'getkey' see all keys: brightness up/down on/off, battery, wifi.
but under X they give unexpected result:
- battery: battery state is shown, but after that i can do nothing, keyboard is off, can't run any applications
- brightness on/off: nothing happens
- wifi on/off: nothing happens
- brightness up/down: the visual is shown, but with no result and heyboard is off

Martin Pitt (pitti) wrote :


this bug is closed, so please file a new one if you still have problems. Use "ubuntu-bug hal-info" for this.

> - battery: battery state is shown, but after that i can do nothing, keyboard is off, can't run any applications.

That sounds like a kernel bug which was fixed a while ago in Jaunty:

linux (2.6.28-7.20) jaunty; urgency=low

  [ Tim Gardner ]

  * SAUCE: Input: atkbd - Samsung NC10 key repeat fix

 Please report it against "linux".

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments