Oh, another Q1U key mapping change you can make is to map the "Menu"
button to F4. F4 opens the Hildon menu in the Midbrowser (found by
spelunking in the Midbrowser source, but it looks like it works in other
Hildon apps, I tested it in tasks-hildon), useful for getting to bookmarks
and stuff. Optionally you can just hit F4 on the virtual keyboard instead
of mapping a key for it. The drawback of changing the mapping of the Menu
button is that it is by default mapped to the regular menu event (which
brings up the right click menu in GNOME apps), so you lose that.
If you want to map the Menu button to F4, you can again edit the .fdi, or
run this command:
sudo setkeycodes e054 62
Is there a place in the wiki, or some other online location, that quirks
like this could be documented on a per-device basis? It would be nice to
have something that describes what features work (touchscreen, wifi,
audio, etc) on different devices (and device versions), and also be able
to give tips on what changes can be made to suit the install for the
particular devices (button mappings, turning on the hide buttons for the
left panel to get the full screen width back, hitting F11 to toggle full
screen apps, etc). I would be happy to maintain it for the Q1U-EL, and
any other devices I can get my hands on.
> I think the issue you have with the arrow keys not acting like arrows on
> the Q1U is because they are mapped as up = F1, down = F3, right = F10,
> left = F9. One way you can change this is by editing:
> and changing the definitions (just look for "Samsung Q1 Ultra", and the
> key mappings are right below that text. replace "f10" with "right", "f1"
> with "up", "f3" with "down", "f9" with left. But the changes will be lost
> the next time hal-info is updated.
> Another way to change the key mappings is to just run a script (as root)
> that does this:
> sudo setkeycodes e056 108
> sudo setkeycodes e057 105
> sudo setkeycodes e058 103
> sudo setkeycodes e059 106
> The nice thing about this approach is that you can make scripts that
> change the keys to whatever you want, and just select the one that is
> right for the situation (map left/right to page up/down in some cases,
> regular arrows for editing/terminal work, and to A/S in another for
> gaming). Maybe there is already a tool to do this for you.
> Or maybe you can do this using a custom keymap, that would be nice if
> possible because then you can leverage existing applications to do the
> switching between layouts.
> I am not very good with the whole scancode/key code/X keyboard mapping
> thing, most of my keyboard knowledge is from coding in DOS (scan codes for
> everything), or SDL. Hopefully someone who is knowledgeable will be able
> to point you to the correct answer, but I know the either the .fdi update
> or the setkeycodes solution will work, since I have already used them both
> on the Q1U.
>> Hi Oliver,
>> Thanks for your replies. That solves most of my problems. Few
>> questions/comments interdispersed below.
>> (also, congratulations on this effort, this is a wonderful system)
>>> > - joystick vs mouse:
>>> > It switches between joystick/mouse but does not work as expected. I
>>> can't use
>>> arrows around the enter key as cursors or scrolling up/down while
>>> viewing GUIs.
>>> With mid edition, I was able to use those
>>> > buttons to scroll LR/UD on documents and as cursors in terminal
>>> window. This
>>> is big usability hazard for me since I use this device for reviewing
>>> strange, since MID and Mobile both use hal now with the exactly
>>> same .fdi file, which daily image did you use ? there was one bug for
>>> two days where through a mis merge the Q1 settings moved into the
>>> toshiba section, so didnt work at all ... this issue should e fixed
>> I used one from 10/06/08. I just did a system upgrade (and got a minor
>> bug to report
) but it did not fix this behavior. The upgrades *do*
>> updated to the latest image's quality, don't they?
>> This is still a major irritation for my set-up.
>> -- The upgraded window. In order to debug what is doing on, I had to
>> at the terminal output. The terminal out extends beyond the screen and
>> therefore I can not follow the latest things it did. It froze at some
>> point and I am not sure if that was a major problem or it hanged because
>> of upgrading something that conflicted.
>>> menu is currently mapped to the kernel menu event (which might do
>>> nothing atm) i'll keep that as suggestion for jaunty ...
>>> the external display should work through the screen properties though,
>>> are you sure your external display supports the resolution ?
>>> if you are, that might be a bug worth to file against xserver-xorg.
>> I will check and get back to you. It sounds like a xorg issue to me as
>> BTW, I saw the demo about the screen calibration software you had on
>> blog. The idea looks nice. Let us know if anything we can provide about
>> our devices can be helpful.
>> Thanks again for great work and keeping up with all these questions.
>> Ubuntu-mobile mailing list
>> Modify settings or unsubscribe at:
> Ubuntu-mobile mailing list
> Modify settings or unsubscribe at:
Ubuntu-mobile mailing list
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-mobile