View source for OpenmokoFramework/Status Update 7

From Openmoko

Jump to: navigation, search

You do not have permission to edit this page, for the following reasons:

  • The action you have requested is limited to users in the group: Administrators.
  • You must confirm your email address before editing pages. Please set and validate your email address through your user preferences.

You can view and copy the source of this page:

Template used on this page:

Return to OpenmokoFramework/Status Update 7.

Personal tools
Openmoko Framework Team Status Report 2009.7

Hi guys! This is the seventh Openmoko Framework Team Status update, featuring our sixth milestone release and more.

For the general motivation, the goals, and the way we are doing our work, please see OpenmokoFramework.

Key pages on:

(Other distributions)

People & Organization

You all should have heard by now that the FSO team is no longer under the hood of Openmoko. The current team still consists of Mickey, Jan, Daniel, and Stefan, however we pretty much sail under the flag of now. As such, this is the last official OpenmokoFramework status report -- future reports will appear elsewhere.


All the public DBus API are documented on the official API reference site. XML-API files for generating language bindings are available from the git tree.

The DBus APIs have received little updates and are pretty much considered stable for FSO-1. If your programming language features integrating C libraries, then we recommend using libfso-glib which handles all the details of dbus communication and ensures that the DBus API contract is respected.

Implementations Framework Image -- 'In Transit' (Milestone V.5)

This is the sixth milestone release of the framework and the diagnostic application 'Zhone'. While we announced that we are going to phase Zhone out as phone application, it remains an important diagnostic application, i.e. for GPS and GSM monitoring.

Framework milestones currently ships in the following form:

  1. fso-console-image: An FSO-compliant image featuring no user interface manager.
  2. fso-illume-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume window manager.
  3. fso-zhone-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume and the Zhone diagnostic applications.

Note that FSO milestones are not distributions per se, but rather demonstration images for the middleware release. Real distributions that are using FSO as middleware are:

  • Openmoko 2009
  • SHR
  • Neovento
  • QtMoko
  • Debian
  • Gentoo
  • Several unreleased homebrewn...


A flashable image that implements the APIs, serving as the basis for mobile application development.


Thanks to all our contributors, especially the testers and the people who build stuff on top of the APIs. Thanks, guys: You Rock!

What's new since Milestone V

Note: These are only the highlights. See the gitweb commit logs for the gory details...

  • General:
    • This is the first milestone release incorporating results from our Cornucopia project -- the next generation reference implementation of the FSO APIs, this time in Vala, which compiles to C.
  • fsousaged
    • Completely rewritten in Vala with drastically improved performance.
    • The ousaged implementation (Python) has been deprecated, we strongly recommend integrators to no longer use this.
  • ogsmd
  • ogpsd
  • odeviced
  • oeventsd
  • opimd
  • onetworkd
  • otimed


  1. Grab a uImage and a .jffs2 for your device from's download section.
  2. Flash it to your Neo 1973 (om-gta01) or Neo FreeRunner (om-gta02) with dfu-util.
  3. Boot and wait until the Zhone main window appears.
  4. If the Zhone main window does not appear on first boot or stays with "connecting to dbus..." longer than 1 minute, then please reboot. The base system still has some problems with dbus starting for the first time
  5. Read the FSO UI Tutorial and have fun. Note though that this has not been updated for this milestone yet (which looks a bit differently and has more features).


  • Please provide feedback and comments for the dbus APIs. This is your chance to take an active role into shaping the application programming interface for all your forthcoming cool applications.
  • Focus on using the services. Zhone is a diagnostic utility and not a phone application.
  • The best way to interact with the framework is by exploring the dbus APIs. For this, you can use these two tools, which are already installed:
    • mdbus -- a dbus introspection and interaction utility,
    • cli-framework -- a python dbus command line interface.
  • Before reporting bugs against the framework, please try with cli-framework to see whether it's really a problem of the framework or rather the UI (which gets much less attention from us).
  • If you want to interact with the GSM modem, while the frameworkd is running, you can use mickeyterm -- a MUXer-aware minimal terminal emulator.

Best way to hand us debug logs

  1. log in via ssh
  2. killall python
  3. edit /etc/frameworkd.conf and add to the frameworkd section:
    1. log_level = DEBUG
    2. log_to = file
    3. log_destination = /somewhere/where/you/have/space (preferably SD or NFS, etc.)
  4. Read our documented frameworkd.conf configuration file to learn about the other options.
  5. relaunch frameworkd (/etc/init.d/frameworkd stop; /etc/init.d/frameworkd start)
  6. log in via ssh (yes, again)
  7. export DISPLAY=:0.0
  8. run your favourite client (SHR, zhone, cli-framework, ...)

Attach the logs to the tickets, please.

What's next

  • More work on opimd.
  • Connman integration.
  • Bluetooth4 Networking.
  • FSO 2.0 reference implementation in Vala
  • More Device Support (G1, G2, Palm Pre)

The Team

Mickey, Jan, Daniel, Stefan.