This link was already posted by someone else but from
http://konttoristhoughts.blogspot.co...few-other.html

Here are some of konttori's answers to requests for improvements stated bugs and requests for additional features

Konttori said...

@Newur:
Yes, clock hit area might be the entire area indeed.

@mike7b4:
Browser toolbar in landscape should indeed be at the bottom. We are planning to get it to autohide in 1.2, but no promises (it's not on the top of the to-do list)

Event feed scroll position remembering: It will remember your position if you open a feed item and the swipe from the side and you'll be at the original position. But when you pan in homescreens, the paradigm dictates that we always show the top area of each view. Sorry.

Media player album to show album and not play random track. I could not agree more. I have been whining about that since spring.

Magnifier works in 1.1 much better than in 1.0.


Konttori said...

@GL: You don't have a rotten battery. The applet just has a threshold of saying when the idle consumption is so high that you won't get near optimal standby time, but less. The variance is greatly dependendent how misbehaving the apps & bg services happen to be. N9 is slightly uncontrolled system compared to WP of iphone (for the good and bad).

@Freddo: our input method framework (MALIIT) http://wiki.maliit.org/Main_Page is very flexible input framework and putting T9 there should be easy peazy. Come to think of it, I've even seen it. ANyway, won't come from Nokia, but you could easily get some other developer to do it.

@Keinbing: Folders will come in 1.2 to home screen. And it's not only apps that need it. If you start using bookmarks a bit more, it's really irritating to not to have bookmarks. Guys in Oulu say that the work should be complete for the feature, so it's about 3 weeks to have decent polish on it. It's one of the "big" features of 1.2

Wifi reception was one of the issues where we had to be dancing on the SAR boundaries. Although wifi in general has been improved by leaps and bounds in 1.1. For me at least, the reception is now perfectly good.
13:21
Konttori said...

@Stefan P: We did make swipe to close as default in 1.1. For the exact reasons that everybody agrees. We actually made the feature just in time for the launch event (like few days before it), and while everybody loved it, we weren't sure that do we make it as default or not. So, being rather on the safe side, we put it off by default. Then after longer period of use, we cannot live without it anymore, and all resistance for having it on by default was gone by the end of the summer. In 1.2, the close will also switch to just close the window, so, it should be exactly what you want. We added some visual hint that close is about to happen so that the switcher view wasn't necessary anymore. Originally we rooted user there in swipe-to-close case so that user would see the window closing and hence undestand that the action actually toggled closing. Anyway, by default in 1.1 and more logical and visual in 1.2.


The switches are tappable, at least in 1.1.

We have now two distinct players: music and movie. I think music player is much better than the one in N900, except for missing dlna, and the poor main view album cover UX blooper.


Konttori said...

@vkvraju:
1.1 is all about reliability, performance and polish. 1.2 is all about adding new features. As it turned out, 1.1 already had plenty of features, mostly due to slipped schedule.

@StefanP: Yes, we could think about disabling touch interaction for the side margins.

@Keinbing: I think graphic equalizer would be better served as a standalone app. (show effects on currently being played back music)

@Weirdfisher: Certainly more effort will be put, but no more products. Plan is of course that the qt as a development platform continues

@thkent: upcoming calendar notifications has been discussed a lot. I can't remember why it's not there, but there was some reason for it...
No comment on the flash support.

@PekkaK: There is "universal copy/paste" in 1.2. Of course there is partial copy paste already in 1.0 and 1.1.


Konttori said...

@Viipottaja: There was no conspiracy behind the delay, just **** ups on multiple different things that were all found one at a time. In HW, SW and production. If I compare this with N900 sales start, we knew all the issues n900 would have pretty much a month before we hoped to make a sales release, then on the last days we agreed that what we have done so far isn't good enough, and delayed it by 2 weeks or so. But it was perfectly trackable. On N9 these issues were coming totally from the blue sky on last minute. One at a time. Fluke of bad luck. I hope you understand that I don't want to be more exact about the issues.

jl: numpad I already answered. Voice control was in the cards, but we eventually dropped it. Not coming, sorry.

@drzuck: I hope the issue is solved already. Please create a bug to : www.developer.nokia.com/bugs

That goes to everybody else as well. If you are interested in helping prioritize 1.2 / 1.3 releases, make bugs there now and as soon as possible. Also contact nokia care for the feature requests / complaints and we'll act on them. (google for nokia care for the phone numbers / feedback forms)

Humm... perhaps I should post these answers to my blog as well in a bit more formulated way.

Can anyone with the N9 go to this link and try to install the Java version and see if it works?
http://www.endomondo.com/m/select
Thanks,

does anyone know how to turn off Toll Ways on Nokia Drive?

features and fixes coming. this is great news!

edit: wheres the magnifying glass?

I think that I have parrot mki9100 and it is working great with both N900 and N9.

So I added a bug report for the N9 browser textbox thing, I thought it would be reported allready but I didnt find it when I searched:

http://www.developer.nokia.com/bugs/show_bug.cgi?id=520


Also suggested this for answering calls when the device is locked:

http://www.developer.nokia.com/bugs/show_bug.cgi?id=521

Multiple wireless flakiness

I am very pleased with my n9 as a whole, but I am experiencing some weird stuff both with Bluetooth and Wifi.

I also have an HP Elitebbok PC running Fedora Linux and an Android Thinkpad Tablet.

When I enable a Wifi hotspot on the n9 my PC sees it and can use it without any problems. But the tablet won't see it. I've tried all kinds of settings but it just won't work.

The tablet picks up every other Wifi network it has come across and could access a hotspot from an Android phone.

The n9 has a hard time seeing some bluetooth devices, including the tablet and my old n900. It usually works the other way around, but pairing is flaky.

Has anyone seen similar problems? Found workarounds?

Should I get my phone replaced or wait for the 1.1 update?

@ Slai

Much appreciated, you really dissected the reviews as you promised

and to be honest I totally agree with you on a lot of the points, and as you said how the N900 started and how it's now, I'm not an app freak also, i install what interests me only, and apps with innovative experience (though the risks sometimes) , and through 2 years with N900 i got 5 apps from the so called OVi store, (thanks to the Maemo community). At the same time i got my N900 my wife had N97, lol, she was so jealous of my phone, that she didn't hold hers for more than 6 month

but away from the stories and the chat, I'm going for the N9 ASAP, i trust the the Linux developers in general, as an Open OS community i feel it's my duty to support hard working ppl like you guys, and F. to all the incompetent A.holes who make such shallow review that can miss lead alot of potential customers from trying something good and different .

Cheers mate.

itpastorn, That could be something to do with your tablet not seeing ADHOC networks, not the N9's problem.

My Archos 101 won't find my N900 wifi hotspot because of that reason.

Yes if you are lucky and dont mind color or memory you might find one.