OpenmokoFramework/Status Update 7

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Installation)
(What's new since Milestone V)
 
(9 intermediate revisions by 3 users not shown)
Line 21: Line 21:
 
'''Freesmartphone.org Framework Image -- 'In Transit' (Milestone V.5)'''
 
'''Freesmartphone.org 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.
+
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:
 
Framework milestones currently ships in the following form:
Line 29: Line 29:
 
# fso-zhone-image: An FSO-compliant image featuring the X-Window system with the Enlightenment-based Illume and the Zhone diagnostic applications.
 
# 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:
+
Note that FSO milestones are not distributions per se, but rather demonstration images for the middleware release. Real distributions that are using FSO as [http://en.wikipedia.org/wiki/Middleware middleware] are:
 
* [[Om 2009|Openmoko 2009]]
 
* [[Om 2009|Openmoko 2009]]
 
* [[SHR]]
 
* [[SHR]]
Line 39: Line 39:
 
===Purpose===
 
===Purpose===
  
A flashable image that implements the freesmartphone.org APIs, serving as the basis for mobile application development.
+
A flashable demonstration image that implements the freesmartphone.org APIs that can serve as the basis for mobile application development.
  
 
===Thanks===
 
===Thanks===
Line 52: Line 52:
 
** This is the first milestone release incorporating results from our [http://www.freesmartphone.org/index.php/Cornucopia Cornucopia] project -- the next generation reference implementation of the FSO APIs, this time in [http://www.vala-project.org Vala], which compiles to C. For those who write in Vala, we provide a .vapi file for libfso-glib.
 
** This is the first milestone release incorporating results from our [http://www.freesmartphone.org/index.php/Cornucopia Cornucopia] project -- the next generation reference implementation of the FSO APIs, this time in [http://www.vala-project.org Vala], which compiles to C. For those who write in Vala, we provide a .vapi file for libfso-glib.
 
** Added interactive loophole for live or post-mortem debugging via telnet.
 
** Added interactive loophole for live or post-mortem debugging via telnet.
 +
** For people who flash their device very often, we now try to bind mount /media/card/bind-home to /home/root. Just create that directory on your SD-Card and it will be mounted on the next reboot.
  
 
* fsousaged
 
* fsousaged
Line 65: Line 66:
 
** Status report messages are auto-acked now.
 
** Status report messages are auto-acked now.
 
** Refresh network status after suspend.
 
** Refresh network status after suspend.
** Added a cell database.
+
** Added a cell database (This is *not* the final API, but a simple test to make cellhunter data available. Later this functionality will be exposed differently)
 
** Redesigned the low level AT command parser to cope with unsolicited responses woven in solicited responses.
 
** Redesigned the low level AT command parser to cope with unsolicited responses woven in solicited responses.
 
** Improved datacall support.
 
** Improved datacall support.
  
 
* ogpsd
 
* ogpsd
** Reintroduced Ephemeris and Almanac uploading.
+
** Reintroduced Ephemeris and Almanac uploading (~ 16 sec TTFF is possible).
 
** Fixed some bugs.
 
** Fixed some bugs.
  
Line 83: Line 84:
  
 
* otimed
 
* otimed
** Major bug fixes, especially for multi-zone countries.
+
** Major bug fixes, especially for multi-zone countries (use network supplied offset there).
** Improved configurability.
+
** Improved configurability (NTP server IP).
  
 
* opimd
 
* opimd
Line 161: Line 162:
 
* Complete switch to fso-abyss.
 
* Complete switch to fso-abyss.
 
* Connman integration.
 
* Connman integration.
* Bluetooth4 Networking.
+
* Streamlining Bluez4 Networking.
 
* More Device Support (G1, G2, Palm Pre).
 
* More Device Support (G1, G2, Palm Pre).
  

Latest revision as of 16:28, 19 July 2009

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:
FSO

(Other distributions)


Contents

[edit] 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 freesmartphone.org now. As such, this is the last official OpenmokoFramework status report -- future reports will appear elsewhere.

[edit] DBus APIs

All the public DBus API are documented on the official freesmartphone.org 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 of choice 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.

[edit] Implementations

Freesmartphone.org 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:

[edit] Purpose

A flashable demonstration image that implements the freesmartphone.org APIs that can serve as the basis for mobile application development.

[edit] Thanks

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

[edit] 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. For those who write in Vala, we provide a .vapi file for libfso-glib.
    • Added interactive loophole for live or post-mortem debugging via telnet.
    • For people who flash their device very often, we now try to bind mount /media/card/bind-home to /home/root. Just create that directory on your SD-Card and it will be mounted on the next reboot.
  • 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
    • Improved support for the Freescale Neptune modems as appearing in the Motorola EZX series.
    • Fully support the Qualcomm MSM modems as appearing in the HTC smartphone family, including the Touch Pro, the G1, etc.
    • Added support for extended SMS properties, including SMS delivery reports.
    • Fixed MCC and MNC presentation.
    • Relaxed the PDU decoder to deal with sloppy encoded SMS.
    • Status report messages are auto-acked now.
    • Refresh network status after suspend.
    • Added a cell database (This is *not* the final API, but a simple test to make cellhunter data available. Later this functionality will be exposed differently)
    • Redesigned the low level AT command parser to cope with unsolicited responses woven in solicited responses.
    • Improved datacall support.
  • ogpsd
    • Reintroduced Ephemeris and Almanac uploading (~ 16 sec TTFF is possible).
    • Fixed some bugs.
  • ophoned
    • Added Bluetooth headset support.
  • odeviced
    • Fixed heaps of bugs everywhere.
  • oeventsd
    • Bugfixes
  • otimed
    • Major bug fixes, especially for multi-zone countries (use network supplied offset there).
    • Improved configurability (NTP server IP).
  • opimd
    • MAJOR overhaul thanks to Sebastian Krzyszkowiak!
    • added new domain Calls (for phone log functionality)
    • working basics of Contacts, Messages and Calls domains
    • working Update/Delete methods and signals
    • added new backends: SQLite-Contacts, SQLite-Messages, SQLite-Calls with full Add/Update/Delete support and ogsmd-Calls (handler)
    • SIM-Messages-FSO and SIM-Contacts-FSO backends: listen to ReadyStatus and AuthStatus signal to init when possible automatically
    • CSV-Contacts and SIM-Contacts-FSO backends: full Add/Update/Delete support
    • SIM-Messages-FSO: full CSM and message receipts handling
    • timestamps and timezones handling in Messages and Calls
    • merging entries - you can store some data for the same contact on SIM backend, others on SQLite, and it'll be merged by opimd into one visible contact
    • avoid duplicating entries on initing backend second time
    • initing backends automatically at boot
    • work on API - lot of new dbus calls (mostly for configuration)
    • make lot of things configurable
    • more error handling
    • A LOT of bugfixes
  • Cornucopia
    • fsousaged: Completely done.
    • fsodeviced: Completely done & in testing.
    • fsogsmd: Waiting for async. dbus server support in Vala.

[edit] Installation on Flash (for booting with U-Boot or Qi)

  1. Grab a uImage and a .jffs2 for your device from freesmartphone.org'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).

[edit] Installation on SD (for booting with Qi)

  1. Grab a tar.bz2 for your device from freesmartphone.org's download section.
  2. Extract it to a partition on the SD card with the tar utility.
  3. Rename the uImage file in /boot to uImage-GTA01.bin (for a Neo 1973) or uImage-GTA02.bin (for a FreeRunner).
  4. Insert the SD card, boot, and wait until the Zhone main window appears.
  5. 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
  6. 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).

[edit] Feedback

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

[edit] 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.

[edit] What's next

  • More work on opimd.
  • Moving towards FSO 2.0 reference implementation in Vala.
  • Complete switch to fso-abyss.
  • Connman integration.
  • Streamlining Bluez4 Networking.
  • More Device Support (G1, G2, Palm Pre).

[edit] The Team

Mickey, Jan, Daniel, Stefan.

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:
FSO

(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 freesmartphone.org now. As such, this is the last official OpenmokoFramework status report -- future reports will appear elsewhere.

DBus APIs

All the public DBus API are documented on the official freesmartphone.org 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 of choice 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

Freesmartphone.org 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:

Purpose

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

Thanks

Thanks to all our contributors, especially the testers and the people who build stuff on top of the freesmartphone.org 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. For those who write in Vala, we provide a .vapi file for libfso-glib.
    • Added interactive loophole for live or post-mortem debugging via telnet.
  • 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
    • Improved support for the Freescale Neptune modems as appearing in the Motorola EZX series.
    • Fully support the Qualcomm MSM modems as appearing in the HTC smartphone family, including the Touch Pro, the G1, etc.
    • Added support for extended SMS properties, including SMS delivery reports.
    • Fixed MCC and MNC presentation.
    • Relaxed the PDU decoder to deal with sloppy encoded SMS.
    • Status report messages are auto-acked now.
    • Refresh network status after suspend.
    • Added a cell database.
    • Redesigned the low level AT command parser to cope with unsolicited responses woven in solicited responses.
    • Improved datacall support.
  • ogpsd
    • Reintroduced Ephemeris and Almanac uploading.
    • Fixed some bugs.
  • ophoned
    • Added Bluetooth headset support.
  • odeviced
    • Fixed heaps of bugs everywhere.
  • oeventsd
    • Bugfixes
  • otimed
    • Major bug fixes, especially for multi-zone countries.
    • Improved configurability.
  • opimd
    • MAJOR overhaul thanks to Sebastian Krzyszkowiak!
    • added new domain Calls (for phone log functionality)
    • working basics of Contacts, Messages and Calls domains
    • working Update/Delete methods and signals
    • added new backends: SQLite-Contacts, SQLite-Messages, SQLite-Calls with full Add/Update/Delete support and ogsmd-Calls (handler)
    • SIM-Messages-FSO and SIM-Contacts-FSO backends: listen to ReadyStatus and AuthStatus signal to init when possible automatically
    • CSV-Contacts and SIM-Contacts-FSO backends: full Add/Update/Delete support
    • SIM-Messages-FSO: full CSM and message receipts handling
    • timestamps and timezones handling in Messages and Calls
    • merging entries - you can store some data for the same contact on SIM backend, others on SQLite, and it'll be merged by opimd into one visible contact
    • avoid duplicating entries on initing backend second time
    • initing backends automatically at boot
    • work on API - lot of new dbus calls (mostly for configuration)
    • make lot of things configurable
    • more error handling
    • A LOT of bugfixes
  • Cornucopia
    • fsousaged: Completely done.
    • fsodeviced: Completely done & in testing.
    • fsogsmd: Waiting for async. dbus server support in Vala.

Installation on Flash (for booting with U-Boot or Qi)

  1. Grab a uImage and a .jffs2 for your device from freesmartphone.org'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).

Installation on SD (for booting with Qi)

  1. Grab a tar.bz2 for your device from freesmartphone.org's download section.
  2. Extract it to a partition on the SD card with the tar utility.
  3. Rename the uImage file in /boot to uImage-GTA01.bin (for a Neo 1973) or uImage-GTA02.bin (for a FreeRunner).
  4. Insert the SD card, boot, and wait until the Zhone main window appears.
  5. 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
  6. 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).

Feedback

  • 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.
  • Moving towards FSO 2.0 reference implementation in Vala.
  • Complete switch to fso-abyss.
  • Connman integration.
  • Bluetooth4 Networking.
  • More Device Support (G1, G2, Palm Pre).

The Team

Mickey, Jan, Daniel, Stefan.