[release notes] Kvarken 4.1.0

So Jolla Maps is no longer available? (10ii)

Seems also I cannot log into Facebook (Facebook states this platform is not supported at the moment). Google login was also tricky as the acceptance button for stuff was rendered very small in the embedded browser.

Most of the basic stuff seems to work. I can’t figure out how to use the fingerprint reader effectively. On Android I would just hold it on the button and the device would unlock almost immediately. With SF I seem to mostly be getting the code unlock and sometimes the fingerprint seems to work. Screen side swipes are a bit finicky.

Sailfish looks gorgeous on the 10ii (my only other reference is a Jolla 1). Much nicer design than Android. I think there could be a greater niche in selling to style conscious forward thinking trend setters.

the same issue here (Xperia 10)

I dug a bit deeper… I did ldd /usr/share/harbour-ytplayer | grep libicu and got this (save a typo or two):

libicui18n.so.68 => /usr/lib/libicui18n.so.68 (0xf54fb000)
libicuuc.so.68 => /usr/lib/libicuuc.so.68 (0xf53ad000)
libicudata.so.68 => /usr/lib/libicudata.so.68 (0xf34e9000)

Are you sure you are running the Openrepos version? (It seems to have outdated harbour-ytplayer, though… Gotta update it soon.) Anyway, let’s continue this discussion over at Openrepos, so this thread stays better in topic :slight_smile:

Not sure if Jolla Maps was ever available to other devices than JollaPhone. I think if you still have your JollaPhone around, you could maybe get the app from there and install it on your other phone(s), but I’m not sure how Xperia 10II reacts to 32bit programs?

Sorry for the noise, seems like I jumped to the old Jolla store version for some reason. I could install 0.6.17 without issue.

1 Like

Same counts for harbour-defender.
As mentioned here

and maybe follow up here

Or even here

Self tested now again with this release on a X and it boots up just fine.

So would you please think about removing this warning as well, please?
Or maybe link to those informations and put a warning that version >=0.4.1 is needed? (or is that not already blocked within some patterns-sailfish package?)

and to avoid confusion, just seen after finishing this post here


Well, you can increase the root volume size quite easily; when using this guide not on a freshly flashed device, check explicitly that there is enough free space for shrinking the “home” LVM volume.

But I never understood why Jolla has not increased the default rootfs size long ago, it is a trivial change and already in their git (but IIRC unmerged) for long.


Looks like the issue with sd cards fixed by this update also. Thanks!

I think it cannot run 32 bit apps.

I didn’t know Jolla Maps was only on the Jolla 1. That’s a bit of a pity as I could not find any native maps application from the store. Jolla Maps was (very) far from perfect, but it did its job better than nothing.

you can find them in open repos


[BUG] Not able to install/upgrade android apps via Aurora store.

I was wrong. It works, but requires reinstall.


For me it worked out of a box, but now no new window is opened after downloading.

It opens a window rather than a new screen. Which has been the standard Android behaviour for years BTW, IIRC.

I’d prefer to stick with official sources (Jolla Store) for apps. To reflect the experience any regular user would get and to keep things stable. Hopefully those are brought to the Jolla Store at some point.

It requires the app creator to add the app to Jolla Store - which is of little interest to them, sadly…

OSM Scout is available in Store, up to date and compiled for aarch64.


I think the last API needed for it to be included was in SFOS in the last review. No idea what the dev will do though.

XA2: thanks for official Location configuration recommendation.

Having Pure Maps open, my Location tray icon keeps flashing, like it can’t get a lock, even though position is already correctly shown on map. Anything I can do to help it here?

First and foremost it requires QtLocation to be allowed, that’s the main reason why there are almost no map-based apps in the store : we don’t want to reinvent the wheel just to bypass this (unbelievable) restriction.