Meego 1.1 RC?

[damnshock]

I was checking around on the meego webpage and check what I found:

http://repo.meego.com/MeeGo/builds/1.0.99/1.0.99.0.20101001.1/handset/images/meego-handset-armv7l-n900/

Acording to this:

http://wiki.meego.com/Release_Engineering/Plans/1.1

It's the first release candidate for meego 1.1 :)

It's weird though as I tryied last week builds and it was totally *unusable*.

Just wanted to share the information ;)

Regards

[HtheB]

Hmmm.. Very Curious about it :D
Anyone wanna try it out? :P

[damnshock]

Hmmm.. Very Curious about it :D
Anyone wanna try it out? :P

Downloading it right now ;)

I'll keep you posted.

[cyeung]

Downloading it right now ;)

I'll keep you posted.And let us know if it provides full functionality of the phone (make and receive phone calls, use 2G/3G, etc.)!

[Stskeeps]

Release candidate periods are for weeding out bugs and some are bigger than others (making things unusable). There's a final release at end of months.

[msa]

does it mean this is fully functional version including telephoning-capabilities?

[Stskeeps]

does it mean this is fully functional version including telephoning-capabilities? at least thats what i would expect from a RC :O

Yes, if you have a PIN-less SIM you can make calls. It comes out the speakers but so it goes.

[Reffyyyy]

And let us know if it provides full functionality of the phone (make and receive phone calls, use 2G/3G, etc.)!

I could make and receive phone calls with the image from a week ago.

EDIT: Nevermind, beat me to it.

[hassan_badredin]

Do i need a Memory Card or i can install to internal memory?
maybe dual boot something?
thanks

[Stskeeps]

You need a microsd and no, no way around it.

[damnshock]

For those who wanna know:

* 1.1 Schedule
* Feature Complete - 25 Aug - DONE.
* Code Freeze -
* 23 Sep - today - Bug cut-off
* 27 Sep - Monday - Critical bug cut-off
* 29 Sep - Branch 1.1. Trunk re-opens on 1.2. [Please note: PRC out 1st week of Oct]
* 28 Sept - 18 Oct - Bug-CCB period
* 18 Oct - Final critical fixes.
* 19 Oct - Final RC.
* Final Release - 27 Oct

[bsving]

Tried it yesterday, useless then and it looks like this is the same version.

[Airtux]

It's nice! its will be a final version for the Nokia N900 Meego at the end of
months?

Please share a vidéo presentation of Meego 1.1 for N900 or pictures!

[Stskeeps]

One thing to keep in mind:

What is getting released in end of October is a platform. This platform has reference applications and such and fairly good N900 support, but it's probably not enough for most end-users.

I'd like to motivate people to take this platform and base on top of it shape it into something they'd like for their phone. Even backporting things from 1.2. Things you could do would be adding MP3 codecs, community Qt applications, etc. It's free to modify and hack and even to publish your own versions of online (some of the closed bits only if you do it on a non-commercial basis, NeoPwn, I'm looking at you).

Next version of MeeGo is in 6 months after 1.1 release and you can do exciting things early on if you organise yourself like the community SSU guys. Even kernel improvements from 1.2 can be used in 1.1 as we're not upgrading the kernel, likely.

There will be platform bug fixes coming out for 1.1 but no new features after release date.

[damnshock]

One thing to keep in mind:

What is getting released in end of October is a platform. This platform has reference applications and such and fairly good N900 support, but it's probably not enough for most end-users.

I'd like to motivate people to take this platform and base on top of it shape it into something they'd like for their phone. Even backporting things from 1.2. Things you could do would be adding MP3 codecs, community Qt applications, etc. It's free to modify and hack and even to publish your own versions of online (some of the closed bits only if you do it on a non-commercial basis, NeoPwn, I'm looking at you).

Next version of MeeGo is in 6 months after 1.1 release and you can do exciting things early on if you organise yourself like the community SSU guys. Even kernel improvements from 1.2 can be used in 1.1 as we're not upgrading the kernel, likely.

For example, one thing important for end users that is not supported in this release is 3G browsing...

[Stskeeps]

For example, one thing important for end users that is not supported in this release is 3G browsing...

Once the UI exists in MeeGo 1.2 for this, it should be trivial to backport. The problem is that the UI doesn't exist for setting up APN and that junk, but is coming for sure (The Intel guys simply didn't have a working modem on their Aava device)

[Laughing Man]

It's nice! its will be a final version for the Nokia N900 Meego at the end of
months?

Please share a vidéo presentation of Meego 1.1 for N900 or pictures!

No. And phone support works, but only if you like to make phone calls via speakerphone.

[Stskeeps]

No. And phone support works, but only if you like to make phone calls via speakerphone.

And this only because we don't have a policy daemon setting up audio routing :)

[Radicalz38]

Once the UI exists in MeeGo 1.2 for this, it should be trivial to backport. The problem is that the UI doesn't exist for setting up APN and that junk, but is coming for sure (The Intel guys simply didn't have a working modem on their Aava device)

