maemo.org - Talk - The EPIC N9 anticipation thread

maemo.org - Talk (https://talk.maemo.org/index.php)

- Nokia N9 / N950 (https://talk.maemo.org/forumdisplay.php?f=51)

- - The EPIC N9 anticipation thread (https://talk.maemo.org/showthread.php?t=72977)

Re: N9 hits FCC???

Quote:

Originally Posted by aironeous (Post 1006727)

http://www.engadget.com/2010/02/16/l...-meego-phones/

That's an old article, and the device mentioned within it was cancelled not long afterwards.

Quote:

http://news.softpedia.com/news/LG-to...h-197505.shtml

and

http://www.intomobile.com/2011/04/29...ne-next-month/

Neither of those articles has to do with a retail device announcement. LG has only announced that their developers will be presenting to other developers at a developers' conference on the topics of:

MeeGo hardware adaptation to prototype hardware
future contributions to the MeeGo project

That's all quite nifty. LG's support should benefit the MeeGo project, and it bodes well for the chances of there eventually being a retail LG MeeGo device of some sort, but it does not indicate LG is necessarily poised to begin shipping MeeGo devices anytime soon. And even if they do, the devices could well be televisions, not phones.

Re: N9 hits FCC???

Quote:

Originally Posted by wmarone (Post 1004426)

Lots of people care about those, and now that the market has a number available then releasing old hardware just makes you look bad.

With luck, they've reused the chassis but updated the guts. I hope so, OMAP3 will be a joke otherwise.

What has the number of cores got to do with hardware being new or not ? Older hardware does have a number of advantages, like not running so fast, so using less power, so giving better battery life...

Re: N9 hits FCC???

Quote:

Originally Posted by xerxes2 (Post 1006209)

MeeGo is based on Moblin not Maemo. And a couple of other things that differs between Maemo and MeeGo besides package management: Maemo uses Busybox and Sysv initsystem and all of Debian's /etc. MeeGo uses Bash, Coreutils and Upstart initsystem. The next MeeGo will hopefully use Systemd too. And I'm sure there are plenty of other things too but these are the most important ones I can think of right now.

Edit: So to clarify:

Maemo: Busybox, DEB and Sysv
MeeGo: Bash, Coreutils, RPM and Upstart

Finally someone give me SOMETHING that maybe is different ;)

But I am not sure:

Meego using Upstart!? And Maemo6 still sysv? Is this confirmed?

Meego using Upstart I thought this was planned for 1.3? Cause it was not ready for 1.2? I remember there was a discussion on this topic in mailinglist and Intel was not sure Upstart was ready to be included in 1.2?

And about Busybox? are you sure this is the case for Maemo6? I can't see any reason they still using BusyBox. Only reason they used it in Maemo 5 was probadly lack of "internal flashmemory" on rootpartition.

Re: N9 hits FCC???

Quote:

Originally Posted by mikecomputing (Post 1006790)

Meego using Upstart!? And Maemo6 still sysv? Is this confirmed?

No, you've got it backwards, see my previous post.

If it's worth anything MeeGo 1.3 will move from sysvinit to systemd. There is a possibility Harmattan is using systemd, but otherwise it'll be upstart like Maemo 5 (Fremantle) uses.

Re: N9 hits FCC???

Quote:

Originally Posted by tswindell (Post 1006772)

Fremantle yes. Harmattan, is this confirmed?

Quote:

* MeeGo uses evolution for contact database, Harmattan uses tracker.

yes this was because Intel decided to abandon tracker. The plan before Mr Flop decided to use WP7 the plan was still tracker. I guess Intel got a bit affraid cause some of the tracker stuff was done by engineers inside Nokia. (And they didnt release patches in time)

Quote:

* MeeGo uses MeeGo Touch Framework for MeeGo 1.2, Harmattan may still be using the ancestor of called DUI.

* MeeGo uses "meego ux components" for qml based apps, Harmattan uses "Qt Components".

Wrong. DUI is libmeegotouch and libmeegotouch is DEPRECATED. That means there is no UI API for handset so far.

Intel has released Meego-ux-components (And is based on qt-components!) and is planned to be used as Tablets UI.

And as you say Nokia is working on qt-components (used in Harmattan). Qt components was opensourced project but for some stupid reason they decided to work on it closed. But it will be released soon open source again.

Non of them is needed to be "compliance!"

And as an Nokia employe already has said Meeego-UX components is good for tablets and qt-components is good for handsets. Both those UI should be API compatible as much as possible. Up to the comunity to decide oif Nokia Handset UI should be in Meego. Personally I think it should cause its needed for handsets.

Quote:

* MeeGo uses sysvinit for startup, Harmattan and Fremantle use upstart.

Edit: I took upstart as systemd wrong me :-/

AFAIK. systemd was planned for Meego 1.3 not 1.2 but I can remember wrong. But I remember this was discussed in mailinglist by Nokia people also, and they were possitive about systemd and maybe is using it in Harmattan what make it infact forward compliance to 1.3 instead.

Quote:

Hope I've answered some of your questions.

[/QUOTE]

I am sorry it didnt :)

Re: N9 hits FCC???

your a **** you ask for evidence from us but offer non youself to say why its complianmt

Re: N9 hits FCC???

Quote:

Originally Posted by tswindell (Post 1006797)

Thoise damn name. I took uptime as systemd :-/

But hopefully Harmattan is using systemd already. Atleast they are forward compliance in that area then ;)

Re: N9 hits FCC???

I hope this Meego smartphone will be another sam fischer's handheld like N900. And not closed-sourced enough to prevent any community development.
Also I have called N900 with the above alias because I am nearly sure that it can even hack a guided missile or a mainstream server computer(At least it did with the PS3 console). What do you think?

Re: N9 hits FCC???

Quote:

Originally Posted by tswindell (Post 1006772)

@bandora, Harmattan is a natural forward development from Fremantle/Maemo5. There are plenty of differences between Harmatten and MeeGo Core/Handset. Why do you need "proof" of something far more enlightened people are telling you, and what does it actually matter to you.

* MeeGo uses ofono for phone functions, Harmattan and Fremantle use telepathy-ring.
* MeeGo uses evolution for contact database, Harmattan uses tracker.
* MeeGo uses MeeGo Touch Framework for MeeGo 1.2, Harmattan may still be using the ancestor of called DUI.
* MeeGo uses "meego ux components" for qml based apps, Harmattan uses "Qt Components".
* MeeGo uses sysvinit for startup, Harmattan and Fremantle use upstart.

Now, I could continue this list. The differences go into the 10s or 20s. But I can't be bothered to spend time on doing research you can do youself ... If you want to know more, look at maemo and meego system diagrams and you can see.

Despite what Nokia are saying Harmatten is Maemo 6, the similarities with MeeGo are basically only QML, DUI/MTF and the fact they're both GNU/Linux. They're hoping that with this being the main development API and similar enough to be compatible with MeeGo they can get a tentative MeeGo label. But like every one that knows has been saying, it's not MeeGo, it's not got a MeeGo Core base and it doesn't have a MeeGo handset layer.

Hope I've answered some of your questions.

This is great information; however it (to a pessimist) signals how isolated Harmattan will ultimately be in regards to the MeeGo ecosystem/code base.

That's enough of an difference to render some apps a probably one release (like Skype) or worse... vendors will be forced to split their dev teams and Harmattan will only get niche level support, if that.

Good information to know though.

Re: N9 hits FCC???

Quote:

Originally Posted by gerbick (Post 1006832)

I think Nokia somehow is still insisting on developing through it's own legacy and rights.