No the one Im referring to is in android settings.
Check my edit above
My problem turned out to mostly likely be the result of switching networks shortly after the first download attempt. It left the phone in release version of 4.6, while it really was still 4.5.
Setting aside the annoyance of the upgrade process not being atomic, I was able to restore the zypp conf file to the 4.5 version and proceed with smooth upgrade via GUI. (I use XA2 dual-sim, by the way.)
I was worried about the Android App Support, thanks to the other reports, but I was positively surprised by it running well on the first try.
I am also very surprised at how much memory management was improved in the Sauna — to the point of regretting buying a 10 V. I am now able to open and use many heavy applications simultaneously, and still get working camera. I am very happy to see this development! Hopefully this fixes the recently discussed issues some people had with the base phone functionality.
At this point the only pain of Early Access I have is the missing Amazfish release for the new system version, which is actually a good thing — in my experience the XA2 release of Sauna is Platinum.
PS: I did not have an opportunity to test voice and text messaging, but I have strong trust in those aspects. I am pretty sure the reports of such a failure would have been made long time ago.
2 Likes
My Jolla C upgrade went through fine, after removing a few (relevant) of all proposed system packages.
My X10III… well, I don’t dare (for the first time) at this point. 
It’s my daily drive for fuck sake.
1 Like
Was able to update smoothly (Xperia 10 III).
The list above was initially longer, including for example amazfish, but disappeared by removing it and other packages from chum & storeman.
Things I tried:
-
pkcon updateshowed the same list as above with the addition ofkdb-sqlite3-driverandlibKDb3-3which I searched withpkconand they looked alright. (Meaning Jolla originated) - Started to install
zypperin order to find out what would be the parent of those dependencies.- By installing
zypper,pkconinstalled also two packages, names of which I don’t remember anymore
-
zypperdid not work but the “updates” were gone frompkcon update's output, maybe thanks to those two packages
- By installing
- Continued with the installation from GUI and no issues
That’s a good point I didn’t think of. What I was expecting from what I understood I was told before, was that the AppSupport part needed work but Sailfish OS 4.6 itself would be available for 10 IV and 10 V upon release. But apparently the situation changed so that yesterday we were told 10 IV and 10 V will be supported only after everything including AppSupport is a go.
Or may be we were at that time reading too much into this haphazard mention of 10 IV/10 V being supported but AppSupport being n/a:
We were at that time kind of demanding in our having to know now whether 10 IV/10 V will be supported.
[quote=“demislition, post:118, topic:17815”]
But apparently the situation changed so that yesterday we were told 10 IV and 10 V will be supported only after everything including AppSupport is a go.[/quote]
On the presentation they say that the OS release for the 10 IV / V will come within a month or two from now. By that they mean the “Free Trial” version. But the paid components (i.e. AppSupport and Exchange) will come only in August. Whereas on the currently supported models (with the old “perpetual” licensing) they already came out along with the OS update, and on the 10 III they seem to work fine with 5G.
So I can’t see why for the new phones (with the new subscription licensing) they would need so much more time for making the commercial stuff available if on the old phones it already works, other than preparing those paid components (incl. AppSupport) for that new licensing, i.e. implementing mechanisms to enable / disable their functionality when you start / stop paying €5 a month (and soon possibly more, because you know, inflation blah blah).
1 Like
It’s still there but disabled by default, more there SFOS 4.6 / Foreca: How to enable the Weather infos is in the the Events view - #5 by pvuorela
Can get it back by adjusting dconf key, e.g. “dconf write /desktop/lipstick-jolla-home/force_weather_loading true”, and events view settings switch by installing extra package lipstick-jolla-home-qt5-weather-widget-settings.
10 Likes
GMaps. Problem was related probably to global spoof signature enforcing being enabled.
For some reason, it seems to have gone lost in the upgrade.
Surely, the Microtube is one of the most desirable apps in SailfishOS. So, I will not update my other Xperia’s to 4.6 until this and the weather eventview is fixed.
2 Likes
Concerning the free trial for Xperias iv and v, I was listening / getting the feeling that Sami or Antti told something:" Of course it will come asap." Whereas paid version will take 1 to 2 months (August). However, I am not sure exactly anymore what they said actually… Too much information or too shortly mentioned yesterday. Personally I do not believe, too, that Free version takes so long time to be released!
By the way the instructions of installation are said in the introduction to be added soon. Soon litterally means:
From very short time delay to one week technically. But, I do not believe it until something really happens!
Also problems exist a lot when people are using English as not their mother tongue (i.e. broken English). Understandable!
I ended up in this situation as well, as bizarre as it is that Jolla will allow Sailfish to happily list all the installed apps as something to be removed, and not be able to predict a “Can not upgrade” situation or the subsequent brickage.
Be that as it may, I gained a new respect for those messages, because after flashing the rescue mode and going in with telnet, this is the kind of stuff I see in the log file
May 21 09:30:36 Xperia10III sailfish-upgrade-ui[4773]: Package: harbour-callrecorder;0.7.4-3;aarch64;installed,
May 21 09:30:36 Xperia10III [RPM][12613]: scriptlet %preun(harbour-callrecorder-0.7.4-3.aarch64) failure: 2
May 21 09:30:36 Xperia10III [RPM][12613]: erase harbour-callrecorder-0.7.4-3.aarch64: failure
May 21 09:30:36 Xperia10III [RPM][12613]: 1 elements failed, 1 scripts failed
May 21 09:30:36 Xperia10III sailfish-upgrade-ui[4773]: Distribution upgrade error: Subprocess failed. Error: RPM failed: Stopping service...
Failed to connect to bus: No such file or directory
error: %preun(harbour-callrecorder-0.7.4-3.aarch64) scriptlet failed, exit status 1
error: harbour-callrecorder-0.7.4-3.aarch64: erase failed
I removed that over telnet, apparently successfully, but can’t continue the investigation right now.
Is there a way to use pkcon or whatever to retry the upgrade? I seem to have network routing issues with the phone attached, like all the internet is between my desktop and phone and nothing else, so that’s fun too.
2 Likes
Although, it’s nice to know, it’s a pita. Can we please just have a normal ‘option’ to display or not? After all the fuss of getting omweather working again, this is a bit of a ‘slap in the face’. I was also considering doing an event view for my weather app (which badly needs refactoring) but am totally uncertain about that now.
1 Like
I’m not sure if a normal option would benefit anyone. People using vanilla OS without rpms outside the store would be confused on a feature which doesn’t work properly. People doing patches or providing hackier rpms can have the patch/rpm override the configuration relatively easily without needing options provided.
Here’s some more paper trail in case anyone wants to see it
/ # cd rootfs
/rootfs # chroot .
~ # head /var/log/systemupdate.log
-- Logs begin at Tue 2024-05-21 09:26:57 EEST. --
pkcon is a disaster, it only complains about “failed to contact PackageKit”.
ssu s tells me I’m on “latest”.
version says “Sailfish OS 4.6.0.11 (Sauna)”
Trying version --dup fails because I don’t - at least now - have networking off the phone… I’ll have to refresh my memory for how to get that working, because version --dup starts off with “REFRESHING CACHE AND DOWNLOADING PACKAGES”
2 Likes
I’ll add some networking notes if anyone cares, or regardless.
Your desktop may start routing via the phone at the end of the USB. This is bad.
Do this on the desktop
sudo ip route del 0.0.0.0 dev usb0
sudo ip route del default dev usb0
sudo ip route add 0.0.0.0 dev enp33s0
sudo ip route add default dev enp33s0
And this on the phone (telnet, not eg. voice)
ip route add 0.0.0.0 via 10.42.66.70 dev usb0
ip route add default via 10.42.66.70 dev usb0
But wait, there’s more!
On the desktop
echo 1 | sudo tee /proc/sys/net/ipv4/ip_forward
sudo iptables -t nat -A POSTROUTING -o enp33s0 -j MASQUERADE
And on the phone, add something reasonable (not 8.8.8.8) to /etc/resolv.conf
echo "nameserver 192.168.1.1" > /etc/resolv.conf
2 Likes
Hi,
I have Android App crashes when swiping for example (but not only) after 4.6 upgrade.
Here’s the log I can see with Journal
may 21 10:41:55 SailfishOS-GNU-Linux kernel: PMI: smblib_get_apsd_result: APSD not done yet.
may 21 10:41:56 SailfishOS-GNU-Linux lipstick[3531]: [W] unknown:0 - Cannot send touch event, no pointer focus, fix the compositor
may 21 10:41:56 SailfishOS-GNU-Linux lipstick[3531]: [W] unknown:0 - Cannot send touch event, no pointer focus, fix the compositor
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: release 27274:27366 transaction 824297 out, still active
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: 26330:26330 BC_DEAD_BINDER_DONE 0000000000000003 not found
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: 26330:26330 BC_DEAD_BINDER_DONE 0000000000000002 not found
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: 26330:26330 BC_DEAD_BINDER_DONE 0000000000000004 not found
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: 25333:25333 BC_DEAD_BINDER_DONE 0000000000000003 not found
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: 26330:26330 BC_DEAD_BINDER_DONE 0000000000000002 not found
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: send failed reply for transaction 895715 to 28618:29786
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: unfinished BINDER_WORK_NODE, proc has died
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: unfinished BINDER_WORK_NODE, proc has died
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: unfinished BINDER_WORK_NODE, proc has died
may 21 10:41:56 SailfishOS-GNU-Linux kernel: binder: unfinished BINDER_WORK_NODE, proc has died
may 21 10:41:56 SailfishOS-GNU-Linux lipstick[3531]: [W] unknown:1036 - file:///usr/share/lipstick-jolla-home-qt5/compositor.qml:1036: TypeError: Cannot read property 'closeHinted' of null
may 21 10:41:56 SailfishOS-GNU-Linux [26330]: [W] unknown:0 - "GNSS Remote died, cleaning up!"
may 21 10:41:56 SailfishOS-GNU-Linux [25333]: [W] unknown:0 - alien died! Trying to reconnect.
Has anyone an idea on how to fix this?
Regards
More fun.
version --dup and the /usr/bin/rnd-dist-upgrade command it calls seem to do nothing. There’s no verbosity nor do I have strace on the phone to gain any verbosity.
I eventually did use curl to install sfos-upgrade as a cheat mode.
mount /sys
ssu re 4.6.0.11
/usr/bin/sfos-upgrade --verify
Of course that does (“does”) the same thing as version --dup, which doesn’t amount to much.
About strace? Anyone got an aarch64 build to put up on openrepos?
You’re running armv7hl userspace are you not?
A 10iii
~ # rpm -qa | grep armv7 | wc -l
0
~ # rpm -qa | grep aarch64 | wc -l
791
And Wireshark confirms, by eg. capturing device usb0 and displaying tcp.port == 443, that any curl requests show up just fine, but /usr/bin/rnd-dist-upgrade is just helping itself to a VSZ of 123m and sitting with it like there’s nothing more important to do.