Download the binary suitable for your OS and install the package. You need the flasher to load the kernel to the device. The original Maemo kernel returns when the device is powered off.
Here are the steps to load the MeeGo kernel to the N device. If your PC screen do not display the above message, try attaching the USB cable whilst holding the "u" button on the keyboard of the N Installing MeeGo on the Nokia N Oct 29, Developer , Smartphone. Step-by-step guide to install the MeeGo image to your Nokia N device.
An image writer utility, like Win32DiskImager. Nokia haters Start gettn sumtin beta 2 stand on Nokia is still trying to catch up. They're really getting far behind the competition against Apple and Android. Samsung and LG might even overtake them soon. And Motorola is gaining so much success lately as well. Nokia should start producing Android devices if they want to keep up.
Greg, 05 Apr Disagree, the N was marketed miserably but the platform is virtually a Maemo spinoff. When the process is complete, you will get image file named mg-handset-armv7nhl-nde-sanity Now rename the extension of file from. Open the Zip file and start Win32DiskImager. Using Win32DiskImager browse to the folder where you have kept the extracted MeeGo image file and select it. Notice the drive letter of MicoSD card in the computer. It will take around min to complete. MeeGo OS will start loading.
If you want to boot Maemo 5 then slide out physical keyboard and during booting and interrupt the process by pressing any keys. You can contact me on Google Talk. I tried do it under linux and windows, both failed.
Help me! Thank you! But when I connect N to a linux machine, I can see the SD been parted to 2 partitions, one is boot, one like normal linux. Hope to chat wid u there so atleast i can install meego or gingerbread on my n coz im still using that borring maemo.
Hey hi i tried downloading MeeGo 1. The MeeGo DE software is currently in a working and remarkably stable state, though the developers caution that it still should not be used as a daily replacement for the N's default Maemo OS — there are the to-be-expected bugs, plus the loss of warranty protection. Still, the team has set very user-oriented goals for the project, and it is a pleasant surprise to see just how well some of them work.
Jukka Eklund led a panel session presentation about the MeeGo DE release on the final day of the conference. In it, he outlined four use-cases that the team established as its goals: working cellular calls, working SMS messages, a working camera, and a browser working over WiFi.
The camera goal was added to the list along the way, he noted, because the camera code was working so well. In addition to that core functionality, the team decided to include certain add-ons on top of the base MeeGo Handset distribution, including additional applications the Firefox For Mobile browser, Peregrine instant messenger, the QmlReddit news reader, etc. The new functionality includes USB modes not yet supported upstream, plus the ability to lock and unlock a SIM card with a PIN code — including a user interface to do so.
That is a novel and interesting approach: the Linux Foundation makes much out of MeeGo's ability to shorten product-development times and costs, but typically with real-world examples where a product emerges only at the end.
The WeTab team was on hand during the MeeGo Conference keynote to say that their MeeGo-based tablet went from design to production in a scant four months, for example. There is certainly no reason to doubt those numbers, but actually seeing the process documented is even better. On top of that, Nokia has long defended its right to keep its own UX layer proprietary because it is the only way to " differentiate " its MeeGo products in the market. That mindset, it seems, has led partly to the project's current UX strategy, where MeeGo releases drop with a set of "reference quality" UXes that vary considerably in usability and polish.
Some such as the dialer have already been merged; others such as the theme and UI layer have a less-than-clear fate awaiting them. Eklund covered the current status of the SF release, gave some time for fellow panelists Makoto Sugano, Harri Hakulinen, Marko Saukko, and Carsten Munk to make comments, then proceeded to demonstrate the new code running on an N The demonstration included the revamped dialer, which he used to call Tom Swindell — the developer who ported the dialer to QML — there in the audience.
He also showed off the basic application set, and demonstrated the N's ability to run the MeeGo Tablet UX although the tablet interface is not quite usable, as it assumes larger screen real estate. As nice as the demo was, I decided that I must try out the code on my own N in order to get the full experience. Installation instructions are on the MeeGo wiki, which proved to be the only challenging part of the process — not insurmountable, but probably due for a cleanup.
The wiki spreads out download, flashing, memory card preparation, and installation instructions over a large number of pages, some of which are not properly updated to reflect the current state of the release and show signs of multiple editors crossing paths.
For example, the "Install image" table lists two separate processes as the " recommended way " to install MeeGo DE, and the most-recommended-process is listed as "Dual-boot install," which is a separate entry from "MMC Installation" even though it in fact requires installing MeeGo DE to the phone's MMC card. In addition, there are a few places where the instructions say that a 2GB memory card is sufficient, but this is no longer true as of the SF release, which takes at least 4GB of storage.
The simplest option is to install the uBoot bootloader on the phone which necessitates activating the unstable Maemo Extras-devel repository first, at least long enough to add uBoot , then to write the raw MeeGo DE image to an un-mounted microSD card. On the SF release download page , this is the large. It is theoretically possible to download the raw image from the N itself, then pipe it through bzcat into dd to write it directly to the memory card, but I wimped out and did the card-preparation step from a desktop Linux machine instead.
With the newly-written memory card inserted into the phone, all that remains it to power it on. The uBoot loader will recognize the bootable volume on the card, and load it by default, booting the phone into MeeGo DE.
To boot the phone into Maemo again, you simply reboot with the memory card removed, or type run noloboot at the uBoot prompt at power-on. There are a few areas where DE is a noticeable improvement over vanilla MeeGo Handset UX: the UI widgets are more consistent in appearance, the text is higher-contrast and more readable, and the UI navigation cues such as the "return to home" button and the application grid's page indicator easier to pick up on.
Loading applications is slow, although this is no doubt largely dependent on the speed of the memory card I used.
0コメント