What do you mean? If you are referring to the full Bluetooth support on android side, Jolla has said that they will publish that package in Jolla store. They have also said that package depends on changes done in 5.1 OS version, so it won’t become available before that is released. Probably takes at least until 5.1 is out from EA release
9 Likes
Thank you for this answer. Hope to see it soon 
1 Like
Do you have DNS issue on 5.1?
[root@RedmiK20 defaultuser]# nslookup www.sailfishos.org
^C
[root@RedmiK20 defaultuser]# nslookup www.sailfishos.org 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
Non-authoritative answer:
Name: www.sailfishos.org
Address: 54.76.0.186
Name: www.sailfishos.org
Address: 52.18.197.122
Name: www.sailfishos.org
Address: 34.251.134.169
[root@RedmiK20 defaultuser]# nslookup www.sailfishos.org 223.5.5.5
Server: 223.5.5.5
Address: 223.5.5.5#53
Non-authoritative answer:
Name: www.sailfishos.org
Address: 52.18.197.122
Name: www.sailfishos.org
Address: 54.76.0.186
Name: www.sailfishos.org
Address: 34.251.134.169
[root@RedmiK20 defaultuser]# ss -tunlp|grep 53
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=1563,fd=16))
udp UNCONN 0 0 0.0.0.0:5355 0.0.0.0:* users:(("systemd-resolve",pid=1563,fd=11))
udp UNCONN 0 0 [::]:5355 [::]:* users:(("systemd-resolve",pid=1563,fd=13))
tcp LISTEN 0 128 0.0.0.0:5355 0.0.0.0:* users:(("systemd-resolve",pid=1563,fd=12))
tcp LISTEN 0 128 [::]:5355 [::]:* users:(("systemd-resolve",pid=1563,fd=14))
[root@RedmiK20 defaultuser]# ss -tunlp|grep 53
udp UNCONN 0 0 127.0.0.53%lo:53 0.0.0.0:* users:(("systemd-resolve",pid=1563,fd=16))
udp UNCONN 0 0 0.0.0.0:5355 0.0.0.0:* users:(("systemd-resolve",pid=1563,fd=11))
udp UNCONN 0 0 [::]:5355 [::]:* users:(("systemd-resolve",pid=1563,fd=13))
tcp LISTEN 0 128 0.0.0.0:5355 0.0.0.0:* users:(("systemd-resolve",pid=1563,fd=12))
tcp LISTEN 0 128 [::]:5355 [::]:* users:(("systemd-resolve",pid=1563,fd=14))
[root@RedmiK20 defaultuser]# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
Active: active (running) since Thu 2026-05-21 08:35:23 CST; 55min ago
Docs: man:systemd-resolved.service(8)
https://www.freedesktop.org/wiki/Software/systemd/resolved
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
Main PID: 1563 (systemd-resolve)
Status: "Processing requests..."
Tasks: 1 (limit: 4915)
Memory: 1.4M
CGroup: /system.slice/systemd-resolved.service
└─1563 /usr/lib/systemd/systemd-resolved
5月 21 09:23:56 RedmiK20 systemd-resolved[1563]: Flushed all caches.
5月 21 09:23:56 RedmiK20 systemd-resolved[1563]: Flushed all caches.
5月 21 09:26:41 RedmiK20 systemd-resolved[1563]: Flushed all caches.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
I fixed my version of rpn calc (one half of Fibonacci) … so that work is in progress…
1 Like
ag-tool trick did not work for me because service ID increases every time when trying to add account which fails. I managed to fix this by adding temporarily this option setConfig("imap4/authentication", 2) to /usr/share/accounts/ui/email.qml
2 Likes
I also keep repeatedly getting a “Account needs to be updated” message with a directly password-authenticated imaps account. Re-entering the password does not help, the message comes up again immediately although the password is certain to be correct.
I had the same issue with google accounts. Elisa Finland accounts survived the upgrade. I removed google accounts and reinstalled them. After that the accounts have been worked properly.
I think I figured this out: the “Server settings” section was now completely blank although previously created account still existed. So, give it the account password, and then immediately (before it has time to try to log in, which will prevent you from going to settings) go to the “Server settings” and fill all the settings fields back with correct values. After that, the account will log in successfully and the “needs updating” status no longer pops up. This took me some time to figure out – deleting and recreating the account will of course have exactly the same end result!
@Keto there’s something wrong with the update process, account data does not get transferred correctly from the previous version of SFOS. Also, some kind of a sanity check about being able to correctly retrieve account settings should to be added, so people don’t get stuck in the “account needs updating” loop.
2 Likes
Interesting issue that came up today: the game FreeShisen, installed originally from F-Droid (archived since start of the year) no longer works right on this updated Sailfish 5.1. You can open the game pull-up menu exactly once, and after that it won’t reopen. Of course this is a bit of an edge case, but I suspect this means something pretty fundamental has changed in the SFOS GUI.
A thing that has changed with SFOS 5.1 seems to be that Android software that has been run once leaves its background processes running, unlike in earlier versions. I was a bit surprised by Slack giving a new messages alert, even though the main app was no longer running and I’ve not given it permission to start up background “services” at bootup. The way they hang around also shows up fairly clearly in power consumption.
I think I noticed that in some 5.0 versions as well. The effect is very obvious to me, and I don’t think it just started in 5.1.
Maybe for me it started ever since I started daily driving my 10V? I’m guessing.
Actually when appsupport starts, all android background tasks start, and continue to run until appsupport is killed. I assume it has always been this way, since that’s what Android does.
It is however very annoying, as I start my calculator, and Signal starts spewing out dozens of alerts and messages.
The ability to stop an applications background task auto-run until the app is started would be an improvement. It should be in apps → setting for android apps.
The separate ability to kill the background when an app closes would be good too. An alternative would be a timeout for appsupport so it shuts down when no android apps are running for xx minutes.
1 Like
I am of the opinion this is a fairly new thing (perhaps since 5.0 as @ThijssjihT suggested?) — I’m sure I would have seen this happening much earlier with software like Slack.
Indeed, having a finer granularity than “completely shut down appsupport” would be quite good, being able to control this for each app would be even better. There are so many pieces of Android software that like to spy on you in the background and also consume battery…
1 Like
This worked for me too, but I now outgoing is failing even though same config used to work.
4 posts were merged into an existing topic: [Release notes] Pispala 5.1.0.11 - Early Access
Actually there is an option for this. Just go to the System settings’ App tab and click on the android app.