Android AppSuport not running after loading any installed Androip apps in C2

General
1

Good Day Sailfish OS Community.

The Android AppSupport in my C2 phone does not working properly.

Any third party installed app via F-droid or Aurora Store triggers somethings that causes the AppSupport to turn itself off and on constantly for a while. Then The AppSupport turns itself off and I am not able to turn it on. It simply goes into this loop of trying to turn itself on and then turns off…

The only solution is to reboot the phone but if I load any android apps, the phenomena starts over again…

Since this phenomena exists, I am not able to use the browser (not the Jolla’s) and those android apps, including my banking app, which worked well previously.

Another issue is that the Brightness, Ringtone volume and Volume go down to Zero from time to time without me doing anything with them. Those were set to maximum when I started to use my C2 phone.

My Jolla and Android accounts are active in the Settings under the Accounts.

Please advise,

Eve

2

Maybe this is this issue: [10 III] [5.0.0.71] Android App Support does not start when “Start Android App Support when device starts” is enabled?

If so, try to disable AppSupport Auto-start-on-boot (and then start it manually after each reboot). Maybe this helps

3

Down to Zero or stop working?

But please create separate topics next time. Otherwise the responses can be convoluted, unclear and hard to find for others.

4

Could it be one Android app causing the issue?

Try to

  1. stop AAS
  2. rename /home/defaultuser/android_storage
devel-su
cd /home
mv .appsupport .appsupport.bak
mv appsupport-root appsupport-root.bak

Now try again. If that works you can start figuring out which bit in one of these folders was the issue.

5

I tried this. When I turn on the AAS manually, then load any android app, the AAS goes into the loop…

6

Understood. Since the phenomena did not happen since this post, I am continuing to observe this in my phone. If this happens again, I will open a new post.
These modules never stopped working. They went down to zero but the Ringtone Volume option disappeared from the upper menu few times, and then I found out that it was ‘unchecked’ somehow from the Menu.

1 Like
7

Oh. Then I fear I’m out of answers :confused:

8

Some do report that after turning off at boot in time or few reboots they don’t experience that. There is a topic with the solution if that’s not the case for you. It involves uninstal AAS and reinstall. But manual backup of andy apps is needed to restore them later IIRC.

11

I do not have many android apps. So, I uninstalled them one by one and after each app removal, I checked whether the AAS will go into the loop. It goes into loop with any android app that is loaded.

12

Did you already tried also uninstal AAS and reinstall?

13

Yes, I did uninstall and re-installed with reboots and without reboots. It did not help.

One note. I have a banking app that I need everyday to approve payments. This is the only app I can use for a short period of time after re-installing the AAS, but the AAS stops after some time and I need to uninstall and re-install it again… So, when I open the banking app and log in, the messages about payment approvals appear on the top of the screen where I need to tap and approve the payments in a pop-up window. This works. However, if I start to scroll on the main page and enter into menu, the AAS stops working after few seconds. Then I just close all the open apps and uninstall the AAS and reboot the phone…

The paid feature is not working and no fixes yet by the developers.

14
  1. try restarting apkd-bridge and apkd-bridge-hw

systemctl –user restart apkd-bridge

  1. check if your getting ooms:

dmesg | grep ‘lowmem\|oom\|Out of memory’

maybe try disabling oomkiller or setting minfree to very low values (note that this is generally a bad idea but i find it useful as a diagnostic, and it goes away after reboot)

devel-su
echo ‘0,0,0,0,0’ | tee /sys/module/lowmemorykiller/parameters/minfree

(again, this is just to diagnose the issue, not fix it)

1 Like
15

See also: https://forum.sailfishos.org/t/android-app-support-crashes-after-starting
which almost completely matches what is described in the top post.

16

This works the way that I do not need to reboot my C2 phone in order to re-start the AAS.

Note:
I turned-on the early access updates and updated from the early releases channel to 5.0.0.73 with AAS uninstalled. After the update, re-installed the AAS. The Jolla shop still has the not-recently-bug-fixed version.