Hi @vige , when the SDK targets matching 4.6 will be available? I would like to release app updates compiled with C++20, but there is just Early Access variant of 4.6.0.11 build target, that should no be used for public releases on Harbour…
4 Likes
Usually it does not matter which point release of a release x.y.z one builds against: On API- and ABI-level they are identical.
E.g. even if a library is fixed (rarely), it is just another patch-level or at most a different point release of that library, which is API-compatible to other point releases of lib-x.y.z.
It would be better to ask that kind of questions from @rainemak. Even better would be asking in Community meeting on 22nd Aug 2024.
I’d say that the EA target can be used just fine for Harbour releases.
2 Likes
I have seen this behavior often, this is so since years.
1 Like
Another problem in this context is that when you switch folders and from mail to list view, synchronization starts immediately, even if you have set the “Synchronization rhythm” to “Off” in the account.
That’s “by design”. It was decided some years ago that when viewing a folder, it should be at the same state than the server one, to avoid confusion. @pvuorela, you may remember our discussion on the matter at that time.
The bad thing is that E-Mail often doesn’t finish synchronizing.
Yes, I’ve seen this behaviour also, and it’s not “by design” ; -) I can’t reproduce it when I want to debug it properly though. But I didn’t give up and I’ll try to fix it one day.
6 Likes
@dcaliste
Thanks for your feedback. Have there been any changes to the code recently to prevent timeouts during synchronization? Because they haven’t occurred since 4.6.0.1…
Does restoring a backup from the memory card still work for you?
For me, the progress bar always stops at “Restoring accounts”.
There is no error message in the LOG. It is a backup of an XperiaX that is to be imported onto an XA2.
This has already been done successfully in the past. I have created the symlink for defaultuser vs. nemo.
I noticed that a backup from June was 1.6GB and one from today is 2.2GB.
But the one from June cannot currently be restored either.
Hello I’m running Sailfish OS version 4.5.0.24 (Struven ketju) on a Xperia 10 II (xqau51 / xqau51). I tried to update to version Sauna 4.6.0.13 yesterday. These are the steps I followed:
1.- Even tough Sauna version 4.6.0.15 is already available the GUI only offered me to update to version 4.6.0.13.
2.- While downloading the update (~1 GB) the message “Uninstall the following before proceeding with the Sailfish OS update” was displayed along with a unusually long list of packages.
3.- In the meantime I uninstalled a couple of the applications that were installed using Chum GUI but I couldn’t uninstall opt kf5 kfbase and opt kf5 kfbase common, so I did so using zypper.
4.- The download was completed.
5.- I ran the ‘ssu status’ command and got this result: Release: 4.6.0.13
6.- Using the command ‘devel-su ssu re 4.5.0.24’ I changed the release back to 4.5.0.24.
7.- I deleted the update using the following commands:
cd $HOME
devel-su
pkill store-client
rm -r /home/.pk-zypp-dist-upgrade-cache/*
rm -r ./.cache/sailfish-osupdateservice/os-info
8.- I restarted the phone, checked for OS updates and GUI offered me to update to version 4.6.0.13 again.
9.- I downloaded the update one more time. This time the message “Uninstall the following before proceeding with the Sailfish OS update” didn’t appear.
10.- Once the download was completed and I selected ‘Install’.
11.- The device restarted then I typed the security code and a horizontal progress bar briefly appeared followed by the message ‘Unable to update Sailfish OS at this point’.
12.- I restarted the device and checked for OS updates. Now a 1 MB update to Sauna 4.6.0.13 is offered. The device appears to be working as usual.
Any suggestions are welcome. Thank you so much!
Try using the sfos-upgrade (openrepos) script. It always helped me in similar cases.
Try installing that first: This seems to be the easiest route by far.
You cannot proceed from 4.5.0.24 to 4.6 because there is a later 4.5 release, namely 4.5.0.25 which is a Stop Release. You must first upgrade to 4.5.0.25 and only then to 4.6.0.15.
If everything is right on the phone, the GUI should guide you through the update chain.
What is the difference between 4.5.0.24 and 4.5.0.25?
Why don’t you just check the changelog/release notes, or search?
https://forum.sailfishos.org/uploads/short-url/ctwwepKOiBJhQvBwRXOAIXNawyU.txt
2 Likes
I have accepted the new EULA via computer in the Jolla account and after this my phones never asked for confirming the new EULA any more.
Today I purchased Xperia 10v, and installed the 4.6.0.15 release, but now getting some issues with it. would it possible to obtain the image for this release (4.6.0.13) here?
It is the End User Licence Agreement (EULA). Read about it here, please:
OS release 4.6.0.13 does not contain any image for Xperia 10 V.
What kind of issues did you see with 4.6.0.15, in addition to those listed here: [Release notes] Sauna 4.6.0.15?
1 Like
sorry for the confusion, but I meant by Issues, is that the Camera and Android are both disabled.
There are known issues, why would you report those? You’re using a trial version for the new Xperias … just wait till those things work in the next release, but be prepared that it may take some time …
3 Likes
It’s currently just a free trial version without the android support, which is exclusive to the paid version, and that’s waiting on Sony to release working AOSP binaries as the ones out now (last release was last August) have bugs like the camera not working.
2 Likes