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

https://together.jolla.com/question/662/enable-setting-of-account-specific-synchronization-schedule/

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

https://together.jolla.com/question/11853/email-signature-per-email-account/

•Ability to define sender name per account

https://together.jolla.com/question/565/a-way-to-specify-senders-name-and-e-mail-in-google-and-imap-account/

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

https://together.jolla.com/question/1224/bug-message-draft-is-deleted-when-moving-between-conversations/

•Add shortcuts to webpages in the launcher area

https://together.jolla.com/question/21678/bookmark-as-launcher/

•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

https://together.jolla.com/question/322/android-applications-should-not-be-grouped-in-the-same-window/

•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
(http://www.freedesktop.org/wiki/Software/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).

Regards,
Soumya
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!

htpp://www.thejollablog.com