That’s not recommended.
1 Like
Thank you for this useful observation. I totally didn’t know that already. /s
Something is probably broken, I just uninstalled AppSupport from the Jolla Store but it’s still there, just the settings entry disappeared. And it won’t reinstall from the store.
Unless there is an easy way to fix this, I will probably leave it as is since the XA2 is no longer my main device and it’s working fine otherwise.
EDIT: ah, I missed the memo that the Aurora Store had to be uninstalled before uninstalling AppSupport. Did that and it’s fully gone now. But it still won’t reinstall.
From command line check ssu lr output, and that it has under “Enabled repositories”
- aliendalvik ... https://store-repository.jolla.com/features/5.0.0.72/appsupport/armv7hl/
Install zypper (if you don’t have it installed already) with
pkcon install zypper
And check output of
zypper packages --repo aliendalvik
If it says “No packages found.”, then there is probably some problem with the Sailfish license.
If it does list a bunch of packages, then you could try
zypper install aliendalvik
and that will probably tell more details on why the AppSupport can’t be installed.
6 Likes
Thank a lot! The aliendalvik repo indeed seems absent from ssu lr and I get the “No packages found.” when attempting to install it.
[defaultuser@XperiaXA2 ~]$ ssu lr
WARNING: ssu.ini does not seem to be writable. Setting values might not work.
Enabled repositories (global):
- adaptation-common ... https://releases.jolla.com/releases/5.0.0.72/jolla-hw/adaptation-common/armv7hl/
- adaptation0 ... https://store-repository.jolla.com/releases/5.0.0.72/jolla-hw/adaptation-qualcomm-sony-nile/armv7hl/
- apps ... https://releases.jolla.com/jolla-apps/5.0.0.72/armv7hl/
- customer-jolla ... :///features/5.0.0.72/customers/jolla/armv7hl/
- hotfixes ... https://releases.jolla.com/releases/5.0.0.72/hotfixes/armv7hl/
- jolla ... https://releases.jolla.com/releases/5.0.0.72/jolla/armv7hl/
Enabled repositories (user):
- sailfishos-chum ... https://repo.sailfishos.org/obs/sailfishos:/chum/5.0_armv7hl/
- store ... https://store-repository.jolla.com/h3113/armv7hl/?version=5.0.0.72
I just noticed that the customer-jolla URL is also mangled. Could that be causing my problems?
1 Like
You have a valid licences?
Yep. I was able to fix it by editing /usr/share/ssu/features.d/customer-jolla.ini and replacing %(releaseRepoBaseURL) with https://releases.jolla.com.
This is really only a band aid fix since I don’t know why releaseRepoBaseURL is returning garbage and probably points to deeper problems with my installation, likely from a previous failed update.
But after this hack I was able to install feature-alien and reinstall aliendalvik, now working nicely with the new settings showing up.
4 Likes
Yes, and it’s a bit weird that it was wrong only for the customer-jolla repo. There might be also other things currently broken in your system, which may be hard to track down, and my recommendation would be to reflash the device at some point.
3 Likes
5.0.0.72 also went well OTA with 10 III from 5.0.0.71.
I had to update my idiot phone to Lineage 23 / Android 16 the other day. Downloading MindtheGapps took a while and in the end I had to do a factory reset because something seems to have timed out. Not much damage, though. It’s my idiot phone but once again I am glad updates are so easy and mostly stable with SFOS.
1 Like
No, after the first attempt, the XA2 was still on 5.0.0.68. After the second attempt, it went directly to 5.0.0.72 from 5.0.0.68.
Thanks, Jolla. The update from 5.0.0.71 to 5.0.0.72 went smoothly. No new bugs so far on Xperia 10 III.
The bug where App Support doesn’t start automatically is still there, as mentioned in the first post. I hope you find the bug. Sometimes AAS just acts up and crashes – it won’t start anymore and I have to restart.
(Translated/Übersetzt mit DeepL)
1 Like
Hi.
I do this small update yesterday on my Sony Xperia 10III. Now the Android App Support is not working anymore, so I can´t start Telegram, Signal.
I had to do the same on my 10 V
Xperia 10 III - Update went smooth. No issues with Dalvic or anything else.
Are there any ideas how I can fix it, so I can use the android apps again?
Now its working again. I had to reboot the phone after deinstalling and installing the android support app again
8 Likes
X10III updated fine from .71 to .72
The AAS autostart on bootup still fails ( AAS works if manually started).
Interestingly it feels globally snappier and reboots faster, although this tiny upgrade doesn’t seem to introduce anything related.
Whereas I can’t quantify the “snappiness” side, the boot time dropped from ~1min20-30s to about 1min. It felt slow since at least .68. For once a positive side-effect 
3 Likes
X10 updated from .71 to .72 (my testphone).
AAS autostart worked the first restart and failed the second one.
After the failed one, on starting an A. app, it said “starting AAS” but didn’t. (Checked in settings/AAS). Start AAS manually worked. Android apps (e.g. browser) work and have network connection OK.
I’m also curious now what will happen after some reboots. Usually things go better than before after a few reboots.
UI is snappy and fast without re-doing the tweaks I made before in old system.
Device seems to work fine.
Thank you @Jolla !
edit: rebooted for test, AAS still not auto-starts.
Q: What is ‘Allow running MicroG’? Is MicroG now implemented in AAS ?
4 Likes
MicroG had to be installed manually in the past
1 Like
You could read this or the other thread esp. about this problem. 
In short:
Disable autostart in AAS settings
1 Like
No, MicroG still needs to be installed separately.