About redesigning incoming call experience in 3.4.0

Very late 2 cents. I love the empirical testing that you’ve done, and the design decision makes sense on a macro level. Individual preferences don’t live on a macro level, and I’d prefer to have the possibility to chose myself which option I prefer.

My problem with the new design is probably because I got used to the old way of doing it. I feel the new way is inconsistent with other actions across different activities (e.g. swipe up/down still exists for alarm, and swiping left for accessing the homepage from pretty much any other place).

3 Likes

Last week I rebooted my XA2 for the xth time. Each time I have to do the instruction, still with pulley menu, very easy. The phone hives a little push when scrolling up or down.
Inkeep my XA2 in Torronsuo because I cannot adapt to the new swiping when picking up a call. Overall the UI becomes more hybrid now, which is a bit chaotic. I also have an XA2plus that has a broken card slot. This has been updated to Koli. I use ot at home only. I really hope that Jolla will give us the option to choose for the pulley menu when answering a call.

I updated my patch to work on SailfishOS 4.
https://coderus.openrepos.net/pm2/project/return-old-incoming-call-screen

4 Likes

hullo @Kuba77 - finally I tried your patch, on all new 4.1.0.23 Kvarken, via Terminal as recommended. No success yet. I’ll try again later this day, could be a mistake been done.

Hello, I am on 4.0.1.48 now so I can’t confirm if my patch works on 4.1.0.23.

thank you - so I’ll wait :wink:

it seems Kvarken 4.1.0.23 is XA2 specific or something…
pkcon update messages no packages require updating to newer versions. So that seems the latest version I can get on my hardware.

sorry: of course 4.1.0.23 is a more recent version than 4.0.1.48

Sailfish OS update 4.1.0 was rolled out to the early access subscribers last week. It will be released to all users in the next 1-2 weeks (that is the plan).

Bluetooth switch is not working since 4.0.1.48 and may be earlier (see here). Are you planing to address this issue?

No, there are no pushes anymore, it’s just swiping. The lack of pushes is one of the reasons that I miss calls. The swioing gesture is too vague.

I’m not sure if it is only behavior of my Sailfish XA2, however I didn’t change /etc/mce. But: When my phone sleeping (display is off) I have call and I didn’t answer this call, LED starts blinking after this call ended. Which is normal and good. Then I wake up phone, look who was calling in events view and switch phone sleeping back (switch display off). The LED stopped blinking / lighting. Which is also OK. But when again (after few minutes) rings SAME number and again I don’t answer call, the LED will not start blinking anymore. Which is weird - because I don’t have any notification about second call. What is logic behind this?

2 Likes

This might be a bug you encountered. Post it to #bug-reports so it gets the right attention