The N9: what MeeGo could have been
The N9 is an attractive device, only slightly larger than a Nexus One. The spouse, upon handling it, complained about the rather sharp corners - but proved reluctant to hand the device back anyway. The corners do stand out in an age when everything is supposed to be rounded, and they can dig into the palm slightly, but it's all a matter of taste. The handset's specifications are reasonably standard for this vintage of device; there is a 1GHz processor, 1GB of RAM, and 16GB of storage. In a welcome change from previous Nokia devices, the N9 uses a standard micro-USB connector instead of something special Nokia made up for that specific handset. The camera is quite nice; there is also a front-facing camera, though the built-in Skype client is unable to use it. By all appearances, the handset is sealed forevermore; replacing the battery does not appear to be an option.
Android users will have likely gotten used to that environment's home screen
which can be populated (especially with CyanogenMod builds) with a wide
variety of application launchers, contact shortcuts, active widgets, and
more. The N9 MeeGo experience is somewhat different, in that there are
three specialized home screens with limited potential for customization.
The first of these is the familiar matrix of icons providing access to
applications on the phone. Users can rearrange the icons (including
putting them into subfolders), but there is no way to put anything other
than application launchers on this screen.
It is also possible to remove applications via this screen. Dishearteningly, one quickly learns that, as with many Android builds, some applications have been rendered immortal and unremovable. Your editor has little use for Facebook or Twitter applications, but they cannot be made to go away. The best that can be done is to move them to a folder where, at least, they can be kept out of sight.
The second "home" screen (accessible via a left or right swipe across the
screen) shows the running applications in a 2x2 grid. Their current
screens are visible, and specific applications can be killed if desired.
As one might expect, tapping on an application's screen brings it back to
the foreground. The third screen is a notification area; messages, weather
information, and the latest urgent Twitter spam will show up here.
Annoyingly, none of the home screens rotate when the phone is held in the landscape orientation. Applications handle rotation without trouble, but the home screens appear to be special.
The applications shipped with the phone are generally attractive and nice to use - though sometimes they seem to get into dead end screens where a "back" button would be nice to have. There is a mapping and navigation application that works nicely and comes with suitably annoying voices in a wide range of languages. The camera application is feature-rich and responsive. There is a central account manager that organizes access credentials; interestingly, it can hook into Google, but not for contact information. Getting access to contacts will be one of the first things a former Android user will want to do; fortunately it is possible by telling the phone that Google is an Exchange server. WiFi tethering is built into the phone but "forbidden" for US users; fortunately, one can install the "SpotOn" application to get around that bit of obnoxiousness.
On the other hand, the web browser makes one wish for the Android
equivalent. Android's browser has a "fit page to screen" option that does
a nice job of rendering the interesting part of a web page in an optimally
readable form; the MeeGo browser, instead, just mashes the entire page,
unreadably, onto the screen, requiring zoom-in gestures and side-to-side
scrolling for almost every
page that has not been specifically designed for small screens. That
Android feature, arguably, is on its own responsible for the
fact that nobody at LWN has found the time to make a more mobile-friendly
version of the site; the N9 has made it clear that not everybody has as
good an experience.
The MeeGo on-screen keyboard, while being entirely functional, is also not as nice as the Android equivalent. There appears to be no built-in spelling correction or word prediction, making typing a longer and more error-prone process. That is one of the bigger shortcomings of this system. Typing on keyboard-less handsets is a painful enough procedure even with a top-quality on-screen keyboard; this is not the place for a second-rate solution. (Correction: there is a simple prediction mechanism that only seems to appear some of the time; it is better than nothing, but doesn't change the main point of this paragraph).
There is, naturally, an applications store full of things to add on to an N9. A number of important programs are there, and, inevitably, the handset comes with Angry Birds already installed. The range of available applications falls far short of that found in the Android store, though. That is far from surprising; given that MeeGo was a lame-duck platform from the beginning, there will be little motivation for developers to put any time into supporting it.
Inside the device
The MeeGo system is a far more Linux-like environment than Android
provides. A terminal application comes preinstalled on the device; it
works well enough for what it is, but the truth of the matter is that
trying to do command-line work with an on-screen keyboard is always going
to be painful. Fortunately, there's an easier way. If one puts the device
into developer mode (a simple menu tweak) and plugs it into a computer's
USB port, the device offers to connect in "SDK mode." In that mode, it
presents as a network interface; there is even a built-in DHCP server so
the computer side of the connection gets configured automatically.
After that, it's
just a matter of using SSH to obtain a shell on the handset. Unlike
Android handsets, the N9 has Busybox on it from the start, so the shell is
actually reasonably usable.
For the most part, the phone environment feels like Linux. There is, however, no functioning su command; one is, instead, supposed to use devel-su. The result is a shell that claims to be root, but all it takes is a find command run from the top of the filesystem to see that root is not all-powerful on this system. There are certain things that one still cannot access or change. This behavior is the result of the MeeGo security framework in action. Through a combination of trusted computing techniques and mandatory access control, Nokia keeps the device locked down at a certain level. It wouldn't do, after all, to let those pesky users have direct access to the media files that they think they bought on their handset.
Of course, keeping the users away is not the only motivation for the security framework; it is also intended to prevent applications from acting against the users' interests. Applications are installed with "resource tokens" describing the actions they are allowed to carry out; they include the ability to query location information, access the camera, make calls, etc. Superficially it looks a lot like the Android permissions mechanism, but the implementation appears to be wired more deeply in at the kernel level.
Notably, the application installer does not expose resource tokens to the user, so there is no way to know what types of access a given application will have - a major difference from Android. One suspects that most Android users never look at the list of requested permissions, but a subset of us tend to examine them closely indeed. The inability to know what access has been granted to an application seems like a major shortcoming. That will be doubly true anywhere outside of a strict walled-garden application repository; on this system, applications from outside Nokia's store, if they can be installed at all, can only have a restricted set of permissions. But, restricted or not, the user should have the chance to review the permissions requested by an application.
What if you want to bypass the mandatory access control and truly have full access to the device? The answer would appear to be a tool called INCEPTION. It allows the installation of applications with full privilege; one can also disable the security framework altogether. Your editor has not had the time to play with this tool, but it appears to be the ticket for those who are eager to void their warranties and reach for full control of the handset.
Perhaps a true measure of the freedom of a piece of hardware is the existence of independent operating system distributions for it. In the Android world, there is CyanogenMod along with a long list of less well-known, often more dubious, "mods." For the N9 the alternatives on offer are somewhat more restricted, but those who are truly adventurous can give NemoN9 a try. Nemo is the current incarnation of the "Mer" project; it is trying to continue the development of the MeeGo framework as an independent effort. Unfortunately, activity in this project seems to have slowed considerably, though it is still producing regular releases and its use in the upcoming Vivaldi tablet may spur development in the future. What releases Nemo has made have not found their way over to NemoN9, though, which was last updated in November, 2011.
The end of the line
Your editor has often said in the past that MeeGo could become a credible challenger to Android and a strong force in the mobile world in general. After some hands-on experience with a MeeGo device, that impression has not changed. MeeGo provides a polished and pleasant user experience. It falls short of current Android releases in some ways, but it is much nicer to use than the early Android-based devices were. With a bit of work, MeeGo could have been a truly competitive - and more community-friendly - alternative. The fact that things did not turn out that way is a sad comment on the state of the market and the management of certain companies.
The good news is that the developers who worked on this system are out
there; many of them are still employed at Nokia. MeeGo may even see some
further development for devices other than handsets. But the sad fact is
that Nokia
has placed its bets on a proprietary operating system with uncertain
prospects in the mobile market. If that bet does not work out as hoped,
Nokia may yet rediscover the high-quality, free-software alternative at its
disposal. Then, perhaps, we'll see a new attempt to put MeeGo-based
handsets on the market. For now, though, the N9 has all the look of a
solid, sleek and polished platform with no future. In truth, it deserved
better than that.
Posted Mar 20, 2012 19:29 UTC (Tue)
by Jonno (subscriber, #49613)
[Link] (3 responses)
Posted Mar 21, 2012 10:19 UTC (Wed)
by tajyrink (subscriber, #2750)
[Link]
Also, about 20 times easier instructions are nowadays available at http://wiki.merproject.org/wiki/Nemo/Installing#Nokia_N9 - the moslo-n9 takes care of many of the ugly parts.
Posted Mar 21, 2012 10:24 UTC (Wed)
by timoph (subscriber, #71883)
[Link] (1 responses)
Posted Mar 21, 2012 12:00 UTC (Wed)
by Jonno (subscriber, #49613)
[Link]
Posted Mar 20, 2012 19:37 UTC (Tue)
by corsac (subscriber, #49696)
[Link] (14 responses)
Posted Mar 20, 2012 19:41 UTC (Tue)
by corbet (editor, #1)
[Link] (13 responses)
Posted Mar 20, 2012 19:51 UTC (Tue)
by corsac (subscriber, #49696)
[Link]
Posted Mar 20, 2012 19:56 UTC (Tue)
by Jonno (subscriber, #49613)
[Link] (3 responses)
2. If you enable developer mode and then turn it of again, the terminal stays installed (at least it did for me), perhaps you got a phone that had been used internally by Nokia first, and not been re-flashed with a vanilla rootfs image.
3. MeeGo 1.2 Harmattan is MeGoo by virtue of having gotten a trademark usage exception from the Linux Foundation for use of the name. However, the underlying OS is closer to Maemo 5 than to the reference MeeGo 1.2, down to using dpkg rather than rpm for package management, which is why some people like to call it Maemo 6.
Posted Mar 21, 2012 8:07 UTC (Wed)
by alexbk (subscriber, #37839)
[Link] (2 responses)
Posted Mar 23, 2012 10:58 UTC (Fri)
by wookey (guest, #5501)
[Link]
So yes if you just _use_ a package manager for managing packages then it's a trivial matter. If you develop for a platform, at the infrastructure/packaging level (i.e as opposed to actually writing apps, when again it doesn't matter much) then the package-tools ecosystem is almost everything.
Posted Mar 23, 2012 18:22 UTC (Fri)
by oak (guest, #2786)
[Link]
Debian has the longest history on ARM, it has been most used ARM distro for a decade and it started the OABI -> EABI and soft-fp -> hard-fp transitions first of the major distros. And nowadays Linaro works with Ubuntu. RPM world plays a bit of catch up and seems more fragmented/marginal on ARM.
Posted Mar 21, 2012 16:38 UTC (Wed)
by krake (guest, #55996)
[Link] (1 responses)
Posted Mar 21, 2012 19:32 UTC (Wed)
by oak (guest, #2786)
[Link]
Posted Mar 21, 2012 21:48 UTC (Wed)
by cfischer (guest, #3983)
[Link] (5 responses)
The browser on the N9 is apparently a safari clone, or at least it reports as such. It has some features as double-click to zoom in on text.
All in all, I'd much prefer a Mozilla mobile browser. Hope it comes soon.
The keyboard is, IMHO, better than on Android - at least better than the Android versions of 1 year ago.
Posted Mar 21, 2012 21:51 UTC (Wed)
by corsac (subscriber, #49696)
[Link] (1 responses)
Posted Mar 21, 2012 22:06 UTC (Wed)
by cfischer (guest, #3983)
[Link]
Posted Mar 21, 2012 22:11 UTC (Wed)
by halla (subscriber, #14185)
[Link] (2 responses)
Posted Mar 23, 2012 0:20 UTC (Fri)
by Lennie (subscriber, #49641)
[Link] (1 responses)
I read somewhere that Webkit browser on the N9 is the most capable of the 3 platforms: iPhone Safari, Android Browser and N9.
Posted Mar 23, 2012 8:58 UTC (Fri)
by corsac (subscriber, #49696)
[Link]
Posted Mar 20, 2012 20:14 UTC (Tue)
by halla (subscriber, #14185)
[Link]
(And I'm still, no matter how dead the platform is, inordinately proud that the documents application uses Calligra =and is free software as well. That was one project where Nokia worked with the community that just worked.)
Posted Mar 20, 2012 20:41 UTC (Tue)
by aorth (subscriber, #55260)
[Link] (3 responses)
I saw one recently in a tech store in South Africa, but was shocked to see its price tag rivaling the Galaxy Note and the Galaxy S2 on the same shelf. Shame, because the hardware looked beautiful, but I could never justify spending that kinda cash on a doomed/abandoned platform.
An aside: the last Nokia phone I used was an Express Music 5800. Managing network connectivity on that damn phone was such a pain in the ass. Nokia made it so difficult to add APNs for different networks (we have many in Kenya). Also, prioritizing known Wifi networks over 3G never worked for me. I never seemed to be able to browse the net properly on it. That was truly a dumb phone trying to be a smart phone.
Posted Mar 22, 2012 7:16 UTC (Thu)
by buchanmilne (guest, #42315)
[Link] (2 responses)
This "strange" pricing continues with contract prices. The N9 launched on Vodacom's Business Call package at R279pm, within 2 months it had dropped to R259pm, but as soon as the Lumia 800 launched (at the same price as N9 launch price, R279pm), it was up to R299pm, the exact same price as Galaxy Nexus and iPhone 4s 16GB. The Lumia 800 is still R279pm, as is the SGS II. Galaxy Note is R399 on the same plan.
Could it be that Nokia is intentionally sabotaging sales of N9 in favour of Luma, even in regions where they have decided to sell the N9?
Posted Mar 23, 2012 0:27 UTC (Fri)
by Lennie (subscriber, #49641)
[Link]
Well there are rumors that the N9 is outstelling the Lumia:
http://www.osnews.com/story/25569/Nokia_N9_Outselling_Lumia_
Even though the Lumia has a much bigger marketing budget.
Posted Mar 23, 2012 4:36 UTC (Fri)
by ringerc (subscriber, #3071)
[Link]
The N9 really feels like a "we have a contract with someone that says we have to release this, but not how" kind of device. It's as genuine an effort as a "sorry" from someone who was ordered to apologise by a court ruling.
I was really looking forward to Maemo, but when the Qt-to-GTK switch hit things started looking black, then the MeeGo trainwreck pretty much killed it well before anyone officially gave up on it. A smartphone platform with two incompatible changes in early life and a first handset with a dead-ended platform is NOT going to be attractive to devs. I'm just amazed it was released at all.
Posted Mar 20, 2012 20:44 UTC (Tue)
by josh (subscriber, #17465)
[Link] (10 responses)
Posted Mar 20, 2012 23:28 UTC (Tue)
by ehovland (subscriber, #2284)
[Link]
Posted Mar 21, 2012 1:32 UTC (Wed)
by jzbiciak (guest, #5246)
[Link] (4 responses)
Posted Mar 21, 2012 15:52 UTC (Wed)
by sumanah (guest, #59891)
[Link] (3 responses)
Posted Mar 22, 2012 17:16 UTC (Thu)
by ssam (guest, #46587)
[Link] (2 responses)
Posted Mar 22, 2012 18:46 UTC (Thu)
by jzbiciak (guest, #5246)
[Link] (1 responses)
Posted Mar 22, 2012 22:47 UTC (Thu)
by ssam (guest, #46587)
[Link]
Posted Mar 22, 2012 10:51 UTC (Thu)
by osma (subscriber, #6912)
[Link]
I'm reasonably happy with the soft keyboard on my N9, but I sometimes miss the ability to type without looking at the phone. That's practically impossible to do with an on-screen keyboard, even though the N9 keyboard gives pretty nice vibration feedback so at least you feel when the key has been "struck".
Posted Mar 27, 2012 1:37 UTC (Tue)
by The_Barbarian (guest, #48152)
[Link]
It does fix the N9 issue of no hw keyboard, but I would miss the N900 resistive touchscreen. And of course the wasted effort from dropping gtk for qt is annoying. I vaguely favor gtk anyway, but the real issue is the switch. qt to gtk would have been as bad.
Posted Mar 31, 2012 11:01 UTC (Sat)
by liljencrantz (guest, #28458)
[Link] (1 responses)
* The system will occasionally (a few times per week) heat up significantly and drain the batteries in a couple of minutes. This is on an n950 with no 3rd party apps running. Manually closing every single application will not help, the only fix I've found is to manually restart. I'm too lazy to dig more.
The whole Nokia Linux phone thing saddens me. I had an n900 that I loved, but Nokia really managed to squander the market window they had - the N9 should have come out a few months after the n900.
Posted Apr 15, 2012 21:59 UTC (Sun)
by Tet (guest, #5433)
[Link]
Regardless of your lack of recommendation, I'll happily take it off your hands for you. I'll make sure you don't lose out on the transaction. Yes, I'm serious. Let me know.
Posted Mar 20, 2012 21:55 UTC (Tue)
by josh (subscriber, #17465)
[Link] (2 responses)
This looks like just a bug; http://forum.meego.com/showthread.php?t=4770&page=4 says that it has nothing to do with US-specific restrictions, just a bug that the wifi doesn't allow the creation of ad-hoc networks. The workaround:
echo 1 > /sys/devices/platform/wl1271/allow_adhoc
Posted Mar 21, 2012 10:21 UTC (Wed)
by tajyrink (subscriber, #2750)
[Link]
Posted Mar 22, 2012 11:31 UTC (Thu)
by osma (subscriber, #6912)
[Link]
http://talk.maemo.org/showpost.php?p=1172934&postcount=1
Posted Mar 21, 2012 1:58 UTC (Wed)
by pwsan (subscriber, #56604)
[Link] (7 responses)
> In a welcome change from previous Nokia devices, the N9 uses a standard
This might be true for Nokia's non-Linux devices. But Nokia's Linux devices, such as the N800, N810, and N900, all used standard mini or micro USB ports.
Posted Mar 21, 2012 4:08 UTC (Wed)
by HelloWorld (guest, #56129)
[Link]
Posted Mar 21, 2012 6:59 UTC (Wed)
by thisisme (guest, #83315)
[Link] (1 responses)
Posted Mar 21, 2012 7:19 UTC (Wed)
by spaetz (guest, #32870)
[Link]
Posted Mar 21, 2012 8:10 UTC (Wed)
by hrw (subscriber, #44826)
[Link] (3 responses)
Posted Mar 21, 2012 8:17 UTC (Wed)
by josh (subscriber, #17465)
[Link] (2 responses)
You could also charge it from a normal USB port, but it would charge a lot slower.
Posted Mar 21, 2012 11:07 UTC (Wed)
by timokokk (subscriber, #52029)
[Link] (1 responses)
Both N900 and N9 charge happily from the USB. They don't even have any other means for charging.
Posted Mar 21, 2012 12:12 UTC (Wed)
by thisisme (guest, #83315)
[Link]
Posted Mar 21, 2012 6:49 UTC (Wed)
by thisisme (guest, #83315)
[Link] (8 responses)
(not trolling, just genuinely interested whether it's actually been done successfully)
Posted Mar 21, 2012 7:58 UTC (Wed)
by khim (subscriber, #9252)
[Link]
Not that I know of. IMNSHO it's just basically impossible to do. Transition to FOSS is inherently disruptive: it produces worse results (as far as blitz and polish is concerned, at least) and brings less money but requires less money for development, too. It's well-known fact that such transitions rarely succeed. The most you can realistically hope to do is to start separate (or semi-separate) entity which will grow from zero using freed sources and will eventually cannibalize old product. Similar to how Quantum successfully transitioned from 5¼ to 3½ HDD via it's Plus Development subsidiary. It's really hard to pull off. And when you do that then usually new thriving company has a different name thus it looks like transition failed. I think you can name quite a few products which went this way if you'll think about it. P.S. If you've read the Innovator's Dilemma then you know that it is possible to survive direct transition (it offers Micropolis as an example) even if this is extremely hard to do. Thus I think we'll see some such examples down the road, but their number will be tiny - this is just a wrong way to approach the problem.
Posted Mar 21, 2012 8:11 UTC (Wed)
by nhippi (subscriber, #34640)
[Link]
Neither Nokia or Sun can be said to be "transformed to open source companies". Nokia only experimented with open source with few products and Sun had a long tradition doing some things in open (nfs, openview..) while others as closed at the same time.
Posted Mar 21, 2012 11:24 UTC (Wed)
by pboddie (guest, #50784)
[Link] (4 responses)
The article makes it pretty clear that not only does Nokia reserve the position of power for itself in any initiative - the attitude was always that customers and the community should count themselves lucky to have access to the toys - but that the organisation wastes a considerable amount of effort on undermining the usability of the eventual products: arbitrary limitations on functionality, contempt for purchasers of their devices, and so on. If people in the organisation were actually assigned to implement useful things instead of measures to keep the customer in check, maybe the resulting products would be competitive.
In fact, Nokia is a great example of not leveraging Free Software but instead attempting to constrain it. Sun also suffered from similar internal infighting, in its case leading to a generally incoherent Free Software strategy as various divisions presumably tried to turn the clock back to the proprietary glory days, in complete denial of the trajectory of the company and the industry.
Posted Mar 21, 2012 11:41 UTC (Wed)
by halla (subscriber, #14185)
[Link] (2 responses)
Sure, there was a learning stage for everyone, but in the end, development was done upstream, bugs were tracked upstream, Nokia sponsored sprints, dinners, t-shirts, posters, organized classes for interns who would work on FreOffice and so on. And the result turned out to be really good for both parties.
Working with Nokia on KOffice/Calligra was without doubt the greatest project I have ever had. Others will have other tales, but I stand by mine.
Posted Mar 21, 2012 14:27 UTC (Wed)
by pboddie (guest, #50784)
[Link] (1 responses)
And the "big and diverse" attitude is used far too often when excusing corporate behaviour: it frequently allows one group of people to benefit from corporate wrongdoing while claiming that they don't really agree with it but they'd like everyone, presumably including those who are on the receiving end of that wrongdoing, directly or indirectly, to keep on indulging their community efforts.
Posted Mar 21, 2012 14:49 UTC (Wed)
by halla (subscriber, #14185)
[Link]
Posted Mar 21, 2012 22:41 UTC (Wed)
by oak (guest, #2786)
[Link]
While it would be nice to have a mass-market smartphone that's useful for / wanted by normal end-users, but still open for tinkering (so that one could e.g. build further products on top it), I don't think Nokia ever aimed at that or saw it as a viable (profitable) market.
I don't think any other company provides such things either.
I guess that if MeeGo thing would have flown, there could have been *separate* developer phones, similar to what Google offers for Android:
(I'm a fellow N9-security hater though. :-))
> In fact, Nokia is a great example of not leveraging Free Software but instead attempting to constrain it.
Open source is about software, not about products. While Nokia treated the specific device distro versions (= collection of specific versions of SW) more like fixed product that gets mainly just fixes, a lot of the SW itself on them was developed openly, at upstream, and the development was more open with each new version, until MeeGo's demise...
It's true that the device end users didn't see much of the open development done by Nokia, but that's mostly because users aren't involved with the open source development, at the corresponding upstream projects[1].
This development happens before the product releases, not half a year after release when most users get the product. By that time the SW has stabilized and developers have mostly moved to new versions of the software, intended for next product(s) and not anymore fitting well into the old devices (lacking RAM, specific types of HW etc).
If there would have been further MeeGo devices, I don't think the lack of resources on previous models would have been such a problem anymore as N9 had 1GB of RAM... :-/
[1] A lot of that "community communication" was hiring of the community members to do the work, starting from around 2004 (output from that early time period was e.g. Xephyr, XResTop and Xresponse tools and many Matchbox window improvements, things that were used later for example in OLPC and OpenMoko).
Btw. Getting things to upstream is sometimes a long process, even when community members are hired to work on it. A good example from this list:
Is the UI "tap-and-hold" feature which upstreaming to Gtk was initiated in 2005:
That feature has comments up to almost today and and it's still not in, and I guess not going to be either. It was more relevant when screens were used with stylus and indication about press and hold action availability could actually be visible behind it. However, nowadays most devices are interacted with fat fingers, not with stylus...
Posted Mar 21, 2012 14:51 UTC (Wed)
by lambda (subscriber, #40735)
[Link]
It depends on your exact definitions. For instance, Netscape certainly failed, but the product did succeed in transitioning into Firefox, and the Mozilla Foundation is pretty successful these days. Or take Blender for example. It's another example of a failing company, that wound up selling its software to the community, and since then has become quite successful as FOSS with a paid development staff including several of the original developers. So in these examples, the company wound up failing, but the product had a successful transition to FOSS and is actively developed with a paid staff. Another example would be Ryzom, an MMORPG; its company went bankrupt, but its assets were purchased and released under the AGPL for the code and a Creative Commons license for the assets, while there are still paid subscriptions for the official server.
There are also examples of success as hybrid companies; companies in which some of their code is FOSS, and some is proprietary. For instance, Apple ships a good deal of their code under a permissive license. Oracle sells a Linux distro, maintains MySQL, developed Btrfs, and so on (though Oracle has obviously had some issues with supporting free software). Or Google, which makes a lot of its money from services and proprietary software, but ships a good deal of free software, including Android.
Posted Mar 21, 2012 8:14 UTC (Wed)
by alexbk (subscriber, #37839)
[Link] (2 responses)
I think it's too late now. Many, if not most of the N9 developers have quit the company in frustration, some are staying simply for the redundancy package (few months worth of salary); the very building in Helsinki where the team was located was shut down and released to rental market last week. It would probably take something drastic such as complete replacement of Nokia board of directors, or a company spin-off to even try to get them back.
Posted Mar 21, 2012 9:02 UTC (Wed)
by halla (subscriber, #14185)
[Link] (1 responses)
I think many people underestimated how much development effort was funded by Nokia (and Intel).
Posted Mar 21, 2012 11:43 UTC (Wed)
by alexbk (subscriber, #37839)
[Link]
Meltemi project strives to be a much more nimble, in-house, working-together effort; I wish them the best of luck and success, although working under an unsupportive management which (I reckon) secretly wants to get rid of you must be horrible.
Posted Mar 21, 2012 8:23 UTC (Wed)
by develer (subscriber, #40796)
[Link] (3 responses)
Posted Mar 21, 2012 10:00 UTC (Wed)
by Jonno (subscriber, #49613)
[Link] (1 responses)
Under the hood this is because the "mp-harmattan-001-pr" package depends on the "account-plugin-twitter" package, and the application management program refuses to remove "mp-harmattan-001-pr".
Posted Mar 21, 2012 13:43 UTC (Wed)
by mve (guest, #54709)
[Link]
Posted Mar 22, 2012 10:56 UTC (Thu)
by osma (subscriber, #6912)
[Link]
Posted Mar 21, 2012 10:19 UTC (Wed)
by AndreE (guest, #60148)
[Link]
Posted Mar 21, 2012 10:44 UTC (Wed)
by MortenSickel (subscriber, #3238)
[Link] (3 responses)
I have to admit, I also was a bit confused of the desktops and the view when I started to use N900, but got used to it and was very happy with it. (until I got my N900 damaged a little while ago... :-( )
Posted Mar 21, 2012 11:35 UTC (Wed)
by halla (subscriber, #14185)
[Link]
Posted Mar 21, 2012 17:47 UTC (Wed)
by dw (subscriber, #12017)
[Link] (1 responses)
Quite surprised to read this. I believe on both platforms (and definitely at least on Android), regardless of what permissions are displayed to the user, applications automatically get the right to run native code that talks to an out of date kernel (in other words, the displayed list of permissions is ultimately meaningless, as endless one-click-root solutions for Android will attest).
Posted Mar 21, 2012 17:49 UTC (Wed)
by dw (subscriber, #12017)
[Link]
Posted Mar 21, 2012 12:14 UTC (Wed)
by and (guest, #2883)
[Link]
actually, you can double-tab on the region on the website which is of interest to you and the N9 browser will make it fit to the screen. I think that's much more productive than using the zoom gesture. (the N900 browser worked the same, BTW.)
Posted Mar 22, 2012 1:48 UTC (Thu)
by ras (subscriber, #33059)
[Link] (10 responses)
He claims that the N9 outsold the Windows phone Lumia's 3 to 1. That would mean a phone the company did not promote, did not release to its major markets, and promised to kill out sold the rival that promoted as the future of Nokia and funded accordingly. For a technology company that behaviour would be perfectly understandable if the N9 was developed by some outside mob and the Lumia was their baby. What makes it utterly bizarre is the reverse is true.
Nonetheless, the divorce between Nokia and Linux isn't as final some are implying here. During the turmoil that followed the Windows Phone announcement, everybody associated with the Linux side of Nokia was nervously looking for an escape hatch before the axe fell. And indeed it appears the axe did fall on some of them, but not all. In fact Nokia did an odd thing. They paid some of the people who live in my area and work on Linux phones large bonuses to stay, to the point that they say they can't afford to leave. Now they are now busily beavering away, developing Linux based phone's for Nokia. They don't say much about what they are working on beyond looking overworked and complaining they are under the hammer to release lots of new Linux based phones. I wish them good luck, and hope they are wildly successful in their endeavours.
Posted Mar 22, 2012 2:46 UTC (Thu)
by imunsie (guest, #68550)
[Link]
Posted Mar 22, 2012 10:03 UTC (Thu)
by alexbk (subscriber, #37839)
[Link] (2 responses)
Posted Mar 22, 2012 12:52 UTC (Thu)
by pboddie (guest, #50784)
[Link] (1 responses)
It's completely possible for people to increasingly hate their jobs, know that their efforts go unrecognised by upper management, see their workload increased and their colleagues laid off, and yet feel that they can somehow prove themselves or make a difference, such is either the misplaced loyalty they have to their employer or the pride they have in their own efforts and the desire to achieve something, even though they can be fairly sure that anything they manage to deliver will be thrown away by the company strategists. My advice to those people is to take any pay-off that gets offered, not to look back, and to avoid wasting even more of their life on something that is most likely to go nowhere.
It may be news to Nokia's upper management, but Linux has been running on what would quite easily be a featurephone by today's standards since 2003 (Motorola A760) or even earlier. Even Trolltech had their Greenphone reference design before being acquired. Four years on and concrete products are now the stuff of smoke and mirrors - such progress!
Posted Jun 16, 2012 12:28 UTC (Sat)
by alexbk (subscriber, #37839)
[Link]
Posted Mar 22, 2012 12:07 UTC (Thu)
by daniels (subscriber, #16193)
[Link] (5 responses)
Don't get me wrong, I have no doubt that the two Lumia devices (800 and 710) which have been out for 3 months, have failed in that very short period of time to achieve the 40% marketshare that Nokia's hundreds of Symbian devices priced from $100-$1000+ once had. But I wouldn't really trust his accounting of the numbers, and I definitely wouldn't trust the spin he puts on it.
Posted Mar 22, 2012 12:19 UTC (Thu)
by osma (subscriber, #6912)
[Link] (1 responses)
The conclusion seems to be that N9 has sold about as much as Lumia models in Q4 2011, i.e. around 1 million each.
Posted Mar 22, 2012 12:25 UTC (Thu)
by daniels (subscriber, #16193)
[Link]
It'd be interesting to do a comparison on the numbers from Q1 2012, which should presumably be released quite soon.
Posted Mar 22, 2012 12:36 UTC (Thu)
by pboddie (guest, #50784)
[Link] (2 responses)
I don't want to get all Wikipedia with you but... [with whom?]
Posted Mar 23, 2012 12:55 UTC (Fri)
by nhippi (subscriber, #34640)
[Link] (1 responses)
Anyone who actually goes through the time to read Tomis articles. For example his source for the "1.5 -> 2.0" million N9 sales? Anonymous comments on allaboutsymbian.com, and from there picking up the biggest number someone made.
Also Tomi is wrong in his basic idea that Nokia was doing just great until Elop came and ruined everything. Nokia was already ruined by his predecessor Kallasvuo who slept through the rise of iPhone and Android.
Posted Mar 23, 2012 16:45 UTC (Fri)
by pboddie (guest, #50784)
[Link]
What Nokia has apparently required all along is management to actually harness the vast resources of the organisation such that the company isn't continually punching below its weight, and it needs to do so by actually dealing with apparently deep-seated organisational issues, not by hoisting a new flag and laying people off.
From what I have read of that blog, the author has an apparently reasonable grasp of market behaviour and the channels, wild sales/shipping estimates notwithstanding. Although I don't buy into some of his enthusiasm, I wouldn't write his opinions off too readily, especially the ones that are blatantly verifiable.
Posted Mar 22, 2012 1:58 UTC (Thu)
by imunsie (guest, #68550)
[Link]
The more official method is to boot an "open mode" kernel using the flasher tool for Harmattan that Nokia provides (which allows a custom kernel to be loaded for a single boot, or flashed permanently):
A kernel that has already been modified to remove aegis is available at:
Just be wary of modifying an N9 in open mode if you later intend to revert back to a stock kernel as a checksum failure will cause the device to lock itself until it is reflashed.
This thread has more details on openmode:
The official N9 kernel sources are available at (I wish this was a git tree):
Having said that, I'm sure INCEPTION is much easier to use than flashing a custom kernel (my N9 is currently getting it's GPS repaired so I haven't been able to try INCEPTION since it came out).
Posted Mar 22, 2012 8:31 UTC (Thu)
by buchanmilne (guest, #42315)
[Link]
Note that as of PR1.2, there *is* video support for GTalk, which uses the front-facing camera. Apparently Skype support may be coming (in PR1.3)?
(I am surprised that on an open-source-related site, lack of features for a proprietary protocol and proprietary application was the first complaint, rather than an open standard with a completely open implementation on the device, in XMPP/Jingle ....)
From an engineering perspective, I believe Nokia took the right approach. I suspect some of the missing pieces (easier access to kernel source, easier means to install/build open mode kernel, lack of default repositories equivalent to extras/extras-devel for Fremantle etc.) were due to the change in direction after Feb 11 2011.
Posted Mar 22, 2012 12:15 UTC (Thu)
by dps (guest, #5725)
[Link]
That said I have a dumb phone which offers voice and text messages but very little else. It supports two bands, neither of which is used for GSM in the US, and has no WiFi, bluetooth or web browsing features.
I also don't care about twitter or facebook, google plus, etc and any do not want any integration of those on any device whatsoever.
Posted Mar 23, 2012 14:02 UTC (Fri)
by corbet (editor, #1)
[Link]
Posted Mar 28, 2012 9:28 UTC (Wed)
by mikhas (guest, #83738)
[Link]
The framework powering the system and the Swype keyboard is open-source: http://maliit.org/ One can write different input method plug-ins for it and they can then be used on whatever platform the framework has been integrated with.
We usually have gotten slightly better reviews than what is presented in this article, but you cannot please everyone (https://wiki.maliit.org/Reviews). The article also misses out on text selection, which has gotten a lot better in PR 1.2 (before, you simply could not select text from a website …). There some videos on youtube, hopefully showing that mobile text input is much more than "just a virtual keyboard": http://www.youtube.com/user/maliitorg
Please also notice that the terminal shown in the screenshot is open-source, too, and it's a pretty advanced terminal, given that it runs on a mobile device. It comes with touch support for text selection and copy'n'paste, zoom and different color schemes (you can cycle through them by swiping). The project is hosted at gitorious: https://gitorious.org/meego-terminal
It also shows a nice integration feature with the keyboard, in that it is the terminal that fully controls (apart from styling) the input method toolbar that is shown on top of the keyboard (see screenshot in article). Technically it would have been feasible to provide word prediction that is fed by bash completion, but we might have to demo that elsewhere.
Disclaimer: I am a Maliit developer.
Posted Mar 29, 2012 6:56 UTC (Thu)
by stem (guest, #83810)
[Link]
~ $ tail -n1 /usr/share/applications/facebookqml.desktop
Please note that NemoN9 is not a separate project, but simply a set of instructions on how to install the Nemo Mobile N950 port on a N9 device. It has not been updated since November simply because the instructions still work.
(Well, you need to replace the Nemo Mobile N950 image link with a more recent one, but if you can't do that yourself you are definitely not in the target audience).
/ Jon, the author of the Nemo Mobile N9 instructions.
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
* terminal is not installed by default, it comes with developer mode
* Harmattan, the OS used in N9, although called MeeGo 1.2, is more Maemo 6 than Meego
The N9: what MeeGo could have been
The N9: what MeeGo could have been
* it's *installed* when you enable developer mode (not sure it's really important, but you seem to insist)
* it seems relevant when you talk about the future, and how MeeGo could see releases on other devices. MeeGo /might/ continue, but it'll just move more away from Harmattan than it is right now, that's all
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
When you've got developer mode, you can remove annoying apps like this:
How to remove annoying apps
dpkg-divert --local --rename /usr/share/applications/facebookqml.desktop
After a reboot (properly with shutdown -r now) facebook is gone for good.
How to remove annoying apps
How to remove annoying apps
How to remove annoying apps
How to remove annoying apps
How to remove annoying apps
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
I saw one recently in a tech store in South Africa, but was shocked to see its price tag rivaling the Galaxy Note and the Galaxy S2 on the same shelf.
For some reason, most operator-run shops are selling the N9 at higher than Nokia Retail prices. At the Nokia shop in Vodaworld (Midrand, Johanesburg) the N9 was R5600 at launch. Most 'Prepaid' prices advertised by operators are in the region of R6300, the same price as the SGS II.
An aside: the last Nokia phone I used was an Express Music 5800. Managing network connectivity on that damn phone was such a pain in the ass. Nokia made it so difficult to add APNs for different networks (we have many in Kenya). Also, prioritizing known Wifi networks over 3G never worked for me. I never seemed to be able to browse the net properly on it.
This is the Symbian (as least Series60, I haven't used Symbian^3) experience, but the Maemo experience (at least on my N900) is vastly different. Wifi networks are very easy to add, and automatic switching to WiFi works well and reliably (except for some reason switching to networks using WPA2-EAP/802.11x, I am not sure if this is fixed in Harmattan / N9). But, on Series 60 (including a colleague's E71 I set up last month), just configuring WAP-EAP/802.11x is virtually impossible if you don't understand the technology quite well (it will give an obscure error message which doesn't allow you to guess that the problem is a missing CA certificate, even after you have changed all the default EAP settings which actively prevent the most common EAP methods from working)
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been, sell us an N950!
The N9: what MeeGo could have been
Yesterday I was actually looking around to figure out how to get an N9 (I live in the US). I love my N900's physical keyboard and easy access to the terminal and root. Seeing this review of the N9 makes me sad because it sounds like even if I get an N9 I won't be terribly happy with it.
Looking for a freedom-friendly smartphone
I've asked around: "What smartphone gives me root, has an OS that'll be around in 2 years, and won't crash too much?" and find the answers dispiriting. Anyone tried Geeksphone Zero?
Looking for a freedom-friendly smartphone
Looking for a freedom-friendly smartphone
Looking for a freedom-friendly smartphone
The N9: what MeeGo could have been
http://everythingn9.com/the-elusive-unicorn-of-nokia-the-...
Then again, the N950 was not even intended to be a polished product.
The N9: what MeeGo could have been
The N9: what MeeGo could have been
* The hardware is incredibly fragile. After a few weeks of use, the headphone plug broke, and the hinge used to pull out the keyboard looks really fragile.
* When making a call with my n950, the person on the other end will receive five second bursts of loud static about once per minute.
I have an n950 lying around somewhere, and I can't recommend it to anyone.
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
http://apps.formeego.org/applications/n9/pr1.0/harmattan/...
The N9: what MeeGo could have been
> micro-USB connector instead of something special Nokia made up for that
> specific handset.
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
Transition to FOSS
Transition to FOSS
Are there any well known technology companies which have successfully transitioned from the traditional, proprietary development model to FOSS?
Transition to FOSS
Transition to FOSS
Transition to FOSS
Transition to FOSS
Transition to FOSS
Transition to FOSS
http://en.wikipedia.org/wiki/Android_Dev_Phone
http://live.gnome.org/Maemo/GtkContributions
https://bugzilla.gnome.org/show_bug.cgi?id=315645
Transition to FOSS
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
Removing applications
Removing applications
Removing applications
Removing applications
http://everythingn9.com/remove-application-shortcuts-noki...
The N9: what MeeGo could have been
The N9: what MeeGo could have been - desktops and "views"
(At least on the N900) you have four (maybe more, but I never used more) "desktops" - comparable to desktops in e.g. KDE. On each of this, there may be a number of icons to start applications or running applets. In addition to the desktop view, you have a general kind of application manager view, where you find icons for all installed applications - to use if you want to start an application that has not gotten an icon on one of the desktops. The third view is a list of running application where you can select which to run in the foreground.
The N9: what MeeGo could have been - desktops and "views"
The N9: what MeeGo could have been - desktops and "views"
The N9: what MeeGo could have been - desktops and "views"
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
The N9: what MeeGo could have been
Meltemi is killed at Nokia
The N9: what MeeGo could have been
The N9: what MeeGo could have been
http://www.meltemiblog.com/2012/01/n9-vs-lumia-sales-numb...
The N9: what MeeGo could have been
The N9: what MeeGo could have been
Unfortunately, Tomi Ahonen has gained a reputation over the past 18 months or so for putting an interesting spin on actual facts, if not just outright making things up.
The N9: what MeeGo could have been
The N9: what MeeGo could have been
Security framework
http://tablets-dev.nokia.com/maemo-dev-env-downloads.php
http://maemo.cloud-7.de/HARM/N9/openmode_kernel_PR1.1/
http://talk.maemo.org/showthread.php?t=81579
http://harmattan-dev.nokia.com/pool/harmattan/free/k/kernel/
The N9: what MeeGo could have been
The camera is quite nice; there is also a front-facing camera, though the built-in Skype client is unable to use it.
Don't you mean 'the built-in Skype support for IM and calls'? AFAIK, like Maemo Fremantle/N900, there is no separate Skype application, instead there is integration into the rest of the phone (via telepathy etc.).
Annoyingly, none of the home screens rotate when the phone is held in the landscape orientation. Applications handle rotation without trouble, but the home screens appear to be special.
I believe this can be changed by editing a css file, or, for users who are inexperience with text editors and CSS, via an app (the best one for PR1.2 seems to be N9 Qtweak.
On the other hand, the web browser makes one wish for the Android equivalent.
Or even the Maemo Fremantle/N900 equivalent, which should have been much easier to provide. But, Firefox is available from the Ovi store, and ships with Flash support, which the built-in browser (using QtWebKit) does not have.
It wouldn't do, after all, to let those pesky users have direct access to the media files that they think they bought on their handset.
I think that is a bit unfair. Nokia is currently the only company that actually sells perpetual use tracks of songs from popular artists in a number of countries (such as South Africa), where iTunes, Amazon and most other competitors currently don't provide any service. However, note that the Nokia N8 had a subscription-based access to an unlimited music library of DRM content, and similar business models require DRM. But, surely, the user should be aware of what they have subscribed to (and not bought). In fact, my only digital music purchases have been from 'Ovi Music', which can be accessed without any proprietary software.
The N9: what MeeGo could have been
Amusingly, I only today stumbled across NITDroid, a project to port Android to Nokia tablets that has been expanded to include the N9. The current status suggests that, while it works, it's definitely an early-adopter sort of distribution at this point.
NITDroid
The N9: what MeeGo could have been
The N9: what MeeGo could have been
NotShowIn=X-MeeGo;