Update went well without issues. Wifi hotspot and internet comnection sharing is now working on my Xperia10III. Thank you very mich for implementing CLAT!
1 Like
Hi,
XA2 Dual and XA2 Single, 4.5.0.19, flashed.
Very happy user here! 
This release is working very well for me. I wouldn’t say “perfectly”, but it is perfect for my daily use.
Glitches, IMHO minor:
From time to time, rarely, the browser crashes.
Also very rarely, an SMS is not sent (that was somewhere in 4.5 other releases. 19 is too new to pronounce myself)
However, I cannot tell about Android Support, as I very rarely use it and generally only to fiddle or make some tests.
Edit: I am using Bluetooth for speakers only. Works well.
If you are using a secondary user, and only in this case, I’d be more careful, as all user data are sometimes (rarely, perhaps once every 3 month) totally deleted.
So, I’d say: go ahead!
In any cases, upgrade or not, I still would recommend you to have a fresh and useable backup.
1 Like
It is in the background. The user cannot do anything but use the mobile data.
2 Likes
About 64-bits Deadbeef: try to install last version from Storeman
3 Likes
Non of this from a month ago on XA2 was fixed! I did though go for 4.5.0.19 hoping for improvement and was terrified after the update as XA2 lost the ability to make phone call. Restarting fixed this issue in my case.
Every update of Sailfish OS is cutting back features and now we are lacking basic functionality that we had almost 20 years ago with Nokia N95, not to mention Nokia N9 which is the grand, grand, grand parent of nowadays Sailfish OS. Thats the reason I keep my Android Xperia 10 III in the drawer hoping for a better days to come!
1 Like
Oh, a version that “works”. ty
1 Like
Share menu seems to break with AlienDalvik when removing certain applications. Share menu still shows item if the app is uninstalled. Seems to occur for Instagram as well as Pixiv. Entries still show on Sailfish’s share function despite them not being installed.
1 Like
Thank you very much @carmenfdezb for the new version and for caring about this wonderful app!!
Is there also a new version for 32 bit Xperia 10 for the new SFOS 4.5.0.19?
On the Volla I could successfully install the new version 0.10 and it works like a charm, but the Volla is still on SFOS 4.4.0.72 because 4.5.0.19 not yet available.
1 Like
You’re welcome, @Seven.of.nine! All merits are for kravich, he did a hard work to implement deadbeef for SailfishOS and I only build it for aarch64.
I contacted to him some time ago and I volunteered to update Deadbeef with all improvements that he had added but I get no answer. At this point, and because the users couldn’t use this app on sfos 4.5, I decided to release the new version for x64 on openrepos.
I could update deadbeef for all architectures on openrepos but maybe, this app should be added to chum repositories, this would allow us to get this app for all architectures and for every update of sailfish.
2 Likes
I have logged a couple of bugs that I do not believe have been addressed. Although there was a complicated workaround posted for the persistent settings issue (somewhere on this forum), the timeout issue while loading large directories is a continuing irritation.
Thanks for the aarch64 build, it is appreciated
Chum would seem the way to go moving forward.
2 Likes
Sandboxing is disabled, so you won’t have any problems with settings now.
2 Likes
Hi,
just a short feedback. Since Sailfish 4.5 I have constantly the problem that my Sony Xperia XA2 dual sim says “no sim card inserted”. I have to restart the phone to use it again. This is very annoying because in the past there wasn´t such a problem. Sorry but I have no log files etc. because Iḿ a normal user. There is no special situation were it happend. But it happens since 4.5. And it happens very often.
i fixed my notifications bug, it was on my end.
the other five regressions previously reported (android-app-sdcard, media-scanner-cpu-100, element-crashes, cannot-send-mms, cannot-bluetooth) remain.
AND i have another regression to report. mcetool --set-exception-length-usb-connect=0 is no longer respected! (nor mcetool --set-exception-length-charger=0)
on sfos=4.4.0.58, it works fine, and the screen stays off when i plug in the charger.
on sfos=4.5.0.19, there seems to be an enforced minimum of 3000msec.
Had a look at the new Calendar right now. The new 3 viewing modes (month, week, day) are really beautiful! Thank you Jolla!
4 Likes
Just to make sure - For those who report problems with MMS:
I had problems with MMS not working properly. I then discovered that there is a setting regulating the maximum size of messages in the Settings - Apps - Messaging (or whatever it’s called in English). Although I just send pictures taken with the phone’s camera, (which, in previous versions, at least, is scaled down to a reduced resolution), increasing this setting solved my problems. So if you, like me at the outset, is not aware of this setting at all or have it set to a low value, test it out by increasing the accepted message size.
(MMS problems may be due to so many factors. The previous time I installed SF on a new phone and encountered MMS problems, it finally turned out to be caused by the phone’s SIM card being a twin card, and my carrier don’t forward MMS to those, only to main SIMs … )
2 Likes
- for me, MMS send works 100% of the time with SFOS 4.4, and is 100% broken on SFOS 4.5 with identical settings
- MMS size settings do not help (although its quite odd that making it larger fixes it for you. for me, only Large-600KB and smaller ever works, on any SFOS version)
- MMS receive works fine for me on SFOS 4.5
what i get in mms-engine is:
2023-05-11 21:35:18 [mms-task-http] /tmp/mms-engine-PNAI41/msg/9091/m-send.req (222265 bytes) -> http://10.188.239.143/mms/wapenc -> /tmp/mms-engine-PNAI41/msg/9091/m-send.conf
2023-05-11 21:35:18 [mms-transfer-list] Transfer /msg/9091/Send started
2023-05-11 21:35:18 [mms-task] Send[9091] NEED_CONNECTION -> TRANSMITTING
2023-05-11 21:35:18 [mms-transfer-list] Update flags => 0x11
2023-05-11 21:35:25 [mms-task-http] HTTP status 200 [application/vnd.wap.mms-message] 18 byte(s)
2023-05-11 21:35:25 [mms-task] Send[9091] TRANSMITTING -> DONE
2023-05-11 21:35:25 [mms-transfer-list] Transfer /msg/9091/Send finished
2023-05-11 21:35:25 [mms-task-send] ERROR: Missing Message-ID
i recompiled mms-engine and added some debug logging nearby. pdu->sc.msgid is NULL and pdu->sc.rsp_text is "OK".
also, the identical mms-engine rpm works correctly on SFOS 4.4, so the problem PROBABLY isnt in mms-engine (although i do have to symlink /usr/lib64/libgmime-3.0.so.0 => libgmime-2.6.so.0 to make one rpm target both platforms, so its not a perfect test. i get the same error with jolla’s RPM as with my custom built one, though, so it’s probably a good bet that the problem is not mms-engine)
2 Likes
Hello
is it safe to upgrade the phone by now?were the issues fixed?i really don’t feel like reading 400 posts.
i need the phone for work.
also should i even update if everything works just fine with my current OS version and i miss nothing?