Ticket #1654 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

[illume] Manually showing and hiding the keyboard.

Reported by: kenrestivo Owned by: openmoko-devel
Priority: highest Milestone:
Component: unknown Version: GTA02v5
Severity: major Keywords:
Cc: raster@…, will@…, vysny@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:


I was delighted a day or to ago when I opkg upgraded and it added a neat new feature: a "qwerty" button appeared in the pull-down menu, and I could click on it to get a keybaord anywhere I needed one! So VTE and minimo were finally useful.

I opkg update; opkg upgraded today, and that feature is gone!

Please bring it back! I loved it. It finally made the FR useful for me. Now it is not again.

Change History

comment:1 Changed 11 years ago by zecke

  • Status changed from new to closed
  • Cc raster@…, will@… added
  • Resolution set to community
  • Summary changed from Qwerty keyboard launcher in ASU to [illume] Manually showing and hiding the keyboard.

I'm trying something new here. I close this bug as "community". It is a design decision by our product manager to not be able to manually show/hide the keyboard. This has been discussed on openmoko-devel (or distro-devel) and the community mailinglist. We engineer's raised our concerns, at the end of the day PM decides.

It is technically possible to change the illume-theme to include the QWERTY button as of now we will not do this for ASU.

comment:2 follow-up: ↓ 6 Changed 11 years ago by queen6

Hi Kenrestivo,

I found this one on the community mailing list:

What you need to do is change your opkg
feeds to use http://downloads.openmoko.org/openmoko-repository/ASU/
which has all the new packages (including an updated version of qpe with
keyboard support enabled). You can download the correct config files from:


Just move /etc/opkg to /etc/opkg-backup then unpack that to /etc,

then: opkg update && opkg upgrade && /etc/init.d/xserver-nodm restart

The keyboard should now pop up automatically when text areas request it.

Once you do it, you will get your qwerty keybard option (dunno for how long though).

Opemnoko team:
I can't understand that decision, but it doesn't matter here. Could you please publish "official" instruction how to enable this button manually and stick it to the wiki (maybe even opkg package to make life easier)?


comment:3 Changed 11 years ago by olberger

  • Blocking 1778 added

(In #1778) Replying to olberger:

At reading https://docs.openmoko.org/trac/ticket/1778 I tend to understand that this is a design decision of the product manager that lead to that situation.

Hence, I guess it may be solved if ticket 1778 was "solved".

Uh... wrong copy/paste. I meant tocket #1654 in the 2 above. Sorry.

comment:3 Changed 11 years ago by olberger

  • Status changed from closed to reopened
  • Severity changed from normal to major
  • Priority changed from normal to high
  • Milestone set to OM-2008.8
  • Resolution community deleted
  • Blocking 1778 removed

There are lots of complaints about this on the users side.

We paid for the device, we're concerned, I guess we can ask for its reopening.

comment:4 Changed 11 years ago by olberger

  • Blocking 1778 added

comment:6 in reply to: ↑ 2 Changed 11 years ago by olberger

  • Priority changed from high to highest
  • Component changed from unknown to Assassin
  • Milestone OM-2008.8 deleted

Replying to queen6:

Could you please publish "official" instruction how to enable this button manually and stick it to the wiki (maybe even opkg package to make life easier)?

I guess the instructions are back : it is in http://wiki.openmoko.org/wiki/ASU_Keyboard_Toggle#Method_1 :

opkg install illume-config

comment:7 Changed 11 years ago by billk

  • Blocking 1778 removed

(In #1778) Replying to olberger:

Replying to olberger:

Replying to billk:

If you read the title of this bug, you will see it has nothing to do with showing/hiding the keyboard which is the ticket you are referring to!


With the ability to show the dialog which allows starting a qwerty keyboard, it would become less unusable :

  1. a full qwerty keyboard (a usable one like that in the FSO, or the matchbox one.)

So I guess "fixing" #1654 would help a great deal...

Having just tested the "opkg install illume-config" workaround for #1654, I understand better now that it indeed doesn't address the problem of the full qwerty keyboard missing.
It is a bit more useable as the qwerty keyboard can appear right away at a single tap on the "qwerty" button in the top row, but then, the rest of its limitations are still there.

We indeed need "a full qwerty keayboard", even if it's easier to make it appear/disappear.

Ive removed the block you entered. Please do not put blocks on bugs you do not understand. That bug is irrelevant and from a version WEEKS ago. The bug as it is entered here is that that 2008.8 does not have a keyboard that is usable for anything other than english SMS. If you wish to raise something about a keyboard switcher, please raise a bug to detail THAT problem. In the meantime, I hope you have not confused people so much they ignore this bug.


comment:8 Changed 11 years ago by vyzivus

  • Cc vysny@… added

comment:9 Changed 11 years ago by zecke

  • Component changed from Installer to unknown

Definitely not an installer bug.

comment:10 Changed 11 years ago by zecke

  • Status changed from reopened to closed
  • Resolution set to fixed

And AFAIK people can install packages to get the QWERTZ button and toggle visibility, so the initial complain is resolved?

Note: See TracTickets for help on using tickets.