My Xperia 10 II was stuck at the upgrade screen overnight, but this helpes and it now says up-to-date
1 Like
XA2U update went ok.
SF browser clicking links problem seems somewhat better.
I was going to ask why it took three times over to get a useful reply, but then i read the conversation again.
You answer differently each time, so it is still impossible to know what you mean.
We cannot read your mind and infer the background info.
The point here is (only!) that surely the update would best be done in a format that keeps true (=can be trivially updated) at least for a couple of releases.
You clearly are not open to help/advice and just want to argue for the sake of it.
I give up.
2 Likes
Hi @jolla4ever. You wrote: “Problem solved by Settings / Override automatic SailfishOS:Chum repository selection to 4.4.0.64.”
How did you do this exactly? Could you please explain this. Thank you very much in advance.
Best regards, Uwe.
Just ok n chum and go to settings. At the bottom there is a text line. Just type 4.4.0.64 in there and you are done.
Setting WLAN regdomain seems broken (regression 4.4.0.64 → 4.4.0.68, if I remember right), see “WiFi Channel above 11 out of range”.
How long does it usually take for chum to start working again? It’s still not showing any packages for me 
More worryingly it doesn’t even show that I have any packages installed. I.e. even packages that I already installed don’t show up, so I can’t manage my existing state. I can see them when I manually force 4.4.0.64, but how does that interact when there are multiple versions involved? Will I have to manually go through every OS version looking for packages that were installed on that particular version?
Chum should always show packages that are currently installed, regardless of versioning.
Chum should display some kind of notice to the effect of ‘there are no packages available for your OS version. Please try again later [how much later?], or select a different OS version from settings’
2 Likes
It is, all the time. That is what I am repeatedly indicating / trying to get across, nothing more / else.
But you answer differently each time, so it is still impossible to know what you mean.
Even though you asked differently each time, it is still impossible for me to know what you mean, because all the things you are complaining about are not there.
(BTW, please refrain from making generic statements and accusations, just because you do not comprehend something.)
You clearly are not open to help/advice and just want to argue for the sake of it.
What’s with this bad-faith interpretation? (Quoting your words fits extremely well here!)
Apparently you just want to argue for the sake of it.
Side note: I always welcome support, if it is helpful, and I will always thoroughly review any advice given. I even like criticism, if it is posed constructively.
But you are just repeatedly questioning things I never have stated, thus it is logical, that I cannot answer them, but have to reply, “please re-read what I wrote” and “I have never stated anything such”.
Can you please point out which part(s) or words of the updated paragraph you perceive not to be “in a format that keeps true (=can be trivially updated) at least for a couple of releases” or which part(s) or words of the updated paragraph you perceive to indicate the following three statements you made:
Maybe you can also denote, why you repeatedly sound as if this impression you have constitutes a regression WRT “in a format that keeps true (=can be trivially updated) at least for a couple of releases” compared to the older version of this paragraph in the release notes.
1 Like
I also had a dimmed display during the upgrade on one of my XA2s. On the other one, the display was bright during the upgrade.
Mea culpa!
I had read this:
You will probably need to uninstall your existing Storeman and then install it using the new “Storeman Installer” app.
as
You will probably need to uninstall your existing Storeman and then install it using the new “Storeman Installer” app after the completed upgrade.
Since that has been basically how it has been turning out several times.
That would have introduced a difference in the instruction and a sync-point with assuring Storeman compatibility with the new wording.
But in fact it only keeps it… so there is no difference - and evidently it works.
1 Like
Updated my Xperia !0 II with normal GUI method, after reboot and install bar at ca 100%& it tuck for hour or two. I tried to power it down by normal methods, but it did not accept. Suddenly it rebooted with additional power cycle and then booted normally to the working GUI. It shows new version 4.4.0.68.
It looks fine. No other issues found so far.
As explained lengthily in at various places (by mentaljam and me and again), this is only necessary when updating from Storeman < 0.2.9 to ≥ v0.2.9 and completely unrelated to SailfishOS upgrades. I already understood that this abbreviated statement may be confusing, SailfishOS release notes are the wrong place to denote this and it has become irrelevant many Storeman releases later: Hence I replaced it with “If you use Storeman, please update it to a recent version before upgrading Sailfish OS.”
For regular users (not on the EA or cBeta release channels) usually only, if one does not “update it to a recent version before upgrading Sailfish OS.”, because I try to have a working Storeman release ready, when the EA phase ends (although the fact that Jolla’s EA phases have become extremely short is detrimental to this goal for Storeman and other apps).
IMO the updated paragraph constitutes a big improvement exactly in these two aspects (and a couple of others), as pointed out.
P.S.: I am glad that you were able to ultimately pin down your misinterpretation, because …
- … I believe our argument was confusing others, both users and sailors.
- … it turned out that you stumbled over a sentence somebody else has written and which I tried to eliminate by substituting it with a more relevant and concise statement.
P.P.S.: Thank you for ultimately assuring, that my updated paragraph constitutes a vast improvement and is indeed temporally invariant. Now I hope even more, that @rainemak will update it soon, so it becomes part of these and future release notes.
2 Likes
On my Xperia 10 III the update to 4.4.0.68 itself went smoothly and without any problems.
But after the update I was faced with the ‘IPv4 mobile data connection not possible’ bug again:
After hours of trial and error, the only solution was a full re-flash to Android 62.0.A.3.109 and then back to SFOS 4.4.0.68.
However, i really don’t want to do this procedure with every update.
Does anyone have any idea what could be causing this problem?
3 Likes
@rainemak asked me to update this on his behalf because he’s not able to do it just now. I’ve updated the paragraph using your updated text @olf. Please let me know if it needs adjusting.
1 Like
Thank you very much.
Please let me know if it needs adjusting.
I sure will, which will be increasing “4.4.0” to the next SailfishOS release Storeman has been successfully tested on (for the release notes of that SailfishOS release).
2 Likes
I updated Jolla C and Xperia 10 III these days, but Alac is still not working - the error message “Alac not supported” still appears when trying to play a file with that codec.
Can someone check if the codec works on his/her device?
Edit: Codec works, but there seems to bee a bug in Media Player when trying to play an Alac file. I’ll try a little further and set up a bug report.
hi, my phone is since i entered the the securitycode for the upgrade into a kind of koma. screenbacklight is light, led is white but nothing happens… it is in this state for almost an hour…
any idea how to make it work again?
it is a xperia 10.
very gratefull for any help.
sincerly
toba
++++ edit: powerbutton and volume up solved the problem ++++ thx again
1 Like
The update process warns me about 300+ packages that I should revert to their original state before upgrading. Some of those are:
dbus
connman
aliendalvik-system
busybox
fuse
libhybris
perl
polkit
python
zypper
…
Kind of worriyng. Yesterday I updated from 4.4.0.58 to 4.4.0.64.
I do have chum and storeman installed. Is it safe to start the upgrade?
I don’t think my configuration and installed packages are exotic. If you need more info to get to the solution, I will gladly provide that.
4 Likes
This sort of warning appears sometimes when you are updating. I ignored these warnings all the time and I did not uninstall chum or storeman if nothing like that was recommended in the release notes.
This worked for my since 2017. But your mileage may vary.
4 Likes