well as said it's a UI issue so I would like to assume that it still can be set to some other way like command line am I right? Could I know how?

[Berserk]

I'd like to motivate people to take this platform and base on top of it shape it into something they'd like for their phone. Even backporting things from 1.2. Things you could do would be adding MP3 codecs, community Qt applications, etc.
Since Qt is cross-platform, porting Qt apps from N900 (PR1.2) tot MeeGo shouldn't be very troublesome I think?
Apart from different system variables/standards maybe?

It's probably not that easy :p

[pwm]

The term release candidate seems to have received a new meaning.

A release candidate is not an alpha or beta. It should contain the full functionality, be thought to be (almost) bug free and be subject to a code freeze where any found bugs are only fixed after decision on project meeting.

I have a hard time seeing a release without PIN-code support as a release candidate unless PIN-code is seen as a bonus feature.

On the other hand - the N900 has been living with prereleases from day one.

[friesoft]

Since Qt is cross-platform, porting Qt apps from N900 (PR1.2) tot MeeGo shouldn't be very troublesome I think?
Apart from different system variables/standards maybe?
It's based on Qt but all the platform apps (of handset ui) are written using libmeegotouch (which is based on Qt)

Honestly I don't know if a plain-qt app integrates that well atm into meego... I would love to be proven wrong...

It's probably not that easy :p
I fear so... it will run but it may not look/feel fully native...

[damnshock]

I just gave it a try and... disapointing to say the least.

It's so damned slow it takes ages to load any app (if we can call those things apps). Half of them don't even launch and don't even think on making phone calls or browse the internet :S

Still a *LOT* of work to do!

Regards

[Stskeeps]

It's so damned slow it takes ages to load any app (if we can call those things apps).


What class microSD do you have?

[Laughing Man]

The term release candidate seems to have received a new meaning.

A release candidate is not an alpha or beta. It should contain the full functionality, be thought to be (almost) bug free and be subject to a code freeze where any found bugs are only fixed after decision on project meeting.

I have a hard time seeing a release without PIN-code support as a release candidate unless PIN-code is seen as a bonus feature.

On the other hand - the N900 has been living with prereleases from day one.

It's like the opposite of Google's Beta. =P

[mikecomputing]

And this only because we don't have a policy daemon setting up audio routing :)

I dont get it but were is nokia atm.? I mean why isnt this already backported from Maemo5 that should be that hard :S

I could understand if there is no UI but backenddaemon should that been in place already? :-S


It is great if more people try to test Meego 1.1 on N900 cause this is VERY IMPORTANT for meego to success. But people should not expect Meego as a main OS yet cause its FAR from ready as enduser OS. But dont forget that MMC is a slower than internal so we should not blame Meego on this issues. Infact WidgetGallery is very smooth in Maemo for those who have installed the meego-widgets demos in extras-devel so thats how Meego will work to when installed on core EEMC I guess :-D (when its a ltittle more stable for endusers)

I dont know maybe there is MicroSD that is very fast so if someone could give a tip... I am using Sandisk SDHD but slow to me :-(

But to the developer start port QT apps too Meego now :-D

[Stskeeps]

I dont get it but were is nokia atm.? I mean why isnt this already backported from Maemo5 that should be that hard :S

Nokia's there (as witnessed by the work going into MeeGo and especially MeeGo on N900) but we figured it'd be a priority to 1) have audio into the kernel at all and 2) making phonecalls (which we got done in the last minute before feature freeze), so well, some good things remain for 1.2.

I guess it's more obvious when you look at what has been needed to be done to get where we're at at the moment, but admittedly, platform has areas it's lacking at the moment.

We've set ourselves up for running MeeGo on N900 project for a long time, so we've had to take the long way of upstreaming kernel drivers, doing things the right way instead of with duct tape.

That 1.1 isn't where I (and probably others) hoped it would be is one thing but I see a lot of work being poured into MeeGo 1.1 and even more will go into 1.2.

[TheBootroo]

just tried 1.0.90.4.20100928.1 on my n900
it works !!

dont tried phone but UX is mainly set up.
wifi works
there is autorotation (even home screen and menu and lock screen)
people, social and sms seems to work
i didnt have samples so i didtn try audio or video but album works
config panel is completing up
mostly encouraging

[bsving]

I just gave it a try and... disapointing to say the least.

It's so damned slow it takes ages to load any app (if we can call those things apps). Half of them don't even launch and don't even think on making phone calls or browse the internet :S

Still a *LOT* of work to do!

Regards

I feel the same. This isn't even alpha state, it is nothing yet. How is this going to be in any sort of usable state in 3-4 weeks?

MeeGo for the N900 looks very much like vapor-ware to me. By the time it eventually will be usable, there will be no one left to use it. I mean, I have already had my N900 for a year now. I had some hope to install MeeGo on it, or that the N9 would available before christmas, but right now I don't see any of those things happening any time soon, more like a full year. I feel it's time to move on, but to what? :)

