Nemo Mobile distribution installation on a Jolla device

PLEASE NOTE, THE INSTRUCTIONS ARE FOR SEASONED USERS ONLY, DO NOT TRY THE INSTALLATION IF YOU DO NOT KNOW WHAT YOU ARE DOING! 

OFFICIAL STATEMENT FROM JOLLA CARE SAYS:
"Our warranty does not cover issues arising from using unauthorized software on the device. If installing the alternative OS causes problems with the hardware, these are not covered by the warranty even if it happens during the warranty period. The user would likely also lose the benefit of their statutory rights to have errors repaired. In other words, anyone trying this would do it at their own risk, we can’t be responsible for the outcome nor can we publicly encourage people to do this."

ALSO PLEASE DO NOT DISTRIBUTE THE HARDWARE ADAPTATION PACKAGES AS THEY ARE PROPRIETARY AND YOU DO NOT HAVE THE PERMISSION FROM JOLLA TO DO SO. THIS IS WHY I CANNOT PROVIDE YOU WITH THE PACKAGES, ONLY THE MEANS TO EXTRACT THEM FROM A EXISTING DEVICE.

1. Extraction of certain packages from Jollas repositories, with "zypper install -f --download-only" and rsyncing them to a separate directory on the Jolla device:

usb-moded-pc-suite-mode-android
droid-system-sbj
gst-av
jolla-recovery-sbj
gstreamer0.10-colorconv
qt5-qtwayland-wayland_egl
gstreamer0.10-droidcamsrc
gstreamer0.10-droideglsink
nemo-qtmultimedia-plugins-gstvideotexturebackend
gstreamer0.10-omx
gstreamer0.10-ffmpeg
hybris-libsensorfw-qt5
qtscenegraph-adaptation
kernel-adaptation-sbj
libhybris-sbj-libEGL
libhybris-sbj-libGLESv2
qt5-qpa-hwcomposer-plugin-sbj
libhybris-sbj-libwayland-egl
sbj-platform-images
sbj-version
sbj-wlan
libhybris-sbj-libhardware
libhybris-sbj
droid-system-packager
nemo-gstreamer0.10-interfaces

2. Copy over the aforementioned packages to a directory in which the Mer SDK resides and can access.

3. Copy over configuration files from Jolla device:

rsync -R /etc/dconf/db/vendor.d/locks/screen-rotation.txt /etc/dconf/db/vendor.d/screen-rotation.txt /etc/dsme/battery_levels.conf /etc/dsme/temp_hw_battery.conf /etc/dsme/temp_hw_core.conf /etc/mce/60-als-jolla.ini /etc/mce/60-doubletap-jolla.ini /etc/mce/60-mce-display-blank-timeout.conf /etc/mce/60-mce-display-brightness.conf /etc/mce/60-mce-possible-display-dim-timeouts.conf /etc/ofono/ril_subscription.conf /etc/usb-moded/android-usb-values.ini /etc/usb-moded/usb-moded.ini /lib/systemd/system/basic.target.wants/dev-mmcblk0p24.swap /lib/systemd/system/create-swap@.service /lib/systemd/system/dev-mmcblk0p24.swap /lib/udev/rules.d/90-toh.rules /lib/udev/rules.d/999-boston-system.rules /usr/lib/oneshot.d/bdaddr-from-factory-data /usr/lib/oneshot.d/btrfs-autodefrag /usr/lib/oneshot.d/resize-filesystem /usr/lib/qt5/plugins/feedback/qtfeedback-sbj.ini /usr/share/ngfd/plugins.d/ngf-vibra-sbj.ini /usr/share/qt5/keymaps/boston.qmap /usr/share/ssu/board-mappings.d/05-sbj.ini /var/lib/environment/compositor/60-boston-ui.conf /var/lib/environment/nemo/60-multimedia.conf /var/lib/environment/nemo/60-sbj-vibra.conf /var/lib/environment/ofono/noplugin.conf to@dest.mer.machine:adaptation

