… indeed it is. 
3 Likes
Thank you! It works. Nice. Well done.
I have filed an internal bug about this. This issue is “tracked”.
6 Likes
Since .12 i seem to have more internet connection problems. That shouldn’t really have changed since .11, right? Are there instructions on how to gather logs for that? Are logs needed?
1 Like
I have the feeling the OOM killer may have become overzealous (or something new has eaten up a lot of memory), since for example Signal keeps restarting when moving from one chat to another.
Thank you for the update.
I have to report a few bugs.
On my 10 III MagicEarth disappeared. It’s now impossible to install apps from Aurora. Downloading new apps and updating within Aurora works but installing doesn’t happen.
On my XA2 plus MagicEarth is still there, but same story: updating of Android apps works, but not installing.
On the XA2 plus suddenly no sound when calling, making phone calls doesn’t work at all.
Installing Apps from Aurora is still possible. The problem is that the “install” window is invisible. But it is there. You (just 
)have to guess the right place, see Android apps not installing on 4.6.0.12
Or you change the Android setting s a described here: [Release notes] Sauna 4.6.0.12 - #47 by Juanro49
3 Likes
There is a blue installing window/button where I can tap on after having downloaded the app: ‘install’. However nothing happens when I tap on it and the window/button keeps saying ‘installing’.
Same with updates.
Are you using the latest version of Aurora Store (4.4.4)?
From what you are describing it appears to me that you might be using an older version of Aurora Store
You are right, I did use Aurora 4.3.5. Thank you. Updated it with F-Droid and tried to install MagicEarth again on Aurora. This failed : the app is nowhere to be seen. Not on the device, nor in the small list of installed Android apps within Aurora, neither on the list of downloads in Aurora because that list has gone now. Tapping on the install button activates it for a few seconds, then it stops.
I can confirm that AppSupport and WhatsApp are crushing consequently. I often see information that the storage is complete, which is inaccurate. Many times, I see info unmount external storage.
In another application, the mobile network does not work - only with WLAN connections.
2 Likes
As already with [Sauna 4.6.0.11], further updating to [Sauna 4.6.0.12] again :
- overwrites custom SFOS root certificates
- and custom AppSupport root certificates
which then need to be added manually again.
Also
-
"Open GApps" needs to be re-installed ( → the famous bash )
as the PlayStore sends AppSupport into a persisting start-loop.
Before running the bash, lz4-support and lz4-supporting squash-tools need to be installed ( again ).
Due to the start-loop of AppSupport you can’t remove the PlayStore manually from the app-gird.
You just need to hope all goes well, while executing the bash. Luckily it does.
Fortunately all Android app settings incl. custom Android Firefox root certificates are not inflicted.
Try “apkd-launcher com.android.settings” instead.
I suggest using shizuku so aurora store (and maybe other stores?) automatically install apps without pompts or dialogues
Edit: this inspired me to create this topic if anyone’s interested Guide - Installing Shizuku
3 Likes
Well amidst all the doom and gloom installation issues reported, I can happily say all is working well post .12 installation on my 10 III.
Albeit I’m not using android support, just stock SFOS.
Updated from 4.5.0.25 with sfos_upgrade 4.6.0.12 on Xperia 10 II (my daily driver) with no problem (as I was unable to dismiss upgrade to already downloaded 4.6.0.11). At first it looks nothing broke by this update. Those android apps that did not work before upgrade still do not work…
No app was removed by upgrade this way. With gui there were 30+ packages to uninstall - this was the reason to hesitate proceeding with upgrade through GUI.
Looks Aurora store is unable to update android apps.
This was discussed earlier in this thread:
3 Likes
Another working solution is simply tapping blindly where the invisible “install” button in the invisile window is. Invisibilty is the challenge. In fact, the usuale button is there
2 Likes
I saw you mentioning “… a Sailjail timing issue means they won’t start from the app grid”, has this been established as the reason for native SF apps sporadically not starting from the app grid (resp. starting with an extreme lag, minutes after the circulating app placeholder vanished), while Android apps do so without problems at the same time? At least since this year, I have regular issues with not being able to open e.g. the Messages or SailOTP app (especially annoying, since I have to use my XA2 as the 2FA authenticator for a long list of services), but never found resp. saw a corresponding “global” thread for this on FSO (only for specific apps not starting sometimes, not “native apps not starting in general in the wrong moment”), also given that FSO’s search feature isn’t very good at spitting out the best-suiting results, unfortunately.