/run is a tmpfs mount meant for runtime files that are not permanent. Not sure how it could have worked before the update, as nothing related this was changed.
I think your dbus service file should go in /usr/share/dbus-1/services instead.
2 Likes
According to your documentation it’s the expected location, however; and as stated - and I re-iterate - it used to work before the update… in fact, i didnt generate the file, nor store it in that location :); I merely made sure to follow the documentation to the letter (including a syntax-sensitive property value “Disabled” , which almost drove me insane 
)
These files are generated to /run/user/*/dbus-1/services/ by Sailjail on user session startup and modified whenever a desktop file changes, e.g. when an application is installed, updated or removed. That new key is used the same way as regular Exec key in Desktop Entry section but it enables use of different arguments.
Perhaps some service is not run to generate these temporary files (which is why they are most likely placed on the tmpfs..)
Right, I think Sailjail does not generate the dbus service file if you have Sandboxing=Disabled.
But again, this did not change in this update, and it is a bit out-of-scope for this topic. So maybe start a new thread about this to sort out what’s actually wrong.
2 Likes
I have a Xperia 10 II just as a tinkering box, so I just wiped the whole thing, reflashed 5.0.0.72 and upgraded it to 5.0.0.73. Installation went without a problem.
Played with the new install for half an hour and seems to be running mostly fine. So far the things that now have some minor issues are Sailfish containers and Pure Maps.
With Sailfish containers I have sometimes issues opening the X session to debian container or the button does not do anything but rebooting the phone seemed to help. With Pure Maps, it seems to crash some times when opening the menus under preferences. Also to this reboot seems to help.
Other than that, everyting seems to work fine.
Thank you for the update. My 10 III now has Android 13. Update went smooth.
Only this: I see that predictive text is included. That’s something I want to get rid of a.s.a.p. Is that possible?
I tried it in terminal on the XA2 plus, to no result. I was happy that the 10 III didn’t have it.
I would appreciate if you gave us the possibility to switch off predictive text.
devel-su
pkcon remove jolla-xt9
reboot
this worked a good few years ago, don't know if the package still has the same name
2 Likes
Thanks a lot for the update!
Regarding the fix for mouse rotation. My connected USB mouse in landscape mode still doesn’t rotate on a Xperia 10III. So for me the topic [C2] Mouse Axis are interchanged in Landscape-Mode - #2 by ric9k is unfortunately not fixed yet with this update 
Predictive text input is optional component on Xperia 10 III, it is not installed by default. But if you have installed it, you can also uninstall it from Store.
2 Likes
C2 and X10V went fine. X10III did not. Error message is just “couldn’t update” or something like that. Free space on root is 556,77 GiB.
This is my daily drive with the most important app ever (BankID). So re flashing is out of question until I get AAS bluetooth support, so I can move BankID to new phone.
Yes, that is unfortunately not a proper fix for the automatic mouse input orientation, but rather a workaround to provide fixed option to set the rotation. The example case there is the Volla Tablet with the attached keyboard / touchpad, used in a landscape orientation.
1 Like
Could you check /var/log/systemupdate.log ? Maybe send that to me in PM.
2 Likes
Thanks, Jolla, the update on my Xperia 10 III went smoothly. It didn’t take long, and everything works.
The AAS autostart error has been fixed.
However, since the update, I’ve been experiencing higher CPU usage. I noticed this because the phone is constantly warmer than usual. The CPU temperature is constantly at 38 degrees Celsius.
Crest shows three processes with consistently higher CPU usage 35 % - 55 %. Now it’s “lipstick-plugin evdevtouch” and “com.android.providers.media.module.” (Image 1)
Before restarting, it was “lipstick-plugin evdevtouch,” “surfaceflinger,” and “zygote64.” (Image 2)
Edit:
It has now stabilized again. “lipstick-plugin evdevtouch” and “zygote64” are only using around 15% of the CPU right now. I was probably too nervous, sorry.
Translated with DeepL.com (free version)
Keto, I got pred.text automatically with the update. It came in the forum app while typing. Went to Store again. Did the test: installed the app and de-installed it. I went to forum in browser: no pred.text anymore. Problem solved.
2 Likes
All fine on my XA2, apparently.
With one possible exception… Since updating yesterday, the native browser stopped responding twice in what looks like a novel way: not loading anything new until Home Screen is restarted through Sailfish Utilities. Can’t reproduce this though.
Done… !
(plus at least 20 chars)
It seems to work very well on my 10V.
Looks good on my 10III
Mystery solved;
the .service file is indeed a leftover from a previous sandboxed installation.
Un(sand)boxing the app (by adding Sandboxing=Disabled) does not remove the .service file.
Worth a bug report?
Pred.text came with the update, a bit confusing. Problem solved: I installed the app and de-installed it. Now it’s gone.
After this update I put my sim in the 10 III again and now the echo seems gone. Hope it stays this way. Not. Following phone calls still had the echo. Waiting for Jolla 2.
After update icons of newly installed Android apps do not appear in SFOS launcher (app grid). Similarly, icons of uninstalled Android apps do not get removed. Same thing on two different devices. Reboots or AAS restarts do not help. Which service is responsible for that?