4. Copy over /sbin/preinit from Jolla device to a separate directory on the Mer SDK host.

5. Create a image using mic2 and Nemo Mobile system packages:
sudo mic cr fs -A armv7hl -o nemo-sbj-armv7hl-devel --pack-to=nemo-sbj-devel.tar.bz2 --record-pkgs=name,url,content,license jolla-sbj-adaptation.ks

The kickstart file is here http://pastebin.com/zZYd0YM7

6. Add the missing configuration files and /sbin/preinit to the created root filesystem package.

7. Copy the root filesystem package to a microSD card. Transfer the microSD card to a Jolla.

8. Reboot jolla to a recovery mode using Volume Down and Power key, use the recovery mode selector to move to a shell.

9. Inside the shell, copy a fresh installation of the sailfish-snapshot script manually to a text editor.

10. Mount the sdcard inside the shell

11. Go to the sdcard directory and issue:
/sdcard # PARTITION=/dev/mmcblk0p28 MOUNTPOINT=/sailfish-snapshot /sailfish-snapshot-script export factory .

12. Back up the current system with sailfish-snapshot:
/sdcard # PARTITION=/dev/mmcblk0p28 MOUNTPOINT=/sailfish-snapshot /sailfish-snapshot-script create prenemo

13. Inject the Nemo Mobile root filesystem package to a new snapshot on the Jolla device, with Jollas default home filesystem:
/sdcard # PARTITION=/dev/mmcblk0p28 MOUNTPOINT=/sailfish-snapshot /sailfish-snapshot-script inject nemo-sbj-devel.tar.bz2 homefs-factory-1.0.4.20.tar.bz2 nemo

14. Make the nemo snapshot the current system:
PARTITION=/dev/mmcblk0p28 MOUNTPOINT=/sailfish-snapshot /sailfish-snapshot-script restore nemo

15. Reboot the Jolla device to activate Nemo Mobile

To get back to SailfishOS:

1. Reboot Jolla back to recovery mode.

2. Enter shell and get sailfish-snapshot to it.

3. PARTITION=/dev/mmcblk0p28 MOUNTPOINT=/sailfish-snapshot /sailfish-snapshot-script restore prenemo

Glacier UI homescreen on Jolla

PLEASE NOTE!
Tampering with custom repositories on Jolla might leave you with a bricked device, please take care to follow instructions and do this only if you really know what you are doing! This requires developer mode to be enabled on your device.
THERE WILL BE BUGS! YOU HAVE BEEN WARNED!
PLEASE NOTE!

First, download a couple of RPM packages, package1 and package2 (for glacier gallery download this package). Then in your device, preferably do this over ssh, do this:

devel-su
ssu ar http://repo.merproject.org/obs/nemo:/devel:/mw/latest_armv7hl/ nemo-devel-mw
ssu er nemo-devel-mw
ssu ur
pkcon refresh
cd /home/nemo/Downloads
pkcon install-local qt5-qtquickcontrols-nemo-5.1.0-nemo1.armv7hl.rpm
ssu dr nemo-devel-mw
ssu ur
pkcon refresh
pkcon install-local lipstick-glacier-home-qt5-0.0.0-1.armv7hl.rpm
# Then do this:
systemctl-user restart lipstick.service 
# After you have done testing it
pkcon remove lipstick-glacier-home-qt5
pkcon install lipstick-jolla-home-qt5
systemctl-user restart lipstick.service

Thats it then, you have successfully tested the Glacier homescreen experience on your Jolla device, good luck testing it :)

Installing SDK version of Sailfish UI on N9

CAUTION: Might break your stuff, back up your nemo installation 
beforehand if you want to be cautious. You have been warned!

!! KNOWN ISSUE !!

Zypper does not always cache the packages, remove lipstick-jolla-home-qt5 with --clean-deps and try again.

Please note, an official guide is coming up from Jolla, which demonstrates this entire process into making an image. This guide will be updated with instructions regarding that.