The N8 looks damn tempting and all, but with no physical keyboard. The G2, or whatever the EU version is called also looks very tempting, but Android does not. Any Bada with physical keyboard does not seem to come into existence in the near future. The E7 looks to be the one.

[friesoft]

I also experienced the same trying the latest Nokia codedrop image....
it is really slow because it running from the mmc but well it starts to work mostly...
the statusbar (battery indicator, ... ) still doesn't seem functional, xterm isn't working as well as power off and such stuff....

still LOTS of polishing and feature development ahead.... but we are on the right track =)
a navigation solution would be great... afaik OVI maps API is exposed via the qtmobility framework... so this should be possible...
or will we get OVI maps as soon as meego becomes really production ready?

[damnshock]

What class microSD do you have?

Class 2 card. But that's not the point: nitdroid runs slow on the same card but usable ;)

[Stskeeps]

Class 2 card. But that's not the point: nitdroid runs slow on the same card but usable ;)

It matters a lot when you run real Linux :) I would recommend at least class 4.

[Airtux]

Sorry to insist, it is possible that someone made a small video Meego 1.1 for N900? its be really nice.
Thanks.

[bsving]

My card is a 4GB and say class 6. It still is unbelievably slow. When connecting to internet, the touch screen keyboard blacks out. Terminal isn't working, although I can see it when it is "minimized" running in the background. When booting it starts all black after a minute with the usual text, and take several minutes before it does anything.

I tried it a month or so ago, and it worked better back then than it does now. I have the dual boot kernel (from Nitdroid) installed, could that in any way have an effect on this? (I believe not, but my experience with MeeGo on the N900 is abysmal, not at all encouraging as some describe it).

Edit: I have to add that Nitdroid runs completely fluent from my card, so I don't believe my card is slow.

[Stskeeps]

My card is a 4GB and say class 6. It still is unbelievably slow. When connecting to internet, the touch screen keyboard blacks out. Terminal isn't working, although I can see it when it is "minimized" running in the background. When booting it starts all black after a minute with the usual text, and take several minutes before it does anything.

I tried it a month or so ago, and it worked better back then than it does now.


First boot is always slow due to sreadahead picking up data and tracker indexing the sample media. But you're right, things are slower than they should be.

We suspect there's a MMC performance problem in the 2.6.35 kernel on OMAP3, not so much the distro itself.

[Dave999]

since it not for end user it no probem if its uber slow, right? ;)

[Odd_gunnic]

videos for the less adveturous would be really good.

On a side note, for anyone with the latest build, are you able to change wallpapers and/or themes if any exist?

[Viny]

Yes can someone please post a video of this for the noobs?
and please dont say me, "you should" .. i would i dont know how to install it and besdies no micro sd.


Thanks

[damnshock]

Yes can someone please post a video of this for the noobs?
and please dont say me, "you should" .. i would i dont know how to install it and besdies no micro sd.


Thanks

It'll record one tomorrow night although there's no much to see anyway...

[cfh11]

guys... just search for "n900 meego video" there are at least 100 out there

[Airtux]

I have not found the last release of Meego 1.1 vidéo. I have just found old version of Meego 1.1.

[geneven]

Just for people who have forgotten:

release candidate means "this MIGHT be the candidate we are releasing as a final. We need some testing to make sure."

Anyone who uses it in another sense is flying in the face of what words mean.

[sjgadsby]

The term release candidate seems to have received a new meaning.

A release candidate is not an alpha or beta. It should contain the full functionality, be thought to be (almost) bug free and be subject to a code freeze where any found bugs are only fixed after decision on project meeting.

MeeGo has a fixed release schedule. What's ready when release time rolls around ships. This isn't a "when it's done" project.

Also, the main MeeGo project isn't focused on polished products for end users. MeeGo's target users are hardware companies who pick up whatever patch levels of MeeGo components they'd like to support, add what hardware drivers they need, layer their differentiating applications and UI tweaks on top, and sell that package to end users.

I had some hope...that the N9 would available before christmas...

Nokia's first "MeeGo" device will be running Maemo 6 with a new name and a few bits added on for MeeGo compatibility. True MeeGo has time to firm up before Nokia uses it as the basis of the software for one of their phones.

[bsving]

Nokia's first "MeeGo" device will be running Maemo 6 with a new name and a few bits added on for MeeGo compatibility. True MeeGo has time to firm up before Nokia uses it as the basis of the software for one of their phones.

Do you know this? or are you speculating? If this is true, then the N9 (the first MeeGo device presumably) makes no sense at all. MeeGo makes no sense, and Maemo makes no sense. Makes no sense to me at least. This means that MeeGo is not one year, but two years into the future. With the E7 coming, this makes even less sense. Not even Nokia is so stupid they have to make a handfull of devices just to make it work on Linux.

