Originally Posted by un-named_user (Post 389968)

I've used the phone now for 4 days now and I'l list out some of the problems I encountered

Originally Posted by un-named_user (Post 389968)

I've used the phone now for 4 days now and I'l list out some of the problems I encountered

Originally Posted by DaveP1 (Post 390148)

A groundbreaking device? Doubtful. It's one of several powerful phones running a version of Linux and it wasn't the first to ship....
The N900 may turn out to be a great phone but it will always be one among many with its own strengths AND weaknesses.

Originally Posted by Holyshit (Post 389896)

Yh Android does and it did so long before the N900. The T-Mobile G1 (and e.g. HTC Hero) run FULL Debian. Yes, they also support native X11, so you can run KDE, LXDE, IceWM whatever you want. So what your point again?

Originally Posted by un-named_user (Post 389968)

I don't seem to understand why there seems to be a tinge of fanboy-ism in some of the replies. Megacrazy has raised very valid points, about how a normal consumer will feel about the device. And people who think that a 10 15 minute fiddle with the device is enough to tell all about it aren't entirely correct.

Yes I love the phone, but it feels very beta-ish after you use it extensively. Yes I know, that it is the culture we live in. Sell now debug later.

...


I still love the phone, I do. The promises it holds, the browser's capabilities(not the stability as of yet), the community behind it. and I hope most of the bugs would be resolved as soon as possible in the coming updates.

No point I suppose in discussing the third party apps, and the things the phone can't do, like lack of mms which I really do need sadly cause I still knowingly bought the phone :)


PS: this is my first post on the forum, been following it for a month or two now. But was too lazy to register :D. So a hi to all.

btw could somebody guide me how to get rid of the damn conversation entries without formatting the phone???

and NO I wont sell my phone :D

Originally Posted by Megacrazy (Post 390368)

2. N900 running maemo.org and engadget while music is playing.
http://www.youtube.com/watch?v=FEnRTbRqYwg

Originally Posted by mece (Post 390920)

The scrolling is a non-issue for me, since I've tried it and it works just fine. I'm not as demanding as you I guess.

However, you seem to have some strange css issues in your browser. Both the t.m.o and engadget sites are messed up in the video and they both render properly on the device I've used.

This is what engadget and tmo are supposed to look like on the N900:
http://media.share.ovi.com/m1/s/1440...5583f5391c.jpg
http://media.share.ovi.com/m1/s/1440...770bb3d0f2.jpg

(thanks edgar2 for the images)

Originally Posted by NotTheMessiah (Post 391083)

... So is a phone ever really truely polished? i think not.

Originally Posted by Megacrazy (Post 390564)

Just to satisfy everyone, the phone has been flashed. The behavior is unchanged. It's just what it is.

It wasn't running any apps when the videos were made.

Anyway, I think I've accomplished what I set out to do with this thread and that was to demonstrate that Nokia has added another unpolished product to their collection. I hope they will learn from their mistakes and continue developing the N900 (which I love) and not jump to another product in 3 months that will be just as unpolished. Apple has shown that it is all about software and sticking with something that works and bringing it to an end.

On the other hand, you guys need to stop generating excuses for Nokia such as "it's version 4 of 5, great effort Maemo team, it will be better with updates etc etc...". Keep in mind that the people who developed this product were paid to work and you and I owe them nothing. On the contrary, they owe us 600$ worth of product that they (IMO) did not fully deliver.

I will be around and follow all the developments of cool apps for the N900 (even if the scrolling sucks) and enjoy the phone for some time to come. Do not kid yourselves though, this product falls short of the iPhone and the Droid (which also just came out) bigtime. It is unfair to average users to sweep problems under the carpet. Admitting a problem is the first step to solving it.

Originally Posted by daperl (Post 390690)

I've recently implemented phase 1 of a double-tap zoom hack for the Diablo GTK webkit, so I spent some time staring at how the iPhone OS webkit implements zoom. It's simple. They just do an animated 2D transform while another thread is rerendering the page. They time the animation such that the final pixel copy happens soon after the animation finishes. If you have such a device, you'll notice that your screen is frozen to UI while this is happening. After the zoom is complete, you have to reregister your onFingerDown event. Nothing will happen until you do. A simple parlor trick, nothing more. Nokia could do this, but instead they decided to show you the continuous output of your appSSS. Plural. So, now all you eye candy weenies know.

