[Release notes] Tampella 5.0.0.55

[ric9k]

Yes. Thanks to @dcaliste we now have the ability to block numbers, one by one via the GUI or more widely by using commands in the terminal.
In example, here is the command used in France to avoid known advertising numbers:

dconf write /sailfish/voicecall/filter/ignored-numbers [“‘^+33162’, ‘^+33163’, ‘^+33270’, ‘^+33271’, ‘^+33377’, ‘^+33378’, ‘^+33424’, ‘^+33425’, ‘^+33568’, ‘^+33569’, ‘^+33948’, ‘^+33949’, ‘^+338060’”]

This will block all numbers beginning with “+33271” etc.

To check how it went, you can use:

dconf read /sailfish/voicecall/filter/ignored-numbers

There is also rejected-numbers instead of ignored-numbers.

[windes]

Yea, i test it, we can simply type in Settings app field this sentence - ^+3956 and press Enter. No need to edit system files! (Sure copy this sentence from Notes, we can’t type ^ there).

[dcaliste]

Thanks @ric9k for the details. Indeed the backend supports blocking ranges of numbers. It was decided not to show it in the UI because I didn’t find any convenient way to do it, adding or editing.

The ignore list lets the caller earing the ringing tone, while the reject list send them to the voice mail.

There is also a white list to always allows a given number or even list, whatever its matching by a ignore or reject pattern.

[rainemak]

Have you tried enabling and disabling Flight mode or maybe changing active sim from Settings → SIM cards. If you have your SIM card in slot 1 maybe like this…

1. disable SIM 1
2. enable SIM 1

Nb, if you have SIM 2 already disable you need to enable it first.

[windes]

Omg, cool! Whitelist! Could you please explain, how to use it?

For example, we can block ALL numbers, except +3956* ? How?

[jovirkku]

@harbourlights

deleting/reinstalling AAS

When removing AAS, did you follow these instructions:

Removing Android AppSupport

?

[demislition]

A funny bug emerges on the Android side of Tampella-by-upgrade-route (Xperia 10 II): after some uptime, when trying to start an Android app, it instead starts another Android app, the one that has last been shut down. Or not so much doesn’t start it but brings it back up at the point it was (supposedly) shut down.

So when trying to start a new Android up, it instead activates the previous, apparently still-running Android app which had its window shut. This happens on the first try on the icon of the new app. The second try correctly starts the Android app that I was trying to start. Looks like the new Android app tries to start on the first try but quite can’t and shuts down after some seconds.

A reboot fixes the issue.

[dcaliste]

To block all incoming calls except some based on a prefix, you can do:

• dconf write /sailfish/voicecall/filter/ignored-numbers ["*"]
• dconf write /sailfish/voicecall/filter/whitelist ["^+3956"]

The logic for the filtering is based on :

 // Give priority to exact matching.
        if (m_whitelist.exactMatch(recipient.remoteUid())) {
            return FILTER_APPROVE;
        } else if (m_rejected.exactMatch(recipient.remoteUid())) {
            return FILTER_REJECT;
        } else if (m_ignored.exactMatch(recipient.remoteUid())) {
            return FILTER_IGNORE;
        } else if (m_whitelist.match(recipient)) {
            return FILTER_APPROVE;
        } else if (m_rejected.match(recipient)) {
            return FILTER_REJECT;
        } else if (m_ignored.match(recipient)) {
            return FILTER_IGNORE;
        } else {
            return FILTER_NO_MATCH;
        }

And the matching function for each list is :

    for (const QString &filter : list()) {
        if (filter.startsWith('+') || filter[0].isDigit()) {
            // Exact number matching
            if (recipient.matchesRemoteUid(filter)) {
                return true;
            }
        } else if (filter.startsWith('^')) {
            // Prefix matching
            if (recipient.remoteUid().startsWith(filter.mid(1))) {
                return true;
            }
        } else if (filter == QStringLiteral("*")) {
            // All
            return true;
        } else {
            qCWarning(voicecall) << "unknown filter" << filter;
        }
    }
    return false;

These are taken from voicecall/plugins/filter/lib at master · sailfishos/voicecall · GitHub for those interested in modifying or improving the code. Note also that this plugin is exporting a library, that can be used in application to change the lists programmatically.

[Kea]

The update went smooth on my XA2 plus, XA2 and 10 III. (The latter is not in use since echo canceling doesn’t
work.)
For the first time since years I could install Tutamail on the XA2 plus and it works!
Qwant search works in the browser.
Wire voice calling works.
Sms works.
Downloading Organic Maps from FDroid failed.
Not yet tested: gps.

The XA2 plus is the best Sailfish device I’ve had. System storage nearly full and the card slot is broken. If I could get hands on a new one with more storage…

[vige]

I’ve bumped to same issue on Xperia 10 III. I don’t know what triggers it, as I think I’ve only seen that happen once.

[lkraav]

Something seems to have been modded with App Support window timings or related mechanics - for example Slack workspace switch now gets stuck in app switcher on 5.0.0.55, whereas previously it would re-zoom into new workspace window successfully by itself.

[hattu]

Fdroid and Aurora do not work with wifi connection.

[hschmitt]

Thanks, what worked for me was I stopped AppSupport, disabled SIM 1, enabled SIM 1, started AppSupport.

[fridlmue]

Is it requiered here to follow the “brutal way” uninstall, or can some apps remain when following the “clean removal” part?
Is it maybe possible to identify some more system files to delete to prevent all android apps from have to be removed?

[filip.k]

Isn’t echo solved with later Android blob reflash?

[Pam]

Xperia 10 IV. 5.0.0.55.
Screen brightness is excellent. Also with auto adjust settings.

[davidrasch]

Sony Xperia XA2 Plus 32GB [Dual-Sim] schwarz gebraucht kaufen | Sony Xperia...

[MeeGo-Junky]

Screen Brightness Xperia 10 V

I am bit puzzled because the screen of my Xperia 10 V under Sailfish OS is very dim. I set brightness to maximum under settings but the device cannot be used outdoors during the day, except for very cloudy days. Why does it appear strange to me? According to the specifications the screen of the Xperia 10 V should be much brighter than the Xperia 10 iii But under Sailfish 4.6.0.15 and 5.0.0.55 maximum screen brightness is much LOWER on Xperia 10 V than on Xperia 10 iii. even 2012 Blackberry Q…

[Kea]

Thank you for your reply. The device I use also has 32GB storage. I am looking for an XA2 with 64 GB. But that is like a needle in a haystack.

[Kea]

I don’t know. I am not keen on flashing, sorry. The person who looked over my shoulder when I did it the last time is not available. Perhaps I will try again in the future.
Besides, I like the screen ratio of the XA2 and XA2 plus more than this narrow, long screen of contemporary Sony’s. The XA2’s also have much better visibility and better sound.