Slashdot Mirror
No More OpenMoko Phone
TuxMobil writes "Bad news for FreeRunner fans: development of the first Open Source smartphone will be discontinued. (English translation via Google)
OpenMoko executive director Sean Moss-Pulz said at OpenExpo in Bern (Switzerland)
that the number of staffers will be reduced to be able to stay in business. OpenMoko
had high intentions: the offspring from Taiwanese electronic manufacturer First International Computer (FIC)
wanted to produce an Open Source smartphone. Not only with Open Source software pre-installed, but with
free drivers and open specifications of the hardware components. This would give programmers as well
as users complete freedom. Up to now the manufacturer has produced two models, the first has sold 3,000 units and
the second one 10,000. Both models were targeted primarily to developers. From the beginning,
OpenMoko had to fight with different problems. The smartphones came onto the market after a huge delay. Some phones
came with construction defects. Also, changes in the team slowed down the development. Software development
for the current smartphone will be continued but with fewer resources, Moss-Pultz said. He still hopes the
community will support the FreeRunner."
If sales reflect demand it appears that Joe Public doesn't see the value of an open source smart phone.
Man blir trött av att gå och göra ingenting.
I would have bought one but they sold out very quickly. I assume they kept production runs short to reduce risk. But doing that guarantees failure. Lately I have been checking back on openmoko.com from time to time. There is no way to buy the phone on line, and the nearest dealer to me is in India.
Its not like they made millions of the things and couldn't sell them.
http://michaelsmith.id.au
The problem was that the phone had some real glaring problems that were never resolved. Such as a one day battery life. And the inability to charge the phone after the battery wore out completely.
I was going to be first in line to buy one when the power management problems were sorted out. But years later... they were still there. I'm really saddened that the phone never truly got the support it needed to succeed.
So where does that leave us for free phones?
Having open source does not alone make a product awesome. However, one thing having open source does is make it so, even if the product fails, the knowledge put into making that product is not lost. And that's pretty awesome.
If sales reflect demand it appears that Joe Public doesn't see the value of an open source smart phone.
Since when did Joe Public ever do a good job of looking after his own interests? "Freedom? Who needs that? Ooh, look, something shiny and new!" People like this cannot possibly sustain an open, non-dictatorial government for the same reason they cannot sustain an Open Source phone. I know those two things may seem unrelated but if you understand one, you understand the other, for the principle in question is quite scalable.
The problem was that the phone had some real glaring problems that were never resolved. Such as a one day battery life. And the inability to charge the phone after the battery wore out completely.
I was going to be first in line to buy one when the power management problems were sorted out. But years later... they were still there. I'm really saddened that the phone never truly got the support it needed to succeed.
So where does that leave us for free phones?
Makes me wonder how many good ideas are ruined by poor implementation. I'm betting this is a very large number. The problem is that people throw out the baby with the bathwater and so they might conclude that open-source phones are inherently a bad idea, instead of concluding that this group failed to design/produce them correctly.
It is a miracle that curiosity survives formal education. - Einstein
As a pissed off Freerunner owner I have this to say -
OM has been badly managed for some time now. Rather than concentrate on getting basic functionality going they wasted time and money doing things over and over and over again. They must have reinvented the wheel at least three times by now.
No disrespect to the developers, but OM the company was a failure. In what they did and in how they failed to communicate properly with their community, ultimately ensuring there wasn't much of one.
The only hope I have for getting a useful device out of the freerunner now is the (independant of OM) Android port.
The GP has a valid point. Sure, OpenMoko dying is sad. But to people writing open source software who *also want their software to be used by people*, there are important lessons here. Listen to users. Prioritize so that basic functionality (oh, I dunno, battery life) is working before getting carried away with GUIs, etc. Aim at a user community which is not just developers from day one if you want a product that non-developers can later use. Too many projects act as if being open-source is the most important thing that matters for success, and this just leads to wasted effort within the community.
If you RTPT (read the poor translation) they are laying off some employees and putting the ones that are left to work on a different electronic device (it didn't say what) that has been under development. They will continue to sell the freerunner and that they eventually want to return to mobile phone development. They hope that independent developers will continue to work on the phone in the meantime.
Take the cheese to sickbay, the doctor should see it as soon as possible - B'Elanna Torres, "Learning Curve"
"Ideas" are worthless. Everybody has good ideas. It is actually implementing the idea that is the hard part.
In other words, the money (and the devil) is in the details.
I've not really followed this project, but aren't the design documents public? If so, some other company could pick this up and run with it, no?
With the advent of Android on Linux, OpenMoko can safely retire. There will be a flood of Android hardware out soon in addition to the G1 and at least some of it will be hackable or open enough for developers to delve into the stack if they want. For example, you'll be able to improve the hardware drivers, add functionality left out by the original makers because they feared patent infringement, and take advantage of hardware acceleration that didn't make it into the shipping product. Perhaps the only sacrosanct portion kept off limits will be the radio stack itself, which if hacked could invalidate the CE mark, FCC, GCF, PTCRB, etc.
I bought a Qtek 9100 (aka HTC wizard) some years ago (~4~5). It came flashed with wm5.
Guess what? Qtek is killed, the official firmware updates went from a very reduced quantity to null.
So, right now - Zero support.
Fortunately there are groups of people constantly cooking their own ROMs with updated stuff.
www.xda-developers.com
Although, rom cookers have a hard time looking for a way to flash these phones that are usually locked down.
For those looking to have Linux on their phone, (I found http://linwizard.sourceforge.net/ for the HTC wizard and I'm part of the development team for a long time now) the task is even worse, there is absolutely no documentation about the hardware.
My point is that with opensource hardware, if the vendor dies, "supporting" the device by the community is much easier.
You realise of course that this was the real-life GNUphone.
...
The Free Software Foundation (NASDAQ: RMS) has announced the Free Software alternative to the evil, DRM-infested, locked-down, defective-by-design iPhone: the GNUPhone.
The key technical innovation of the GNUPhone is that it is completely operated from the command line. "What could be more intuitive than a bash prompt?" said seventeen-year-old Debian developer Hiram Nerdboy. "The ultimate one-dimensional desktop! Just type dial voice +1-555-1212 -ntwk verizon -prot cdma2000 -ssh-version 2 -a -l -q -9 -b -k -K 14 -x and away you go! Simple and obvious!"
The phone will also serve as a versatile personal media player. "I can play any .au file or H.120 video with a single shell command! The iPod could never measure up to this powerful ease of use." Video is rendered into ASCII art with aalib. "If blocky ASCII teletype softcore pinups were good enough for 1970s minicomputer operators, they're good enough for you. Respect your elders."
The KDE project will be bringing its next-generation KDE 4 desktop to the GNUPhone. "you can flip, twirl, dice, blend, fold, spindle and mutilate your terminal windows to your heart's content," said developer Aaron Seigo. "look at that cool effect! any complaint that basic functions don't actually work is ignorant of the intrinsic beauty of the plasma api and is just more fun spread by haters like stevie ray vaughan-nichols and novell corporation."
Actual successful voice calls are expected by 2011 to 2012. Regulatory approval is proving problematic in the corrupt, corporate-captured US environment. "The FCC said that if we dared switch on this, uh, 'piece of shit' in a built-up area in its present form, they'd break all our fingers with a fourteen-pound cluebat," said Nerdboy. "They're obviously shilling for Apple, Nokia and Microsoft."
The second version of the GNUPhone will run EMACS on the HURD kernel and be operated by writing eLisp macros on the fly. "It's the clearest, most elegant and natural operating environment anyone could conceive of," said Nerdboy. "Really, we're not out to destroy Apple; that will just be a completely unintentional side effect."
http://rocknerd.co.uk
The Buzz generated by OpenMoko was huge; several people at my work were just waiting for something that could be used as a phone before they purchased one. We waited three months, then six months, and then finally gave up expecting anything. That was a year and a half ago.
I got the Neo 1973 and used it in my autonomous boat project, as it had GPS, GPRS, could run Python and connect via USB to many types of devices. At this point while late there was still some promise.
One issue was the desire to please the techies. In order to be a real success it would always have needed to operate well as a phone. It never really achieved that. I would have preferred to see development limited to providing basic phone functionality first, then once that was stable extending it.
Instead it seemed that the Neo became a techie plaything, which was cool for me wanting a small device for my robotics, but not so good for a company trying to compete in the phone market where millions of units are sold. OpenMoko didn't deliver working software. The first rule of Open Source is to deliver something that works early.
Although there is a community around OpenMoko I suspect it will move to platforms that have a real future on mobile devices now. The Android platform may not be perfect yet, but it holds far more promise as a polished product that techies can extend, yet is still a viable mass market phone.
Personally I feel that Sean was too idealistic, and that OpenMoko needed someone stronger that could make some hard headed business decisions rather than making decisions that would see the total reworking of the platform when the first one wasn't even working.
I am very disappointed that such a great opportunity has failed because those in charge misunderstood that the tech people were his market. Certainly a healthy community is a good thing, but you can't create a polished product by trying to please every man and his dog.
Reposting from http://lists.openmoko.org/pipermail/community/2009-April/044915.html
Sean's speech at ESC about making a 3G device:
Since I worked on the presentation with Sean for the days he was here in
SF, let me give you my view and sean's view. That way we won't get into
some version of the telephone game.
Sean discussed three things at OpenExpo.
1. Our successes.
2. Our mistakes.
3. Our challenges
I won't go over 1& 2 but I'll cover #3 since rasters perception has
a bit of color added to it. Only a tiny bit and he's entitled
to that color commentary, I'll just add what Sean and I, as authors
of the presentation, had as our message.
Our biggest challenge was to make a choice about how to spend the
balance of 2009.
There were two paths:
A: Fulfill our promises on FreeRunner and launch GTA03
B: Fulfill our promises on FreeRunner and launch project B.
We will talk more about project B in the coming months, but these
salient facts should be able to guide any budding executives out there.
1. GTA03 was in constant flux as a design.
2. GTA03 schedule was consequently always slipping.
3. The resources required for GTA03 are 3X those required for Project B.
4. We don't have 3X.
So, we picked plan B.
Now comes the question, what about GTA03? how do we get there? And when?
and what is it?
Well my basic argument was and is this:
First we attend to the issues that still remain with the GTA02. That's
why the VP of marketing ( of all people) is working on the buzz fix
problem. Second we complete project B. When we've done that, then we
get to eat dessert. Essentially, I made the same argument I heard so
many times on this list: "How do expect us to buy a GTA03 when you've
yet to deliver on all the promise of FreeRunner?" And I took the
arguments I heard from disty seriously, "how do you expect us to buy FR,
when GTA03 is right around the corner?" And I accepted the arguments I
heard from Engineers I respect who questioned the viability of the GTA03
in the market place. All of those arguments said "put a bullet in its
brain pan!"
So, what about GTA03? As it was defined, it is dead. So how do we
get to a new GTA03? Two requirements: continue to improve GTA02; deliver
on project B. What is GTA03 and when do we get there? There are a number
of independent efforts out there that are pitching me ideas for GTA03.
I talked to sean a bit about this and I'd like to try to open up more
of the design process and the marketing process to the community.
Perhaps on a separate list. Some of these discussions have already started.
What can you do to help?
1. Move GTA02 code upstream.
2. Stay Involved.
3. Continue work on applications
4. Buy a FreeRunner.
5. Get involved in GTA03 discussions
No, I'm sorry, but now you can just fuck off too.
The "GPL is viral" meme was lame ten years ago, the fact that you still spout it now is basically proof of mental deficiency.
OM was developed by a company full of people that also get up and go to work every day.
It was managed badly. That has nothing to do with the license. Grow up.
This has not been such a good year for open hardware projects. First OLPC, and now OpenMoko. I would say that both projects may have been overly ambitious, and were certainly poorly managed. I wonder, what will be next? OpenPandora? Can anyone list any successful open hardware projects?
See,
If it was me running that company, I'd be pimping it to these guys. Give them a phone you can mod the shit out of, you'll get sales.
Now, in order to do so, you'd have to realize those guys aren't developers. They know just enough programming to get into trouble. Therefore, "open source" isn't what they want. They just want an easy way to bling their phone or run some program their cell phone company won't let them. That is their pain, and something like OpenMoko could have cured it.
Granted, if you ever wanted to expand outside that niche market, you'd have to cure pain felt by a lot of people. Most people don't mod their phone. However, I'd bet a lot of people are dissatisfied with how restricted their service seems. You'd have to do something to lessen that pain.
This is a means to an end. You don't sell people on the fact it is "open", you sell them on the fact you can use any wallpaper you want. You sell them on the fact they can install games the mobile provider doesn't want them to.