Originally Posted by jjx (Post 390657)

Well it shows the same scrolling / rendering issue, so at least we can confirm Megacrazy doesn't a have a "slow special" in that department :D

It's very interesting to see that the issue doesn't occur (or only very slightly) when zoomed out and showing a complex web page with tens of thousands of characters and plenty of images. It only occurs when you've zoomed in fully.

That tells me it is definitely a software issue with the rendering algorithm. If it was raw performance, it would be slower when zoomed out, due to increased scene complexity (whether hardware-assisted rendering or not). Since that's Gecko's area (the heart of Mozilla, Firefox, Fennec) I don't think we can blame Nokia for Gecko's behaviour - after all Gecko is an excellent browser engine choice in most respects - but we can annoy the folks at Mozilla with these videos until they improve it :D

I have no comment on the other issues.

Originally Posted by NotTheMessiah (Post 391083)

well it seems to me that perhaps megacrazy has gone at this phone with the mind set of it should do anything everything as fast as my pc. which isnt realistic. The thing has a 600MHz chip in it, not a core 2 duo. Anyone who had a pc back a few years ago when 600MHz was "fast" will be able to tell you that there was an element of being patient while the computer finished having a think about a thing or two.

I'd say remember this is not a pc, laptop, or even a netbook and so if its being laggy when you have 10 things running at once. close some stuff!

Of course the software is always going to have some bugs, no such thing as 100% bug free software. People make software and people make mistakes. This is something we all have to accept.

I think saying the phone "sucks" is not really justified, perhaps unpolished but even then i cant remember the last phone i had that didnt have a little bit of glitchyness to it. So is a phone ever really truely polished? i think not.

Originally Posted by ossipena (Post 391159)

actually it is very logical. when zooming in, all characters except i,I,F,H,l,L need exponentially more details if you dont want characters to look blocky. when zooming out, level of detail needed is decreased.actually it is very logical. when zooming in, all characters except i,I,F,H,l,L need exponentially more details if you dont want characters to look blocky. when zooming out, level of detail needed is decreased.

Originally Posted by borland (Post 391193)

That is absolutely not true. WindowsXP runs perfectly on 366Mhz Celeron. There is no jittering, scrolling is smooth- I use one as a file server (yes I am cheap.)

Originally Posted by hallokitty (Post 391210)

Although you won't be having much fun with flash on that machine ;)

That said, XP uses 2D hardware accelerated rendering paths only for the desktop, and on the n900, surely it can use the 3D hardware to get far smoother scrolling

Originally Posted by kanishou (Post 391118)

But that's exactly what the N900 browser does too. All the fluid animations, scrolling, etc are using a pixmap buffer, while the actual page rendering is happening in the background.

Originally Posted by NotTheMessiah (Post 391295)

Actually one more point on this. the 366 celeron in question is obviously x86. and x86 is a CISC (Complex Instruction Set Computer) whereas the ARM chips are RISC (Reduced Instruction Set Computer). This means that the x86 family has more at is disposal to get a task done, therefore will be quicker. Cant expect the same performance from a RISC architecture as in some cases it will have to execute more instructions to achieve the same computation an x86 chip could do with one instruction meaning more clock cycles get used therefore causing things to run slower.

Originally Posted by daperl (Post 390755)

I start Holiday and parent mode tomorrow, so the earliest I'll probably get back to it is Monday. I used it for a few hours last night and I was very happy with it. It's only about 15 lines of code, mostly inserted JavaScript. There's plenty more to do, of course. For instance, there's no instant visual cue that it's happening, so one solution is what Apple did: an opaque animated overlay that eventually becomes transparent. Anyway, I'm motivated, and maybe the same time that Bundyo sorts out all his Fremantle/Diablo stuff, I'll have something more robust to insert into Tear and take it for a spin.

Originally Posted by etuoyo (Post 391636)

If I drag and drop the whole of My Music folder from my PC on to the device won't it be able to see and play my Playlists?

Originally Posted by borland (Post 391193)

That is absolutely not true. WindowsXP runs perfectly on 366Mhz Celeron. There is no jittering, scrolling is smooth- I use one as a file server (yes I am cheap.)

Originally Posted by chilko (Post 391777)

playlists works fine