Video: Nokia N900 and NEMO Mobile snapshot 0.20130218.1.NEMO.2013-03-24.2

| March 27, 2013 | 28 Replies

Screen Shot 2013-03-27 at 21.23.01The last post on the 950 reminded me of this video I watched the other day on the Nokia N900 (note the resistive stylus that pops on the screen every now and again?).

The N900 is running NEMO Mobile snapshot 0.20130218.1, part of the Mer project on MAEMO which otherwise looks like Harmattan to me. I think the resemblance is noted in one of the comments.

Screen Shot 2013-03-27 at 21.28.53

Here’s an older video where it looked more like the old Maemo.

nsuffys

 

Category: Maemo, Nokia

About the Author ()

Hey, thanks for reading my post. My name is Jay and I'm a medical student at the University of Manchester. When I can, I blog here at mynokiablog.com and tweet now and again @jaymontano. We also have a twitter and facebook accounts @mynokiablog and  Facebook.com/mynokiablog. Check out the tips, guides and rules for commenting >>click<< Contact us at tips(@)mynokiablog.com or email me directly on jay[at]mynokiablog.com
  • Grazy

    wow, very cool. I had a N900 (sold for an N9!) I’m impressed! wish i hadn’t sold mine now :) memories! Great phone! way ahead of its time.

    • always wanted but couldn’t get an n9

      swap my n900 for your n9 if you like?

      • Grazy

        nah, I’m not saying i don’t like my N9 :) in fact i still love it and will find it hard to move onto windows!

        But this time i will not be selling!

  • Leroy Stolnholz

    NEMO was also a kind of response of community for idiotic decision not to develop Harmattan any more. Hence was created NEMO 1.3 CE like Community Edition which contained also needed fixes for bugs known or noticed in Harmattan 1.2., that is why NEMO 1.3. As swipe UI was from Harmattan and Nokia owned it was not possible to include it in NEMO. Mer is MEego Reconstructed, with Mer core and tools NEMO project was created hence NEMO simply IS MeeGo, or another MeeGo incarnation. 80-95% of code is MeeGo. In the same way Sailfish OS simply is another incarnation of MeeGo.

    MeeGo is the best, the biggest and the most important achievement in whole the Nokia history.

    Recently China has decided to cooperate with Cannonical, to combine “Kylin”, the Chinese Linux with Ubuntu to create “Kylin Ububntu Linux” for China, as China national OS. Considering how good and deep relations Nokia had in China, eg.: China Telekom was the partner in the MeeGo project, how warmly MeeGo was accepted and how good was community response – because all of this Nokia was more then close to have opportunity to combine Kylin and MeeGo, so to be the co-creator the Kylin MeeGo supported and devoted for China.

    To underline how pathetic all this is you should know that Cannonical is working to use the Mer project (so in fact the MeeGo exactly) and to make Ubuntu compatible on APIs level with Sailfish. So MeeGo, but slightly differed and under another brand will be the China national Linux….

    I love Elop, I adore his infinite wisdom and enlighted management – he is the hero of the howling success of the Nokia. He is our best hope for the Nokia better future and glory. Thank you Mr Elop!!!

    Still can’t understand how it was possible to hesitate a chance to enter China market??? Talleyrand said once: “that was worse then a crime, that was stupidity”.

    Thank you for you attention and cooperation. have a nice day.

    • Trexus

      Wrong. Nemo is based on MeeGoCE 1.3, which has zero to do with Harmattan (AKA Maemo 6x).
      Nemo does not try to fix bugs in Harmattan since this is not possible, as much of the code is closed/proprietary.
      Sailfish is (loosely) based on Nemo + MeR (which is what Nemo also uses)

      you also make many other completely incorrect assertions, such as the claim that ubuntu uses MeR, it does not.
      It started-off loosely based on cyanogenmod, but has been gradually evolving into it’s own unique stack.
      it does use libhybris, which was something 1st devised by Sailfish devs, but since forked & contributed to by many others, libhybris != MeR

      • Ethan Raygreen

        Wrong. Nemo is the Mer project. See for details at the Merproject.org site. And Mer was based and contains more or less 80-90% of MeeGo source code.

        Nemo is not Harmattan, that is true.

        Sailfish is based on Mer and use the Mer core and some parts of Nemo, as all of them are open source project. The Mer is the standard for vendors to build an own distribution, like eg. Sailfish.

        Ubuntu has started an cooperation with Sailfish and Mer to obtain compatibility at APIs level. If you don’t know it doesn’t meter this is not possible. See also what is Palsma Active.

        And I don’t have monopoly for truth, something can now be different somehow about Ubuntu slightly.

        • Trexus

          Err, no it’s not, they are two distinct projects, mer provides lower layers, it is not in any way tied to nemo, that’s why we have cordia and plasma, which also use mer.
          There has been some early talks to possibly share some Qt/QML components, but that has zero to do with mer, & it’s very unlikely it’ll results in much.

          • Witcher of open spells

            Mer is (after MeeGo abandoned) everything what was above kernel and below UI. Mer is a base to build a distribution for vendors. Mer has created standard of this. Mer is th core, but now not a full distribution. And yes it contains MeeGo.

            However, from that time (MeeGo abandon) the Mer project has developed Mer and Mer tools so now it is much further then it was.

            Nemo has added a kernel and Nemo UI so we have Nemo. Jolla has added similar so we have Sailfish. Jolla, Sailfish, Nemo, and community around them are actively contributing to Mer, hence Mer continue development, so now it is much more then previously MeeGo was – as it is in open sources usually.

            Current Mer before all above, as a project, it was toward the Maemo project, but now it is not. Now it is MER from MEego Reconstructed.

            Some trivialisation were made above to explain things faster and easier. Whatever – this is really promising project, or if sb would want a promiseware ;D

            • Trexus

              Yep, pretty much correct…
              As for it being very promising, it’s too early to say, I hope it is.

        • Trexus

          “And Mer was based and contains more or less 80-90% of MeeGo source code. ”

          Again, MeR != MeeGo, Nemo is similar, you seem to have a miscomprehension as-to-what MeR is.

          • Witcher of open spells

            I think this is not quite true. And it has been changing.
            1st Mer was about Maemo
            Nokia abandoned MeeGo
            Mer become the recnstructed meego with meritocracy govering
            Mer has taken MeeGo source code and created Mer core, start further development
            Nemo was created, also as Harmattan replacement as it was also abandoned
            Jalla has started Sailfish using Mer core and tools, and also some parts from Nemo, adding own UI better then swipe, and a kernel will be hardware depended.

            And still Mer is separate project which is developed.

            Sailfish is separate project which is developed.

            The same Ubuntu, and Kylin Ubuntu. According to China authorities (if I could say so in my limited knowledge of subject) Kylin Ubuntu is to be a replacement for Windows in China in all areas MS Windows is used. And this could be MeeGo if not abandoned by Nokia. Also that is why MeeGo was a subject of attacks, it was a threat. The original project was devastated so Ubuntu has come into the play. This is cute management of Nokia’s future, isn’t it?

            • Trexus

              Not sure what isn’t quite true, everything I said was 100% correct, & Nemo wasn’t created as a replacement for Hartmattan, it is a direct descendant of MeeGoCE.
              Everything else you say is more-or-less correct, except the last bit about MeeGo being a “guaranteed success/threat” to Windows in the desktop/laptop form-factors.

        • Trexus

          “And I don’t have monopoly for truth, something can now be different somehow about Ubuntu slightly.”

          You seem to be still trying to suggest it was once based around MeR, & now is different slightly…
          Ubuntu was never based around MeR, it has a very different lower lvl stack than MeR, it would’ve been great if they chose to use it. But Canonical often likes to play their own game instead of being a team player, so they have more control etc.

          • Witcher of open spells

            Exactly, Ubuntu was/is completely different project. If they will make it compatible at APIs level still it will be, but for devs will be a compatibility so they will have bigger market. That is the point.

            • Witcher of open spells

              The great question is how they will play when they are to create Kylin Ubuntu for Chinese. Cannonical has established and stabil organisation from years, while Jolla is new however experienced. Chinese in such a case prefer a partner which looks more stable and reliable. Even if befere they have involved in Nokia’s MeeGo project as a strong partner. Probably they will observe and adopt steps to future situation.

              And Nokia has lost the great opportunity which was just in the Nokia’s fingers. It’s the pity. And the shame also. Not to enter the China market? Hard to believe even.

              • Trexus

                Kylin is a totally diff. form-factor sector to the handset one.

                • Witcher of open spells

                  Kylin is simply Linux made by Chinese for China. Linux can be different each other. But considering the fact they are commonly are using Kylin in China in internet-cafees bars makes me believe still this is Linux. Internet caffes – one come to surf internet etc. like we here, the same way.

                  Chine want to be not binded by necessity of using Windows, so looking for alternatives. Do you think China Telecom was accidentally MeeGo partner? hahaha If in China such a big company, in fact the biggest telecom in the World, takes part in something then this is not accidental and thought over by many many persons and planned far far ahead.

                  Now they decided to merge Kylin and Ubuntu. Perhaps they would merge Kylin with MeeGo. Or use them both. Or replace Kylin with MeeGo, or develop them together. Nokia has lost much more then the market for N9.

                  • Trexus

                    You fail to understand my point.

                    • Trexus

                      I will explain better later, bed time.

            • Trexus

              They’re not talking about a entire compatibility layer, I doubt that will ever happen, what may happen is some shared UX/UI components, but even that will probably be a relatively small subset

              • Witcher of open spells

                Wrong. Compatibility layer is fro Android. Sailfish, Ubuntu and Mer are talking/working on compatibility at the level of APIs, but not any compatibility layer. This is more about to use the Mer standard, and to contribute to it together, to share each other with working solutions.

                • Trexus

                  No. I am not wrong, I am telling you, there is no compat. layer, there’s an initial agreement to have some shared UI/UX components between ubuntu/nemo(sailfish)/plasma & maybe bbx. That is all, nothing more & nothing less.

                  Do I srsly have to dig up the relevant discussions to shut your clueless arse up? Your starting to tempt me now.

                  • Trexus

                    Alien Dalvik is not a compat. layer, & there’s nothing “similar” to it planned for ubuntu/nemo/plasma etc. as your earlier posts suggested. All that’s planned, is some shared UI/UX components, & even that’s still in the the preliminary stages.

                    • Witcher of open spells

                      Before it has been stated that Alien Dalvik will be used it was described as ACL aplication compatibility layer for Android or just Android compatibility layer. From this comes your “layer” in fact this is software which use fact that Android is castrated Linux, so with some “help” Android apps will run on another Linux as Sailfish is, and it will run as native apps meaning no lags.

                      Talks/works, or whatany you want to call them, are Sailfish Ubuntu Mer and reported to be related with compatibility of APIs, only you see in this any “layer”. In what stage they are is as known as Jolla smaprtfon specs – so unknown.

                      “Do I srsly have to dig up the relevant discussions to shut your clueless arse up? Your starting to tempt me now.”
                      You can do what you want it is only your choice. When you mix things like “ubuntu/nemo/plasma” together then this could be quite good idea.

                    • Trexus

                      You’re conflating openACL with alien dalvik, they’re in-fact slightly different in terms of how they work.

                      Onto the main point; you’re continually suggesting that the current cooperation planned will lead to an API/Binary compat. layer.
                      That’s not what has been discussed so far, & I don’t see it ever happening, again, what’s been discussed is shared UX/UI components, very different to a entire API compat. layer.

                      Harmattan & MeeGoCE (now Nemo) had a compat. layer planned & (mostly) implemented. Doing the same between BBX & Sailfish would be extremely unlikely, between Sailfish & Ubuntu won’t be much more likely. Between Sailfish and Plasma may be a possibility, but I don’t see the two projects focusing their resources towards that. Between Nemo & Sailfish is quite possible, it’s already partly there in many ways.

                      But the fact remains; chats taking place have nothing to do with universal compat. layer, they’re to do with some shared UX/UI components (likely a relatively small subset) that’ll enable some apps (or even OS UX/UI’s) to look similar, NOT to enable universal interoperability.

                      That clearer?
                      P.S.
                      apologies for the “clueless” tag, I was ready for bed & grumpy!

  • chris wayne

    I hated my N900, bought it the week of it’s release on USA (i’m from Mexico) for about $750 dollars and the shit became a brick just by turning it on after 2 days! then i sent it back to Nokia and they sent it back after 1 month and 1 week and the phone came without the manual and it was so damn dirty (a lot of fingerprint’s oil in), after just 3 weeks of normal use the screen started doing some clicking while using the stylus, i was furious, then i decided to sold it and what was my surprise?, the price of the phone was cut due to poor sales so the price of my used N900 was going to be even cheaper if i wanted to get some money back. At the end i sold it to some Linux geek for miserable $450 dollars, worst business of my life. Now i’m back to Nokia with a superb (for the price tag) Lumia 710 and due to the quality of the phone i’m about to buy the 920 (or should i wait EOS/Catwalk?)…

    • Peggy Fralker

      I have tried Lumnia 800 after 2 days it has died – reason unknown. I have replaced it with a new one – after 5 days it has reseted by itself and I lost all my data. L800 has reseted 2 times more – it has realised it reset itself when battery reach 20% during using… I can’t replace battery. I was told it is ok as it is Lumia failure… unremoveable… And ought to have battery loaded always or have charger with me – this is best solution… Finally I give it back to retailer and now I have other phone. That was the worst experience with a phone in my life, I don’t want any Lumnia again.

  • Shane

    It’s also available for N9/N950 & in some ways is better suited for that hw.
    Still runs pretty well on my N900 though…