Comparing the Freedoms Offered By Maemo and Android
An anonymous reader writes "Maemo 5 and Android have received a lot of publicity lately, despite the former not even shipping yet. Both have become famous partly for using the Linux kernel, but now that we have a choice, how do we pick one? Is the issue as mundane as choosing your favorite desktop distribution, or is there a more significant difference? This article compares the two from an end user and developer perspective, emphasizing root access and ease of sharing code."
Maemo 5 and Android have received a lot of publicity lately, despite the former not even shipping yet. Both have become famous partly for using the Linux kernel, but now that we have a choice, how do we pick one?
I assume that you'd probably pick the one that you can actually buy. Or you could opt to buy nothing, but that's not really picking one.
"We" don't really have a choice, do we?
If I choose that one, there's a danger that some geek will say, "You don't even know how to pronounce it, you clueless f***!" Big-time pain and humiliation.
I choose the one that will install on the hardware I own. or the one that has the most pro user functions and anti carrier functions...
I.E. mp3 ringtones that are not locked out.
Backgrounds can be any file I choose to upload to it, same as themes. Give me a way to design and upload a look change without makign the carrier rich.
All features enabled and systems in place that keep the carrier from disabling features in the phone or forcing an update to my phone that is crippled.
Allows me to use a voip client at a wifi hotspot to circumvent airtime charges.
there are features on my S60 phone that I dont see anywhere else. If I press end on a ringing call it will SMS that person with a "I'm really busy right now, I'll call you back as soon as I can" That is a ROCKING feature that I dont see on any of these phones.
Finally scripting. I want scripting on my phone. a sequence to happen when number xx-xxx-xxxx calls me.
So I choose whatever empowers me and works on my hardware.
Do not look at laser with remaining good eye.
the N900 gets released 16th November
http://www.product-reviews.net/2009/10/22/nokia-n900-uk-release-date-pushed-back-to-november/
It pays to be obvious, especially if you have a reputation for being subtle.
The reason the providers lock the phone to their service (besides profit) is support. They only need to support one variation of the platform. More than that is way too costly. The end user in the U.S. wants support from one place not two. If they didn't do this then the average (idiot) user would hear "this is an issue with your device, contact the manafacturer" and "it is your service provider that is causing your problem, contact them". When you want support, you don't want to chase around to get it.
Athiesm is a religion like not collecting stamps is a hobby.
This is just a blog by someone unknown that is also very light on facts.
He seems of the opinion the Maemo owners will be better treated if the root their hardware because Nokia make it slightly easier to do. The problem is that we do not yet know what Nokia will make you agree to in order to install the gain root privileges application. In my opinion they will make you agree to voiding your warranty anyway so that will put you in the same boat as most android owners.
Even if Nokia do not then most carriers will, and the vast majority of phones are purchased through a carriers discount so the user does not end up paying full price for the handset.
I dont read
Pronounce it 'Nokia smartphone'.
Nerd rage is the funniest rage.
On their website, Nokia says "end of October": http://store.nokia.com/webapp/wcs/stores/servlet/productdetail_10500_10101_-1_10000367
I pre-ordered my N900 through Amazon a few weeks back. I figured it'd be easier to get Android working under Maemo than the other way around.
Also, Maemo has a pretty long history of development. I was actually planning on buying an N810 a few months ago until I found out that the N900 might actually have a decent GPS.
Plus, Android phones will be cheap and easy to come by... so hopefully I'll get one for my wife and get to play with it there. But what I've always really wanted in my pocket was a little debian box, and the N900 is pretty much the first thing that fits the bill in that respect. I could care less about the smartphone bit, other than the network connectivity, and of course the fact that I shouldn't need to carry a separate mobile phone around with me anymore.
I played around with Familiar linux (from http://handhelds.org/ ) on an old IPaq for a while, but it was always a bit frustrating that the hardware support wasn't completely there. So it shouldn't be too hard for Nokia to improve upon that experience :P
I really do hope Google caves in to the demand for a native google maps / google earth application on the Maemo, though.
That's the UK release date. For US, it's supposedly the end of October, but I'll believe it when I see it.
screw "send to voice mail". I want the phone to *PICK UP*, play one of a selection of pre-recorded messages, and then allow the caller to press a button if they really really want to interrupt, or answer the question in the message. 200MHz on an ARM is plenty of power to implement this.
- unfettered access to the linux subsystem (ie, need adblocking? You can replace /etc/hosts with an ad/malware blocking version! You can patch many aspects of the phone this way, go check out the patches on precentral)
- if you are a web developer (html, css, javascript), you already know how to write code for this phone. It's that easy. The SDK is freely available, and RUNS FINE ON LINUX. No need to keep a windows box around just to write some phone apps.
- like all the other apps, controlling the US is also done via javascript. Many features can be unlocked just by uncommenting some code.
- and for just plain old users... the interface is very clean, consistent, and beautiful. It stays out of your way. Some of the included apps aren't as powerful as they maybe should be, but that is what the openness of the phone and the homebrew community is for.
This article seems to push pretty hard for an OS that hasn't been getting a whole lot of press. That being said, I'm not sure Maemo is in a position to take on Android.
First, consider the fact that "anything that can run on a desktop can run on Maemo". This sounds like an incredible freedom, but it makes me wonder how much care and innovation went into their mobile framework for developers. Android goes out of its way to provide access to everything a mobile developer would care about: text messaging, the camera, open GL surfaces, the sensor controls... even core functionality can be completely replaced. Want a new home screen? Want a new dialer? Their Activity and Intent framework is very well designed to accomplish anything you may want to accomplish on a *mobile device*. If the Maemo is all about putting a desktop computer in your pocket, I'm not sure how convenient that will be for mobile developers.
Second, consider market penetration. Android is showing up everywhere: phones big and small, net books, GPS devices and e-book readers. Maemo is on one device. Nokias phone. Sure, it may end up on more devices in the future, but will any of these devices *not* be a Nokia? Maybe. Google has done a lot of pushing, however, to give Android visibility. Google has done a lot to cater to developers. They even went as far as releasing the operating system and an emulator for developers to get started before an actual device ever hit the market. Android is going to see more market penetration than Maemo, if not only because Google is going out of its way to make it accessible.
Third, what does their content model look like? Do they have a market application? How difficult is it for developers to publish apps? How do they safeguard against malicious software? Android has a very accessible market. Securing their very open market is a strong permission model, which allows developers to write the code they want to write, without getting their hands slapped (unlike the iPhone experience). I don't know what content model is in store for Maemo, but it will need to be equally well thought out.
In conclusion, I applaud Nokia for taking one further step in the direction of openness. But I'm not convinced that Maemo can stand up to Android. "Super open!" and "desktop like!" aren't going to win the mobile war.
Can land lines receive SMS where you live?
I don't know about now, because I haven't had a landline for a while, but they definitely could back in 2005. The text of the message was read out by a voice synthesiser and you had the option to replay it when you received an SMS. This is in the UK, so it may be different in other places. They occasionally get celebrities to record the voice samples used for the synthesis. For a while, Tom Baker was doing the voice, so it sounded like you were being sent a message by The Doctor.
I am TheRaven on Soylent News
From my personal opinion Android simply doesn't stand a chance. While Android does run Linux kernel it doesn't have X Window etc. It's glorified java platform that doesn't even support full java spec. You can do anything with it, but things will take a lot of work.
Maemo on the other hand is what I see as a 'real' Linux platform running software stack which makes it pretty trivial to port existing apps to it.
Stuff I currently run on my N810:
-Real browser looking firefox with flash support
-MPlayer for playing nearly any format I can throw at it...
-Gnumeric for spreadsheets
-Battle for Wesnoth, Beneath the steel sky, Duke Nukem 3D when I feel like playing something
-Vnc server & client
-Gjiten for translating stuff to Japanese. Japanese symbols display nicely etc.
Only thing I'm really missing is the phone functionality. Even if the only improvement to N900 would be adding that, I would be happy. Adding processing power etc. makes it a must buy for me.
are an illusion. so long as either device you buy is tied to a draconian carrier its just another big ass phone screwing up the line of my pants and sucking down 5 hours worth of charge time in 3 days. the phones may be free, but their features, options and abilities will quickly be restricted at the carrier level.
A phone with freedoms is a phone that doesnt require service contracts or "new every 2" plans for hardware. Its also a phone that lets you question and subvert greedy carrier tactics and, god forbid, gauge and monitor a carriers network performance independently from their own claims of most reliable and most coverage. buy either one, but remember the freedom stops after the transceiver driver comes up.
Good people go to bed earlier.
all the features you mentioned are available with windows mobile.
Additionally, you get a lot of nice extra features, like random restarts, battery monitor that always reports full battery, battery that lasts 1 full day when you're lucky, touchscreen that sometimes responds to your touch (sometimes even to do what you want it to do!), apps that cost much more than I am willing to pay and don't do what I need, plus a generally clunky and inconsistent UI.
I have a windows mobile phone and I will NEVER make that mistake again.
And before I get flamed: I know, many of the problems I have are specific to the device, not to windows mobile, so I have also blacklisted LG for my next purchase. Still, the OS makes you feel like it's windows 98 all over *shiver*.
Ringtones are not public performances. Here, have an article from an obviously biased but generally honest source: http://www.eff.org/deeplinks/2009/10/court-rules-phones-ringing-public-dont-infringe-co
Yes, it really sucks to have a mature system that supports remote display (want to run CPU-intensive apps elsewhere and display on your portable? Want to run apps on the portable and display them on a bigger screen?), is compatible with most UNIX GUI software written since the mid '80s, supports compositing, OpenGL, accelerated text rendering, and cleanly separates policy and mechanism so that window and compositing management can be easily swapped out and replaced.
You know, I am generally happiest when my machine is running an X server as the native environment - things just felt too awkward trying to run X apps on Mac OS X for instance - and I don't think X is as bad as people make it out to be...
But, on the other hand, I have to say, remote display really is not a priority for me on my phone at all. :) It might be fun to play with from time to time but in general it's not something I think I need.
Compatibility would probably be the main reason I'd appreciate Maemo's X server. One of the things that always drives me crazy with PalmOS is that it was always so much damn work to port things to it. Some of this work is unavoidable - when you're working with a small touchscreen display as your main interface, some of the UI assumptions that would go with a 1600x1200 display with a three-button mouse don't apply... To have a reasonable UI it has to be tailored to fit the small display and the precision limitations that go with a touchscreen (especially a resistive touchscreen operated without a stylus...)
Bow-ties are cool.
Hey AC, The lawsuit was a cease a desist on including copyrighted software in his releases. Namely Gmail and other Google Apps.
Half of writing history is hiding the truth.
None of the metrics really have anything to do with the average user.
1. Freedom from crashes. random, and forced resets.
2. Freedom to find the applications that I want to run without having to write them myself.
3. Freedom from having to learn a complex and inconsistent UI.
Most smart phone users really want and need a good smart phone first. Most users will never want to root the phone. How free and open a consumer software system is of little concern if it is not functional. I would love to see Android and Maemo put in the hands of a new smart phone users that doesn't know FOSS or the GPL from a hole in the ground just to see how functional they are. I would also like to see a comparison of the SDKs from a programmers point of view. Finally we can talk about how "free" they are. All of that is important but usability really is very important and it wasn't talked about in this story at all.
I have yet to play with Maemo but my next phone will probably be an Android device. I don't want to be on the AT&T network so the iPhone is out. WinMo doesn't really thrill me, and the PalmOS still lacks voice dialing and video recording. My wife loves her PalmPre but I am disappointed with the SDK and the fact that it still lacks video recording and voice dialing! MY STINKING SANYO FEATURE PHONE CAN SHOOT VIDEO AND DO VOICE DIALING.
Right now I am torn between the Samsung Moment and the HTC Hero I just hope that we see them get 1.6 and 2.0 updates very soon.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
You know, it's just one trade-off and it might not be much worse than linking C++ dynamically... Or Jitting Java byte code.
I have owned an Agenda VR3 and a Zaurus. I can tell you that there are many ways to wast CPU cycles and that in any case it takes effort to avoid them. The Agenda guys spent a lot of time trying to optimize the binaries and resolve issues caused by C++. They might have had an easier time coding in Python and avoiding C++. Or not. It's a complex issue, so it's hard to say even now after the dust has settled.
I don't think there is any silver bullet nor that Javascript, Dalvik or C++ are bad per se. What matters is the effort that the makers put into integrating the software and the hardware, testing, optimizing etc.
The Pre uses the V8 Javascript engine and it might be more efficient to jit a few tens of lines of Javascript than to link a C++ binary with all kinds of libraries (say stdc++, qt, X11 etc.).
Also, I remember that programming in GFA Basic and running the programs on my 8MHz Atari was quite fast actually. So why would it be such a mistake on Palm's part to use Javascript on a machine that is about 500 times faster (the fastest instruction took 4 clock cycles on the 68k)?
I think the Pre is really interesting as almost everything in it is Open Source (V8, Webkit, Linux etc.), based on standards (HTML, Javascript). Also people seem to be able to compare it with the iPhone without laughing so it must be a rather good integration of hardware and software too...
Anyway just my 2 cents and an occasion to fondly remember the gadgets of my youth ;-)
Sadly, I think it's November for everywhere.
http://talk.maemo.org/showpost.php?p=355093&postcount=423
The next site to slashdot will be ready soon, but subscribers can beat the rush and start slashdotting it early!
Built in on Windows, MacOS.
Built in on every web browser.
Built in on virtually all smartphones.
Available as Spidermonkey on Unix systems.
It's pretty much everywhere already. It'll replace most of the others; perl, python, ruby as the libraries and VMs available for it improve.
That's a lovely poem. Really. The Vogons would absolutely hate it.
Being a good scripting language is all well and good. That doesn't make said scripting language a good choice for an embedded platform.
Bow-ties are cool.