Note: This is the (ongoing) description of the new framework architecture that is in development. See OpenmokoOldFramework for the framework architecture of 2007.1 and 2007.2 and NeoSoftwareStack for the current status (which has nothing to do yet with this framework)

Audio

Gstreamer is to be used for all kinds of event sounds where a) multiple audio formats need to be supported and b) a latency of about one second is acceptable. This goes for e.g. ring tones, welcome tones, plug indication.

Pulseaudio is to be used for event sounds, where low-latency is necessary, e.g. touch click sounds and UI event acknowledge sounds. Pulseaudio is our general all-purpose mixer. Gstreamer will use the pulseaudio sink to feed audio through.

GSM

The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon

GPS

Network

The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:

Network Manager or Intel Connection Manager (undecided yet)

ppp

High Level

Usage

The Usage subsystem is coordinating application I/O requirements preventing. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think reference counting for I/O requirements.

With this added layer, we could later think about monitoring subsystems, subsystem usage statistics, or accounting.

See discussion page about PolicyKit.

Events

signaling events via I/O (ringing, blinking, vibrating)

might use fd.o notification API

PIM

An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description here

Context

Intelligent context API, integrating location as one -- among other -- sources

TBD
Reference Geoclue

Telephony

Voice

Data

Preferences

settings database

Network

high level networking queries

Implementation

Completion Status

Low Level

device control: 50%

audio: 80%

GSM: 80%

Bluetooth: 80%

GPS: 80%

Network: 50%

High Level

Usage: 0%

Event: 0%

Preferences: 0%

Context: 0%

Telephony: 50%

Networking: 0%

PIM: 0%

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 Dbus 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.

(Holger 'Zecke' Freyther -- hopefully joining the team after releasing ASU, working in Berlin, Germany.)

Subsystem Ownership

Phase 1 subsystems

odeviced (mickey)

ophoned (mickey)

ousaged (jan)

oeventd (jan)

opreferencesd (guillaume)

ocontextd (guillaume)

Phase 2 subsystems

network (to be defined)

pim (to be defined)

Roadmap

The milestone releases are combined Openmoko Framework and Zhone releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does not exist. Until Framework 1.0.0 (later this year), we will not use any versioning in components. Afterwards, individual components may see individual releases.

Note: If you have implemented a task, please edit this page and add a '[done]' behind. In the very unlikely event that you can't finish a task for a milestone, then add strike it through and add it to the next milestone. Don't leave it sitting untouched -- poor little feature does not deserve this!

P h a s e O n e

Milestone Release 1 (2008/06/15):

Features

Telephony I

Initiate outgoing call [done]

Accept incoming call [done]

Reject incoming call [done]

Zhone specific

Show operator name (or EMERGENCY ONLY) and signal strength [done]

Show battery status [done, with known hardware limitations on 01]

Dim screen when idle [done]

Suspend/Resume on Power Button [done, not fully tested]

Tasks

odeviced (mickey)

power control for GSM

LED control [done]

idle control [done]

ophoned (mickey)

sim pin handling [done]

network registration handling [done]

call handling [done]

ousaged (jan)

allocate / deallocate resources [done]

oeventd (jan)

change audio scenario [done]

ring [done]

opreferencesd (guillaume)

research and discuss required API [done]

evaluate gconf-dbus API

since gnome people just start to deprecate gconf, check whether there is anything better for us to reuse

Note: This is the (ongoing) description of the new framework architecture that is in development. See OpenmokoOldFramework for the framework architecture of 2007.1 and 2007.2 and NeoSoftwareStack for the current status (which has nothing to do yet with this framework)

Answering the TOP x questions

Question 1: Is this a part of the current images yet?

Answer: No.

Question 2: Is this the mystic ASU?

Answer: No.

Question 3: When can I see this as part of an image?

Answer: See roadmap at the bottom of this document. It's going to be an interesting autumn and winter '08 ;)

Audio

Gstreamer is to be used for all kinds of event sounds where a) multiple audio formats need to be supported and b) a latency of about one second is acceptable. This goes for e.g. ring tones, welcome tones, plug indication.

Pulseaudio is to be used for event sounds, where low-latency is necessary, e.g. touch click sounds and UI event acknowledge sounds. Pulseaudio is our general all-purpose mixer. Gstreamer will use the pulseaudio sink to feed audio through.

GSM

The low level GSM services expect a modem complying to GSM 07.07, GSM 07.05, and assorted GSM specifications, talking an AT-protocol over a serial line. If GSM 07.10 is supported, we use the multiplexing daemon

GPS

Network

The low level networking service assumes network interfaces, such as USB, Ethernet, Wifi, etc. We rely on the following software here:

Network Manager or Intel Connection Manager (undecided yet)

ppp

High Level

Usage

The Usage subsystem is coordinating application I/O requirements preventing. Applications are not supposed to turn on or off devices, since they do not have any knowledge about concurrent applications that may be also using the device -- think reference counting for I/O requirements.

With this added layer, we could later think about monitoring subsystems, subsystem usage statistics, or accounting.

See discussion page about PolicyKit.

Events

signaling events via I/O (ringing, blinking, vibrating)

might use fd.o notification API

PIM

An intelligent storage database server. This is being carried out as a Google Summer of Code project. See complete description here

Context

Intelligent context API, integrating location as one -- among other -- sources

TBD
Reference Geoclue

Telephony

Voice

Data

Preferences

settings database

Network

high level networking queries

Implementation

Completion Status

Low Level

device control: 50%

audio: 80%

GSM: 80%

Bluetooth: 80%

GPS: 80%

Network: 50%

High Level

Usage: 0%

Event: 0%

Preferences: 0%

Context: 0%

Telephony: 50%

Networking: 0%

PIM: 0%

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 Dbus 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.

(Holger 'Zecke' Freyther -- hopefully joining the team after releasing ASU, working in Berlin, Germany.)

Subsystem Ownership

Phase 1 subsystems

odeviced (mickey)

ophoned (mickey)

ousaged (jan)

oeventd (jan)

opreferencesd (guillaume)

ocontextd (guillaume)

Phase 2 subsystems

network (to be defined)

pim (to be defined)

Roadmap

The milestone releases are combined Openmoko Framework and Zhone releases. Remember: A feature that isn't visible, working, and tested in our framework testing application (Zhone) does not exist. Until Framework 1.0.0 (later this year), we will not use any versioning in components. Afterwards, individual components may see individual releases.

Note: If you have implemented a task, please edit this page and add a '[done]' behind. In the very unlikely event that you can't finish a task for a milestone, then add strike it through and add it to the next milestone. Don't leave it sitting untouched -- poor little feature does not deserve this!

P h a s e O n e

Milestone Release 1 (2008/06/15):

Features

Telephony I

Initiate outgoing call [done]

Accept incoming call [done]

Reject incoming call [done]

Zhone specific

Show operator name (or EMERGENCY ONLY) and signal strength [done]

Show battery status [done, with known hardware limitations on 01]

Dim screen when idle [done]

Suspend/Resume on Power Button [done, not fully tested]

Tasks

odeviced (mickey)

power control for GSM

LED control [done]

idle control [done]

ophoned (mickey)

sim pin handling [done]

network registration handling [done]

call handling [done]

ousaged (jan)

allocate / deallocate resources [done]

oeventd (jan)

change audio scenario [done]

ring [done]

opreferencesd (guillaume)

research and discuss required API [done]

evaluate gconf-dbus API

since gnome people just start to deprecate gconf, check whether there is anything better for us to reuse