I found why sometimes it failed: missing ldconfig
So when you use a new gui, do :
1) untar it and properly link it
2) log it as root
3) run ldconfig
Then either reset or log out. qtopia will start only if you are not logged in. (think about this feature a safe way to hack) . If your console crashes (or an app hangs) a long press on "record" will open a new one.
I strongly suggest to start up a network connection manually and monitor /var/log/qtopia.log for applications log files. If they crash they'll tell you why in this file. do tail -f /var/log/qtopia.log to monitor it.
Regarding external keyboard, it's mostly working. Today I tested my bluetooth mouse and keyboard.
I only have the following problems:
- redraw of the mouse pointer confuses some apps like freenoteqt
- a/fn confusion (I really need C3000/c1000 files ! I hope someone will provide them)
- the blue Fn button on the stowaway bt keyboard turns light off (my fault - mapped 0x1052 )
- the arrows are rotated
They can be fixed.
On the Gui problems, the only serious remaining bug is the date/clock app. I simply don't understand why it fails. Maybe it must be run as root?
Could testers please concentrate on the console mode bugs? The gui problems will hopefully be fixed with the next release, which will ship with a minimal qtopia 1.5. It will also include a development environment module based on the devimage 1.6 put in the proper places instead of symlinked all over.
PS: I would be interested in any "size reduction" proposal for the base system. 12 Mb is still too much - it should be even more minimal