SFOS 4.5 feedback thread

General
#6

Wow! What an update! Many good things to enjoy of! Thank you!
Update went smoothly and fast (X10III)

At notifications screen; when starting Signal (android), app gives notification “Background connection established”. Now in 4.5.0.16 this notification cannot be dismissed anymore. Dismiss button is greyed out. (other notifications are still possible to dismiss but not this)

New calendar buttons “month - week - day” are not very nice in my humble opinion. Atleast not the placing of them. It’s quite thumb demanding task to select buttons if phone is in one hand… it would have been consistent if swipes would have been used (as in Phone app, Clock app and so on).
(I know…horizontal swipes are already used for scrolling calendar… but like this it is not optimal …in my opinion)

When in week view and landscape mode; huge amount of screen real estate is given to the buttons and day numbers. With simple organization of buttons and day numbers there could be a lot more space for the calendar itself.

[4.5.0.16] Signal notification cannot be deleted from the notification area
#7

Thanks a lot for this update that tries to address so many issues. Anyone already tried mobile hotspot on Xperia 10 III?
What happened to Chum? The icon disappeared during updating my testing device Xperia 10 II, and when trying to re-install from Openrepos, nothing happens.

2 Likes
#8

I note Sailfish still doesn’t indicate when the update is early access (though I didn’t try installing it). Good way to break newcomers’ devices.
Does the implementation of the Vulcan API excite anyone?

#9

It’s in the first lines of Release notes.

1 Like
#10

They’re not even vaguely obvious at any point in the upgrade process.

#11

Open settings of Signal from Sailfish’s settings and under Notifications, disable Background connection.

5 Likes
[4.5.0.16] Signal notification cannot be deleted from the notification area
#12

You can’t get the early access releases without explicitly signing up for them through your Jolla user profile on account.jolla.com.

9 Likes
#13

Good to know but still, Early Access should be prominently displayed in the Update Settings menu option and not trigger notificattions.

#14

It kind of is, on the page where it is enabled and if you do so you probably know what you are doing, and if not there is a good warning:

The early releases are mainly intended for developers, and the screening of potential critical issues with new releases before publishing to the wider audience.

2 Likes
#15

But why? People sign up for early access because they want to get the newest release as soon as possible, so not triggering notifications would be strange. Not to mention the update notification has never made any sound in the first place (despite there being an unused update notification sound in the OS). Showing an ‘Early Access’ banned on the update screen would admittedly be a nice bit of visual flair, but it would only solve a non-existent problem.

#16

The first release after many months is always an EA release and as @nthn wrote, this update isn’t visible to non EA users. In present state, a phone says ‘no update available’ if someone on 4.4.0.72 checks for version update and has not explicitly subscribed for EA releases (this requires also an extra registration at Jolla/Sailfish homepage) AND has set the phone to EA updates in Settings/developer tools. So it can’t happen accidentally to some innocent newbie.

1 Like
#17

You and I have very different definitions of “prominent” then.

Why? Because roughly a tenth of the main users of the forum installed it and now have problems. God forbid SF OS ever gets more popular. It’s also design 101.
Anyway, I mostly wrote the original comment to bump the thread and because I told Steve he shouldn’t install an Early Access release.

#18

Update went quite smoothly. After the OS installed, I note my device rebooted itself twice but succeeded in booting.

My Whatsapp UI had inverted colours (Here Maps too), no idea why, but thanks to forum member @pherjung, I was able to fix the problem. Timezone issues still exist though.

#19

How long it takes after the full bar of update progress has gone through until the device reboots.

Or, do I just press the power button to forcefully reboot the device.

(I recall I had to do something similar when I flashed Sailfish OS to the device)

#20

Does Partnerspace still work in 4.5?

1 Like
#21

The progress bar got stuck on my Xperia 10 II as well. I waited about 30 minutes before forcefully rebooting and everything’s fine now. It’s probably okay to reboot after only a minute or two, but it doesn’t hurt to play it safe.

#22

Great features! But …
On XA2 the automatic rotation does not seem to work after the update. Can someone else confirm?

#23

Not sure as partnerspace is an experimental function.

#24

was there some magic button combination to be pressed in order to make this powerdown – pressing power button for one minute does not do it… ?

#25

It’s very easy to enable and disable, so I’d be very grateful if someone could test it for me… I remember having heard some rumors that it was going to disappear in 4.5, so I’d like to verify it because I use it and I won’t upgrade if it’s gone…

To enable it (with Calculator app running in it) just type in Terminal:

dconf write /desktop/lipstick-jolla-home/partnerspace/applications "['/usr/share/applications/jolla-calculator.desktop']"

Then to disable, type:

dconf write /desktop/lipstick-jolla-home/partnerspace/applications "@as []"

Thank you very much in advance anyone who can check this for me.