Comment 59 for bug 271706

I have cleaned up the duplicates for this bug, and changed the summary to deal with only the U300.

If anybody is subscribed to this bug and does not own a U300, please search for a volume repeat/stuck problem related to your hardware, to keep things organized for the maintainers. Unfortunately we have to deal with these keyboard quirks on a hardware-to-hardware basis.

As far as a patch goes for the U300, I will see about writing one for this system, based on the above information. I'm not sure if what I have in mind will work, but I will try to write a patch for the U300 for on the current Ubuntu kernel - and then hopefully someone in this bug subscription is comfortable/capable of compiling an ubuntu kernel to test it on a U300.

(Although I must say, this one is the most unique keyboard hardware quirk I have seen yet).

To illustrate this hardware quirk, for those trying to understand it (or those curious =D):
Wheel Up = on, off, on, off, ON (so keep sending from this point on)
Wheel Down = on, off, on, off, ON (so keep sending from this point on)
But when we do it again:
Wheel Up = negate last "up" state (so OFF), on, off, on, off
Wheel Down = negate last "down" state (so OFF), on, off, on, off
cycle complete.

I will do my best in the absence of any accountable logic on your part, Toshiba xD