Originally Posted by smegheadz

having a release date target of Q2 cut short to Q4 is a hell of a task.
on projects i've worked on we had our planning and workload set with a tight deadline. we had it knocked short by 2months due to unforeseen circumstances and because of this it wasn't up to scratch. we had to focus on core tasks and anything that was deemed small risk had to be pushed back in the queue. on the product rollout with the software and hardware did as it was intended but had bugs and features that were planned weren't implemented. but by our original deadline we had it as originally planned. Changing a date on a product release to an earlier one is a massive pain in the hole and given that the original deadlines are nearly always set to be tight it's even worse.

again this may not be the case but it holds as much weight as the other theories and perspectives.

Originally Posted by delmar

qTranslation from an Italian forum:
Emerging Device Nokia is looking for individuals with a proven track record of success. We are currently looking for experienced Architects SW. There will be a key member of the newly formed team which will take the overall management of the Linux device, SW and kernel architecture for our products, demonstrating a capacity to understand and manage complex projects and SW, including their configurability, modularity and interfaces. The scope of work is all in the SW as a whole, as in the optimal development and adaptation to Nokia devices and services. The role is also to ensure optimal system performance and SW, HW and architects together with our suppliers, as well as having excellent communication skills to succeed at international level, multi-company environment with our vendors and partners.

The requirements are:
Degree or equivalent degree on the architecture of the software
5 years of experience on the Linux system kernel and practical experience in Architecture and Engineering of the SW-depth programming skills in C / C Knowledge Qt / QML Excellence in teamwork Deep understanding of core technologies such as Linux kernel, upstart, glibc toolchain Deep understanding on energy management in a mobile device Deep understanding on the management and efficiency of the power and practices of software engineering, as well as the ability to communicate Deep understanding of Linux kernel development experience Deep understanding of file systems Deep understanding on developing Linux USB Deep understanding of positioning technologies including NPE

Originally Posted by marxian

I use them every day, so I like to think that I know what I'm talking about. There is no need for the differentiation when working at such a high level. That's the whole point of it, to abstract away the differences in low-level APIs. Of course the low-level code will be different, but the declarative components can, and should, be the same. The bigger problem is that there are many basic features in Symbian that don't work unless you resort to native Symbian C++ code. You can't even use the hardware volume keys in Qt.

Come back when you've tried developing some Qt applications for Meego-Harmattan, Freemantle and Symbian.

Originally Posted by xerxes2

I still have hope.

Originally Posted by hotnikkelz

Hear me sinner, there is no hope only despair and gnashing of teeth.
I have seen it.

Forget the future, and just buy/use what suits your purposes...for now until something better comes.

Originally Posted by erendorn

Maybe these webcams come with commercial grade drivers, and the front facing camera of the N9 does not?

Originally Posted by Chuck Norris

Can't disable Aegis. Do I need to jailbreak my n9

Still love the phone though

Originally Posted by jalyst

Well that's not entirely true, what about the mirror app that's already up on the store?
Hundreds of posts about no video calling, and yet no mention of Peregrine?
http://wiki.peregrine-communicator.org/display/app/home
http://wiki.peregrine-communicator.o...y/app/download
IIRC video chat's (XMPP/Jingle, not sure about MUJI) coming w/1.1 stable.
Their last estimate about 1-month back was approx. mid-October.
It may not perform as well as Skype, but it's a nice stop-gap until/if Skype comes.

Originally Posted by jalyst

http://forums.whirlpool.net.au/forum...t=1785096&p=33
http://forums.whirlpool.net.au/forum...5096&p=34#r661

Originally Posted by jalyst

But this is still a WIP, and far from a forgone conclusion.

Originally Posted by BigBadGuber!

More s h i t on NOKIA N9.....sad...muy sad

http://blog.gsmarena.com/nokia-n9-fw...res-the-proof/

Originally Posted by Transcend

This beauty arrive today!
http://imageshack.us/photo/my-images/80/nokian9.jpg/

Originally Posted by xalted13

I fear for our future and open-source phones. The way its going now no company will make anything even remotely open to n900 or n9.

Originally Posted by danramos

In context, he was talking about how camera support might have been held back because of quality--whereas I'm making the point that missing camera support COMPLETELY is a far worse issue than the excuse about quality being the factor. The fact that other applications are using the front camera only SOLIDIFIES my stance.

You realize that you're, once again, helping my argument on my behalf instead of debating an opposing point, right? If that's the case, you might as well 'thank' me or just simply pass over without a reply.

Which part is a WIP? The whole thing? Didn't you read the Maemo.org thread about the cat and mouse game with Aegis? Didn't the N9 have long enough to be worked on? Why are Nokia so quick to patch up holes found AEGIS and leave everything else flopping around insecure and unpatched, unfixed? Where is Nokia's priority? Not on your behalf as a customer, it would appear.

Only SOME pentile matrix displays have really ugly issues--I'm not sure that the N9 is or isn't one of them

and their article is effectively the equivalent of shouting, 'AHHA! IT'S PENTILE MATRIX! I KNEW IT! PENTILE MATRIX IS BAD!' and doesn't really go on to explain why THIS particular version is bad--it just assumes it. Can you help explain why this is bad--or maybe do they have a follow-up with better information?

Originally Posted by jalyst

Since when was that news, known for ages...

Yep it's Pentile AMOLED (what Samsung calls Super AMOLED*) + Nokia's CBD tech.
Unfortunately it's not Super AMOLED "Plus"...
So only 8x RG-BG-RG-BG sub-pixels, Vs SAMOLED+'s 12x RGB-RGB-RGB-RGB-RGB-RGB.
So 50% more sub-pixels, as Samsung likes to boast!
But this only matters for some warmer colours, they're sometimes a tiny bit more grainy/pixelated.
And some text, particularly very small text....
But at the pixel level the N9 does have about 15% more density, plus Nokia's CBD brings some improvements.

Worthwhile reading the 1st 6-posts (and links) here:
http://talk.maemo.org/showthread.php?t=74802&page=8

It's also brighter than the SGSII's, one person's anecdotal claims:

Jakimans comparo....
http://shootspeak.com/2011/10/08/scr...ung-galaxy-s2/

One issue is that adjustment of brightness isn't quite as granular as the SGSII.
So one can't get it just a tad brighter w/o reaching the pink tinge issue** at top brightness.
But hopefully that will be rectified with a hack...

It's a shame they couldn't have gone with SAMOLED+, & kept the res. at approx. 854x480.
That would've made the N9 better than many phones out now, except for beast phones on the way.
I hope they upgrade the panel later, but now that they've thrown all their chips in with MS.
I doubt that the N9 will ever get any hw refreshes, even very minor ones...

*the sub-pixel config. is exactly the same, but it may be more than a marketing name
**not confirmed if that's a wide-spread issue yet.