[Release notes] Vanha Rauma 4.4.0.64

Announcements
#304

Thanks. Indeed, that was the issue. I was able to successfully update the system with commands provided in those links.

#305

jisho.orgā€™s dark theme still not working in this version of the browser.

1 Like
#306

Hey there!

First thanks for the all the work some people put into sfos and trying to help other folks :slight_smile:

I have an Xa2 with 4.3 and Xperia X compact recently flashed with the sailfish-patcher and 4.4

I did a backup (including some apps) on my xa2 and used it on the xcompact but besides that its ā€œcleanā€.

The Wifi is acting different on my compact in comparison to xa2 bu in general it seems to work fine.
(On xa2 I could just one click wifi in the upper menu and turn it on and off. On xcompact the wifi search always comes up even if Iā€™m in reach of a know wifi. It seems it is also connecting correctly but still showing the search wifi. Can click anywhere to make it disappearā€¦ so not a big problem.)

But I think Iā€™m running into some sandbox problems. Iā€™m using Wifikiller and I guess it is not sandbox ready. If I add the

[X-Sailjail]
Disabled

with a newline before that in
/usr/share/applications/WiFiKilL3r.desktop

The Wifikiller Icon disappears. Same for harbour-ownkeepass (The app is working but only in non hidden i.e. default folders, workaround for me is keeping the database in one of these folders, like ~/Documents)

However if I start the apps through the command line or launch them with storeman the apps are working like expected. Am I missing something cause the sailjail line is often mentioned as a workaround in this threadā€¦

Thanks in advance and keep on doing whatever you do.

kk

#308

Itā€™s
[X-Sailjail]
Sandboxing=Disabled

#309

Thanks man, donā€™t know how Iā€™m able to miss that while copying. Cheers

#310

The update on my Xperia 10 II, like nearly any SFOS update so far, was completely without problems. After reading this thread, I had de-installed storeman out of caution. Looking forward to Xperia 10 III support to be ready!

3 Likes
#311

Also had this. For me, it turned out that the installation wasnā€™t completed. The version number was increased to 4.4.0.58 but several applications (browser, gpodder and even phone calls) didnā€™t work. Turned out aliendalvik-control had disrupted the installation: both manual and sfos-upgrade attempts to remove it had failed due to some mime-type warning which defaulted to abort.
zypper remove aliendalvik-control
and then i for ignoring the warning made it possible to complete the installation with sfos-upgrade. Iā€™m sure you have solved your issue by now, but it might help someone else.

3 Likes
#312

4.4.0.58 list of things broken ability to make or recieve calls, sms, bluetooth, GPS, netowrk unable to get signal often, unable to connect to 2g/3g/4g more often than not, sound was too low, VPN enabled still connects without running thru the VPN.

FIXED everything on XperiaX by simply doing a clean install of Sailfish 3.4 and now everything works as it should, best yet my favourite patches all work again.

Highly recommended fix, cannot see ANYTHING that 4.x brought to the table that 3.4 didnā€™t have.

1 Like
#313

Interesting. Thank you. I would like to reinstall 4.4.0.58 after having removed aliendalvik-control. If I run sfos-upgrade after the removal of aliendalvik, sfos-upgrade will attempt til downgrade my current 4.4.0.58 installation to 4.3.0.15. I am not sure I want to procede with that. What procedure would you recommend?

#314

SPOT ON!!..wipe and start again!

1 Like
#315

Had same issue with aliendalvik control
removed with rpm, then version --dup finished the upgrade successfully .

#316

rpm -e aliendalvik-control fails for me. What is the exact command you are using?

#317

It seems to remove it, but then it is still present in the Settings menu. All the files belonging to aliendalvik-control are also still present. I am not sure that this command really removes aliendalvik-control?

#318

rpm - e --noscripts aliendalvik-control

#319

This did not complete the upgrade at my end. Rather, it downgraded my system to 4.3.0.15. After that I then downloaded the 4.4 upgrade package once more and completed the upgrade. I hope it is better now.

#321

Interesting. You are right - I can also still see aliendalvik-control in the settings menu. Not sure why it wasnā€™t removed. For me, this still allowed me to complete the upgrade with sfos-upgrade.

#322

I found in ā€˜General - How to remove Alien Dalvik through the console?ā€™ (How to remove Alien Dalvik through the console?)

devel-su
pkcon remove aliendalvik
rm -rf /home/.android/*
rmdir /home/.android
rm -rf android_storage
reboot

I used these commands just now on a phone where I donā€™t need AD at the moment, with CLI in the /home/defaultuser directory. Worked perfect.

Thanks to @sfbg and @aspergerguy

1 Like
#323

@gaidheal, @mortenbo,

  1. do not use rpm for package management, only use rpm -q for analysing! See for more details and for an explanation.

  2. sfos-upgrade and version --dup do the same; neither one does try to downgrade SailfishOS, when not explicitly commanded so (which will likely fail). SailfishOS was obviously never fully upgraded on your devices and either of these command revealed its real state.

2 Likes
#324

@olf rpm was the only command that would successfully remove that package. Normally I use zypper/pkcon neither worked as they failed on the script. Hence rpm -e --noscript
anyway phone is now working where as it was in a broken upgrade state.

#325

That is also my conclusion. It was basically just the version number that was upgraded. Thanks.