hey guys, i got a quesetion i was playing with a n9 running latest meego in a store and pressedtehpwoer button several times (by mistake kinda) and at the end it booted and show system failure due to too many reboots, try reflashing firmware.

mine has already been one round to the repair shop, but in case of replacing it then, they just reflashe it with the new 1.1.... so on top of its problem I now also have to log in several e-mail accounts 10-30 times a day...

rules as gathered by me over time: get permission, show you're a bot, show owner/contact for service (when misbehaves), don't log (and publish) chan without public notice in chan, do not interfere with other bots, do not spam chan with crap

i think we have something more productive to do than finding obscure references in blog posts. it should be possible to find the location of the antichrist by decoding the first letter of each freenode blog post

DANG, I was stupid enough to read a bit more in yesterday's chanlog. Mentioning aegis doesn't change my blood pressure. The BS dj spreads about images downloaded form an official Nokia fileserver via navifirm were NDA'd and thus illegal to use... WOOOAAAHH >:-(

one way *might* be to give the lockscreen app a patched fontset (it uses a very specific one I guess) and change the space, 1 and 2 chars to sth that has a leading icon displaying your state/notification left to the first digit of time

that always-visible mail status thing is really useful, you can just glance at your phone to see if there's anything that needs checking, so even though it might seem an irrelevant thing it actually makes the user experience way better

btw, a friend of mine asked me if it would be possible to make the lock screen clock fade out/in when changing position, instead of the hard no-transition it does now. is that possible or is there some sort of hardware limitation in the low power display mode?

Arkenoi: don't ask me, I always thought thanks to general architecture esp regarding aegis the whole harmattan is unservicable and evventually that issue will bite Nokia's ass when backups are impossible to restore etc

but the idea is you create a QNetworkAccessManager once, and then you load in your url into a QNetworkRequest, where you then set all the post data and headers. you then post the QNeworkRequest via QNetworkAccessManager::post(), which returns a QNetworkReply

QNetworkAccessManager and QNetworkRequest can be reused as much as you want, and QNetworkReply is something you never make yourself, and should delete in the QNetworkReply::finished() signal via QNetworkReply::deleteLater()

ieatlint: whom-it-may-concern? dj already 3 times deserved a kickban and only nobody notices as all the people involved (except him) managed things behind the scenes and always were WAY too forgiving and reluctant to ban him

okay, now I really don't understand how the Ovi QA is testing. I installed my application on "Nokia Remote Device Access", where the devices still run PR 1.0 of the N9 - and everything works fine as it does here! Seems they are really just unable to enter the login data o_O