Originally Posted by anthonie

Another thing is my N9 seems to warm up a lot more than it does running Harmattan. Just having the terminal and a browser open, perhaps the store and in half an hour or so the device really starts to warm up. Not to alarming heats but enough to be significant in comparison to Harmattan.

Anyone else experiencing things like this?

Edit: Also, is there a way to get rid of the boot warning (warranty) without flashing the phone through again? I mean, I didn't care at first, but rebooting often makes it quite annoying. However, a clean format/reflash sequence for both Harmattan and Sailfish is not an option.

Originally Posted by Hurrian

1) It's the added CPU overhead of some stuff in Sailfish, and maybe some lacking power management stuff. It's bearable - definitely not as hot as running NITDroid.

2) Nope, only option's to reflash. The NAND area that displays the image is locked (to programs using the CAL library) from writes.

Originally Posted by anthonie

When I try and enter my simlock pin, often I need to pick up the phone first, before I can enter digits. Almost as if the accelerometer triggers the keypads to function or something. But for that, it should happen consistently, but it doesn't. When I type digits, phone laying down, sometimes it takes 3 of 4 keystrokes before the eventhandler picks it up. Sometimes it doesn't react and I need to pick up the phone first. Odd behaviour, it seems.

Originally Posted by anthonie

Bummer. And the warning is only removable by a complete flash (id est, including EMMC)?

Originally Posted by juiceme

That's capacitive touch for you

For some reason the digitizer needs better earthing (through a firm grip on the device) to work on Sailfish than on Harmattan.
I think it is due to some calibration that would be needed on the device to make it more sensitive, and that's missing on MER so the digitizer works on default sensitivity.

Some people experience this behaviour on Harmattan, also, so it is not that uncommon.

Originally Posted by marmistrz

I'm not an expert here (no warranty for this method) but you can take a try to flash a closed mode kernel, remove the warranty warning, and flash open mode & ubiboot back. In worst case you'll end up reflashing, what you were to do.

Originally Posted by anthonie

You mean using the stock kernel image to overwrite the NAND en then quitting the process of flashing? Sounds legit. Question is, how to know when it's safe to press Ctrl-C?