ahahaha as if I know anything about coding

I reflashed the N9 to try this new image.

The summary is: great work! Congrats to all involved :-)

There are, nonetheless, a fair amount of polishment to be done. Following is a quick list for reference.
* as discussed before, the system lags often and does not feel responsive
* the graphical interface crashed a few times, mostly while trying to open the keyboard; eventually it worked
* charging works but the battery indicator does not update
* the system started without any ambience (black background)
* after applying one ambience, the app screen still has a black background

I have not yet tried to use the store or update the sw, and currently I do not have a sim card on the phone.

This is hope of a new life for the N9. Well done!

On a scale of 1 - 10, 10 being Android or MeeGo (smooth OS) what would you rate SFOS?

maybe a 4

notice that the kernel is being ported as we speak, and most of the problems may simply vanish as the new kernel matures ;-) or so I hope!

The PowerVR SGX driver used by the N9 has a lot of bugs which require software workarounds. At least Qt4 has such hacks, unfortunately most of them are not available in Qt5 release.

So having a non-buggy release is not possible? Does SFOS use Qt5 and MeeGo Qt4? Is that one of the distinctions?

That seems like the wrong approach. Wouldnt it be better to compile working kernel modules ?
Some have had success in compiling for kernel 2.6.32, perhaps that information can be usefull in replacing the stock-drivers ?
http://listas.gnu.org.ve/pipermail/p...er/000036.html

I'm not sure if the situation is that bad. And I THINK the drivers (also the stock ones) are derived from the SDK (but I could be wrong). However, if it is said that there are PowerVR SGX drivers which are less buggy than the ones in N9, it can be tried. Or, if the bugs are in open source parts, it can be fixed.

These are my observations till now:

1. I have not experienced such crashes in latest Nemo images. However, it might be due to not using as much graphics components/effects as SailfishOS.

2. There could be relatively easy fixes/workarounds for current problems, since they have some special nature: I can successfully run Sailfish voicecall-ui from command line always. But running it from GUI cause a crash almost always if 'voicecall-ui -prestart' is already running; and it tries to tell it to bring up the GUI, and it causes a crash in one of these locations (usually the latter):

A simple workaround for now (for all applications), is seems to be to disable all prestart and invoker single instance running logic with starting applications from scratch and closing them completely when not needed. This will make running apps slower, but you probably won't experience any UI crashes. I've not tried this approach for all apps, but at least it works for voicecall-ui.

As a side note, Qt libraries used in Nemo development images are newer than the ones in SailfishOS image, so I have a little hope that the new version comes with some bugfixes which could prevent such crashes. But it needs to be tested; it's just a hope!

I have the aliendalvik RPM package if anyone wants to give it a try let me know, but am not sure is it working or not

Thanks to everybody who helps with SailfishOS port, I've created new image based on latest updates (including latest filippz kernel).
New SailfishOS (1.1.0.39) images based on previous .ks:

sailfish-hv-1.1.0.39-20141110.img.xz - 174.1 MB
vmlinuz-3.5.3-1.1.1-n950-sailfish - 3.4 MB

The first file is an xz compressed ext4 image (uncompressed image will be around 1.3GB), and the second one is the same kernel used for the image (not required if you use Alt_OS partition). It can be uncompressed in GNU/Linux environments using "xz -d", and in Windows using software like 7zip.

- To boot using N9 easy boot, just copy the kernel and uncompressed image file to your ~/MyDocs/boot partition and modify ubiboot.conf file accordingly.

- To boot using normal method (with Alt_OS partition), you can dd the image to Alt_OS partition, and use resize2fs to enlarge the filesystem to fill the partition (as noted by kibet85, you'll also need to run fsck on the image before resize2fs); which can be done inside Harmattan (this command also decompresses the .xz image):
Or, you can loop mount the image and copy the files using 'cp -a' (or rsync). This is not recommended, only use if you want to preserve some data in your SailfishOS partition.The kernel file is not needed when using Alt_OS partition.
What works:
* Audio (thanks to filippz)
* Call
* SMS
* Battery status (might not work in the first boot)
* Cellular network status (might not work in the first boot)
* WiFi
* Volume Buttons
* Accelerometer (at least, apps respond to orientation changes; e.g. Messaging app)
* Power button! Jolla shutdown splash screen also works.
* USB Ethernet device / Developer mode.

What doesn't work:
* GPS
* Camera
* Android compatibility (not included at all)
* Alarms when locked!

- Note: everything else is not tested (or I don't remember now!)

Known issues:
* Everytime you open or close an application, UI might crash!
* Don't plus USB cable during the first boot, or you might need to re-install!
* Tutorial graphics doesn't appear correctly, but you can successfully pass it!
* Battery status might not work on the first boot. It should work in sugsequent boots.
* DHCP server doesn't work in developer mode. You should assign the IP address of virtual ethernet device manually. You should be able to ssh to device after setting up developer mode settings in Sailfish.

MD5 Checksums:
b255e9c9632f91d9e9c66e9a5f438eb8 sailfish-hv-1.1.0.39-20141110.img.xz
b8ceac73990a514ced796b3dbd0e3b3f vmlinuz-3.5.3-1.1.1-n950-sailfish

SHA256 Checksums:
160454aa9928e4ba4723b115d26f6e238866178b1a0fd27f3e b354309d21a6e0 sailfish-hv-1.1.0.39-20141110.img.xz
15409204722547213a3ecc404da85a0f96b8d6d0e1f428b2d1 c85f8ae6214706 vmlinuz-3.5.3-1.1.1-n950-sailfish