The thing is, the world still needs a genuinely open smart-phone. OK, you can pull teeth to root your Android phone and install that successor-to-Cyanogenmod-thing, but we're still far from the openness of the PC ecosystem. Remember being able to build a PC from parts bought piecemeal from ads in Computer Shopper, then install your choice of Microsoft DOS, FreeDOS, Windows, Linux, FreeBSD, OpenBSD, NetBSD, DragonflyB…
Mobile hardware is a nightmare. The best thing we have to cope with it, so far, is libhybris. And I don't see things getting much better. All we have is Pyra, the incoming Neo900 and semi-closed Jollas with Sailfish.
Ten years after first shipping Openmoko Neo1973
31–40 of 57 posts
Re: Ten years after first shipping Openmoko Neo1973
#32The thing is, the world still needs a genuinely open smart-phone. OK, you can pull teeth to root your Android phone and install that successor-to-Cyanogenmod-thing, but we're still far from the openness of the PC ecosystem. Remember being able to build a PC from parts bought piecemeal from ads in Computer Shopper, then install your choice of Microsoft DOS, FreeDOS, Windows, Linux, FreeBSD, OpenBSD, NetBSD, DragonflyB…
Mobile hardware is a nightmare. The best thing we have to cope with it, so far, is libhybris. And I don't see things getting much better. All we have is Pyra, the incoming Neo900 and semi-closed Jollas with Sailfish.
Re: Ten years after first shipping Openmoko Neo1973
#33Apple even stole some of the visual design elements. The speaker grill was almost identical: http://gizmodo.com/229243/openmoko-smartphone-did-they-have-...
Openmoko was also promoting the "app store" concept much earlier than Apple, which tried to prevent third party native apps the first year of the iPhone.
From a 2006 linuxfordevices.com article about openmoko (remember this was before the iPhone was unveiled):
"The Neo1973 is based on a Samsung S3C2410 SoC (system-on-chip) application processor, powered by an ARM9 core. It will have 128MB of RAM, and 64MB of flash, along with an upgradable 64MB MicroSD card. Typical of Chinese phone designs, the Neo1973 sports a touchscreen, rather than a keypad -- in this case, an ultra-high resolution 2.8-inch VGA (640 x 480) touchscreen. "Maps look stunning on this screen," Moss-Pultz said. The phone features an A-GPS (assisted GPS) receiver module connected to the application processor via a pair of UARTs. The commercial module has a closed design, but the API is apparently open. Similarly, the phone's quad-band GSM/GPRS module, built by FIC, runs the proprietary Nucleus OS on a Texas Instruments baseband powered by an ARM7 core. It communicates with Linux over a serial port, using standard "AT" modem commands. The Neo1973 will charge when connected to a PC via USB. It will also support USB network emulation, and will be capable of routing a connected PC to the Internet, via its GPRS data connection. [...] Moss-Pultz adds, "Applications are the ringtones of the future." [...] As for additional software components, Moss-Pultz admits, "Quite a lot is there, and quite a lot is not there. We're hoping to change this." In addition to a dialer, phonebook, media player, and application manager, the stack will likely include the Minimo browser [...] He adds, "Mobile phones are the PCs of the 21st century, in terms of processing power and broadband network access. "
Re: Ten years after first shipping Openmoko Neo1973
#34The GTK-based om2007 it came with was a joke, and had already been ditched for EFL (Enlightenment) in om2008 when it arrived. The EFL UI got the job done, but all of the actual 'phone applications (contacts, SMS, calls, etc.) came from QtMobile (QtExtended), so I ended up installing QtMoko (Debian + QtMobile) and have been using it like that for years.
Some annoyances I've had:
- The mic volume inexplicably getting set really low; I seem to remember fixing it via alsa.conf
- WPA WiFi doesn't seem to work in the GUI; running wicd-curses in a console is fine
- Can't manage to get audio out of a bluetooth headset
- The excellent predictive keyboard was ditched in an OS update in favour of a clunky non-predictive one. Apparently this was due to prediction only working well for English; as an Englishman, I was fine with that, but haven't been able to reinstate the old one :(
Re: Ten years after first shipping Openmoko Neo1973
#35They had grandiose visions (mesh networking), but all I really wanted was rock solid calling and wifi. It's actually only recently (last year) that I moved to a smart phone, otherwise I'd happily support an open phone.
Also, I believe the freerunner was not 100% open. My recollection was that both the GSM driver (either firmware or device driver) and the graphics driver (openmoko was unable to open up the source to the device driver although they tried) were closed.
Re: Ten years after first shipping Openmoko Neo1973
#36Earlier quoted context omitted.
The main problem with kde was the decision to rewrite everything for version 4 (and the same goes for gnome 2->3)
They went chasing the eyecandy, but ignored that what really cements a platform's utility is API stability...
Re: Ten years after first shipping Openmoko Neo1973
#37Earlier quoted context omitted.
They went chasing the eyecandy, but ignored that what really cements a platform's utility is API stability...
That's just not true. Most of KDE's 3->4 rewrite was about rewriting from Qt3 to Qt4 for better API and also introducing abstraction layers like Solid and Phonon only and only for the sake of API stability.
If the APIs were stable, there would not be a need to drop one for the other.
Look at the kernel, there have never been a situation where one have to go "sorry, but i only support X+1 from now on".
Similarly, until the 64-bit version, and that in turn was because of hardware not software, one could run binaries from Windows 3.0 (at least) on present day Windows.
That is the kind of stability i am talking about. That is the kind of stability that get third parties to stay with a platform.
Re: Ten years after first shipping Openmoko Neo1973
#38One of the issues in the open-source movement is the complete disregard for UX. Freedom is a noble goal, but I don't care how free your software/device is if I need to be an engineer and spend hours in the command line to accomplish a simple task. Until this changes we won't see much progress of open-source in the real world. For such a phone to succeed it needs to be as easy to use (if not more) as its proprietary c…
What's the "real world" here? Open Source software has made great strides in the mobile and server/datacentre space.
Open source UIs used by the general public, less so sure. But then one could argue that most of the UI frameworks people use these days are open source and written in JS...
Re: Ten years after first shipping Openmoko Neo1973
#39The thing is, the world still needs a genuinely open smart-phone. OK, you can pull teeth to root your Android phone and install that successor-to-Cyanogenmod-thing, but we're still far from the openness of the PC ecosystem. Remember being able to build a PC from parts bought piecemeal from ads in Computer Shopper, then install your choice of Microsoft DOS, FreeDOS, Windows, Linux, FreeBSD, OpenBSD, NetBSD, DragonflyB…
Maybe it's a subjective thing, but it feels to me like we've actually taken several steps back in the last 5 years or so.
Re: Ten years after first shipping Openmoko Neo1973
#40I had a freerunner. It was great if you wanted to show someone the linux bootup text on a tiny screen. It was kinda fun to play with raw GPS data, running xterms and stuff onscreen, and various toy things. But IMHO the change of "desktop" environment about three times during the first year of release was a killer. The platform devs seemed to be switching around massive parts of the lower stack at the time they should…
Getting a GPS fix? Why yes, wait for 2-5 minutes and be ready to lose it at the sight of a building in a far distance...
Call/voice quality was abysmal - short: it was a nice gimmick with big ambitions, but it was not ready for prime time.