FSO

From Openmoko

Revision as of 09:56, 5 August 2011 by Quix0r (Talk | contribs)

Jump to: navigation, search
Key pages on:
FSO

(Other distributions)


FSO (freesmartphone.org) is a project to create a standardized service layer (middleware) for Linux-based phones. It was funded by Openmoko Inc. from January 2008 until March 2009. Focus is on stable highlevel services that you can access from whatever language or UI that supports dbus. The FSO middleware has been integrated into most of the current distributions including SHR, Om 2009, neovento, Debian and Gentoo. At the moment FSO only works on the Openmoko phones. There is work in progress for bringing it to the Palm Pre and several HTC devices. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.

Contents

Building FSO

See Building_FSO for more information. The feeds are now at http://downloads.freesmartphone.org.

History

The current progress is documented on the freesmartphone.org website

Purposes

  • Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
  • Support competing UIs while collaborating on developing services
  • Encourage framework users (e.g. application developers) to also contribute to the framework

Requirements

  • Make it simple
  • Concentrate on core services
  • Be programming language agnostic
  • Be UI toolkit agnostic
  • Try to reuse existing technologies as much as possible, but not at the cost of a bad API

How to achieve that technically

  • Choose D-Bus as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
  • Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
  • Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
  • By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

Mandatory Reading

Architectural Overview

frontside

Software Components

Please see the description at http://www.wiki.freesmartphone.org/index.php/Architecture

Known API Consumers

Tools

  • mdbus -- a dbus introspection and interaction utility,
  • cli-framework -- a python dbus command line interface.
  • mickeyterm -- a MUXer-aware minimal terminal emulator.

Scripts

  • Example Scripts that work over dbus

How to debug

  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 (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

The role of Python

Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the D-Bus APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.

Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, if necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.

Team

Download and see also

Personal tools
Key pages on:
FSO

(Other distributions)


FSO (freesmartphone.org) is a project to create a standardized service layer (middleware) for Linux-based phones. It was funded by Openmoko Inc. from January 2008 until March 2009. Focus is on stable highlevel services that you can access from whatever language or UI that supports dbus. The FSO middleware has been integrated into most of the current distributions including SHR, Om 2009, neovento, Debian and Gentoo. At the moment FSO only works on the Openmoko phones. There is work in progress for bringing it to the Palm Pre and several HTC devices. For more information see http://www.freesmartphone.org, http://docs.freesmartphone.org, and http://trac.freesmartphone.org.

Building FSO

See Building_FSO for more information. The feeds are now at http://downloads.freesmartphone.org.

History

The current progress is documented on the freesmartphone.org website

Purposes

  • Give people the infrastructure to create solid and exciting software products based on the Openmoko platform
  • Support competing UIs while collaborating on developing services
  • Encourage framework users (e.g. application developers) to also contribute to the framework

Requirements

  • Make it simple
  • Concentrate on core services
  • Be programming language agnostic
  • Be UI toolkit agnostic
  • Try to reuse existing technologies as much as possible, but not at the cost of a bad API

How to achieve that technically

  • Choose D-Bus as the collaboration line. Below dbus, we can work together. Above dbus, we can differentiate
  • Expose features through dbus APIs implemented by UI-agnostic and language-agnostic services (daemons)
  • Optimize for Openmoko devices, but support multiple architectures and purposes through plugin interfaces and suitable hardware abstraction mechanisms
  • By not being afraid of reinventing the wheel for a wheelbarrow if all the existing wheels are made for sports cars

Mandatory Reading

Architectural Overview

frontside

Software Components

Please see the description at http://www.wiki.freesmartphone.org/index.php/Architecture

Known API Consumers

Tools

  • mdbus -- a dbus introspection and interaction utility,
  • cli-framework -- a python dbus command line interface.
  • mickeyterm -- a MUXer-aware minimal terminal emulator.

Scripts

  • Example Scripts that work over dbus

How to debug

  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 (zhone, cli-framework, ...)

Attach the logs to the tickets, please.

The role of Python

Where we write new code, we will use Python to implement the dbus services. The reason for that being the rapid prototyping nature of Python and the emphasis on the D-Bus APIs. Using Python, the turnaround times to experiment with APIs are incredibly faster than for using a compiled language such as C or C++.

Once the APIs have been used by application programmers, we can start profiling and possibly reimplement some of the services with daemons written in Vala, if necessary. We might as well succeed in improving performance by using Pyrex/Cython/Ctypes to keep the benefits of Python.

Team

Download and see also