OpenMind 2007: OpenMoko - The Truly Open Mobile Phone Platform
I skipped out on the previous session so that I could get my electric plug adapter from my room (and to get a break from typing.) I've come back during the afternoon break and am waiting for the OpenMoko session to start. The room is pretty full - I'm guessing that I'm not the only one who is interested in the project.
The presenter is Michael Shiloh from OpenMoko. Michael helps community developers work with OpenMoko. He's a very clear speaker and his presentation pace is only a bit faster than my typing speed. I'm going to try to transcribe his presentation mostly in entirety.
A handful of people of aren't familiar with OpenMoko and another handful are working with it.
OpenMoko is for any portable device that probably has GPS and a network connection.
Everything is Open Source from the drivers to the kernel.
The hardware itself is as open as possible. You can solder on additional devices and can even reflash the bios.
So, why do we need OpenMoko? Why do we need another one?
Michael points out how little innovation has been happening in the mobile space vs. the Net space.
The OpenMoko folks think that the difference was driven by the fact that the Net was an open ecosystem.
OpenMoko wants to bring this kind of open ecosystem to the mobile space. They believe that a closed ecosystem can't compete with an open ecosystem.
They also think that the diversity of people who like to participate in open ecosystems is very beneficial to creating true innovation.
OpenMoko also believes that there is a kind of circular dependency with devices. A company working on a new device will choose hardware based on what kind of apps should run on the device. This excludes outsiders from extending a device in a way that isn't tied to the hardware.
OpenMoko is trying to ensure that many people are free to extend both the hardware and software.
This openness has allowed the OpenMoko community to discuss the possibility of how one could extend the device, using things like light sensors and accelerometers in innovative ways, such as using the accelerometer to determine when someone is driving quickly and shouldn't be disturbed with a call.
There are barriers to participation beyond the ecosystem.
OpenMoko doesn't have an NDA or restrictive EULA, you don't need to be certified by OpenMoko (or even to have the hardware) to start developing applications. There isn't even special hardware to do things like reflash the bios or program the real device.
When starting with a new project, you have to decide what existing components to use. If you choose generic components, like X11, then you gain flexibility, but you lose performance.
OpenMoko chose to value standard software components over custom components. You lose some performance, but existing developers can use more of their skills to work on the project.
As the OpenMoko team was working on the low levels of the project, they were still thinking about the visibility and prestige of the project.
Keeping this in mind, they tried to make it an attractive device that can be widely distributed, as way to help increase distribution and to give developers feedback and prestige.
There are many community resources - a wiki, bug tracker, IRC channels, maling lists, a Planet OpenMoko, etc.
They wanted to make sure that there is a good channel for getting external input back into the company - one of those channels is Michael.
OpenMoko is a generic mobile computing platform. They don't quite know what this means yet.
Getting
It has a full VGA screen, which is pretty outrageous in a cell-phone saved device (at least until those other guys came out with their device.)
It has GPS, which we think is important.
It should be network capable.
It should be Free Software and Open Source.
It turns out that these things are really complex to deliver.
One key thing is that the device manufacturers don't want to release device drivers under a Free Software license.
Device manufacturers may be afraid of the competitive aspects of releasing the source of the driver.
It might also be that device manufacturers also want to protect their customers. Keeping something private may give the device manufacturer's customers a temporary edge.
It might also just be habit - this is how they did it in the past, why not do it like this in the future.
There are three options for OpenMoko in dealing with device drivers:
* OpenMoko could try to make it so that customers get access to the data sheet so that they can write their own drivers.
* OpenMoko could get the data sheet and then could write the drivers. But this makes lots of work for OpenMoko
* The last option is to have the device makers write the drivers and then distribute them as Open Source. This is least desirable, as - without the data sheet - it is hard to maintain the driver.
The solution was that two of the founders went on a tour to device vendors. In the end, some devices were discarded because a device manufacturer wouldn't provide an open driver.
In the end, they did it. Open WiFi, Open CPU, Open 2/3D graphics, Open 3D Motion Sensors, Open GPS - 100% Open.
At this point, Michael is showing a picture of the chips on the device and notes that you can see all the chips serial numbers and so on - something that is usually hidden on proprietary devices.
They've started shipping devices in July 2007. The first shipment of 1000 sold out in four days. The next one will ship in November of 2007. In 2008, there is a new style of device coming that looks really nice.
The first version that came out was very much a developer edition. It wasn't a working cell phone - but instead a development tool. If this were a proprietary device, then this is a version that would have been given to the internal team of a development company to further refine the device.
Interestingly, magazines have wanted to review it - but it isn't ready for review or consumers, yet.
The next version will work as a cell phone, but it still won't be a consumer-ready device. This isn't due to the hardware, but the software. The software isn't ready for prime-time just yet.
The next devices will be more diverse - they might be something like tablet PCs or have fewer features or whatever.
So, why is OpenMoko better or worse than the iPhone. Well, OpenMoko had no intention of being better or worse than the iPhone. They just happened to come out at the same time and be a bit similar. The line that Michael likes to use now is, "Comparing the iPhone to the Neo1973 (the OpenMoko hardware device) is like comparing a hammer to an apple." It is a tool to use for developing a better end product.
The name apparently doesn't have anything to do with The Matrix. Instead, it is a reference to when the first cell phone came out (in 1973) and how the OpenMoko project hopes that this phone will start a revolution in the mobile device space.
Someone asks about the radio for the phone - is it unlocked. Michael notes that the radio itself is a black box, but everything around it is open source. The issue is that various bits of legislation don't allow devices that can change power and frequency using software commands.
The next question is, "What attracts you most - selling to individuals or companies?" As an individual Michael is interested in having a cool device. As a company, part of OpenMoko's strategy is to develop and sell customized versions of the hardware and software.
A followup question is roughly this, "Who is behind OpenMoko?" OpenMoko was a project of FIC - a big Taiwanese chip maker - that has now been spun off into its own group.
Editor's Note: Holy Jumping Religious Figures - if a Taiwanese chip maker has figured out the Open Source dynamic, some of the remaining chip makers in North America really need to get their act together if they want to not be crushed.
A great session!
Link Summary
Related posts
Posted on Tuesday, October 2nd, 2007 at 3:54
You can follow any responses to this entry through the RSS 2.0 feed.
You can leave a response, or trackback from your own site.One Response to “OpenMind 2007: OpenMoko - The Truly Open Mobile Phone Platform”
Leave a Reply
Comments are moderated. I delete obvious SEO attempts and other content-free comments.
October 11th, 2007 at 9:54
[...] Shiloh's clear and accessible OpenMoko [...]