aw....this phone looks good but the inner side is nothing...
a 434MHz processor, Xperia is 528Mhz...
still no attractive transition, still SE, samsung & LG
and iphone got an attractive interface....
the only good in this phone is the memory....
MBAH MARIJANS, 01 May 2009Why people always complaining the processor n RAM on this phone?This the first ever upgradeabl... morewho needs an upgrade if we already have a phone with high speed cpu?
nokia shouldn't go for such option like that. if they offer us a high-end class phone, then we should take it with the highest level specs that can be put at its time belong.
a phone is not like a pc, that can be easily upgraded or modified. a phone is more complicated since it has very compact form and has to put many devices in it.
zaheed, 01 May 2009really? can u really upgrade this phone?????? ram and clock speed????The Manual instruction about how to upgrade it will found at nearby NOKIA dealer,but remember it's Sold separately.
HAS NOKIA explained why the choice of this 434mhz cpu and 128 ram?
this phone is sexy in brown, Gpu lack is fine with me, cause i dont play game on my phone, its battery drain fast.
Why people always complaining the processor n RAM on this phone?This the first ever upgradeable phone on this world.We can Overclocked or even change the processor and put more RAM on it.Now i'm asking to SE n Samsung fansboy,Can your phone do that?
fast enough everyone XD
ARM 11 MPCore 434Mhz CPU
i'm waiting for my NAM to come :D
Mickis, 01 May 2009I still wonder if N97 comes with an pen, like 5800 does any one who could answer me that, you ... morethe N97 will have a stylus as well but it's like the Omnia wereTF to put it LOL
but damn and NAM all ready i'm gonna crap my self
i'm so happy 5800 and N97
i think with this cpu specs it is fast enough to operate symbian but want to see how it handles multitasking..if well...then this is for me...
cant wait to see this phone. i wonder how slow or fast the processor will be with all the loaded features?
I still wonder if N97 comes with an pen, like 5800 does any one who could answer me that, you can answer me on my blog www.metrobloggen.se/utmaning just comment me there so i know if it comes with a pen.
Thanx, now im going to bed.
Im pretty sure the same guy posted 3 times about the cpu ??
The MHz of a cpu doesnt always indicate the speed. It is possible to have a lower clocked cpu and perform quicker then that of a high clocked cpu. Take alook at the computers we sell today. Much lower MHz then that of say the pentium 4. But todays computers are brilliantly faster then the old P4s.
This may be true in the new nokia.
This phone seem appealing to business people. If nokia can keep price low at 500 vs 600 euro. sales will easily be 5x or even 10x more. Reason being, at 600, businessman
will buy for themselves only, at 500 they will buy in
bulk for gifts to their executives. Nokia, think about it.
I'd strongly recommend running the hell away from Symbian. It's awful.
Let us gloss over the lousy documentation (in which it's impossible to find anything, and where there are no links between chapters --- so, e.g., you can't follow a superclass chain up through the S60 chapter into the Symbian core chapter). Let us also gloss over the lousy build system (a horrible maze of crappy perl scripts, which, apart from being so hideously slow that our project takes the best part of ten minutes to build even if no source files have changed, doesn't allow you to have two source files in the same project with the same name. Even if they're in different directories). Let us also pass quickly over the debugger, trying not to make eye contact, that's unreliable, will only let you debug one task at a time, and which tends to crash if you do the wrong thing.
No, let's talk about the language.
You program for Symbian in C++. Good, you might think. No. This is C++ with all the good bits taken out and replaced by badly designed bits.
Let's take exceptions. There are no C++ exceptions. What there are instead are Leave codes; a macro-and-longjmp framework that replaces exceptions which allows you to throw an integer value and then catch it further up the call stack. Unfortunately because this is implemented without compiler assistance it doesn't unwind the stack frame, so destructors of locals aren't called! All is not lost, though: there's a complicated and easy-to-get-wrong manual cleanup stack on which you can push stuff that you want the system to free for you in such situations. God help you if you forget to push something, or pop something at the wrong point...
Let's take strings. There's no standard string class, of course. What there are are an even dozen different classes for storing strings in different ways: on the heap, on the stack, constant strings owned by someone else, etc. There are some superclasses that will allow you to pass references to these things around without having to worry about the implementation.
Except... it doesn't actually work. The various different string superclasses are incompatible. You can cast a TDes (mutable abstract string) to a TDesC (immutable abstract string). You can't cast a TPtr (mutable pointer to mutable string data) to a TPtrC (mutable pointer to immutable string data). Some of their system functions require you to pass in a reference to a concrete string type, so god help you if want to use a different implementation. You can't use certain implementations in certain contexts. The result is that for some operations you have to allocate a fixed-size buffer on the stack, call a system function to populate it, then copy the buffer into another buffer on the heap, because the buffer-on-heap object is immutable! Despite being resizeable and assignable!
Things get even worse when you want to store multiple strings. There's a labyrinthine maze of string array classes: arrays of fixed sized strings, arrays of descriptors, arrays of pointers to strings, arrays of pointer strings (which are different)... add this to Symbian's bizarre convention where a data storage class allocates memory in its constructor but does not free it in its destructor (which means the user must manually Close() method on all member variables) and simply figuring out who's responsible for freeing a particular object becomes non-trivial. I once spent three days trying to find out how to store an array of strings without leaking them. I kid you not.
(To be fair, they have been trying to fix this with OpenC++, a new programming environment based on, like, standards. It doesn't actually work. The interface to Symbian C++ code is patchy and poorly specced which means it's only really useful for running chunks of third-party code in a sandbox --- you still need to write your actual application in Symbian C++.)
i dont agree that its gonna be slow see specs of n95 8gb and n82 they are same but still n82 is slower can anybody tell me why????so please dont denounce n97 performance even before it is released n97 is probably going to be a killer phone and i bet a proper nokia symbian user cant get place in other ui's as this is the best Os in mobiles,it doesnt matter if its not eye catching like iphone which is only an eyecandy and fun to use but with no such capabilities.n97 is really going to rock the mobile industry and se cant even think to compete with nokia,,,match like with like xperia is nothing comparing to communicator,,,,and slow and steady wins the race...keep it up
Anonymous, 01 May 2009Where did I say I hate it?
I just didn't find it useful enough for my needs, i.e. using ema... moreAll you say is bad things about nokia like you just did. So the rule applies to you! When were we talking about resale value?
It's obvious you hate nokia.