Who, after the N900 episode, will be crazy enough to get a N9 if it is not even running MeeGo?

[tkatchev]

There is no real difference between Maemo and MeeGo, besides the name and community politics/licensing.

Thus your complaint makes no sense.

Do you know this? or are you speculating? If this is true, then the N9 (the first MeeGo device presumably) makes no sense at all. MeeGo makes no sense, and Maemo makes no sense. Makes no sense to me at least. This means that MeeGo is not one year, but two years into the future. With the E7 coming, this makes even less sense. Not even Nokia is so stupid they have to make a handfull of devices just to make it work on Linux.

Who, after the N900 episode, will be crazy enough to get a N9 if it is not even running MeeGo?

[benny1967]

Do you know this? or are you speculating?

oh come on... you could know (http://wiki.maemo.org/What_can_we_realistically_expect#I_am_confused.__W hat_is_Harmattan_and_what_is_MeeGo_.3F__What_is_th e_difference_between_both_.3F__Do_they_share_commo n_features_.3F) if you only wanted to. This has been explained over and over again.

[sjgadsby]

Do you know this? or are you speculating?

Since the time of the Moblin-Maemo merger announcement, Nokia has been plainly stating that they are continuing to build Harmattan for their next Maemo MeeGo device. Rather than being fully MeeGo, they've said that Harmattan will be an "instance of MeeGo", a transitional release. For that reason, MeeGo-Harmattan (or MeeGo 1.0 N, if you prefer) still uses DEBs rather than RPMs, etc.

If this is true, then the N9 (the first MeeGo device presumably) makes no sense at all. MeeGo makes no sense, and Maemo makes no sense.

While following the convoluted naming scheme can be troublesome, it sounds as though you're throwing up your hands at more than that. What other frustrations do you see?

This means that MeeGo is not one year, but two years into the future. With the E7 coming, this makes even less sense.

How does the E7 enter into it?

Who, after the N900 episode, will be crazy enough to get a N9 if it is not even running MeeGo?

Oh, it will say MeeGo on the box, though there will be some sort of distinguishing mark attached. The latest trend by Nokia has been to use an "N", as in "MeeGo 1.0 N", though it remains to be seen if that will the be final, official choice.

[bsving]

Christ :eek: So it is like this:

->OS2008 - Exclusively Internet tablet OS
Maemo5 - Exclusively N900
Maemo6 - Does not officially exist, but will be used on the next MeeGo device.
MeeGo - Will not be used on anything, but application development will be compatible with Symbian, and Maemo6 (that does not exist) and also with Maemo5.

MeeGo will be supportet on the N900, but not officially. Mostly because Nokia is developing Maemo6 (that will never exist) for the new MeeGo device.

One question still remains; will the new MeeGo device (N9 presumably) ever run MeeGo? Will anything ever run MeeGo.

Maybe I have been sleeping in class, but the facts still remains, MeeGo on the N900 is far far from being in any sort of usable state. But more importantly, why should it ever be in a usable state? When there is no difference between Maemo5, Maemo6 (that does not exist) and MeeGo (that never will exist) from an aplication developer point of view, wouldnt it be better to use those recources to develop Maemo further also for the N900, to keep the N900 alive so that lots of apps (compatible with Symbian, MeeGo and Maemo6) later on can be recompiled for those platforms?

I mean, come on, this is a mess! a terrible mess, an unbelievable mess. No sense of direction, no focus. This simply does not make sense - period.

Symbian, on the other hand, is finally on the right path. It started with S60.5 and continues slowly but steadily evolving into the future.

The E7 is Nokias new "comunicator", the new flagship. This can only mean that the N9 is something different, or that it will be very late.

[wmarone]

But more importantly, why should it ever be in a usable state?
MeeGo proper is never going to be finished, as it is supposed to serve as a basis from which forks are made for specific purposes.

When there is no difference between Maemo5, Maemo6 (that does not exist) and MeeGo (that never will exist) from an aplication developer point of view
An application developer only needs to think Qt. That's all.

I mean, come on, this is a mess! a terrible mess, an unbelievable mess. No sense of direction, no focus. This simply does not make sense - period.
No, I think you simply don't understand it and are panicking.

Symbian, on the other hand, is finally on the right path. It started with S60.5 and continues slowly but steadily evolving into the future.
Oddly enough, for Symbian application developers only need to think Qt as well. Which is good, because I never heard good things about Symbian development.

[cfh11]

I mean, come on, this is a mess! a terrible mess, an unbelievable mess. No sense of direction, no focus. This simply does not make sense - period.


Facepalm. How much more organized and transparent can it get? Note that this is only one of several useful pages at meego.com.

http://wiki.meego.com/Release_Engineering/Plans/1.1

Also, check out this link from the wiki here at maemo.org that has been up since the beginning of the year IIRC.

http://wiki.maemo.org/What_can_we_realistically_expect#The_MeeGo_project _has_announced_support_for_the_N900.__What_does_it _really_mean_for_my_N900_.3F

[casper27]

To quote Quim Gil
"This would be way clearer if they didn't rebrand it as MeeGo yet, but they wanted to get the marketing behind that brand already. You can think of Harmattan as half MeeGo. The next release after Harmattan will be Nokia's first full MeeGo. "
Pretty clear to me.

[mikecomputing]

To quote Quim Gil
"This would be way clearer if they didn't rebrand it as MeeGo yet, but they wanted to get the marketing behind that brand already. You can think of Harmattan as half MeeGo. The next release after Harmattan will be Nokia's first full MeeGo. "
Pretty clear to me.

Can we get up some kind of a list between the differences between tjhe three "OS:es" so we dont get million threads about this:)