First things first, you need a working copy of Nemo Mobile running on N9, you can grab one from this link, magnet link. I will not cover the installation of Nemo Mobile for your N9, you can follow this guide to do that.

You also need a working copy of Sailfish SDK running. I will also not cover the installation process here but its quite straightforward to setup. After having a Mer SDK virtual machine instance running, do this to gain ssh access to the virtual machine:

ssh -i ~/SailfishOS/vmshare/ssh/private_keys/engine/mersdk mersdk@localhost -p 2222

In this ssh shell, run:

sb2 -t SailfishOS-armv7hl -m sdk-install -R zypper mr -k -all

Then:

sb2 -t SailfishOS-armv7hl -m sdk-install -R zypper in lipstick-jolla-home-qt5

This generates rpm packages to /parentroot/srv/mer/targets/SailfishOS-armv7hl/var/cache/zypp/packages/jolla/ subdirectories, copy them all over to a separate directory on the host machine as one flat directory, like this:

mkdir ~/sailfishrpms

cd /parentroot/srv/mer/targets/SailfishOS-armv7hl/var/cache/zypp/packages/jolla/

cp ./*/*/*.rpm ~/sailfishrpms/

Copy these over to Nemo Mobile running in N9, using eg. scp. Usually one wants to copy over entire directory like the above sailfishrpms.

Then in the device, over ssh, execute:

cd sailfishrpms

zypper install --force *

This will install all of the generated rpms to the device, although with warnings, afterwards reboot to gain access of the Sailfish, SDK version, homescreen.

 CAUTION: Might break your stuff, back up your nemo installation beforehand if you want to be cautious. You have been warned!

Adding armv7hl target to Sailfish SDK

One day I was talking with David Greaves on IRC about the possibility to add an armv7hl target to Sailfish SDK, namely Qt Creator component, as the SDK is based on Mer Qt Creator but Mer's Qt Creator is a bit outdated as it doesn't support Qt5 as Sailfish SDK does. David said that the fix for adding cross-tools to Mer SDK virtual machine shipped with has not yet been released but I got the manual fix from him, so here goes:

First go to your Mer SDK VM:

ssh -i ~/SailfishOS/vmshare/ssh/private_keys/engine/mersdk -p 2222 mersdk@localhost

sudo -s

Edit your /usr/share/ssu/repos.ini, go to [release] section and add to end:

mer-cross=%(releaseProtocol)://%(releaseDomain)/%(releasePath)/%(release)/mer/%(arch)/cross/

Also one must add mer-cross to: [default-repos]

release=jolla,nemo,mer-core,mer-cross

Exit your editor and then refresh your mer-cross repository with command:

Now a word of warning, this will add an experimental repository to your system!

ssu er mer-cross
ssu ur
zypper ar http://repo.merproject.org/obs/mer-tools:/testing/latest_i486/mer-tools:testing.repo
zypper ref
zypper dup

After this, go to your Qt Creator, select tab SailfishOS.
In that pages tabs, select 'Toolchains' and press install on 'Mer-SB2-armv7hl'.
The toolchain should be installed without intervention from user.

The Sailfish SDK now has arm toolchain installed by default, so you only need to add a target:

The next step is to install a viable target to the SDK. Return to 'Targets' tab and make sure that Mer-SB2-armv7hl is the selected toolchain, then add whatever name you'd like for you target and as the target url add:

https://dl.dropboxusercontent.com/s/5w8uwazmdsaalgn/nemo-wayland-arm.tar.bz2

Target installation should now proceed to download the target image, unpacking it and then updating Qt Creator with the newly created target.

And that's pretty much it, you can now compile Qt5 applications with Sailfish SDK. The build will also work for Sailfish applications but running them won't work as Jolla is still to release the Silica library for armv7hl.

Stay tuned for the knowledge of getting Qt5 apps to run on your N9/50 Nemo Wayland, from within Qt Creator, in the near future!