I am afraid there is no official offline backup. 
2 Likes
On 4.4.0.72 I still get multiple
(usually two, sometimes 3) copies of SMS. It was introduced on 4.4.0.68 and affects 10-20% of incoming messages.
Similar issues for me.
I created SMS received multiple times
There is also SMS's arriving over and over again, but it looked to be more specific to a network.
1 Like
@flypig Microsoft 365 Account: I should withdraw my complaint about creating a new MS 365 account. Solution was to clear browser cache and cookies complete, all time. After that I could proceed and finish sign in.
6 Likes
I’m glad you got it working @PrhggfCKfuQ4, and thanks for sharing your experience as that could well be useful for others to be aware of.
3 Likes
I’ve just accidentally discovered that now the OS update insolently uninstalls by itself those packages that it considers potentially conflicting and is asking the user to remove (but it wasn’t removing them by itself until now).
During the last OS update to .72 I was shown (as always) a warning that OBEX ContentFilter Off by @olf is conflicting with the update, which I always ignore since it doesn’t conflict with anything. Until this recent update, it just stayed there intact, whereas during the last update to OS .72 it got automatically removed, which I discovered only when trying to transfer something via Bluetooth that the default OBEX filter disallows. A quick look using Install History by @nephros revealed that it got shamelessly uninstalled in the middle of OS update, without notifying me about it…
4 Likes
right now I did the update on the Volla (by CLI) and got also ‘conflict’ warnings. But I hopefully confirmed and in the end everything was fine!
I updated via the GUI, so - as always - it just showed the warning about that package conflicting with the update and telling me to remove it, but without requiring any kind of confirmation. It always complains about that package (and I always just ignore it) but it was never messing with it by itself and that package survived multiple earlier updates. So I was really surprised that this time it just went ahead and uninstalled it by itself. I’ve just discovered it on the 10 III. I’ll check if the same happened on the XA2U.
Just checked, it was not uninstalled when I updated, but others were (like puremaps and systemdatascope).
I used sfos-upgrade but that should not make a difference in theory.
BTW, install-history just parses /var/log/zypp/history, you can look through that file for other uninstall events if necessary.
1 Like
Seems Sailfish si slowly dying? Since there are only 4 build versions during two months?
How is this supposed to make any sense?
One quick question. A friend and I have both upgraded to 4.4.0.72 recently (an XA2 and a 10II respectively). Following the update I have had a “feeling” like the battery of my XA2 has been draining more quickly (i.e. I need to recharge the phone more often). It is not dramatic but noticeable. Now today without prompting him my friend actually mentioned the very same thing about his 10II.
So, here’s that question: Are we imagining things?
1 Like
Today on my 10 III I’ve experienced for the first time ever the infamous “total lack of audio” bug. Reboot fixed it. So it’s still present on .72. Together with the lack of audio, also volume control disappeared (no reaction whatsoever to pressing Volume buttons).
Another bug that I’ve discovered in the last two days is that the Phone app UI in the Call History tab is not always properly refreshed - I mean the list doesn’t get scrolled to the top to reveal the most recent call (the second item is shown as topmost and it takes scrolling the list manually to reveal the first item on the list). This bug is especially annoying in case of a missed call, which we won’t notice without manually scrolling the list to the top to reveal it.
1 Like
Very few packages actually got updated. So either one of those is esting more resources, which you could check via htop for example, or there should be no difference.
SoundCloud login problem for my XA2 4.4.0.72 fresh install:
This is not the first time this issue occurred.
Sorry, I’ve only discovered it now 
Well, to be honest I think that is a fair comment looking at the last updates… My Xperia 10 iii still is on Android since major bugs (e.g. loss of audio) haven’t been fixed yet. Apart from that, there still is one of the two main cameras usable only under Sailfish OS, yet. Since my Xperia 10 i is still running fine, I’m not in a hurry to move to Sailfish OS on my Xperia 10 iii yet. And I also have the feeling, that things are slowing down at the development side at Jolla… just look at their blog, no substantial updates for months. Let’s hope for the best, I don’t want to leave the ship yet!
2 Likes
[Release notes] Vanha Rauma 4.4.0.64 mentions “Sensors of tele and uwide camera lenses are disabled for now” as an Xperia 10 III issue, without further explanation. This still seems to be the case for 4.4.0.72 — is this issue being worked on, are there guesses of when it would be fixed?
I’m kinda disappointed in only having ⅓ of the cameras being operational.
2 Likes
The remaining back cameras can be enabled after Camera2 API has been implemented. It looks like the project can take still some time… Could someone shed some light on that?
4 Likes