Differences between Maemo5 and Nokias "branded Meego(Harmattan)" (as far as we know atleast):

* QT instead of GTK+ as "desktop UI"
* QT (Console) in top of GLIB as backend daemons etc...
* MeegoTouch UI framework in top of QT core
* Hopefully a QT based FULLY working OviMaps (same as N8 but we cant be sure but hope...)

Similar to Maemo5:

* Still linux kernel
* still debian package manager
* Frameworks: QT Mobility that probadly will be fully supported in upcoming 1.3 of Maemo5 (very strongly atleast)
* QT4.7 (atleast in extras-devel)
* alot of backend daemons still the same. Some rewritted in QT.
* GStreamer multimedia backend?`(not sure about this can someone confirm?)
* Possibility to develop apps in Python
* QML development via QTCreator
* C/C++ support via QTCreator
* And i think, but I am not sure, that MeegoTouch framework will be possible to backport to Maemo5 (I base this on the facts that we already have MeegoTouch widgets gallery demo in extras-devel :)

Differences between core Meego and Nokias branded Meego(Harmattan):

* Some closed apps, drivers and adobe flash etc..
* Hopefully cooler UI than core Meego UI
* Debian package manager instead of RPM

As we can see in above list there is not that much differences between Maemo5 and Meego/Harmattan the difference will be even less for endusers. And in the case of Meego/Harmattan I could understand Nokia in that case it takes time to port from RPM to DEB as an example... Also we will never see a fully open sourced HW based product. There will always bee closed components and without them Meego is ripdead project. (I base this facts on that I have NEVER seen a pfully working product based on fully open sourced drivers etc... and endusers does want Flash/DRM and so on..). BUT hopefully Meego atleast will be more open than android... and with a good development framework like QT and QML Nokia hoppefully soon back in bussiness IF nokia release a Meego product ASAP.

[mannakiosk]

To all those who think all this Maemo/MeeGo/Harmattan stuff is a mess or stupid or whatnot:

At the moment, the N900 has the closest to a regular GNU/Linux distro on a phone, That means that it's the phone that is the most like my desktop and laptop and server computers. I like that.

Android isn't like that. Android has some java-ish layer on top of the linux kernel making it technically a "Linux phone", but not in the broader sense the word Linux is used (meaning the whole OS, GNU/Linux+X+whatnot).

I also like the Free software thing, the social movement of ensuring freedom for computer users around the world.

For these reasons, the N900 is currently the best phone in existence and it is likely that the N9 will be the best for the same reasons when it comes out.

Obviously, if you don't care about the idea of freedom as much, some other phone may be the best from your perspective.

[Dave999]

To quote Quim Gil
"This would be way clearer if they didn't rebrand it as MeeGo yet, but they wanted to get the marketing behind that brand already. You can think of Harmattan as half MeeGo. The next release after Harmattan will be Nokia's first full MeeGo. "
Pretty clear to me.

will half meego be possible to update to full meego or are nokia do the wedontsupportupdate again? we will see. Step 1 of 2 in meego evolution :).

Hope Quim or somebody from nokia comment on this before star selling N9.

looking forward to the first release of half meego :)

[twaelti]

First boot is always slow due to ... tracker indexing the sample media.
Welcome back tracker, arch-enemy of mine and every other user interested in usability instead of over-engineering :D

[Stskeeps]

Welcome back tracker, arch-enemy of mine and every other user interested in usability instead of over-engineering :D

Tracker's my #4 arch-enemy. #1 is Scratchbox. #2 is fennec-qt and #3 is myself.

:P

[bsving]

MeeGo, for netbooks at least, is 100% open source. I have asked a direct question, and I got a direct answer to that question. The MeeGo team will not release any software that is not open source, no blobs allowed anywhere.

This would also mean that the MeeGo team will not release software for the N900 that is not 100% open source? I don't know if this really is the case, but it would be a natural assumption. The MeeGo team releases MeeGo, not Nokia. Therefore, the MeeGo on the N900 will never be in a usable state. To get it in a usable state will be "up to the community", as explained by Nokia.

Nokias software, Harmattan/Maemo6 or whatever it will be called, can of course be released with as many blobs necessary to make it work. But the situation is that Harmattan will not be based on MeeGo, it will be based on Maemo, but with a MeeGo friendly UX. The N9 will run Maemo.

If it is so much easier for Nokia to use Maemo instead of MeeGo on the N9, then why shouldn't it be the same for the N900. The N900 already runs Maemo. What benefits will MeeGo give, that Maemo does not? None, according to Nokia. Why would Nokia release drivers (binary blobs) that also work with the MeeGo kernel? I bet they wont. Why should they? they have Maemo after all.

Who cares anyway, the N900 is old and Nokia use Qt (as if we didn't have Qt since long before Nokia acquired it). In effect Nokias "MeeGo" is only the UX based on Qt. To me the whole MeeGo operation looks more like a maneuver to differentiate the open source activity (MeeGo kernel) and the commercial activity (Maemo kernel) in which future "MeeGo" nokia devices will be based. Or it is a complete mess.

[sjgadsby]

Why would Nokia release drivers (binary blobs) that also work with the MeeGo kernel? I bet they wont.

They already have.

[Stskeeps]

MeeGo, for netbooks at least, is 100% open source. I have asked a direct question, and I got a direct answer to that question. The MeeGo team will not release any software that is not open source, no blobs allowed anywhere.

This would also mean that the MeeGo team will not release software for the N900 that is not 100% open source? I don't know if this really is the case, but it would be a natural assumption. The MeeGo team releases MeeGo, not Nokia. Therefore, the MeeGo on the N900 will never be in a usable state. To get it in a usable state will be "up to the community", as explained by Nokia.


Well, your information is wrong as Netbook actually comes with funny bits like Flash and Chrome..

The general policy in this area is simple: The MeeGo platform must not depend on closed binaries and must be open source. Images (as in the things you install to devices) can pull in closed bits from a non-oss repository. These licenses must be fair (no royalties, etc) and blobs must be redistributable. This means you can for example add codecs or 3d accelerator libraries, etc.

We do this in MeeGo for N900 for the following bits:

TI OMAP3 SGX drivers (3d acceleration)
BME (battery management) + libcal (access to CAL area)
WL1251 (wifi firmware) and bluetooth firmware
(and cos of a technical problem, Xorg driver as well. It's open source.)

And we try to keep our blobs to a minimum. They're a terrible bother to deal with.

[thp]

Video time!

http://www.youtube.com/watch?v=cWtMLs3j09U

(Thanks to Stskeeps for updated graphics drivers, which make the UI faster..)

[Diavoli]

All I can say is WOW!

[bsving]

Well, your information is wrong as Netbook actually comes with funny bits like Flash and Chrome..



Don't know how they got Flash in there as open source, but is has Chromium not Chrome. Chromium is the non-spyware open source version of Chrome if I'm not mistaken.

[Airtux]

yes it's fast ... thanks! i like Meego, all applications works or not?

[fatalsaint]

Don't know how they got Flash in there as open source, but is has Chromium not Chrome. Chromium is the non-spyware open source version of Chrome if I'm not mistaken.

If I'm not mistaken.. there is actually two releases. One with Chromium, One with Chrome that requires you to accept a EULA and stuff before downloading.

[bsving]

If I'm not mistaken.. there is actually two releases. One with Chromium, One with Chrome that requires you to accept a EULA and stuff before downloading.

You are right. This makes it more irritating. Google is OK with an Eula that is so anti open source as it is possible to be, but Broadcom drivers necessary to make wifi work is not. The Broadcom license explicitly allow redistribution, Google explicitly does not. Besides, why include Chrome when there is Chromium?

http://forum.meego.com/showthread.php?t=207&highlight=open+source

http://forum.meego.com/showpost.php?p=5752&postcount=12

I read somewhere else on that forum that the best solution to all wifi-problems is to get an Intel wifi card :)

More mess :D

[NvyUs]

Video time!

http://www.youtube.com/watch?v=cWtMLs3j09U

(Thanks to Stskeeps for updated graphics drivers, which make the UI faster..)

looking very good thanks for the video

[pelago]

Video time!

http://www.youtube.com/watch?v=cWtMLs3j09U

(Thanks to Stskeeps for updated graphics drivers, which make the UI faster..)
That looks much smoother than all the other videos I've seen. There does seem to be a small problem with it not recognising "clicks", e.g. when trying to launch apps by clicking on them it seems to start dragging instead.

[wmarone]

That looks much smoother than all the other videos I've seen. There does seem to be a small problem with it not recognising "clicks", e.g. when trying to launch apps by clicking on them it seems to start dragging instead.

The N900 will do that today on Maemo 5, so it's probably an artifact of the resistive screen and nothing specifically with MeeGo.

[Reffyyyy]

The N900 will do that today on Maemo 5, so it's probably an artifact of the resistive screen and nothing specifically with MeeGo.

There's a problem with MeeGo's touchscreen. There is a bug for it but I don't know the link. It has absolutely nothing to do with the screen.

[wmarone]

There's a problem with MeeGo's touchscreen. There is a bug for it but I don't know the link. It has absolutely nothing to do with the screen.
You sure? I have that sort of thing happen all the time on my N900 today.

I'm curious as to which bug this is.

[Reffyyyy]

http://bugs.meego.com/show_bug.cgi?id=4985

Think that may be it.

I have the problem on MeeGo but don't have it on my Axim X50V or 02 XDA IIS.

In my experience, it's only an issue with MeeGo.

[slender]

The N900 will do that today on Maemo 5, so it's probably an artifact of the resistive screen and nothing specifically with MeeGo.
Maybe your n900 screen & maemo but not mine. Calibrate and if that doesn´t help reflash and try again and if you are able to reproduce issue with factory default device then write bug report.

[m0da]

Video time!

http://www.youtube.com/watch?v=cWtMLs3j09U

(Thanks to Stskeeps for updated graphics drivers, which make the UI faster..)

Anyone see screen tearing in portrait mode?

I DON'T :D

[cfh11]

Maybe your n900 screen & maemo but not mine. Calibrate and if that doesn´t help reflash and try again and if you are able to reproduce issue with factory default device then write bug report.

I am almost positive that the occasional unresponsive screen issues are a symptom of the software, not hardware. It seems that when the CPU/RAM is maxed out the screen can become unresponsive. I have this issue when I load a page in MicroB with alot of content (esp Flash-based) such as engadget.com. Also hildon-desktop seems to suffer when the device is performing i/o intensive activities. Just my $.02

[wmarone]

Maybe your n900 screen & maemo but not mine. Calibrate and if that doesn´t help reflash and try again
I'll watch the video again, and see if it matches what I've seen on mine. It certainly looked familiar to what I've seen across multiple reflashes, but might not be the same.

and if you are able to reproduce issue with factory default device then write bug report.
Which is pointless, really, since even if it was a bug it'd just be marked as WONTFIX and likely won't be seen at all on the next hardware revision with a capacitive screen. ;)

[slender]

I am almost positive that the occasional unresponsive screen issues are a symptom of the software, not hardware. It seems that when the CPU/RAM is maxed out the screen can become unresponsive. I have this issue when I load a page in MicroB with alot of content (esp Flash-based) such as engadget.com. Also hildon-desktop seems to suffer when the device is performing i/o intensive activities. Just my $.02
Sherlock I presume? You are saying that for example if you run apt-get update in background and do something in foreground it is sluggish? I wonder :) I have never ever used OS that behaves fluently under pressure and still multi-tasks properly. Although we are starting to see HW that is capable of doing some heavy duty (4 gigabytes of ram and SSDs in raid and 64-bit OS with core 2 or more processors).

Yes when CPU maxes UI becomes unresponsive. Not good thing and one of things that should be avoided of course but to me it´s have been like that for last 18 years what I have used different computers and OSes. Some linux distributions are quite good but still they normally need pretty good processor, much ram and probably some tweaking (Brainfck kernel etc.) when we are speaking about UI responsiveness.

[slender]

I'll watch the video again, and see if it matches what I've seen on mine. It certainly looked familiar to what I've seen across multiple reflashes, but might not be the same.
Hmm. Just came my mind that if you have scheduled apt-get running in background (in default mode IIRC it´s between 24h intervals) then I believe you but on the other hand is´t just because of low powered cpu, low ram and well linux kernel giving cpu time as it is optimized to give it.

Which is pointless, really, since even if it was a bug it'd just be marked as WONTFIX and likely won't be seen at all on the next hardware revision with a capacitive screen. ;)

I do not believe that this has anything to do with capacitive vs. resistive.

btw. if you use stylus you have to be very careful when clicking stuff because you have to exactly point point you are clicking. When using your finger you can just click on bigger area. I find finger clicking much faster when clicking links while zoomed out..

[me2000]

What is getting released in end of October is a platform. This platform has reference applications and such and fairly good N900 support, but it's probably not enough for most end-users. WTF ! Nokia needs to get off its *ss and start delivering actual end user software ! None of this, "its a platform" BS !

Android and Apple are kicking their butts and Symbian is DEAD. Nobody wants it anymore . (Save the speech for the Symbian crowd, OK)

re: video: Its nice to see something working. What I see there looks pretty nice.

[wmarone]

WTF ! Nokia needs to get off its *ss and start delivering actual end user software ! None of this, "its a platform" BS !
Panic! Anger!

No, MeeGo is a platform. Nokia will use it directly once it's ready to be fully adapted to hardware. You won't see any of that. What you see here is the open source project that owes you nothing.

[vkv.raju]

WTF ! Nokia needs to get off its *ss and start delivering actual end user software ! None of this, "its a platform" BS !

Android and Apple are kicking their butts and Symbian is DEAD. Nobody wants it anymore . (Save the speech for the Symbian crowd, OK)

re: video: Its nice to see something working. What I see there looks pretty nice.

To not frustrate you even further, I would advise you to not wait for an usable MeeGo OS for atleast an year more. Your required eye candy would only be ready then. And w.r.t. features and support, they would be there even sooner.

Btw, why does everyone talk as if the mobile world is going to end any soon. Mobile devices are not going anywhere and they are here to stay. It's better an organisation plan their strategy that is for long-term and not short-term. I clearly see Nokia adapting to this long-term strategy model and which is actually good.

What if they are delayed by an year or so? Lesser than expected profits? But this is the cost anyone has to pay for a long-term strategy. Thats normal.

So, move on. All will be good at the end.

Btw, if you think Android and Apple are kicking others butts now. The time is not far when they would be kicking their own butts! :)

[agdroubi]

What is this version, I didn't get it:
http://repo.meego.com/MeeGo/builds/1.1.80/1.1.80.1.20101008.1/handset/images/meego-handset-armv7l-n900/

[NvyUs]

thats looks like a branch for MeeGo1.2 development i think
MeeGo 1.1 RC 2 starts with 1.0.99

[Diph]

thats looks like a branch for MeeGo1.2 development i think
MeeGo 1.1 RC 2 starts with 1.0.99
Yep.

http://wiki.meego.com/Release_Engineering/Plans/1.2

[HellFlyer]

Guys I wanna try the latest build of MeeGo , i just cant find the url with full and user friendly instructions. Please help me out , I have a 16gb class 10 sd card and I think it should run pretty well

Thanks :)

[mece]

Guys I wanna try the latest build of MeeGo , i just cant find the url with full and user friendly instructions. Please help me out , I have a 16gb class 10 sd card and I think it should run pretty well

Thanks :)

here: http://wiki.meego.com/ARM/N900/Install/MMC.

current latest prebuilt image is here: http://repo.meego.com/MeeGo/builds/1.0.99/1.0.99.1.20101008.1/handset/images/meego-handset-armv7l-n900/

[slewis1972]

anyway to setup dual boot, that includes the options for overclocked n900?

the wiki does not have this info and i wonder if someone has done it as would also like to give it ago.

[agdroubi]

anyone tried the latest version?

[mbo]

anyone tried the latest version?

1.1.80 gave me a black screen at booting. The 1.0.99 build I've used only for 5 minutes. I've tried to type in my wifi pw, but the virtual keyboard was a stopper for me. The 1.1.80 build from last week was more responsive as the latest 1.0.99.

[peynaud]

Can you have a triple boot as follows?

1. Maemo
2. Nitdroid
3. Meego

Thanks

[Gundogan]

Dont think you can multiboot MeeGo atm like you can with nitdroid:

http://wiki.meego.com/ARM/Dual_Boot_Fremantle_and_MeeGo_on_N900

Under construction. This feature is not working in MeeGo due to kexec problems

[ptyxs]

For those who wanna know:

* 1.1 Schedule
* Feature Complete - 25 Aug - DONE.
* Code Freeze -
* 23 Sep - today - Bug cut-off
* 27 Sep - Monday - Critical bug cut-off
* 29 Sep - Branch 1.1. Trunk re-opens on 1.2. [Please note: PRC out 1st week of Oct]
* 28 Sept - 18 Oct - Bug-CCB period
* 18 Oct - Final critical fixes.
* 19 Oct - Final RC.
* Final Release - 27 Oct

Where are we at exactly by now ?

[Stskeeps]

Where are we at exactly by now ?

I believe that's called 'panic phase' ;)

[tebsu]

exactly by now, we are on 11 Oct

another question: will this meego have the same bad thing with the rootfs? or is it solved a different way? also i like to know, if i still need my sd card once the RC is out.

wbr

[HellFlyer]

here: http://wiki.meego.com/ARM/N900/Install/MMC.

current latest prebuilt image is here: http://repo.meego.com/MeeGo/builds/1.0.99/1.0.99.1.20101008.1/handset/images/meego-handset-armv7l-n900/

Thanks for the links but after reading siome stuff I think I will wait a little more , there are some nasty bugs like this one http://bugs.meego.com/show_bug.cgi?id=8063, I dont wanna be disappointed in MeeGo without even trying :D

[longcat]

is there any new video of meego 1.1 (not that one with smooth accelerated ui) ...

[me2000]

Btw, why does everyone talk as if the mobile world is going to end any soon. Mobile devices are not going anywhere and they are here to stay. It's better an organisation plan their strategy that is for long-term and not short-term. I clearly see Nokia adapting to this long-term strategy model and which is actually good. It takes about 10x the effort to chase a market and gain market share after the leader(s) have been established versus to lead the market with the new offering.

[benny1967]

It takes about 10x the effort to chase a market and gain market share after the leader(s) have been established versus to lead the market with the new offering.

That's exactly the advantage Nokia (as the market leader) has.

[di1in]

is it possible to flash this onto the device memory in the hopes of a faster os