I thought everything Android got deleted, including your apps & data.
That doesn’t happen (any more?). But I don’t know what does happen.
You are reinstalling
these
rpm -qa |grep -E "alien|apkd|appsupport"
but
feature-alien-0.4.2-1.2.3.jolla.aarch64
packages.
You can read about removing apps&data HERE.
App Support is based on an LXC container for Android now. My question was more about what happens to that?
App Support reinstalled so fast, I’m guessing nothing happened to it.
So I have to uninstall, delete the container manually with lxc-destroy and hope App Support recreates it?
As you’re probably aware, I’m trying to make a fresh Android installation for Revolut.
I believe that you need to remove (for SFOS 4)
rm -rf /home/.android
rm -rf /home/defaultuser/android_storage
dirs where all Appsupport apps&data are stored and reboot (see “Brutal way”)
LXC container is created from downloaded appsupport-image-unprivileged (or privileged 
) and user data from directories mentioned above.
I can’t find this. Tried find . -name "appsupport"
lxc-ls -f shows no App Support LXC so is it hidden?
This is the name of rpm that you install via packer manager.
The name of LXC appsupport container is “default”.
lxc-ls -f (elevated) returns nothing, even when I’m actively using Android apps. I’m SSHing in via MobaXterm.
lxc-ls -n default --lxcpath=/tmp/appsupport
2 Likes
Thanks!
lxc-destroy -n default --lxcpath=/tmp/appsupport deleted it. [Stop App Support & uninstall it first]
Aurora lost its settings? But newly-installed Revolut is still complaining about root, sadly, though I’m not surprised it wasn’t corrupted, being read-only.
So Revolut is perhaps picking up on some Android app installation. Next step, deleting .android and android-storage.
Not sure if this is helpful but a Reddit user is claiming Revolut is using DexProtector/Licelus. There’s a video for removing it from a decompiled APK but I think that’s one of my last options.
Why are you expecting the container to matter here?
The data seems to be stored outside it…
Why are you expecting this to change?
1 Like
I’m not really, it’s just less destructive to my installation to check that first.
Why are you expecting this to change?
Because no-one else here seemingly has the problem (though isn’t going through verification) and because others have fixed it with Magisk Alpha et al.
Also, there’s a good chance I can fix it by editing the APK but it might take me weeks & a lot of handholding.
I’ve broken my normal capacity to even install App Support now.
I uninstalled it, ran
lxc-destroy -n default --lxcpath=/tmp/appsupport
rm -rf /home/.android
rm -rf /home/defaultuser/android_storage
… then reinstalled
Reboot → start App Support says “unable to start”. Look for the line appsupport.service: Failed with result ‘protocol’
catlogs here. Phone is the 10 iii, latest version of SF.
PS Android app icons are still clogging up my app selector and can’t be uninstalled.
You can remove them from home/defaultuser/.local/share/applications.
Something did a cleanup and the icons got removed automatically.
Somehow the containers package got damaged and lxc-ls is no longer recognised as a command! lxc-destroy is.
… else container support might get broken? But since I did the brutal method plus lxc-destroy, I’m thinking there’s a serious bug somewhere that’s borked my App Support potential and containers.
Whatever did the cleanup got rid of those 3 apps. But lxc-ls is still not recognised and App Support still won’t start.