Maybe you haven't noticed, but they are, along with Nokia ...

You have one, Maemo. Meego is not really ever intended to be more usable on N900 than Maemo. If a production-ready Meego for N900 is the *only* reason you are using the N900 and visiting this forum, you are wasting your (and our) time.

Your criticism is unfair. Please indicate what hardware adaption of Meego is not up to scratch. Most of the issues affecting use of the N900 (e.g. no PIN entry dialog) in current builds (please go see the reports on qa-reports.meego.com) are non-N900-specific.

This has nothing to do with Maemo or Meego, the hardware is still not too bad (only very expensive handsets have better hardware IMHO), but is quite old, and will not be competitive against newer models for long. But, that is *hardware*.

While Meego does provide *some* features that will make the N900 seem a bit faster than when running Maemo, the penalty for running from SDHC will always have a greater effect. I haven't seen anyone proposing a Meego image suitable for flashing over Maemo, so, really, don't expect Meego on N900 to be an every-day experience.

(Note to others, this reply assumes abill_uk isn't trolling, if he trolls further I will not feed him any more, and neither should you)

Since abill_uk is on my ignore list by now, I'd like to say we're making increasingily rapid progress on the MeeGo DE and MeeGo N900 work as anyone who follows us is quite aware of. (FWIW, we post meeting logs every week to relevant mailing lists on meego.com, ~230 people in our IRC channel actively discussing. We're not really discussing much on talk.maemo.org but on mailing lists and IRC instead - you're all very welcome there). meego-handset@meego.com mailing list is the primary area these days

However, hardware adaptation is often of the nature that you don't really see it in a UI but it matters in actual usage. As an example, we have been working (succesfully) getting CPU frequency scaling working and power management. Which means you have longer battery life in usage (and it doesn't get hot while in usage). Or the fact we actually have a open source camera stack, though some features (autofocus, etc) will be closed source. That we upstream the drivers means that people can upgrade N900 to newer kernels with ease in longer term.

The basic UI is already quite fast. On UI side the applications in Handset has been neglected as they're being replaced with those from Tablet UX. Dialer has been undergoing redesign in QML (by our local tswindell/alterego).

I'll address some points by abill_uk:

(about RC1, RC2 dates..)
We actually have a wiki that specifies the MeeGo release process. http://wiki.meego.com/Release_Engineering/Plans/1.2 , http://wiki.meego.com/Release_Engine...lease_Timeline - the information is actually quite visibly on display and there's not even a sign saying "beware of the leopard".

So, given that you seem to not have a simple clue about hardware adaptation - kernel development is actually hard. I love community and all - but I also know that a community will require certain skill within to accomplish some things. And proper development skills for hardware adaptation are really hard to come by. Nowadays we have people attached who actually made the product kernel for Maemo5 and it -still- takes time. Why? Because hardware adaptation isn't simple. This isn't a X86 device - it is actually high tech.

We're in the N900 hardware adaptation working to provide a solid basis for development. This can be seen in http://cybercomchannel.com/meego-phone-cybercom for instance - this was done in minimal time because of a solid hardware adaptation.

Two challenges has existed here: 1) Handset UX has been written in MTF which was new technology for many and almost immediately obsoleted by the choice by Nokia to have one developer story, Qt and Qt Quick. 2) Handset UX was left to bitrot around same time. -- means very little talents available to do anything to improve matters.

This made it hard to build a community around.

I'd like to say that by now, the tablet UX solves these issues by being in QML and contributions are very welcome. In fact, it's already attracting contributions.

MeeGo on N900's end result is a device you can modify to your heart's wishes, and with ease. With the DeveloperEdition work, it will have a solid basis of features that just work(TM).

The only closed source binaries we have are:
* SGX drivers (with vsync support), replacable with deliverables from TI OMAP3 if you so wanted
* BME (battery management)
* WLAN and Bluetooth firmware + their calibration tools

Rest is open source and modifiable - and to be honest, Tablet UX seems to work really well when it comes to usage (we're still sorting out some optimizations and fixes for ARM). I intend to use it for my kitchen tablet myself.

Now, isn't that something you'd like? Limitless* possibilities on your mobile device.

(*) Let's not get into a discussion about Flash Player and other closed source binaries. That's one of the reasons it's called 'developer' edition)

It was pointed out by the Meego team the hardware minimum requirements and the N900 falls short of those requirements so what you are say "Maybe you haven't noticed, but they are, along with Nokia ..." so where is your proof? because where i stand Nokia have ceased 100% support of any kind for the N900 and the cpu it uses OMAP 3430 has now been superceded at least 2 times as their is now the 3630 and the 3640.

I raised the possibility of changing the 3430 with the 3630 on this forum, being the same package but not a easy mod by any standards.

There is your problem and people who know about os programmers know full well they move forward not backwards, that means the N900 is now dated and not only Nokia have moved on but also Intel.

So having said all this where is the proof MeeGo is to be full established as an os for the N900 by Nokia and Intel?.

In order to establish Meego for our device there has to be a team willing to do this as it is going backwards instead of catching up with technology.

I just don't see this happening and the reason i pulled a comment about an unknown telling us information from some video, it should have came from Stskeeps, that was my point there.

I have my doubts but time will tell, i dont go by hype as we learned a huge lesson from Qwim who led us all to believe Nokia would do everything for the N900, ha what a let down that was !.

I am a realist not a pessimist.

That is an obvious one to answer and any handset with 512mb ram and a 1ghz cpu will be the target, the N900 fails in these specs and the reason why i said MeeGo would have to be downgraded to even work on this device.

great news, so I can test some stuff out tonight, cheers mate!

The only thing i ever read that was even slightly promising was dashed by the latter comments and this is what i read.....

This hardware adaptation team maintains the port of MeeGo for the N900.

Due to the use of closed components in the hardware adaptation, this team cannot run fully in the open. However, it will strive to minimize the non-openness in its work related to those components and the number of those components. Closed components will be maintained exclusively by employees and subcontractors of Nokia.

Source http://wiki.meego.com/Devices/N900

Once i read the Nokia part that brought back the grim past of how they dropped us like a stone.

I wish the team luck but i do not think it will run the way people hope.

If i can find a way to up the ram and use the overclock routine then just maybe i might get close to a MeeGo spec device.

I've been using MeeGo 1.1 on my Lenovo Ideapad for months and it is fully functional.

Where have you seen that? Such a statement is at odds with the N900 being the MeeGo reference handset device.

That device is a nice little laptop but way supasses the N900 Texrat, for a start it has got a 1.6 ghz cpu and upto 1gb of ram.

I wish the N900 could match those specs.

That was mentioned in Handset architect talk at MeeGo conference, however, I think the field might look slightly different these days. I haven't seen a single compliance document stating this to be the minimum for handset profile currently.