Even if some people managed to build their own images here and were able to boot Meego, I feel it's useful to inform everyone why there is currently no N900 image and the current state of Meego on the N900. I got this email 3 hours ago from the meego-dev@meego.com mailing list:
Originally Posted by
Subject: [MeeGo-dev] About building Handset UX Day1 image for N900; some notes and explanations
From: harri.hakulinen@nokia.com
to: MeeGo-dev
sender-time: Sent at 4:16 AM (GMT+02:00).
mailing list: meego-dev.meego.com
Hello Meegos,
As you know, yesterday Handset UX developement was opened in MeeGo. As N900 is the other hanset reference device in MeeGo, we are of course actively developing all the required adaptation elements to make it possible to run MeeGo Handset UX on N900.
From N900 adaptation point of view, we have had some quite nasty last minute stabilty broblems related to our Day1 builds. It looks like Wlan and connman are not working nicely together now, and we don't know yet what exactly is the problem. We have recently started to use .35rc3 kernel, but that does not seem to be the issue, it's rather something related to wlan or Connman configuration, or something above connman that we are not fully aware of.
Now, when all the related source's are available, perhaps we can solve those issues as MeeGo community !
This really is Day 1 "codedrop" for Hanset UX rather than release, we also have bunch of other known issues and errors, like
- Wlan does not work on every boot
* sometimes you need to boot again..
- Sreen rotation does not work
* our accelerometer sensor is not working right at the moment
- On some applications closing button is hardly visible
- You can use home button once per application to go to task swicther, and come back, but not more than that
* this is known bug in framework
- There is no phone functionality
* Our new opensource drivers for modem module are not stable enough yet.
And in addition we still have some issues know already earlier, like
- Battery loading does not work
* BME, (nokia closed) component still don't work properly..
Because of all this and some misc problems, we decided that there is no point of creating ready-made image for N900. However, there is everything available to build your own image if you are really interested to try it now. Many things are now moving all the time, and what you get with these instructions is in fact the daily image containing the latest state of MeeGo Handset UX development for N900.
After all, this is "code drop" related to MeeGo development, and it is actually interesting first exercise to setup your build environment and start your MeeGo development by creating your first image yoursefl !
The kickstart file to enable the image creation is available at
Before you can download it, you need to enter valid IMEI code of your N900 device. That is required because of our current licensensing situation for some closed components that are required to build functional Handset UX Day 1 image. We are working on this issue and I hope we can get rid of this extra step in very near future.
Even if some people managed to build their own images here and were able to boot Meego, I feel it's useful to inform everyone why there is currently no N900 image and the current state of Meego on the N900. I got this email 3 hours ago from the meego-dev@meego.com mailing list:
From his reply, I see that the current version of MeeGo and Android N900 port has lots of similarities in terms of what working and what not.
As far as I understand everything, it seems that we will have a completely working Meego.
I understand it mainly from the fact that according to Patola 's mail the IMEI we have to input in order to get the latest meego build is due to the closed components licensing.
From this I understand that those closed components are made available to the meego devs hence they have access to the cellular modem,3G ect, resulting in a fulctional meego release for the n900(minus multi-touch )
If one of those with more knowledge can approve of this i'll be happy. t might end all the speculation around if "this" or "that" will work.
Important to note: even if you don't like the UI, it's completely open, replaceable.
It doesn't matter that it can be replaced, it should at the very least be desirable as is, right out of the box. Even if that look and feel is simply utilitarian, it is better than trying to make some kind of cute statement, one that is simply lost on me. I know it's largely just a wallpaper, however, the videos floating around show a great deal of wasted space between elements.
guys can u guys help me this, i follow the step to step 7 which is
7)Mount the SD card, replace /dev/sdc1 with your device and first partition.
Code:
mkdir mount
sudo mount /dev/sdc1 mount
and my sd name is /dev/sdb2
so how do i do it ?
mkdir mount
sudo mount /dev/sdb1 mount
but it then return command is it is busy or not found in fmap or something
guys can u guys help me this, i follow the step to step 7 which is
7)Mount the SD card, replace /dev/sdc1 with your device and first partition.
Code:
mkdir mount
sudo mount /dev/sdc1 mount
and my sd name is /dev/sdb2
so how do i do it ?
mkdir mount
sudo mount /dev/sdb1 mount
but it then return command is it is busy or not found in fmap or something
Your SD name would actually be /dev/sdb, not /dev/sdb2. The number at the end refers to a partition number on the card - you don't write MeeGo to the partition but rather write it to the root car itself so that it can create 2 of it's own partitions.
Your dd command would have of=/dev/sdb in it and then you would mount /dev/sdb1 when that is finished.
If you just want to run MeeGo handset to see how it looks like, and don't necessarily need it on your N900, and have a netbook or other MeeGo-compatible computer at hand, you can get a netbook build of the handset UX from here:
)