Sailfish OS for Tablet Shown Off for the First Time on the Jolla Tablet


Last month, Jolla has shown off how Sailfish OS looks on the Jolla Table for the first time. Jolla said that they are working harder than ever to get the Jolla Tablet running Sailfish OS in the best shape.

Jolla said that they optimized it to ensure that the Jolla Tablets will last a full day when our crew carries them through meetings and demos from early morning till late evening. WiFi, Bluetooth and other connectivity things are also good. They also plan to provide the following profiles with the first version of the tablet software: OPP, FTP, HID, DID, A2DP, AVRCP, AVCTP, AVDTP, GAVDP, RFCOMM, and SPP (list subject to change.

You can read the whole article on


Experience Sailfish Os on your Android Phone with Jolla Launcher Now Available!!


The much awaited Jolla Launcher for Android is now available  Alpha Testers who signed up last week.


Jolla Launcher is designed to give Android Device Owners the opportunity to try out the smooth Sailfish OS Experience in a simple and risk free way, providing you the effortless gesture based swipe interface highlights of the essential tools that make Sailfish OS stand out from the competition. This Community Alpha release is targeted mainly for Nexus 4 and Nexus 5 devices. The Jolla Launcher Alpha can also be installed on many other devices running Android 4.3 or later

Read the full news on our new site!!!

Jolla Announces Sailfish OS Update 8 To Come in July


Last month, Jolla announced that they’re not going to release an update next month but it all changes today. Soumya Bijjal, Software Project Manager at Jolla reveals on Sailfish Devel Mailing list the details about the upcoming update.

One of the most exciting feature that Sailfish OS Update 8 will bring is to Display each Android Apps on its own App Window. Right now Android Apps are grouped in a single window and you need to use the Android App Manager to switch between the apps.

Check out the full list below!

Hi all,

We will release another update (update8) in July before we take a break. ETA for the following update is end of August/beginning of September. Here is a quick summary of what we have planned for update8:

•Ability to set synchronization schedule for different accounts separately

•Support filtering file selection by file type and uploading multiple files in Browser
•Ability to define email signature per account

•Ability to define sender name per account

•Save unsent messages as drafts when messages app is pushed to background

•Add shortcuts to webpages in the launcher area

•Stroke entry for writing in Chinese
•Improved HTML email viewer
•Improved tutorial app for beginners
•Display each Android app in its own window in the home screen

•Search word auto-completion in the Store client
•Enhanced layout for Google and generic mail accounts settings

Changes to resource policy implementation in QtMultimedia
With update8,

1. QSoundEffect will behave  nicely with resource manager and doesn't
need user to do the resource  policy integration themselves. Earlier, a
bug in policy enforcement has allowed QSoundEffect to function even
without acquiring resources.

2. QAudioOutput will have internal resource  policy implementation. This
will conflict with possible external resource policy implementation.

3. Resource-enabled objects residing in same binary will share the
resource connection,  thus allowing multiple objects to play along
correctly. Previously multiple resource-enabled objects would conflict
with themselves (a shortcoming of resource manager implementation).

There will be an additional mail outlining the changes in more detail.
Changes to RPM side-loading and packagekit authorization
With update8,

1. “pkcon” will only work as privileged and root users (privileged =
setgid privileged nemo aka “devel-su --privileged”)

2. “sdk-deploy-rpm” will be available in developer mode, and can be
used to install single RPMs (right now, this does not have any
confirmations, but we will add it later, so that the user knows
when packages are installed, and not silently installed in the background)
So if you had e.g. “pkcon install-local -y” kind of commands in your
“deploy from sdk to device” scripts, you have to change that to
“sdk-deploy-rpm”. If you are using the SDK (Qt Creator), it will
continue working as before (the SDK has been updated to make
use of the new command).

3. Third party apps should just open the RPM file with
xdg-open/QDesktopServices::openUrl()/Qt.openUrlExternally(), which will
give the RPM to store-client and it shows a nice GUI for installing the
RPM (only when sideloading is enabled; this also works without developer
mode being enabled, therefore can be used by apps submitted to Harbour too)

4. If for some reason your app really requires access to the full
PackageKit API, you can use the normal polkit
( mechanisms to allow
your app to access PackageKit (this might require installing additional
polkit config files alongside your application - this doesn't work for
Harbour apps, but will work for apps distributed through other means)
So if you had e.g. “pkcon install-local -y” kind of commands in your
“deploy from sdk to device” scripts, you have to change that to
“sdk-deploy-rpm”. If you are using the SDK (Qt Creator), it will
continue working as before (the SDK has been updated to make use of the
new command).

Disclaimer:  This is an intent of the release content  and not a
promise. We will do  our best to keep you informed on the  changes since 
the planning.

Read the full news on our new site!


Nexus 5 Running Sailfish OS Caught in the Wild


Sailfish OS was unofficially ported to the Nexus 5 by Siteshwar Vashish with the help of Martin Brook. Martin also ported the Sailfish OS to the Nexus One. They flashed the Sailfish OS Image that was originally released for the Nexus 4 and Samsung Galaxy S3h


Jolla released the Sailfish OS Images for the Nexus 4. They will also publish a Hardware Adaptation Development Kit (HADK) in the next few weeks, that will allow Android devices supporting CyanogenMod 10.1 to have a Sailfish OS port created.

Read the full news 📰 in our new site…


Early Adopters Of Sailfish OS Can Now Install SailfiSh OS On Their Nexus 4


Are you an early adopter of Sailfish OS? If yes, you might want to check out your email because Jolla finally released Sailfish OS for the Nexus 4.

Early Sailfish OS Adopters are receiving email from Jolla that they can now install Sailfish OS on their Nexus 4. For those who are asking on how they become an Early Adopter, they asked to be an Early Adopter on Sailfish Freenode IRC

According to the email they will also publish the images for the Samsung Galaxy S3 LTE. However, not all features are working as Carsten noted.

Dear early adopter of SailfishOS for Android devices.

 We're kicking off today by publishing the first Early Adopter Release of SailfishOS ( for Nexus 4 (mako) to early adopters. Please make sure to read this whole e-mail through.

 Later we'll be publishing images for Samsung Galaxy S III LTE (i9305) and we'll be delivering updated images as we go along for each device as hardware support improves. This is just the beginning.

 We are also working on the SailfishOS hardware adaptation development kit, which describes how to port SailfishOS to existing CyanogenMod 10.1 devices. Later versions of CM will be supported eventually. We'll publish the HADK in the next few weeks if everything goes well.

 This installation image is for early adopters only, meaning we know that some things are not functional or perhaps even broken -- please see release notes below. We think it's worth sharing already now to get all of you properly included in the early stages of the project.

 We want to build a community around SailfishOS for Android devices that is based on mutual trust and respect for what we are all doing. Hence -- we ask that whenever you do screenshots, videos, forum or blog posts (and we're happy if you do!) or the like, you emphasise that this is an under-development snapshot and not a final product release.

 It is important for Jolla that the correct expectations are set for those who might be users of the final product -- and that they understand what they see is not a released product.

 WARNING: Modifying or replacing your device’s software may void your device’s warranty, lead to data loss, hearing loss, hair loss, financial loss, privacy loss, security breaches, or other damage, and therefore must be done entirely at your own risk. No one affiliated with this project is responsible for your actions but yourself. Good luck.

 NOTE: You will lose your on-device data, so make a proper backup.

 To install this release of SailfishOS on a Nexus 4 device:

 * Install adb and fastboot
 a. Debian/Ubuntu: apt-get install android-tools-adb android-tools-fastboot
 b. Fedora: yum install android-tools
 c. Mac OS X: Install Homebrew from, then: brew install android-platform-tools
 d. Windows: See for instructions

 * Install Android 4.2.2 (JDQ39) to your Nexus 4
 a. Instructions here:
 b. Download links can be found here:

 * Download CyanogenMod 10.1.3 for your Nexus 4
 a. The file you want to download is
 b. Download links can be found here:

 * Download the SailfishOS for Android image for "mako"
 a. The file you want to download is

 * Install CyanogenMod 10.1.3 on your Nexus 4
 a. Follow the instructions at:

 * After flashing the "" file, flash the SailfishOS .zip file in the same way ("on top of it")
 * Reboot bootloader, SailfishOS should boot and be visible

 We can recommend reading through -- some parts may not apply to Nexus 4

 If you want to go back to normal CyanogenMod:
 a. Boot into recovery mode
 b. Choose "Wipe data / factory reset"
 c. Flash
 d. (to go back to SailfishOS, flash the SailfishOS .zip on top of it)

 To SSH into your device via USB (Linux)
 1. Enable remote connection in Settings->System->Developer mode
 2. Set your USB interface on host machine to IP
 3. ssh nemo@
 4. Use the password from developer mode to log in
 5. Use the 'devel-su' command with the same password in order to gain root
 6. To SSH over WLAN, use IP listed in developer mode under "WLAN IP address"

Release notes and Known issues for Early Adopter Release 1 for mako/Nexus 4:
 * We have a subtle watermark underneath the UI at all times stating
“SailfishOS development software” “This is not production quality”.
Developer mode is activated at all times.
 * Modem and related functionality works, 3G data, SMS but no call audio
 (comes in next release). There has been no throughout testing of telephony
 related functionality (roaming, airplane mode, data counters,
 etc) and any use of this functionality is at your own risk.
 * Sensors, Device clock/alarms, Reset device, Bluetooth, USB control + MTP,
 Bluetooth, WLAN hotspot, Camera (photography, video recording), and video
 playback is not supported in this release.
 * Jolla account / Store is removed from the image due to problems with
 registering with Jolla infrastructure.
 * The image SW is not currently upgradeable, nor is any typically licensed
 multimedia codecs (MP3, etc), HERE maps, Android application compatibility
 layer, or word prediction for virtual keyboard preinstalled.
 * After returning from suspend, UI may be slow for a moment. It is not
 possible to double-tap to wake up the device. Power button may fail to wake
 device at times, check if you are covering the proximity sensor.
 Powering off device puts it into a state of deep slumber; possible to get
 out of by holding power button and volume down key with a bit of
 * Fingerterm applications may fail to launch during first attempts.
 * FPS drop while scrolling in homescreen due to non-batching when rendering
 of application icon grid
 * Icons/graphics appear unproportionally small in browser toolbar, time
 select widget, and Settings favourite icons
 * Multiboot / multirom is not supported currently
We will all meet in #sailfishos on and please use us (thp, alterego, Stskeeps, lbt, sledges) to work together, report any bugs, graphical glitches or missing functionality that you find, which are not included in the release notes above. You can also find the hardware adaptation source code at .

 You are also welcome to participate in threads at about Nexus 4 and SailfishOS as well as for more general SailfishOS topics at

 Best regards,
 Carsten Munk (Stskeeps) on behalf of the SailfishOS for Android devices team
 Chief Research Engineer @ Jolla

Read the full article here –

Watch: Sailfish OS Running on Samsung Galaxy S3


Last month,Jolla announced that they are going to release a Sailfish OS Rom for Android Devices. At MWC 2014, Jolla displayed a couple of Android Devices where they successfully ported Sailfish OS like the Nexus 4, Nexus 7, Samsung Galaxy S3 and Xiaomi.

Thomas Perl, uploaded a video about their progress on Sailfish OS for Android

Are you excited to port Sailfish OS on your Android Phone? Tell us in the comments below!

Read the full article on our new site.

Sailfish OS Update Timeline + Update 5 Will Sail To Your Jolla Soon


After releasing Sailfish OS 1.0 yesterday Jolla’s COO Marc Dillon confirmed on Twitter that they are about to finish the Sailfish OS Update 5

Ohijarvi or Update 4 is the biggest among the four updates, Ohijarvi is a software update for Jolla Phone that brings a host of new features. Things like new camera options, internet sharing,improved keyboard, extended landscape support, enhancements to the Jolla store, new general settings, and many more

Dillon also confirmed that MMS is included in the next update, the only thing that is missing is LTE support. Although there’s an app for that, it is better to have it on settings.

Are you excited about the next update? Tell us in the comments below!

Thanks for the tip Ru!

Read the full article on our new site