Om 2009 is the next version of the official Openmoko distribution. It is currently under development and should be released in June 2009 to replace Om 2008. It will be based on freesmartphone.org milestone 5.5 framework.
The latest images are under testing.
Updating to the latest uboot or qi is also recommended.
Detailed instructions for flashing.
The image will boot fullscreen into Paroli and all of the features below will be available
Currently Om 2009 is starting its beta phase. Testing builds will be generated into the testing disto.
This page will be updated to reflect the status of Om 2009
Below is the feature list for Om 2009. It's broken down into features that have been implemented and need testing, and features that still need to be finished
phone calls incoming and outgoing
sms incoming and outgoing
simple phone book (no images)
suspend and resume
resume speed < 2 seconds - this is close but waiting on a kernel bug
battery indicator - works for gta02 battery
switch to elementary
scrolling in UI - fixed by migrating from etk to elementary
in-call volume adjustment
Not Yet Implemented or Broken
boot time < 2 minutes - currently examining ways to speed this up
battery indicator - doesn't work for gta01 battery
gprs & edge - works from the command line
user changeable ring tones - works via command line
bluetooth - support in FSO milestone 5.5, needs GUI
wifi - works from the command line, kernels bugs still present
led indication for missed calls or sms
settings tool (feature phone settings as well as advanced functions)
Bug List and Known Issues
Power button does not shutdown device - quick fix copy /etc/freesmartphone/oevents/paroli_rules.yaml to /etc/freesmartphone/oevents/rules.yaml
otimed sets timezone incorrectly in large countries FSO 389
Power status events ignored FSO 381
gsm0710muxd: "Modem does not respond to AT commands" OM 2257
feeds are incorrectly set to unstable
The get persistent logs to a file the a few things need to be changed.
The logging output needs to be set to DEBUG and sent to a file. Edit /etc/frameworkd.conf and change
[frameworkd] version = 1 log_level = INFO log_to = syslog
[frameworkd] version = 1 log_level = DEBUG log_to = file log_destination = /var/log/frameworkd.log
Now to have persistent logs, ones that remain after a reboot, the /var/log symlink needs to be turned into a directory
rm /var/log mkdir /var/log
Your log files should now be full of information and remain there after a reboot.