Christopher Price is the Founding Editor of Today, he leads the team building Console, Inc. - a new kind of Android™ device. He still likes to pontificate... a lot. You can visit his personal blog at

Google - +ChristopherPrice | Twitter - @chrisprice | LinkedIn

Questions for Chris? You can also reach him by email, but please use the contact form for general comments, questions, and feedback.

26 responses to “Nokia Appears to be Forking MeeGo for the Next Billion”

  1. molbal

    I have an N9 and a Lumia 800, too. I don’t want to anger you, but I prefer the Lumia. It is just faster. I am also typing from that. But I love the N9, too. I think Elop does it right. I like how he still improved Symbian.

  2. Jimmy

    Elop had nothing to do with improving Symbian. Phones are built on three-to-five year roadmaps, everything in Anna and Belle was already being coded before Elop came on the scene.

    I’m not saying WP7 is bad, but Elop sent MeeGo and Belle to slaughter. Belle may have been on the way out, but MeeGo was on the way up.

    Elop is a troll hired by Steve Ballmer to force-feed Nokia to Microsoft at a bargain barn price. Just watch, I doubt we’ll see MeeGo come back before it’s curtains for Nokia. Sad thing is, the developing world will suffer the most from it. Geeks will have webOS and Android to compete with Windows, not to mention iOS.

  3. raul

    elop does right… yeah… his in a path to break nokia…
    elop mantra “nokia only will succed if microsoft benefits, i dont really matter if nokia will succed with android, symbian, meego, etc, its with windows or i rather want to bankrupt”

  4. john

    Most of Us Would Rather see nokia Die Than Continue its Current mangled existence as WinKia.

    A Painful Death By A Thousand Cuts. Lets Help Make It Faster By Boycotting All Nokia Phones Running WinMo!

  5. Jed

    “While Nokia has kept its promise to actively develop for MeeGo, nobody else did. Intel, AMD, and other companies outright abandoned both developers and startups that were embracing MeeGo, and dumped it in-favor of the non-realtime Tizen.”

    Stopped reading there…..
    When you’re going to write an article & act like you know what you’re talking about.
    Please at least make an effort to be far better informed.

  6. Jed

    Nokia “did” abandon MeeGo, some of the work it’s done for the N9 does go back into the Qt code-base.
    Elements that they allow to be open, but those elements have nothing to do with real MeeGo.

    The recent PR1.2 update for the N9 has zilch to do with MeeGo Core 1.2 (Vanilla MeeGo).
    The only connection they have, is that small fragments of their UX code-base are shared.
    N9’s MeeGo is more closely related to Maemo5, nowadays it’s often referred to as Maemo6x.
    It also (or at least did) has a MeeGo compatibility layer, so porting between both is less troublesome.
    Real MeeGo for handsets (originally known as MeeGoCE) is now known as MeR (MeeGo reconstructed).
    It uses a UX layer Nokia/others started that’s now called Nemo, it can also use Plasma or Cordia.

  7. Jed

    “but those elements have nothing to do with real MeeGo.”

    Correction, not nothing, they’re of direct benefit to MeR+Nemo/Plasma etc.

    Nokia has made very clear it’s not doing anything on the high-end in the foreseeable future.
    What it may re-use much of it’s N9 code-base (Maemo6x) for, is an oft rumored project called Meltemi.
    This is supposedly stripped-down Maemo6x + Qt5 + SwipeUX & will replace S40 in the low-end.
    It will not be for high-end devices sadly…
    However it sounds like they’re trying to bring a smartphone-like experience to dumb/featurephones.
    Esp. given their recent purchase of the company/platform called smarterphone.

  8. Jed

    When they refer to “the next billion” they’re referring to their dumb/featuerphone market.
    Despite failing abysmally in recent years with smartphones, Nokia’s still doing well in that segment.
    In fact if it weren’t for that segment, Nokia’s entire mobile phone division would be almost dead by now.
    These are their lowest end Symbian phones, but primarily their S40-class phones.
    Nokia has been gearing/optimizing Qt for this segment, & apparently S40 will be replaced by Meltemi.
    So they can begin to “blur the lines” between true smartphones, & dumb/featurephones.
    Ultimately this platform may creep into the top-end, but that def. won’t happen any sooner than 2017.
    Not while Nokia’s contract with MS is in place, & even after that the chances are still quite slim IMO.

  9. elemental

    N9 with MeeGo is superior, and I believe they went with WP7 crap only to survive.

  10. Jimmy

    Wow, Jed, for someone that stopped reading the article after the first sentence, you sure have a lot to contribute!

    I find it funny that your subsequent comments “correct” things to the point that you are basically in agreement with the author of the article :p

  11. Jed

    ^There is some significant incorrect points in the article.
    Try re-reading it, and then try re-reading what I wrote.

    As for my 1st post, it was rude, I do apolgize to the author.
    I must’ve been having a bad hair day….

  12. Craig

    Thumbs up to Jed for apologizing.

    Thanks to all for the technical stuff.

    Got four Nokias this year (C07?.. Symbian), N9 and two Lumia710s.

    The Lumias are sweet and fast. They’re all nice phones. Too bad there wasn’t just a tad bit more support for the N9 and some speed tweeks. No perfect phone yet but there are a lot of nice ones.

    If I could get an iPhone, jailbroken, to run on T-Mo with 3G that would be ideal. Basically, anything but Android (which is also in my pocket.) 😉

  13. Jed

    “Too bad there wasn’t just a tad bit more support for the N9 and some speed tweeks

    Huh? There is still support for the N9….
    There’s already been two major updates and there’s another one on the way.
    The updates have been far more substantial than the updates I’ve received for my L800.
    Whether support will be around for much longer is hard to know.
    But there’s no way one can say there hasn’t been good support “so far”.

  14. Jed

    “I think Craig is referring to platform-based support.”

    Well yes there’s no doubt that support is lacking there…
    In fact “tonnes” is lacking there, given that there’s not a single extra device planned! 🙁

    “which was splitting hairs in their contract/agreement with Intel to “globally” launch at least one MeeGo handset.”

    I never saw evidence that they were bound to release at least one “MeeGo” device worldwide.
    In fact they had a fight with the LF to even be allowed to use the MeeGo name.
    For a long time it looked like the LF may not even let them use the name…

    Never made any sense to me why they even wanted to use the name so badly.
    MeeGo hadn’t been marketed heavily, & what N950/N9 used was more akin to Maemo6x anyway.
    Plus the whole MeeGo name had become badly tainted at that point, so it all made zero sense.

    I think it had more to do with the fact that they’d invested far too much time/resources to simply shelve the whole thing.
    It would be grossly negligent, had they done that…

  15. Jed

    “But, the N9 is 100% MeeGo-based and compatible according to Nokia.”

    It is 100% compatible (thanks to a compatibility layer), but it’s certainly not 100% Vanilla MeeGo, far from it.
    Anyone that’s been involved with MeeGo for the past 2yrs would know that…
    I’m amazed that Nokia would say this to you, but if it wasn’t one of their engineers then I guess we needn’t be surprised.

  16. Jed

    for some reason my larger response is not appearing…..

  17. Jed

    [“Intel acknowledged to that Nokia had, as part of their Memo of Intent (the contract wherein the companies agreed to partner on MeeGo),
    that Nokia would at least launch one MeeGo device.”]

    This agreement is on the public record somewhere for all to see?
    Not saying it’s incorrect, all I said was I can’t recall seeing any iron-clad evidence of such an agreement.
    I’ve certainly seen it written about & speculated on many times etc.

    [“He has said, on the record, that MeeGo would be not be continued by Nokia even if the N9 was widely successful.”]

    They’ve also hinted that they’re still very much focused on developing their own Linux/FOSS-based OS.
    Just not one that’s called “MeeGo” or structured/geared (strategically) in the same way.

    [“If you want to call that grossly negligent, you’re welcome to your opinion…
    supporters of Elop would argue that Microsoft’s investment ($1 Billion) outweighed MeeGo’s market value.”]

    Not sure why you’re bringing that side of the argument into it…
    I was not arguing against the switch the “MS-only” strategy (although a lot can be said there).
    I was simply stating that abandoning it entirely after all that time/resources was never happening.
    As evidenced by the fact that they didn’t….
    Maybe if they’d come to the decision they did earlier it would’ve been feasible.

    [“Nokia refutes the notion that they are not using stock MeeGo. They dispute your claim that “Maemo6x” is what they are using.
    Nokia did take some features planned for its internal MeeGo implementation, and kept them exclusive. But, the N9 is 100% MeeGo-based and compatible according to Nokia.”]

    Well your contacts at Nokia are wrong….
    Go & check all the freely accessible commits & one can come to the same conclusion.
    N9/950 uses a different package management system, the underlying windowing system is entirely different, as are much of the UX components, & it goes on.
    Vanilla MeeGo’s UI components are now freely observable in the MeR+Nemo/Plasma etc distros which it has evolved into.
    The differences are there for all to see….

    The plan was always to have at least 2x primarily Maemo-based handsets before migrating to MeeGo proper.
    But the strategy change occurred well before they got to that point.
    The full switch probably would have occurred w/their 1st x86 handset in about June/July 2012.
    After a third & final Maemo6x device had been released (which would be shipping by about now).

  18. Alan

    they didn’t release Meego 1.2 earlier this week. The whole software that have been powering the N9 has always been Maemo core with a slapped on Meego 1.2 interface layer – and the end product is namely Meego 1.2 Harmattan.

    What they released earlier this week is PR1.2 aka Meego 1.2 Harmattan 1.2 (yes I know what I am talking). This is the third public release of the Meego 1.2 Harmattan software after PR1.0 and PR1.1….so this is not a dead end yet, Meego 1.2 Harmattan 1.3 is already in the pipeline (PR1.3), but keep fingers crossed whether there will be a PR1.4 or PR1.5…I guess that will all depends on the sales volume of the N9.

  19. Jed

    The actual UX layer is also quite different to Vanilla MeeGo.
    Elements of what into Vanilla MeeGo ended-up in Maemo6x (MeeGo-Harmattan) & vice versa, but they’re still quite different UX-wise.
    If the project was still going, then in about 3mth every new phone from then on would be using only Vanilla MeeGo & it’s UX.

  20. Why is Nokia Still Working on MeeGo? | Netbooknews - Netbooks, Netbook Reviews, Smartbooks and more

    […] Via PhoneNews […]

  21., Nicole Scott Plagiarized Our Latest MeeGo Coverage |

    […] article editorializing on why Nokia is still updating MeeGo… and found entire paragraphs of my editorial inside of it.It’s quite common for people to quote others in their editorials, but this is […]

  22. Nokia working on Two New low end MeeGo Smartphones | Netbooknews - Netbooks, Netbook Reviews, Smartbooks and more

    […] is also a lot more adaptable than Windows Phone, its roots are in open source.  PhoneNews raises some good points around MeeGo, if we think about where the next billion handsets are coming […]

  23. Nokia Reverses Course, Quietly Begins Selling N9 in United States |

    […] years” of support. And two, Nokia appears to be using the MeeGo Harmattan platform to fuel its “next billion” initiative for smartphones in the developing world.And, at $599 sticker price at Fry’s Electronics, […]

  24. Nokia’s Linux Skunkworks Effort Dies with a Whimper |

    […] its goal was to replace Series 40 at its end of life, empowering smartphones to be cheap, and roll with the punches of a developing world’s harsh limitations in power, cost, and connectivity. Technology […]