[Release notes] Tampella 5.0.0.73 - Early Access

[rtr2001]

@wetab73

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.

Install/remove via Aurora app store (or uninstall from the appgrid) work for me (X10III).

[yusssufff]

Upgrade smooth and no issues on 10 II.
Thanks Jolla .
I have still to test now if it solved or partly solved this substancial issue i had with android-telegram audio and video calls:

[BUG] [Xperia10II] [5.0.0.67] Hashed audio call on telegram

REPRODUCIBILITY: reproducable on 10 II, but not on XA2 OS VERSION: 5.0.0.67 HARDWARE: Xperia 10 II UI LANGUAGE: English REGRESSION: DESCRIPTION: When making a telegram audio call, the sound heard is very hashed, relatively impossible to hear the other person speaking… PRECONDITIONS: android app support via paid licence STEPS TO REPRODUCE: open android telegram app make a call EXPECTED RESULT: Hearing the other person correctly ACTUAL RESULT: Very hard to hear to other person (sound…

[yusssufff]

First observation after upgrade: When clicking on a link (hyperlinks), i used to have the full option of various installed android (and stock) browsers to use to open it. I could choose to tap either of them to open the link.
Now it just directly opens with default browser. Or if an android browser is set as default, then the option is just given to open either with that default android browser or the stock sailfish one (other android browsers dont appear as options to open).
Thats for hyperlinks in sailfish apps (eg Fernschreiber) or android apps (eg telegram).

[wetab73]

@yusssufff

I could choose to tap either of them to open the link.
Now it just directly opens with default browser.

I’ve been experiencing this annoyance (on all my devices) ever since the first 5.0.x.x release. Not only hyperlinks to browsers, but actually all MIME types are affected, i.e. you are no longer offered to open a music file in some Android audio player, or an image in an Android picture viewer, etc. I even discussed it in another thread a few weeks ago (i.e. before this latest OS update) and the other user confirmed also having it. So it’s not this update, but OS 5.x in general no longer handling MIME types of Android apps. See

AppSupport randomly crashes until device reboot

Is this an intentional change that on SFOS 5.x if AAS isn’t running MIME assignments of Android apps are not visible to SFOS? For example, on SFOS 4.x if I click some link to a web page, I am presented with a list of web browsers including Android ones (e.g. Firefox), even if AAS is not started, and if so then selecting an Android app automatically stats AAS and then lauches it. On SFOS 5.x, however, if I click a link to a web page and AAS isn’t started, I am only shown a list of native SFO…

Anyway, can someone please tell me which service is responsible for updating Android icons in the Sailfish launcher (app grid), i.e. adding them upon installation of an Android app and removing upon uninstallation? This update broke it and icons of newly installed Android apps just don’t get added, and I would really like to try to fix it.

[catonyourcomputer]

I don’t know but this may be worth posting a Community Meeting entry since it seems quite serious

[rtr2001]

I wonder if your upgrade went fine.

I’d check the upgrade log for errors and maybe attempt a version --dup.

[lkraav]

@lkraav

Is restoring SFOS stock AAS image for upgrade duration enough here as well?

I’m live on A13, with injected MindTheGApps. Details at

Google Play Services on Xperia 10 III Sailfish 4.4.0.64 (now 5.0.0.73)

I’m live on A13 Thanks Opus 4.6, it solved all challenges mostly on first try. Giving it stock system.img to explore helps things along, too. I think my installgapps.sh fork should be fairly foolproof now for A13, but there’s no warranty and no guaranteed support, or response time of any kind. [Screenshot_20260208_173449_001] Yes, it seemed to be a problem of some kind. In an initial makeover, Google system services would crash with permission error, and AAS would fai…

Overall, the process was pretty much the same as previous stock system.img updates, other than now installer script needing to update for MTG (since Open GApps project died).

AFAICT update process with a patched system.img is still

• Settings > AAS: disable “Start on bootup”
• Update to 5.0.0.73, stock system.img replaces ours
• Re-patch with A13-compatible script version
• Start AAS
• devel-su appsupport-attach /system/bin/logcat to monitor for any unexpected crashes

At above post, I was made aware there’s another method some people are using: Google Apps changes can be live-mounted into AAS LXC. I haven’t tested this myself yet, but it seems like a solid way to avoid stock image patching busywork, so will probably look into it on one of the upcoming weekends. Based on what I’ve seen, it’s likely AAS will crash with missing permissions for Google services, and you will have to get updated permission schemas shipped one way or another.

Anyway, fortunately nothing insurmountable, and I’m already seeing a couple of great wins:

• Google Wallet works
• ChatGPT app works

Both previously failed due to various missing security mechanisms in A11 AAS, but whatever they missed, seems to be there now!

TBD how well good ol’ mobile data holds up between WIFI switches!

[pemek]

Update went smooth, Xperia10III is up and running, most of the basic stuff works.
But:

• MIME handling between SFOS and AAS does not work

• Android app start in small window 1/3 of size, scalled. IKO (bank app) - always, in some cases DDG browser started for logging in in other app.

Regarding IKO app, there was a W/A earlier to start it using qCommand and apkd-launcher (or running from other app) but it does not work now.

Edit: ING, first start after installation in Autora Store also opened in minimized form, consecutive attempts to reproduce failed. Removing and installing again, start → again minimized, next start, ok. (reference: [4.6.0.11] App Support, app grid - ING Banking App and others are killed (closed) after entering PIN )

[Keto]

@wetab73

After update icons of newly installed Android apps do not appear in SFOS launcher (app grid)

Could you crate a separate topic about this in bug reports category?

[Keto]

@wetab73

I’ve been experiencing this annoyance (on all my devices) ever since the first 5.0.x.x release. Not only hyperlinks to browsers, but actually all MIME types are affected, i.e. you are no longer offered to open a music file in some Android audio player, or an image in an Android picture viewer, etc. I even discussed it in another thread a few weeks ago (i.e. before this latest OS update) and the other user confirmed also having it. So it’s not this update, but OS 5.x in general no longer handling MIME types of Android apps.

This is also something that should have it’s own thread. Discussing them in random threads easily goes unnoticed and is difficult to track.

[abranson]

Android 13 changed its behaviour when opening web links: it no longer lets you leave the browser choice as ‘Ask every time’ - it always automatically opens them in a default browser. If your default in AppSupport is set to the same as SailfishOS then you won’t get a choice, while if it’s set to something else then you’ll get to choose between those two.

The mechanism for URL and MIME type handing with Android apps has also changed. Previously, handler desktop files were generated with MIME handlers declared as close to the Android handling as we could get, but there was a limit on how accurate that could be. So it’s been switched to query Android directly, which is much more accurate but requires AppSupport to be running so it can process the query.

Desktop files for Android apps should be generated in ~/.local/share/applications. If you’re not getting any at all, then that’s not working in your case and some logs might help (in another thread maybe).

[yusssufff]

I noticed that after the update, AAS is busy ‘‘optimizing’’ apps. That appears in the notification area, can take quite some minutes to complete the job.
I guess if user reboots or even try to open some AAS apps it may interfear with that needed process? If not then no worries, but if yes maybe it should be written in upgrade message that user should wait 5 mn after upgrade to let AAS do its thing?
I remember such a warning appeared in one of the big AAS upgrade some years ago (the one that switched from Alien Dalvik to AAS i think)

[wetab73]

@Keto

Could you crate a separate topic about this in bug reports category?

@Keto

This is also something that should have it’s own thread. Discussing them in random threads easily goes unnoticed and is difficult to track.

Of course, I will create separate topics for both issues. Please just note that there was a valid reason for first asking such questions “in random threads” just to first (try to) make sure that it not an individual, unique problem of mine not worth separate thread / bug report, rather than actual bug.

[abranson]

You don’t need to worry about messing with it - it’s always done this in the background and we’ve just added a special notification in this release to show you what’s going on. If you interrupt it then it’ll just resume next time.

[pemek]

Replying to myself as I found an answer to my problem. In Android Developer Options there is an option named “Enable freeform windows”, it was enabled in my case. Disabling it fixed improper scaling.

[pawel.spoon]

Update went fine on C2

[teleshoes]

anyone got any comment on network improvements for AAS 10III? (i have to restart AAS every couple of hours to get mobile internet to work on 10III on 5.0.0.72)

(i’ve got a fresh 10III coming in the mail that i will test 5.0.0.73 on when it arrives. OTA updates dont usually work for me, so i’ll do a fresh install of 5.0.0.72 and then OTA that one)

[attah]

What do you do with your devices to make OTA updates not work? I have had like one update fail ever.
I don’t have any AAS network problems either really - there was a slight regression at some point (which got solved), but in total at has been good.

[Keto]

The AppSupport 13 update brings the “Treat mobile data as WLAN” option in the settings, which in many cases should help with the connectivity issues.

Though it has the down side that options in apps which depend on the used connection type (such as use lower streaming quality or limit downloads on mobile data) do not work as intended.

Sorry, correction: This does not seem to available on Xperia 10 II and III

[attah]

@Keto

The AppSupport 13 update brings the “Treat mobile data as WLAN” option in the settings,

Where exactly? I cant see it in the AAS entry in settings.