This thread isn't "was I mis-sold the device" or "was I stupid because I expected something else": it is "will it ever be a polished product". How it's sold and even what people expect is not relevant to that question. So please drop the "you were told it's not a smartphone" distraction. A smartphone is, in any case, a rapidly evolving concept which *includes* mobile computing functionality nowadays. It's reasonable to expect both in one package.

Personally I'm quite happy with the "phone" functionality. Sound quality is excellent, phone controls work quite well, dialing is easy. As a phone, it's one of the best I've used. Contacts are a bit limited and annoying, but that's true on most phones.

It's the "mobile computer" part which is showing lack of polish, imho.

Following is just one example:

Since updating to PR1.2, the device freezes for a few seconds every so often. Occasionally it does it in mid transition, so you can clearly see it's doing something odd or badly implemented. There isn't anything unusual running in the background or taking up RAM as far as I can tell.

Usually it happens in the browser - I touch the screen to scroll a bit or click on a link, and there isn't even a feedback click. After a few seconds it unfreezes, and there's a rapid burst of clicks - all those touches queued up in the interval.

Sometimes the result is what I thought I was touching isn't what it registers. Last time I wrote a long (and imho interesting ;-) post to a forum, my simple wish to touch the bottom-right fullscreen icon resulted, a few seconds later (because it froze), in a delayed click preceded by a screen rotation which caused the browser to register my "fullscreen" as "go back", thereby deleting my half an hour of writing before it was posted. Very annoying, very crap behaviour.

When it didn't freeze (before PR1.2), it was still possible to touch the wrong UI elements if you're lying on your back and it decides to rotate because the angles are borderline (fair enough), because you touch before the (unexpected) rotation and it registers on the UI element in that position after the transition. Result: mis-clicks. But it's much worse since the random freezes.

A "polished" N900 wouldn't have those behaviours, and if such a behaviour slipped in, it would be treated as a bug and fixed *quickly* because that's what polish is all about: attention to detail, caring about those details, getting it just right so it's a pleasure to use.

That's what seems to be missing: That careful attention to details, and caring about them.