uvatbc | # 41 | 2011-10-21, 23:01 | Report

Yeah, stupid snotty.... hey! I resemble that remark!

I think the n950 isn't distributed because of the hardware issues with reception. In other words, quite a few people with n950's (me included) have reported wifi/gsm reception issues when holding it wrong.
There's also the lack of NFC support, which by itself doesn't sem to be worth canning distribution, but it adds to the fact that the n950 isn't the direction in which Nokia seems to be pushing its hardware.

mikecomputing | # 42 | 2011-10-21, 23:21 | Report

Now people complains about "no NFC support" and problem with Wifi on a prototype device and send bugreports about N950 related issues now that is EPIC FAIL.

Why not start send bugreports about how MrElop is an ashole and N950 is not released to public also to make it even more EPIC EPIC FAIL?

Now seriously, If send bugreports send RELATED bugreports to N9 not about issues about N950 or do people here really expect issues with free devices like N950 will be fixed!? I doubt....

Personally I got enought of those ridicilous discussions about N950 was not released we already now this! GET OVER IT!!!

---

Last edited by mikecomputing; 2011-10-21 at 23:24.

Vaskinn | # 43 | 2011-10-23, 10:08 | Report

If Nokia expects those developers to use the N950 to develop applications for use on the N9 (and other qt devices) the devices needs to work, and Nokia needs to use some resources to keep them working. Now most of those developers are smart enough not to expect Nokia to fix anything without having been told about it.

How would you expect them to report an error then if they don't have access to an N9 or if the error is only present/visible on the N950?

mikhas | # 44 | 2011-10-23, 10:58 | Report

No one is triaging them for us (=developers), and we have enough bug reports in the internal one. You see, this public one has a complete different structure and complete different workflow (this was also the problem with the MeeGo bugtracker, for me), compared to what I mainly use. And I already spend too much time in bugtrackers anyway.

So what *you* want is to find a new Andre who does the copypasta magic from the public bugtracker to the internal one. I know it's the wrong way (why cant the bugs be dealt with in the open, grrr!), but I doubt it'll change.

hawaii | # 45 | 2011-10-23, 13:52 | Report

Looks like my question got buried, so I shall pose it again.

Is it just me, or does haptic feedback on text input not work properly?

All values provide a low vibration. My motor works fine. Didn't have this issue in beta1 but it's never worked right after PR1.0 or 1.1 now.

Anybody else?

ajalkane | # 46 | 2011-10-23, 15:21 | Report

I would guess it's because the vibration is calibrated for N9. As N950 is made of different material it may be non optimal for it. The first firm ware was probably a bit more customized.

I've seen nothing but praise for N9's haptic feedback.

Saturn | # 47 | 2011-10-23, 17:04 | Report

sh*t,I got the same problem. I'm currently away and cannot flash.

did you understand from where it comes?

anla | # 48 | 2011-10-23, 17:49 | Report

I cannot flash either right now.
Here is a list of my installed apps in case of a conflict.
Stopwatch , elements , worldclock , terminal , swipemeeout , mtimer , filmtrailer uk , pelegrine , brainplus , currencyconverter , toshl , easywallpaper , sdk connection , jazz fm , swipemanager , angrybirds , ap mobile , accuweather , camera pro.

Do you have any of these installed ?

Creamy Goodness | # 49 | 2011-10-23, 21:07 | Report

yeah the touch screen vibration doesn't usually work for me either. sometimes it does though. weird. I think the swype keyboard has more feedback, can't imagine why though.

mikhas | # 50 | 2011-10-23, 22:03 | Report

You guessed correctly.