preserving illume keyboard on update

Carsten Haitzler (The Rasterman) raster at
Mon Aug 25 03:01:21 CEST 2008

On Sun, 24 Aug 2008 01:53:47 +0200 Jelle De Loecker <skerit at>

the whole keyboard thing is a mess right now. illume has one - that seemingly
people want. qpe has one that om wants. illume provides a gui config to turn
it's keyboard on and off or launch a 3rd party vkbd app and use that. this gui
is turned off by om and pretty much permanently inaccessible. qpe doesn't
provide any way to say "yes" or "no" to getting its keyboard up. so basically
qpe is playing the game of "take my keyboard or dont use qpe" right now, and
illume is playing the game of "do what you want - i have config for that", but
that game is pretty much inaccessible.

there is a dbus call you can use to fiddle with some config but that
incantation needs a dbus session key (so you'll need to steal it from a running
session or do this with a terminal on the FR itself), but this still will only
affect illume and do nothing about qpe.

this all needs to be resolved and so it'll be a mess until it's cleared up. the
wiki is not really correct - it's well behind any development and it's not
really understanding how the keyboard works, but that has been changing rapidly.

> There is a script on the wiki which enables you to install the full 
> qwerty keyboard, unfortunately the last file gives a 404, which makes it 
> rather useless.
> Is there a way, other then recompiling it, to get the good keyboard back?
> How does one get a dictionary for their own language, anyway? Or how do 
> you get an Azerty keyboard?
> /Met vriendelijke groeten,/
> *Jelle De Loecker*
> Kipdola Studios - Tomberg
> Russell Sears schreef:
> > VictorSigma wrote:
> >   
> >> I currently have the 20080823 openmoko-qtopia-x11-image-om-gta02.jffs2
> >> image flashed on my freerunner and it is working great. The problem is
> >> that it originally comes with the illume keyboard pre-installed but
> >> whenever I 'opkg update' the keyboard is changed to the qtopia version. Is
> >> there anyway to preserve the illume keyboard or reinstall it after the
> >> update?
> >>
> >> thanks
> >>     
> >
> > rasterman explained this already.  qpe (the monolithic binary blob that 
> > makes phone calls) is hardcoded to start up its own keyboard.  If qpe 
> > registers its keyboard first, then you don't get the illume one anymore.
> >
> > I think the fix is to break disable the qpe keyboard somehow.  I've 
> > tried breaking it's config file, but that crashes qpe, breaking phone 
> > calls...  I got a bit further than that, and think I found the code (51% 
> > sure...) that turns the qpe keyboard on, but now I don't have time to 
> > deal with it anymore.
> >
> > If you time to mess with it, consider rebuilding qpe with this patch 
> > removed:
> >
> >;a=commit;h=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04
> >
> > the diff:
> >
> >;a=blobdiff;f=src/server/phone/serverinterface/phonelauncher/phonelauncher_illume.cpp;h=405a0b654e9c34a390d18e3466242de5de1cc53d;hp=623258b15a27a969dd8a0926884792936f41103b;hb=5a1a5204e9a4ace32dca98fdfd3b52b75592ee04;hpb=38d2a3923ef46b12279901e5a5dc4c84aeae5d6e
> >
> > A better approach would add a config option to turn qpe's keyboard off. 
> > The long-term goal is to replace it with the illume one, but OM will be 
> > supporting the qpe keyboard in the near-term...
> >
> > -Rusty
> >
> > _______________________________________________
> > support mailing list
> > support at
> >
> >   

Carsten Haitzler (The Rasterman) <raster at>

More information about the support mailing list