Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

No, it was pretty clear from the start. MeeGo for N900 won't be supported by Nokia (pretty clearly stated, ie, no Nokia Care calls). Work on a MeeGo(.com) hardware adaptation for N900 was started.

I'll give you that there has been a lot of personality split between if MeeGo is end user (netbook) or a platform. In practice however, isn't Android a platform and what you actually use, is HTC Android (with google apps, which isn't part of Android)? Similar model with MeeGo.

It's called Maemo ;)

Seriously though: Only way to not resort to 'dual booting' is by it being preinstalled on your phone or you getting in touch with flasher somehow.

I can make and receive calls on MeeGo/N900. That it comes out the speakers instead of ear piece is because the audio policy daemon simply isn't a 1.1 feature. So it goes.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

Right. N900 not supported either.

Note to Nokia: quit stringing people along with moving deadlines, vague product definitions and propagating false hopes. You aren't fooling anyone. You are only hurting yourself.

I'm sure it is. Only HTC doesn't say its a platform when a software deadline rolls around. They ship software that works on their phone.

In that case, I'll be throwing my N900 in the garbage and buying an Android phone like all the rest of the market has. Silly me for thinking something of quality was going to come from this Nokia + Intel effort.

Silly me, but I thought that is the sort of thing the N900 hardware adaption team, with Nokia's blessing, would broach.

You know what is really funny here is Nokia's attitude toward the N900 user base. Instead of looking at it as a huge, free testing force, they want to wash their hands of it. Have you noticed how Redhat uses Fedora ? That should be your model, not washing your hands of it. Guess what the quality of Meego 1.6 on your next device is going to be if you don't get it properly tested ????

I guess the handset "platform" doesn't need that "feature". :rollseyes:

This whole situation stinks and as long as things continue as they are, I don't see any change happening for the foreseeable future.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

.. uhm, that's exactly how the model is like - build a product on top of the platform.

It does need that feature, hence why it's planned for 1.2.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

well, their smartphone userbase doesn't probably even utilise couple percent of the capabilities. calls +smses plus camera and that is it. It is hard to say if smartphone features will break to amongst Joe Averages.


what do you mean when you talk about embedding something to the os?

and mobile devices are compromises, so there must be flaws. always.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

from the time i got a maemo device.......i learned how to hack.....hack.....screw the device.......bring it back to usable state.....and hack again.....i believe making the device on your own design and function by tweaking the system is what maemo stands for.....


and yes!!! meego will be like that!

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

So not even the "platform" is complete.

So, Meego 1.2, to be released in April, 2011, will be installable by a common user and runnable without dual booting, on an N900 and suitable for everyday usage by a normal user ?

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

I love this:
=============================================
tablets-dev.nokia.com Software Authentication
In order to download the software, you will need to provide your device's 15-digit IMEI number and accept the end-user software agreement. If you agree, you have 1 hours of time to download the software after which the acceptance must be renewed.
The IMEI number is printed on the device's packaging and on the label underneath the device's battery, and displayed in the Settings application (field IMEI in Settings > General > About Product). To find the identification number printed on your device, do the following:
Switch the device off.
Disconnect the charger from the device.
Open the battery cover and remove the battery.
The identification number is printed on the label underneath the battery. The IMEI number is directly below the 2D barcode and the "MADE IN ..." text. It consist of 15 characters which is separated by / (slash) characters. Only the numbers need to be entered in the field below.
=============================================

Seems pretty open to me !

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

Will you pay attention and stop being an ***? I understand you're looking for a target to rage at, but pretty much everything you've attacked the MeeGo project for is either baseless, irrelevant, or just reveals that you are simply reacting without investigating.

Installable by a common user, no. For that it would need to be supported by Nokia and they have said they would not. It is intended to be a complete reference implementation of MeeGo against actual ARM hardware. Without dual booting? Probably. Every day usage? Likely as well. Complete end-user experience? Unknown.

It will be functional, it will be usable. If someone wanted to they could apply the tweaks, software, and improvement to turn it into a real end-user OS instead of a reference target.

Stop bashing people and their efforts because you can't be bothered to understand what's going on.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

The 1.1 platform isn't complete for basing a proper handset product on. We can all see that.

What is hoped, at least for me, is that MeeGo(.com!!) 1.2 is a solid enough platform to take and build a proper handset product of.

I don't want to go into promises of what MeeGo.com 1.2 is like, you can go see that during development and what is already in the bugs.meego.com featurezilla.

What is on -my- (for the N900 port) table of what I hope to see for N900 in accomplishments for 1.2, relevant to this topic, so far, on an entirely technical manner:

OMAP3 GLES implementation must provide hardware vsync
eMMC as installation target for MeeGo N900
uImage target support in kernel-n900
ext2 or FAT partition in N900 image for uImage placement
Open BME IPC implementation and contextkit plugin
OMAP3 PM and DVFS
OMAP3 DSP support and base image
OMAP3 DSP accelerated Ogg Theora and Ogg Vorbis
ARMv7 hard floating point port of MeeGo
OMAP3 DSP accelerated JPEG encode/decode
Ability to include OMAP3 DSP h264, m4v, mpeg4, aac, vpp codecs into filesystem
NEON optimized Vorbis and FLAC
NEON optimized Qt, detectable on runtime
WL1251 calibration and set-up of MAC address from CAL
Bigger image size for N900 images (4gb)
Release engineering: easy install of MeeGo PR1.3 u-boot for dual-boot purposes

What I -hope- for MeeGo 1.2 is that we'll have a feature complete (please note that when people say 'feature complete', it means that these were the features indicated for this specific release, you can't say that an application is 'perfect' cos there'll always be features that aren't there and may arrive in the future) handset UX with reference applications.

My hope is that someone takes that MeeGo 1.2 + hardware adaptation, mixes it up with usual nice things like MP3 codecs and other things, publishes it (as they legally can) a user-suitable
installation with community apps.

Re: IMO, MeeGo will be a tragedy on smartphone market like Maemo!
 

http://repo.meego.com/MeeGo/builds/1...t-armv7l-n900/

Last I checked, going there wasn't necessary anymore. Stop being a tool.