djszapi: I'm not blaming anything, I just told you there were talking about aegis in chat about that camera-ui issue, and sent you the link...you should thank me for letting you check that nothing is wrong, not the opposite...

djszapi, yes - I like that the only thing bitching and inhibiting the use of a proprietary ui _seems_ by logs to come out of the ah so precious aegis enforcement protocols _with_ nokia signed libs & drivers </offtopic>

DocScrutinizer: yeah... But at least the N950 community program was phrased in a way that they expect it to be used to develop stuff for the platform. I wouldn't take a Windows Phone under similar conditions.

javispedro: the thing is - it _did not happen_ prior the OTA :) and only real clues point to them orcs (orcexec or whatever the 3 distinct temp-files were) that appear only after the gstreamer fails to patch thru to the signal, so whether the camera works (some of the times) or fails prolly is linked with the packages updated

if you get a notification, rather than what Maemo 5 does (play a beep, or if you're not using libplayback, mutes the song), or what Harmattan does, it lowers the player's music, plays the notification sound, and raises the volume

does nokia plan to actually sell a single of those lumia things? if they're shipping one to all diehard Nokia fans that would buy a Nokia branded phone even if it came with CP/M preinstall, and the die-hard WP fans already got the Nokia "exclusive" stuff on their Samsungs...

for mere flashing of kernel that might not apply though, as the version of "the image" (which seems to be actually a number of distinct files) is not directly locked to kernel version which seems hasn't changed from latest "image" to most recent OTA update 40-4

and the "one way claim" maybe was meant about there's no way back to secure mode from a rootfs messed with in open mode, which makes kinda sense in that you probably need to flash the rootfs as well, and in that moment you're definitely screwed when you updated to PR1.1 OTA and your image is PR1.0 -> "downgrade not allowed"

Sazpaimon_: lemme put it this way: prior to trying to flash an open mode kernel, you should probably try to reflash device to HARM proper. If that works prior to installing a cutome kernel, then it will most likely work to revert from that custom kernel as well later on

and that'S btw exactly the problem with current OTA SSU, there is no compatible fiasco image to unbrick, as you'll see "downgrade not allowed" when you try to flash with that image of yours on a N9 that has been updated to 40-4

"If you received a Nokia E7 back in February when we announced our new smartphone strategy, you’ll automatically receive a Windows Phone device. If you are currently a Nokia Developer Champion or a Nokia Launchpad member, you are already eligible, and you will soon receive an e-mail to explain how to get your new Nokia Windows Phone."

those who can login to launchpad, enjoy this bit of engrish "WINTER SALE NOW ONGOING. *Promo ends until supplies last. Please note we will not be adding new devices for Discounted Device Program service."

I now know that the flashable images are in nokia care, but it's >9000 (5days) queue and I can't do without my work phone that long (and as it's OTA that screwed my phone and not me, I refuse to pay extra for "express" service)

janpod: we saw the links to the correct kernel in /var/lib/fiasco-flasher/staging/ , and I saw gconfd failing post-inst scripts, thus could reason that the update reboot never took place, and didn't know which argument to pass to reboot for updating, a simple -u flag's for update x)

jonni: were you the hasty one that rushed the image out in the open? If so - thanks for that too, now I can feel good about writing test programs and don't need to worry about bricking it permantly anymore :)

too bad I'm really too busy - I'm cooking up a skype-able frontal camera shinding (currently testing with desktop Skype, streaming as a webcam) *disclaimer* and no I'm not releasing sources as everything I code is the property of my co-owned company x)

I'm asking only because my friend bought N9, and I've advised him against activating developer mode until flasher is available since I know at least one instance where the phone entered MALF after activating developer mode.

Also, -- bad UX in the merging contacts UI. --- It should not close merging dialog when pressing "Merge" -- it should rather say OK, -- STAY at the same place in the list, and allow you to choose more contacts to merge.